[Desktop-packages] [Bug 2001911] Re: [SRU] libreoffice 7.4.4 for kinetic
** Description changed: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * Version 7.4.2 is currently released in kinetic and 7.4.3 in kinetic-proposed. For a list of fixed bugs compared to 7.4.3 see the list of bugs fixed in the release candidates of 7.4.4 (that's a total of 114 bugs): https://wiki.documentfoundation.org/Releases/7.4.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/amd64/libr/libreoffice/20230106_232736_1d62c@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/arm64/libr/libreoffice/20230107_123110_dfe59@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/armhf/libr/libreoffice/20230107_140034_7d823@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/ppc64el/libr/libreoffice/20230107_011032_e9378@/log.gz - * [s390x] ... (not availble due to infrastructure problems) + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/s390x/libr/libreoffice/20230112_013620_d1bce@/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 114 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. -- 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/2001911 Title: [SRU] libreoffice 7.4.4 for kinetic Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Kinetic: In Progress Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * Version 7.4.2 is currently released in kinetic and 7.4.3 in kinetic-proposed. For a list of fixed bugs compared to 7.4.3 see the list of bugs fixed in the release candidates of 7.4.4 (that's a total of 114 bugs): https://wiki.documentfoundation.org/Releases/7.4.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * 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
[Desktop-packages] [Bug 2002609] [NEW] Disable pressure for not detecting contact size
Public bug reported: [ 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 ] * 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 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2000544 somerville ** Tags added: oem-priority originate-from-2000544 somerville -- 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: Disable pressure for not detecting contact size Status in OEM Priority Project: New Status in libinput package in Ubuntu: New 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 ] * 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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-2002265 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002558] Re: The ethernet connection icon has disappeared
Can you attach a screenshot or photo of the problem? ** Summary changed: - erro Icon connection + The ethernet connection icon has disappeared ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2002558 Title: The ethernet connection icon has disappeared Status in gnome-shell package in Ubuntu: Incomplete Bug description: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 11 13:53:57 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6290] [17aa:397f] InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20136 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=c7305ad4-8faf-45a3-8420-afbb79aaf181 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2012 dmi.bios.release: 0.93 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G485 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G485 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:br0.93:efr0.0:svnLENOVO:pn20136:pvrLenovoG485:rvnLENOVO:rnLenovoG485:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG485:skuLENOVO_MT_20136: dmi.product.family: IDEAPAD dmi.product.name: 20136 dmi.product.sku: LENOVO_MT_20136 dmi.product.version: Lenovo G485 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2002558/+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 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)
If the original problem is still present then please follow the instructions in comment #3. If it is not still present then we can close the bug. I am also skeptical that you need to create any i915.conf or xorg.conf files because it sounds like those were the cause of the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/2002432 Title: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load) Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I can only boot into recovery mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 10 18:45:16 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:501e] InstallationDate: Installed on 2015-11-17 (2611 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20AV002WXS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset dis_ucode_ldr i915.enable_hangcheck=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2018 dmi.bios.release: 1.93 dmi.bios.vendor: LENOVO dmi.bios.version: J4ET93WW(1.93) dmi.board.asset.tag: Not Available dmi.board.name: 20AV002WXS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540: dmi.product.family: ThinkPad L540 dmi.product.name: 20AV002WXS dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540 dmi.product.version: ThinkPad L540 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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 xserver.bootTime: Tue Jan 10 18:24:35 2023 xserver.configfile: /root/xorg.conf.new xserver.devices: xserver.errors: Server terminated with error (2). Closing log file. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:21.1.3-2ubuntu2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002432/+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 1995766] Re: X server segfault when starting youtube videos
*** This bug is a duplicate of bug 1999213 *** https://bugs.launchpad.net/bugs/1999213 Yes that's still bug 1999213. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-14 (174 days ago)
[Desktop-packages] [Bug 2002594] [NEW] gdm3 crashed with SIGTRAP ("GdmSession: no session desktop files installed, aborting...") in get_fallback_session_name() from get_default_session_name() from get
*** This bug is a duplicate of bug 1717878 ***
https://bugs.launchpad.net/bugs/1717878
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gdm3. This problem was most recently seen with package version 43.0-1ubuntu2,
the problem page at
https://errors.ubuntu.com/problem/f4fce39ac75fb4f87b243f14cb5f8e72f90c2c0f
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: hirsute jammy kinetic lunar
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2002594
Title:
gdm3 crashed with SIGTRAP ("GdmSession: no session desktop files
installed, aborting...") in get_fallback_session_name() from
get_default_session_name() from get_session_name() from
get_session_name() from get_session_filename()
Status in gdm3 package in Ubuntu:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gdm3. This problem was most recently seen with package version 43.0-1ubuntu2,
the problem page at
https://errors.ubuntu.com/problem/f4fce39ac75fb4f87b243f14cb5f8e72f90c2c0f
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2002594/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
** Tags added: dt-962 -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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)]
Workaround committed to mutter for the next lunar update, whenever that may be. https://salsa.debian.org/gnome-team/mutter/-/commit/d615363fa9 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-mesa-22.3.3 fixed-upstream -- 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 Committed 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 1983794] Re: Evolution not deleting autosave files
This bug was fixed in the package libcanberra - 0.30-10ubuntu2
---
libcanberra (0.30-10ubuntu2) lunar; urgency=medium
* d/p/gtk-module-Handle-display-closing-gracefully: Do not leak objects on
destruction.
As per previous fix for LP: #1949200 we were leaking Gtk Widgets when they
were manually destroyed, because we never released the reference that we
added previously.
Thanks to Alberts Muktupāvels for providing the test case and some analysis.
(LP: #1983794)
-- Marco Trevisan (Treviño) Tue, 10 Jan 2023
12:59:22 +0100
** Changed in: libcanberra (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1997996] Re: when in Trash, no dedicated top banner
Are you sure the total absence of « banner / bar » is expected ? It's a usability regression. On https://gitlab.gnome.org/GNOME/nautilus/-/issues/2096#note_1525051 the « banner / bar » is still there ( it's indeed older than 22.10 release. ) ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2096 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2096 -- 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/1997996 Title: when in Trash, no dedicated top banner Status in nautilus package in Ubuntu: Invalid Bug description: Hi, Ubuntu 22.10 here. When in Trash, Nautilus no longer displays a top banner in main window offering to empty or restore. Files attached : screenshots from 22.10 and 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1997996/+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 1965518] Re: [USB-Audio - USB Audio, recording] Recording problem
This is most likely related to USB IDs having to be added to ALSA UCM2 configuration. The specific commit for MSI Z690 Edge WiFi (USB ID 0db0:1feb) is https://github.com/alsa-project/alsa-ucm- conf/commit/c9c7559425a1b67a18700367fc54f75046a724f8 On Ubuntu 22.04 (and with an ASUS ALC4080 mainboard having the same symptoms) downloading and installing the latest UCM2 release failed as from version 1.2.7 "Syntax 6" is in use (https://alsa- project.org/wiki/Changes_v1.2.6.3_v1.2.7) which is not supported by the ALSA libraries supplied with Ubuntu 22.04. I had to add the section into the distribution-supplied USB-Audio.conf file manually, microphone is working for me now. -- 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/1965518 Title: [USB-Audio - USB Audio, recording] Recording problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio Realtek ALC4080 is not recording audio. What I did found out, that the bar which indicates that something is recording is going up, when I play some sound on ubuntu, so input "thinks" it is output I think. If raport is somehow saying I was not using that mic at the moment, that is because I was using other card which I need to buy, for mic to temporarly work. I rechecked it before sending report, and yes, that original from MBO audio input is still not working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Fri Mar 18 10:39:26 2022 InstallationDate: Installed on 2022-03-12 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed Symptom_Card: USB Audio - USB Audio Symptom_Type: None of the above Title: [USB-Audio - USB Audio, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.10 dmi.board.asset.tag: Default string dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D31 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965518/+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 1997996] Re: when in Trash, no dedicated top banner
This was an intentional change. https://gitlab.gnome.org/GNOME/nautilus/-/commit/5b954ee5354 Therefore, I'm closing this bug. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1997996 Title: when in Trash, no dedicated top banner Status in nautilus package in Ubuntu: Invalid Bug description: Hi, Ubuntu 22.10 here. When in Trash, Nautilus no longer displays a top banner in main window offering to empty or restore. Files attached : screenshots from 22.10 and 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1997996/+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 2002575] Re: Update nautilus to 43.2
** Description changed: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) + + Nautilus 43 switched to GTK4 which was a major change for a complex app. + Many regressions have been fixed in the new point release updates. + + Test Case 0 + --- + Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Ensure that Nautilus still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- 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/2002575 Title: Update nautilus to 43.2 Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Kinetic: Triaged Bug description: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) Nautilus 43 switched to GTK4 which was a major change for a complex app. Many regressions have been fixed in the new point release updates. Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Ensure that Nautilus still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2002575/+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 1988622] Re: gnome-sushi stopped working
** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released -- 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/1988622 Title: gnome-sushi stopped working Status in nautilus package in Ubuntu: Fix Released Bug description: Click a file, press space bar: nothing happens, sushi does not start. It was working few days ago. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-sushi 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 09:48:06 2022 InstallationDate: Installed on 2022-08-11 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-sushi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988622/+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 1995311] Re: seahorse-nautilus not working on ubuntu 22.10
seahorse-nautilus needs to be ported from GTK3 to GTK4 before it can be reintroduced to Ubuntu ** Package changed: nautilus (Ubuntu) => seahorse-nautilus (Ubuntu) ** Changed in: seahorse-nautilus (Ubuntu) Importance: Undecided => High ** Changed in: seahorse-nautilus (Ubuntu) Status: Confirmed => Triaged -- 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/1995311 Title: seahorse-nautilus not working on ubuntu 22.10 Status in seahorse-nautilus package in Ubuntu: Triaged Bug description: impossible to install seahorse-nautilus on ubuntu 22.10 so I cannot encrypt/decrypt files (except with line commands) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse-nautilus/+bug/1995311/+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 1995412] Re: Expandable folders option disappeared
This feature was added to Nautilus 44 Alpha which is expected to be part of Ubuntu 23.04 in April. ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Committed -- 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/1995412 Title: Expandable folders option disappeared Status in nautilus package in Ubuntu: Fix Committed Bug description: Ubuntu 22.10 nautilus: Installed: 1:43.0-1ubuntu1 Nautilus click on 'Preferences' Expandable folders option was present in Ubuntu 22.04 now disappeared in Ubuntu 22.10. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 1 18:54:22 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1580, 879)' InstallationDate: Installed on 2022-10-25 (7 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995412/+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 2002573] Re: Printer test page still emits the pre-2022 Ubuntu logo
Exact file in the source package (cups-filters) is debian/local/default-testpage-ubuntu.pdf Please keep the white area in the lower half of the page, when printing, cups-filters fills this part with printer property information. -- 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/2002573 Title: Printer test page still emits the pre-2022 Ubuntu logo Status in cups-filters package in Ubuntu: New Bug description: As it says on the tin. This is on 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002573/+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 2002573] Re: Printer test page still emits the pre-2022 Ubuntu logo
Elio, looks like someone in your team would be needed here to update said PDF file with the new logo ... Please forward if needed ... ** Changed in: cups-filters (Ubuntu) Importance: Undecided => High -- 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/2002573 Title: Printer test page still emits the pre-2022 Ubuntu logo Status in cups-filters package in Ubuntu: New Bug description: As it says on the tin. This is on 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002573/+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 2002573] Re: Printer test page still emits the pre-2022 Ubuntu logo
The template for the test page is /usr/share/cups/data/default- testpage.pdf which belongs to the cups-filters binary package. Moving to cups-filters ... ** Package changed: system-config-printer (Ubuntu) => cups-filters (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/2002573 Title: Printer test page still emits the pre-2022 Ubuntu logo Status in cups-filters package in Ubuntu: New Bug description: As it says on the tin. This is on 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002573/+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 2002575] [NEW] Update nautilus to 43.2
Public bug reported: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) Test Case 1 --- Install the update Ensure that Nautilus still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: nautilus (Ubuntu) Importance: High Status: Fix Committed ** Affects: nautilus (Ubuntu Kinetic) Importance: High Status: Triaged ** Tags: kinetic upgrade-software-version ** Also affects: nautilus (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: nautilus (Ubuntu Kinetic) Status: New => Triaged -- 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/2002575 Title: Update nautilus to 43.2 Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Kinetic: Triaged Bug description: Impact -- This is a new stable release in the GNOME 43 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS (The current version in Ubuntu 22.10 is 43.0) Test Case 1 --- Install the update Ensure that Nautilus still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2002575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002510] Re: bbswitch-dkms fails to build with jammy/linux-hwe-5.19
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2002510 Title: bbswitch-dkms fails to build with jammy/linux-hwe-5.19 Status in bbswitch package in Ubuntu: New Status in bbswitch source package in Jammy: New Bug description: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] To fix it we can take two approches: a) we import the Lunar version (0.8-14) into Jammy, and it's missing dependency (dh-dkms) or b) we apply the attached debdiff that is syncing the Jammy version up to Lunar, reverting on top the bits depending on dh-dkms. Whichever is the path of last resistance, i'm happy with it. [Regression potential] It's the same DKMS we are already using in Lunar, and it contains all the fixes upstream developed so far: Jammy and Lunar share the same base version (0.8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002573] [NEW] Printer test page still emits the pre-2022 Ubuntu logo
Public bug reported: As it says on the tin. This is on 23.04. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: bitesize ubuntu-logo ** Tags added: bitesize ubuntu-logo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/2002573 Title: Printer test page still emits the pre-2022 Ubuntu logo Status in system-config-printer package in Ubuntu: New Bug description: As it says on the tin. This is on 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/2002573/+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 2002558] Re: erro Icon connection
** Package changed: ubuntu => 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/2002558 Title: erro Icon connection Status in xorg package in Ubuntu: New Bug description: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 11 13:53:57 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6290] [17aa:397f] InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20136 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=c7305ad4-8faf-45a3-8420-afbb79aaf181 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2012 dmi.bios.release: 0.93 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G485 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G485 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:br0.93:efr0.0:svnLENOVO:pn20136:pvrLenovoG485:rvnLENOVO:rnLenovoG485:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG485:skuLENOVO_MT_20136: dmi.product.family: IDEAPAD dmi.product.name: 20136 dmi.product.sku: LENOVO_MT_20136 dmi.product.version: Lenovo G485 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2002558/+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 2002558] [NEW] erro Icon connection
You have been subscribed to a public bug: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 11 13:53:57 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6290] [17aa:397f] InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20136 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=c7305ad4-8faf-45a3-8420-afbb79aaf181 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2012 dmi.bios.release: 0.93 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G485 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G485 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:br0.93:efr0.0:svnLENOVO:pn20136:pvrLenovoG485:rvnLENOVO:rnLenovoG485:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG485:skuLENOVO_MT_20136: dmi.product.family: IDEAPAD dmi.product.name: 20136 dmi.product.sku: LENOVO_MT_20136 dmi.product.version: Lenovo G485 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic performance third-party-packages ubuntu wayland-session -- erro Icon connection https://bugs.launchpad.net/bugs/2002558 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
The proposed change breaks extraction for drivers without -open.
A more appropriate fix is to regex extract the version number:
```
version = int(re.findall("[0-9]+", package_name)[0]
```
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1993019
Title:
UnboundLocalError: local variable 'version' referenced before
assignment
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Bug description:
Hello, we received a drive-by complaint about the ubuntu-drivers
autoinstall tool:
< Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
< Fhazal> this error appear when i try to auto install recommended driver
< Fhazal> https://pastebin.com/ydZVFT24
The contents of the pastebin:
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in
nvidia_desktop_pre_installation_hook
with_nvidia_kms = version >= 470
UnboundLocalError: local variable 'version' referenced before assignment
Skimming the version on my system it sure feels plausible:
def nvidia_desktop_pre_installation_hook(to_install):
'''Applies changes that need to happen before installing the NVIDIA
drivers'''
with_nvidia_kms = False
# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
try:
version = int(package_name.split('-')[-1])
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470
if with_nvidia_kms:
set_nvidia_kms(1)
If there was an exception splitting, indexing, or converting to an
int, that 'version' variable may not have a value.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+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 2002563] [NEW] The ethernet connection icon has disappeared
Public bug reported: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 14:50:09 2023 InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.1.1 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.82 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started limited enabled enabled disabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2002563 Title: The ethernet connection icon has disappeared Status in network-manager package in Ubuntu: New Bug description: The ethernet connection icon has disappeared, it's a cosmetic problem, I can access the internet both via cable, WI-FI and VPN, I would like to report this error, as I still haven't found a solution to the problem on the internet. In settings, it also disappeared, only the VPN settings are still visible. (I used google translator, if possible answer me in Portuguese.) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 14:50:09 2023 InstallationDate: Installed on 2022-07-29 (166 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.1.1 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.82 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started limited enabled enabled disabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2002563/+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 2002228] Re: incorrect maximum window geometry on secondary monitor makes contextmenu of gtk4 apps unusable
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4790 was backported to GTK 4.8.3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2002228 Title: incorrect maximum window geometry on secondary monitor makes contextmenu of gtk4 apps unusable Status in gtk4 package in Ubuntu: New Status in sway package in Ubuntu: New Bug description: since upgrade to 22.10 gtk4 apps like nautilus on sway on the external monitors are restricted to size of the resolution of the first monitor (which is the laptop lcd, hence smaller) which results in broken apps contextmenu (like renaming files in nautilus is impossible). There is a bugreport in sway for it https://github.com/swaywm/sway/issues/7000 but i dont quite understand where the correct fix should be located: sway, wlroots, gtk4? However there seems to be a fix (workaround) for gtk4: https://gitlab.gnome.org/GNOME/gtk/-/issues/5402 -> https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4790 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: sway 1.7-5 [modified: usr/share/wayland-sessions/sway.desktop] ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Jan 8 01:04:27 2023 InstallationDate: Installed on 2022-03-24 (290 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: sway UpgradeStatus: Upgraded to kinetic on 2022-10-20 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2002228/+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 1995766] Re: X server segfault when starting youtube videos
*** This bug is a duplicate of bug 1999213 *** https://bugs.launchpad.net/bugs/1999213 Another crash: e2cad21a-91d2-11ed-9d18-fa163e993415 (I'm probably going to upgrade to 22.10 today so presumably I won't have any more.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash
[Desktop-packages] [Bug 2002521] Re: Incompatibility issue between g-c-c and libnm0
weird, what about $ ldd -r /usr/bin/gnome-control-center ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 Status in gnome-control-center package in Ubuntu: Incomplete Bug description: After system update from Ubuntu 20.04 to 22.04 settings won't open (neither using the GUI gear icon nor using the terminal command gnome- control-center). The error message it returns is "gnome-control-center: /lib/x86_64-linux-gnu/libnm.so.0: version `libnm_1_24_0' not found (required by gnome-control-center)". Have tried remove and reinstall g-c-c and libnm0 with no results. Everything is up to date but it seems that g-c-c still tries to use libnm version 1.24.0 instead of most recent (and installed on notebook) libnm 1.36.6. 1: Description: Ubuntu 22.04.1 LTS Release: 22.04 2: gnome-control-center: Instalados: 1:41.7-0ubuntu0.22.04.5 Candidato: 1:41.7-0ubuntu0.22.04.5 Tabla de versión: *** 1:41.7-0ubuntu0.22.04.5 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu13.2 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:41.4-1ubuntu12 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libnm0: Instalados: 1.36.6-0ubuntu2 Candidato: 1.36.6-0ubuntu2 Tabla de versión: *** 1.36.6-0ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.36.4-2ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3: Settings to open. 4: Didn't open. The cursor turns to the loading wheel then goes back to arrow with nothing happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 11:50:00 2023 InstallationDate: Installed on 2022-01-21 (354 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2023-01-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+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 1983794] Re: Evolution not deleting autosave files
** Description changed:
+ [ Impact ]
+
+ Autosave files are not removed from evolution local state directories
+ (and windows leaked)
+
+
+ [ Test case ]
+
+ 1. Open evolution, and start to compose a new email
+ 2. Write enough text and wait few minutes so that this command returns a file
+ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
+ 3. Close the email composer window, hitting "Do not save"
+ 4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
+ 5. Opening and closing again evolution should not ask to restore the previous
email
+
+
+ [ Regression potential ]
+
+ No sounds could be performed during some UI actions
+
+ ---
+
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was
installed with the distribution on a new system and received settings
imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string). When
the email is successfully sent, the autosave file SHOULD be deleted.
It's not. When evolution is shut down and restarted I'm asked if I want
to recover an unfinished email. Answering No to this will delete the
autosave file, but otherwise it persists and the recovery query recurs
the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people
aren't dealing with it, perhaps considering it a distro-specific bug.
On a system used by many people this is a potential security issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
In Progress
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1983794] Re: Evolution not deleting autosave files
** Also affects: evolution (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: libcanberra (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: libcanberra (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: libcanberra (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: libcanberra (Ubuntu Kinetic)
Importance: Undecided => Low
** Changed in: libcanberra (Ubuntu Kinetic)
Importance: Low => Medium
** Changed in: evolution (Ubuntu)
Importance: Medium => Low
** Changed in: libcanberra (Ubuntu Kinetic)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
In Progress
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 2002521] Re: Incompatibility issue between g-c-c and libnm0
and $ dpkg -l libnm0 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 Status in gnome-control-center package in Ubuntu: Incomplete Bug description: After system update from Ubuntu 20.04 to 22.04 settings won't open (neither using the GUI gear icon nor using the terminal command gnome- control-center). The error message it returns is "gnome-control-center: /lib/x86_64-linux-gnu/libnm.so.0: version `libnm_1_24_0' not found (required by gnome-control-center)". Have tried remove and reinstall g-c-c and libnm0 with no results. Everything is up to date but it seems that g-c-c still tries to use libnm version 1.24.0 instead of most recent (and installed on notebook) libnm 1.36.6. 1: Description: Ubuntu 22.04.1 LTS Release: 22.04 2: gnome-control-center: Instalados: 1:41.7-0ubuntu0.22.04.5 Candidato: 1:41.7-0ubuntu0.22.04.5 Tabla de versión: *** 1:41.7-0ubuntu0.22.04.5 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu13.2 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:41.4-1ubuntu12 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libnm0: Instalados: 1.36.6-0ubuntu2 Candidato: 1.36.6-0ubuntu2 Tabla de versión: *** 1.36.6-0ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.36.4-2ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3: Settings to open. 4: Didn't open. The cursor turns to the loading wheel then goes back to arrow with nothing happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 11:50:00 2023 InstallationDate: Installed on 2022-01-21 (354 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2023-01-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+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 1986168] Re: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libinput (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1986168 Title: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: 1. In 20.04 LTS I had configured the Marble Mouse by adding 39 conf etc according to https://help.ubuntu.com/community/Logitech_Marblemouse_USB 2. On upgrade to 22.04.1 LTS, these no longer work. The edits etc are still in place but the Marble Mouse buttons I configured previously are not working. Expected behavior is they should still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1986168/+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 1986168] Re: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1986168 Title: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: 1. In 20.04 LTS I had configured the Marble Mouse by adding 39 conf etc according to https://help.ubuntu.com/community/Logitech_Marblemouse_USB 2. On upgrade to 22.04.1 LTS, these no longer work. The edits etc are still in place but the Marble Mouse buttons I configured previously are not working. Expected behavior is they should still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1986168/+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 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)
Hello Daniel, Thanks you for you attention. During night I fixed the issue. I decided to update from 22.04 -> 22.10 Ubuntu. Then I added settings of module in conf file /etc/modprobe.d/i915.conf and automatically generated /etc/X11/xorg.conf file. I will send them later. Other hand was troubles with GUI (desktop setting). I switched to slim display manager (gdm not worked) under description of https://phoenixnap.com/kb/how-to-install-a-gui-on-ubuntu. There is still minor issues but it worked and I can work with Ubuntu 22.10 I will send the content of files afternoon. Best regards Marian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/2002432 Title: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load) Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I can only boot into recovery mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 10 18:45:16 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:501e] InstallationDate: Installed on 2015-11-17 (2611 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20AV002WXS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset dis_ucode_ldr i915.enable_hangcheck=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2018 dmi.bios.release: 1.93 dmi.bios.vendor: LENOVO dmi.bios.version: J4ET93WW(1.93) dmi.board.asset.tag: Not Available dmi.board.name: 20AV002WXS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540: dmi.product.family: ThinkPad L540 dmi.product.name: 20AV002WXS dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540 dmi.product.version: ThinkPad L540 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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 xserver.bootTime: Tue Jan 10 18:24:35 2023 xserver.configfile: /root/xorg.conf.new xserver.devices: xserver.errors: Server terminated with error (2). Closing log file. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:21.1.3-2ubuntu2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002432/+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 2002521] Re: Incompatibility issue between g-c-c and libnm0
Thank you for your bug report, what's the output of $ which gnome-control-center and $ ldd -r /lib/x86_64-linux-gnu/libnm.so.0 ? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 Status in gnome-control-center package in Ubuntu: Incomplete Bug description: After system update from Ubuntu 20.04 to 22.04 settings won't open (neither using the GUI gear icon nor using the terminal command gnome- control-center). The error message it returns is "gnome-control-center: /lib/x86_64-linux-gnu/libnm.so.0: version `libnm_1_24_0' not found (required by gnome-control-center)". Have tried remove and reinstall g-c-c and libnm0 with no results. Everything is up to date but it seems that g-c-c still tries to use libnm version 1.24.0 instead of most recent (and installed on notebook) libnm 1.36.6. 1: Description: Ubuntu 22.04.1 LTS Release: 22.04 2: gnome-control-center: Instalados: 1:41.7-0ubuntu0.22.04.5 Candidato: 1:41.7-0ubuntu0.22.04.5 Tabla de versión: *** 1:41.7-0ubuntu0.22.04.5 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu13.2 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:41.4-1ubuntu12 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libnm0: Instalados: 1.36.6-0ubuntu2 Candidato: 1.36.6-0ubuntu2 Tabla de versión: *** 1.36.6-0ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.36.4-2ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3: Settings to open. 4: Didn't open. The cursor turns to the loading wheel then goes back to arrow with nothing happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 11:50:00 2023 InstallationDate: Installed on 2022-01-21 (354 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2023-01-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+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 1996634] Re: xdg-email fails to execute thunderbird.desktop properly
I can confirm the existence of the bug and that applying the linked upstream commit (three lines added to the xdg-email shellscript) fixed the problem for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1996634 Title: xdg-email fails to execute thunderbird.desktop properly Status in xdg-utils package in Ubuntu: Confirmed Bug description: Kubuntu users who use thunderbird as their default mailer will not be able to open mailto: links in html pages. This appears to be a KDE- specific bug from the notes upstream. This issue has been fixed upstream, but the fixes are not yet in: ii xdg-utils 1.1.3-4.1ubuntu3~22.04.1 all desktop integration utilities from freedesktop.org The upstream commit is: https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/187 I verified that the changes in the /usr/bin/xdg-email script listed above address the issue. After applying the code changes, chrome is now able to open mailto links to launch thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1996634/+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 1996634] Re: xdg-email fails to execute thunderbird.desktop properly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xdg-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1996634 Title: xdg-email fails to execute thunderbird.desktop properly Status in xdg-utils package in Ubuntu: Confirmed Bug description: Kubuntu users who use thunderbird as their default mailer will not be able to open mailto: links in html pages. This appears to be a KDE- specific bug from the notes upstream. This issue has been fixed upstream, but the fixes are not yet in: ii xdg-utils 1.1.3-4.1ubuntu3~22.04.1 all desktop integration utilities from freedesktop.org The upstream commit is: https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/187 I verified that the changes in the /usr/bin/xdg-email script listed above address the issue. After applying the code changes, chrome is now able to open mailto links to launch thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1996634/+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 2002521] [NEW] Incompatibility issue between g-c-c and libnm0
Public bug reported: After system update from Ubuntu 20.04 to 22.04 settings won't open (neither using the GUI gear icon nor using the terminal command gnome- control-center). The error message it returns is "gnome-control-center: /lib/x86_64-linux-gnu/libnm.so.0: version `libnm_1_24_0' not found (required by gnome-control-center)". Have tried remove and reinstall g-c-c and libnm0 with no results. Everything is up to date but it seems that g-c-c still tries to use libnm version 1.24.0 instead of most recent (and installed on notebook) libnm 1.36.6. 1: Description:Ubuntu 22.04.1 LTS Release:22.04 2: gnome-control-center: Instalados: 1:41.7-0ubuntu0.22.04.5 Candidato: 1:41.7-0ubuntu0.22.04.5 Tabla de versión: *** 1:41.7-0ubuntu0.22.04.5 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu13.2 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:41.4-1ubuntu12 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libnm0: Instalados: 1.36.6-0ubuntu2 Candidato: 1.36.6-0ubuntu2 Tabla de versión: *** 1.36.6-0ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.36.4-2ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3: Settings to open. 4: Didn't open. The cursor turns to the loading wheel then goes back to arrow with nothing happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 11:50:00 2023 InstallationDate: Installed on 2022-01-21 (354 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2023-01-06 (4 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 Status in gnome-control-center package in Ubuntu: New Bug description: After system update from Ubuntu 20.04 to 22.04 settings won't open (neither using the GUI gear icon nor using the terminal command gnome- control-center). The error message it returns is "gnome-control-center: /lib/x86_64-linux-gnu/libnm.so.0: version `libnm_1_24_0' not found (required by gnome-control-center)". Have tried remove and reinstall g-c-c and libnm0 with no results. Everything is up to date but it seems that g-c-c still tries to use libnm version 1.24.0 instead of most recent (and installed on notebook) libnm 1.36.6. 1: Description: Ubuntu 22.04.1 LTS Release: 22.04 2: gnome-control-center: Instalados: 1:41.7-0ubuntu0.22.04.5 Candidato: 1:41.7-0ubuntu0.22.04.5 Tabla de versión: *** 1:41.7-0ubuntu0.22.04.5 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu13.2 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:41.4-1ubuntu12 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libnm0: Instalados: 1.36.6-0ubuntu2 Candidato: 1.36.6-0ubuntu2 Tabla de versión: *** 1.36.6-0ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.36.4-2ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3: Settings to open. 4: Didn't open. The cursor turns to the loading wheel then goes back to arrow with nothing happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 11 11:50:00 2023 InstallationDate: Installed on 2022-01-21 (354 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8
[Desktop-packages] [Bug 2002470] Re: Software & Updates - Authentication Tab - Restore Defaults - no Trusted Software Providers loaded
** Package changed: ubuntu => software-properties (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2002470 Title: Software & Updates - Authentication Tab - Restore Defaults - no Trusted Software Providers loaded Status in software-properties package in Ubuntu: New Bug description: Enabled livepatch on two cleanly installed laptops - entered settings GUI for livepatch by right-clicking on status icon and selecting 'Livepatch Settings...' - navigate to the 'Authentication' tab - click on the 'Restore Defaults' button - on one laptop, keys are loaded from the /etc/apt/ and /etc/apt/trusted.gpg.d folders - on the other, however, nothing happens / no keys are loaded even though the exact same keys are on both machines. I can't determine why these systems behave differently as they were both installed using the exact same USB media using the exact same setup process. Both laptops are configured with: Ubuntu 22.04.1 LTS Livepatch 10.4.1 Gnome Version 42.5 What I expected to happen: Authentication tab's Trusted Software Providers area gets populated with default keys - i.e., Trusted Software Providers' keys are displayed What happened instead: nothing; Authentication tab's Trusted Software Providers area remains blank - i.e., No keys are displayed in the Trusted Software Providers area I don't know if this presents a security vulnerability or not; I guess it depends on whether or not livepatch would retrieve / install packages from untrusted sources? I would expect not, but I'm not certain if that's true. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2002470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002510] Re: bbswitch-dkms fails to build with linux 5.19 on jammy
** Description changed: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] - ... + To fix it we can take two approches: + + a) we import the Lunar version (0.8-14) into Jammy, and it's missing + dependency (dh-dkms) + + or + + b) we apply the attached debdiff that is syncing the Jammy version up to + Lunar, reverting on top the bits depending on dh-dkms. + + Whichever is the path of last resistance, i'm happy with it. [Regression potential] - It's the same DKMS we are already using in Kinetic and Lunar, it's the - offically supported version (upstream doesn't have stable branches) and - it contains all the fixes so far developed upstream. + It's the same DKMS we are already using in Lunar, and it contains all + the fixes upstream developed so far: Jammy and Lunar share the same base + version (0.8). ** Patch added: "bbswitch_0.8-14ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+attachment/5640642/+files/bbswitch_0.8-14ubuntu1.debdiff ** Summary changed: - bbswitch-dkms fails to build with linux 5.19 on jammy + bbswitch-dkms fails to build with jammy/linux-hwe-5.19 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2002510 Title: bbswitch-dkms fails to build with jammy/linux-hwe-5.19 Status in bbswitch package in Ubuntu: New Status in bbswitch source package in Jammy: New Bug description: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] To fix it we can take two approches: a) we import the Lunar version (0.8-14) into Jammy, and it's missing dependency (dh-dkms) or b) we apply the attached debdiff that is syncing the Jammy version up to Lunar, reverting on top the bits depending on dh-dkms. Whichever is the path of last resistance, i'm happy with it. [Regression potential] It's the same DKMS we are already using in Lunar, and it contains all the fixes upstream developed so far: Jammy and Lunar share the same base version (0.8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002470] [NEW] Software & Updates - Authentication Tab - Restore Defaults - no Trusted Software Providers loaded
You have been subscribed to a public bug: Enabled livepatch on two cleanly installed laptops - entered settings GUI for livepatch by right-clicking on status icon and selecting 'Livepatch Settings...' - navigate to the 'Authentication' tab - click on the 'Restore Defaults' button - on one laptop, keys are loaded from the /etc/apt/ and /etc/apt/trusted.gpg.d folders - on the other, however, nothing happens / no keys are loaded even though the exact same keys are on both machines. I can't determine why these systems behave differently as they were both installed using the exact same USB media using the exact same setup process. Both laptops are configured with: Ubuntu 22.04.1 LTS Livepatch 10.4.1 Gnome Version 42.5 What I expected to happen: Authentication tab's Trusted Software Providers area gets populated with default keys - i.e., Trusted Software Providers' keys are displayed What happened instead: nothing; Authentication tab's Trusted Software Providers area remains blank - i.e., No keys are displayed in the Trusted Software Providers area I don't know if this presents a security vulnerability or not; I guess it depends on whether or not livepatch would retrieve / install packages from untrusted sources? I would expect not, but I'm not certain if that's true. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: livepatch -- Software & Updates - Authentication Tab - Restore Defaults - no Trusted Software Providers loaded https://bugs.launchpad.net/bugs/2002470 You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties 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 2002510] [NEW] bbswitch-dkms fails to build with linux 5.19 on jammy
Public bug reported: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] ... [Regression potential] It's the same DKMS we are already using in Kinetic and Lunar, it's the offically supported version (upstream doesn't have stable branches) and it contains all the fixes so far developed upstream. ** Affects: bbswitch (Ubuntu) Importance: Undecided Status: New ** Affects: bbswitch (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: [Impact] - bbswitch-dkms fails to build with linux 5.19 on jammy. + bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] ... [Regression potential] It's the same DKMS we are already using in Kinetic and Lunar, it's the offically supported version (upstream doesn't have stable branches) and it contains all the fixes so far developed upstream. ** Also affects: bbswitch (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2002510 Title: bbswitch-dkms fails to build with linux 5.19 on jammy Status in bbswitch package in Ubuntu: New Status in bbswitch source package in Jammy: New Bug description: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] ... [Regression potential] It's the same DKMS we are already using in Kinetic and Lunar, it's the offically supported version (upstream doesn't have stable branches) and it contains all the fixes so far developed upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2001911] Re: [SRU] libreoffice 7.4.4 for kinetic
** Description changed: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release - * Version 7.4.2 is currently released in kinetic and 7.4.3 in kinetic-proposed. For a list of fixed bugs compared to 7.4.3 see the list of bugs fixed in the release candidates of 7.4.4 (that's a total of ? bugs): + * Version 7.4.2 is currently released in kinetic and 7.4.3 in kinetic-proposed. For a list of fixed bugs compared to 7.4.3 see the list of bugs fixed in the release candidates of 7.4.4 (that's a total of 114 bugs): https://wiki.documentfoundation.org/Releases/7.4.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... - * [s390x] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/amd64/libr/libreoffice/20230106_232736_1d62c@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/arm64/libr/libreoffice/20230107_123110_dfe59@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/armhf/libr/libreoffice/20230107_140034_7d823@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/ppc64el/libr/libreoffice/20230107_011032_e9378@/log.gz + * [s390x] ... (not availble due to infrastructure problems) * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] - * A minor release with a total of ? bug fixes always carries the + * A minor release with a total of 114 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. ** Changed in: libreoffice (Ubuntu Kinetic) Status: New => In Progress -- 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/2001911 Title: [SRU] libreoffice 7.4.4 for kinetic Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Kinetic: In Progress Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * Version 7.4.2 is currently released in kinetic and 7.4.3 in kinetic-proposed. For a list of fixed bugs compared to 7.4.3 see the list of bugs fixed in the release candidates of 7.4.4 (that's a total of 114 bugs): https://wiki.documentfoundation.org/Releases/7.4.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA
[Desktop-packages] [Bug 2002314] Re: System freezes after locking screen with the nouveau driver
** Description changed: This is a Hybrid graphics laptop with Ubuntu 22.10 (also happened with 22.04) and xserver-xorg-video-nouveau version 1.0.17-2build1. - After locking the screen manually or automatically after the specified - timeout, the whole laptop freeze or behave extremely slow, either ways a - hard reset is a must by holding the power button to bring it back to - life. + After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. + This can happen right after the locking or after a while, but it doesn't happen if I suspended the laptop and wake it up. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: dmi.board.name: UX435EG 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.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --
