[Ubuntu-x-swat] [Bug 1948978] Re: Thunderbird write e-mail window never released in wayland
*** This bug is a duplicate of bug 1932328 *** https://bugs.launchpad.net/bugs/1932328 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1932328, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1932328 Thunderbird under Wayland does not correctly close (or manage) windows -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1948978 Title: Thunderbird write e-mail window never released in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1948978/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1948978] [NEW] Thunderbird write e-mail window never released in wayland
Public bug reported: If I run Thunderbird (latest version), when I write an e-mail or reply to an e-mail, a new window opens. When I send the e-mail, it works correctly and the e-mail is sent, but the red dot on the Thunderbird icon on the task bar never goes out. If I close or pkill Thunderbird, only the main Thunderbird window is released by the display manager and it is not possible to open Thunderbird again without logging out or restarting gdm3. This is with Wayland. There is no Thunderbird process left to kill. Everything works fine with Xorg, so on this computer running 21.10, I will be using Xorg instead of Wayland for now. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 27 14:53:29 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff67] Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff67] InstallationDate: Installed on 2020-03-06 (600 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: TOSHIBA Satellite L305 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=baeb07e4-08ee-4d13-be78-7571c5723e1d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2009 dmi.bios.vendor: INSYDE dmi.bios.version: 2.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.20:bd12/09/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-04X02F:skuMontevina_Fab:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L305 dmi.product.sku: Montevina_Fab dmi.product.version: PSLB8U-04X02F dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1948978 Title: Thunderbird write e-mail window never released in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1948978/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
The reverts are in the latest firmware tree: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d7b50e61669dc137924337d03d09b8986eb752a3 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d843e520a4b0d92b986645548d11ade3b9b239a4 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=99d72504bff7ab40c261b8509c0b9d8abf98b296 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1946359] Re: [MIR] vulkan-tools
-- src:vulkan (Bionic) --
[Summary]
TODO: MIR team ACK, pending some requested changes (see below) and security
review.
The legacy src:vulkan package is quite big and contains embedded sources. It is
of much bigger scope than the vulkan-tools and vulkan-loader packages there
were split out of it in newer series. Any required changes would need to be
SRUed into Bionic first. I wonder if this is really worth the effort to get it
MIRed? I'd also like to ask for a security review with special regard to the
embedded sources, as those have not been covered by the newer vulkan-loader MIR
(LP: #1742711).
This does need a security review, so I'll assign ubuntu-security
List of specific binary packages to be promoted to main: vulkan-utils,
libvulkan1 (libvulkan-dev can be excluded)
Notes:
The src:vulkan MIR in Bionic basically combines the MIRs of src:vulkan-loader
(libvulkan1) and src:vulkan-tools (vulkan-utils) that are already (being)
accepted in newer series. Therefore, it is pretty similar to the "vulkan-tools"
MIR above and the "vulkan-loader" MIR in LP: #1742711, but due to embedded
sources it is of much bigger scope.
Required TODOs:
* get rid of the embedded sources (or take maintenance of those, in
coordination with the security team)
* make use of the integrated test suite, so that it fails the build if any
tests fails
* keep track of symbol names & changes in a debian/libvulkan1.symbols file
Recommended TODOs:
* Add a team bug subscriber
* add autopkgtests
* fix lintian errors
* fix some build warnings
[Duplication]
* There is no other package in main providing the same functionality.
[Dependencies]
OK:
* no other Dependencies to MIR due to this (quilt is only a build-dep)
* No dependencies in main that are only superficially tested requiring more
tests now?
[Embedded sources and static linking]
OK:
* no static linking (some static linking in loader/ and external/glsl is only
used for Windows builds)
Problems:
* embedded glslang, spirv-{tools,headers}, hlsl, glm and vkjson sources
[Security]
OK:
* history of CVEs does not look concerning
* does not run a daemon as root
* does not use webkit1,2
* does not use lib*v8 directly
* does not parse data formats
* does not open a port
* does not process arbitrary web content
* does not use centralized online accounts
* does not integrate arbitrary javascript into the desktop
* does not deal with system authentication (eg, pam), etc)
[Common blockers]
OK:
* does not FTBFS currently
* no translation present, but none needed for this case (user visible)?
* not a python/go package, no extra constraints to consider in that regard
Problems:
* does have a test suite, but that doesn't seem to run during build
* no autopkgtest
[Packaging red flags]
OK:
* Ubuntu does not carry a delta (but might need one to carry the proposed
changes)
* d/watch is present and looks ok (if needed, e.g. non-native)
* the current release is packaged (almost, lacking 1 release behind, afterwards
the package was split into vulkan-loader and vulkan-tools)
* Upstream update history is good
* Debian/Ubuntu update history is slow (but acceptable)
* promoting this does not seem to cause issues for MOTUs that so far maintained
the package
* d/rules is rather clean
* Does not have Built-Using
* is not on the lto-disabled list (LTO hasn't been a thing for Bionic)
Recommendation:
* fix lintian errors (those only affect libvulkan-dev, that we do not want to
promote):
+ E: libvulkan-dev: missing-dependency-on-libc needed by
usr/lib/x86_64-linux-gnu/libVkLayer_core_validation.so and 5 others (missing
${shlibs:Depends}?)
+ E: libvulkan-dev: package-must-activate-ldconfig-trigger
usr/lib/x86_64-linux-gnu/libVkLayer_utils.so
Problems:
* symbols tracking is NOT in place
[Upstream red flags]
OK:
* no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests)
* no use of user nobody
* no use of setuid
* no important open bugs (crashers, etc) in Debian or Ubuntu
* no dependency on webkit, qtwebkit, seed or libgoa-*
* not part of the UI for extra checks
Recommended:
* There is some fishy usage of malloc (passing the argument count into malloc)
in cube.c and cube.cpp inside the "WinMain" function, but this seems to be
unused inside the linux build.
* attempt to fix external/glslang build warnings
+ glslang/MachineIndependent/attribute.cpp:85:16: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
+ SPIRV/GlslangToSpv.cpp:780:38: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
* attempt to fix vulkan build warnings:
+ layers/vk_layer_logging.h:1029:13: warning: ‘void
InsertCmdDebugUtilsLabel(debug_report_data*, VkCommandBuffer, const
VkDebugUtilsLabelEXT*)’ defined but not used [-Wunused-function]
+ layers/vk_layer_logging.h:1013:13: warning: ‘void
EndCmdDebugUtilsLabel(debug_report_data*, VkCommandBuffer)’ defined but not
used [-Wunused-function]
+
[Ubuntu-x-swat] [Bug 1946359] Re: [MIR] vulkan-tools
Hi Miriam! I checked the vulkan-tools MIR for Jammy/Impish/Hirsute/Focal, which looks rather straight forwards, but requires a few additional changes before the MIR team can give the final ACK. Also, I checked the vulkan MIR for Bionic, that seems to be much more complicated. Please see my remarks in the next comment. I will be requesting security review for this one, too. -- vulkan-tools -- [Summary] TODO: MIR team ACK, pending some requested changes (see below). This MIR is looking pretty good overall, I do not see any big security constraints and I think we do not need a security review. But the proposed autopkgtests should be integrated and a build-time test suite needs to be added in addition to integrating the LTO workaround (or fix) into the package itself. All of those changes need to be SRUed into the stable series down to Focal/Bionic. This does NOT need a security review List of specific binary packages to be promoted to main: vulkan-tools (we can probably skip the transitional vulkan-utils package). Notes: As this MIR is to be backdated to Hirsute/Focal (and Bionic for src:vulkan) we need the proposed changes to be SRUed to those series first. (see https://wiki.ubuntu.com/StableReleaseUpdates) Required TODOs: * Add build-time tests that fail the build if they don't pass * Integrate the proposed autopkgtests * avoid the lto-disabled list (for arm64), should be fixed (or worked around) inside the package itself * SRU those changes down to the stable series (Impish/Hirsute/Focal/Bionic) Recommended TODOs: * Add a team bug subscriber * Check build warning (in Focal version): "cube.cpp:2067:38: warning: ‘void* memset(void*, int, size_t)’ clearing an object of non-trivial type" * Try to keep vulkan-tools more up-to-date in the future [Duplication] * There is no other package in main providing the same functionality. [Dependencies] OK: * no other Dependencies to MIR due to this (glslang-tools is only a build-dep, all others are in main already) * No dependencies in main that are only superficially tested requiring more tests now [Embedded sources and static linking] OK: * no embedded source present * no static linking [Security] OK: * history of CVEs does not look concerning (no CVEs found) * does not run a daemon as root * does not use webkit1,2 * does not use lib*v8 directly * does not parse data formats * does not open a port * does not process arbitrary web content * does not use centralized online accounts * does not integrate arbitrary javascript into the desktop * does not deal with system authentication (eg, pam), etc) [Common blockers] OK: * does not FTBFS currently * no translation present, but none needed for this case (user visible)? * not a python/go package, no extra constraints to consider in that regard Recommended: * The package does not contain any autopkgtests. Those are being prepared but we want them to be inside the archive and SRUed to all relevant series (i.e. down to Focal/Bionic): https://git.launchpad.net/~mirespace/+git/vulkan-tools/log/?h=impish-vulkan-tools-adding-dep8-tests Problems: * does NOT have a test suite that runs at build time and fails the build upon error. (Maybe use something similar to what is described in BUILD.md -> ### Linux Tests or run the proposed autopkgtest during build, too?) [Packaging red flags] OK: * Ubuntu does carry a delta, but it is reasonable and maintenance under control (adding tests, will be submitted to Debian, too) * symbols tracking not applicable for this kind of code. * d/watch is present and looks ok (if needed, e.g. non-native) * Upstream update history is good * Debian/Ubuntu update history is slow, but reasonable * promoting this does not seem to cause issues for MOTUs that so far maintained the package * no massive Lintian warnings * d/rules is rather clean * Does not have Built-Using Recommended: * the current release is NOT packaged (upstream at v1.2.196, Debian at v1.2.189, Ubuntu at v1.2.162) Problems: * is on the lto-disabled list (for arm64), this should be fixed or the workaround should be included directly in the package [Upstream red flags] OK: * no incautious use of malloc/sprintf (as far as I can check it) * no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests) * no use of user nobody * no use of setuid * no important open bugs (crashers, etc) in Debian or Ubuntu * no dependency on webkit, qtwebkit, seed or libgoa-* * not part of the UI for extra checks Recommended: * Focal version shows errors during build (that seems to be fixed in later versions): "cube.cpp:2067:38: warning: ‘void* memset(void*, int, size_t)’ clearing an object of non-trivial type ‘struct vk::SubresourceLayout’; use assignment or value-initialization instead [-Wclass-memaccess]" * There is some fishy usage of malloc (passing the argument count into malloc) in cube.c and cube.cpp inside the "WinMain" function, but this seems to be unused inside the linux build. -- You
[Ubuntu-x-swat] [Bug 1947677] Re: Colemak keyboard layout's left-hand backspace is also acting as Caps Lock
I have since found that executing in Terminal, the command 횡횖횘획횖횊횙 -횎 "회횕횎횊횛 홻횘회횔" is a temporary workaround to fix this behaviour; however, I would definitely think this issue should be fixed so it works out-of-the-box for new users. It's a very problematic behaviour for one's primary backspace to be also toggling caps lock, affecting daily typing. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1947677 Title: Colemak keyboard layout's left-hand backspace is also acting as Caps Lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947677/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Hi. I'm picking up this ticket from Seth. Reading through the history it seems it's still an open issue? My understanding is that upstream 'fixed' this by reverting fw blobs in version 20210818. I can produce a linux-firmware test package for hirsute 20.04 with these reverts if necessary. Just let me know. ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
