GNOME 2 package is obsolete
Further to comments #21 and #24 issue fixed
Debian task also showing fixed
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=473566.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: gnome-terminal (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/436188
Title:
gnome-terminal assert failure: ERROR:terminal-
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
I have followed the most recent steps to reproduce (with a Maverick
client, and Lucid host) but cannot reproduce this bug.
Malaise - does this occur every time for you? Can you try launching
gnome-terminal with --disable-factory and see if this also produces
the problem?
--
gnome-terminal
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
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 maybe
This seems to be fixed on Lucid, there's no confirmation based on the
reports (duplicates) that the issue is reproducible on Lucid, could
somebody please test the same and confirm ? Thanks in advance.
** Changed in: gnome-terminal (Ubuntu)
Status: Triaged = Incomplete
--
gnome-terminal
I've tried all the workarounds listed above with no success. I've also
tried something I found in another thread (below)
I subsequently discovered that the original user can be fixed by deleting these
directories in /home/original-user
.dbus
.gconf
.gconfd
.gnome2
.gnome2_private
The only
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:
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 remote_host, but I can't find it.
I'm sure that cleaning this obsolete reference would solve the problem.
--
gnome-terminal assert failure:
I confirm the use case:
Problem occurs when stopping (shutdown) the remote host while a ssh -X
remote_host gnome-terminal is running.
Local host is Hardy, remote is Karmic. DisallowTCP=false on remote host, of
course.
--
gnome-terminal assert failure:
Correction
Problem occurs IF stopping (shutdown) the remote host while a ssh -X
remote_host 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:
$ 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 socket
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
On Sat, 2009-12-12 at 16:35 +, Malaise wrote:
i confirm. From a Hary I do:
Is this bug really in a state where it needs confirmation? I think this
is a well known issue plaguing a lot of people -- and sadly, even after
a major distribution update (i.e. this was a bug in Intrepid too) it's
I have just come across this problem with a source code install. The
way the system was build was using make DESTDIR=/arch/pkg/32/gnome-
terminal-2.28.0 install etc for each gnome package. The contents of
these directories was then copied onto a clean file system before being
run under KVM.
I got this just now on an up-to-date Karmic install. So this bug is
alive and well in Karmic.
Please! Let's not have two releases in a row where the basic
functionality of:
$ ssh -X karmic-host gnome-terminal
fails to work correctly.
--
gnome-terminal assert failure:
I've just seen this for the first time now, on Karmic.
--
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 notification because you are a member of Ubuntu
Had this today for the first time on karmic64 up to date
--
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 notification because you are a member of Ubuntu
had this problem directly after an update. a restart settled it. sorry
--
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 notification because you are a
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Triaged
--
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 notification because you are a
Macports: http://trac.macports.org/ticket/18142
** Visibility changed to: Public
** Bug watch added: trac.macports.org/ #18142
http://trac.macports.org/ticket/18142
--
gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init:
assertion failed: (app-default_profile_id !=
Arch: http://bbs.archlinux.org/viewtopic.php?id=56472
--
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 notification because you are a member of Ubuntu
Previously appeared as: bug #298426
** Changed in: gnome-terminal (Ubuntu)
Status: New = Confirmed
** Bug watch added: Red Hat Bugzilla #473566
https://bugzilla.redhat.com/show_bug.cgi?id=473566
** Also affects: gnome-terminal (Fedora) via
Theoretically this has been fixed/superseded...
gnome-terminal (2.26.2-2) unstable; urgency=low
* 02_let_gconf_autostart.patch: Don’t exit if there is no GConf daemon
running. Instead, let dbus-daemon and gconfd be autostarted as they
should be if this is needed. Thanks to Sean Finney
** Changed in: gnome-terminal (Debian)
Status: Unknown = New
--
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 notification because you are a
** Changed in: gnome-terminal (Fedora)
Status: Unknown = Confirmed
--
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 notification because you are a
28 matches
Mail list logo
