#551 closed defect (invalid)
xpra doesn not kill Xvfb
| Reported by: | lennard | Owned by: | Antoine Martin |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | server | Version: | 0.12.x |
| Keywords: | Cc: |
Description (last modified by )
When xpra server quits, because the client exited (--exit-with-children was used), the Xvfb-for-Xpra-:100 process remains running and has to be be killed by hand. I used xpra 0.12.0.
Change History (4)
comment:1 Changed 8 years ago by
| Description: | modified (diff) |
|---|---|
| Owner: | changed from Antoine Martin to Antoine Martin |
| Status: | new → assigned |
comment:2 Changed 8 years ago by
Wait... Maybe I know what this is, as I've seen it before.
Do you have OpenCL or CUDA installed by any chance? And in particular the AMD ICD?
comment:3 Changed 8 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | assigned → closed |
@lennard: I believe your user account got wiped when the server ran out of diskspace... sorry about that. (the trac password file was restored from an earlier backup)
I am closing this bug as 'invalid' because there is nothing wrong with the xpra code, it works reliably in countless environments and operating systems, the only thing that breaks it is the AMD ICD. If that is not the case, feel free to re-open this ticket with the details requested.
comment:4 Changed 17 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/551
copyleft 2010 - 2021
Please specify what distribution you use and paste the server log.