[Desktop-packages] [Bug 2003833] Re: colord migration blocked by impossible depends on argyll
I'm not sure Argyll is going to be MIR-able; could we instead demote colord-sensor-argyll to universe? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/2003833 Title: colord migration blocked by impossible depends on argyll Status in colord package in Ubuntu: New Bug description: colord recently re-enabled argyll support. Unfortunately since argyll is in universe and colord is in main, this is causing an 'impossible depends' migration error for colord. colord-sensor-argyll/amd64 in main cannot depend on argyll in universe Impossible Depends: colord -> argyll/2.3.1+repack-1ubuntu1/amd64 colord (1.4.6-2) unstable; urgency=medium * debian/control: - Build-Depend on polkitd. Fixes FTBFS (Closes: #1022355) - Bump Standards-Version to 4.6.1 (no changes needed) * debian/rules: * debian/control: * debian/not-installed: - Re-enable Argyll support. Argyll no longer appears in danger of being removed from the archive. * debian/copyright: - Fix misspelling of Richard Hughes' name - Drop no-longer-necessary Files: stanzas - Include full license details of data/profiles -- Christopher James Halse Rogers Tue, 01 Nov 2022 11:02:35 +0100 There is a MIR for argyll (LP: #821883) which could be a solution for this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/2003833/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
This issue is still present on 23.04, resolved by deleting old certificate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 2003833] [NEW] colord migration blocked by impossible depends on argyll
Public bug reported: colord recently re-enabled argyll support. Unfortunately since argyll is in universe and colord is in main, this is causing an 'impossible depends' migration error for colord. colord-sensor-argyll/amd64 in main cannot depend on argyll in universe Impossible Depends: colord -> argyll/2.3.1+repack-1ubuntu1/amd64 colord (1.4.6-2) unstable; urgency=medium * debian/control: - Build-Depend on polkitd. Fixes FTBFS (Closes: #1022355) - Bump Standards-Version to 4.6.1 (no changes needed) * debian/rules: * debian/control: * debian/not-installed: - Re-enable Argyll support. Argyll no longer appears in danger of being removed from the archive. * debian/copyright: - Fix misspelling of Richard Hughes' name - Drop no-longer-necessary Files: stanzas - Include full license details of data/profiles -- Christopher James Halse Rogers Tue, 01 Nov 2022 11:02:35 +0100 There is a MIR for argyll (LP: #821883) which could be a solution for this issue. ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuses -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/2003833 Title: colord migration blocked by impossible depends on argyll Status in colord package in Ubuntu: New Bug description: colord recently re-enabled argyll support. Unfortunately since argyll is in universe and colord is in main, this is causing an 'impossible depends' migration error for colord. colord-sensor-argyll/amd64 in main cannot depend on argyll in universe Impossible Depends: colord -> argyll/2.3.1+repack-1ubuntu1/amd64 colord (1.4.6-2) unstable; urgency=medium * debian/control: - Build-Depend on polkitd. Fixes FTBFS (Closes: #1022355) - Bump Standards-Version to 4.6.1 (no changes needed) * debian/rules: * debian/control: * debian/not-installed: - Re-enable Argyll support. Argyll no longer appears in danger of being removed from the archive. * debian/copyright: - Fix misspelling of Richard Hughes' name - Drop no-longer-necessary Files: stanzas - Include full license details of data/profiles -- Christopher James Halse Rogers Tue, 01 Nov 2022 11:02:35 +0100 There is a MIR for argyll (LP: #821883) which could be a solution for this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/2003833/+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 1958019]
I wanted to report a similar issue on Lenovo Legion 7 Slim AMD. Onboard speakers do not seem to produce sound but in settings menu sound appears to be getting produced on the speakers. Headphones work fine. Thankfully I primarily use headphones but wanted to report the issue. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
Hello Bram, or anyone else affected, Accepted fonts-noto-color-emoji into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fonts-noto-color- emoji/2.038-0ubuntu1 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: fonts-noto-color-emoji (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 fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 This update requires the nototools update to be accepted as a build dependency LP: #1990681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+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 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
This bug was fixed in the package libnl3 - 3.4.0-1ubuntu0.1 --- libnl3 (3.4.0-1ubuntu0.1) focal; urgency=medium * Backport one upstream fix to support devices using NLA_F_NESTED - 7de65a051fb3 (attr: mark nested attributes as NLA_F_NESTED) (LP: #1998765) -- Robert Liu Fri, 02 Dec 2022 22:05:28 +0800 ** Changed in: libnl3 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: Fix Released Status in libnl3 source package in Jammy: Invalid Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+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 1998765] Update Released
The verification of the Stable Release Update for libnl3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: Fix Released Status in libnl3 source package in Jammy: Invalid Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+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 2002609] Re: [SRU] Disable pressure for not detecting contact size
This bug was fixed in the package libinput - 1.20.0-1ubuntu0.2 --- libinput (1.20.0-1ubuntu0.2) jammy; urgency=medium * Disable pressure for not detecting contact size (LP: #2002609) - d/p/0001-quirks-add-quirks-for-Dell-Precision5680-Touchpad.patch Disable the pressure handling for the touchpad. -- Kai-Chuan Hsieh Thu, 12 Jan 2023 14:58:22 +0800 ** Changed in: libinput (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2002609 Title: [SRU] Disable pressure for not detecting contact size Status in OEM Priority Project: New Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Jammy: Fix Released Status in libinput source package in Kinetic: Fix Released Bug description: [ Impact ] * Dell's platform has a touchpad report pressure capability * The predefined threshold for the touchpad cause the user experience bad * Disable pressure event handling to align with upstream [ Test Plan ] * on Dell precision 5680 with touchpad vid:0x27c6 pid:0x0f60 * check left/right button * check 2 fingers scrolling * check 1 finger drag and drop * check 2 fingers drag and drop [ Where problems could occur ] * The quirk match the PID VID only, it won't impact other touchpad [ Other Info ] * https://gitlab.freedesktop.org/libinput/libinput/-/commit/29a49e968e67eb7bf6d63c9f93b06ee983772018 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2002609/+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 2002609] Re: [SRU] Disable pressure for not detecting contact size
This bug was fixed in the package libinput - 1.21.0-1ubuntu1 --- libinput (1.21.0-1ubuntu1) kinetic; urgency=medium * Disable pressure for not detecting contact size (LP: #2002609) - d/p/0001-quirks-add-quirks-for-Dell-Precision5680-Touchpad.patch Disable the pressure handling for the touchpad. -- Kai-Chuan Hsieh Thu, 12 Jan 2023 16:08:15 +0800 ** Changed in: libinput (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2002609 Title: [SRU] Disable pressure for not detecting contact size Status in OEM Priority Project: New Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Jammy: Fix Released Status in libinput source package in Kinetic: Fix Released Bug description: [ Impact ] * Dell's platform has a touchpad report pressure capability * The predefined threshold for the touchpad cause the user experience bad * Disable pressure event handling to align with upstream [ Test Plan ] * on Dell precision 5680 with touchpad vid:0x27c6 pid:0x0f60 * check left/right button * check 2 fingers scrolling * check 1 finger drag and drop * check 2 fingers drag and drop [ Where problems could occur ] * The quirk match the PID VID only, it won't impact other touchpad [ Other Info ] * https://gitlab.freedesktop.org/libinput/libinput/-/commit/29a49e968e67eb7bf6d63c9f93b06ee983772018 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2002609/+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 2003735]
7.4.5 was a hotfix release, updating target in status-whiteboard -- 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/2003735 Title: [SRU] libreoffice 7.4.4 updates for kinetic Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Kinetic: Fix Committed Status in libreoffice source package in Lunar: In Progress Bug description: [Impact] * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1 * It includes one crash fix for https://bugs.documentfoundation.org/show_bug.cgi?id=153059 https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1&id=ef02234e55c1ca0890b6882fb2d9a33328cbb88e * This SRU will cherry-pick this specific patch only. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1604/ * 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 * Test plan for this crash fix 1. Open a new writer document 2. Insert a page break 3. Go to page 1 and click on the header 4. Go to page 2 and click on the header button -> Crash [Regression Potential] * This is well defined and upstream tested patch to fix a specific crash. * 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/df-libreoffice/+bug/2003735/+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 2003735] Re: [SRU] libreoffice 7.4.4 updates for kinetic
Hello Rico, or anyone else affected, Accepted libreoffice into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.2 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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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 Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/2003735 Title: [SRU] libreoffice 7.4.4 updates for kinetic Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Kinetic: Fix Committed Status in libreoffice source package in Lunar: In Progress Bug description: [Impact] * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1 * It includes one crash fix for https://bugs.documentfoundation.org/show_bug.cgi?id=153059 https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1&id=ef02234e55c1ca0890b6882fb2d9a33328cbb88e * This SRU will cherry-pick this specific patch only. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1604/ * 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 * Test plan for this crash fix 1. Open a new writer document 2. Insert a page break 3. Go to page 1 and click on the header 4. Go to page 2 and click on the header button -> Crash [Regression Potential] * This is well defined and upstream tested patch to fix a specific crash. * 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/df-libreoffice/+bug/2003735/+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 2003735] Re: [SRU] libreoffice 7.4.4 updates for kinetic
** Description changed: [Impact] * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release - https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1 + https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1 * It includes one crash fix for https://bugs.documentfoundation.org/show_bug.cgi?id=153059 https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1&id=ef02234e55c1ca0890b6882fb2d9a33328cbb88e * This SRU will cherry-pick this specific patch only. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1604/ * 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 + * Test plan for this crash fix + 1. Open a new writer document + 2. Insert a page break + 3. Go to page 1 and click on the header + 4. Go to page 2 and click on the header button + -> Crash + [Regression Potential] * This is well defined and upstream tested patch to fix a specific crash. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- 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/2003735 Title: [SRU] libreoffice 7.4.4 updates for kinetic Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Kinetic: In Progress Status in libreoffice source package in Lunar: In Progress Bug description: [Impact] * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1 * It includes one crash fix for https://bugs.documentfoundation.org/show_bug.cgi?id=153059 https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1&id=ef02234e55c1ca0890b6882fb2d9a33328cbb88e * This SRU will cherry-pick this specific patch only. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1604/ * 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 * Test plan for this crash fix 1. Open a new writer document 2. Insert a page break 3. Go to page 1 and click on the header 4. Go to page 2 and click on the header button -> Crash [Regression Potential] * This is well defined and upstream tested patch to fix a specific crash. * 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/df-libreoffice/+bug/2003735/+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 1993907] Re: nautilus freezes randomly
Same here! Nautilus freezing by itself randomly... If I start a search, freeze instantly! Reopen only killing the process... any viable workaround?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993907 Title: nautilus freezes randomly Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus becomes unresponsive and "files" is not responding sign appears at random ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 15:39:58 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-05-13 (161 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993907/+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 1210316] Re: xf86-video-ati XMir acceleration detection broken: x crashes with radeon hd7850 video card with error /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/driver
Keep up the good work. https://onegoodhandyman.co.uk/service/electrical/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1210316 Title: xf86-video-ati XMir acceleration detection broken: x crashes with radeon hd7850 video card with error /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/radeon_drv.so: undefined symbol: exaGetPixmapDriverPrivate Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: Description: x crashes with radeon hd7850 video card with error /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/radeon_drv.so: undefined symbol: exaGetPixmapDriverPrivate steps: 1. install saucy 2. sudo apt-get update 3. sudo apt-get install unity-system-compositor 4. reboot expected results: xmir is running actual results: xmir crashes then runs in failback mode additional info: robotfuel: Well, that would be because it hasn't loaded the EXA module, which is perfectly reasonable robotfuel: What's not reasonable is that it's trying to resolve EXA symbols. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-ati 1:7.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDmesg: [ 10.764013] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 13.869816] init: lightdm main process (967) terminated with status 1 Date: Thu Aug 8 22:18:55 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2320] InstallationDate: Installed on 2013-08-08 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=69ca392e-047d-4815-a27f-7ec25932fc2e ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904 dmi.board.name: DZ77BH-55K dmi.board.vendor: Intel Corporation dmi.board.version: AAG39008-400 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr: version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu8 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu8 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3 xserver.bootTime: Thu Aug 8 21:55:43 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputRaritan D2CIM-DVUSB KEYBOARD, id 8 inputRaritan D2CIM-DVUSB MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.2-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1210316/+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 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
The 4 packages of the new generation of cups-filters are uploaded to Lunar now: libcupsfilters 2.0~b2, libppd 2:2.0~b2, cups-filters 2.0~b2, cups-browsed 2.0~b2, all but cups-filters considered NEW. As soon as the NEW packages land in Universe I will add tasks for them to this MIR bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-filters package in Ubuntu: Incomplete Bug description: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2003259/+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 821883] Re: [MIR] argyll
@Bryce, @RAOF: thanks for the notice! I feel we should then reuse this MIR to file a new template with our modern MIR rules (Note that the initial demand was made in 2011!) I’m thus marking it as incomplete until this is DONE, feel free to redirect this request directly to the team who will own and maintain the package. ** Changed in: argyll (Ubuntu) Assignee: Till Kamppeter (till-kamppeter) => Chris Halse Rogers (raof) ** No longer affects: colord (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/821883 Title: [MIR] argyll Status in argyll package in Ubuntu: Incomplete Bug description: Note this MIR is for both argyll and libicc2 (both packages are currently in Universe). With the most recent argyll package the binary packages of argyll and libicc2 are now all produced by the argyll source package. We followed Debian to unsplit here as the upstream source for both is argyll. The libicc2 source package in Universe can get dropped. Availability: Currently available in Universe, building on all currently supported architectures, see https://launchpad.net/ubuntu/+source/argyll Rationale: In Oneiric we want to introduce ICC-based color management on the operating system level, using the same architecture as Fedora does. argyll (support for color calibration) and libicc2 (ICC handling library) are part of this architecture. Therefore we need them in Main. This MIR is a work item of the following Blueprint: https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-icc-color- management According to the Blueprint additional demand on CD space for the whole introduction of color management is around 300K only. Security: No security vulnerabilities known at CVE and Secunia for the current version (1.3.3), vulnerabilities of older versions are all fixed, no SUID components, no daemons. Quality assurance: Installs without debconf questions. The package is maintained upstream as new releases occur regularly and they get packaged for Debian by Roland Mas (see debian/changelog). UI standards: The package are a library and command line utilities. The complete upstream documentation is available in /usr/share/doc/argyll/. Each command shows a help page by calling it without parameters. Dependencies: Depends only on standard libraries for X and images. They are all in Main. Maintenance: See "Quality assurance". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argyll/+bug/821883/+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 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
Thanks for the MIR, however, as you wanted to do a simple MIR and not a full one, this is really lacking details and not tracking the real packages the MIRs are supposed to apply on. Please be considerate for the reviewer and help them as much as possible by following the process, so that from one bug report, we can see: - which source packages are impacted - which binary packages needs to be promoted. That, without any more verbiage. Also, those packages were packaged a very long time ago, so it’s probably the right opportunity to ensure, especially with the split, that they all confirmant with the MIR policy. So, do you mind: - add one source package for any source package impacted. - for each source package, check the MIR requirements and file the template, ONE FOR EACH, in the description (you can separate them by markers to make it clearer). - state in each source package what code was moved where - remove cups-filters source package from here, and tell what’s going to happens with current cups-filters source package. Should it be demoted? Until there, I’m marking that bug as incomplete. ** Changed in: cups-filters (Ubuntu) Status: New => Incomplete ** Changed in: cups-filters (Ubuntu) Assignee: Didier Roche-Tolomelli (didrocks) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-filters package in Ubuntu: Incomplete Bug description: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2003259/+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 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
** Changed in: cups-filters (Ubuntu) Assignee: (unassigned) => Didier Roche-Tolomelli (didrocks) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-filters package in Ubuntu: Incomplete Bug description: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2003259/+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 2003790] [NEW] After successful pairing new bluetooth headphones + mix - sound crash
Public bug reported: Bluetooth pairing reports established using bluetoothctl, but the sound device is not available on the Ubuntu device(?settings) manager. Only the existing speakers (non buetooth) are showing as sound outputs (sinks). Bluetooth data: beadon@semiauto:~$ bluetoothctl Agent registered [CHG] Controller 28:DF:EB:B6:9B:66 Pairable: yes [Shure TW1]# show Controller 28:DF:EB:B6:9B:66 (public) Name: semiauto Alias: semiauto Class: 0x007c Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0541 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0c (12) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded Headphones: disable bluetooth, enable bluetooth, attempt connection. Bluetooth device is connected to another device (Android phone). Expected behavior is to disconnect the existing connection to the phone and pair only with the laptop. an 24 09:31:07 semiauto systemd[1]: Stopped target Bluetooth Support. Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/sbc_xq Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_1 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_0 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/faststream Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/faststream_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSink/opus_05 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_51 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_71 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSink/opus_05_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_pro Jan 24 09:31:07 semiauto systemd[1]: Started Load/Save RF Kill Switch Status. Jan 24 09:31:12 semiauto systemd[1]: systemd-rfkill.service: Deactivated successfully. Jan 24 09:31:20 semiauto systemd[1]: Starting Load/Save RF Kill Switch Status... Jan 24 09:31:20 semiauto systemd[1]: Started Load/Save RF Kill Switch Status. Jan 24 09:31:20 semiauto kernel: [66926.266001] usb 3-10: new full-speed USB device number 15 using xhci_hcd Jan 24 09:31:20 semiauto kernel: [66926.416144] usb 3-10: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02 Jan 24 09:31:20 semiauto kern
[Desktop-packages] [Bug 2003784] [NEW] Nautilus crashes on renames (Pango/GTK crash)
Public bug reported: I believe it's this bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/5311 Open Nautilus -> Hit F2 or select 'Rename' from the menu -> press an arrow key -> crash Using Kinetic, Xorg. Log messages: _pango_layout_get_iter: assertion 'PANGO_IS_LAYOUT (layout)' failed segfault at 0 ... error 4 in libpango-1.0.so.0.5000.10[...] Upstream bug reports: - https://gitlab.gnome.org/GNOME/gtk/-/issues/5311 (<--- this is where it was solved) - https://gitlab.gnome.org/GNOME/nautilus/-/issues/2609 - https://gitlab.gnome.org/GNOME/nautilus/-/issues/2454 - https://gitlab.gnome.org/GNOME/pango/-/issues/715 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2003784 Title: Nautilus crashes on renames (Pango/GTK crash) Status in nautilus package in Ubuntu: New Bug description: I believe it's this bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/5311 Open Nautilus -> Hit F2 or select 'Rename' from the menu -> press an arrow key -> crash Using Kinetic, Xorg. Log messages: _pango_layout_get_iter: assertion 'PANGO_IS_LAYOUT (layout)' failed segfault at 0 ... error 4 in libpango-1.0.so.0.5000.10[...] Upstream bug reports: - https://gitlab.gnome.org/GNOME/gtk/-/issues/5311 (<--- this is where it was solved) - https://gitlab.gnome.org/GNOME/nautilus/-/issues/2609 - https://gitlab.gnome.org/GNOME/nautilus/-/issues/2454 - https://gitlab.gnome.org/GNOME/pango/-/issues/715 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2003784/+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 1988859] Re: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]
This bug was fixed in the package mutter - 43.2-5ubuntu1 --- mutter (43.2-5ubuntu1) lunar; urgency=medium * Merge with Debian. Remaining change: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch mutter (43.2-5) unstable; urgency=medium [ Daniel van Vugt ] * Update Support-Dynamic-triple-double-buffering.patch. Fix tearing on monitors attached to secondary GPUs (LP: #1999216) * Add patch for cursor-renderer-native to workaround broken arm64 drivers. By forcing cursors to use dumb buffers. At least until Mesa gets fixed for panfrost, vc4, v3d... (LP: #1988859) -- Jeremy Bicha Mon, 23 Jan 2023 11:44:41 -0500 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1988859 Title: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)] Status in Mesa: New Status in Mutter: New Status in mesa package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Bug description: Every so often, the desktop will go black and then re appear on Ubuntu 22.10 Wayland Session which should not be occurring (this does not happen on 22.04.) Note that only the cursor can be seen. Reporting this before release so that it can be patched for (at least) the RasPi. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8 Uname: Linux 5.19.0-1001-raspi aarch64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.23.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 16:10:37 2022 DisplayManager: gdm3 ImageMediaBuild: 20220826 RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1988859/+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 1999216] Re: Secondary monitor tears when connected to a secondary GPU using Wayland
This bug was fixed in the package mutter - 43.2-5ubuntu1 --- mutter (43.2-5ubuntu1) lunar; urgency=medium * Merge with Debian. Remaining change: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch mutter (43.2-5) unstable; urgency=medium [ Daniel van Vugt ] * Update Support-Dynamic-triple-double-buffering.patch. Fix tearing on monitors attached to secondary GPUs (LP: #1999216) * Add patch for cursor-renderer-native to workaround broken arm64 drivers. By forcing cursors to use dumb buffers. At least until Mesa gets fixed for panfrost, vc4, v3d... (LP: #1988859) -- Jeremy Bicha Mon, 23 Jan 2023 11:44:41 -0500 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1999216 Title: Secondary monitor tears when connected to a secondary GPU using Wayland Status in mutter package in Ubuntu: Fix Released Bug description: Secondary monitor tears when connected to a secondary GPU using Wayland. Confirmed locally and first reported in: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1609480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999216/+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 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
** Changed in: brltty (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Confirmed Status in brltty source package in Oneiric: Fix Released Status in brltty package in Debian: Confirmed Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+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 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot
i am sorry forget this part because distrohop to fedora & opensuse. i make new issue at gitlab about this issue too https://gitlab.gnome.org/GNOME/gjs/-/issues/526. this part fix leak on gnome-shell part but its still have issue undefined ram usage increase. ** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #526 https://gitlab.gnome.org/GNOME/gjs/-/issues/526 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1973638 Title: gnome-shell 42 leaks tens of megabytes with every screenshot Status in GNOME Shell: Fix Released Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: [Impact] gnome-shell's memory usage grows by tens of megabytes with every screenshot. A few screenshots make it 100MB larger and a few dozen screenshots make it 1GB larger. [Test Plan for GNOME Shell Fix] TODO [Test Plan for GJS Fix] 1. Log into gnome-shell. 2. Measure its real memory usage: grep RSS /proc/`pidof gnome-shell`/status 3. Take 20 full screen screenshots by pressing PrtScn each time. No need to save them anywhere. 4. Measure the memory usage again. Expected: Memory usage grows a little but growth does not exceed a few hundred megabytes. It should level off after a while and sometimes even shrink due to garbage collection. Observed: Memory usage grows without bounds, easily exceeding 1GB after about 20 screenshots (depending on screen resolution). It never shrinks significantly. [Where problems could occur] Since the fix affects GJS, problems could occur in any part of gnome- shell. [Other Info] This leak requires multiple fixes to minimize the memory usage. For the moment we are only aiming to fix the main GJS portion of the bug that allows memory usage to exceed 1GB. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=ubiquity ** Also affects: ubiquity (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zsys (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: snapd (Ubuntu Jammy) ** No longer affects: systemd (Ubuntu Jammy) ** Changed in: ubiquity (Ubuntu Jammy) Importance: Undecided => High ** Changed in: ubiquity (Ubuntu Jammy) Status: New => Triaged ** Changed in: ubiquity (Ubuntu Jammy) Milestone: None => ubuntu-22.04.2 ** No longer affects: zfs-linux (Ubuntu Jammy) ** No longer affects: zsys (Ubuntu Jammy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Triaged Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
brltty won't be reinstalled on upgrades, removing it is a perfectly valid option. I linked a relevant Debian bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Confirmed Status in brltty source package in Oneiric: Fix Released Status in brltty package in Debian: Unknown Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+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 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
** Bug watch added: Debian Bug tracker #721763 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721763 ** Also affects: brltty (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721763 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Confirmed Status in brltty source package in Oneiric: Fix Released Status in brltty package in Debian: Unknown Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+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
Re: [Desktop-packages] [Bug 1968610] Re: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia
If Bram's suggestion fails, try to disable hardware acceleration: chromium --disable-gpu ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1968610 Title: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia Status in chromium-browser package in Ubuntu: Confirmed Bug description: When launching Chromium as a snap on Ubuntu 22.04, it will not open properly and will open the browser with only the titlebar and a transparent window. I am using an Nvidia Graphics card with the 510.60.02 Nvidia proprietary drivers. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Chromium Version: 100.0.4896.75 2022-04-07 When running "snap run chromium" in the terminal, the following output happens. Attached screenshot of result. nyaa@nyaa-desktop:~$ snap run chromium Gtk-Message: 13:42:20.777: Failed to load module "canberra-gtk-module" Gtk-Message: 13:42:20.778: Failed to load module "canberra-gtk-module" MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open nvidia-drm: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load driver: nvidia-drm MESA-LOADER: failed to open kms_swrast: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load swrast driver [9358:9478:0411/134223.111306:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. Edit: I have recently tested this more, and I've isolated it to Wayland and the snap version of Chromium. On X, the chromium snap runs correctly. When I run Chromium as a binary from the Chromium website, the issue doesn't occur on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968610/+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 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+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 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+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 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
This bug is not related to PC. Please log a new bug from your PC by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+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
