[Desktop-packages] [Bug 1973379] Re: "additional drivers" says we are using nvidia drivers but its not true
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- 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/1973379 Title: "additional drivers" says we are using nvidia drivers but its not true Status in software-properties package in Ubuntu: Expired Bug description: after selecting the recommended, tested nvidia driver, and restarting the system as suggested, no nvidia modules are loaded at all, instead just nouveau kernel modules are loaded and all the nvidia tools confirm that no nvidia drivers are being used and running. But starting the software properties and opening the "additional drivers" tab again, I'm being told the nvidia drivers are in selected and "1 proprietary driver in use". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 13 23:20:12 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-04-12 (760 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 SourcePackage: software-properties UpgradeStatus: Upgraded to jammy on 2022-04-28 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973379/+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 1982493] Re: gnome-remote-desktop: Couldn't retrieve RDP username: Credentials not set - and more
The security issue you refer to looks to have been assigned CVE-2022-24882 which was fixed via https://ubuntu.com/security/notices/USN-5461-1 more than a month ago. If there is still a subsequent bug in gnome-remote-desktop / freerdp then you should file a specific bug about that *and* mark it as public so the appropriate Ubuntu developers can see it. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24882 ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Fix Released ** Package changed: gnome-remote-desktop (Ubuntu) => freerdp2 (Ubuntu) ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1982493 Title: gnome-remote-desktop: Couldn't retrieve RDP username: Credentials not set - and more Status in freerdp2 package in Ubuntu: Fix Released Bug description: An immediate upgrade to 2.7.0 appears to be critical both for functionality (cannot work without it and having the backported NTLM fixes) and security: Please see the following for details: https://askubuntu.com/questions/1419705/gnome-remote-desktop-couldnt-retrieve-rdp-username-credentials-not-set-and The FreeRDP developers believe that Ubuntu has not backported the NTLM fixes from 2.7.0 to 2.6.1 and subsequently the reason for the failures users are experiencing. The easier / more clean path appears to be to upgrade to FreeRDP 2.7.0. It seems to be related to this vulnerability bounty: https://vuldb.com/?id.198528 See: * https://www.freerdp.com/2022/04/25/2_7_0-release * https://github.com/FreeRDP/FreeRDP/blob/2.7.0/ChangeLog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1982493/+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 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1972977 Title: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+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 1982472] Re: Support A+N platform
FWIK, there are many related packages need to modify together since it's
similar to an interface change.
It'll be more reasonable if we target to Jammy+.
The power-saving mode in Jammy is almost useless (but the nvidia-340, 390 may
still need it).
However, the 'power-saving' mode apply:
```
"Section \"ServerLayout\"\n"
"Identifier \"layout\"\n"
"Option \"AllowNVIDIAGPUScreens\"\n"
"EndSection\n\n");
```
and disable nvidia driver.
If so, then I think we could say it's "non-nvidia" ("no-nvidia", etc..) instead
of "intel" or "amd".
Which will more suitable when multiple graphic cards are attached.
Hi Alberto,
Have you any comment on this?
** Also affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1982472
Title:
Support A+N platform
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
New
Status in nvidia-settings package in Ubuntu:
New
Bug description:
The 'Power Saving Mode' of Nvidia app should change to ATI when the
integrated graphic is Advanced Micro Devices.
[Steps to reproduce]
1. Install the OEM image
2. Boot and log
3. 'Dash' -> 'Nvidia Settings'
4. Verify the 'PRIME Profiles'
[Expected result]
Nvidia (Performance Mode)
Nvidia On-Demand
AMD (Power Saving Mode)
u@Thor-P3-AMD-2:~$ prime-select
Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query
[Actual result]
Nvidia (Performance Mode)
Nvidia On-Demand
Intel (Power Saving Mode)
u@Thor-P3-AMD-2:~$ prime-select
Usage: /usr/bin/prime-select nvidia|intel|on-demand|query
[Failure rate]
100%
[Other Information]
ubuntu 22.04
nvidia-prime 0.8.17.1
nvidia-settings 510.47.03-0ubuntu1
nvidia-driver 510.73.05-0ubuntu0.22.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1982472/+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 1982472] Re: Support A+N platform
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1982472 Title: Support A+N platform Status in OEM Priority Project: New Status in nvidia-prime package in Ubuntu: New Bug description: The 'Power Saving Mode' of Nvidia app should change to ATI when the integrated graphic is Advanced Micro Devices. [Steps to reproduce] 1. Install the OEM image 2. Boot and log 3. 'Dash' -> 'Nvidia Settings' 4. Verify the 'PRIME Profiles' [Expected result] Nvidia (Performance Mode) Nvidia On-Demand AMD (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query [Actual result] Nvidia (Performance Mode) Nvidia On-Demand Intel (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|intel|on-demand|query [Failure rate] 100% [Other Information] ubuntu 22.04 nvidia-prime 0.8.17.1 nvidia-settings 510.47.03-0ubuntu1 nvidia-driver 510.73.05-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1982472/+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 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation
Huh, interesting. When I hover my cursor over the sound widgit in my top panel bar, it says: Output: 100% 0.00 dB Built-in Audio Analog Stereo And it says this even when I have something playing that ought to be outputting sound. Doesn't 0.00 db mean silence? Reading this now to find out what I can: https://sound.stackexchange.com/questions/25529/what-is-0-db-in-digital- audio -- "So audio meters don't show the dBu, dBV or dBFS level of the signal (some do, but as an extra). Instead they show 0dB as the standard operating level of the system." Oddly fascinating read. I had no idea that decibels were coined in relation to Bell labs. -- 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/1575912 Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hardware sound device is available, according to: aplay -l sudo lspci https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 27 22:06:16 2016 InstallationDate: Installed on 2016-04-24 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PXD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PXD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+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 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation
Re:^^^ Oh, and I have the soundcard: Realtek ALC269VB Analog, also. -- 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/1575912 Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hardware sound device is available, according to: aplay -l sudo lspci https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 27 22:06:16 2016 InstallationDate: Installed on 2016-04-24 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PXD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PXD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+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 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation
Hi, This sounds similar to my bug. I am pretty sure my physical speakers work, and even that they worked when I first installed Ubuntu Mate 22.04, but very shortly afterwards they stopped working. The headphone jack also doesn't work. I installed a jack-detection repo and now sometimes (not constantly) the headphones will shoot out max volume white noise. Here is my Alsa info: http://alsa- project.org/db/?f=608937f066095ec6710e5f3bafc292815da99414 I've been trying to fix this problem for a couple weeks now. I've followed different blogs on similar topics and read through various solutions to similar problems posted on launchpad or stackoverflow. Any help would be greatly appreciated. -- 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/1575912 Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hardware sound device is available, according to: aplay -l sudo lspci https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 27 22:06:16 2016 InstallationDate: Installed on 2016-04-24 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PXD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PXD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+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 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings
You can get the freerdp deb from https://launchpad.net/ubuntu/+source/freerdp2/2.6.1+dfsg1-3ubuntu2.2/+build/23854758 , that's probably another issue due to the apt phasing -- 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/1968213 Title: Icon theme reverts to Yaru when entering Appearance settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: [ Impact ] I upgraded to the 22.04 beta last week from 21.10. I use a custom icon theme. Whenever I enter the Appearance tab in settings the icon theme is set back to Yaru. [ Test case(s) ] 1. Run gsettings set org.gnome.desktop.interface gtk-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu User theme settings should have not changed (Adwaita is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The icon theme is still reset if changed externally while the appearance panel is open. -- 1. Run gsettings set org.gnome.desktop.interface icon-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu Icon theme settings should have not changed (Adwaita icon theme is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The theme is still reset if changed externally while the appearance panel is open. -- 1. From Gedit settings, select an editor color scheme that is not Yaru or Yaru-dark. 2. Start Settings Appearance panel: gnome-control-center ubuntu Gedit theme should not have changed 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Does not change the Gedit theme, unless a Yaru variant is selected as gedit color scheme. [ Regression Potential ] Theme is not updated to upgraders that use some unsupported custom themes. Theme selection doesn't work in some custom configurations. --- ProblemType: BugDistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 20:47:41 2022 InstallationDate: Installed on 2022-02-02 (64 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)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/1968213/+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 1981611] Re: conf file prompt during upgrade from Focal to Jammy
This bug was fixed in the package speech-dispatcher - 0.11.1-3ubuntu1 --- speech-dispatcher (0.11.1-3ubuntu1) kinetic; urgency=medium * debian/speech-dispatcher.maintscript: - don't remove mary-generic.conf on upgrade, it's included in the package again. Fix conffile prompt on update (lp: #1981611) -- Sebastien Bacher Thu, 21 Jul 2022 17:15:31 +0200 ** Changed in: speech-dispatcher (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1981611 Title: conf file prompt during upgrade from Focal to Jammy Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Bug description: * Impact A conffile prompt is displayed on upgrade * Test Case upgrade speech-dispatcher from the focal to the jammy-proposed version, there should be no conffile prompt * Regression potential the change only remove a .mainscript line to remove the conffile, if the change was incorrect the prompt could still be there or a an old conffile could be not removed on upgrade - I was performing a distribution upgrade of an Ubuntu Desktop install of Ubuntu 20.04 to Ubuntu 22.04 when I encountered a debconf prompt regarding a speech-dispatcher config file which I had not modified. From /var/log/dist-upgrade/apt-term.log: Setting up speech-dispatcher (0.11.1-1) ...^M Installing new version of config file /etc/speech-dispatcher/modules/cicero.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/dtk-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/epos-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/festival.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/flite.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/llia_phon-generic.conf ...^M ^M Configuration file '/etc/speech-dispatcher/modules/mary-generic.conf'^M ==> Deleted (by you or by a script) since installation.^M ==> Package distributor has shipped an updated version.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** mary-generic.conf (Y/I/N/O/D/Z) [default=N] ? n^M Installing new version of config file /etc/speech-dispatcher/modules/swift-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/speechd.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/mary-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/espeak-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/pico-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ivona.conf ...^M speech-dispatcherd.service is a disabled or a static unit not running, not starting it.^M Removing obsolete conffile /etc/speech-dispatcher/modules/baratinoo.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ibmtts.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/kali.conf ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1981611/+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 1981611] Re: conf file prompt during upgrade from Focal to Jammy
Hello Brian, or anyone else affected, Accepted speech-dispatcher into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/speech- dispatcher/0.11.1-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: speech-dispatcher (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1981611 Title: conf file prompt during upgrade from Focal to Jammy Status in speech-dispatcher package in Ubuntu: Fix Committed Status in speech-dispatcher source package in Jammy: Fix Committed Bug description: * Impact A conffile prompt is displayed on upgrade * Test Case upgrade speech-dispatcher from the focal to the jammy-proposed version, there should be no conffile prompt * Regression potential the change only remove a .mainscript line to remove the conffile, if the change was incorrect the prompt could still be there or a an old conffile could be not removed on upgrade - I was performing a distribution upgrade of an Ubuntu Desktop install of Ubuntu 20.04 to Ubuntu 22.04 when I encountered a debconf prompt regarding a speech-dispatcher config file which I had not modified. From /var/log/dist-upgrade/apt-term.log: Setting up speech-dispatcher (0.11.1-1) ...^M Installing new version of config file /etc/speech-dispatcher/modules/cicero.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/dtk-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/epos-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/festival.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/flite.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/llia_phon-generic.conf ...^M ^M Configuration file '/etc/speech-dispatcher/modules/mary-generic.conf'^M ==> Deleted (by you or by a script) since installation.^M ==> Package distributor has shipped an updated version.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** mary-generic.conf (Y/I/N/O/D/Z) [default=N] ? n^M Installing new version of config file /etc/speech-dispatcher/modules/swift-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/speechd.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/mary-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/espeak-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/pico-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ivona.conf ...^M speech-dispatcherd.service is a disabled or a static unit not running, not starting it.^M Removing obsolete conffile /etc/speech-dispatcher/modules/baratinoo.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ibmtts.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/kali.conf ...^M To manage notifications about this bug go to:
[Desktop-packages] [Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
** Changed in: poppler (Ubuntu) Status: New => Triaged ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly Status in Poppler: Unknown Status in evince package in Ubuntu: Invalid Status in poppler package in Ubuntu: Triaged Bug description: Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04. The symptom is that one can edit the form content and also save it, but that the entered text is only visible when the form field is focused and in edit mode. Otherwise the text it is invisible, also on printouts. Such bugs have been reported against Evince for a long time (e.g., https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am reporting this as a new bug because for the current form with which I am experiencing this it is a regression. I have attached the problematic form with two form fields filled out, one in the upper left corner and the big one in the lower half. I have produced this by taking the original, empty form (produced by somebody else) and first opened it in Evince 41.4, which I have installed from the snap package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field and saved the form. Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and entered text in the big field and saved the form. Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince 41.4. When I open the PDF again, only the text in the first field is visible. The text in the second field is visible only if I click into the field. The visibility of the field contents is the same for Evince 41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the problem is with Evince 42.3 incorrectly saving the field content, not with displaying it. Firefox shows and prints the content of both fields, though. Note that I cannot switch back to Evince 41 because for some other forms that I have the exact same problem happens only with the old version and the new version fixes it. So it seems that something changed that fixed it for some forms and broke it for others. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:32:27 2022 InstallationDate: Installed on 2021-11-26 (222 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: ID Status Spawn Bereit Zusammenfassung 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00 Installiere "evince" Snap SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1980836/+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 1982477] Re: UI does not work with Linux version 5.15.0-41
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu) -- 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/1982477 Title: UI does not work with Linux version 5.15.0-41 Status in linux package in Ubuntu: Incomplete Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+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 1982495] Re: distorted audio after update 5.15.0-42-lowlatency
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1982495 Title: distorted audio after update 5.15.0-42-lowlatency Status in linux package in Ubuntu: Incomplete Bug description: Hi. It is happening again updating 5.15.0-42 LOWLATENCY, as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066 Focusrite 2i2 2nd generation. Booting 5.13.0-52 LOWLATENCY solve, no distorted audio. Thx in advance, pleased to report more information about ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.15.0-42.45~20.04.1-lowlatency 5.15.39 Uname: Linux 5.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alf1589 F jackdbus /dev/snd/pcmC1D0c: alf1589 F...m jackdbus /dev/snd/pcmC1D0p: alf1589 F...m jackdbus /dev/snd/seq:alf1717 F a2jmidid CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Jul 21 17:17:29 2022 InstallationDate: Installed on 2021-02-05 (530 days ago) InstallationMedia: Ubuntu-Studio 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA NVidia Title: [USB-Audio - Scarlett 2i2 USB, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2012 dmi.bios.release: 30.240 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote TK85 dmi.board.vendor: Packard Bell dmi.board.version: V1.30 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.30 dmi.modalias: dmi:bvnPackardBell:bvrV1.30:bd08/13/2012:br30.240:svnPackardBell:pnEasyNoteTK85:pvrV1.30:rvnPackardBell:rnEasyNoteTK85:rvrV1.30:cvnPackardBell:ct10:cvrV1.30:skuCalpella_CRB: dmi.product.family: Intel_Mobile dmi.product.name: EasyNote TK85 dmi.product.sku: Calpella_CRB dmi.product.version: V1.30 dmi.sys.vendor: Packard Bell modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2022-07-21T16:49:41.895417 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982495/+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 1982495] Re: distorted audio after update 5.15.0-42-lowlatency
** Package changed: ubuntu => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1982495 Title: distorted audio after update 5.15.0-42-lowlatency Status in pulseaudio package in Ubuntu: New Bug description: Hi. It is happening again updating 5.15.0-42 LOWLATENCY, as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066 Focusrite 2i2 2nd generation. Booting 5.13.0-52 LOWLATENCY solve, no distorted audio. Thx in advance, pleased to report more information about ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.15.0-42.45~20.04.1-lowlatency 5.15.39 Uname: Linux 5.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alf1589 F jackdbus /dev/snd/pcmC1D0c: alf1589 F...m jackdbus /dev/snd/pcmC1D0p: alf1589 F...m jackdbus /dev/snd/seq:alf1717 F a2jmidid CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Jul 21 17:17:29 2022 InstallationDate: Installed on 2021-02-05 (530 days ago) InstallationMedia: Ubuntu-Studio 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA NVidia Title: [USB-Audio - Scarlett 2i2 USB, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2012 dmi.bios.release: 30.240 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote TK85 dmi.board.vendor: Packard Bell dmi.board.version: V1.30 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.30 dmi.modalias: dmi:bvnPackardBell:bvrV1.30:bd08/13/2012:br30.240:svnPackardBell:pnEasyNoteTK85:pvrV1.30:rvnPackardBell:rnEasyNoteTK85:rvrV1.30:cvnPackardBell:ct10:cvrV1.30:skuCalpella_CRB: dmi.product.family: Intel_Mobile dmi.product.name: EasyNote TK85 dmi.product.sku: Calpella_CRB dmi.product.version: V1.30 dmi.sys.vendor: Packard Bell modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2022-07-21T16:49:41.895417 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1982495/+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 1982495] [NEW] distorted audio after update 5.15.0-42-lowlatency
You have been subscribed to a public bug: Hi. It is happening again updating 5.15.0-42 LOWLATENCY, as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066 Focusrite 2i2 2nd generation. Booting 5.13.0-52 LOWLATENCY solve, no distorted audio. Thx in advance, pleased to report more information about ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.15.0-42.45~20.04.1-lowlatency 5.15.39 Uname: Linux 5.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alf1589 F jackdbus /dev/snd/pcmC1D0c: alf1589 F...m jackdbus /dev/snd/pcmC1D0p: alf1589 F...m jackdbus /dev/snd/seq:alf1717 F a2jmidid CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Jul 21 17:17:29 2022 InstallationDate: Installed on 2021-02-05 (530 days ago) InstallationMedia: Ubuntu-Studio 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA NVidia Title: [USB-Audio - Scarlett 2i2 USB, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2012 dmi.bios.release: 30.240 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote TK85 dmi.board.vendor: Packard Bell dmi.board.version: V1.30 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.30 dmi.modalias: dmi:bvnPackardBell:bvrV1.30:bd08/13/2012:br30.240:svnPackardBell:pnEasyNoteTK85:pvrV1.30:rvnPackardBell:rnEasyNoteTK85:rvrV1.30:cvnPackardBell:ct10:cvrV1.30:skuCalpella_CRB: dmi.product.family: Intel_Mobile dmi.product.name: EasyNote TK85 dmi.product.sku: Calpella_CRB dmi.product.version: V1.30 dmi.sys.vendor: Packard Bell modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2022-07-21T16:49:41.895417 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- distorted audio after update 5.15.0-42-lowlatency https://bugs.launchpad.net/bugs/1982495 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981966] Re: [SRU] libreoffice 7.3.5 for jammy
Correct, it is suppose to be replaced by 7.4.0~rc2 next week. -- 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/1981966 Title: [SRU] libreoffice 7.3.5 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release * Version 7.3.4 is currently released in jammy. For a list of fixed bugs compared to 7.3.4 see the list of bugs fixed in the release candidates of 7.3.5 (that's a total of 83 bugs): https://wiki.documentfoundation.org/Releases/7.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1797/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220719_091411_74233@/log.gz * [arm64] ... * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220719_110142_388ca@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220719_082728_0b9aa@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220719_080609_7c067@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 83 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981966/+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 1981881] Re: Firefox snap broken in Guest Account
How do you enable a guest account in Xubuntu? I just installed xubuntu 22.04 in a VM and I can't see the option on the login screen. ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1981881 Title: Firefox snap broken in Guest Account Status in firefox package in Ubuntu: Incomplete Bug description: My laptop is sometimes used by visitors. They want to browse the internet. So I setup the guest-account. I found out that the Firefox snap is broken on guest-accounts. When opening Firefox nothing happens. When starting FF from the command line of the guest-account I found out the following: $ firefox 2022/07/12 00:46:01.906615 tool_linux.go:82: cannot open snapd info file “/snap/snapd/current/usr/lib/snapd/info”: open /snap/snapd/current/usr/lib/snapd/info: permission denied Version information: Guest Account on Xubuntu 22.04 (Jammy) FF version: 102.0.1 (64-bit) Mozilla Firefox Snap for Ubuntu canonical-002-1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981881/+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 1981611] Re: conf file prompt during upgrade from Focal to Jammy
** Changed in: speech-dispatcher (Ubuntu) Status: Triaged => Fix Committed ** Description changed: + * Impact + A conffile prompt is displayed on upgrade + + * Test Case + upgrade speech-dispatcher from the focal to the jammy-proposed version, there should be no conffile prompt + + * Regression potential + the change only remove a .mainscript line to remove the conffile, if the change was incorrect the prompt could still be there or a an old conffile could be not removed on upgrade + + - + I was performing a distribution upgrade of an Ubuntu Desktop install of Ubuntu 20.04 to Ubuntu 22.04 when I encountered a debconf prompt regarding a speech-dispatcher config file which I had not modified. From /var/log/dist-upgrade/apt-term.log: Setting up speech-dispatcher (0.11.1-1) ...^M Installing new version of config file /etc/speech-dispatcher/modules/cicero.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/dtk-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/epos-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng-mbrola-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak-ng.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/espeak.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/festival.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/flite.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/llia_phon-generic.conf ...^M ^M Configuration file '/etc/speech-dispatcher/modules/mary-generic.conf'^M - ==> Deleted (by you or by a script) since installation.^M - ==> Package distributor has shipped an updated version.^M -What would you like to do about it ? Your options are:^M - Y or I : install the package maintainer's version^M - N or O : keep your currently-installed version^M - D : show the differences between the versions^M - Z : start a shell to examine the situation^M - The default action is to keep your current version.^M + ==> Deleted (by you or by a script) since installation.^M + ==> Package distributor has shipped an updated version.^M + What would you like to do about it ? Your options are:^M + Y or I : install the package maintainer's version^M + N or O : keep your currently-installed version^M + D : show the differences between the versions^M + Z : start a shell to examine the situation^M + The default action is to keep your current version.^M *** mary-generic.conf (Y/I/N/O/D/Z) [default=N] ? n^M Installing new version of config file /etc/speech-dispatcher/modules/swift-generic.conf ...^M Installing new version of config file /etc/speech-dispatcher/speechd.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/mary-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/espeak-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/pico-generic.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ivona.conf ...^M speech-dispatcherd.service is a disabled or a static unit not running, not starting it.^M Removing obsolete conffile /etc/speech-dispatcher/modules/baratinoo.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/ibmtts.conf ...^M Removing obsolete conffile /etc/speech-dispatcher/modules/kali.conf ...^M -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1981611 Title: conf file prompt during upgrade from Focal to Jammy Status in speech-dispatcher package in Ubuntu: Fix Committed Bug description: * Impact A conffile prompt is displayed on upgrade * Test Case upgrade speech-dispatcher from the focal to the jammy-proposed version, there should be no conffile prompt * Regression potential the change only remove a .mainscript line to remove the conffile, if the change was incorrect the prompt could still be there or a an old conffile could be not removed on upgrade - I was performing a distribution upgrade of an Ubuntu Desktop install of Ubuntu 20.04 to Ubuntu 22.04 when I encountered a debconf prompt regarding a speech-dispatcher config file which I had not modified. From /var/log/dist-upgrade/apt-term.log: Setting up speech-dispatcher (0.11.1-1) ...^M Installing new version of config file /etc/speech-dispatcher/modules/cicero.conf ...^M Installing new version of config file /etc/speech-dispatcher/modules/dtk-generic.conf ...^M Installing new version of config file
[Desktop-packages] [Bug 1981966] Re: [SRU] libreoffice 7.3.5 for jammy
Hello Rico, or anyone else affected, Accepted libreoffice into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.5-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1981966 Title: [SRU] libreoffice 7.3.5 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release * Version 7.3.4 is currently released in jammy. For a list of fixed bugs compared to 7.3.4 see the list of bugs fixed in the release candidates of 7.3.5 (that's a total of 83 bugs): https://wiki.documentfoundation.org/Releases/7.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1797/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220719_091411_74233@/log.gz * [arm64] ... * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220719_110142_388ca@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220719_082728_0b9aa@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220719_080609_7c067@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 83 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings
Hi Łukasz, For some reason I am unable to install the update. It was kept back, when I ran `sudo apt upgrade` and when I try to explicitly install it I get this: karol@kolatek ~ $ sudo apt list --upgradable Listing... Done gnome-control-center/jammy-proposed 1:41.7-0ubuntu0.22.04.3 amd64 [upgradable from: 1:41.7-0ubuntu0.22.04.1] N: There are 3 additional versions. Please use the '-a' switch to see them. karol@kolatek ~ $ sudo apt install gnome-control-center 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: libfreerdp-server2-2 : Depends: libfreerdp2-2 (= 2.6.1+dfsg1-3ubuntu2.1) but 2.6.1+dfsg1-3ubuntu2.2 is to be installed E: Unable to correct problems, you have held broken packages. karol@kolatek ~ $ -- 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/1968213 Title: Icon theme reverts to Yaru when entering Appearance settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: [ Impact ] I upgraded to the 22.04 beta last week from 21.10. I use a custom icon theme. Whenever I enter the Appearance tab in settings the icon theme is set back to Yaru. [ Test case(s) ] 1. Run gsettings set org.gnome.desktop.interface gtk-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu User theme settings should have not changed (Adwaita is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The icon theme is still reset if changed externally while the appearance panel is open. -- 1. Run gsettings set org.gnome.desktop.interface icon-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu Icon theme settings should have not changed (Adwaita icon theme is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The theme is still reset if changed externally while the appearance panel is open. -- 1. From Gedit settings, select an editor color scheme that is not Yaru or Yaru-dark. 2. Start Settings Appearance panel: gnome-control-center ubuntu Gedit theme should not have changed 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Does not change the Gedit theme, unless a Yaru variant is selected as gedit color scheme. [ Regression Potential ] Theme is not updated to upgraders that use some unsupported custom themes. Theme selection doesn't work in some custom configurations. --- ProblemType: BugDistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 20:47:41 2022 InstallationDate: Installed on 2022-02-02 (64 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)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/1968213/+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 1970449] Re: GPG keys are not shown in Software and Updates
** Also affects: software-properties (Ubuntu Kinetic) Importance: Low Status: Confirmed ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: fr-2565 ** Tags removed: fr-2565 rls-jj-incoming -- 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/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Confirmed Status in software-properties source package in Jammy: New Status in software-properties source package in Kinetic: Confirmed Bug description: software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1981966] Re: [SRU] libreoffice 7.3.5 for jammy
I see kinetic is still on rc2, but I suppose this is only temporary. -- 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/1981966 Title: [SRU] libreoffice 7.3.5 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release * Version 7.3.4 is currently released in jammy. For a list of fixed bugs compared to 7.3.4 see the list of bugs fixed in the release candidates of 7.3.5 (that's a total of 83 bugs): https://wiki.documentfoundation.org/Releases/7.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1797/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220719_091411_74233@/log.gz * [arm64] ... * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220719_110142_388ca@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220719_082728_0b9aa@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220719_080609_7c067@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 83 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981966/+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 1982494] [NEW] package libgl1-mesa-dri 22.0.1-1ubuntu2 failed to install/upgrade: unable to make backup link of './usr/lib/x86_64-linux-gnu/dri/crocus_dri.so' before installing
Public bug reported: Errors were encountered while processing: /tmp/apt-dpkg-install-LWXYKW/08-libgl1-mesa-dri_22.0.1-1ubuntu2.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CasperVersion: 1.470 CompositorRunning: None Date: Thu Jul 21 15:12:11 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/x86_64-linux-gnu/dri/crocus_dri.so' before installing new version: Input/output error GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39f1] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 80SV ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: mesa Title: package libgl1-mesa-dri 22.0.1-1ubuntu2 failed to install/upgrade: unable to make backup link of './usr/lib/x86_64-linux-gnu/dri/crocus_dri.so' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2016 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 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 510-15IKB dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvr3JCN23WW:bd11/10/2016:br1.23:efr1.23:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB:skuLENOVO_MT_80SV_BU_idea_FM_Lenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.sku: LENOVO_MT_80SV_BU_idea_FM_Lenovo ideapad 510-15IKB dmi.product.version: Lenovo ideapad 510-15IKB 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.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-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 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy ubuntu -- 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/1982494 Title: package libgl1-mesa-dri 22.0.1-1ubuntu2 failed to install/upgrade: unable to make backup link of './usr/lib/x86_64-linux- gnu/dri/crocus_dri.so' before installing new version: Input/output error Status in mesa package in Ubuntu: New Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-LWXYKW/08-libgl1-mesa-dri_22.0.1-1ubuntu2.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CasperVersion: 1.470 CompositorRunning: None Date: Thu Jul 21 15:12:11 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/x86_64-linux-gnu/dri/crocus_dri.so' before installing new version: Input/output error GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39f1] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 80SV ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- Python3Details: /usr/bin/python3.10,
[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
** Changed in: modemmanager (Ubuntu) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu) Status: New => Triaged -- 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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1981881] Re: Firefox snap broken in Guest Account
It was also recently discussed on https://discourse.ubuntu.com/t/known- issues-with-firefox-snap/24663/88 ** Changed in: firefox (Ubuntu) Importance: Undecided => Low -- 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/1981881 Title: Firefox snap broken in Guest Account Status in firefox package in Ubuntu: New Bug description: My laptop is sometimes used by visitors. They want to browse the internet. So I setup the guest-account. I found out that the Firefox snap is broken on guest-accounts. When opening Firefox nothing happens. When starting FF from the command line of the guest-account I found out the following: $ firefox 2022/07/12 00:46:01.906615 tool_linux.go:82: cannot open snapd info file “/snap/snapd/current/usr/lib/snapd/info”: open /snap/snapd/current/usr/lib/snapd/info: permission denied Version information: Guest Account on Xubuntu 22.04 (Jammy) FF version: 102.0.1 (64-bit) Mozilla Firefox Snap for Ubuntu canonical-002-1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981881/+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 1981881] Re: Firefox snap broken in Guest Account
That looks like https://bugzilla.mozilla.org/show_bug.cgi?id=1757195. ** Bug watch added: Mozilla Bugzilla #1757195 https://bugzilla.mozilla.org/show_bug.cgi?id=1757195 -- 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/1981881 Title: Firefox snap broken in Guest Account Status in firefox package in Ubuntu: New Bug description: My laptop is sometimes used by visitors. They want to browse the internet. So I setup the guest-account. I found out that the Firefox snap is broken on guest-accounts. When opening Firefox nothing happens. When starting FF from the command line of the guest-account I found out the following: $ firefox 2022/07/12 00:46:01.906615 tool_linux.go:82: cannot open snapd info file “/snap/snapd/current/usr/lib/snapd/info”: open /snap/snapd/current/usr/lib/snapd/info: permission denied Version information: Guest Account on Xubuntu 22.04 (Jammy) FF version: 102.0.1 (64-bit) Mozilla Firefox Snap for Ubuntu canonical-002-1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981881/+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 1969303] Re: "No package to remove" error when attempting to uninstall
Test run: * With old version (41.5), under "install" tab attempted to uninstall package "0ad" * Error message "no package to remove" given * Ran `which 0ad` which exited with return code 0 * Installed proposed package (41.5-2ubuntu2) * Rebooted machine * Under "install" tab attempted to uninstall package "0ad" * Prompted for confirmation and password * Application removed from list of installed packages * `which 0ad` exits with error code 1 (command non-existent or not executable) * `apt list 0ad` not showing `[installed]` or `[auto]` or `[manual]`. * Install application "2048" (source deb) * Removed application "2048" * Attempt to locate a package with a snap source **failed** * Attempt to remove package with a snap source **failed** (no packages listed with snap sources, including some I know I installed previously). * Downgraded gnome-software and gnome-software-common to 41.5-2 * Attempt to locate a package with a snap source **failed** * Attempt to remove package with a snap source **failed** (no packages listed with snap sources, including some I know I installed previously). Unfortunately, I did not check if I could uninstall snaps before doing the upgrade. However, there are snaps installed that I must have done through gnome-software, that I can now no longer see or remove. As such, I cannot in good faith tag this verification-done-jammy. However, the bug mentioned is passed so I'm not sure if I should label it verification-failed-jammy. I'd suggest future testers check explicitly that they can see, install and remove snap packages before and after the upgrade, and wouldn't mind if someone verifies this for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall Status in GNOME Software: Fix Released Status in snap-store-desktop: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Jammy: Fix Committed Bug description: [Impact] * The Ubuntu repository version of gnome-software in 22.04 does not allow a user to uninstall an application. For new users this could be be construed as disconcerting allowing only installing apps without the ability to remove those apps later if required. This SRU is applicable only to the gnome-software application installed from the repository and not the branded ubuntu-store snap that is the default in Ubuntu (but not in flavours such as Ubuntu Budgie) This fix for gnome-software has been backported from the v41 version of ubuntu's snap-store. The fixed software now checks for the status of a deb package installed - either manually installed or automatically as part of a distro install. Previously this check was not done and gnome-software defaulted to not allowing the package to be uninstalled. The new status check allows gnome-software to evaluate that the package can be uninstalled. [Test Plan] * Choose a package from the installed list in gnome-software. Click the trash icon. Note the error message that the package cannot be removed. * install gnome-software from the proposed repository. Logout and login. Repeat the trash icon click step above. This time the package can be removed. Confirm via either your distro menu or searching in GNOME Overview (if you are using gnome-software from the repository) that the application has been successfully removed. * Perform additional testing such as installing applications from the repository (change the source to "Ubuntu (deb)") and then deleting the application. * Perform additional testing such as installing applications from the snap repository (change the source to "Snap") and then deleting the application. [Where problems could occur] * The code changed is specific to 'packagekit' repos i.e. debian based repos. Thus it is sensitive to possible regressions when installing & removing apps. * The patch itself is well tested since it was backported to the ubuntu snap-store several weeks ago and has been rolled out. No adverse issues has been reported. * The risk would be that there could be additional changes to the snap-store that was not incorporated in gnome-software possibly producing different results. * The additional regression tests in the Test Plan will reveal this. [Other Info] * There is no need to backport this to Kinetic since a revised version of the patch has been upstreamed (GNOME Team) and is in the kinetic version. On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any application If you want to uninstall a software, there is
[Desktop-packages] [Bug 1982340] Re: Clients of the WebExtensions portal see the FDs as closed when the portal is used for the first time
Successfully tested xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1 from jammy-proposed using the test plan in the bug description, in a clean and up-to-date jammy amd64 VM. I first reproduced the problem without the update from jammy-proposed, then installed the updated xdg-desktop-portal and reverted to a pristine state by deleting ~/.local/share/flatpak/db/webextensions and ~/snap/firefox, and rebooting the machine. After enabling the chrome- gnome-shell extension, it worked OOTB without the need to restart the portal. ** 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 xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1982340 Title: Clients of the WebExtensions portal see the FDs as closed when the portal is used for the first time Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Jammy: Fix Committed Bug description: [Impact] * Without this patch, the WebExtensions portal won't allow native connectors to communicate with a browser the first time they are spawned by the portal. Closing and restarting the browser won't do, only killing the portal and letting it restart. * This patch is being backported to jammy as this is currently the primary target for the effort of enabling native messaging in the firefox snap (not widely available yet, but the portal is available in jammy, and once the firefox implementation lands in the snap, we want this to work seamlessly). * The patch is trivial, it adds a missing variable initialization, which fixes the problem. [Test Plan] * Steps to reproduce the bug: - in a fully up-to-date jammy VM, install the chrome-gnome-shell package, and download and side-load the latest test snap from https://launchpad.net/~osomon/+snap/firefox-native-messaging (because the firefox implementation hasn't landed upstream yet) - if it exists, delete ~/.local/share/flatpak/db/webextensions and reboot to ensure a pristine state - run the firefox snap, browse to https://addons.mozilla.org/firefox/addon/gnome-shell-integration/, and click the "Add to Firefox" blue button - accept the firefox prompt to install the extension - you will soon be prompted by GNOME Shell (with a modal dialog) to allow firefox to use the WebExtensions portal to start the native connector, click "Allow" - browse to https://extensions.gnome.org/local/ - without the patch, you'll get a message that "an unexpected error occurred" - with the patch, firefox is able to talk to the native connector and displays a page with the currently installed GNOME Shell extensions * Note that this can also be tested with another extension that uses native messaging to talk to a native connector on the system, e.g. https://github.com/keepassxreboot/keepassxc-browser [Where problems could occur] * The patch is trivial and it's hard to imagine that initializing an uninitialized variable could have undesirable side effects. * In any case, the WebExtensions portal isn't currently used by any piece of software (this is being tested for firefox but isn't merged and therefore not widely available yet), so possible side effects wouldn't be noticed until the native messaging portal support lands in the firefox snap (see https://phabricator.services.mozilla.com/D140803). [Other Info] * We are still hoping to get the native messaging portal support in the firefox snap in time for Ubuntu 22.04.1, so for it to be a seamless experience this patch needs to land for the .1 release too. [Original Description] (this was initially reported here: https://github.com/flatpak/xdg- desktop-portal/pull/705#issuecomment-1123392120) When testing the WebExtensions portal against the only known client so far (firefox snap + the corresponding upstream patch https://phabricator.services.mozilla.com/D140803), I'm consistently seeing the following problem: the first time the user is prompted for authorization and accepts, the portal will spawn the native connector and pass the file descriptors to the client (firefox snap), but the client sees the file descriptors as closed. Closing the client and re- opening it doesn't help. Only when the portal is terminated and restarted does communication through FDs start working normally. It turns out this is caused by a missing variable initialization, which is trivially fixed by https://github.com/jhenstridge/xdg- desktop-portal/pull/2. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.4-1ubuntu1~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1
[Desktop-packages] [Bug 1971608] Re: Firefox PDF font rendering is often messed up
The issue is being discussed on https://github.com/ubuntu/gnome- sdk/issues/49 now, one workaround is to do $ mkdir ~/snap/firefox/current/.config/fontconfig/conf.d; cp /etc/fonts/conf.d/* ~/snap/firefox/current/.config/fontconfig/conf.d ** Bug watch added: github.com/ubuntu/gnome-sdk/issues #49 https://github.com/ubuntu/gnome-sdk/issues/49 -- 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/1971608 Title: Firefox PDF font rendering is often messed up Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I don't know whether it is an ubuntu bug or a firefox bug but since I am running the mozilla-supported ubuntu snap of firefox 99.0.1 (on 22.04 jammy) (firefox 100 not yet available on snap), posting it here. Many pdfs have messed-up fonts on this firefox. Following a reddit thread, I tried disabling browser.display.use_document_fonts in about:config. Then the pdfs render correctly, but html webpages have messed-up fonts. Reddit post with screenshots and sample URL here; previous reddit thread linked therein. https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/ Others (on this and previous thread) report it doesn't happen on other platforms. On this thread, someone confirms it on a Ubuntu VM, and someone else says it doesn't happen on Mint (based on Ubuntu but I think doesn't use snaps). To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 387957] Re: Improve Save As Dialog Box (focus issues)
The file-chooser dialog as descripted in comment No. 43 bothers me since I updated to Jammy. It's not the state of art and workflow. Glad I found this place to urgently beg for a change. I will try the solutions offered in comments 41 and 42. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/387957 Title: Improve Save As Dialog Box (focus issues) Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: The save dialog box has the irritating habit of not focusing on the file name area once I have browsed to the location where I would like to save my document. This is done better in Windows. There are two main scenarios when saving a document where this behaviour annoys: Scanario 1 - Browsing to save location by double-clicking: 1. File -> Save As (to bring up the "Save" dialog box). 2. Double click on the folder in which you would like to save the document. 3. Notice that the focus is now in the folder list area, not on the file name area. 4. I now have to click in the file name area to be able to name my document. In Windows, the focus is returned immediately to the file name box once a folder is double clicked, so the name can be typed and the document saved in one step. Scenario 2 - Browsing save location using the keyboard (find as you type): 1. File -> Save As (to bring up the "Save" dialog box). 2. Click on the folder area so that folder names can be typed to find them. Hit enter to enter desired folder. 3. Within the folder, step 2 can be repeated for subfolders indefinitely. 4. Once the desired location has been reached, the user must use the mouse click in the file name area to name the file before saving. In Windows, when using find as you type, although focus is retained by the folder area when entering a lower folder level (so that you can browse to another level using the keyboard if desired), jumping to the file name box is simply a matter of pressing tab ONCE. In Ubuntu, I have to reverse tab (shift-tab) around 10 times to get back to the file name box at the top of the screen, or use the mouse - most annoying. Solutions (copy the Windows behaviour): 1. If a folder is double clicked with the mouse, the focus should jump back to the file name box. 2. If a folder is entered into by pressing enter (on the keyboard), focus should remain in the folder area, but the file name box should only be a single tab away. I understand that solution 2 is problematic in that tabbing would ordinarily jump to the next element (usually the "file type" dropdown), not back to the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248174] Re: Update the Ubuntu colour palette to fit the spec
I no longer use Ubuntu. You will need to check it out yourself. -- 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/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Incomplete Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+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 1977663] Re: Remote Control under Remote Desktop sharing option only works for VNC
Hello Marco, or anyone else affected, Accepted gnome-control-center into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:41.7-0ubuntu0.22.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1977663 Title: Remote Control under Remote Desktop sharing option only works for VNC Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: [ Impact ] Toggling "Remote Control" doesn't apply the value to the RDP service [ Test case 1] 0. Install the updated gnome-control-center packages. 1. Open the Settings app 2. In the left sidebar, choose Sharing. 3. Turn on sharing in the top bar of the app the click Remote Desktop 4. Turn on Remote Desktop 5. Turn on "Enable Legacy VNC Protocol" 6. Turn on Remote Control 7. Open a terminal and run grdctl status View-only: No and Status: enabled should show for both RDP and VNC. [ Test case 2] Complete Test Case 1. Then From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. Just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the RDP connection works and that you can remotely control the first computer from the second computer. Disconnect. Then reconnect but switch the protocol in Remmina to VNC So something like: VNC jeremy@192.168.1.1 Ensure that the VNC connection works and that you can remotely control the first computer from the second computer. [ Regression Potential ] Remote control setting does not work for VNC, changing settings manually from gsettings isn't immediately reflected by the UI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1977663/+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 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings
Hello Karol, or anyone else affected, Accepted gnome-control-center into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:41.7-0ubuntu0.22.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1968213 Title: Icon theme reverts to Yaru when entering Appearance settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: [ Impact ] I upgraded to the 22.04 beta last week from 21.10. I use a custom icon theme. Whenever I enter the Appearance tab in settings the icon theme is set back to Yaru. [ Test case(s) ] 1. Run gsettings set org.gnome.desktop.interface gtk-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu User theme settings should have not changed (Adwaita is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The icon theme is still reset if changed externally while the appearance panel is open. -- 1. Run gsettings set org.gnome.desktop.interface icon-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu Icon theme settings should have not changed (Adwaita icon theme is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The theme is still reset if changed externally while the appearance panel is open. -- 1. From Gedit settings, select an editor color scheme that is not Yaru or Yaru-dark. 2. Start Settings Appearance panel: gnome-control-center ubuntu Gedit theme should not have changed 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Does not change the Gedit theme, unless a Yaru variant is selected as gedit color scheme. [ Regression Potential ] Theme is not updated to upgraders that use some unsupported custom themes. Theme selection doesn't work in some custom configurations. --- ProblemType: BugDistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 20:47:41 2022 InstallationDate: Installed on 2022-02-02 (64 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)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/1968213/+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 1980606] Please test proposed package
Hello David, or anyone else affected, Accepted gnome-control-center into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:41.7-0ubuntu0.22.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1980606 Title: gnome-control-centre crashes after enabling "Sharing" Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Jammy: Fix Committed Bug description: Impact -- gnome-control-center uses gsettings schemas from the gnome-remote-desktop package without being able to handle if those schemas are not installed. Because gnome-control-center keeps track of which page was last opened, it's not possible to simply ignore the Sharing page, a user would need to manually open the Settings app to a different page or else the Settings app won't run at all. ubuntu-desktop and gnome-shell already Recommend gnome-remote-desktop so most people won't experience this issue. Test Case - sudo apt remove gnome-remote-desktop Run gnome-control-center From the left sidebar, click Sharing (The app crashes) Install the update. The update will install gnome-remote-desktop. Run gnome-control-center The app should work like normal What Could Go Wrong --- This only adds a hard dependency on gnome-remote-desktop. Without this fix, the Sharing panel didn't work at all. Original Bug Report --- After the crash, gnome-control-centre fails to launch again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Jul 3 20:39:04 2022 InstallationDate: Installed on 2017-05-24 (1866 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-05-31 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1980606/+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 1980606] Re: gnome-control-centre crashes after enabling "Sharing"
It's hard for me to check: is this already released for kinetic? Since the bug status says Fix Committed there. ** Changed in: gnome-control-center (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1980606 Title: gnome-control-centre crashes after enabling "Sharing" Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Jammy: Fix Committed Bug description: Impact -- gnome-control-center uses gsettings schemas from the gnome-remote-desktop package without being able to handle if those schemas are not installed. Because gnome-control-center keeps track of which page was last opened, it's not possible to simply ignore the Sharing page, a user would need to manually open the Settings app to a different page or else the Settings app won't run at all. ubuntu-desktop and gnome-shell already Recommend gnome-remote-desktop so most people won't experience this issue. Test Case - sudo apt remove gnome-remote-desktop Run gnome-control-center From the left sidebar, click Sharing (The app crashes) Install the update. The update will install gnome-remote-desktop. Run gnome-control-center The app should work like normal What Could Go Wrong --- This only adds a hard dependency on gnome-remote-desktop. Without this fix, the Sharing panel didn't work at all. Original Bug Report --- After the crash, gnome-control-centre fails to launch again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Jul 3 20:39:04 2022 InstallationDate: Installed on 2017-05-24 (1866 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-05-31 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1980606/+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 1982343] Re: Cannot parse policy entries with unsupported types
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1982343 Title: Cannot parse policy entries with unsupported types Status in adsys package in Ubuntu: New Status in adsys source package in Focal: New Status in adsys source package in Jammy: New Bug description: [Impact] Policies with unsupported types are currently unable to be parsed. Even if Ubuntu doesn't support these types we should still be able to parse the Microsoft ones - otherwise we are unable to apply any of the GPOs. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu supports a limited subset of types, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982343/+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 1982347] Re: Username is case sensitive when applying policies on login
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1982347 Title: Username is case sensitive when applying policies on login Status in adsys package in Ubuntu: New Status in adsys source package in Focal: New Status in adsys source package in Jammy: New Bug description: [Impact] When logging in (either via login or ssh) to an AD account using different case combinations, adsysd uses the specified account name instead of the lowercase one reported by getent/whoami to apply the GPOs. I believe this comes from the pam_get_item call here: https://github.com/ubuntu/adsys/blob/e3316e5e37970a07f09fa6df553ddac096c91255/pam/pam_adsys.c#L266 This works but has the unintended side effect of producing multiple dconf profile files for each variant of the username, and caching policies as well: root@ubuntu2204:~# ls /etc/dconf/profile/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz root@ubuntu2204:~# ls /var/cache/adsys/policies/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz Of course this all stems from the username retrieved by PAM so there might be more unintended side-effects, the dconf one being the easiest to observe. To ensure an unified experience, when a target name is normalized from e.g. DOMAIN\User to User@DOMAIN, it will also be lowercased. [Test Plan] Reproduction: * With adsys set up, log in on the Ubuntu client using an AD account, alternating cases * Observe multiple files created at /var/cache/adsys/policies With the fix applied, remove *all* cached policies at /var/cache/adsys/policies and attempt to login with different case combinations of the AD account, e.g.: administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz As root, check the contents of /var/cache/adsys/policies - you should only see a lowercase entry: administra...@warthogs.biz [Where problems could occur] Target name normalization is exercised by the code that dumps policies applied for a given user, and by the code that updates or creates a policy for a given user. If this happens to cause a bug, it will render the core part of adsys unusable. We believe this is highly unlikely given that in some cases, adsys already used the lowercase variant of the username to apply and display policies. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982347/+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 1982345] Re: Cannot parse policy entries with no data
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1982345 Title: Cannot parse policy entries with no data Status in adsys package in Ubuntu: New Status in adsys source package in Focal: New Status in adsys source package in Jammy: New Bug description: [Impact] The Default Domain Policy for Computers has a bunch of SystemCertificates keys with no data which adsys fails to parse. Here are some examples: Software\Policies\Microsoft\SystemCertificates\ACRS\Certificates Software\Policies\Microsoft\SystemCertificates\ACRS\CRLs Software\Policies\Microsoft\SystemCertificates\ACRS\CTLs Software\Policies\Microsoft\SystemCertificates\CA\Certificates Software\Policies\Microsoft\SystemCertificates\CA\CRLs Software\Policies\Microsoft\SystemCertificates\CA\CTLs Software\Policies\Microsoft\SystemCertificates\Disallowed\Certificates Software\Policies\Microsoft\SystemCertificates\Disallowed\CRLs Software\Policies\Microsoft\SystemCertificates\Disallowed\CTLs Software\Policies\Microsoft\SystemCertificates\DPNGRA\Certificates When examined with a hex editor, these look like the following: : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. The last field of the [key;value;type;size;data] stanza is entirely empty (semicolon succeeded immediately by a closing brace) whereas we expect a null character. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not have policy entries with no data, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy for Computers on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/384 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982345/+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 1982349] Re: Manage energy profile settings
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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/1982349
Title:
Manage energy profile settings
Status in adsys package in Ubuntu:
New
Status in adsys source package in Focal:
New
Status in adsys source package in Jammy:
New
Bug description:
[Impact]
Adsys cannot currently manage GSettings power management keys, such
as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/settings-daemon/plugins/power/lid-close-ac-action
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
/org/gnome/settings-daemon/plugins/power/power-button-action
/org/gnome/settings-daemon/plugins/power/power-saver-profile-on-low-battery
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
[Test Plan]
* Open the Group Policy Management Editor for a configured policy
* Navigate to Computer Configuration > Administrative Templates > Ubuntu >
Client management > Power Management
* Double click on the last entry: Whether to hibernate ...
* Enable it, set the value to "hibernate"
* On a client with adsys, while connected on an AD account, run sudo adsysctl
update -m -vv
* Observe the logs that indicate the parsing of the dconf key:
DEBUG Analyzing entry
{Key:org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
Value:hibernate Disabled:false Meta:s Strategy: Err:}
* Observe the output of the following command (it should print 'hibernate'):
gsettings get org.gnome.settings-daemon.plugins.power
sleep-inactive-battery-type
[Where problems could occur]
This code is located in the dconf policy application manager and
restricted to it. The negative impact in case of a new bug will be
seen by gsettings key not being applied.
[Other Info]
This issue was initially reported on GitHub at
https://github.com/ubuntu/adsys/issues/135
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982349/+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 1982348] Re: Describe if a key requires an Ubuntu Pro subscription
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1982348 Title: Describe if a key requires an Ubuntu Pro subscription Status in adsys package in Ubuntu: New Status in adsys source package in Focal: New Status in adsys source package in Jammy: New Bug description: [Impact] Before applying policies, adsys checks for the existence of an Ubuntu Pro subscription. If not found, all keys with the exception of dconf keys are filtered, as they require Ubuntu Pro. Annotate the generated ADMX/ADML files with this information. [Test Plan] * Open the Group Policy Management Editor * Navigate to User Configuration > Administrative Templates > Ubuntu > Session Management > User Scripts > Logoff scripts * The description should contain the following line: An Ubuntu Pro subscription on the client is required to apply this policy. [Where problems could occur] This is a purely visual change that only impacts generated XML files. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/377 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982348/+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 1982351] Re: [SRU] Backport adsys-windows binary package
** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: adsys (Ubuntu) Status: New => Fix Released -- 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/1982351 Title: [SRU] Backport adsys-windows binary package Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: New Bug description: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] * adsys-windows is a new binary package. Impact is thus only for people installing. * This is a enterprise feature requested by desktop customers running LTS. [Test Plan] 1. Install the adsys-windows package 2. Copy the adwatchd.exe executable from /usr/share/adsys/windows on a Windows machine and run it: 3. Set a path where the configuration file will be written 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the root of the watched directory. If a GPT.INI is not found, the daemon will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982351/+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 1982330] Re: Cannot apply policies from uppercase class path like "MACHINE"
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1982330
Title:
Cannot apply policies from uppercase class path like "MACHINE"
Status in adsys package in Ubuntu:
New
Status in adsys source package in Focal:
New
Status in adsys source package in Jammy:
New
Bug description:
[Impact]
ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed
folders. adsysctl expects the folders to be title cased (e.g.
Machine), but they are uppercase (e.g. MACHINE). This prevents any
GPOs from being applied.
This is a common occurence with GPOs created by Microsoft, like the
Default Domain Policy.
[Test Plan]
Reproduction:
* Mark the Default Domain Policy as active for the client, and set some
Ubuntu policy entries.
* Restart and/or manually sync the client machine.
* Observe the log message indicating that parsing the GPO failed:
Policy "Default Domain Policy" doesn't have any policy for class
"user" open
/var/cache/adsys/sysvol/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/User/Registry.pol:
no such file or directory
* Observe that the Ubuntu policies were not applied.
To confirm the bug is fixed, repeat the steps above after applying the
fix, and the policies should be applied.
[Where problems could occur]
* Fixing this bug will allow adsys to parse, and possibly fail when
applying policies from an uppercase path, whereas before it silently
ignored them. Fixes for these potential bugs have also been submitted.
[Other Info]
The issue was initially reported on GitHub:
https://github.com/ubuntu/adsys/issues/346
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982330/+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 1982342] Re: Cannot parse policies with empty values
** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New -- 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/1982342 Title: Cannot parse policies with empty values Status in adsys package in Ubuntu: New Status in adsys source package in Focal: New Status in adsys source package in Jammy: New Bug description: [Impact] In addition to empty data, some Microsoft policy entries happen to have empty values as well. See the following entry: // [key;value;type;size;data] : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. This fails hard when parsing, returning an `empty value` error, rendering the remaining policies unparsable. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not support policy entries with empty values, we must still be able to parse them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982342/+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 1248174] Re: Update the Ubuntu colour palette to fit the spec
Is there an Ubuntu color palette in any Ubuntu release under standard support (18.04 or later, including Kinetic)? ** Changed in: gimp (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Incomplete Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+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 1969303] Re: "No package to remove" error when attempting to uninstall
Hello frenchy82, or anyone else affected, Accepted gnome-software into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/41.5-2ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-software (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall Status in GNOME Software: Fix Released Status in snap-store-desktop: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Jammy: Fix Committed Bug description: [Impact] * The Ubuntu repository version of gnome-software in 22.04 does not allow a user to uninstall an application. For new users this could be be construed as disconcerting allowing only installing apps without the ability to remove those apps later if required. This SRU is applicable only to the gnome-software application installed from the repository and not the branded ubuntu-store snap that is the default in Ubuntu (but not in flavours such as Ubuntu Budgie) This fix for gnome-software has been backported from the v41 version of ubuntu's snap-store. The fixed software now checks for the status of a deb package installed - either manually installed or automatically as part of a distro install. Previously this check was not done and gnome-software defaulted to not allowing the package to be uninstalled. The new status check allows gnome-software to evaluate that the package can be uninstalled. [Test Plan] * Choose a package from the installed list in gnome-software. Click the trash icon. Note the error message that the package cannot be removed. * install gnome-software from the proposed repository. Logout and login. Repeat the trash icon click step above. This time the package can be removed. Confirm via either your distro menu or searching in GNOME Overview (if you are using gnome-software from the repository) that the application has been successfully removed. * Perform additional testing such as installing applications from the repository (change the source to "Ubuntu (deb)") and then deleting the application. * Perform additional testing such as installing applications from the snap repository (change the source to "Snap") and then deleting the application. [Where problems could occur] * The code changed is specific to 'packagekit' repos i.e. debian based repos. Thus it is sensitive to possible regressions when installing & removing apps. * The patch itself is well tested since it was backported to the ubuntu snap-store several weeks ago and has been rolled out. No adverse issues has been reported. * The risk would be that there could be additional changes to the snap-store that was not incorporated in gnome-software possibly producing different results. * The additional regression tests in the Test Plan will reveal this. [Other Info] * There is no need to backport this to Kinetic since a revised version of the patch has been upstreamed (GNOME Team) and is in the kinetic version. On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any application If you want to uninstall a software, there is an error message : "no package to remove" No problem to uninstall this same software with synaptic for example To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1248174] Re: Update the Ubuntu colour palette to fit the spec
In the palettes tab there was an Ubuntu color palette. ** Changed in: gimp (Ubuntu) Status: Incomplete => Triaged -- 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/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Triaged Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+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 1982477] [NEW] UI does not work with Linux version 5.15.0-41
Public bug reported: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/1982477 Title: UI does not work with Linux version 5.15.0-41 Status in gdm3 package in Ubuntu: New Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1982477/+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 1982472] [NEW] Support A+N platform
Public bug reported: The 'Power Saving Mode' of Nvidia app should change to ATI when the integrated graphic is Advanced Micro Devices. [Steps to reproduce] 1. Install the OEM image 2. Boot and log 3. 'Dash' -> 'Nvidia Settings' 4. Verify the 'PRIME Profiles' [Expected result] Nvidia (Performance Mode) Nvidia On-Demand AMD (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query [Actual result] Nvidia (Performance Mode) Nvidia On-Demand Intel (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|intel|on-demand|query [Failure rate] 100% [Other Information] ubuntu 22.04 nvidia-prime 0.8.17.1 nvidia-settings 510.47.03-0ubuntu1 nvidia-driver 510.73.05-0ubuntu0.22.04.1 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1981179 sutton ** Tags added: oem-priority originate-from-1981179 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1982472 Title: Support A+N platform Status in OEM Priority Project: New Status in nvidia-prime package in Ubuntu: New Bug description: The 'Power Saving Mode' of Nvidia app should change to ATI when the integrated graphic is Advanced Micro Devices. [Steps to reproduce] 1. Install the OEM image 2. Boot and log 3. 'Dash' -> 'Nvidia Settings' 4. Verify the 'PRIME Profiles' [Expected result] Nvidia (Performance Mode) Nvidia On-Demand AMD (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query [Actual result] Nvidia (Performance Mode) Nvidia On-Demand Intel (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|intel|on-demand|query [Failure rate] 100% [Other Information] ubuntu 22.04 nvidia-prime 0.8.17.1 nvidia-settings 510.47.03-0ubuntu1 nvidia-driver 510.73.05-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1982472/+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 1981837] Re: Using DiNG triggers ubuntu-dock opacity
Please test: https://github.com/micheleg/dash-to-dock/pull/1767.patch If it works for you then I will get it merged upstream. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Patryk Skorupa (skoruppa) -- 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/1981837 Title: Using DiNG triggers ubuntu-dock opacity Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1981837/+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 1981837] Re: Using DiNG triggers ubuntu-dock opacity
I did not, but indeed that sounds like the right fix for dash-to-dock and ubuntu-dock. I've added a task tracking the bug in ubuntu-dock here. ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #230 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/230 ** Also affects: gnome-shell-extension-desktop-icons-ng via https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/230 Importance: Unknown Status: Unknown -- 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/1981837 Title: Using DiNG triggers ubuntu-dock opacity Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1981837/+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 1982463] Re: cheese - webcam image frozen
The following programs do not have problems with the streams: * Zoom - works with both my webcam and the Silvercrest Dia Scanner * MS Teams for Linux - works with the webcam * Webcamoid - works with both my webcam and the Silvercrest Dia Scanner -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] Re: cheese - webcam image frozen
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1949183 Is not the same as my problem. The video freezes, but I'm still able to take pictures. The application is responsive. When I add a second camera device (A silvercrest dia slide scanner), it results in the same problems. It also continually seems to be busy with adjusting the white-balance with this device. pinhole does not freeze, but is very slow and adjusting white-balance continually. When I switch between devices, the camera stream freezes, just like cheese. -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] lsusb.txt
apport information ** Attachment added: "lsusb.txt" https://bugs.launchpad.net/bugs/1982463/+attachment/5604527/+files/lsusb.txt -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1982463/+attachment/5604525/+files/ProcCpuinfoMinimal.txt -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] lspci.txt
apport information ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1982463/+attachment/5604526/+files/lspci.txt -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1982463/+attachment/5604524/+files/ProcCpuinfo.txt -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] Re: cheese - webcam image frozen
apport information ** Tags added: apport-collected gstreamer-error jammy ** Description changed: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-05-25 (56 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: Intel Corporation NUC6CAYH + Package: cheese 41.1-1build1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=nl_NL.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 + RelatedPackageVersions: + cheese41.1-1build1 + cheese-common 41.1-1build1 + Tags: jammy gstreamer-error + Uname: Linux 5.15.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/23/2017 + dmi.bios.release: 5.6 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 + dmi.board.name: NUC6CAYB + dmi.board.vendor: Intel Corporation + dmi.board.version: J23203-404 + dmi.chassis.type: 3 + dmi.chassis.vendor: Intel Corporation + dmi.chassis.version: 2 + dmi.ec.firmware.release: 20.0 + dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: + dmi.product.family: Intel NUC + dmi.product.name: NUC6CAYH + dmi.product.version: J26843-405 + dmi.sys.vendor: Intel Corporation ** Attachment added: "CheeseDebug.txt.gz" https://bugs.launchpad.net/bugs/1982463/+attachment/5604522/+files/CheeseDebug.txt.gz -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB
[Desktop-packages] [Bug 1982463] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1982463/+attachment/5604523/+files/Dependencies.txt -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] Re: cheese - webcam image frozen
Also please take a look at bug: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1949183 to see if this is your case -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] Re: cheese - webcam image frozen
Some extra output of apport-collect: (cheese:91412): cheese-WARNING **: 10:53:11.868: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Pijplijn gezet op gepauzeerd ... Pijplijn klaar en heeft PREROLL niet nodig... Pijplijn klaar met PREROLL ... Pijplijn gezet op afspelen ... New clock: pipewireclock1 FOUT: van element /GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir: Internal data stream error. Extra debug-informatie: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir: streaming stopped, reason not-negotiated (-4) Execution ended after 0:00:00.021758105 Pijplijn gezet op NULL ... Pijplijn wordt vrijgemaakt ... Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 719, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 637, in run_update_report self.crashdb.update(self.options.update_report, self.report, File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 382, in update report.write_mime(mime, skip_keys=skip_keys) File "/usr/lib/python3/dist-packages/problem_report.py", line 547, in write_mime f = open(v[0], 'rb') # file name FileNotFoundError: [Errno 2] Bestand of map bestaat niet: '.cache/CheeseDebug.txt' -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] Re: cheese - webcam image frozen
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1982463 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982463] [NEW] cheese - webcam image frozen
Public bug reported: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Movie of what happens" https://bugs.launchpad.net/bugs/1982463/+attachment/5604518/+files/IMG_0623.MOV -- 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/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1982347] Re: Username is case sensitive when applying policies on login
** Description changed: [Impact] When logging in (either via login or ssh) to an AD account using different case combinations, adsysd uses the specified account name instead of the lowercase one reported by getent/whoami to apply the GPOs. I believe this comes from the pam_get_item call here: https://github.com/ubuntu/adsys/blob/e3316e5e37970a07f09fa6df553ddac096c91255/pam/pam_adsys.c#L266 This works but has the unintended side effect of producing multiple dconf profile files for each variant of the username, and caching policies as well: root@ubuntu2204:~# ls /etc/dconf/profile/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz root@ubuntu2204:~# ls /var/cache/adsys/policies/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz Of course this all stems from the username retrieved by PAM so there might be more unintended side-effects, the dconf one being the easiest to observe. To ensure an unified experience, when a target name is normalized from e.g. DOMAIN\User to User@DOMAIN, it will also be lowercased. [Test Plan] - * Enable a dconf policy on the AD controller - * Log in with an AD account, alternating cases - * Observe multiple files created at /etc/dconf/profile and /var/cache/adsys/policies + Reproduction: + * With adsys set up, log in on the Ubuntu client using an AD account, alternating cases + * Observe multiple files created at /var/cache/adsys/policies + + With the fix applied, remove *all* cached policies at + /var/cache/adsys/policies and attempt to login with different case + combinations of the AD account, e.g.: + + administra...@warthogs.biz + administra...@warthogs.biz + administra...@warthogs.biz + administra...@warthogs.biz + + As root, check the contents of /var/cache/adsys/policies - you should + only see a lowercase entry: administra...@warthogs.biz + [Where problems could occur] - After login succeeds, an AD username is _always_ reported as lowercase - by the system, so there are no suspected side-effects of this change. + Target name normalization is exercised by the code that dumps policies + applied for a given user, and by the code that updates or creates a + policy for a given user. If this happens to cause a bug, it will render + the core part of adsys unusable. + + We believe this is highly unlikely given that in some cases, adsys + already used the lowercase variant of the username to apply and display + policies. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/378 -- 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/1982347 Title: Username is case sensitive when applying policies on login Status in adsys package in Ubuntu: New Bug description: [Impact] When logging in (either via login or ssh) to an AD account using different case combinations, adsysd uses the specified account name instead of the lowercase one reported by getent/whoami to apply the GPOs. I believe this comes from the pam_get_item call here: https://github.com/ubuntu/adsys/blob/e3316e5e37970a07f09fa6df553ddac096c91255/pam/pam_adsys.c#L266 This works but has the unintended side effect of producing multiple dconf profile files for each variant of the username, and caching policies as well: root@ubuntu2204:~# ls /etc/dconf/profile/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz root@ubuntu2204:~# ls /var/cache/adsys/policies/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz Of course this all stems from the username retrieved by PAM so there might be more unintended side-effects, the dconf one being the easiest to observe. To ensure an unified experience, when a target name is normalized from e.g. DOMAIN\User to User@DOMAIN, it will also be lowercased. [Test Plan] Reproduction: * With adsys set up, log in on the Ubuntu client using an AD account, alternating cases * Observe multiple files created at /var/cache/adsys/policies With the fix applied, remove *all* cached policies at /var/cache/adsys/policies and attempt to login with different case combinations of the AD account, e.g.: administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz As root, check the contents of /var/cache/adsys/policies - you should only see a lowercase entry: administra...@warthogs.biz [Where problems could occur] Target name normalization is exercised by the code that dumps policies applied for a given user, and by the code that updates or creates a policy for a given user. If this happens to cause a bug, it will
[Desktop-packages] [Bug 1982351] Re: [SRU] Backport adsys-windows binary package
** Description changed: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] * adsys-windows is a new binary package. Impact is thus only for people installing. - * This is a entreprise feature requested by desktop customers running LTS. + * This is a enterprise feature requested by desktop customers running LTS. [Test Plan] 1. Install the adsys-windows package - 2. Copy the adwatchd.exe executable on a Windows machine and run it: + 2. Copy the adwatchd.exe executable from /usr/share/adsys/windows on a Windows machine and run it: 3. Set a path where the configuration file will be written 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the root of the watched directory. If a GPT.INI is not found, the daemon will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. -- 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/1982351 Title: [SRU] Backport adsys-windows binary package Status in adsys package in Ubuntu: New Bug description: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] * adsys-windows is a new binary package. Impact is thus only for people installing. * This is a enterprise feature requested by desktop customers running LTS. [Test Plan] 1. Install the adsys-windows package 2. Copy the adwatchd.exe executable from /usr/share/adsys/windows on a Windows machine and run it: 3. Set a path where the configuration file will be written 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the root of the watched directory. If a GPT.INI is not found, the daemon will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982351/+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 1982349] Re: Manage energy profile settings
** Description changed:
[Impact]
Adsys cannot currently manage GSettings power management keys, such as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/settings-daemon/plugins/power/lid-close-ac-action
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
/org/gnome/settings-daemon/plugins/power/power-button-action
/org/gnome/settings-daemon/plugins/power/power-saver-profile-on-low-battery
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
[Test Plan]
- * Open the Group Policy Management Editor
+ * Open the Group Policy Management Editor for a configured policy
* Navigate to Computer Configuration > Administrative Templates > Ubuntu >
Client management > Power Management
- * Activate any of the entries
+ * Double click on the last entry: Whether to hibernate ...
+ * Enable it, set the value to "hibernate"
+ * On a client with adsys, while connected on an AD account, run sudo adsysctl
update -m -vv
+ * Observe the logs that indicate the parsing of the dconf key:
+
+ DEBUG Analyzing entry
{Key:org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
Value:hibernate Disabled:false Meta:s Strategy: Err:}
+ * Observe the output of the following command (it should print 'hibernate'):
gsettings get org.gnome.settings-daemon.plugins.power
sleep-inactive-battery-type
[Where problems could occur]
- This feature is additive and only impacts generated files that are used
- solely on Windows.
+ This code is located in the dconf policy application manager and
+ restricted to it. The negative impact in case of a new bug will be seen
+ by gsettings key not being applied.
[Other Info]
This issue was initially reported on GitHub at
https://github.com/ubuntu/adsys/issues/135
--
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/1982349
Title:
Manage energy profile settings
Status in adsys package in Ubuntu:
New
Bug description:
[Impact]
Adsys cannot currently manage GSettings power management keys, such
as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/settings-daemon/plugins/power/lid-close-ac-action
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
/org/gnome/settings-daemon/plugins/power/power-button-action
/org/gnome/settings-daemon/plugins/power/power-saver-profile-on-low-battery
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
[Test Plan]
* Open the Group Policy Management Editor for a configured policy
* Navigate to Computer Configuration > Administrative Templates > Ubuntu >
Client management > Power Management
* Double click on the last entry: Whether to hibernate ...
* Enable it, set the value to "hibernate"
* On a client with adsys, while connected on an AD account, run sudo adsysctl
update -m -vv
* Observe the logs that indicate the parsing of the dconf key:
DEBUG Analyzing entry
{Key:org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
Value:hibernate Disabled:false Meta:s Strategy: Err:}
* Observe the output of the following command (it should print 'hibernate'):
gsettings get org.gnome.settings-daemon.plugins.power
sleep-inactive-battery-type
[Where problems could occur]
This code is located in the dconf policy application manager and
restricted to it. The negative impact in case of a new bug will be
seen by gsettings key not being applied.
[Other Info]
This issue was initially reported on GitHub at
https://github.com/ubuntu/adsys/issues/135
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982349/+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 1248174] Re: Update the Ubuntu colour palette to fit the spec
What does this bug have to do with GIMP? ** Changed in: gimp (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Incomplete Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+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 1982351] Re: [SRU] Backport adsys-windows binary package
** Description changed: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] - * adsys-windows is a new binary package. Impact is thus only for people installing. - * This is a entreprise feature requested by desktop customers running LTS. + * adsys-windows is a new binary package. Impact is thus only for people installing. + * This is a entreprise feature requested by desktop customers running LTS. [Test Plan] - Copy the adwatchd.exe executable on a Windows machine and run it: - 1. set a path where the configuration file will be written - 2. input a list of scripts directories to be watched + 1. Install the adsys-windows package + 2. Copy the adwatchd.exe executable on a Windows machine and run it: + 3. Set a path where the configuration file will be written + 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the - root of the watched directory. + root of the watched directory. If a GPT.INI is not found, the daemon + will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. -- 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/1982351 Title: [SRU] Backport adsys-windows binary package Status in adsys package in Ubuntu: New Bug description: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] * adsys-windows is a new binary package. Impact is thus only for people installing. * This is a entreprise feature requested by desktop customers running LTS. [Test Plan] 1. Install the adsys-windows package 2. Copy the adwatchd.exe executable on a Windows machine and run it: 3. Set a path where the configuration file will be written 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the root of the watched directory. If a GPT.INI is not found, the daemon will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982351/+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 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
I found out that the bug is actually in poppler and have reported a bug upstream, where it is being worked on. ** Also affects: poppler (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/poppler/poppler/-/issues #1267 https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267 ** Also affects: poppler via https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly Status in Poppler: Unknown Status in evince package in Ubuntu: New Status in poppler package in Ubuntu: New Bug description: Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04. The symptom is that one can edit the form content and also save it, but that the entered text is only visible when the form field is focused and in edit mode. Otherwise the text it is invisible, also on printouts. Such bugs have been reported against Evince for a long time (e.g., https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am reporting this as a new bug because for the current form with which I am experiencing this it is a regression. I have attached the problematic form with two form fields filled out, one in the upper left corner and the big one in the lower half. I have produced this by taking the original, empty form (produced by somebody else) and first opened it in Evince 41.4, which I have installed from the snap package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field and saved the form. Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and entered text in the big field and saved the form. Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince 41.4. When I open the PDF again, only the text in the first field is visible. The text in the second field is visible only if I click into the field. The visibility of the field contents is the same for Evince 41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the problem is with Evince 42.3 incorrectly saving the field content, not with displaying it. Firefox shows and prints the content of both fields, though. Note that I cannot switch back to Evince 41 because for some other forms that I have the exact same problem happens only with the old version and the new version fixes it. So it seems that something changed that fixed it for some forms and broke it for others. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:32:27 2022 InstallationDate: Installed on 2021-11-26 (222 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: ID Status Spawn Bereit Zusammenfassung 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00 Installiere "evince" Snap SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1980836/+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
