[winswitch] No menu bar in Ubuntu

[Douglas Doole]

Thanks Antoine.

I thought the --start was the trick I needed, but it seems I've stumbled
onto something new. :-(

My general model is that I have xpra running, and then I create and dispose
of terminal windows as needed. Then I run commands as needed from the
terminal.

I had been using "DISPLAY=:10 gnome-terminal" and had the menu bar problem.

Since xpra is already running, I can't use "xpra start --start=...", so I
used "xpra control :10 start gnome-terminal". This gives me a terminal
window with a menu bar. Any commands I start from the terminal (gvim,
eclipse) also have their menu bar. Yay!

But when I try to start a second terminal using "xpra control :10 start
gnome-terminal", xpra hangs. I get the title bar and border for the second
window, but its contents are black. All existing windows stop responding to
input. (Even the close button in the title bar is non-responsive.) The xpra
icon in the systray changes from an X to the clipboard icon. (The systray
icon responds normally.) Running "xpra list" shows a LIVE session. If I
disconnect the client, the server still reports a LIVE session. However as
soon as I try to reconnect the client the server reports it as DEAD
(cleaned up). (The session is not fully cleaned up though - there are still
6 xpra related processes running, including "xpra start" and
Xorg-for-Xpra". Manually killing the Xorg-for-Xpra process cleans
everything up.)

Any idea on this one?

In the short term, I can just create my first window using xpra control
start and then spawn new terminals from that. However my preferred way to
work is to have a terminal icon in the launcher that I click to spawn a new
terminal in xpra.

- Doug

On Wed, Jan 18, 2017 at 9:37 AM Antoine Martin via shifter-users <
shifter-users at lists.devloop.org.uk> wrote:

> On 19/01/17 00:29, Douglas Doole via shifter-users wrote:
> > Any thoughts on this? I can open a bug, but I'd like to know that I'm not
> > missing something first.
> Sorry, forgot to reply - I wanted to test first but couldn't find the time.
> It's probably best to file a ticket so this doesn't get lost again.
>
> My guess is that there must be some setting that is forwarded that tells
> the application to not use Ubuntu's "global menu".
> We do have some environment variables that are set to try to turn it
> off, but maybe these are no longer sufficient.
>
> These environment variables will only affect commands started with:
> xpra start --start=THECOMMAND
> And not with:
> DISPLAY=:100 THECOMMAND
> Yet another reason for always using the "--start" option.
>
> Cheers
> Antoine
>
> >
> > Thanks.
> >
> > - Doug
> >
> > On Thu, Jan 12, 2017 at 1:37 PM Douglas Doole <dougdoole at gmail.com>
> wrote:
> >
> >> I'm using xpra 1.0.1 (also saw this on 1.0) on a Ubuntu 14.04.5 system.
> >> Most of the time I'm running it in loopback mode.
> >>
> >>    xpra start :10
> >>    xpra attach ssh:localhost:10
> >>
> >> When I do this, however, I don't see the menu bars for my applications
> >> (gvim and eclipse being my most commonly used). All the menu bar at the
> top
> >> of the screen says is "attachXpra"
> >>
> >>  If I attach from my MacBook, then I see menu bars. (The menu bars are
> in
> >> each window instead of at the top of the screen, and there's a generic
> Xpra
> >> menu at the top of the screen. That's fine by me.)
> >>
> >> So it looks like the xpra server is aware of the menu bars, but the
> Ubuntu
> >> client isn't showing them. Is there some setting I'm missing?
> >>
> >> Thanks.
> >>
> >> - Doug
> >>
> > _______________________________________________
> > shifter-users mailing list
> > shifter-users at lists.devloop.org.uk
> > http://lists.devloop.org.uk/mailman/listinfo/shifter-users
> >
>
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
>