Now I reproduce it 100%.
>From a Hardy I do: ssh -X karmic-host gnome-terminal. While the terminal is
>connected reboot the Karmic host.
Then do ssh -X karmic-host gnome-terminal again.
Workaround (works 100%): On the Karmic host, rm -rf .dbus/session-bus/*, then
reboot the Hardy host.
But mayb
Can anybody explain where this reference to "/tmp/dbus-xxx" cames from and how
to clean it?
This seems to be stored somewhere on the , but I can't find it.
I'm sure that cleaning this "obsolete" reference would solve the problem.
--
gnome-terminal assert failure: ERROR:terminal-app.c:1444:termin
Workaround (not 100% precise):
- remove rm -rf $HOME/.dbus on both hosts
- reboot both hosts
- retry
- on the remote host, $HOME/.dbus now belongs to root!!!
- remove it (as root).
Now it works, as far as I could understand.
--
gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_ap
>$ ssh -X karmic-host gnome-terminal
>fails to work correctly.
i confirm. From a Hary I do: ssh -X karmic-host gnome-terminal
It fails with:
Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
// 6l times
Failed to get the session bus: Failed to connect to socke
In fact, it seems to be fixed after doing:
rm -rf $HOME/.dbus on the remote host then reboot it.
--
gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init:
assertion failed: (app->default_profile_id != NULL)
https://bugs.launchpad.net/bugs/436188
You received this bug notif
I confirm the use case:
Problem occurs when stopping (shutdown) the remote host while a "ssh -X
gnome-terminal" is running.
Local host is Hardy, remote is Karmic. DisallowTCP=false on remote host, of
course.
--
gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init:
asser
Correction
Problem occurs IF stopping (shutdown) the remote host while a "ssh -X
gnome-terminal" is running.
And it occurs AFTER rebooting the remote host, of course.
--
gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init:
assertion failed: (app->default_profile_id != NU
Yes I confirm that the problem with the scenario above is 100% reproducible
(with 2 Lucid).
With ssh -X S "gnome-terminal --disable-factory" the problem is still present.
Adam, if you want me to do more tests or if you want to log on my
machines you can contact me directly.
--
You received this
Unfortunately I can confirm that the problem still occurs between 2 hosts on
Lucid.
>From client host C to server host S.
C: ssh -X S gnome-terminal
S: reboot
C: // do NOT close (force quit) the ghost window. When S reboots it disappears
C: ssh -X S gnome-terminal // Fails with the following lo
