[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/144638
Title:
ssh -X an
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I noticed that the issue your bugging is updated in
Maverick. Please update via www.ubuntu.com repost a detailed error
report, and update the bug status. Thanks!
--
ssh -X and run gnome apps then exit problem
http
Updating what I wrote on 12/18/2008, the correct way to launch gnome
apps is via "dbus-launch": this should solve most of the issues people
are having with this.
ssh -f -Y HOSTNAME "exec dbus-launch roxterm >&/dev/null &1 >/dev/null
https://bugs.launchpad.net/bugs/144638
You received this bug not
Still an issue in Karmic.
--
ssh -X and run gnome apps then exit problem
https://bugs.launchpad.net/bugs/144638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
Just testing in latest Ubuntu 9.04 Jaunty beta + updates as of April 3.
Still a problem.
One thing that I do notice is that the second ssh -X will close fine.
Maybe something to do with the number of open connections being
incorrect?
--
ssh -X and run gnome apps then exit problem
https://bugs.l
Oops. pasted wrong thing for remote/forwardedX script:
..
@echo off
SET DISPLAY=127.0.0.1:0.0
\cygwin\bin\ssh.exe -Y -q -n z...@imnotabouttotellyoumyhostname.com
"/usr/bin/gnome-terminal --sm-disable --disable-sound --zoom=1.5 >& /dev/null <
/dev/null & ; exec sleep 1"
...
I found this thread via googling. This seems to be a gnome bug that
didn't exist in previous versions. I invoked it when upgrading boxes
from fedora 7 to fedora 10. I do not run Ubuntu, as I've been a Fedora
user since 1.0, and prior to that (mid-nineties) I used slackware when I
wasn't compiling m
The redirecting of stdin/stdout/stderr streams as directed in the link
above doesn't seem to fix the problem.
I'll re-emphasize that the problem is not in all X programs, it seems to
be limited to GNOME ones,
xterm, xclock seem to be fine.
CTRL+C is still the only workaround
--
ssh -X and run
A fix is to redirect the background process stdin/stdout/stderr streams (e.g.
to files, or /dev/null if you don't care about them).
Can you refer to http://www.snailbook.com/faq/background-jobs.auto.html and see
if this helps
Thanks.
--
ssh -X and run gnome apps then exit problem
https://bugs
This is still a problem in Hardy.
A workaround that I found out about is by typing CTRL+C, the terminal is
back
--
ssh -X and run gnome apps then exit problem
https://bugs.launchpad.net/bugs/144638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in: ubunt
I've had this problem as well. The biggest problem is with forwarding a
whole desktop session. On our school's Solaris thin clients, I have the
profile set to run "ssh -XCT [EMAIL PROTECTED] startkde" at login. When I
logged out from KDE SSH hung, forcing me to use another computer to kill
the asso
This is a recent problem, seems as though only since feisty, but still
present with gusty it seems. Before that exiting after ssh -X worked
fine.
--
ssh -X and run gnome apps then exit problem
https://bugs.launchpad.net/bugs/144638
You received this bug notification because you are a member of Ub
13 matches
Mail list logo
