xpra icon
Bug tracker and wiki

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#900 closed defect (fixed)

google chrome fail to start

Reported by: Jiang Owned by: Antoine Martin
Priority: critical Milestone: 0.16
Component: core Version: 0.15.x
Keywords: Cc:

Description

After upgrading to xpra 0.15.2, from the apt repository, google chrome no longer start. I am running Ubuntu 14.04, both client (32 bit) and server (64 bit).

Symptom: after upgrading restarting both server and client, I type DISPLAY=100 screen as usual, on the server. Starting firefox from screen works as before. But starting google chrome resulting no window being forwarded. The chrome is running on the server. Starting chrome from a forwarded X session works. starting chrome with no command line options, still no forwarded window.

Downgrading the client to 0.15.1 while the server is still running 0.15.2 does not solve the problem. Only downgrading both server and client returns chrome forwarding back to work.

Cannot find anything strange on either server or client log.

Change History (5)

comment:1 Changed 4 years ago by Antoine Martin

Status: newassigned

Very odd, I see nothing in any of the fixes that could explain this. But chrome does do weird things.
Will try it asap.

comment:2 Changed 4 years ago by Antoine Martin

Bisected down:

comment:3 Changed 4 years ago by Antoine Martin

Yep, I did the backport all wrong, fixup in r9768.
And this new error only triggered for applications that set the decorations flag, and chrome does - and I didn't test that as I should have.

A related problem is that early window setup errors don't trigger log messages because it is very hard to differentiate a bug (like this one) from other harmless failures (ie: the window has gone away) - but I'll try to make this better.

I am not going to release 0.15.3 just for this one fix. I'm just spinning more packages as 0.15.2-2 instead, they'll land in the repos in the next few hours.

comment:4 Changed 4 years ago by Jiang

Resolution: fixed
Status: assignedclosed

I can verify that this is fixed in 0.15.2-2. Thank you for being so responsive and efficient!

comment:5 Changed 4 years ago by Antoine Martin

FYI: r9820 should allow us to catch early window setup failures in the future (may backport)

Note: See TracTickets for help on using tickets.