Hi, Lots of titling WMs seem to have this issue, in Xmonad it's the same for example, I didn't manage to track it down despite debugging attempts, I know too little about X or WMs. For what it's worth, It works with the awesome WM, and with i3 which I use now - pity, because I liked dwm much more in general, but I need the hangouts for work.
Cheers, Jarosław Rzeszótko 2014-02-27 1:36 GMT+01:00 <meta...@gmail.com>: > was this resolved? having the same trouble with cwm, latest chromium and > latest googletalk-plugin > > > On Tuesday, January 22, 2013 2:56:20 PM UTC+1, Jarosław Rzeszótko wrote: >> >> Hi, >> >> The plugin also outputs some debugging information to the console, >> maybe this will be more helpful: >> >> >> 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 503 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.) >> >> >> Cheers, >> Jarosław Rzeszótko >> >> 2013/1/22 Jarosław Rzeszótko <szt...@gmail.com>: >> > Hi, >> > >> > I attach straces from dwm (crash) and from awesome for comparision (no >> > crash). The turning point seems to be the attempt to clone some >> > process and then the program crashes with the select call visible in >> > the strace (this is the last call before a segfault, then the program >> > and strace exit). The part of the gdb stack trace from the segfault >> > that is still readable starts like this: >> > >> > #8 0xb7766d4b in start_thread () from /lib/libpthread.so.0 >> > #9 0xb6df451e in clone () from /lib/libc.so.6 >> > >> > Maybe it is some kind of a thread-safety issue? I know too little >> > about window managers to investigate further on my own. >> > >> > Cheers, >> > Jarek >> > >> > 2013/1/22 Chris Down <ch...@regentmarkets.com>: >> >> Do you have an strace from the plugin? >> >> >> >> >> >> On 22 January 2013 20:09, Jarosław Rzeszótko <szt...@gmail.com> wrote: >> >>> >> >>> Hi, >> >>> >> >>> I am running dwm 6.0 (and I tried also without any additional patches >> >>> and >> >>> using the default configuration file) and when I install the newest >> >>> version >> >>> of the Google Talk plugin, open a hangout in Google Plus and select >> >>> "Screen >> >>> sharing" a window appears for a fraction of a second and then the >> >>> Google >> >>> Talk plugin crashes. This happens only with dwm, I tried several other >> >>> window managers, including other tiling ones, in different modes, and >> >>> with >> >>> them it worked correctly without issues. Now I know Google products >> >>> might >> >>> not appeal to the crowd here, and they don't necessarily appeal to me >> >>> either, but I need the hangouts for my telework and it is not a choice >> >>> made >> >>> by me. Also I think this must be a problem with dwm behaving in a >> >>> non-standard-compliant way in some respect so it would be well worth >> >>> fixing. >> >>> >> >>> If someone has any idea altogether at all about how to attack this, I >> >>> would be willing to try to debug it or submit a patch. I hacked on dwm >> >>> a bit >> >>> in the past, I just have no idea how to go about diagnosing a problem >> >>> like >> >>> this. >> >>> >> >>> Cheers, >> >>> Jarosław Rzeszótko >> >> >> >> >> >
