codehenry / xmonad

Automatically exported from code.google.com/p/xmonad
0 stars 0 forks source link

Google Hangouts screen sharing crashes #527

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
1. Open a new Google Hangout

2. Press "Share your screen"

3. The window for selecting the window to share appears for a fraction of a 
second and then the hangout crashes. 

I am using xmonad 0.11 on Gentoo without any additional configuration changes. 
The same functionality works with other window managers, also other tiling ones.

Original issue reported on code.google.com by szty...@gmail.com on 24 Jan 2013 at 8:33

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I have the same issue

Original comment by codd...@gmail.com on 4 Apr 2014 at 9:37

GoogleCodeExporter commented 8 years ago
Same issue happens for me on Arch with 0.11.

Original comment by lambdatr...@gmail.com on 4 Apr 2014 at 6:04

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
How to solve this problem?

Original comment by codd...@gmail.com on 5 Nov 2014 at 7:09

GoogleCodeExporter commented 8 years ago
I have the same problem, I cannot share my screen anymore.

Original comment by rvign...@gmail.com on 12 Jan 2015 at 5:25

GoogleCodeExporter commented 8 years ago
I have the same issue, I attach some debug information.

[024:306] 0x7f814a62e670: C->F: ["setshareoptions","","c17395517021261106635_NMS",0,{"fps":5,"maxPixels":2400000 }] [024:306] 0x7f814a62e670: C->F: ["share-pick","","c17395517021261106635_NMS",0,{"titleHint":null,"onlyShowHinted Titles":false,"onlyShowDesktops":false}] The program 'GoogleTalkPlugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAtom (invalid Atom parameter)'. (Details: serial 400 error_code 5 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

Original comment by eloy...@gmail.com on 13 Jan 2015 at 7:48

GoogleCodeExporter commented 8 years ago
I have had this issue with many different tiling window managers, except for 
i3. On the dwm mailing list someone suggested this fix:

xprop -root -f _NET_CLIENT_LIST_STACKING 32x -set _NET_CLIENT_LIST_STACKING 0

Maybe it is relevant to xmonad too, I haven't actually tried it.

Original comment by szty...@gmail.com on 13 Jan 2015 at 7:51

GoogleCodeExporter commented 8 years ago
xprop -root -f _NET_CLIENT_LIST_STACKING 32x -set _NET_CLIENT_LIST_STACKING 0
This hack fixes the problem even for XMonad

Original comment by ext.mnai...@kyriba.com on 19 May 2015 at 3:06