FS#56634 - [gjs] GNOME shell hangs when dragging window across workspaces after updating gjs
Attached to Project:
Arch Linux
Opened by Max Bruckner (FSMaxB) - Friday, 08 December 2017, 15:01 GMT
Last edited by Jan de Groot (JGC) - Friday, 15 December 2017, 23:08 GMT
Opened by Max Bruckner (FSMaxB) - Friday, 08 December 2017, 15:01 GMT
Last edited by Jan de Groot (JGC) - Friday, 15 December 2017, 23:08 GMT
|
Details
Description:
I did a full system update and suddenly GNOME started to hang immediately once I tried to drag a window to another workspace. By hang I mean that it doesn't react to keystrokes or mouseclicks anymore and is stuck in the window overview screen. Sometimes some of the windows rearrange in the overview, but other than that, nothing happens. While hanging, the cursor has an arrow shape, similar to the one when resizing windows. Analysing the list of updated packages, I found out that gjs was the cause. I did a git bisect and the offending commit seems to be: 85f88a18faef28cd5ec09817d048082ec1f6bd97 object: check in gjs_typecheck_object if the object has been finalized For bisection I used the PKGBUILD of gjs-1.50.2+8+gb65c785-1. In order to get it to build, I needed to comment out the `git revert -n` line in the PKGBUILD for all commits before 85f88a18faef28cd5ec09817d048082ec1f6bd97. I didn't test newer versions of gjs so far. I also didn't test a different computer. Additional info: * good package: 1.50.2 * back package: 1.50.2+8+gb65c785-1 * proprietary nvidia driver (nvidia-dkms) * Xorg Steps to reproduce: Install the bad version of gjs. Log into GNOME and try to drag a window to a different workspace. |
This task depends upon
Closed by Jan de Groot (JGC)
Friday, 15 December 2017, 23:08 GMT
Reason for closing: Fixed
Additional comments about closing: gjs was reverted to last stable release.
Friday, 15 December 2017, 23:08 GMT
Reason for closing: Fixed
Additional comments about closing: gjs was reverted to last stable release.
I also tested 1.51.2 and the issue doesn't happen with that newer version. I'll try to bisect the fix, although I'm not sure if that makes sense since I think that the commit that broke things is not ancestor of 1.51.2.
Now it is broken by 40084ad481771f85f0dd183d3e07c9d3ceefa4a6 object: check in gjs_typecheck_object if the object has been finalized
Which seems to be the same commit but cherry-picked.