[Desktop-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
Marking as verified according to comment #21 ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic ** Changed in: software-properties (Ubuntu) Status: Confirmed => Invalid ** Changed in: software-properties (Ubuntu Mantic) Status: Confirmed => Invalid ** Changed in: software-properties (Ubuntu Noble) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Invalid Status in ppa-purge source package in Mantic: Fix Committed Status in software-properties source package in Mantic: Invalid Status in ppa-purge source package in Noble: Fix Released Status in software-properties source package in Noble: Invalid Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version
[Desktop-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
The updates look good, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Confirmed Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Technically, Steve Langasek already removed libglib2.0-0 from noble release just before release. This upload is necessary to ensure that we don't accidentally bring it back. Test Case - 1. Is libglib2.0-0 built? 2. Run rmadison libglib2.0-0 There should be 0 results for noble, noble-proposed, or noble-updates 3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu 22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is currently set to disallow upgrades to 24.04 LTS. If this is still the case when it is time to verify this SRU, you can manually substitute jammy → noble in /etc/apt/sources.list for purposes of testing this upgrade, probably in a VM since that's not the supported way to upgrade. Where Problems Could Occur -- Doing an upload to not build a package that already does not exist in Ubuntu 24.04 LTS should have no regression potential. The only other change in this SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 is also removed for people who were using Ubuntu 24.04 LTS early. That also should not cause problems since the package was an empty transitional package for early Ubuntu 24.04 LTS users. Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by removing the transitional package and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 We have landed the removal in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. The removal was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. (Although that particular detail was fixed by the removal that already happened.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+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 2063221] Re: Drop libglib2.0-0 transitional package
Hi Jeremy, This looks mostly good, AFAICT. Could you please complete the SRU bug template by adding the section 'Where problems could occur' / 'Regression potential'? [1] And although the 'Test Case' is feasible to understand, based on the 'Impact' section, it would be nice to have a 'functional' test, if at all possible/reasonably doable. For example, I tried to reproduce the thunderbird deb2snap issue, but it didn't. I realize there might be a more complex package setup/install list to trigger it, but maybe there's something simpler that you are aware of. (Or if it's too complex / not worth it, just clarifying that and mentioning what shouldn't change / how to check for no regressions, would be OK too; I tried to convey that in comment #1). Thanks! [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Changed in: glib2.0 (Ubuntu Noble) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Incomplete Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Where Problems Could Occur -- We have landed the change from this SRU in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. This SRU was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. Hmm, we can't actually drop libglib2.0-0 after release, can we? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+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 2063221] Re: Drop libglib2.0-0 transitional package
I tested this with a local package build and local repo in a mantic container,
doing an `apt --dry-run dist-upgrade` without/with that repo (w/ noble apt
sources list),
and manually download/run noble's release upgrader without/with that repo.
The behavior is the same (ie, no regressions) as expected;
libglib2.0-0 is removed in favor of libglib2.0-0t64 in all cases.
Test 1)
Just Noble:
$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2
$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' |
fgrep libglib2.0
17: libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6
libglib2.0-0
30: libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79: libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu1 Ubuntu:24.04/noble
[amd64]) []
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu1
Ubuntu:24.04/noble [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu1 Ubuntu:24.04/noble [all])
Noble and local build/repo:
$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu3
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2
$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' |
fgrep libglib2.0
17: libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6
libglib2.0-0
30: libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79: libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu3 localhost [amd64])
[]
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu3 localhost [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu3 localhost [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu3 localhost [all])
Test 2)
Just Noble:
$ dpkg -l | fgrep libglib2.0
rc libglib2.0-0:amd64 2.78.0-2
amd64GLib library of C routines
ii libglib2.0-0t64:amd64 2.80.0-6ubuntu1
amd64GLib library of C routines
ii libglib2.0-bin 2.80.0-6ubuntu1
amd64Programs for the GLib library
ii libglib2.0-data 2.80.0-6ubuntu1
all Common files for GLib library
$ dpkg -l | grep thunderbird
ii thunderbird 2:1snap1-0ubuntu3
amd64Transitional package - thunderbird -> thunderbird snap
$ snap list thunderbird
Name Version Rev Tracking Publisher Notes
thunderbird 115.10.1-1 470 latest/stable canonical✓ -
Noble and local build/repo:
$ dpkg -l | fgrep libglib2.0
rc libglib2.0-0:amd64 2.78.0-2
amd64GLib library of C routines
ii libglib2.0-0t64:amd64 2.80.0-6ubuntu3
amd64GLib library of C routines
ii libglib2.0-bin 2.80.0-6ubuntu3
amd64Programs for the GLib library
ii libglib2.0-data 2.80.0-6ubuntu3
all Common files for GLib library
$ dpkg -l | grep thunderbird
ii thunderbird 2:1snap1-0ubuntu3
amd64Transitional package - thunderbird -> thunderbird snap
$ snap list thunderbird
Name Version Rev Tracking Publisher Notes
thunderbird 115.10.1-1 470 latest/stable canonical✓ -
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0
[Desktop-packages] [Bug 2047146] Re: Issues Encountered with Ubuntu 23.10 - Icon Minimization and Full-Screen App Behavior
** Package changed: ubuntu => gnome-desktop (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2047146 Title: Issues Encountered with Ubuntu 23.10 - Icon Minimization and Full- Screen App Behavior Status in gnome-desktop package in Ubuntu: New Bug description: # System Details Report --- ## Report details - **Date generated:** 2023-12-21 14:00:57 ## Hardware Information: - **Hardware Model:** ASUSTeK COMPUTER INC. N552VW - **Memory:** 32,0 GiB - **Processor:** Intel® Core™ i7-6700HQ × 8 - **Graphics:**NVIDIA GeForce GTX 960M - **Graphics 1:** NVIDIA GeForce GTX 960M - **Disk Capacity:** 1,5 TB ## Software Information: - **Firmware Version:**N552VW.304 - **OS Name:** Ubuntu 23.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.1 - **Windowing System:**X11 - **Kernel Version:** Linux 6.5.0-14-generic Dear Ubuntu Development Team, I recently managed to install the Ubuntu image with the kernel version 6.6.7. Before installing Ubuntu 23.10, I noticed logs related to the configuration of the Linux 6.6.7 kernel, which, however, did not boot successfully on my system. After successfully installing Ubuntu 23.10, I removed the newly installed 6.6.7 kernel and reverted to a more stable version of the kernel (version 6) that boots without any issues. However, I've encountered a unique problem post-installation. When I minimize applications, their icons appear in the upper right corner of the horizontal toolbar as expected. However, the mouse cursor behaves oddly around these icons. Even if I move the cursor slightly away from an icon (about a hundred pixels or so), and click on an area of the desktop (not on the toolbar itself), it unexpectedly activates the corresponding minimized application. This issue, which did not occur before, is not urgent but becomes increasingly inconvenient over time. Furthermore, in certain applications like Spotify, I sometimes encounter another issue where the window control buttons (close, maximize, minimize) disappear, and the application enters a full-screen mode, akin to a video game. This behavior seems sporadic, and I'm unsure how to consistently resolve it. Could these issues be related to screen settings or other system configurations? Also, is the full-screen behavior a known bug? Any guidance on avoiding or rectifying these problems would be greatly appreciated. Thank you for your attention to these matters. Best regards, Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2047146/+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 2046221] Re: Get help with matrix does not lead to ubuntu support
Marking as wishlist per request from OP in IRC ** Changed in: ubuntu-docs (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2046221 Title: Get help with matrix does not lead to ubuntu support Status in gnome-user-docs package in Ubuntu: Fix Committed Status in ubuntu-docs package in Ubuntu: Confirmed Bug description: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/2046221/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
Verification done on mantic-proposed. On arm64 with ubuntu-desktop-minimal installed, running do-release-upgrade from lunar to mantic (with mantic-proposed enabled and pinning setup) does install `protection-domain-mapper` and `qrtr-tools` (`flash-kernel` already installed). Test Steps: --- Part 1) - launch aws arm64 instance with Ubuntu 22.04/jammy Part 2) - do-release-upgrade to 22.10/lunar - install ubuntu-desktop-minimal - enable lunar-proposed (converted to mantic-proposed in do-release-upgrade later) Part 3) - set pin priority for mantic-proposed/ubuntu-desktop-minimal - do-release-upgrade to 23.04/mantic Details: --- Start on Jammy: $ lsb_release -cs jammy $ dpkg --print-architecture arm64 $ uname -m aarch64 $ sudo apt update && sudo apt -y dist-upgrade && sudo reboot Upgrade to Lunar: $ sudo sed -i 's/^Prompt=.*/Prompt=normal/' -i /etc/update-manager/release-upgrades $ do-release-upgrade Checking for a new Ubuntu release = Welcome to Ubuntu 23.04 'Lunar Lobster' = ... $ lsb_release -cs No LSB modules are available. lunar Prepare for testing: $ sudo apt install -y ubuntu-desktop-minimal Test/Before: (only 1 out of 3 packages installed) $ dpkg -s flash-kernel protection-domain-mapper qrtr-tools | grep -e Package: -e Version: dpkg-query: package 'protection-domain-mapper' is not installed and no information is available dpkg-query: package 'qrtr-tools' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files. Package: flash-kernel Version: 3.106ubuntu14 Enable -proposed: $ sudo add-apt-repository -yp proposed cat
[Desktop-packages] [Bug 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
Hi Rico,
Thanks for the clarifications!
> 1) 2) 3) 6) are packaging bugs regarding Java support
> Those are needed to allow Java support to be disabled on specific archs if
> needed.
> Fortunately this wasn't required yet while the already applied mitigations to
> the bridgetests still are sufficient.
So, it does look like this is not _required_ right now, correct?
(i.e., no archs are getting Java support disabled in this SRU.)
I take this from your comment ("if needed" and "wasn't required yet")
_and_ `d/rules` assignments of OOO_BASE_ARCHS and OOO_REPORTBUILDER_ARCHS,
which remain the same value ("amd64 arm64 armhf ppc64el riscv64 s390x").
In this case, I guess such changes should not be included in this SRU,
but left for when it is actually needed; maybe others can comment too.
And perhaps a separate bug report with more details would be recommended,
but please do not work on this at the moment, while others don't comment.
> 4) 5) follow the upstream CMIS changes
> Upstream bumped the internal requirement of libcmis which finally allows the
> proper CMIS service support.
> Unfortunately it had to be disabled before because it was broken.
Understood.
I reviewed some of the docs/changes related to this, and this scenario
is more complex, since this (CMIS support) is a feature, with different
considerations for SRU (e.g., support in LTS and newer interim releases).
I'll have to ask for others with more experience in such case to comment,
but these are some thoughts for now:
CMIS is a standard related to a feature for opening/saving files on remote
servers [1].
"LibreOffice supports many document servers ... that implement the OASIS CMIS
standard."
[1] https://help.libreoffice.org/7.6/en-US/text/shared/guide/cmis-
remote-files.html
In general, features only land in the development release, until feature freeze
[2],
but there are cases for stable releases as well, when considering LTS releases:
[3]
[2] https://wiki.ubuntu.com/FeatureFreeze
[3] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
"""
For Long Term Support releases we sometimes want to introduce new features.
...
To avoid regressions on upgrade, any such feature must then also be added to
any newer supported Ubuntu release.
...
For new upstream versions of packages which provide new features, but don't fix
critical bugs, a backport should be requested instead.
"""
So, theoretically, enabling CMIS in Mantic could meet the requirement to have it
in Jammy, and it is (jammy-updates 1:7.3.7-0ubuntu0.22.04.3 has ENABLE_CMIS=y).
It just turns out to be disabled in Lunar (lunar-updates
4:7.5.8-0ubuntu0.23.04.1
has ENABLE_LIBCMIS=n, I guess it might be due to issues/broken as you
mentioned?),
so there's some intermediary release with it disabled.
> (continuing)
> Upstream chose Openssl as official choice for this feature/combination which
> was followed here.
> But it would be possible to continue using gnutls if the SRU requires it.
Ack, thanks for clarifying.
In this case, if libcurl4-gnutls/openssl were only being used due to
ENABLE_CMIS,
which is disabled in mantic-release, then maybe we could change it, as it would
be
effectively the only usage of it.
But it turns out it's apparently already used due to ENABLE_WEBDAV, so changing
it
would affect something already present in mantic-release, so at least initially,
keeping it as-is sounds better -- unless there's an upstream rationale that
gives
good reasons for switching, sure (and assessing/dealing with the change in
Mantic).
I'll ask for an additional review on these points.
Thanks again for all your work on this SRU and its review!
--
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/2044019
Title:
[SRU] libreoffice 7.6.3 for mantic
Status in libreoffice package in Ubuntu:
Fix Released
Status in libreoffice source package in Mantic:
Incomplete
Bug description:
[Impact]
* LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line:
https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release
* Version 7.6.2 is currently released in mantic. For a list of fixed bugs
compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3
(that's a total of 116 bugs):
https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs
7.6.3 RC2 is identical to the 7.6.3 release
* 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
[Desktop-packages] [Bug 2045754] [NEW] Graphics card driver crash
Public bug reported:
I was just browsing the web when the bottom half of the display became black,
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.
I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.
After reboot everything is working again for now.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec 6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-06 (30 days ago)
dmi.bios.date: 05/18/2023
dmi.bios.release: 16.18
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1618
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X670E-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1618:bd05/18/2023:br16.18:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze kubuntu mantic ubuntu wayland-session
** Attachment added: "dmesg log of the crash"
https://bugs.launchpad.net/bugs/2045754/+attachment/5726688/+files/dmesg-gpu-txt
--
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/2045754
Title:
Graphics card driver crash
Status in xorg package in Ubuntu:
New
Bug description:
I was just browsing the web when the bottom half of the display became black,
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.
I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.
After reboot everything is working again for now.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec 6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
InstallationMedia:
[Desktop-packages] [Bug 1588443] Re: package fonts-sil-abyssinica 1.500-1 failed to install/upgrade: el paquete fonts-sil-abyssinica no está listo para configurarse no se puede configurar (estado act
I don't know why the error occurred. A newer version (2.201-1) of the package has been uploaded to Debian sid that hopefully does not cause the same errors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-sil-abyssinica in Ubuntu. https://bugs.launchpad.net/bugs/1588443 Title: package fonts-sil-abyssinica 1.500-1 failed to install/upgrade: el paquete fonts-sil-abyssinica no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in fonts-sil-abyssinica package in Ubuntu: New Bug description: Error al instalar e iniciar SO ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fonts-sil-abyssinica 1.500-1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: fonts-sil-abyssinica: Configure libkf5xmlgui-bin: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 1 12:37:22 2016 DpkgTerminalLog: dpkg: error al procesar el paquete fonts-sil-abyssinica (--configure): el paquete fonts-sil-abyssinica no está listo para configurarse no se puede configurar (estado actual `half-installed') ErrorMessage: el paquete fonts-sil-abyssinica no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2016-05-23 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fonts-sil-abyssinica Title: package fonts-sil-abyssinica 1.500-1 failed to install/upgrade: el paquete fonts-sil-abyssinica no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-sil-abyssinica/+bug/1588443/+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 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
Hi Rico,
Thanks for the nice and detailed SRU template, and all the testing.
While looking at this, particularly the changes in the packaging,
there are a few points that seem to warrant clarification, since
are apparently not related/supporting the upstream bug fixes, or
are not justified as to why included in a SRU (ie, which issues
or bugs are being addressed).
I checked most of these points with Andreas yesterday, and he too
agreed more details would be required before proceeding with this.
Could please address the points below? That's very appreciated.
Thanks again for all the effort on this!
cheers,
Mauricio
...
Changes:
$ debdiff libreoffice_7.6.2-0ubuntu1.dsc
libreoffice_7.6.3-0ubuntu0.23.10.1.dsc | filterdiff -i '*/debian/*'
There are some changes in debian/ that may warrant some clarification
as they do not fit into the SRU policy for minor release updates
(ie, bug-fix only) or to be related to the bugs fixed by upstream
(ie, to support a bug-fix).
I've looked for similarities in the changelog of previous releases,
but apparently haven't found them as precedents. This is the first
time I'm looking at this package, so I might be missing something.
I'll note specific changes in changelog/rules below, for clarity.
1)
d/changelog
18 +- don't try to install dbreport config modules into
19 + -uiconfig-report-builder if the report builder is disabled
d/rules
413 +ifeq "$(ENABLE_REPORTBUILDER)" "y"
414 mv
$(PKGDIR)-common/$(OODIR)/share/config/soffice.cfg/modules/dbreport \
415
$(PKGDIR)-uiconfig-report-builder/$(OODIR)/share/config/soffice.cfg/modules
416 +else
417 + rm -rf
$(PKGDIR)-common/$(OODIR)/share/config/soffice.cfg/modules/dbreport
418 +endif
Is this possibly a separate bug, as apparently it's not related to
an upstream bug fix; it would be nice to have some clarification.
Maybe this is covered in the SRU policy under "it is also acceptable to
upload new microreleases with many bug fixes without individual
Launchpad bugs for each of them", but I considered such 'many bug fixes'
to be related to the upstream bugs, and this change is on packaging.
2)
d/changelog
20 +- switch OOO_BASE_ARCHS/OOO_REPORTBUILDER_ARCHS variables
21 + (build base on all architectures instead of Java architectures
22 + and report-builder-* only on archs where Java is enabled, not on
23 + "all base archs"); there's -sdbc-{mysql,postgresql,firebird} anyway
d/rules
356 -OOO_BASE_ARCHS := $(OOO_JAVA_ARCHS)
357 +OOO_BASE_ARCHS := $(OOO_ARCHS)
358 $(eval $(call gen_no_archs,OOO_BASE_ARCHS))
359 -OOO_REPORTBUILDER_ARCHS := $(OOO_BASE_ARCHS)
360 +OOO_REPORTBUILDER_ARCHS := $(OOO_JAVA_ARCHS)
Similarly; it would be nice to have some clarification,
and perhaps explain the trailing note about '-sdbc-* anyway'.
3)
d/changelog
24 +- don't try to build Jar_{OOoRunner,test,ConnectivityTools} if Java is
25 + disabled as an extra safety net (instead of checking for junit only)
Similary, it would be nice to have some clarification.
d/rules
399 -ifeq "$(BUILD_TEST_PACKAGES)" "y"
400 - ifeq "$(ENABLE_JUNIT4)" "y"
401 +ifeq "$(ENABLE_JAVA)" "y"
402 + ifeq "$(BUILD_TEST_PACKAGES)" "y"
403 +ifeq "$(ENABLE_JUNIT4)" "y"
404 PATH=$(BUILD_PATH) LD_LIBRARY_PATH=$(BUILD_LD_LIBRARY_PATH)
ARCH_FLAGS=$(ARCH_FLAGS) TMP=`mktemp -q -d` $(MAKE) Jar_{OOoRunner,tes
t,ConnectivityTools}
405 +endif
4)
d/changelog
26 +- re-enable cmis; bump libcmis build-dep to >= 0.6.1
Similarly; it would be nice to have some clarification.
And also the reason to enable it in an SRU? Maybe some relation to
an upstream bug or ubuntu bug? Any changes at behavior/runtime?
(apparently just an internal build dep; why is this needed, and
isn't the archive version (older) sufficient?)
d/rules
343 @@ -356,7 +356,7 @@
344 DICT_DIR=/usr/share/hunspell
345 HYPH_DIR=/usr/share/hyphen
346 THES_DIR=/usr/share/mythes
347 -ENABLE_LIBCMIS=n
348 +ENABLE_LIBCMIS=y
386 @@ -1423,7 +1429,7 @@
387endif
388ifeq "$(ENABLE_LIBCMIS)" "y"
389 ifneq (,$(filter libcmis, $(SYSTEM_STUFF)))
390 - BUILD_DEPS += , libcmis-dev (>= 0.5.2~), libcmis-dev (<< 0.6~)
391 + BUILD_DEPS += , libcmis-dev (>= 0.6.1~), libcmis-dev (<< 0.7~)
392 endif
393else
394 CONFIGURE_FLAGS += --disable-libcmis
5)
27 +- build against libcurl4-openssl-dev instead of gnutls
334 @@ -271,7 +271,7 @@
335 USE_GSTREAMER=y
336 endif
337 ENABLE_CURL=y
338 -CURL_SECTYPE=gnutls
339 +CURL_SECTYPE=openssl
Similarly; it would be nice to have some clarification on its reason,
and potential changes to runtime behavior or functionality.
This is a significant change.
6)
30 + * debian/control.ure.in:
31 +- make ure-java actutally Architecture: %OOO_JAVA_ARCHS%
Similarly, it would be nice to have some clarification.
** Changed in: libreoffice (Ubuntu Mantic)
Status: In Progress => Incomplete
--
You received this bug notification
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
Verification (synthetic) of the XDG_SESSION_TYPE fix in Mantic:
$ lsb_release -cs
No LSB modules are available.
mantic
The packages are downloaded from Launchpad librarian
since previous versions are not available in archive.
Before the fix (reverted) // 1:23.10.12
---
The XDG_CURRENT_DESKTOP variable IS NOT passed in `pkexec ... --env=`.
$ wget https://launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/1:23.10.12/+build/26929436/+files/{ubuntu-release-
upgrader-{core,gtk},python3-distupgrade}_23.10.12_all.deb
$ sudo apt install -y ./ubuntu-release-upgrader-
core_23.10.12_all.deb ./ubuntu-release-upgrader-gtk_23.10.12_all.deb
./python3-distupgrade_23.10.12_all.deb
$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.12
$ export XDG_CURRENT_DESKTOP=just:testing
$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 |
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'
--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty
After the fix (reapplied) // 1:23.10.13
---
The XDG_CURRENT_DESKTOP variable IS passed in `pkexec ... --env=`.
$ wget https://launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/1:23.10.13/+build/26932072/+files/{ubuntu-release-
upgrader-{core,gtk},python3-distupgrade}_23.10.13_all.deb
$ sudo apt install -y ./ubuntu-release-upgrader-
core_23.10.13_all.deb ./ubuntu-release-upgrader-gtk_23.10.13_all.deb
./python3-distupgrade_23.10.13_all.deb
$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.13
$ export XDG_CURRENT_DESKTOP=just:testing
$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 |
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'
--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty,XDG_CURRENT_DESKTOP=just:testing
Latest version (mantic-proposed) // 1:23.10.14
---
The XDG_CURRENT_DESKTOP variable IS passed in `pkexec ... --env=`.
$ sudo add-apt-repository -yp proposed
$ sudo apt install -y -t mantic-proposed ubuntu-release-
upgrader-core
$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.14
$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 |
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'
--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty,XDG_CURRENT_DESKTOP=just:testing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text became unreadable during a distribution upgrade
Status in Cinnamon:
New
Status in Ubuntu MATE:
New
Status in ubuntu-meta package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
Fix Released
Status in ubuntu-meta source package in Mantic:
Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
Fix Committed
Bug description:
[ Impact ]
* On Ubuntu Mate with the Lunar series, when running
ubuntu-release-upgrader, the displayed font of running
applications (including the upgrader) becomes very corrupted.
* This is not just a display problem, it is also a functional one.
The release upgrader will have text corrupted to the point
where a dialog asks a decision, and displays two buttons, but the
text is unreadable and one has to guess which button is the one
that carries out their desired action.
* In the early parts of the upgrader tool, users are told in bold:
"To prevent data loss close all open applications and documents."
This is just before the "Start Upgrade" button is available.
But they may not do so. Many applications may have a corrupted
font.
* To address this, an additional environment variable is being
passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
critical criteria for making the Mate version of the fix work.
* Also in the change are
* an update to tests
* from pre-build.sh
* an update of the mirrors.cfg, adding and removing several
mirrors
* a refresh of the po files
[ Test Plan ]
* acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
* as user, run "update-manager -d"
* monitor the "Distribution Upgrade" screen. During the "Installing
the upgrades" step (and mind that this step will be long), observe
the text of the "Distribution Upgrade" screen and verify that the
font does not corrupt.
* Repeat the above for Ubuntu Desktop
[ Where problems could occur ]
* We are changing, at release time, ubuntu-release
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
Summary for Mantic SRUs. There are 3 LP bugs combined in mantic-proposed (list sorted by package version so it's helpful). 1) Bug 2034986, used twice, 1A) First for 1:23.10.9, for 'fix v1': * Temporary font for Ubuntu MATE (LP: #2034986) It's released to mantic-updates with 1:23.10.10 (fix for autopkgtests). 1B) Later for 1:23.10.11, for XDG_CURRENT_DESKTOP: * do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986) It's reverted in 1:23.10.12: * Temporarily revert "do-release-upgrade: pass XDG_CURRENT_DESKTOP env var" and reapplied in 1:23.10.13: * do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986) 2) Bug 2039356, used for 'fix v2' in 1:23:10.12: * Adjustments of unreadable text workaround (LP: #2039356) 3) Bug 2039172, used for an unrelated quirk: * DistUpgradeQuirks: prevent upgrades on BIOS systems with XFS /boot (LP: #2039172) ... So, for verification, we have to consider 1:23.10.11 up to .14. .11 doesn't need verification, as it's reverted in .12 .12 is verified (comment #65 / bug 2039356 comment #3) .13 is not yet verified (comment #65, #66) .14 is verified, but pending questions (bug 2039172 comment #9) Thus, it seems what is pending for releasing mantic-proposed is verification for .13 (that I'm happy to do synthetically), plus a question for .14 (I'd be be happy to help, if needed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" -
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
Happy to (in addition to comment #19) confirm that qpdf + libqpdf29 from noble-release and mantic/lunar-proposed fix the issue. noble: --- $ lsb_release -cs No LSB modules are available. noble $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf | grep Version: Version: 11.6.3-1 $ qpdf --check 018.pdf checking 018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect mantic: --- $ lsb_release -cs No LSB modules are available. mantic $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.5.0-1 Version: 11.5.0-1 $ qpdf --check 018.pdf WARNING: 018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: 018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: 018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: 018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: 018.pdf: file is damaged WARNING: 018.pdf (offset 110267): xref not found WARNING: 018.pdf: Attempting to reconstruct cross-reference table qpdf: 018.pdf: unable to find trailer dictionary while recovering damaged file $ sudo add-apt-repository -yp proposed $ sudo apt install -y -t mantic-proposed qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.5.0-1ubuntu1 Version: 11.5.0-1ubuntu1 $ qpdf --check 018.pdf checking 018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect lunar: --- $ lsb_release -cs lunar $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.3.0-1 Version: 11.3.0-1 $ qpdf --check 018.pdf WARNING: 018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: 018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: 018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: 018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: 018.pdf: file is damaged WARNING: 018.pdf (offset 110267): xref not found WARNING: 018.pdf: Attempting to reconstruct cross-reference table qpdf: 018.pdf: unable to find trailer dictionary while recovering damaged file $ sudo add-apt-repository -yp proposed $ sudo apt install -y -t lunar-proposed qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.3.0-1ubuntu1 Version: 11.3.0-1ubuntu1 $ qpdf --check 018.pdf checking 018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Released Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Fix Released Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
Marking Noble as Fix Released (11.6.3-1). $ git log --oneline -1 pkg/ubuntu/noble | cat 03517080d29d 11.6.3-1 (patches unapplied) $ git show pkg/ubuntu/noble -- libqpdf/QPDFTokenizer.cc ** Changed in: qpdf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Released Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Fix Released Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change
[Desktop-packages] [Bug 2043407] Re: icons-notifications-counter keeps active after program closes
Setting as wishlist per request from OP. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2043407 Title: icons-notifications-counter keeps active after program closes Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu desktop 24.04 development branch @ 13/11/2023 with kernel 6.5.0-10-generic With the new icons-notifications-counter enabled the program counts like expected until notification area has been readed and cleaned, the count disappears from the dock icon. But when the program closes, the count number remains active on a pinned icon on the dock would it not be better to remove the count when program closes? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell-extension-ubuntu-dock 87ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 13 17:50:40 2023 InstallationDate: Installed on 2023-11-09 (4 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to noble on 2023-11-09 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2043407/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
** Changed in: ubuntu-meta (Ubuntu Noble) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Fix Committed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image - * protection-domain-mapper [2] and qrtr moved from universe to main in Mantic. + * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Confirmed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
Updated regression potential with theoretical issues, and other info with status in main for protection-domain-mapper and qrtr. ** Description changed: [ Impact ] - * ubuntu-seeds were changed since last meta update - * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release + * ubuntu-seeds were changed since last meta update + * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] - * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to + * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] - * This is automatically generated change + * This is automatically generated change based on ubuntu-seeds commit + [1]. + + * Theoretically, regressions would occur if new desktop-minimal-recommends +dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): +- have issues on install during release-upgrade; +- have issues on regular system usage (after installed). [ Other Info ] - - * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image + + * ubuntu-meta was not uploaded during final freeze, to prevent + rebuilding all images as changes affect arm64 only, which is a brand new + release image + + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- + seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a ** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. - * Theoretically, regressions would occur if new desktop-minimal-recommends -dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): -- have issues on install during release-upgrade; -- have issues on regular system usage (after installed). + * Theoretically, regressions would occur if new desktop-minimal-recommends + dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): + - have issues on install during release-upgrade; + - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image + * protection-domain-mapper and qrtr moved from universe to main in Mantic. + * flash-kernel is/was already in main. + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a ** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image - * protection-domain-mapper and qrtr moved from universe to main in Mantic. - * flash-kernel is/was already in main. + * protection-domain-mapper [2] and qrtr moved from universe to main in Mantic. + * flash-kernel is/was already in main. - [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- - seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a + [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory + [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package
[Desktop-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
The changes are not yet in the development release (Noble). Submitted MR [1] with noble series update + these changes. [1] https://code.launchpad.net/~mfo/ubuntu/+source/ubuntu- meta/+git/ubuntu-meta/+merge/455081 ** Merge proposal linked: https://code.launchpad.net/~mfo/ubuntu/+source/ubuntu-meta/+git/ubuntu-meta/+merge/455081 ** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu Noble) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu Noble) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Confirmed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2040068] [NEW] Can't connect my Synology NAS from Ubuntu 22.04
Public bug reported: I purchased a Synology DS723+ NAS (under DSM 7.2-64570). I access it without any problem from a Huawei MateBook 14s running Ubuntu 22.04. I can't do it, however, from an Acer Swift 5 also running Ubuntu 22.04. Seen from this PC, I get the following message: "Unable to access location Failed to get list of shares from server: Invalid argument." When I look at my NAS log, the connection attempt gives the following message: "Host [192.168.1.22] failed to connect via [SMB] due to [SMB1 not permitted]." While the message obtained after a successful connection with the other PC is the following: "User [xxx] from [xxx(192.168.1.36)] via [CIFS(SMB3)] accessed shared folder [Photos]." I tried to compare the differences between the 2 PCs running Ubuntu 22.04 without success. Samba was not initially installed on the Acer Swift 5 initially, but the installation did not correct the problem. After reading different posts, I understand that the SMB1 connection is disabled by default since Ubuntu 20.04: I therefore do not understand why the Acer Swift 5 seems to connect like that. And when I run "journalctl -f" on my Acer and then try to connect to the NAS, here is what I get: oct. 09 21:56:32 xxx gvfsd[9205]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. oct. 09 21:56:47 xxx gvfsd[9205]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 18:06:52 2023 InstallationDate: Installed on 2020-02-21 (1337 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: Upgraded to jammy on 2022-09-04 (412 days ago) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2040068 Title: Can't connect my Synology NAS from Ubuntu 22.04 Status in gvfs package in Ubuntu: New Bug description: I purchased a Synology DS723+ NAS (under DSM 7.2-64570). I access it without any problem from a Huawei MateBook 14s running Ubuntu 22.04. I can't do it, however, from an Acer Swift 5 also running Ubuntu 22.04. Seen from this PC, I get the following message: "Unable to access location Failed to get list of shares from server: Invalid argument." When I look at my NAS log, the connection attempt gives the following message: "Host [192.168.1.22] failed to connect via [SMB] due to [SMB1 not permitted]." While the message obtained after a successful connection with the other PC is the following: "User [xxx] from [xxx(192.168.1.36)] via [CIFS(SMB3)] accessed shared folder [Photos]." I tried to compare the differences between the 2 PCs running Ubuntu 22.04 without success. Samba was not initially installed on the Acer Swift 5 initially, but the installation did not correct the problem. After reading different posts, I understand that the SMB1 connection is disabled by default since Ubuntu 20.04: I therefore do not understand why the Acer Swift 5 seems to connect like that. And when I run "journalctl -f" on my Acer and then try to connect to the NAS, here is what I get: oct. 09 21:56:32 xxx gvfsd[9205]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. oct. 09 21:56:47 xxx gvfsd[9205]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 18:06:52 2023 InstallationDate: Installed on 2020-02-21 (1337 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: Upgraded to jammy on 2022-09-04 (412 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2040068/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
I have the same issue on Ubuntu 23.04 using NVIDIA 470.199.02 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 2038377] [NEW] package libdecor-0-plugin-1-cairo:amd64 0.1.0-3build1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tent
Public bug reported: Ao instalar esta dando erro ... ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libdecor-0-plugin-1-cairo:amd64 0.1.0-3build1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 3 16:59:12 2023 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2023-01-24 (252 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: libdecor-0 Title: package libdecor-0-plugin-1-cairo:amd64 0.1.0-3build1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libdecor-0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libdecor-0 in Ubuntu. https://bugs.launchpad.net/bugs/2038377 Title: package libdecor-0-plugin-1-cairo:amd64 0.1.0-3build1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in libdecor-0 package in Ubuntu: New Bug description: Ao instalar esta dando erro ... ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libdecor-0-plugin-1-cairo:amd64 0.1.0-3build1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 3 16:59:12 2023 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2023-01-24 (252 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: libdecor-0 Title: package libdecor-0-plugin-1-cairo:amd64 0.1.0-3build1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdecor-0/+bug/2038377/+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 2035397] [NEW] I had a problem with HDMI
Public bug reported: I don't know a lot about Linux and Ubuntu, but recently, due to college, I did a duo boot so I could have both Windows and Linux. But, whenever im at Linux, for some reason, my screen doesn't share with another monitor through HDMI, but with Windows it does. So i searched for some instructions, and ive been told to try and run this code in my therminal ubuntu-bug xorg, and that's why im here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:56:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] [1d05:1116] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited GA106M [GeForce RTX 3060 Mobile / Max-Q] [1d05:1116] InstallationDate: Installed on 2023-08-31 (13 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Avell High Performance A70 LIV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=c99dc4b0-1110-43e9-a231-5487f4e4ce0d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07AVE00 dmi.board.asset.tag: Standard dmi.board.name: Avell A70 LIV dmi.board.vendor: Avell High Performance dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: Standard dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07AVE00:bd02/22/2021:br5.17:efr1.14:svnAvellHighPerformance:pnA70LIV:pvrStandard:rvnAvellHighPerformance:rnAvellA70LIV:rvrStandard:cvnAvellHighPerformance:ct10:cvrStandard:skuA70LIV: dmi.product.family: A70 LIV dmi.product.name: A70 LIV dmi.product.sku: A70 LIV dmi.product.version: Standard dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2035397 Title: I had a problem with HDMI Status in xorg package in Ubuntu: New Bug description: I don't know a lot about Linux and Ubuntu, but recently, due to college, I did a duo boot so I could have both Windows and Linux. But, whenever im at Linux, for some reason, my screen doesn't share with another monitor through HDMI, but with Windows it does. So i searched for some instructions, and ive been told to try and run this code in my therminal ubuntu-bug xorg, and that's why im here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:56:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] [1d05:1116] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited GA106M [GeForce RTX 3060 Mobile / Max-Q] [1d05:1116] InstallationDate: Installed on 2023-08-31 (13 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType:
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Agreed, I think it's reasonable to track down why this seemed to break Kinetic entirely before releasing to the other stable series. I can see from the logs that adsys seems to be failing due to an internal LDAP error (NT_STATUS_INVALID_PARAMETER), so it might be worth looking into that a bit deeper. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage notifications about
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
I see riscv64 on Focal currently fails to build, but looking at the previous adsys versions there that seems to be the case for some time now. Looking at the build logs, it's unlikely to be related to this patch. I'm a little concerned about the report on Kinetic breaking login with this new version, as that seems like a severe regression. Would dropping this for Kinetic altogether be an option? If I'm reading the Releases page correctly, it's going to be EOL by the end of the month and future releases should already include this fix (Lunar has adsys-0.11, and Mantic has adsys-0.12). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
I've discussed this internally, and seems like the Desktop team is ok with us pushing this bug fix as an SRU before the new 0.12 release for adsys. Matthew, I did a minor modification to your changelog entry to add attribution for the upstream patches, but otherwise your debdiffs seem good. Sponsored for F/J/K, thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: In Progress Status in adsys source package in Jammy: In Progress Status in adsys source package in Kinetic: In Progress Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Hi Matthew, thank you for the debdiffs! Things look good overall, I'd just like to add attribution for the upstream patches (for Didier Roche). This is something one can easily add when uploading, so don't worry about supplying a new debdiff just for this change. We've discussed this offline, but I'm going to mention it here as well, so we can track it later: There's an upload for adsys 0.12 sitting in the Jammy queue, and we'd have to either trample over that or wait for it to release in order to get the fix for this bug. There's some discussion going on over at the ubuntu-release mailing lists about granting adsys an SRU exception [0]. I'm going to reach out to the ones in charge of LP bug 2020682 to see if we can release this bug fix first, as the SRU exception discussion might take some time, still. [0] https://lists.ubuntu.com/archives/ubuntu- release/2023-June/005650.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: In Progress Status in adsys source package in Jammy: In Progress Status in adsys source package in Kinetic: In Progress Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link:
[Desktop-packages] [Bug 2024618] [NEW] In some boots, screen display is totally black possible i915 issue
Public bug reported: Hi, In some boots my laptop's graphic card(Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx) only display a black screen, everything else seems to work, the system is able to produce sounds. Its possible to make the display go back to work after close and open the lid. After some tests and debug, it was seen that the screen wasn't entirely black the brightness seems to be setted to the minimum(almost impossible to see), and with a external monitor the brightness level was checked in `/sys/class/backlight/intel_backlight/actual_brightness` it was set to the default value, so the problem can't be the backlight. I believe is a i915 driver problem. it was tested the following kernel's params: i915.enable_dpcd_backlight=3 i915.enable_dpcd_backlight=1 i915.enable_dpcd_backlight=0 i915.invert_brightness=1 i915.invert_brightness=-1 i915.modeset=0 i915.modeset=1 i915.register_backlight=1 Still no results. Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 21 16:03:20 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] InstallationDate: Installed on 2023-06-21 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. RTL8723BU 802.11b/g/n WLAN Adapter Bus 001 Device 002: ID 0bda:5830 Realtek Semiconductor Corp. MTD camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Compaq 420 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic root=UUID=774e3ecb-1e91-4c0e-8036-66b475c7f433 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 09/27/2021 dmi.bios.release: 5.11 dmi.bios.version: V1.13.X dmi.board.asset.tag: Default string dmi.board.name: N14JP6-V2 dmi.board.vendor: Compaq dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Compaq dmi.chassis.version: Default string dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvn:bvrV1.13.X:bd09/27/2021:br5.11:efr1.0:svnCompaq:pn420:pvrDefaultstring:rvnCompaq:rnN14JP6-V2:rvr:cvnCompaq:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Presario dmi.product.name: 420 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Compaq version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session ** Description changed: - Hi, - In some boots my laptopt graphic card(Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx) only display a black screen, everything else seems to work, the system is able to produce sounds. Its possible to make the display go back to work after close and open the lid. After some tests and debug, it was seen that the screen wasn't entirely black the brightness seems to be setted to the minimum(almost impossible to see), and with a external monitor the brightness level was checked in `/sys/class/backlight/intel_backlight/actual_brightness` it was set to the default value, so the problem can't be the backlight. I believe is a i915 driver
[Desktop-packages] [Bug 2023675] Re: flip effect doesn't work on GStreamer 1.22
Hi, Steve! The package(gnome-video-effects 0.5.0-1ubuntu2) was installed and tested using the following steps: Opened Cheese, in the main screen the flip(horizontal-invertion) effect was applied correctly, checked other effects to confirm if the effect was indeed being applied correctly and yes it was. So with this tests on the package gnome-video-effects 0.5.0-1ubuntu2 its confirmed that the problem was solved. ** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-video-effects in Ubuntu. https://bugs.launchpad.net/bugs/2023675 Title: flip effect doesn't work on GStreamer 1.22 Status in GNOME Video Effects: Fix Released Status in gnome-video-effects package in Ubuntu: Fix Released Status in gnome-video-effects source package in Lunar: Fix Committed Status in gnome-video-effects package in Debian: Fix Released Bug description: Impact -- The Flip effect in the Cheese app doesn't work in Ubuntu 23.10. Test Case - 1. Install the updated gnome-video-effects packages 2. Open the Cheese app 3. Click the Effects button and verify that Flip is showing a reversed version of No Effect What Could Go Wrong --- This is a simple one-line patch. gnome-video-effects has only one reverse dependency in Ubuntu: cheese. Original Bug Report --- Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar gnome-video-effects: Installed: 0.5.0-1ubuntu1 Candidate: 0.5.0-1ubuntu1 Version table: *** 0.5.0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The file located in: /usr/share/gnome-video-effects/flip.effect is using the property "method" which is deprecated as you can see in GStreamer "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi- language=c" Deprecated version: PipelineDescription=videoflip method=horizontal- flip So the fix for this problem is to change the property to the new one, which is called video-direction, after this the effect will work correctly. Fix: PipelineDescription=videoflip video-direction=horiz The program that I used to test this effect was Cheese. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-video-effects/+bug/2023675/+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 2024377] Re: Adsys can't fetch GPOs
** Description changed:
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums, Reddit
or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all steps
on Integration Ubuntu Desktop whitepaper. Currently using SSSD backend,
I can log with Active Directory users however when adsys is installed I
can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get policies
for "ubuntu": can't download all gpos and assets: one or more error
while fetching GPOs and assets: can't download "ubuntuRoot": can't check
if ubuntuRoot needs refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
It happens when using "adsysctl update -m" or "adsysctl update
usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
"adsysctl update" too.
I've upgrade the machine to 22.10 and the error changed to:
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER').
-
After upgrade to 23.04 the error persist same as the above.
-
Full info 22.04 (- verbose):
-
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
- We will only use the defaults, env variables or flags.
- DEBUG Connecting as [[2504:109556]]
- DEBUG New request /service/UpdatePolicy
- DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
- DEBUG NormalizeTargetName for "ubuntu", type "computer"
- DEBUG Check if grpc request peer is authorized
- DEBUG Authorized as being administrator
- DEBUG GetPolicies for "ubuntu", type "computer"
- DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
- DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
- DEBUG Analyzing "assets"
- DEBUG Analyzing "ubuntuRoot"
- INFO No assets directory with GPT.INI file found on AD, skipping assets
download
+ We will only use the defaults, env variables or flags.
+ DEBUG Connecting as [[2504:109556]]
+ DEBUG New request /service/UpdatePolicy
+ DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
+ DEBUG NormalizeTargetName for "ubuntu", type "computer"
+ DEBUG Check if grpc request peer is authorized
+ DEBUG Authorized as being administrator
+ DEBUG GetPolicies for "ubuntu", type "computer"
+ DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
+ DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
+ DEBUG Analyzing "assets"
+ DEBUG Analyzing "ubuntuRoot"
+ INFO No assets directory with GPT.INI file found on AD, skipping assets
download
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": can't download all gpos and assets: one or more error while fetching
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs
refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
-
Full info 23.04 (- verbose):
- INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
- DEBUG Connecting as [[58811:006019]]
- DEBUG New request /service/UpdatePolicy
- DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
- DEBUG NormalizeTargetName for "ubuntu", type "computer"
- DEBUG Check if grpc request peer is authorized
- DEBUG Authorized as being administrator
- DEBUG GetPolicies for "ubuntu", type "computer"
- DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
+ INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
+ DEBUG Connecting as [[58811:006019]]
+ DEBUG New request /service/UpdatePolicy
+ DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
+ DEBUG NormalizeTargetName for "ubuntu", type "computer"
+ DEBUG Check if grpc request peer is authorized
+ DEBUG Authorized as
[Desktop-packages] [Bug 2024377] [NEW] Adsys can't fetch GPOs
Public bug reported:
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums, Reddit
or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all steps
on Integration Ubuntu Desktop whitepaper. Currently using SSSD backend,
I can log with Active Directory users however when adsys is installed I
can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get policies
for "ubuntu": can't download all gpos and assets: one or more error
while fetching GPOs and assets: can't download "ubuntuRoot": can't check
if ubuntuRoot needs refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
It happens when using "adsysctl update -m" or "adsysctl update
usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
"adsysctl update" too.
I've upgrade the machine to 22.10 and the error changed to:
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER').
After upgrade to 23.04 the error persist same as the above.
Full info 22.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
We will only use the defaults, env variables or flags.
DEBUG Connecting as [[2504:109556]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target: ubuntu,
Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
DEBUG Analyzing "assets"
DEBUG Analyzing "ubuntuRoot"
INFO No assets directory with GPT.INI file found on AD, skipping assets
download
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": can't download all gpos and assets: one or more error while fetching
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs
refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
Full info 23.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
DEBUG Connecting as [[58811:006019]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target: ubuntu,
Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.deltasul.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER')
Additional info:
Domain Controller and machine are on the same subnet without firewall on any
level;
Domain Controller is a Windows Server 2019 updated to the last security version;
Both machine and user are on the same OU with "no heritage" enabled and just
one policy added to permit usern...@domain.com.br to become root;
The info header directory is "/home/jzprates" on both logs because I've
collected them using the local account using "sudo adsysctl update -m -";
If I disable Adsys login on pam-auth-update, Ubuntu creates a homedir and enter
correctly with domain users.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: adsys 0.11.0
ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
Uname: Linux 6.2.0-23-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 19 11:22:10 2023
InstallationDate:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Hi Lucas, Thank you for taking a look at this! I was originally sponsoring this one for Matthew, but given it's now targeting a development release, I can't sponsor that one (as I'm currently an SRU developer). If a coredev could do the sponsoring for devel, I'd be happy to work with Matthew on the other series if necessary. -- 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/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from
[Desktop-packages] [Bug 2023675] Re: flip effect doesn't work on GStreamer 1.22
** Changed in: gnome-video-effects (Ubuntu) Assignee: (unassigned) => Phelipe Matheus Couto de Aguiar (matheus-aguiar-dev) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-video-effects in Ubuntu. https://bugs.launchpad.net/bugs/2023675 Title: flip effect doesn't work on GStreamer 1.22 Status in gnome-video-effects package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar gnome-video-effects: Installed: 0.5.0-1ubuntu1 Candidate: 0.5.0-1ubuntu1 Version table: *** 0.5.0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The file located in: /usr/share/gnome-video-effects/flip.effect is using the property "method" which is deprecated as you can see in GStreamer "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi-language=c; Deprecated version: PipelineDescription=videoflip method=horizontal- flip So the fix for this problem is to change the property to the new one, which is called video-direction, after this the effect will work correctly. Fix: PipelineDescription=videoflip video-direction=horiz The program that I used to test this effect was Cheese. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-video-effects/+bug/2023675/+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 2023677] Re: Flip effect isnt working because of gnome-video-effects
I made a bug report related to this problem in the project of gnome- video-effects, where you can find the fix https://bugs.launchpad.net/ubuntu/+source/gnome-video- effects/+bug/2023675 in the diff file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/2023677 Title: Flip effect isnt working because of gnome-video-effects Status in cheese package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar cheese: Installed: 44.0-1 Candidate: 44.0-1 Version table: *** 44.0-1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The main effect used in the camera should be the flip-effect, but the effect isn't working due to the property "method" being deprecated as you can see in "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi- language=c" The file located in /usr/share/gnome-video-effects/flip-effect is using the command: PipelineDescription=videoflip method=horizontal- flip So the fix to this problem is to change the deprecated property to the new one, which is called "video-direction", the line should be: PipelineDescription=videoflip video-direction=horiz after this changes the flip effect will work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/2023677/+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 2023675] Re: flip effect doesn't work on GStreamer 1.22
here is the bug fix, that was informed in the LP ** Patch added: "gnome-video-effects_0.5.0-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-video-effects/+bug/2023675/+attachment/5679541/+files/gnome-video-effects_0.5.0-1ubuntu2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-video-effects in Ubuntu. https://bugs.launchpad.net/bugs/2023675 Title: flip effect doesn't work on GStreamer 1.22 Status in gnome-video-effects package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar gnome-video-effects: Installed: 0.5.0-1ubuntu1 Candidate: 0.5.0-1ubuntu1 Version table: *** 0.5.0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The file located in: /usr/share/gnome-video-effects/flip.effect is using the property "method" which is deprecated as you can see in GStreamer "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi-language=c; Deprecated version: PipelineDescription=videoflip method=horizontal- flip So the fix for this problem is to change the property to the new one, which is called video-direction, after this the effect will work correctly. Fix: PipelineDescription=videoflip video-direction=horiz The program that I used to test this effect was Cheese. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-video-effects/+bug/2023675/+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 2023677] [NEW] Flip effect isnt working because of gnome-video-effects
Public bug reported: Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar cheese: Installed: 44.0-1 Candidate: 44.0-1 Version table: *** 44.0-1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The main effect used in the camera should be the flip-effect, but the effect isn't working due to the property "method" being deprecated as you can see in "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi- language=c" The file located in /usr/share/gnome-video-effects/flip-effect is using the command: PipelineDescription=videoflip method=horizontal-flip So the fix to this problem is to change the deprecated property to the new one, which is called "video-direction", the line should be: PipelineDescription=videoflip video-direction=horiz after this changes the flip effect will work correctly ** Affects: cheese (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/2023677 Title: Flip effect isnt working because of gnome-video-effects Status in cheese package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar cheese: Installed: 44.0-1 Candidate: 44.0-1 Version table: *** 44.0-1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The main effect used in the camera should be the flip-effect, but the effect isn't working due to the property "method" being deprecated as you can see in "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi- language=c" The file located in /usr/share/gnome-video-effects/flip-effect is using the command: PipelineDescription=videoflip method=horizontal- flip So the fix to this problem is to change the deprecated property to the new one, which is called "video-direction", the line should be: PipelineDescription=videoflip video-direction=horiz after this changes the flip effect will work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/2023677/+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 2023675] [NEW] flip effect doesn't work on GStreamer 1.22
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 23.04 Release:23.04 Codename: lunar gnome-video-effects: Installed: 0.5.0-1ubuntu1 Candidate: 0.5.0-1ubuntu1 Version table: *** 0.5.0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The file located in: /usr/share/gnome-video-effects/flip.effect is using the property "method" which is deprecated as you can see in GStreamer "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi-language=c; Deprecated version: PipelineDescription=videoflip method=horizontal-flip So the fix for this problem is to change the property to the new one, which is called video-direction, after this the effect will work correctly. Fix: PipelineDescription=videoflip video-direction=horiz The program that I used to test this effect was Cheese. ** Affects: gnome-video-effects (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-video-effects in Ubuntu. https://bugs.launchpad.net/bugs/2023675 Title: flip effect doesn't work on GStreamer 1.22 Status in gnome-video-effects package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar gnome-video-effects: Installed: 0.5.0-1ubuntu1 Candidate: 0.5.0-1ubuntu1 Version table: *** 0.5.0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The file located in: /usr/share/gnome-video-effects/flip.effect is using the property "method" which is deprecated as you can see in GStreamer "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi-language=c; Deprecated version: PipelineDescription=videoflip method=horizontal- flip So the fix for this problem is to change the property to the new one, which is called video-direction, after this the effect will work correctly. Fix: PipelineDescription=videoflip video-direction=horiz The program that I used to test this effect was Cheese. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-video-effects/+bug/2023675/+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 2023008] Re: cannot install libegl-mesa0 on 22.04.2 LTS
This bug affects me too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2023008 Title: cannot install libegl-mesa0 on 22.04.2 LTS Status in mesa package in Ubuntu: New Bug description: # Summary `apt install libegl-mesa0` does not install it due to a dependency conflict in the apt repo. libegl-mesa0 has dependency to explicit versions of: * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2. # Expected behavior These closely linked packages to be up-to-date in the Ubuntu repo. # Workaround It is possible to install libegl-mesa0 by first downgrading the conflicting package versions: apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1 apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1 and then installing it normally: apt install libegl-mesa0 # Details ``` # apt install libegl-mesa0 Reading package lists... Done Building dependency tree... Done Reading state information... 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: libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed E: Unable to correct problems, you have held broken packages.` ``` 1) Is the hard dependency (=) really necessary? 2) Or should I just downgrade existing libglapi-mesa and libgbm1 installs? The difference is minor patch version only so I am hesitant to do so (there must have been a reasons for the .2 patch). # Environment ## cat /etc/lsb-release ``` cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" ``` # apt-cache policy ``` apt-cache policy libegl-mesa0 libegl-mesa0: Installed: (none) Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: 22.2.5-0ubuntu0.1~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 22.0.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2023008/+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 2020641] Re: Installing or removing apps through snap-store launches another gdm session
Marking Kinetic as Won't Fix (release close to EOL, as mentioned in an email thread). ** Also affects: gdm3 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session Status in gdm3 package in Ubuntu: Fix Committed Status in gdm3 source package in Jammy: Fix Committed Status in gdm3 source package in Kinetic: Won't Fix Status in gdm3 source package in Lunar: Fix Committed Status in gdm3 source package in Mantic: Fix Committed Bug description: gdm3 version: 42.0-1ubuntu7.22.04.2 Ubuntu version: Ubuntu 22.04.2 LTS [Description] Installing or removing snap packages through NICE DCV on AWS will cause the user to be kicked out of their session. The issue happens on machines running nvidia GPUs (passed through to a VM) with the GRID driver installed as well as the normal nvidia driver. [Steps to reproduce] Simply install or remove any snap through the snap store will trigger the issue, for example: $ snap install skype also running any of the following commands will also trigger the issue: $ snap connect skype:opengl :opengl $ snap disconnect skype:opengl :opengl $ snap connect skype:camera :camera $ snap disconnect skype:camera :camera After further investigation I was able to pin down the issue to udev and could reproduce the issue by running the following command: $ sudo udevadm trigger --parent-match=/sys/devices/pci:00/:00:1e.0/drm/card0 where "/sys/devices/pci:00/:00:1e.0/drm/card0" corresponds to the nvidia GPU of my instance. A more generic way of triggering the issue would be running: $ sudo udevadm trigger [Solution] I have investigated the issue and discovered that it lies within GDM3 in the "udev_is_settled" function (daemon/gdm-local-display-factory.c). In the case where the udev is settled the line "g_clear_signal_handler (>uevent_handler_id, factory->gudev_client);" at the end of the function is triggered however this is not the case when the function returns early and will lead to the user being logged out. In its current implementation there are three different return points before "g_clear_signal_handler" is executed where the udev devices would already have settled. I have written a patch that fixes this issue by making sure the function "g_clear_signal_handler" is executed in all cases for which the udev is settled. [possible regressions] Excessive clearing of the signal handler might cause a case where it is not being re-initialized the next time it is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+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 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
** Tags removed: sts-sponsor ** Tags added: se-sponsor-halves -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: In Progress Status in adsys source package in Jammy: In Progress Status in adsys source package in Kinetic: In Progress Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.11.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.11.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.11.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.11.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 2021438] [NEW] Display
Public bug reported: When the system turns off the screen by power management, the screen does not come back active again, having to activate the brightness keys for it to come back. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 21:14:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:3a2d] NVIDIA Corporation GP107M [GeForce GTX 1050 3 GB Max-Q] [10de:1c91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP107M [GeForce GTX 1050 3 GB Max-Q] [17aa:3a2d] InstallationDate: Installed on 2023-05-28 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 81TR ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=efac633a-69bd-49a0-b3ca-ba7e617e416a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO IDEAPAD L340-15IRH dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrBGCN34WW:bd05/21/2021:br1.34:efr1.34:svnLENOVO:pn81TR:pvrLENOVOIDEAPADL340-15IRH:rvnLENOVO:rnINVALID:rvrNoDPK:cvnLENOVO:ct10:cvrLENOVOIDEAPADL340-15IRH:skuLENOVO_MT_81TR_BU_idea_FM_IDEAPAD: dmi.product.family: IDEAPAD dmi.product.name: 81TR dmi.product.sku: LENOVO_MT_81TR_BU_idea_FM_IDEAPAD dmi.product.version: LENOVO IDEAPAD L340-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu -- 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/2021438 Title: Display Status in xorg package in Ubuntu: New Bug description: When the system turns off the screen by power management, the screen does not come back active again, having to activate the brightness keys for it to come back. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 21:14:21 2023 DistUpgraded: Fresh install DistroCodename: lunar
[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** Tags added: se-sponsor-dgadomski -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: In Progress Status in gjs source package in Kinetic: Triaged Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() 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/gjs/+bug/1974293/+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 2020362] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2020362/+attachment/5674702/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+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 2020362] Re: Gnome notifies keyboard battery is low but actually mouse battery is low
** Attachment added: "Captura de tela de 2023-05-22 09-18-07.png" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+attachment/5674699/+files/Captura%20de%20tela%20de%202023-05-22%2009-18-07.png ** Tags added: apport-collected lunar wayland-session ** Description changed: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2022-01-12 (494 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + Package: gnome-settings-daemon 44.0-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 + Tags: lunar wayland-session + Uname: Linux 6.2.0-20-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+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 2020362] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2020362/+attachment/5674700/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+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 2020362] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2020362/+attachment/5674701/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+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 2020362] [NEW] Gnome notifies keyboard battery is low but actually mouse battery is low
Public bug reported: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+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 2018731] Re: Graphics memory (VRAM) leak in mutter-x11-frames
I have 3GB of GPU RAM usage by mutter-x11-frames (and my gpu only has 8GB total) nvidia-smi: ``` /usr/libexec/mutter-x11-frames 3348MiB ``` Ubuntu 23.04 Kernel 6.2.0-20-generic Nvidia 530.41.03 GTX 3070 Ti Desktop with one 4K screen, 200% scaling. -- 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/2018731 Title: Graphics memory (VRAM) leak in mutter-x11-frames Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I'm seeing degraded performance with NVIDIA Geforce 3008 Mobile and two screens. After launching nvidia-smi, I can clearly see that there's a memory leak in mutter-x11-frames, which uses around 10-12 GB of VRAM. nvidia-drivers-525 Ubuntu 23.04 X11 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 8 14:28:13 2023 DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] InstallationDate: Installed on 2023-02-09 (87 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-20 (18 days ago) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 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/mutter/+bug/2018731/+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 2018535] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/2018535/+attachment/5671722/+files/ShellJournal.txt -- 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/2018535 Title: Dialog boxes are displayed on background (hidden) on second monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Dialog boxes of applications opened on the second screen (side by side mode) are displayed hidden behind the main application window. The same problem does not happen if the application is open on the first screen. When trying to take a screenshot to send here the image is updated and the dialog is displayed over the main application window. How to reproduce it: Open gnome text editor and when open preferences dialog. If you do it on the first screen you can see the dialog box but do it on the second screen you cannot see the dialog box. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (481 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (10 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018535/+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 2018535] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/2018535/+attachment/5671723/+files/monitors.xml.txt -- 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/2018535 Title: Dialog boxes are displayed on background (hidden) on second monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Dialog boxes of applications opened on the second screen (side by side mode) are displayed hidden behind the main application window. The same problem does not happen if the application is open on the first screen. When trying to take a screenshot to send here the image is updated and the dialog is displayed over the main application window. How to reproduce it: Open gnome text editor and when open preferences dialog. If you do it on the first screen you can see the dialog box but do it on the second screen you cannot see the dialog box. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (481 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (10 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018535/+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 2018535] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2018535/+attachment/5671721/+files/ProcEnviron.txt -- 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/2018535 Title: Dialog boxes are displayed on background (hidden) on second monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Dialog boxes of applications opened on the second screen (side by side mode) are displayed hidden behind the main application window. The same problem does not happen if the application is open on the first screen. When trying to take a screenshot to send here the image is updated and the dialog is displayed over the main application window. How to reproduce it: Open gnome text editor and when open preferences dialog. If you do it on the first screen you can see the dialog box but do it on the second screen you cannot see the dialog box. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (481 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (10 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018535/+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 2018535] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2018535/+attachment/5671720/+files/ProcCpuinfoMinimal.txt -- 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/2018535 Title: Dialog boxes are displayed on background (hidden) on second monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Dialog boxes of applications opened on the second screen (side by side mode) are displayed hidden behind the main application window. The same problem does not happen if the application is open on the first screen. When trying to take a screenshot to send here the image is updated and the dialog is displayed over the main application window. How to reproduce it: Open gnome text editor and when open preferences dialog. If you do it on the first screen you can see the dialog box but do it on the second screen you cannot see the dialog box. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (481 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (10 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018535/+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 2018535] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2018535/+attachment/5671719/+files/GsettingsChanges.txt -- 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/2018535 Title: Dialog boxes are displayed on background (hidden) on second monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Dialog boxes of applications opened on the second screen (side by side mode) are displayed hidden behind the main application window. The same problem does not happen if the application is open on the first screen. When trying to take a screenshot to send here the image is updated and the dialog is displayed over the main application window. How to reproduce it: Open gnome text editor and when open preferences dialog. If you do it on the first screen you can see the dialog box but do it on the second screen you cannot see the dialog box. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (481 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (10 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018535/+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 2018535] Re: Dialog boxes are displayed on background (hidden) on second monitor
apport information ** Tags added: apport-collected wayland-session ** Description changed: Dialog boxes of applications opened on the second screen (side by side mode) are displayed hidden behind the main application window. The same problem does not happen if the application is open on the first screen. When trying to take a screenshot to send here the image is updated and the dialog is displayed over the main application window. How to reproduce it: Open gnome text editor and when open preferences dialog. If you do it on the first screen you can see the dialog box but do it on the second screen you cannot see the dialog box. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2022-01-12 (481 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 44.0-2ubuntu3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 + RelatedPackageVersions: mutter-common 44.0-2ubuntu4 + Tags: lunar wayland-session + Uname: Linux 6.2.0-20-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-04-27 (10 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2018535/+attachment/5671718/+files/Dependencies.txt -- 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/2018535 Title: Dialog boxes are displayed on background (hidden) on second monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Dialog boxes of applications opened on the second screen (side by side mode) are displayed hidden behind the main application window. The same problem does not happen if the application is open on the first screen. When trying to take a screenshot to send here the image is updated and the dialog is displayed over the main application window. How to reproduce it: Open gnome text editor and when open preferences dialog. If you do it on the first screen you can see the dialog box but do it on the second screen you cannot see the dialog box. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (481 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (10 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018535/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Hi folks, thank you for the hard work on this bug! I've tested out the debdiff for Jammy, and unfortunately it seems we're still missing some pieces. A fresh install with the fixed version looks ok, but when upgrading from the previous version, I can still see the old link under default.target.wants/: root@halves-jammy-tm:~# dpkg -l | grep tracker-ext ii tracker-extract3.3.0-1ubuntu1 amd64metadata database, indexer and search tool - metadata extractors root@halves-jammy-tm:~# ls -l /etc/systemd/user/default.target.wants/ total 0 lrwxrwxrwx 1 root root 47 May 1 14:32 tracker-extract-3.service -> /usr/lib/systemd/user/tracker-extract-3.service We should include a proper cleanup step for the upgrade path for all debdiffs, as the other releases will probably present the same issue. -- 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/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Confirmed Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Confirmed Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Confirmed Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Confirmed Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Confirmed Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
** Tags removed: sts-sponsor ** Tags added: se-sponsor-halves -- 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/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Confirmed Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Confirmed Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Confirmed Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Confirmed Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Confirmed Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 Focal requires four additional patches to solve the issue, namely: commit 8065985c8d818414a36fe151862afdf42c5eda8a Author:
[Desktop-packages] [Bug 2015660] Re: Unable to set Super+P as custom shortcut
lucio@biscoito:~$ gsettings get org.gnome.mutter.keybindings switch-monitor ['p', 'XF86Display'] Add 'Super+P' as a custom shortcut maybe should disable and warn about Mutter switch-monitor keybind. -- 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/2015660 Title: Unable to set Super+P as custom shortcut Status in gnome-control-center package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu lucio@biscoito:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-control-center: Installed: 1:44.0-1ubuntu4 Candidate: 1:44.0-1ubuntu4 Version table: *** 1:44.0-1ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I'm trying to run "playerctl play-pause" using the custom gnome shortcut 'Super+P'. 4) What happened instead 1. Nothing happens. 2. If using another shortcut like 'Super+W' it works, but not Super+P. 3. playerctl play-pause works on cli. lucio@biscoito:~$ dconf dump / | grep Super close=['q'] lower=['j'] maximize=['f'] move-to-workspace-1=['1'] move-to-workspace-2=['2'] move-to-workspace-3=['3'] move-to-workspace-4=['4'] raise=['k'] switch-to-workspace-1=['1'] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] toggle-tiled-left=['h'] toggle-tiled-right=['l'] email=['m'] mic-mute=['BackSpace'] screensaver=['x'] terminal=['Return'] volume-down=['minus'] volume-mute=['BackSpace'] volume-up=['equal'] www=['b'] binding='p' << the infamous one. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 8 20:18:56 2023 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/2015660/+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 2015660] [NEW] Unable to set Super+P as custom shortcut
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu lucio@biscoito:~$ lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-control-center: Installed: 1:44.0-1ubuntu4 Candidate: 1:44.0-1ubuntu4 Version table: *** 1:44.0-1ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I'm trying to run "playerctl play-pause" using the custom gnome shortcut 'Super+P'. 4) What happened instead 1. Nothing happens. 2. If using another shortcut like 'Super+W' it works, but not Super+P. 3. playerctl play-pause works on cli. lucio@biscoito:~$ dconf dump / | grep Super close=['q'] lower=['j'] maximize=['f'] move-to-workspace-1=['1'] move-to-workspace-2=['2'] move-to-workspace-3=['3'] move-to-workspace-4=['4'] raise=['k'] switch-to-workspace-1=['1'] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] toggle-tiled-left=['h'] toggle-tiled-right=['l'] email=['m'] mic-mute=['BackSpace'] screensaver=['x'] terminal=['Return'] volume-down=['minus'] volume-mute=['BackSpace'] volume-up=['equal'] www=['b'] binding='p' << the infamous one. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 8 20:18:56 2023 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 lunar wayland-session ** Attachment added: "My conf" https://bugs.launchpad.net/bugs/2015660/+attachment/5662293/+files/Screenshot%20from%202023-04-08%2020-18-14.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/2015660 Title: Unable to set Super+P as custom shortcut Status in gnome-control-center package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu lucio@biscoito:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-control-center: Installed: 1:44.0-1ubuntu4 Candidate: 1:44.0-1ubuntu4 Version table: *** 1:44.0-1ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I'm trying to run "playerctl play-pause" using the custom gnome shortcut 'Super+P'. 4) What happened instead 1. Nothing happens. 2. If using another shortcut like 'Super+W' it works, but not Super+P. 3. playerctl play-pause works on cli. lucio@biscoito:~$ dconf dump / | grep Super close=['q'] lower=['j'] maximize=['f'] move-to-workspace-1=['1'] move-to-workspace-2=['2'] move-to-workspace-3=['3'] move-to-workspace-4=['4'] raise=['k'] switch-to-workspace-1=['1'] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] toggle-tiled-left=['h'] toggle-tiled-right=['l'] email=['m'] mic-mute=['BackSpace'] screensaver=['x'] terminal=['Return'] volume-down=['minus'] volume-mute=['BackSpace'] volume-up=['equal'] www=['b'] binding='p' << the infamous one. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 8 20:18:56 2023 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/2015660/+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 2015347] Re: Regression: GTK statusbars look very weird on 200% scaling
With latest apt-get update it is now solved. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015347 Title: Regression: GTK statusbars look very weird on 200% scaling Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: I don't know where I need to report this bug, but it's quite a serious one. On both livecd and installed version of Ubuntu 23.04 the statusbars of some applications (for example libreoffice, Visual Studio Code, the keychain dialog when logging in and more) are really small and weird looking when using Gnome with 200% scaling. https://pasteboard.co/S0idNZig1HEV.png It looks like the legacy compatibility mode of GTK for these apps doesn't take into account scaling. This worked properly on 22.10 and earlier. System: Ubuntu 23.04 beta NVIDIA RTX 3070Ti (nvidia drivers on install, nouveau I guess on livecd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2015347/+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 2015347] [NEW] Regression: GTK statusbars look very weird on 200% scaling
Public bug reported: I don't know where I need to report this bug, but it's quite a serious one. On both livecd and installed version of Ubuntu 23.04 the statusbars of some applications (for example libreoffice, Visual Studio Code, the keychain dialog when logging in and more) are really small and weird looking when using Gnome with 200% scaling. https://pasteboard.co/S0idNZig1HEV.png It looks like the legacy compatibility mode of GTK for these apps doesn't take into account scaling. This worked properly on 22.10 and earlier. System: Ubuntu 23.04 beta NVIDIA RTX 3070Ti (nvidia drivers on install, nouveau I guess on livecd) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Schermafdruk van 2023-04-02 17-20-37.png" https://bugs.launchpad.net/bugs/2015347/+attachment/5661187/+files/Schermafdruk%20van%202023-04-02%2017-20-37.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015347 Title: Regression: GTK statusbars look very weird on 200% scaling Status in gtk+3.0 package in Ubuntu: New Bug description: I don't know where I need to report this bug, but it's quite a serious one. On both livecd and installed version of Ubuntu 23.04 the statusbars of some applications (for example libreoffice, Visual Studio Code, the keychain dialog when logging in and more) are really small and weird looking when using Gnome with 200% scaling. https://pasteboard.co/S0idNZig1HEV.png It looks like the legacy compatibility mode of GTK for these apps doesn't take into account scaling. This worked properly on 22.10 and earlier. System: Ubuntu 23.04 beta NVIDIA RTX 3070Ti (nvidia drivers on install, nouveau I guess on livecd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2015347/+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 2012506] [NEW] No-change rebuilds needed for foo2zjs in lunar
Public bug reported: The last security update made to the jbigkit package introduced an ABI change. Package foo2zjs depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild foo2zjs in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. ** Affects: foo2zjs (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No-change rebuilds needed for foo2zjs and splix in lunar + No-change rebuilds needed for foo2zjs in lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/2012506 Title: No-change rebuilds needed for foo2zjs in lunar Status in foo2zjs package in Ubuntu: New Bug description: The last security update made to the jbigkit package introduced an ABI change. Package foo2zjs depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild foo2zjs in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/2012506/+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 2012507] [NEW] No-change rebuilds needed for splix in lunar
Public bug reported: The last security update made to the jbigkit package introduced an ABI change. Package splix depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild splix in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. ** Affects: splix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/2012507 Title: No-change rebuilds needed for splix in lunar Status in splix package in Ubuntu: New Bug description: The last security update made to the jbigkit package introduced an ABI change. Package splix depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild splix in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/2012507/+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 2008920] [NEW] Brltty does not permit Arduino devices to run on ubuntu
Public bug reported: Every time I start a new ubuntu installation from zero I get some errors on Arduino devices that does not recognize with the following error: [ 561.144042] usb 1-2: new full-speed USB device number 15 using xhci_hcd [ 561.293021] usb 1-2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54 [ 561.293028] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 561.293031] usb 1-2: Product: USB2.0-Ser! [ 561.294936] ch341 1-2:1.0: ch341-uart converter detected [ 561.295634] ch341-uart ttyUSB0: break control not supported, using simulated break [ 561.295695] usb 1-2: ch341-uart converter now attached to ttyUSB0 [ 561.845448] input: BRLTTY 6.5 Linux Screen Driver Keyboard as /devices/virtual/input/input28 [ 561.961485] usb 1-2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [ 561.961910] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [ 561.961937] ch341 1-2:1.0: device disconnected So I have to remove brltty manually (apt remove brltty), that just no problem. But I think this modulo shouldn't disable others serial devices by default. In summary its sad that, for default, ubuntu does not work with arduino. For me this is a bug, or brltty should be default if it can't live with others devices. ** Affects: brltty (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/2008920 Title: Brltty does not permit Arduino devices to run on ubuntu Status in brltty package in Ubuntu: New Bug description: Every time I start a new ubuntu installation from zero I get some errors on Arduino devices that does not recognize with the following error: [ 561.144042] usb 1-2: new full-speed USB device number 15 using xhci_hcd [ 561.293021] usb 1-2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54 [ 561.293028] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 561.293031] usb 1-2: Product: USB2.0-Ser! [ 561.294936] ch341 1-2:1.0: ch341-uart converter detected [ 561.295634] ch341-uart ttyUSB0: break control not supported, using simulated break [ 561.295695] usb 1-2: ch341-uart converter now attached to ttyUSB0 [ 561.845448] input: BRLTTY 6.5 Linux Screen Driver Keyboard as /devices/virtual/input/input28 [ 561.961485] usb 1-2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [ 561.961910] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [ 561.961937] ch341 1-2:1.0: device disconnected So I have to remove brltty manually (apt remove brltty), that just no problem. But I think this modulo shouldn't disable others serial devices by default. In summary its sad that, for default, ubuntu does not work with arduino. For me this is a bug, or brltty should be default if it can't live with others devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2008920/+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 2002510] Re: bbswitch-dkms fails to build with jammy/linux-hwe-5.19
Confirmed that bbswitch-dkms (0.8-10ubuntu2.1) can be installed and built on a jammy system running the hwe-5.19 kernel: === Setting up bbswitch-dkms (0.8-10ubuntu2.1) ... Loading new bbswitch-0.8 DKMS files... Building for 5.19.0-32-generic Building initial module for 5.19.0-32-generic Done. bbswitch.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.19.0-32-generic/updates/dkms/ === I couldn't test loading the module due to lack of hardware. ADT tests were also successful with the GA 5.15 kernel: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/b/bbswitch/20230127_140815_7abe1@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/b/bbswitch/20230127_140058_98ecd@/log.gz ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2002510 Title: bbswitch-dkms fails to build with jammy/linux-hwe-5.19 Status in bbswitch package in Ubuntu: Fix Released Status in bbswitch source package in Jammy: Fix Committed Bug description: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] To fix it we can take two approches: a) we import the Lunar version (0.8-14) into Jammy, and it's missing dependency (dh-dkms) or b) we apply the attached debdiff that is syncing the Jammy version up to Lunar, reverting on top the bits depending on dh-dkms. Whichever is the path of last resistance, i'm happy with it. [Regression potential] It's the same DKMS we are already using in Lunar, and it contains all the fixes upstream developed so far: Jammy and Lunar share the same base version (0.8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+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 1996900] [NEW] display flashes
Public bug reported: During normal usage the display sometimes flashes black. In particular some websites cause intense flickering with several black frames per second. This actually seems to happen in both Wayland and xorg sessions and flashes the entire screen, so it seems more like a driver bug but I'm not sure where to file that. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 17 14:00:15 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] InstallationDate: Installed on 2022-10-30 (18 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2022 dmi.bios.release: 6.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0603:bd09/08/2022:br6.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption kinetic kubuntu ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1996900 Title: display flashes Status in xorg package in Ubuntu: New Bug description: During normal usage the display sometimes flashes black. In particular some websites cause intense flickering with several black frames per second. This actually seems to happen in both Wayland and xorg sessions and flashes the entire screen, so it seems more like a driver bug but I'm not sure where to file that. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 17 14:00:15 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] InstallationDate: Installed on 2022-10-30 (18 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install)
[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)
Are you using Compton? If so, please see https://askubuntu.com/a/1439993/682596 and https://gitlab.xfce.org/xfce/xfwm4/-/issues/676 Basically, Compton could be at fault for creating these key delays. As soon as I start Compton manually in a similar fashion as the OS startup, the problem appears. I am not using double keyboards. ** Bug watch added: gitlab.xfce.org/xfce/xfwm4/-/issues #676 https://gitlab.xfce.org/xfce/xfwm4/-/issues/676 -- 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/108 Title: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg) Status in GNOME Shell: Fix Released Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1993920] [NEW] Some windows overflow to other monitors whenever they're near to border and wider than main screen
Public bug reported: After upgrading to Ubuntu 22.10, some applications (for example, VSCode and MySQL Workbench) are presenting weird behavior: if I move it to the secondary monitor and maximize the window, it gets mirrored in the main monitor. I've made some tests and realized that this issue occurs if I place the application window near to the divisor between the two monitors and this window's width is greater than the main monitor's one. Here is a link to a video that shows this issue: https://youtu.be/FmYSgpwS6Bk ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 18:19:27 2022 DistUpgraded: 2022-10-20 20:40:37,319 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Comet Lake UHD Graphics [144d:c834] InstallationDate: Installed on 2022-10-15 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=46adeab8-b7f5-472d-b479-38b045a695ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago) dmi.bios.date: 02/23/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P12RFH.054.220223.HC dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550XCJ-KF1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA664A0C-C01-G002-S0001+10.0.19041 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP12RFH.054.220223.HC:bd02/23/2022:br5.16:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XCJ/550XCR:pvrP12RFH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XCJ-KF1BR:rvrSGLA664A0C-C01-G002-S0001+10.0.19041:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRFH: dmi.product.family: Notebook 5 Series dmi.product.name: 550XCJ/550XCR dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRFH dmi.product.version: P12RFH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1993920 Title: Some windows overflow to other monitors whenever they're near to border and wider than main screen Status in xorg package in Ubuntu: New Bug description: After upgrading to Ubuntu 22.10, some applications (for example, VSCode and MySQL Workbench) are presenting weird behavior: if I move it to the secondary monitor and maximize the window, it gets mirrored in the main monitor. I've made some tests and realized that this issue occurs if I place the application window near to the divisor between the two monitors and this window's width is greater than the main monitor's one. Here is a link to a video that shows this issue: https://youtu.be/FmYSgpwS6Bk ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 18:19:27 2022 DistUpgraded: 2022-10-20 20:40:37,319 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-21-generic, x86_64: installed
[Desktop-packages] [Bug 1992854] [NEW] Update wpebackend-fdo to 1.6.1
Public bug reported:
Impact
--
This is a minor bugfix release of the 1.6.x series:
https://wpewebkit.org/release/wpebackend-fdo-1.6.1.html
The version currently in 20.04 LTS is 1.6.0, which accidentally shipped with
a bug that made the symbols wpe_fdo_get_{major,minor,micro}_version hidden.
These were supposed to be public (which is fixed in 1.6.1) and can be used
by other components to check the installed version at runtime.
In particular WebKitGTK depends on wpebackend-fdo, and we expect future
security updates may use these functions. The WebKitGTK team has committed
to making it possible for 20.04 to get updates until April 2023, and this
update makes those possible. Users of WebKit-based browsers should be able
to browse the Web with an up-to-date WebKitGTK stack that receives security
updates :)
Test Plan
-
The following C program can be used to check that the bug is present before
the wpebackend-fdo update, and that the issue was fixed afterwards:
/*
* $CC -o wpefdoversion wpefdoversion.c $(pkg-config --cflags --libs
wpebackend-fdo-1.0)
*
* This will:
* - Fail to link with wpebackend-fdo 1.6.0
* - Succeed with version 1.6.1
*/
#include
#include
int main(int argc, char *argv[]) {
printf("wpebackend-fdo runtime version: %d.%d.%d\n",
wpe_fdo_get_major_version(), wpe_fdo_get_minor_version(),
wpe_fdo_get_micro_version());
return 0;
}
Browsers which use WebKitGTK for rendering web content running in a Wayland
session
use wpebackend-fdo. Loading e.g.
https://people.igalia.com/aperez/poster-circle.html
in Epiphany (package epiphany-browser) should work the same before and after
the update.
What Could Go Wrong
---
Given the little amount of changes between versions 1.6.0 and 1.6.1, the
possibility
of breakage is minimal to none. Diff:
https://github.com/Igalia/WPEBackend-fdo/compare/1.6.0...1.6.1
If there were unexpected build failures for the package, an alternative would
be to
continue shipping version 1.6.0 with commit
1dda80de5372e56cdc6f818a3fca493f7cc1f9d6
applied, which would solve the issue with the
wpe_fdo_get_{major,minor,micro}_version
symbols without including the rest of the changes from 1.6.1:
https://github.com/Igalia/WPEBackend-
fdo/commit/1dda80de5372e56cdc6f818a3fca493f7cc1f9d6
Finally, given that default installs of Ubuntu desktop do not include a
WebKitGTK
based browser, users are likely to have another web browser available if things
were
to go wrong.
** Affects: wpebackend-fdo (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Test program C source"
https://bugs.launchpad.net/bugs/1992854/+attachment/5623985/+files/wpefdoversion.c
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpebackend-fdo in Ubuntu.
https://bugs.launchpad.net/bugs/1992854
Title:
Update wpebackend-fdo to 1.6.1
Status in wpebackend-fdo package in Ubuntu:
New
Bug description:
Impact
--
This is a minor bugfix release of the 1.6.x series:
https://wpewebkit.org/release/wpebackend-fdo-1.6.1.html
The version currently in 20.04 LTS is 1.6.0, which accidentally shipped with
a bug that made the symbols wpe_fdo_get_{major,minor,micro}_version hidden.
These were supposed to be public (which is fixed in 1.6.1) and can be used
by other components to check the installed version at runtime.
In particular WebKitGTK depends on wpebackend-fdo, and we expect future
security updates may use these functions. The WebKitGTK team has committed
to making it possible for 20.04 to get updates until April 2023, and this
update makes those possible. Users of WebKit-based browsers should be able
to browse the Web with an up-to-date WebKitGTK stack that receives security
updates :)
Test Plan
-
The following C program can be used to check that the bug is present before
the wpebackend-fdo update, and that the issue was fixed afterwards:
/*
* $CC -o wpefdoversion wpefdoversion.c $(pkg-config --cflags --libs
wpebackend-fdo-1.0)
*
* This will:
* - Fail to link with wpebackend-fdo 1.6.0
* - Succeed with version 1.6.1
*/
#include
#include
int main(int argc, char *argv[]) {
printf("wpebackend-fdo runtime version: %d.%d.%d\n",
wpe_fdo_get_major_version(), wpe_fdo_get_minor_version(),
wpe_fdo_get_micro_version());
return 0;
}
Browsers which use WebKitGTK for rendering web content running in a Wayland
session
use wpebackend-fdo. Loading e.g.
https://people.igalia.com/aperez/poster-circle.html
in Epiphany (package epiphany-browser) should work the same before and after
the update.
What Could Go Wrong
---
Given the little amount of changes between versions 1.6.0 and 1.6.1, the
possibility
of breakage is minimal to none. Diff:
[Desktop-packages] [Bug 1991678] [NEW] X seems to lag at random intervals
Public bug reported: Hey, I trust you are well. I just noticed odd behaviour probably related to video resources which causes the entire GUI to lag for typing or to transition between screens and apps especially if there's a notification or any other new graphical interaction. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 11:30:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0839] InstallationDate: Installed on 2022-06-09 (116 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Latitude 3490 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0YRH3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/24/2022:br1.19:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn0YRH3X:rvrA00:cvnDellInc.:ct10:cvr:sku0839: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1991678 Title: X seems to lag at random intervals Status in xorg package in Ubuntu: New Bug description: Hey, I trust you are well. I just noticed odd behaviour probably related to video resources which causes the entire GUI to lag for typing or to transition between screens and apps especially if there's a notification or any other new graphical interaction. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 11:30:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0839] InstallationDate: Installed on 2022-06-09 (116 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Latitude 3490 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0YRH3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/24/2022:br1.19:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn0YRH3X:rvrA00:cvnDellInc.:ct10:cvr:sku0839: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
It looks like this wasn't needed in practice; marking as Won't Fix. ** Changed in: ghostscript (Ubuntu Xenial) Status: In Progress => Won't Fix ** Changed in: ghostscript (Ubuntu Xenial) Importance: Medium => Undecided ** Changed in: ghostscript (Ubuntu Xenial) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) ** Changed in: ghostscript (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: ghostscript (Ubuntu Bionic) Importance: Medium => Undecided ** Changed in: ghostscript (Ubuntu Bionic) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in cups-filters package in Ubuntu: Invalid Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Invalid Status in ghostscript source package in Xenial: Won't Fix Status in cups-filters source package in Bionic: Invalid Status in ghostscript source package in Bionic: Won't Fix Bug description: [Impact] * After an update of ghostscript but not cups-filters users may hit errors printing PDF files (LP#1828401). * This is possible as Landscape does not consider the -security pocket (has both ghostscript/cups-filters) but rather USN notices and ghostscript had a notice [0]. The regression on cups-filters was identified later, and doesn't warrant a USN notice. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. * This doesn't fix the current situation with Landscape and USNs so this same problem might still occur again, but at least it is already in place on future updates. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. [Other Info] * This is only required in Xenial and Bionic. * Trusty doesn't have the ghostscript update that causes the problem. * Disco/Eoan have the cups-filters fix that it requires (1.22.5+). [Links] [0] https://usn.ubuntu.com/3970-1/ [1] https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+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 1988847] Re: Add a direct link to the irc support channel list
Marking as wishlist per request from OP on Libera ** Changed in: yelp (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1988847 Title: Add a direct link to the irc support channel list Status in yelp package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 @ 6/9/2022 [Current Case] When launching the gnome Yelp icon under category 'Get more help'/community support the user is forwarded to https://ubuntu.com/support/community-support and needs to click 4 times to actualy get to the irc channel list to get support [Wislist] Please add a more direct link towards the Ubuntu irc support channels from inside Yelp/get more help so the user can get a better support experience. The Yelp icon is on the Ubuntu-desktops dock by default, so this could benefit to a quick irc help ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 42.1-1 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 14:56:22 2022 SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1988847/+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 1987168] [NEW] Video problems
Public bug reported: Video doesn't show options for other resolutions ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 20 11:26:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2022-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. H55M-S2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7695fd9a-b5ed-4bac-a4ca-5ca31eec559d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: H55M-S2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd09/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2V:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2V:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: H55M-S2V dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1987168 Title: Video problems Status in xorg package in Ubuntu: New Bug description: Video doesn't show options for other resolutions ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 20 11:26:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2022-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. H55M-S2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7695fd9a-b5ed-4bac-a4ca-5ca31eec559d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: H55M-S2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd09/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2V:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2V:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: H55M-S2V dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this
[Desktop-packages] [Bug 1983144] Re: Make thunderbird recognize irc: system-handler
setting as WISHLIST per request from OP on#ubuntu-discuss ** Changed in: thunderbird (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983144 Title: Make thunderbird recognize irc: system-handler Status in thunderbird package in Ubuntu: New Bug description: Ubuntu 22.04 @ 29/07/2022 Current case: Thunderbird is installed by default on ubuntu and has a built-in chat/irc client but when clicking irc/ircs links on a browser system-handler does not recognize thunderbird as default irc client Wishlist: Please make Thunderbird open irc links to open with its built-in chat client so users can find their favorite irc (support) channels easy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 Uname: Linux 5.17.7-051707-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1007 F pulseaudio BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 20:25:54 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IpRoute: default via 192.168.1.1 dev enp1s0f1 proto dhcp metric 100 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev enp1s0f1 scope link metric 1000 192.168.1.0/24 dev enp1s0f1 proto kernel scope link src 192.168.1.34 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.63 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Prefs: extensions.lastAppVersion: "91.11.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.11.0/20220628000715 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983144/+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 1970013] Re: Totem Video player displays distorted video (Intel Ivy Bridge)
Posted a new bug tagged regression-update: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983042 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1970013 Title: Totem Video player displays distorted video (Intel Ivy Bridge) Status in Gstreamer1.0: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in totem package in Ubuntu: Invalid Status in gstreamer-vaapi source package in Jammy: Fix Released Bug description: Impact -- Videos are unplayable in apps like Ubuntu's default video player for people using some Intel graphics cards including Ivy Bridge. Test Case - On an affected system, install the update. Then try playing the video. It should display normally. What Could Go Wrong --- If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. Original Bug Report --- Ubuntu 22.04 freshly installed along with ubuntu-restricted-extra package. Default totem player unable to play videos properly. videos looks distorted. Forwarding videos does not work. Video get stopped once forwarded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 11:02:49 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9] InstallationDate: Installed on 2022-04-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 34601F4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.release: 2.59 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 34601F4 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 34601F4 dmi.product.sku: LENOVO_MT_3460 dmi.product.version: ThinkPad X1 Carbon 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 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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 2:2.99.917+git20210115-1 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/gstreamer1.0/+bug/1970013/+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 1983042] [NEW] gstreamer-vaapi 1.20.1-1ubuntu1 can't be installed
Public bug reported: The "Depends: libgstreamer-plugins-bad1.0-0 (>= 1.20.3)" kept when backporting gstreamer-vaapi 1.20.3 isn't matched by such a backported version of the libgstreamer-plugins-bad1.0-0 package. See https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1970013/comments/18 I'm not sure if the other package should be backported or if the dependency metadata change should be reverted. Looking at the upstream bug, the fix does interact with the bad plugins by giving them higher priority. Not sure if either option has been sufficiently tested. https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2459 ** Affects: gstreamer-vaapi (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1983042 Title: gstreamer-vaapi 1.20.1-1ubuntu1 can't be installed Status in gstreamer-vaapi package in Ubuntu: New Bug description: The "Depends: libgstreamer-plugins-bad1.0-0 (>= 1.20.3)" kept when backporting gstreamer-vaapi 1.20.3 isn't matched by such a backported version of the libgstreamer-plugins-bad1.0-0 package. See https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1970013/comments/18 I'm not sure if the other package should be backported or if the dependency metadata change should be reverted. Looking at the upstream bug, the fix does interact with the bad plugins by giving them higher priority. Not sure if either option has been sufficiently tested. https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2459 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1983042/+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 1978890] Re: FIPS/OEM installation compatibility is unclear to the end-user
We discussed this on the UA team and we believe we can warn the user of the potential problems of enabling FIPS we using a OEM kernel, but we don't think we should block this on the UA side, since users could still be aware of the risk and follow through with the procedure. However, before we deliver this through UA, we believe we need to sort the GRUB_FLAVOUR_ORDER scenario. Otherwise we will warn the user and even if they want to proceed with FIPS, the will end up in the OEM kernel regardless. But let us know if you think we should definitely block enabling FIPS on a machine running a OEM kernel. -- 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/1978890 Title: FIPS/OEM installation compatibility is unclear to the end-user Status in subiquity package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: [Overall Summary] Converting to cover all oem/fips compatibility issues with ua/installers/update-manager. These projects are mostly silo'd, so when they all converge it creates a confusing and frustrating experience for the user. At it's core, the problem is that both fips and oem us GRUB_FLAVOUR_ORDER to select the preferred kernel to boot from, disregarding versioning. The main issues are: 1. ubuntu-drivers should not attempt to `oem-ify` a `fipsified` machine 2. ua tool should not attempt to `fipsify` an oem machine 3. subiquity should mention that drivers page is potentially making machine realtime & fips incompatible Below are some reproducible examples of issues: --- (Subiquity installer case) [Summary] A recent change to the subiquity snap adds support for installing oem drivers at time of instance install. If the user installs these packages, then attempts to install the fips packages post-install, fips will install as expected, but the system will always boot to the oem kernel. [Expected Behavior] Messaging should clearly indicate that installing the oem packages will make the environment incompatible with fips/RT kernel/ etc. [Observed Behavior] Subiquity just offers additional drivers, without clarifying the compatibility complications. [Replication Steps] (Using Dell Inc. Precision 7920 Tower/060K5C) 1. Install from current focal ISO 2. Confirm driver installation on the oem gui page 3. Install ua client/fips 4. Reboot 5. Observe kernel version (oem) --- (update-manager case) [Summary] A feature was added to allow for post-install enablement for oem-enabled devices via update manager: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050 While this works great for some situations, it can lead to users unexpectedly installing the oem meta package + associated kernel, overwriting an existing fips installation, as the "Improved hardware support" bundle may not be noticed when operating update-manager [Expected Behavior] For non linux-generic running installs, the post-install oem enablement functionality should not trigger, nor should it add the additional repositories to the client's sources.list.d. [Observed Behavior] sources.list.d is updated and "Improved hardware support" is allowed as an option in update-manager, which leads to clients unexpectedly losing compliance in fips environments. [Replication Steps] (Using Dell Inc. Precision 7920 Tower/060K5C) 1. Install from current focal ISO 2. Attach a ua subscription 3. Enable the fips-updates service 4. Reboot the system, login the desktop and wait for a while. The notification will pop up and it will show "Improved hardware support" on the certified machines that has the OEM metapackage support. 5. Click through the update-manager prompt and install the oem packages 6. Reboot check fips status oem's config in /etc/default/grub.d/* does not have a number prefix, and thus will always override 99-ubuntu-fips.cfg when calling update- grub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1978890/+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 1982688] Re: Make poweroff, logout and restart icons able to drag on dock
marking WISHLIST per request from OP on #ubuntu-discuss. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist -- 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/1982688 Title: Make poweroff, logout and restart icons able to drag on dock Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 desktop @ 24/07/2022 Current situation: the power-off, reboot and logout icons are now searchable in application launcher but they cannot be dragged onto the dock Wishlist: please make these icons physical to be able to drag onto the dock so users can fastly power-off logout and restart their systems ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 11:29:51 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982688/+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 1981932] [NEW] Loud squeaking noise which disappears when audio is played
Public bug reported: When I connect my headset, theres a loud radio like noise which disappears when I play some audio but comes back as soon as i stop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: costa 1294 F pulseaudio costa 6980 F alsamixer /dev/snd/controlC1: costa 1294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 17 22:35:58 2022 InstallationDate: Installed on 2022-07-17 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Nitro AN515-55, Realtek ALC295, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stonic_CMS dmi.board.vendor: CML dmi.board.version: V1.00 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd03/19/2020:br1.0:efr1.0:svnAcer:pnNitroAN515-55:pvrV1.00:rvnCML:rnStonic_CMS:rvrV1.00:cvnAcer:ct10:cvrV1.00:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-55 dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1981932 Title: Loud squeaking noise which disappears when audio is played Status in alsa-driver package in Ubuntu: New Bug description: When I connect my headset, theres a loud radio like noise which disappears when I play some audio but comes back as soon as i stop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: costa 1294 F pulseaudio costa 6980 F alsamixer /dev/snd/controlC1: costa 1294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 17 22:35:58 2022 InstallationDate: Installed on 2022-07-17 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Nitro AN515-55, Realtek ALC295, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stonic_CMS dmi.board.vendor: CML dmi.board.version: V1.00 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd03/19/2020:br1.0:efr1.0:svnAcer:pnNitroAN515-55:pvrV1.00:rvnCML:rnStonic_CMS:rvrV1.00:cvnAcer:ct10:cvrV1.00:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-55 dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1981932/+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 1936261] Re: Session creation inhibited when trying to connect to VNC server after Ubuntu 21.04 upgrade
Seeing this bug, checking the logs I see: Jun 07 17:22:27 pjds-ubuntu gnome-remote-desktop-daemon[30361]: [17:22:27:525] [30361:2971765] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] Jun 07 17:22:27 pjds-ubuntu gnome-remote-de[30361]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set with version RDPGFX_CAPVERSION_104, Client cap flags: H264 (AVC444): true, H264 (AVC420):> Jun 07 17:22:28 pjds-ubuntu gnome-remote-de[30361]: Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited Just checking google for related issues I came across this upstream bug: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/16. Maybe it's not the same issue though, as I am using RDP. Cheers, Peter ** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #16 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/16 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1936261 Title: Session creation inhibited when trying to connect to VNC server after Ubuntu 21.04 upgrade Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 21.04 from 20.10, connecting to VNC server will not work from some clients. Prompts for password, then the client gives the error message "The connection closed unexpectedly." Gnome- remote-desktop package gives the following error message in syslog: > gnome-remote-de[111245]: Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1936261/+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 1973176] [NEW] webkit process hangs when viewing certain contens on whatsapp web loaded on epiphany
Public bug reported: One interesting note is that under system monitor, it shows the process as having 99 GB of virtual memory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwebkit2gtk-4.1-0 2.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 12 09:40:00 2022 InstallationDate: Installed on 2022-05-08 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1973176 Title: webkit process hangs when viewing certain contens on whatsapp web loaded on epiphany Status in webkit2gtk package in Ubuntu: New Bug description: One interesting note is that under system monitor, it shows the process as having 99 GB of virtual memory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwebkit2gtk-4.1-0 2.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 12 09:40:00 2022 InstallationDate: Installed on 2022-05-08 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1973176/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I tried the sudo apt install xdg-desktop-portal-gnome, but no luck. Download does not work with Chrome or Firefox. Executing the command indicates 0 upgrades, 0 newly installed and 0 not upgraded. I guess I have the latest version running. I'm using the generic install of 22.04. Ubuntu was working fine before the upgrade. Any other suggestion? ** Description changed: - Whenever any file is downloaded, the browser will freeze. + Whenever any file is downloaded, the browser will freeze. Download + files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. -- 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/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1970043] Re: freeze occurs when wayland is connected to a second monitor
Same bug on 22.04, fresh install, Ryzen 5800U. Workaround : Enable fractional scaling, plug, then disable it. Solved the issue permanently. -- 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/1970043 Title: freeze occurs when wayland is connected to a second monitor Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I didn't encounter this bug with ubuntu 21.10 and when I tried to use x11 in 22.04 everything was fine, so it seems to be related to mutter42. And my computer is an amd 47 4800u machine and should only have one integrated graphics card ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 24 00:38:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1970043/+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 1969853] Re: Bluetooth doesn't work but seems active
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969853 Title: Bluetooth doesn't work but seems active Status in bluez package in Ubuntu: New Bug description: After updating to version 22.04, with kernel 5.15.0-25, Bluettoth stopped working via menu. Before I used versions 20.04 and 21.10, the latter with kernel 5.13, and Bluetooth was recognized normally. The bluetooth status in the terminal is this: diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago Docs: man:bluetoothd(8) Main PID: 1100 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18808) Memory: 1.8M CPU: 66ms CGroup: /system.slice/bluetooth.service └─1100 /usr/lib/bluetooth/bluetoothd abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service... abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64 abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service. abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management interface 1.21 initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969853/+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 1966581] Re: Launcher screenshot UI cannot be added to dock
Importance set to WISHLIST per request on #ubuntu-bugs-announce ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist -- 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/1966581 Title: Launcher screenshot UI cannot be added to dock Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 27/03/2022 The new gnome-shell built-in screenshot UI has a launcher when you search it from start/applications, but the icon cannot be dragged or added to the dock This wishlist is for novice users that might not be familiar with the prt scr button and might benefit a launcher from the dock, like gnome-screenshot did before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 13:38:44 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966581/+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 1965138] [NEW] Desktop application should check for service available information before listing it
Public bug reported: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "jammy-desktop-error.png" https://bugs.launchpad.net/bugs/1965138/+attachment/5569662/+files/jammy-desktop-error.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965138 Title: Desktop application should check for service available information before listing it Status in software-properties package in Ubuntu: New Bug description: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965138/+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 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
Steps to reproduce: This is a video of how to reproduce it: https://emalm.com/?v=DsBSK 1. Go to google.com 2. Click the Google logo, move the logo as little as possible but enough to cause dragging and then release as soon as possible after you see that your mouse started dragging. Eventually you could just do it extremely quickly like in the video: https://emalm.com/?v=DsBSK 3. Sometimes the cursor would get stuck in the drag mode with the Google logo attached to it (even though the mouse button is no longer pressed). It usually requires a lot of attempts to reproduce. It's reproducible on 20.04 and 21.10 Wayland. It's reproducible in Chrome, Firefox title bar, some other programs. It makes the mouse unusable. I'm absolutely certain that it's not an issue with the mouse (I've researched and tested everything thoroughly). I've verified the release event is received via xinput --test-xi2 --root, verified that this doesn't affect non-draggable things (like mousedown / mouseup Javascript events), verified with another input device (graphics tablet), where it also happens. I've tested different kernels: 5.4, 5.11, 5.13 and this bug exists on all of them. -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+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 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
Please also see: https://askubuntu.com/questions/1394981/mouse-gets- stuck-in-drag-mode-if-you-click-something-move-the-mouse-and-quickly -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+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 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
I can reproduce it on Live CDs: 20.04 21.10 Wayland. So it doesn't seem to be a problem with Xorg, but maybe something more low-level. This bug requires immediate attention! It makes the mouse unusable and requires crazy workarounds like mapping a keyboard key to a click and using it as a mouse button (so it releases immediately, to prevent dragging). -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+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 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
I have a similar problem on Linux Mint Cinnamon 20.3: https://bugs.launchpad.net/ubuntu/+bug/1961034 Video: https://emalm.com/?v=DsBSK Is anyone working on fixing this bug? -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+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 1956211] [NEW] package libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-li
Public bug reported: didn't succeed to instal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 3 10:41:34 2022 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 InstallationDate: Installed on 2021-02-02 (335 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: sane-backends Title: package libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1956211 Title: package libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 Status in sane-backends package in Ubuntu: New Bug description: didn't succeed to instal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 3 10:41:34 2022 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 InstallationDate: Installed on 2021-02-02 (335 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: sane-backends Title: package libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1956211/+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 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb
I can confirm as well for 18.04. Still there, and #11 still solves it. -- 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/1314160 Title: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb Status in cups package in Ubuntu: Confirmed Bug description: When I print to my smb printer, I get a dbus notification of the following entries in my syslog: Apr 29 12:27:15 tinker kernel: [ 3359.467314] type=1400 audit(1398770835.923:150): apparmor="DENIED" operation="mknod" profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7 Apr 29 12:27:15 tinker kernel: [ 3359.467453] type=1400 audit(1398770835.923:151): apparmor="DENIED" operation="mknod" profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7 Apr 29 12:27:15 tinker kernel: [ 3359.469047] type=1400 audit(1398770835.923:152): apparmor="DENIED" operation="mknod" profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7 I get new entries every time I print. I'm running Ubuntu 14.04 with cups-daemon 1.7.2-0ubuntu1 on btrfs, fwiw. I saw this replicated on http://www.dedoimedo.com/computers/ubuntu- trusty-tahr-laptop-ultrabook.html . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1314160/+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 1877038]
(In reply to paul from comment #12) > (In reply to Neha Kochar [:neha] from comment #11) > > > Sorry for the delay in getting this finished. We don't currently have > > anyone available to work on this. We will prioritize this as soon as we > > can. Windows works because of the work in Bug 1508115. > > I appreciate the work that you guys for free and I understand that resources > are tight. Is there some way we could provide some financial support to > address this specific issue? > > How can Firefox claim to be all about Privacy, Security and Speed when it > doesn't support the greatest improvement we have ever had to all of those > things when it comes to logins? I expected Firefox to be the very first > to get this working, not the last. > > Again, I do really appreciate what the developers do but I really think that > this issue deserves to be a top priority and I'm sure there are plenty of > people who would be willing to fund it. Currently someone from SUSE has been working on authenticator-rs. They really want to see webauthn added to firefox and have been working for weeks on CTAP2 support now. You can check out https://github.com/mozilla/authenticator-rs/pull/150 https://github.com/mozilla/authenticator-rs/pull/154 and their own development branch on https://github.com/msirringhaus/authenticator- rs/tree/ctap2-cont Of course, work would be much light if it wasn't a single person doing all the work! Maybe this gives you some idea of the progress of things right now :) -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 9325] Re: No sound in firefox with flashplugin
[Child 33262, MediaDecoderStateMachine #1] WARNING: Decoder=7fc16122f800 [OnMediaSinkAudioError]: file /build/firefox- oeeWcI/firefox-90.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3941 -- 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/9325 Title: No sound in firefox with flashplugin Status in firefox package in Ubuntu: Invalid Bug description: I have apt-get the flash plugin for mozilla, installed it via firefox's extensions and even downloaded it from macromedia.com, but to no avail. I still get no sound with flash content in firefox 1.0 My sound elsewhere works, but not in flash content. Any ideas why? It worked fine in mandrake, suse, and xp sp2 (ugh) Thanks, Evan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/9325/+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 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)
I'm here to say that I'm having the same issue. Until this evening, I was using Debian 10 with KDE, but I installed Ubuntu 20.04 a few hours ago. I use a laptop with a external keyboard connected on it and my laptop have a numeric keyboard and my external keyboard don't, so I always use the laptop keyboard to insert numbers. However, each time I swap the keyboard, my computer frozen. Also, I have a mouse with several buttons and two of them are configured as "PgUp" and "PgDn" because I find it more practical over there. However, unfortunately, I can't use it properly because the computer crashes every time I press a button. However, I think it's worth mentioning that mouse buttons that belong to the mouse (like click and scroll) don't have this problem. In short, if I switch keyboards, whether it's laptop, external or mouse buttons, my computer freezes. -- 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/108 Title: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg) Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1937871] Re: [Galaxy Buds Live (F88A), Volume lower than it should be
** Tags added: hw-specific kernel-bug -- 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/1937871 Title: [Galaxy Buds Live (F88A), Volume lower than it should be Status in alsa-driver package in Ubuntu: New Bug description: Galaxy Buds Live sound volume is lower than in other devices using non-linux operating systems. This however doesn't happen with the zen linux kernel where the volume is more acceptable. If I try to mitigate this with volumes level above 100 percent in pulse audio, the sound is distorted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-1009.10-oem 5.13.0 Uname: Linux 5.13.0-1009-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gregassagraf 5248 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 16:09:14 2021 InstallationDate: Installed on 2021-07-19 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Galaxy Buds Live (F88A) Symptom_Type: None of the above Title: [Galaxy Buds Live (F88A), playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07N10G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/01/2021:br1.6:svnDellInc.:pnInspiron5402:pvr:sku0A01:rvnDellInc.:rn07N10G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5402 dmi.product.sku: 0A01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1937871/+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 1937871] [NEW] [Galaxy Buds Live (F88A), Volume lower than it should be
Public bug reported: Galaxy Buds Live sound volume is lower than in other devices using non- linux operating systems. This however doesn't happen with the zen linux kernel where the volume is more acceptable. If I try to mitigate this with volumes level above 100 percent in pulse audio, the sound is distorted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-1009.10-oem 5.13.0 Uname: Linux 5.13.0-1009-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gregassagraf 5248 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 16:09:14 2021 InstallationDate: Installed on 2021-07-19 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Galaxy Buds Live (F88A) Symptom_Type: None of the above Title: [Galaxy Buds Live (F88A), playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07N10G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/01/2021:br1.6:svnDellInc.:pnInspiron5402:pvr:sku0A01:rvnDellInc.:rn07N10G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5402 dmi.product.sku: 0A01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1937871 Title: [Galaxy Buds Live (F88A), Volume lower than it should be Status in alsa-driver package in Ubuntu: New Bug description: Galaxy Buds Live sound volume is lower than in other devices using non-linux operating systems. This however doesn't happen with the zen linux kernel where the volume is more acceptable. If I try to mitigate this with volumes level above 100 percent in pulse audio, the sound is distorted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-1009.10-oem 5.13.0 Uname: Linux 5.13.0-1009-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gregassagraf 5248 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 16:09:14 2021 InstallationDate: Installed on 2021-07-19 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Galaxy Buds Live (F88A) Symptom_Type: None of the above Title: [Galaxy Buds Live (F88A), playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07N10G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/01/2021:br1.6:svnDellInc.:pnInspiron5402:pvr:sku0A01:rvnDellInc.:rn07N10G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5402 dmi.product.sku: 0A01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1937871/+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 1933085] Re: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
I was informed by Alberto Milone that the 340 driver was discontinued and won't get updates to support the 5.11 kernels. ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1933085 Title: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in linux-hwe-5.11 source package in Focal: Invalid Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-340 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/n/nvidia-graphics-drivers-340/20210611_210127_38d90@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933085/+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 1933085] Re: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1933085/+attachment/5505995/+files/make.log ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1933085 Title: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in linux-hwe-5.11 source package in Focal: Invalid Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-340 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/n/nvidia-graphics-drivers-340/20210611_210127_38d90@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933085/+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
