Created attachment 4978 register/call addtional dbus services by screen Using --drop-down option on second screen (:0.1) of dual screen (:0.0 and :0.1) setup each time would create a new drop down window. I believe it's because every time it's because there is already a dbus instance running on 0.0, which would return display mistach on invocation, force screen :0.1 to create new one every time. In addition to default dbus service name org.xfce.Terminal5 I have a hack to register encoded services at org.xfce.Terminal5.screen._0x3A_0_0x2E_0 == :0.0 org.xfce.Terminal5.screen._0x3A_0_0x2E_1 == :0.1 and get the invocation to retry matching names if default call returned display mismatch. This seems to work despite some strange dbus error on registration which is not consistent with the duplicate registration.
Fixed another way, hopefully.
I just installed debian xfce4-terminal 0.6.2, but when starting an addtional xfce4-terminal on a separate display/screen, (all) the original xfce4-terminal disappeared! It actually failed with: $ xfce4-terminal The program 'xfce4-terminal' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 604 error_code 8 request_code 1 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) I did try gdb & etc but couldn't find out what occurred. Then when I reverted the changes using function terminal_gdbus_display_name(), the problem stopped.
Created attachment 5067 revert changes removes BadMatch failure. This is the debug patch I made that reverted recent change and avoided the X system error.
Closing old bugs.