xpra icon
Bug tracker and wiki

Opened 12 days ago

Last modified 22 hours ago

#2026 assigned enhancement

Do not allow client to die during bug/diagnostic collection

Reported by: stdedos Owned by: Antoine Martin
Priority: major Milestone: future
Component: client Version: 2.4.x
Keywords: Cc:

Description

I tried to collect diagnostics for a bug report, however the client decided to kill itself.

It was during a shadow timeout, and the client decided to kill itself immediately.

Kindly hold/block/ignore "the kill signal" while the diagnostics window is open.

Change History (5)

comment:1 Changed 11 days ago by Antoine Martin

Status: newassigned

Not sure how easy to implement this is going to be.
FYI: until that's implemented, you can fire the bug report tool separately from xpra. (see wiki/ReportingBugs)

And as of r20920, simply by running:

xpra bug-report

comment:2 Changed 11 days ago by stdedos

I was wondering: Does the tool collect "more information" when called from the offending session, or does it collect the same regardless?

It would be nice if you could call it from the server (xpra bug-report :10) or from the client (xpra bug-report ssh://user@ip/10), to collect "everything you need" in memory, and then drop whatever the user didn't want to provide.

comment:3 Changed 11 days ago by Antoine Martin

Does the tool collect "more information" when called from the offending session, or does it collect the same regardless?

More: it also collects "xpra info".

It would be nice if you could call it from the server (xpra bug-report :10) or from the client (xpra bug-report ssh://user@ip/10), to collect "everything you need" in memory, and then drop whatever the user didn't want to provide.

Please file a separate ticket for that.

comment:4 Changed 11 days ago by Antoine Martin

New ticket for separate bug reports with xpra info: #2027

comment:5 Changed 22 hours ago by Antoine Martin

Milestone: 2.5future

Difficult:

  • the launcher gui overrides some of the exit methods
  • so does the disconnect notification code: r20984
  • keeping the client running after the server requested disconnection will trigger all sorts of problems (pings won't be received, we'll paint spinners over the windows, etc)
Note: See TracTickets for help on using tickets.