xpra icon
Bug tracker and wiki

Opened 6 years ago

Closed 6 years ago

#512 closed defect (needinfo)

calling 'xpra stop' seems to mess up linux environment

Reported by: Stepan Salenikovich Owned by: Stepan Salenikovich
Priority: minor Milestone:
Component: server Version: 0.11.x
Keywords: stop environment Cc:

Description

OS: arch linux, using dwm as the windows manager
version: xpra-winswitch 0.11.2-1 installed from Arch Linux AUR: https://aur.archlinux.org/packages/xpra-winswitch/

description:
Running the xpra stop command seems to mess up my linux environment, specifically the settings related to the terminal emulator. After I execute xpra stop if I launch a new terminal (I'm using urxvt, but the same can be observed with xterm), it does not respect my settings in .Xresources. Running source .Xresources does NOT restore the settings. In another very similar Arch Linux install, my default shell also becomes sh instead of bash. The only way I've found to restore my environment is by restarting X.

Also, this doesn't happen if I simply killall xpra instead of xpra stop

I'm not sure if this was the case in the previous version, 10.x, as I have deleted it and the Arch Linux AUR doesn't save previous versions of the package.

Change History (2)

comment:1 Changed 6 years ago by Antoine Martin

Keywords: stop, environmentstop environment
Owner: changed from Antoine Martin to Stepan Salenikovich

Weird. Please post your .Xresources. Nothing has changed in this area for a long time, not in 0.11 and probably not in 0.10 either.

I have no idea why/how we can cause such problems. xpra stop only closes the connections cleanly, killall xpra will end up doing pretty much the same thing (only fired via a signal).

Does this happen if you disconnect the client first? And if you don't?
Does it still mess up the terminal emulator if you use a different one for launching xpra?

comment:2 Changed 6 years ago by Antoine Martin

Resolution: needinfo
Status: newclosed
Note: See TracTickets for help on using tickets.