[Desktop-packages] [Bug 550856] Re: page size setting is broken, use it as default crop or fix it by other means
(and by the way I found the same issue happens with xsane; my guess is there is the same bug there) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/550856 Title: page size setting is broken, use it as default crop or fix it by other means Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.11 series: Fix Released Status in simple-scan package in Ubuntu: Fix Released Status in simple-scan source package in Saucy: Fix Released Status in simple-scan source package in Trusty: Fix Released Bug description: For some SANE drivers simple scan always scans the largest scan area ignoring the "Page Size" setting in the preferences. To reproduce: 1. Open Simple Scan 2. Set page size in Document > Prefrences > Page Size, e.g. to "4x6" 3. Scan a document Expected result: The document is scanned at the requested size Observed result: The document is scanned at the maximum size Regression potential: Low. The fix was to set the page size using an alternative method for drivers that do not support the page-width, page-height options. There is a small chance that these settings might change behaviour / expose bugs on drivers that were previously working. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/550856/+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 550856] Re: page size setting is broken, use it as default crop or fix it by other means
I believe the issue is with ADF only My option are set as A4 scanning, ADF. Running de debug mode, i can see the requests for options : [+135,61s] DEBUG: scanner.vala:795: Option 6: name='tl-x' title='Top-left x' type=fixed size=4 unit=mm min=0,00, max=215,84, quant=0 cap=soft-select,soft-detect [+135,61s] DEBUG: scanner.vala:798: Description: Top-left x position of scan area. [+135,61s] DEBUG: scanner.vala:1002: sane_get_option_descriptor (7) [+135,61s] DEBUG: scanner.vala:795: Option 7: name='tl-y' title='Top-left y' type=fixed size=4 unit=mm min=0,00, max=355,51, quant=0 cap=soft-select,soft-detect [+135,61s] DEBUG: scanner.vala:798: Description: Top-left y position of scan area. [+135,61s] DEBUG: scanner.vala:1002: sane_get_option_descriptor (8) [+135,61s] DEBUG: scanner.vala:795: Option 8: name='br-x' title='Bottom-right x' type=fixed size=4 unit=mm min=0,00, max=215,84, quant=0 cap=soft-select,soft-detect [+135,61s] DEBUG: scanner.vala:798: Description: Bottom-right x position of scan area. Then it seems it issues a call for action : [+135,61s] DEBUG: scanner.vala:602: sane_control_option (4, SANE_ACTION_SET_VALUE, source="ADF Duplex") -> (SANE_STATUS_GOOD, "ADF Duplex") [+135,61s] DEBUG: scanner.vala:602: sane_control_option (3, SANE_ACTION_SET_VALUE, mode="Gray") -> (SANE_STATUS_GOOD, "Gray") [+135,61s] DEBUG: scanner.vala:514: sane_control_option (2, SANE_ACTION_SET_VALUE, resolution=200) -> (SANE_STATUS_GOOD, 200) [+135,61s] DEBUG: scanner.vala:554: sane_control_option (8, SANE_ACTION_SET_VALUE, br-x=210,00) -> (SANE_STATUS_GOOD, 210,00) [+135,61s] DEBUG: scanner.vala:554: sane_control_option (9, SANE_ACTION_SET_VALUE, br-y=297,00) -> (SANE_STATUS_GOOD, 297,00) This will work for flatbed, as the paper, whether A4 of Letter size, is left-aligned (it tl-x=0, which i guess is the default); however with ADF, Letter is centered while A4 paper is centered in he scanning area which is 21.6cm wide; hence there should be a margin of 0.3 cm on each side of the scanning aread that for a flatbed, the offset for top left X should be 0 while for ADF, the A4 page is centered in the scanner area total width, ie, the top left X should be 6/2 = 3mm Am I wrong, or, what is missing here, is a call to set "top left x" ie ,tl-x=3 to offset where the scan range should actually start when scanning A4 with ADF. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/550856 Title: page size setting is broken, use it as default crop or fix it by other means Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.11 series: Fix Released Status in simple-scan package in Ubuntu: Fix Released Status in simple-scan source package in Saucy: Fix Released Status in simple-scan source package in Trusty: Fix Released Bug description: For some SANE drivers simple scan always scans the largest scan area ignoring the "Page Size" setting in the preferences. To reproduce: 1. Open Simple Scan 2. Set page size in Document > Prefrences > Page Size, e.g. to "4x6" 3. Scan a document Expected result: The document is scanned at the requested size Observed result: The document is scanned at the maximum size Regression potential: Low. The fix was to set the page size using an alternative method for drivers that do not support the page-width, page-height options. There is a small chance that these settings might change behaviour / expose bugs on drivers that were previously working. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/550856/+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 550856] Re: page size setting is broken, use it as default crop or fix it by other means
I am finding the same with a brother adf scanner. Whaterever i do, xsane or simple-scan will scan with letter witdh (and a bit longer than letter length), though I tried to set this up do A4 instead. Any chance to have this fixed ? It sounds unbelievable it has been around for such a long time Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/550856 Title: page size setting is broken, use it as default crop or fix it by other means Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.11 series: Fix Released Status in simple-scan package in Ubuntu: Fix Released Status in simple-scan source package in Saucy: Fix Released Status in simple-scan source package in Trusty: Fix Released Bug description: For some SANE drivers simple scan always scans the largest scan area ignoring the "Page Size" setting in the preferences. To reproduce: 1. Open Simple Scan 2. Set page size in Document > Prefrences > Page Size, e.g. to "4x6" 3. Scan a document Expected result: The document is scanned at the requested size Observed result: The document is scanned at the maximum size Regression potential: Low. The fix was to set the page size using an alternative method for drivers that do not support the page-width, page-height options. There is a small chance that these settings might change behaviour / expose bugs on drivers that were previously working. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/550856/+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 897222]
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- 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/897222 Title: [Upstream] Picture moves to left importing Word .doc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611229/+files/Test%20case.doc -O testcase.doc && lowriter -nologo testcase.doc is the "X" picture in the top right on the document remains in the same place importing from Word (Word screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611268/+files/Test%20case.jpg ). 4) What happens is the X moves to the left (LO screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611239/+files/Libreoffice.png ). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice-writer 1:3.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Nov 28 14:24:02 2011 ProcEnviron: LANGUAGE=pl_PL:pl:en_GB:en PATH=(custom, user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-10-18 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/897222/+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 897235]
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- 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/897235 Title: [Upstream] Rounded rectangle corners are indented importing Word .doc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897235/+attachment/2611270/+files/Test%20case.doc -O testcase.doc && lowriter -nologo testcase.doc is the gray and white rounded rectangle corners look as they do in the Word screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897235/+attachment/2611275/+files/Test%20case.jpg . 4) What happens instead is the corners are indented in LO screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897235/+attachment/2611273/+files/Libreoffice.png . ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice-writer 1:3.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Nov 28 14:49:44 2011 ProcEnviron: LANGUAGE=pl_PL:pl:en_GB:en PATH=(custom, user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-10-18 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/897235/+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 2026727] Re: Clicking on a notification in the notification list no longer raises window in LTS 22.04.3
Updated the title and description to clarify that the regression is restricted to messages in the notification list and not popup notifications. ** Description changed: - As part of the LTS 22.04.3 release many gnome package updates are - available in the 'proposed' repository. When checking these on a test - machine I noticed that the window raise behavior when clicking on - notifications has regressed for some applications. In 22.04.2 clicking - on a notification in gnome shell would raise the application window and - focus the inbox or chat channel the message was received in. In the - 22.04.3 proposed packages this is still the case for e.g. Thunderbird, - but for other applications such as 'slack' and 'signal' clicking on a - new message notification no longer raises the application window. + The window raise behavior when clicking on notifications in the + notification list has regressed in LTS 22.04.3. + + In 22.04.2 clicking on a queued notification in the list would raise the + application window and focus e.g. the inbox or chat channel the message + was received in. In 22.04.3, when clicking on queued notifications for + applications such as thunderbird, slack' and signal the application + window is no longer raised and 'Window is ready' notifications are not + triggered. + + The issue only occurs for queued messages in the message list, for + example when 'do not disturb' is enabled. Clicking on pop-up + notifications still focuses attention on the application the + notification originated from. + Although not a major bug, it's quite annoying as it breaks the workflow and means extra work in finding the application and the channel that the message arrived at. Due to the many package updates it's not clear to me which update broke the behavior (maybe mutter or gnome-shell) but filing it under shell because of the notification area issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-77.84-generic 5.15.108 Uname: Linux 5.15.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 08:47:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (1102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-11-19 (232 days ago) ** Summary changed: - Clicking on a notification in the notification list no longer raises window in LTS 22.04.3 + Clicking on a notification in the notification list no longer raises application window in LTS 22.04.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026727 Title: Clicking on a notification in the notification list no longer raises application window in LTS 22.04.3 Status in gnome-shell package in Ubuntu: Confirmed Bug description: The window raise behavior when clicking on notifications in the notification list has regressed in LTS 22.04.3. In 22.04.2 clicking on a queued notification in the list would raise the application window and focus e.g. the inbox or chat channel the message was received in. In 22.04.3, when clicking on queued notifications for applications such as thunderbird, slack' and signal the application window is no longer raised and 'Window is ready' notifications are not triggered. The issue only occurs for queued messages in the message list, for example when 'do not disturb' is enabled. Clicking on pop-up notifications still focuses attention on the application the notification originated from. Although not a major bug, it's quite annoying as it breaks the workflow and means extra work in finding the application and the channel that the message arrived at. Due to the many package updates it's not clear to me which update broke the behavior (maybe mutter or gnome-shell) but filing it under shell because of the notification area issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-77.84-generic 5.15.108 Uname: Linux 5.15.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 08:47:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (1102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color
[Desktop-packages] [Bug 2026727] Re: Clicking on a notification in the notification list no longer raises window in LTS 22.04.3
** Summary changed: - Clicking on a notification no longer raises window in LTS 22.04.3 + Clicking on a notification in the notification list no longer raises window in LTS 22.04.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026727 Title: Clicking on a notification in the notification list no longer raises window in LTS 22.04.3 Status in gnome-shell package in Ubuntu: Confirmed Bug description: As part of the LTS 22.04.3 release many gnome package updates are available in the 'proposed' repository. When checking these on a test machine I noticed that the window raise behavior when clicking on notifications has regressed for some applications. In 22.04.2 clicking on a notification in gnome shell would raise the application window and focus the inbox or chat channel the message was received in. In the 22.04.3 proposed packages this is still the case for e.g. Thunderbird, but for other applications such as 'slack' and 'signal' clicking on a new message notification no longer raises the application window. Although not a major bug, it's quite annoying as it breaks the workflow and means extra work in finding the application and the channel that the message arrived at. Due to the many package updates it's not clear to me which update broke the behavior (maybe mutter or gnome-shell) but filing it under shell because of the notification area issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-77.84-generic 5.15.108 Uname: Linux 5.15.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 08:47:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (1102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-11-19 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026727/+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 2031433] Re: webkit2gtk 2.41.90 fails to build on riscv64
https://launchpad.net/ubuntu/+source/webkit2gtk/2.41.92-1/+latestbuild/riscv64
** Changed in: webkit2gtk (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/2031433
Title:
webkit2gtk 2.41.90 fails to build on riscv64
Status in Webkit:
Confirmed
Status in webkit2gtk package in Ubuntu:
Fix Released
Bug description:
- webkitgtk 2.41.90
- Ubuntu 23.10
-
https://salsa.debian.org/webkit-team/webkit/-/blob/wk2/experimental/debian/rules
-
https://salsa.debian.org/webkit-team/webkit/-/blob/wk2/experimental/debian/control
webkitgtk 2.41.90 fails to build on riscv64 but seems to build ok on
our other architectures.
Full build log
---
https://launchpad.net/ubuntu/+source/webkit2gtk/2.41.90-1ubuntu1
Build log excerpt
--
In file included from
JavaScriptCore/DerivedSources/unified-sources/UnifiedSource-15db4ad9-1.cpp:1:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp: In member
function
‘JSC::Wasm::B3IRGenerator::PartialResult
JSC::Wasm::B3IRGenerator::addI32Popcnt(ExpressionType, JSC::B3::Variable*&)’:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp:5214:25:
error: ‘supportsCountPopulation’ is not a member of ‘JSC::MacroAssembler’
5214 | if (MacroAssembler::supportsCountPopulation()) {
| ^~~
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp: In lambda
function:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp:5224:17:
error: ‘class JSC::CCallHelpers’ has no member named ‘countPopulation32’
5224 | jit.countPopulation32(params[1].gpr(), params[0].gpr(),
params.fpScratch(0));
| ^
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp: In member
function
‘JSC::Wasm::B3IRGenerator::PartialResult
JSC::Wasm::B3IRGenerator::addI64Popcnt(ExpressionType, JSC::B3::Variable*&)’:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp:5241:25:
error: ‘supportsCountPopulation’ is not a member of ‘JSC::MacroAssembler’
5241 | if (MacroAssembler::supportsCountPopulation()) {
| ^~~
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp: In lambda
function:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp:5251:17:
error: ‘class JSC::CCallHelpers’ has no member named ‘countPopulation64’
5251 | jit.countPopulation64(params[1].gpr(), params[0].gpr(),
params.fpScratch(0));
| ^
To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/2031433/+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 2036333] Re: signon-ui no longer works for Goolge authentication
Link to report on KDE's bug tracker: https://bugs.kde.org/show_bug.cgi?id=420280 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/2036333 Title: signon-ui no longer works for Goolge authentication Status in signon-ui package in Ubuntu: New Status in signon-ui package in Fedora: Unknown Bug description: The version of signon-ui from Launchpad no longer works for adding Google services in Kubuntu. The login hangs indefinitely after entering an email address. Apparently, a slightly newer version from its current home on git reportedly works, and is what others have been using: https://gitlab.com/accounts-sso/signon-ui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/2036333/+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 2036333] [NEW] signon-ui no longer works for Goolge authentication
Public bug reported: The version of signon-ui from Launchpad no longer works for adding Google services in Kubuntu. The login hangs indefinitely after entering an email address. Apparently, a slightly newer version from its current home on git reportedly works, and is what others have been using: https://gitlab.com/accounts-sso/signon-ui ** Affects: signon-ui (Ubuntu) Importance: Undecided Status: New ** Affects: signon-ui (Fedora) Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #2230099 https://bugzilla.redhat.com/show_bug.cgi?id=2230099 ** Also affects: signon-ui (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2230099 Importance: Unknown Status: Unknown ** Bug watch added: KDE Bug Tracking System #420280 https://bugs.kde.org/show_bug.cgi?id=420280 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/2036333 Title: signon-ui no longer works for Goolge authentication Status in signon-ui package in Ubuntu: New Status in signon-ui package in Fedora: Unknown Bug description: The version of signon-ui from Launchpad no longer works for adding Google services in Kubuntu. The login hangs indefinitely after entering an email address. Apparently, a slightly newer version from its current home on git reportedly works, and is what others have been using: https://gitlab.com/accounts-sso/signon-ui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/2036333/+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 2036330] Re: geoclue crashed with SIGSEGV in g_task_attach_source()
*** This bug is a duplicate of bug 2034902 *** https://bugs.launchpad.net/bugs/2034902 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2034902, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2036330/+attachment/5701553/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2036330/+attachment/5701555/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2036330/+attachment/5701558/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2036330/+attachment/5701559/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2036330/+attachment/5701560/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2036330/+attachment/5701561/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2036330/+attachment/5701562/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 2034902 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2036330 Title: geoclue crashed with SIGSEGV in g_task_attach_source() Status in geoclue-2.0 package in Ubuntu: New Bug description: Happened right after booting into the system after the upgrade from kernel 6.3 to 6.5 and installing other package updates. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: geoclue-2.0 2.7.0-3ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Sep 16 22:06:51 2023 ExecutablePath: /usr/libexec/geoclue InstallationDate: Installed on 2023-08-13 (34 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230813) ProcAttrCurrent: /usr/libexec/geoclue (enforce) ProcCmdline: /usr/libexec/geoclue ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fcb91ce9fc6 : cmp %rsi,(%rax) PC (0x7fcb91ce9fc6) ok source "%rsi" ok destination "(%rax)" (0x55b9dbb96) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: geoclue-2.0 StacktraceTop: g_task_attach_source () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_task_return_error_if_cancelled () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: geoclue crashed with SIGSEGV in g_task_attach_source() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2036330/+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 2036327] Re: gnome-shell crashed with signal 5 in g_log_structured_array()
*** This bug is a duplicate of bug 2034672 *** https://bugs.launchpad.net/bugs/2034672 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2034672, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2036327/+attachment/5701516/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2036327/+attachment/5701518/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2036327/+attachment/5701522/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2036327/+attachment/5701523/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2036327/+attachment/5701524/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2036327/+attachment/5701526/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2036327/+attachment/5701527/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 2034672 gnome-shell crashed with GLXBadDrawable on startup in a Xorg session ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036327 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: just downloaded iso image from Your development site and run the software. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 18:32:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036327/+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 2036315] Re: sol takes a long time to start
Problem occurs on Mantic installed from Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) selecting Normal installation (full), does NOT occur on same PC, different partition installed from same ISO but selecting Minimal installation and then installing aisleriot by hand via apt. Both systems are updated at same level. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: New Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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 2036317] Re: Snap icons are not restored after update of snap :)
** Package changed: ubuntu => firefox (Ubuntu) -- 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/2036317 Title: Snap icons are not restored after update of snap :) Status in firefox package in Ubuntu: New Bug description: A very minor issue. I use Ubuntu 16.04 ESM for banking, so I use the newest snaps of Firefox and LibreOffice :) After an update of the snap the icon disappears and I have to move it there again manually. I noticed that In Ubuntu Unity 22.04 that issue has been solved, so maybe you can have a look at that solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 4.15.0-216.227~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-216-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 16 11:14:03 2023 InstallationDate: Installed on 2017-03-29 (2362 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2036317/+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 2036317] [NEW] Snap icons are not restored after update of snap :)
You have been subscribed to a public bug: A very minor issue. I use Ubuntu 16.04 ESM for banking, so I use the newest snaps of Firefox and LibreOffice :) After an update of the snap the icon disappears and I have to move it there again manually. I noticed that In Ubuntu Unity 22.04 that issue has been solved, so maybe you can have a look at that solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 4.15.0-216.227~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-216-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 16 11:14:03 2023 InstallationDate: Installed on 2017-03-29 (2362 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- Snap icons are not restored after update of snap :) https://bugs.launchpad.net/bugs/2036317 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox 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 2025531] Re: file-roller crashed with signal 5 in g_object_new_valist()
First it happened after system update of the VBox VM and again after the reboot, just at the moment I wanted to shut down the system. I only did run the following script: sudo snap refresh sudo apt autoremove -y sudo apt autoclean sudo apt clean sudo journalctl --vacuum-time=3d if [ "$1" = "-z" ]; then echo "Start Zeroing" dd if=/dev/zero of=/home/bertadmin/zeroes rm /home/bertadmin/zeroes else echo "No Zeroing" fi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2025531 Title: file-roller crashed with signal 5 in g_object_new_valist() Status in file-roller package in Ubuntu: Incomplete Bug description: While edubuntu-mantic parallel installing kubuntu kde-desktop ubuntucinnamon-desktop: E: /tmp/apt-dpkg-install-iBrOhl/518-kubuntu-settings- desktop_1%3a23.04.5_all.deb: »/etc/skel/.face« tried to override because of desktop-base 12.0.6ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: file-roller 43.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 14:35:45 2023 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2023-07-01 (0 days ago) InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230629) ProcCmdline: /usr/bin/file-roller --service ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 5 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: My solution in synaptic was: uninstall kubuntu-desktop and kubuntu-settings-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2025531/+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 2036315] [NEW] sol takes a long time to start
Public bug reported: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: aisleriot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: New Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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 2036309] Re: Screen glitches after sleep mode
** Attachment added: "Screenshot from 2023-09-16 14-23-47.png" https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2036309/+attachment/5701471/+files/Screenshot%20from%202023-09-16%2014-23-47.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2036309 Title: Screen glitches after sleep mode Status in wayland package in Ubuntu: New Bug description: After sleep, I have the login screen, but after login the whole gnome interface is malfunctioning and displaying different subtitles and icons. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.86.05 Fri Jul 14 20:46:33 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 14:13:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU106 [GeForce RTX 2060 SUPER] [1462:c755] MachineType: ASRock Z790 PG Lightning ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=f9e4a75f-7780-4ccd-8811-7a257c4d1586 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.01 dmi.board.name: Z790 PG Lightning dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.01:bd01/09/2023:br5.27:svnASRock:pnZ790PGLightning:pvrToBeFilledByO.E.M.:rvnASRock:rnZ790PGLightning:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: Z790 PG Lightning dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: ASRock version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2036309/+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 2036309] Re: Screen glitches after sleep mode
** Attachment added: "Screenshot from 2023-09-16 14-17-40.png" https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2036309/+attachment/5701470/+files/Screenshot%20from%202023-09-16%2014-17-40.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2036309 Title: Screen glitches after sleep mode Status in wayland package in Ubuntu: New Bug description: After sleep, I have the login screen, but after login the whole gnome interface is malfunctioning and displaying different subtitles and icons. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.86.05 Fri Jul 14 20:46:33 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 14:13:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU106 [GeForce RTX 2060 SUPER] [1462:c755] MachineType: ASRock Z790 PG Lightning ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=f9e4a75f-7780-4ccd-8811-7a257c4d1586 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.01 dmi.board.name: Z790 PG Lightning dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.01:bd01/09/2023:br5.27:svnASRock:pnZ790PGLightning:pvrToBeFilledByO.E.M.:rvnASRock:rnZ790PGLightning:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: Z790 PG Lightning dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: ASRock version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2036309/+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 2036309] [NEW] Screen glitches after sleep mode
Public bug reported: After sleep, I have the login screen, but after login the whole gnome interface is malfunctioning and displaying different subtitles and icons. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.86.05 Fri Jul 14 20:46:33 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 14:13:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU106 [GeForce RTX 2060 SUPER] [1462:c755] MachineType: ASRock Z790 PG Lightning ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=f9e4a75f-7780-4ccd-8811-7a257c4d1586 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.01 dmi.board.name: Z790 PG Lightning dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.01:bd01/09/2023:br5.27:svnASRock:pnZ790PGLightning:pvrToBeFilledByO.E.M.:rvnASRock:rnZ790PGLightning:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: Z790 PG Lightning dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: ASRock version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu wayland-session ** Attachment added: "Screenshot from 2023-09-16 14-17-40.png" https://bugs.launchpad.net/bugs/2036309/+attachment/5701448/+files/Screenshot%20from%202023-09-16%2014-17-40.png ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2036309 Title: Screen glitches after sleep mode Status in wayland package in Ubuntu: New Bug description: After sleep, I have the login screen, but after login the whole gnome interface is malfunctioning and displaying different subtitles and icons. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.86.05 Fri Jul 14 20:46:33 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins:
[Desktop-packages] [Bug 2033643] Autopkgtest regression report (libreoffice/4:7.5.6-0ubuntu0.23.04.1)
All autopkgtests for the newly accepted libreoffice (4:7.5.6-0ubuntu0.23.04.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/4:7.5.6-0ubuntu0.23.04.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#libreoffice [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2033643 Title: [SRU] libreoffice 7.5.6 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of 53 bugs): https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs 7.5.6 RC2 is identical to the 7.5.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * 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. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135055/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230901_205756_d4783@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230902_020105_e2774@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230901_185845_d6d5b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230901_174418_b7c30@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230901_201014_90e5e@/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 53 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/2033643/+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 2036190] Re: fwupd running in WSL 2 in Ubuntu-22.04 fails to start
Mario Limonciello: I don't think gnome-software is trying to start fwupd, but it's trying to access it. -- 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/2036190 Title: fwupd running in WSL 2 in Ubuntu-22.04 fails to start Status in gnome-software package in Ubuntu: New Bug description: The fwupd systemd service file contains "ConditionVirtualization=!container". This blocks fwupd from starting in WSL 2 Ubuntu-22.04 instance. Modifying the fwupd systemd service file to contain: # /etc/systemd/system/fwupd.service.d/override.conf [Unit] ConditionVirtualization= fixes this issue. WSL 2 is a light-weight utility VM, not a container. I noticed this issue when starting gnome-software. gnome-software output this error to the terminal: 09:48:20:0857 Gs plugin fwupd took 25.0 seconds to do setup 09:48:21:0461 PK failed to set proxy: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid 09:48:21:0462 GsPluginPackageKit failed to set proxies: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid 09:48:46:0298 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark 09:48:46:0299 Gs not handling error failed for action refresh: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) 09:48:46:0299 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark 09:48:46:0299 Gs not handling error failed for action get-updates-historical: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fwupd 1.7.9-1~22.04.3 Uname: Linux 5.10.16.3-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Xpra Date: Fri Sep 15 13:01:49 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2036190/+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 2035220] Re: cve-2023-4863
** Changed in: chromium (Debian)
Status: New => Fix Released
--
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/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in firefox-esr package in Ubuntu:
Fix Released
Status in libwebp package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Released
Status in chromium package in Debian:
Fix Released
Status in libwebp package in Debian:
Fix Released
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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
