[Desktop-packages] [Bug 1999008] Re: /usr/lib/xorg/Xorg:6:xf86ModeVRefresh:drmmode_output_add_gtf_modes:drmmode_output_get_modes:xf86ProbeOutputModes:xf86InitialConfiguration
** Also affects: xorg-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Lunar) Importance: Undecided Status: New -- 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/1999008 Title: /usr/lib/xorg/Xorg:6:xf86ModeVRefresh:drmmode_output_add_gtf_modes:drmmode_output_get_modes:xf86ProbeOutputModes:xf86InitialConfiguration Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Jammy: New Status in xorg-server source package in Kinetic: New Status in xorg-server source package in Lunar: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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/xorg-server/+bug/1999008/+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 1341155] Re: Xorg crashed with SIGABRT in pci_device_next() with mesa utils
closing as fixed then ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Fix Released -- 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/1341155 Title: Xorg crashed with SIGABRT in pci_device_next() with mesa utils Status in xorg-server package in Ubuntu: Fix Released Bug description: came up when i installed mesa utils with nvidia optimus graphic card and i was testing it happend when i change from nvidia to intel after i tested glxgears ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-core 2:1.15.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Sat Jul 12 18:22:19 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1af2] InstallationDate: Installed on 2014-07-10 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) MachineType: ASUSTeK Computer Inc. UL30VT ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic root=UUID=b797dc1a-0cba-433f-89ce-7fb6e4f6d4c9 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: pci_device_next () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 pci_device_find_by_slot () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 pci_device_vgaarb_init () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 ?? () xf86BusConfig () Title: Xorg crashed with SIGABRT in pci_device_next() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL30VT dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL30VT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Jul 12 18:22:34 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4140 vendor AUO xserver.version: 2:1.15.1-0ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1341155/+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 1999008] [NEW] /usr/lib/xorg/Xorg:6:xf86ModeVRefresh:drmmode_output_add_gtf_modes:drmmode_output_get_modes:xf86ProbeOutputModes:xf86InitialConfiguration
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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: xorg-server (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Lunar) Importance: Undecided Status: New ** Tags: jammy kinetic -- 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/1999008 Title: /usr/lib/xorg/Xorg:6:xf86ModeVRefresh:drmmode_output_add_gtf_modes:drmmode_output_get_modes:xf86ProbeOutputModes:xf86InitialConfiguration Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Jammy: New Status in xorg-server source package in Kinetic: New Status in xorg-server source package in Lunar: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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/xorg-server/+bug/1999008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
Yes，the OEM project we are working on is based on a qualcomm chip
qcs410, in this BSP, we integrate an out-of-tree WiFi driver for WCN3980
(https://git.codelinaro.org/clo/la/platform/vendor/qcom-
opensource/wlan/qcacld-3.0), this driver is also used in the qualcomm
Android kernel, this driver has more features than linux in-tree
drivers. And in qcacld-3.0 driver, there are many wiphy features are set
netlink attribute NESTED flag (please see the log below), so with the
kernel 5.2 and later version, the validate_nla() will check if the
netlink message set the NLA_F_NESTED or not, if not set, the validation
will fail for qcacld-3.0 driver.
And this change is safe for in-tree drivers, since these drivers don't
have netlink attribute NESTED flag, the validate_nla() will not be
impacted even we set NLA_F_NESTED to the netlink messages.
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: [PARAM_SSID_LIST] = {
.type = NLA_NESTED },
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: [PARAM_BSSID_PREFS] = {
.type = NLA_NESTED },
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: [PARAM_BSSID_PARAMS] =
{.type = NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c:
[PARAM_ROAM_CONTROL_CONFIG] = {.type = NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: [PARAM_SCAN_FREQ_LIST]
= {.type = NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c:
[PARAM_FREQ_LIST_SCHEME] = {.type = NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c:
[QCA_ATTR_ROAM_CONTROL_SELECTION_CRITERIA] = {.type = NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: .type =
NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: .type =
NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: .type =
NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: .type =
NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: [SET_CHAN_CHAN_LIST] =
{.type = NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c: [SET_CHAN_FREQ_LIST] =
{.type = NLA_NESTED},
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c:
[STATS_SET_DATA_PKT_INFO] = {.type = NLA_NESTED },
wlan/qcacld-3.0/core/hdd/src/wlan_hdd_cfg80211.c:
VENDOR_NLA_POLICY_NESTED(qca_wlan_vendor_set_trace_level_policy),
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1998765
Title:
libnl3 3.4.0 doesn't work with WCN3980
Status in OEM Priority Project:
New
Status in libnl3 package in Ubuntu:
New
Bug description:
When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
to an AP.
I tried a different libnl3 from BSP and found that WCN3980 can work
correctly. The version used in BSP is 3.5.0.
I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the
root cause.
According to the commit, it seems that the flag should be set for kernel
later than 5.2.
[1]
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998963] Re: gnome-shell crahing after update
that fixed it now gnome-shell only needs to solve it's crashing on failing to delete problem and this will be solved -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998963 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: Incomplete Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:43:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998963/+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 1983456] Re: Context menu options are shown under dock panel and can not be chosen in Wayland sessions
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1887 https://github.com/micheleg/dash-to-dock/issues/1887 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1887 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Won't Fix => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1983456 Title: Context menu options are shown under dock panel and can not be chosen in Wayland sessions Status in Dash to dock: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1. Ubuntu 22.04.1 LTS 2. Installed packeges: ... gnome-shell-common/jammy-updates,jammy-updates,now 42.2-0ubuntu0.2 all [installed,automatic] gnome-shell-extension-appindicator/jammy,jammy,now 42-2~fakesync1 all [installed,automatic] gnome-shell-extension-desktop-icons-ng/jammy-updates,jammy-updates,now 43-2ubuntu1 all [installed,automatic] gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates,now 72~ubuntu5.22.04.1 all [installed,automatic] gnome-shell/jammy-updates,now 42.2-0ubuntu0.2 amd64 [installed,automatic] 3. Expected to choose "Property" option in right-click context menu of a folder in file manager. 4. In some position of file manager's window near middle to bottom of the screen, the context menu was shown under dock panel without possibility to choose options, the dock hides menu. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1983456/+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 1997360] Please test proposed package
Hello Sebastien, or anyone else affected, Accepted libqmi into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.32.0-1ubuntu0.22.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libmbim (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Kinetic: Fix Committed Status in libqmi source package in Kinetic: Fix Committed Status in modemmanager source package in Kinetic: Fix Committed Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997360] Re: Update from git snapshot to stable 1.20
These seem reasonable, particularly if there's later HWE updates to be made. I assume the Cert lab has some of the hardware to test on? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Kinetic: Fix Committed Status in libqmi source package in Kinetic: Fix Committed Status in modemmanager source package in Kinetic: Fix Committed Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997360] Please test proposed package
Hello Sebastien, or anyone else affected, Accepted libmbim into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libmbim/1.28.0-1~ubuntu22.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Kinetic: Fix Committed Status in libqmi source package in Kinetic: Fix Committed Status in modemmanager source package in Kinetic: Fix Committed Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997360] Re: Update from git snapshot to stable 1.20
Hello Sebastien, or anyone else affected, Accepted modemmanager into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: modemmanager (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-kinetic ** Changed in: libqmi (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Kinetic: Fix Committed Status in libqmi source package in Kinetic: Fix Committed Status in modemmanager source package in Kinetic: Fix Committed Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1995619] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load() from mozilla::detail::IntrinsicMemoryOps::
** Also affects: gjs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1995619 Title: gnome-shell crashed with SIGSEGV in std::__atomic_base::load() from mozilla::detail::IntrinsicMemoryOps::load() from mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) Status in gjs package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71 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/gjs/+bug/1995619/+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 1998963] Re: gnome-shell crahing after update
It looks like gnome-shell is repeatedly trying to delete files under /home/grizzlysmit/.config/gnome-shell/extension-updates/ and failing then vanishing (crashing?) Please try deleting all locally installed extensions: cd ~/.config/gnome-shell/extension-updates/ rm -rf * cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. ** This bug is no longer a duplicate of bug 1998962 gnome-shell crahing after update ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998963 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: Incomplete Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:43:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998963/+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 1998950] Re: GPU hang on Alder Lake laptop
** Changed in: linux Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 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 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 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/linux/+bug/1998950/+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 1998962] Re: gnome-shell crahing after update
*** This bug is a duplicate of bug 1998963 *** https://bugs.launchpad.net/bugs/1998963 ** This bug has been marked a duplicate of bug 1998963 gnome-shell crahing after update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998962 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: New Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:06:10 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998962/+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 1998893] Re: NV reverse prime HDMI has no output
Is there a particular reason why we should take the PCI-ID removals? They seem safe enough, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Triaged Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were synced from the kernel and such id's should not be in the wild. Other than that these just add id's and modify some vendor branding. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998893] Proposed package upload rejected
An upload of mesa to jammy-proposed has been rejected from the upload queue for the following reason: "Looks like there's unintentional changes in src/mesa/formats.csv". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Triaged Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were synced from the kernel and such id's should not be in the wild. Other than that these just add id's and modify some vendor branding. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998950] Re: GPU hang on Alder Lake laptop
>From the attached kernel log: [10112.178526] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:859b, in Xorg [1998] [10112.179245] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [10112.282534] i915 :00:02.0: [drm] Xorg[1998] context reset due to GPU hang [10112.282711] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 [10112.282720] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 [10112.299590] i915 :00:02.0: [drm] HuC authenticated [10112.299976] i915 :00:02.0: [drm] GuC submission enabled [10112.299977] i915 :00:02.0: [drm] GuC SLPC enabled [10124.168247] Asynchronous wait on fence :00:02.0:Xorg[1998]:6 timed out (hint:intel_atomic_commit_ready [i915]) [10124.168641] Asynchronous wait on fence :00:02.0:Xorg[1998]:6 timed out (hint:intel_atomic_commit_ready [i915]) [10135.176271] Asynchronous wait on fence :00:02.0:Xorg[1998]:6a timed out (hint:intel_atomic_commit_ready [i915]) [10135.176691] Asynchronous wait on fence :00:02.0:Xorg[1998]:6a timed out (hint:intel_atomic_commit_ready [i915]) [10145.928345] Asynchronous wait on fence :00:02.0:Xorg[1998]:6c timed out (hint:intel_atomic_commit_ready [i915]) [10145.928723] Asynchronous wait on fence :00:02.0:Xorg[1998]:6c timed out (hint:intel_atomic_commit_ready [i915]) [10157.192386] Asynchronous wait on fence :00:02.0:Xorg[1998]:74 timed out (hint:intel_atomic_commit_ready [i915]) [10157.192755] Asynchronous wait on fence :00:02.0:Xorg[1998]:74 timed out (hint:intel_atomic_commit_ready [i915]) and [12194.234423] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:859b, in Xorg [205503] [12194.235106] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [12194.338868] i915 :00:02.0: [drm] Xorg[205503] context reset due to GPU hang [12194.339052] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 [12194.339060] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 [12194.355616] i915 :00:02.0: [drm] HuC authenticated [12194.356153] i915 :00:02.0: [drm] GuC submission enabled [12194.356158] i915 :00:02.0: [drm] GuC SLPC enabled [12203.157415] Asynchronous wait on fence :00:02.0:Xorg[205503]:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12203.157795] Asynchronous wait on fence :00:02.0:Xorg[205503]:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12214.374853] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa2c! [12214.374867] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa2a! [12214.374870] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa28! [12214.374872] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa26! [12214.374875] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa24! [12214.374877] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa22! [12214.933492] Asynchronous wait on fence :00:02.0:Xorg[205503]:c timed out (hint:intel_atomic_commit_ready [i915]) [12214.933892] Asynchronous wait on fence :00:02.0:Xorg<205503>:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12214.934191] Asynchronous wait on fence :00:02.0:Xorg[205503]:c timed out (hint:intel_atomic_commit_ready [i915]) [12214.934435] Asynchronous wait on fence :00:02.0:Xorg<205503>:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12225.173469] Asynchronous wait on fence :00:02.0:Xorg[205503]:46 timed out (hint:intel_atomic_commit_ready [i915]) [12225.173793] Asynchronous wait on fence :00:02.0:Xorg[205503]:46 timed out (hint:intel_atomic_commit_ready [i915]) [12236.181623] Asynchronous wait on fence :00:02.0:Xorg[205503]:6a timed out (hint:intel_atomic_commit_ready [i915]) [12236.181806] Asynchronous wait on fence :00:02.0:Xorg<205503>:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12236.181898] Asynchronous wait on fence :00:02.0:Xorg[205503]:6a timed out (hint:intel_atomic_commit_ready [i915]) [12236.181973] Asynchronous wait on fence :00:02.0:Xorg<205503>:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12247.189660] Asynchronous wait on fence :00:02.0:Xorg[205503]:9e timed out (hint:intel_atomic_commit_ready [i915]) [12247.190077] Asynchronous wait on fence :00:02.0:Xorg[205503]:9e timed out (hint:intel_atomic_commit_ready [i915]) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6757 https://gitlab.freedesktop.org/drm/intel/-/issues/6757 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/6757 Importance: Unknown Status: Unknown ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1998950 Title: GPU hang on Alder Lake
[Desktop-packages] [Bug 1972977] Proposed package upload rejected
An upload of mesa to jammy-proposed has been rejected from the upload queue for the following reason: "Looks like there's unintentional changes in src/mesa/formats.csv". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998939] Re: constantly crashing gnome-shell
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998939 Title: constantly crashing gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Gnome shell is constantly crashing when workload is high. Gnome shell crashed constantly when I was running firefox, when I was running virtualbox. The screen becomes blank after the crash and after a few moment I am presented with a login screen. The problem is old and yet it is not fixed. I am getting annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 20:25:59 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-10-28 (39 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998939/+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 1998964] Re: Laptop wakes up from sleep when lid is closed if mouse is moved
Understandably waking up is annoying in this case but if you had an external monitor and keyboard plugged in then waking up on mouse movement would be the right thing to do. To block USB from waking the system up I would try: sudo sh -c "echo XHCI > /proc/acpi/wakeup" ** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1998964 Title: Laptop wakes up from sleep when lid is closed if mouse is moved Status in gnome-settings-daemon package in Ubuntu: Opinion Bug description: When laptop lid is closed the system goes to sleep, but wakes up if mouse is moved even if lid is still closed. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 5.18.19-051819-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 22:59:20 2022 DistUpgraded: 2022-10-24 14:48:02,231 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M] [1043:16c2] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c4) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cezanne [1043:16c2] InstallationDate: Installed on 2021-10-12 (420 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.19-051819-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash i8042.reset vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-24 (43 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1998964/+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 1985089] Re: Resizing two edge tiled windows is laggy
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-mutter-44 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/1985089 Title: Resizing two edge tiled windows is laggy Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985089/+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 1998963] Re: gnome-shell crahing after update
*** This bug is a duplicate of bug 1998962 *** https://bugs.launchpad.net/bugs/1998962 ** This bug has been marked a duplicate of bug 1998962 gnome-shell crahing after update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998963 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: New Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:43:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998963/+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 1998982] Re: Unable to configure 3 monitors
Screenshot of the display settings. ** Attachment added: "Screenshot from 2022-12-06 17-05-04.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1998982/+attachment/5634942/+files/Screenshot%20from%202022-12-06%2017-05-04.png ** Tags added: rls-kk-incoming -- 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/1998982 Title: Unable to configure 3 monitors Status in gnome-control-center package in Ubuntu: New Bug description: I recently purchased a portable USB monitor and decided to connect it to my desktop system as a 3rd monitor. For a couple of hours I was able to setup all three monitors as "joined displays" however at one point when the new monitor started powering on it would mirror one of the other two displays. Additionally, it was quite difficult to move the mouse from either of the mirrored displays to the other one. I'll attach a screenshot of how the displays section of gnome-control- center looks. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 17:05:42 2022 InstallationDate: Installed on 2018-08-10 (1579 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-12-02 (4 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-04-25T14:01:05.604406 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1998982/+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 1998982] [NEW] Unable to configure 3 monitors
Public bug reported: I recently purchased a portable USB monitor and decided to connect it to my desktop system as a 3rd monitor. For a couple of hours I was able to setup all three monitors as "joined displays" however at one point when the new monitor started powering on it would mirror one of the other two displays. Additionally, it was quite difficult to move the mouse from either of the mirrored displays to the other one. I'll attach a screenshot of how the displays section of gnome-control-center looks. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 17:05:42 2022 InstallationDate: Installed on 2018-08-10 (1579 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-12-02 (4 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-04-25T14:01:05.604406 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic rls-kk-incoming third-party-packages -- 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/1998982 Title: Unable to configure 3 monitors Status in gnome-control-center package in Ubuntu: New Bug description: I recently purchased a portable USB monitor and decided to connect it to my desktop system as a 3rd monitor. For a couple of hours I was able to setup all three monitors as "joined displays" however at one point when the new monitor started powering on it would mirror one of the other two displays. Additionally, it was quite difficult to move the mouse from either of the mirrored displays to the other one. I'll attach a screenshot of how the displays section of gnome-control- center looks. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 17:05:42 2022 InstallationDate: Installed on 2018-08-10 (1579 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-12-02 (4 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-04-25T14:01:05.604406 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1998982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1341155] Re: Xorg crashed with SIGABRT in pci_device_next() with mesa utils
Hi, That is fine, having updated I have not had a recurrence of this bug to my knowledge. Regards R. Avant On Mon, 5 Dec 2022, 6:48 pm Paul White, <1341...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. We are sorry that we do not always have the capacity to > review all reported bugs in a timely manner. > > Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. > > I'm setting the status of this bug to 'Incomplete' as it's not seen any > activity for some time. If this issue is still relevant when using a > currently maintained release of Ubuntu then please let us know which > one(s) otherwise this bug report can be left to expire in approximately > 60 days time. > > ** Changed in: xorg-server (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1378665). > https://bugs.launchpad.net/bugs/1341155 > > Title: > Xorg crashed with SIGABRT in pci_device_next() with mesa utils > > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > came up when i installed mesa utils with nvidia optimus graphic card > and i was testing it happend when i change from nvidia to intel after > i tested glxgears > > ProblemType: Crash > DistroRelease: Ubuntu 14.10 > Package: xserver-xorg-core 2:1.15.1-0ubuntu8 > ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 > Uname: Linux 3.16.0-3-generic x86_64 > .tmp.unity.support.test.0: > > ApportVersion: 2.14.4-0ubuntu2 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CrashCounter: 1 > Date: Sat Jul 12 18:22:19 2014 > DistUpgraded: Fresh install > DistroCodename: utopic > DistroVariant: ubuntu > ExecutablePath: /usr/bin/Xorg > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Mobile 4 Series Chipset Integrated Graphics > Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:1af2] > InstallationDate: Installed on 2014-07-10 (1 days ago) > InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) > MachineType: ASUSTeK Computer Inc. UL30VT > ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth > /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch > ProcEnviron: > > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic > root=UUID=b797dc1a-0cba-433f-89ce-7fb6e4f6d4c9 ro quiet splash vt.handoff=7 > Signal: 6 > SourcePackage: xorg-server > StacktraceTop: >pci_device_next () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 >pci_device_find_by_slot () from > /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 >pci_device_vgaarb_init () from > /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 >?? () >xf86BusConfig () > Title: Xorg crashed with SIGABRT in pci_device_next() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > dmi.bios.date: 07/14/2010 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 211 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UL30VT > dmi.board.vendor: ASUSTeK Computer Inc. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK Computer Inc. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: > dmi.product.name: UL30VT > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK Computer Inc. > version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.54-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.8.2-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.910-0ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.10-1ubuntu2 > xserver.bootTime: Sat Jul 12 18:22:34 2014 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: >product id4140 >vendor AUO > xserver.version: 2:1.15.1-0ubuntu8 > > To manage notifications about this bug go to: > >
[Desktop-packages] [Bug 1998253] Re: [snap] Editing identity doesn't display fields
** Changed in: thunderbird Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1998253 Title: [snap] Editing identity doesn't display fields Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: Running the thunderbird snap from latest/beta: 108.0b1-1 (277) The thunderbird snap is running on a 22.10 host that is up to date. When I go to edit the identity associated to an account, the fields I expect (server name, port, authentication) are missing and I see an empty window (see attachments). When I launch thunderbird from the cli, I see these logs when it launches and no other logs added when I open the Manage Identities -> Edit window. heather@fenrir:~$ snap run thunderbird Gtk-Message: 13:41:09.447: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [GFX1-]: glxtest: libpci missing [GFX1-]: glxtest: VA-API test failed: missing or old libva-drm library. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1998253/+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 1998253]
Pushed by alessan...@thunderbird.net: https://hg.mozilla.org/comm-central/rev/2d9e5216f608 Make the identity dialog work on small screens after bug 1796915. r=aleca -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1998253 Title: [snap] Editing identity doesn't display fields Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: Running the thunderbird snap from latest/beta: 108.0b1-1 (277) The thunderbird snap is running on a 22.10 host that is up to date. When I go to edit the identity associated to an account, the fields I expect (server name, port, authentication) are missing and I see an empty window (see attachments). When I launch thunderbird from the cli, I see these logs when it launches and no other logs added when I open the Manage Identities -> Edit window. heather@fenrir:~$ snap run thunderbird Gtk-Message: 13:41:09.447: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [GFX1-]: glxtest: libpci missing [GFX1-]: glxtest: VA-API test failed: missing or old libva-drm library. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1998253/+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 1998253]
Created attachment 9306705 Bug 1803372 - Make the identity dialog work on small screens after bug 1796915. r=aleca -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1998253 Title: [snap] Editing identity doesn't display fields Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: Running the thunderbird snap from latest/beta: 108.0b1-1 (277) The thunderbird snap is running on a 22.10 host that is up to date. When I go to edit the identity associated to an account, the fields I expect (server name, port, authentication) are missing and I see an empty window (see attachments). When I launch thunderbird from the cli, I see these logs when it launches and no other logs added when I open the Manage Identities -> Edit window. heather@fenrir:~$ snap run thunderbird Gtk-Message: 13:41:09.447: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [GFX1-]: glxtest: libpci missing [GFX1-]: glxtest: VA-API test failed: missing or old libva-drm library. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1998253/+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 1998253]
Regression window;
https://hg.mozilla.org/comm-central/pushloghtml?fromchange=5171c08d7233b84a491d3d1a13264cef3a3cb61e=35e34ed159cbb6a8407be3de30b17951b6b02737
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8a97830c36c3a6aedd56c1519773df80ddd68f9c=460e8620ad58b4d447c59e1e20ac94447979f2e6
Suspect:1ad8f3c7f4b69004bd214f56df0a51704bec8402Richard
Marti — Bug 1797337 - Port bug 1796915: Use contain rather than
min-{width,height} for scrollable dialogs. r=aleca
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1998253
Title:
[snap] Editing identity doesn't display fields
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Running the thunderbird snap from latest/beta: 108.0b1-1 (277)
The thunderbird snap is running on a 22.10 host that is up to date.
When I go to edit the identity associated to an account, the fields I
expect (server name, port, authentication) are missing and I see an
empty window (see attachments).
When I launch thunderbird from the cli, I see these logs when it
launches and no other logs added when I open the Manage Identities ->
Edit window.
heather@fenrir:~$ snap run thunderbird
Gtk-Message: 13:41:09.447: Not loading module "atk-bridge": The functionality
is provided by GTK natively. Please try to not load it.
[GFX1-]: glxtest: libpci missing
[GFX1-]: glxtest: VA-API test failed: missing or old libva-drm library.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1998253/+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 1998253]
I can confirm it with the STR from comment 0. Alice, can you give us a regression window? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1998253 Title: [snap] Editing identity doesn't display fields Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: Running the thunderbird snap from latest/beta: 108.0b1-1 (277) The thunderbird snap is running on a 22.10 host that is up to date. When I go to edit the identity associated to an account, the fields I expect (server name, port, authentication) are missing and I see an empty window (see attachments). When I launch thunderbird from the cli, I see these logs when it launches and no other logs added when I open the Manage Identities -> Edit window. heather@fenrir:~$ snap run thunderbird Gtk-Message: 13:41:09.447: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [GFX1-]: glxtest: libpci missing [GFX1-]: glxtest: VA-API test failed: missing or old libva-drm library. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1998253/+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 1990200] Re: goa-daemon crashed with SIGABRT
Unsure of librest update is installed correctly since I've never installed a package this way. The following dpkg -l shows the librest at 0.9.1.-2. 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. cliff@cliffps:/etc/apt/sources.list.d$ dpkg -l | grep librest ii librest-1.0-0:amd640.9.1-2ubuntu1 amd64 Will watch for the goa error. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Released Status in librest source package in Kinetic: Fix Committed Bug description: * Impact The gnome-online-accounts sometime crash after resuming from suspend * Test case Install the librest update, restart your system and verify that configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-calendar and the top panel widget, evolution should list your email account and nautilus should be able to browse your gdrive folder. We should also confirm that error reports stop with the library update * Regression potential The patch makes the code better handle an empty payload. The librest rdepends in the archive are gnome-initial-setup/gnome-online- accounts/gnome-maps so we should verify that those keep working as expected. - Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+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 1995245] Re: Update gnome-remote-desktop to 43.2
** Description changed: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop - except for the "New Audio Forwarding Feature" test case. + except for the "New Audio Forwarding Feature" test case and the "Basic + VNC Test Case (for Ubuntu 22.04 LTS only) What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1995245 Title: Update gnome-remote-desktop to 43.2 Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Kinetic: In Progress Bug description: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case and the "Basic VNC Test Case (for Ubuntu 22.04 LTS only) What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+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 1998966] [NEW] Update gnome-remote-desktop to 42.7
Public bug reported: Impact -- This is a new stable release in the GNOME 42 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release, 42.4: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.4...42.7 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-remote-desktop (Ubuntu) Importance: High Status: Fix Released ** Affects: gnome-remote-desktop (Ubuntu Jammy) Importance: High Status: In Progress ** Tags: jammy upgrade-software-version ** Also affects: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1998966 Title: Update gnome-remote-desktop to 42.7 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the GNOME 42 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release, 42.4: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.4...42.7 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1998966/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
@Stephan, thanks for the update. I'm not going to close it as invalid because as pointed out by people previously it seems the font didn't have the issue in past series, even if the setting is non standard and the priority low as a result there might still be an issue there. ** Changed in: gnome-font-viewer (Ubuntu) Status: Confirmed => Invalid ** Changed in: fonts-dejavu (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Invalid Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+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 1995245] Re: Update gnome-remote-desktop to 43.2
** Changed in: gnome-remote-desktop (Ubuntu Kinetic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1995245 Title: Update gnome-remote-desktop to 43.2 Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Kinetic: In Progress Bug description: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+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 1998962] Re: gnome-shell crahing after update
so this one can be closed if need be -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998962 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: New Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:06:10 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998962/+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 1998962] Re: gnome-shell crahing after update
I redid this on that box using lynx so hopefully everything is correct in that bug report -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998962 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: New Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:06:10 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998962/+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 1998964] Re: Laptop wakes up from sleep when lid is closed if mouse is moved
I don't know which package this problem involves. But I guess this problem can be easily reproduced with multiple different machines running 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/1998964 Title: Laptop wakes up from sleep when lid is closed if mouse is moved Status in xorg package in Ubuntu: New Bug description: When laptop lid is closed the system goes to sleep, but wakes up if mouse is moved even if lid is still closed. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 5.18.19-051819-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 22:59:20 2022 DistUpgraded: 2022-10-24 14:48:02,231 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M] [1043:16c2] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c4) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cezanne [1043:16c2] InstallationDate: Installed on 2021-10-12 (420 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.19-051819-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash i8042.reset vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-24 (43 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1998964/+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 1998964] [NEW] Laptop wakes up from sleep when lid is closed if mouse is moved
Public bug reported: When laptop lid is closed the system goes to sleep, but wakes up if mouse is moved even if lid is still closed. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 5.18.19-051819-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 22:59:20 2022 DistUpgraded: 2022-10-24 14:48:02,231 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M] [1043:16c2] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c4) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cezanne [1043:16c2] InstallationDate: Installed on 2021-10-12 (420 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.19-051819-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash i8042.reset vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-24 (43 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1998964 Title: Laptop wakes up from sleep when lid is closed if mouse is moved Status in xorg package in Ubuntu: New Bug description: When laptop lid is closed the system goes to sleep, but wakes up if mouse is moved even if lid is still closed. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 5.18.19-051819-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 22:59:20 2022 DistUpgraded: 2022-10-24 14:48:02,231 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M] [1043:16c2] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c4) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cezanne [1043:16c2] InstallationDate: Installed on 2021-10-12 (420 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.19-051819-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash i8042.reset vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-24 (43 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567
[Desktop-packages] [Bug 1998963] Re: gnome-shell crahing after update
I did this one using lynx on the box in question hopefully the data will be correct -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998963 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: New Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:43:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998963/+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 1998963] [NEW] gnome-shell crahing after update
Public bug reported: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:43:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998963 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: New Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:43:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998963/+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 1998962] Re: gnome-shell crahing after update
Oh it added a lot of stuff I do not know where it got those but I suspect it was from this box rather than the box in question -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998962 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: New Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:06:10 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998962/+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 1998962] [NEW] gnome-shell crahing after update
Public bug reported: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:06:10 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages ** Attachment added: "got this using `ubuntu-bug gnome-shell` on that box" https://bugs.launchpad.net/bugs/1998962/+attachment/5634890/+files/apport.gnome-shell.ictvkfgj.apport -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998962 Title: gnome-shell crahing after update Status in gnome-shell package in Ubuntu: New Bug description: I upgraded everything a few days ago and it wanted a restart so I restarted when it came back I could login, but it would boot me straight out again back to the display manager, so I tried a console that was fine, and ssh from another machine that was fine, then I just tried Xorg crashed and said something had gone wrong and gave me a button to log out tried both Xorg and wayland multiple times same problem. 1) $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 2) $ apt-cache policy gnome-shell gnome-shell: Installed: 43.0-1ubuntu2 Candidate: 43.0-1ubuntu2 Version table: *** 43.0-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to login as normal 4) I got a crash and booted out ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.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 CasperMD5CheckResult: pass Date: Wed Dec 7 07:06:10 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (220 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998962/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
This bug was fixed in the package ubuntu-release-upgrader - 1:22.04.15 --- ubuntu-release-upgrader (1:22.04.15) jammy; urgency=medium * DistUpgrade: Remove firefox from deb2snap.json (LP: #1964036) * DistUpgrade: Just pass filename to apport report (LP: #1985964) * Run pre-build.sh: updating mirrors and translations. -- Nick Rosbrook Fri, 14 Oct 2022 10:29:36 -0400 ** Changed in: ubuntu-release-upgrader (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in firefox source package in Jammy: New Status in ubuntu-release-upgrader source package in Jammy: Fix Released Bug description: [Impact] By removing the firefox deb and installing the snap instead, ubuntu- release-upgrader is subverting the logic of the firefox transitional deb. [Test Case] Perform an upgrade from focal to jammy: $ do-release-upgrade On an affected system, the firefox deb will be removed by the upgrade, and the snap will be installed instead. On a fixed system, ubuntu- release-upgrader will not remove the firefox deb, and the deb will handle the transition to the snap. [Where problems could occur] If the patch was wrong, e.g. JSON syntax error or similar, it could mess up the remaining deb2snap entries. [Original Description] 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1964036] Update Released
The verification of the Stable Release Update for ubuntu-release- upgrader has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in firefox source package in Jammy: New Status in ubuntu-release-upgrader source package in Jammy: Fix Released Bug description: [Impact] By removing the firefox deb and installing the snap instead, ubuntu- release-upgrader is subverting the logic of the firefox transitional deb. [Test Case] Perform an upgrade from focal to jammy: $ do-release-upgrade On an affected system, the firefox deb will be removed by the upgrade, and the snap will be installed instead. On a fixed system, ubuntu- release-upgrader will not remove the firefox deb, and the deb will handle the transition to the snap. [Where problems could occur] If the patch was wrong, e.g. JSON syntax error or similar, it could mess up the remaining deb2snap entries. [Original Description] 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1995245] Re: Update gnome-remote-desktop to 43.2
** Summary changed: - Update gnome-remote-desktop to 43.1 + Update gnome-remote-desktop to 43.2 ** Changed in: gnome-remote-desktop (Ubuntu) Status: Fix Released => Fix Committed ** Description changed: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- - desktop/-/compare/43.0...43.1 + desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1995245 Title: Update gnome-remote-desktop to 43.2 Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Kinetic: Triaged Bug description: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+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 1985089] Re: Resizing two edge tiled windows is laggy
** Changed in: mutter Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985089 Title: Resizing two edge tiled windows is laggy Status in Mutter: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985089/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
Looking into this again, I found that I had the following line in /etc/environment: FREETYPE_PROPERTIES="truetype:interpreter-version=35 cff:no-stem- darkening=1 autofitter:warping=1" I can't remember why I set this, probably some hinting issues in an old Xubuntu version. Removing it causes v40 of the interpreter to be used, fixing the broken letters. The font is obviously broken when used with v35, but few people are going to notice unless they're as clumsy as me, so you may want to close the ticket. I also found out that `ftview` from the freetype2-demos package is great for investigating these issues, as it lets you cycle through all the relevant settings. Thanks for your help and apologies for not realising that I had a non- standard setup. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+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 1998950] [NEW] GPU hang on Alder Lake laptop
Public bug reported: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 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 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze kinetic 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/1998950 Title: GPU hang on Alder Lake laptop Status in xorg package in Ubuntu: New Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1851067] Re: Unnecessary Delays Recovering from Screen Lock
** Changed in: gnome-control-center Status: New => Fix Released -- 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/1851067 Title: Unnecessary Delays Recovering from Screen Lock Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Bug description: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off: https://gitlab.gnome.org/GNOME/gnome-control- center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png **Side-note:** this is bad terminology because your screen will still go into the exact same state that "Screen Lock: On" accomplishes (upon an inactivity timeout), but the only difference is that you won't have to enter your password to regain access to the desktop. I would have named this "Require Password Authentication After Inactivity Timeout" (to me wordy is better than unclear). While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of things. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press the "enter" key. I want to be able to accomplish this also by moving my mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. Also, there should be separate setting for "blank screen x time", and "monitor power off after x time". My ideal settings would to make the screen go black after 5 minutes of inactively and to turn my monitors completely off after 15 minutes of inactively, and I'd like to control whether each of these requires password authentication or not. On the 5 minute one, I personally would note require a password, but I would require a password after monitor going off. However, on either of these, I expect the desktop to be fully functional immediately after coming out of these states. At the very least please remove these unnecessary delays. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+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 1998676] Re: The link to Java has been changed
** Description changed: -- 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/1998676 Title: The link to Java has been changed Status in libreoffice package in Ubuntu: New Bug description: I want to produce labels for my Christmas cards. I have added the database for 2022 in Tools > Options > LibreOffice Base > Databases. It is called CardList2022.odb. When I test this new database I do not get an error message. I am using a LibreOffice Spreadsheet CardList2022.ods to hold my list of Cards. The database shows it as a table. I then go File > New > Labels in a Writer document and select the 2022 database. However, when I try to select a Table nothing is shown and there are no Database fields. If I choose 'New Document' nothing is shown. I would expect to have a sheet of names and addresses. The Ubuntu release I am using is 22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1998676/+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 305927] Re: gedit leaks memory
Bug report did not close due to bug watch Initial reports were about GNOME 2 version of gedit Upstream issue closed "RESOLVED OBSOLETE" on 2020-11-24 No reply to comment #10 after almost 4 years so closing ** Changed in: gedit (Ubuntu) Status: Incomplete => Invalid ** Changed in: gedit (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/305927 Title: gedit leaks memory Status in gedit: Confirmed Status in gedit package in Ubuntu: Invalid Bug description: Binary package hint: gedit It seems gedit doesn't release the memory used to open a file when closing it making it so use ridiculous space in ram for little files if you opened a big file and closed it. Strangely gnome system monitor reports a lower memory use under the processes tab, but reports the used ram in the resources tab and top actually gives the high amounts of used ram. To try this: 1- open gedit 2- open top 3- notice the ram use: 19393 weltall 20 0 38980 19m 10m S0 0.7 0:00.79 gedit 4- get a big file to open (mysql dumps are the best to try. I've tried with a ~50 mb dump) 5- you will notice an higher ram use, for sure > 300mb to open a 50mb file is a bit excessive but this is still an optimization issue which goes beyond this bug report: 19393 weltall 20 0 342m 305m 12m S2 10.1 3:02.14 gedit 6- close the tab which had the file 7- check again top no changes in ram use: 19393 weltall 20 0 342m 305m 12m S0 10.1 3:02.85 gedit this is definitely a memory leak or a bad ram retaining for future use implementation 8- try to reopen the file, gedit will take the same time to parse the file, but the increase of ram use is more little: 19393 weltall 20 0 381m 345m 12m S0 11.4 6:01.23 gedit 9- close the file again the ram use doesn't change again other gnome applications have similar leak issues like nautilus which after some days takes more than 300mb like nothing and closing windows doesn't release ram so maybe the problem might reside in underlying libraries. It seems applications like geany actually releases correctly the ram but i didn't investigate if they use similar libraries i'm using ubuntu intrepid with all the updates from normal repositories (altough this bug has been present since various releases) Description: Ubuntu 8.10 Release: 8.10 gedit: Installed: 2.24.2-0ubuntu1 Candidate: 2.24.2-0ubuntu1 Version table: *** 2.24.2-0ubuntu1 0 500 http://it.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 2.24.0-0ubuntu1 0 500 http://it.archive.ubuntu.com intrepid/main Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/305927/+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 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour
Bug report did not expire due to bug watch Upstream issue closed "RESOLVED OBSOLETE" on 2020-11-24 No reply to comment #15 after 4 years so closing ** Changed in: gedit (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consistently show wrong behaviour Status in gedit: Confirmed Status in gedit package in Ubuntu: Invalid Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1516713/+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 1636406] Re: UnknownMethod DescribeAll
Bug did not expire due to bug watch Upstream issue closed "RESOLVED OBSOLETE" on 2020-11-24 No reply to comment #3 after more than 4 years so closing ** Changed in: gedit (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1636406 Title: UnknownMethod DescribeAll Status in gedit: Confirmed Status in gedit package in Ubuntu: Invalid Bug description: Running gedit with -s -w fails: $ gedit -s -w bla.txt Failed to register: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "DescribeAll" with signature "" on interface "org.gtk.Actions" doesn't exist Omitting the -w parameter however works correctly and the calling process is blocked, so perhaps the -w parameter is no longer needed? Anyway, just wanted you to know that -w is borked. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gedit 3.22.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 25 11:25:15 2016 InstallationDate: Installed on 2016-09-05 (49 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gedit UpgradeStatus: Upgraded to yakkety on 2016-09-30 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1636406/+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 1728053] Re: Copy to USB is very slow
Bug report did not expire due to bug watch Upstream issue was closed "RESOLVED NOTGNOME" on 2017-10-31 No reply to comment #10 after almost four years so closing ** Changed in: nautilus (Ubuntu) Status: Incomplete => 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/1728053 Title: Copy to USB is very slow Status in nautilus package in Ubuntu: Invalid Bug description: Ubuntu 16.04.3 LTS from 32 bit machines to a USB stick or winchester, the speed is approx. starting at 25MB/s, it slows down to 100kB/s. At the end of the copying, you will stand for a long time. A ca. Copy the 1.5GB file to approx. it lasts for 20 minutes: unusable ... Ports and Devices: USB2 and USB3. 4.10.0-37-generic #41~16.04.1-Ubuntu SMP Fri Oct 6 22:42:22 UTC 2017 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1728053/+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 1998939] [NEW] constantly crashing gnome-shell
Public bug reported: Gnome shell is constantly crashing when workload is high. Gnome shell crashed constantly when I was running firefox, when I was running virtualbox. The screen becomes blank after the crash and after a few moment I am presented with a login screen. The problem is old and yet it is not fixed. I am getting annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 20:25:59 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-10-28 (39 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998939 Title: constantly crashing gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell is constantly crashing when workload is high. Gnome shell crashed constantly when I was running firefox, when I was running virtualbox. The screen becomes blank after the crash and after a few moment I am presented with a login screen. The problem is old and yet it is not fixed. I am getting annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 6 20:25:59 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-10-28 (39 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998939/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
For printing PDFs via command line, it is "lp -o print-scaling=none ...". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Does Inkscape's print dialog not have something like a "Print Scaling" option with choices like "Auto", "Auto Fill", "Fit", "Fill", and "None"? If there is such an option you have to set it to "None", this leaves the input document in its original size. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
In order to work around this I first printed my labels to a PDF file in LibreOffice, then printed that file with 101.5% scaling. I had to do it this way because LibreOffice does not use the standard printer dialog - the scaling option is not shown. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] [NEW] Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Public bug reported: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
** Also affects: spirv-llvm-translator-15 (Ubuntu) Importance: Undecided Status: New ** Changed in: spirv-llvm-translator-15 (Ubuntu) Status: New => Invalid ** Changed in: spirv-llvm-translator-15 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: In Progress Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 830949] Re: [Intel N10 Graphics] Need Compiz' "Copy to Texture" plugin so can display on multi-head layouts bigger than the max GL texture size
APK LEGEND is one of the best platforms to provide the latest gaming apps or tools. We do provide the latest apps that are in high demand in the online market. We upload apps and files that aren’t available on Google Play Store. Users or visitors can get accurate apk files according to their preferences. https://apklegend.net/ -- 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/830949 Title: [Intel N10 Graphics] Need Compiz' "Copy to Texture" plugin so can display on multi-head layouts bigger than the max GL texture size Status in Compiz: New Status in Unity: Won't Fix Status in compiz package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in compiz source package in Oneiric: Won't Fix Status in xserver-xorg-video-intel source package in Oneiric: Invalid Status in compiz source package in Precise: Invalid Status in xserver-xorg-video-intel source package in Precise: Invalid Bug description: This is part of the master bug 824099 Oneiric Alpha 3 installed on this system. Under testing, one test is to plug in an external monitor and ensure that external video functions properly. On this EeePC, it does not. (See photo attached to this bug). Once the external montior is plugged in, both the primary display and the external display are horribly garbled. The only thing that exists on the screen that's remotely readable is the panel at the top. The rest of the desktop area is just a mess. Affected systems: Dell Latitude 2110 (Intel Corporation: N10 Family Integrated Graphics Controller) Asus EeePC 1001PXD (Intel Corporation: N10 Family Integrated Graphics Controller) Asus EeePC 1011PX (Intel Corporation: N10 Family Integrated Graphics Controller) Asus EeePC 1015PX (Intel Corporation: N10 Family Integrated Graphics Controller) Dell Mini 10 (Intel Corporation: N10 Family Integrated Graphics Controller) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/830949/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
** Description changed: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap + + Bootstrapping plan: + - s-l-t-14 built from NEW + - llvm-15 built with s-l-t-14 + - s-l-t-15 built against llvm-15 + - llvm-15 built again with s-l-t-15 + -> mesa ready for building + + [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: In Progress Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-llvm-translator-14 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
I just noticed that this font (and many others) are marked as "experimental" even in the most recent version of the source [0] [1]. So it might be broken in some scenarios. I opened an issue to clarify if that might be the case [2]. Meanwhile, if you change your XFCE font settings like mentioned above, does it help? [0] - https://git.launchpad.net/ubuntu/+source/fonts-dejavu/tree/README.md?h=applied/ubuntu/kinetic [1] - https://github.com/dejavu-fonts/dejavu-fonts/blob/master/README.md [2] - https://gitlab.freedesktop.org/freetype/freetype/-/issues/1193 ** Bug watch added: gitlab.freedesktop.org/freetype/freetype/-/issues #1193 https://gitlab.freedesktop.org/freetype/freetype/-/issues/1193 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+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 1988230] Re: glib 2.73 breaks modemmanager
** Changed in: glib2.0 (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1988230 Title: glib 2.73 breaks modemmanager Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: I'm filing this bug in case we want to fix it before letting glib 2.73 in to kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1988230/+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 1995743] Re: webdav error trying to connect to nextcloud
For those having the same problem: You can simply replace the URL to open in order to make it work. Instead of /remote.php/dav/files/$USERNAME you can use /remote.php/webdav/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1995743 Title: webdav error trying to connect to nextcloud Status in gvfs package in Ubuntu: Confirmed Bug description: upgraded to ubuntu 22.10 from 22.04 and webdav fails to connect to nextcloud. Reimaged back to 22.04 and it worked. Error message is "Message recipient disconnected from message bus without replying Please select another viewer and try again." I have tried webdav from mate 22.10 and gnome 22.10 with same failure. Crash report fails as well but I was able to get a copy before deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1995743/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
** Description changed: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 - spirv-llvm-translator + spirv-llvm-translator-14 - needed to bootstrap libclc from llvm + + spirv-llvm-translator-15 + - needed for the actual libclc-15 after initial bootstrap [Test case] Install the new mesa on various hw, see that everything still works like before or better. - [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: In Progress Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-llvm-translator-14 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1996490] Re: Failed to set resolutions with 2.5k@90Hz panels
This bug was fixed in the package xorg-server - 2:21.1.4-2ubuntu1.2 --- xorg-server (2:21.1.4-2ubuntu1.2) kinetic; urgency=medium * re-calculate-the-clock-and-refresh-rate.diff: Fix modes on 2.5k@90Hz panels. (LP: #1996490) -- Timo Aaltonen Fri, 25 Nov 2022 13:59:07 +0200 ** Changed in: xorg-server (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- 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/1996490 Title: Failed to set resolutions with 2.5k@90Hz panels Status in HWE Next: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: In Progress Status in xorg-server source package in Jammy: Fix Released Status in xorg-server source package in Kinetic: Fix Released Status in xorg-server source package in Lunar: In Progress Bug description: [Impact] Failed to set resolutions with new 2.5k@90Hz panels, the reported resolutions from xrandr are all invalid and got blank screen. [Fix] Below commit re-calculate clock and refresh rate fixes this issue. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993 [Test] Verified on 2.5k@90Hz panel laptops and my laptop 1920x1080@60Hz Will be tested in proposed for wider range. [Where problems could occur] Not sure if the re-calculated clock and refresh rate works for all different panels, need to verify it wider in proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996490/+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)]
I don't want to be waiting indefinitely for Mesa to get fixed (which is GNOME's position right now) so have proposed a patch for Ubuntu: https://salsa.debian.org/gnome-team/mutter/-/merge_requests/86 -- 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: New Status in mutter package in Ubuntu: In Progress 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 1993992] Re: kinetic.xml has wrong filename for a wallpaper
@Brian, that's not the installer slideshow sorry if that was confusing. The desktop has a feature where it can rotate during the day through a set of images, each cycle we include a such entry with the current wallpapers. ** Changed in: ubuntu-wallpapers (Ubuntu Kinetic) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1993992 Title: kinetic.xml has wrong filename for a wallpaper Status in ubuntu-wallpapers package in Ubuntu: Fix Released Status in ubuntu-wallpapers source package in Kinetic: New Bug description: * Impact One of the kinetic wallpapers is incorrectly referenced in the xml definition which makes the image not used by the slideshow * Test case Selected the kinetic slideshow in the backgrounds settings, it should alternate through every image in the set including Twisted_Gradients_by_Gustavo_Brenner * Regression potential The change update filename is the xml definition, check that the background settings correct lists the images and that the slideshow works as expected --- In the kinetic wallpaper package, the kinetic.xml file that handles the rotating background has the wrong filename for "/usr/share/backgrounds/Twisted_Gradients_by_Gustavo_Brenner.png". It uses ".jpg" instead of the correct ".png" extension. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1993992/+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
