gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init: assertion failed: (app->default_profile_id != NULL)

[James Dearing]

Binary package hint: gnome-terminal

I had just installed Amarok in Ubuntu using apt-get, then closed the terminal, ran Amarok, attempted to open Synaptic while Amarok was running (Synaptic didn't open: it suddenly couldn't accept my password), then I tried to reopen the terminal and I got this error.

ProblemType: Crash
Architecture: amd64
AssertionMessage: ERROR:terminal-app.c:1444:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
CheckboxSubmission: 9230974a767de8fe0d75ee61fe42cd76
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Fri Sep 25 17:37:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-terminal
NonfreeKernelModules: nvidia
Package: gnome-terminal 2.28.0-0ubuntu1
ProcCmdline: gnome-terminal
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
Signal: 6
SourcePackage: gnome-terminal
StacktraceTop:
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 g_assertion_message () from /lib/libglib-2.0.so.0
 g_assertion_message_expr ()
 ?? ()
Title: gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[James Dearing (dearingj)]

I just tried switching to a terminal via Ctrl+Alt+F1, and I was able to log in with that. From there I entered "sudo /etc/init.d/gdm restart", sudo accepted my password, and now I am able to open Synaptic and gnome-terminal without problems.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #436188, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.