Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-06-15 Thread René J . V . Bertin
Thiago Macieira wrote: > There's nothing to be changed, unless you want to disable clipboard support > completely. I'm guessing I could implement a fallback to XStoreBuffer, so that at least text copying works? Heck, since this is on Mac I could even pipe text content into pbcopy... Now,

Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-06-15 Thread Thiago Macieira
On Friday, 15 June 2018 02:20:20 PDT René J. V. Bertin wrote: > Thiago Macieira wrote: > >> Yeah, DOH :) I don't have the GTk sources on my system currently but it's > >> likely that somewhere there will be a call to xcb_set_selection_owner() > >> in > >> there too, no? That's where the error

Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-06-15 Thread René J . V . Bertin
René J. V. Bertin wrote: > FWIW, I notice that GTk(3) doesn't use > xcb_xfixes_select_selection_input_checked() at all, so there's another > possible reason why GTk applications are not affected when the issue hits me. Or simply the fact it doesn't use xcb_set_selection_owner() at all. It does

Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-06-15 Thread René J . V . Bertin
Thiago Macieira wrote: >> Yeah, DOH :) I don't have the GTk sources on my system currently but it's >> likely that somewhere there will be a call to xcb_set_selection_owner() in >> there too, no? That's where the error message I see comes from: the call >> fails (doesn't have the expected

Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-06-14 Thread René J . V . Bertin
it took a while, but I just got bitten by this again. The diagnostics output I added shows this: QXcbClipboard::setMimeData: Cannot set X11 selection owner clipboard mode= 0 connection= 0x7fcdab809000 time= 4293362843 newOwner= 20971523 effective owner: 4194305 Any idea what to make of

Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-03-07 Thread René J . V . Bertin
Thiago Macieira wrote: > Yes, it's likely. That doesn't mean GTK prints something as a result of that. No, but I don't care about the error message in itself. > And this symptom doesn't happen with GTK? And no, which is what I meant when I said that those applications aren't affected (I use

Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-03-07 Thread Thiago Macieira
On Wednesday, 7 March 2018 07:36:43 PST René J. V. Bertin wrote: > Thiago Macieira wrote: > > Obviously no GTK application is going to print something about > > "QXcbClipboard". > > Yeah, DOH :) I don't have the GTk sources on my system currently but it's > likely that somewhere there will be a

Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-03-07 Thread René J . V . Bertin
Thiago Macieira wrote: > Obviously no GTK application is going to print something about > "QXcbClipboard". Yeah, DOH :) I don't have the GTk sources on my system currently but it's likely that somewhere there will be a call to xcb_set_selection_owner() in there too, no? That's where the error

Re: [Interest] "QXcbClipboard::setMimeData: Cannot set X11 selection owner"

2018-03-07 Thread Thiago Macieira
On Wednesday, 7 March 2018 03:21:45 PST René J.V. Bertin wrote: > QXcbClipboard::setMimeData: Cannot set X11 selection owner > > I'm seeing this sporadically in applications connected to an XQuartz X11 > server that has been running for a certain time. It always seem to affect > all the