libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: gnome-terminal comment: Started running the app from the 'f/start' menu. crash_function: __GI_raise executable: /usr/bin/gnome-terminal kernel: 3.1.1-2.fc16.x86_64 pid: 15561 pwd: /home/nathaniel reason: Process /usr/bin/gnome-terminal was killed by signal 6 (SIGABRT) time: Tue 22 Nov 2011 09:59:43 AM EST uid: 1000 username: nathaniel backtrace: Text file, 19573 bytes build_ids: Text file, 2542 bytes dso_list: Text file, 5579 bytes maps: Text file, 25839 bytes smolt_data: Text file, 3281 bytes environ: :XDG_VTNR=1 :SSH_AGENT_PID=1447 :XDG_SESSION_ID=1 :SAL_USE_VCLPLUGIN=gtk :HOSTNAME=f16-tomcat :IMSETTINGS_INTEGRATE_DESKTOP=yes :XDG_MENU_PREFIX=lxde- :SHELL=/bin/bash :TERM=dumb :XDG_SESSION_COOKIE=9c28cb10f216c057eea1686000000010-1321945602.704277-1642269212 :HISTSIZE=1000 :GNOME_KEYRING_CONTROL=/tmp/keyring-7aBgoR :SYSFONT=latarcyrheb-sun16 :IMSETTINGS_MODULE=none :USER=nathaniel :SSH_AUTH_SOCK=/tmp/ssh-DfFISmFu1338/agent.1338 :DESKTOP_SESSION=LXDE :PATH=/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/nathaniel/.local/bin:/home/nathaniel/bin :MAIL=/var/spool/mail/nathaniel :QT_IM_MODULE=xim :PWD=/home/nathaniel :XMODIFIERS=@im=none :GNOME_KEYRING_PID=1271 :LANG=en_US.UTF-8 :KEYTABLE=us :HISTCONTROL=ignoredups :SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass :XDG_SEAT=seat0 :HOME=/home/nathaniel :SHLVL=1 :XDG_CONFIG_HOME=/home/nathaniel/.config :BOOT_IMAGE=/vmlinuz-3.1.1-2.fc16.x86_64 :LOGNAME=nathaniel :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-UDw9pCasSf,guid=fb6778a559661b709669801b00000037 :PREFERRED=/usr/bin/startlxde :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :XDG_RUNTIME_DIR=/run/user/nathaniel :DISPLAY=:0 :GTK_IM_MODULE=gtk-im-context-simple :XAUTHORITY=/home/nathaniel/.Xauthority :_LXSESSION_PID=1338 :XDG_CURRENT_DESKTOP=LXDE gconf_subtree: : /apps/gnome-terminal/profiles: : /apps/gnome-terminal/profiles/Default: : foreground_color = #000000000000 : bold_color = #000000000000 : palette = #2E2E34343636:#CCCC00000000:#4E4E9A9A0606:#C4C4A0A00000:#34346565A4A4:#757550507B7B:#060698209A9A:#D3D3D7D7CFCF:#555557575353:#EFEF29292929:#8A8AE2E23434:#FCFCE9E94F4F:#72729F9FCFCF:#ADAD7F7FA8A8:#3434E2E2E2E2:#EEEEEEEEECEC : visible_name = Default : background_color = #FFFFFFFFDDDD var_log_messages: :Nov 22 09:58:55 f16-tomcat yum[15409]: Installed: gnome-terminal-3.2.1-2.fc16.x86_64 :Nov 22 09:59:46 f16-tomcat abrt[15565]: Saved core dump of pid 15561 (/usr/bin/gnome-terminal) to /var/spool/abrt/ccpp-2011-11-22-09:59:43-15561 (27549696 bytes) xsession_errors: :abrt-applet: repeated crash in gnome-terminal-3.2.1-2.fc16, not showing the notification :abrt-applet: repeated crash in gnome-terminal-3.2.1-2.fc16, not showing the notification
Created attachment 535065 [details] File: dso_list
Created attachment 535066 [details] File: build_ids
Created attachment 535067 [details] File: smolt_data
Created attachment 535068 [details] File: maps
Created attachment 535069 [details] File: backtrace
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 756018 has been marked as a duplicate of this bug. ***
*** Bug 756047 has been marked as a duplicate of this bug. ***
*** Bug 756391 has been marked as a duplicate of this bug. ***
*** Bug 756546 has been marked as a duplicate of this bug. ***
*** Bug 756837 has been marked as a duplicate of this bug. ***
*** Bug 757179 has been marked as a duplicate of this bug. ***
*** Bug 757366 has been marked as a duplicate of this bug. ***
*** Bug 757369 has been marked as a duplicate of this bug. ***
*** Bug 757526 has been marked as a duplicate of this bug. ***
*** Bug 757603 has been marked as a duplicate of this bug. ***
*** Bug 757682 has been marked as a duplicate of this bug. ***
*** Bug 757801 has been marked as a duplicate of this bug. ***
*** Bug 758087 has been marked as a duplicate of this bug. ***
*** Bug 758715 has been marked as a duplicate of this bug. ***
*** Bug 759713 has been marked as a duplicate of this bug. ***
*** Bug 759733 has been marked as a duplicate of this bug. ***
*** Bug 759835 has been marked as a duplicate of this bug. ***
*** Bug 759951 has been marked as a duplicate of this bug. ***
*** Bug 759952 has been marked as a duplicate of this bug. ***
*** Bug 759953 has been marked as a duplicate of this bug. ***
*** Bug 761289 has been marked as a duplicate of this bug. ***
*** Bug 761373 has been marked as a duplicate of this bug. ***
*** Bug 761719 has been marked as a duplicate of this bug. ***
*** Bug 766222 has been marked as a duplicate of this bug. ***
*** Bug 773384 has been marked as a duplicate of this bug. ***
*** Bug 772384 has been marked as a duplicate of this bug. ***
*** Bug 772091 has been marked as a duplicate of this bug. ***
*** Bug 771277 has been marked as a duplicate of this bug. ***
*** Bug 770835 has been marked as a duplicate of this bug. ***
*** Bug 770056 has been marked as a duplicate of this bug. ***
*** Bug 768678 has been marked as a duplicate of this bug. ***
*** Bug 751904 has been marked as a duplicate of this bug. ***
*** Bug 752246 has been marked as a duplicate of this bug. ***
*** Bug 753533 has been marked as a duplicate of this bug. ***
*** Bug 768677 has been marked as a duplicate of this bug. ***
*** Bug 768211 has been marked as a duplicate of this bug. ***
*** Bug 768092 has been marked as a duplicate of this bug. ***
*** Bug 767854 has been marked as a duplicate of this bug. ***
*** Bug 767386 has been marked as a duplicate of this bug. ***
*** Bug 766758 has been marked as a duplicate of this bug. ***
*** Bug 766436 has been marked as a duplicate of this bug. ***
The code that is asserting here is /* Ensure we have valid settings */ g_assert (app->default_profile_id != NULL); So for some reason, we fail to get the default profile id, which is stored in GConf as /apps/gnome-terminal/global/default_profile
*** Bug 718721 has been marked as a duplicate of this bug. ***
Anybody who is still seeing this should please try to run gconftool-2 --unset /apps/gnome-terminal/global/default_profile in a terminal (probably not gnome-terminal, though :-( )
crashed on calling application backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 555157 [details] File: backtrace
dragged file to terminal to get patch to directory backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 555286 [details] File: backtrace
opened gnome-terminal after terminator crashed backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 555288 [details] File: backtrace
- Installed fresh F16 - Installed gnome-terminal - Tried to start gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 555353 [details] File: backtrace
just launch the terminal rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
started terminal, yesterday I did gconftool-2 --unset /apps/gnome-terminal/global/default_profile backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 555358 [details] File: backtrace
crashed on start backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 555710 [details] File: backtrace
I started nautilus-open-terminal. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 556210 [details] File: backtrace
i was opening terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 556693 [details] File: backtrace
Just assign hotkey for terminal to Win+T and press it. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 557183 [details] File: backtrace
I tried to open a gnome-terminal. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 557342 [details] File: backtrace
The error occured when I tryed to open the Terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Kororaa release 16 (Chum)
Created attachment 557519 [details] File: backtrace
I tried to launch a terminal from the favourites bar, it immediately brought up abrt and that was it. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 557525 [details] File: backtrace
Opening gnome-terminal fails, both from the regular icon, and from nautilus-open-terminal. Just started after installing updates then restarting. Updates haven't been installed for at least 2 weeks, so it must have happened somewhere in that time. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 557611 [details] File: backtrace
I tried running 'gconftool-2 --unset /apps/gnome-terminal/global/default_profile', it didn't help. Both before and after running that, gconf-tool shows an empty config tree. Maybe this is related?
Turns out logging out then back in fixed it.
This the first time I tried to open a terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 558082 [details] File: backtrace
Related to bug reported by Scott Harvey: This happens after I have booted up for the first time, then I try to open gnome-terminal via right click-Open in Teminal item in the desktop. Just like some of the others I log out of gnome-desktop and then back in it works.
launching terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 558162 [details] File: backtrace
Clicked on icon backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 558938 [details] File: backtrace
starting terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 559255 [details] File: backtrace
This error occured when I tryed to open the Terminal. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Kororaa release 16 (Chum)
Created attachment 559371 [details] File: backtrace
This error happened when I opened the terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Kororaa release 16 (Chum)
Created attachment 559411 [details] File: backtrace
WHAT THE HELL IS THAT?????? How many months should it take to fix such damn stupid error which prevent such basic application as the terminal from being opened ??!!! I got really tired of such sh*t from Fedora. Do you guys have QA? This is a release! How is it ever possible to have such shameful crashes like this one in the release system not being fixed for MONTHS??!! backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 559806 [details] File: backtrace
Really no idea.... Worked fine before last reboot. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 559825 [details] File: backtrace
open gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 560241 [details] File: backtrace
I turn on my computer & it's always the same bug, i can't open the terminal & I have to close-up the session and turn on once again backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 560263 [details] File: backtrace
started gnome-terminal with "right click-->open in terminal" backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 560425 [details] File: backtrace
Happend again. It's getting annoying backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 560581 [details] File: backtrace
Selected terminal from gnome-shell dock backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 560940 [details] File: backtrace
in gnome3 shell, clicked app. launcher and... crash. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 560952 [details] File: backtrace
It crashes when I try to load by clicking on the relative icon backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 561527 [details] File: backtrace
Tried to launch terminal. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 561830 [details] File: backtrace
just opened terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 562325 [details] File: backtrace
I hate latest Fedora/GNOME for this shit! Without a good terminal there is no linux! What a shame! Since F15 linux stopped being a reliable desktop :((( backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 562356 [details] File: backtrace
No idea what I was doing when this crashed, forwarding all the info I have. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 562443 [details] File: backtrace
Just by launching it. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 562585 [details] File: backtrace
I tried to start gnome-terminal using keyboard shortcut. Then I tried to run it from another already open terminal (guake) and I got several (six) lines: Chyba GConf: Nie je možné spojenie s konfiguračným serverom: D-BUS error: The GConf daemon is currently shutting down. (gconf.master.sk.po file says original line would be "GConf Error: Configuration server couldn't be contacted") and then I got ** ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Zrušené (bol uložený výpis pamäte) (the last line would be ABORTED (core dumped)) After killing gconfd-2 (it restarted automatically) everything worked again. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 563866 [details] File: backtrace
It happens every time I try to open the gnome-terminal. When I open i (from icon on dektop or from applications menu), nothing happens. I can see my CPU led indicates some activity for a very short time, then nothing. This crash-report then pops up just after. I'm not sure for how long it has been this way, but at least today (Sun feb 19). backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 564132 [details] File: backtrace
launching gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 564435 [details] File: backtrace
this happened suddenly but when i run the terminal before any program when i start fedora 16 it works THis problem is only in fedora i used gnome 3.2 on other distribution and this did not appeared on any distribution other thatn fedora 16 backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 565671 [details] File: backtrace
i used the open in terminal nautilus extension to open the terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 565685 [details] File: backtrace
Feb 25 2012. Problem is still NOT SOLVED! backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 565820 [details] File: backtrace
Try to open gnome-terminal. It crashes. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 566290 [details] File: backtrace
bug still happening on latest fedora
It happens ONLY with Gnome terminal. All other terminals like xterm, lxterminal and others work perfectly fine. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 567158 [details] File: backtrace
I inserted a patriot 8gb flash drive into the third or forth usb slot on my laptop. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 567344 [details] File: backtrace
My system have installed from Fedora-16 (KDE) live CD I just want to check again bugreport https://bugzilla.redhat.com/show_bug.cgi?id=551062 My steps: $ sudo yum install -y gnome-terminal bla-bla ... installed $ gnome-terminal GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. ** ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Aborted (core dumped) backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 568072 [details] File: backtrace
This keeps happening from time to time, and disappears after a logout or a reboot, without any identifiable reason... And it's getting very annoying! Basically what happpens is at least gnome-terminal and evolution refuses to start. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 568522 [details] File: backtrace
(In reply to comment #143) > This keeps happening from time to time, and disappears after a logout or a > reboot, without any identifiable reason... And it's getting very annoying! Try killing gconfd-2 instead of logging out or rebooting.
It won't open, crsahes before the GUI is built backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 568899 [details] File: backtrace
click on icon backtrace_rating: 4 Package: gnome-terminal-3.3.0-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Created attachment 568983 [details] File: backtrace
I've tried to start terminal with ctrl-alt-T combination backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 569444 [details] File: backtrace
When I tried to open the terminal with a keys combination that i established (Ctrl+t), the terminal don't opened and I got the error window. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 569465 [details] File: backtrace
This seams to be a DBus <-> GConf related problem. On my systems sometime when I boot it works the whole day but on some boots it does not. In this situation if I try to run gnome-terminal from another terminal I get: Błąd GConf: Nie można nawiązać połączenia z serwerem konfiguracji: Błąd usługi D-Bus: Usługa GConf jest obecnie wyłączana. Błąd GConf: Nie można nawiązać połączenia z serwerem konfiguracji: Błąd usługi D-Bus: Usługa GConf jest obecnie wyłączana. Błąd GConf: Nie można nawiązać połączenia z serwerem konfiguracji: Błąd usługi D-Bus: Usługa GConf jest obecnie wyłączana. Błąd GConf: Nie można nawiązać połączenia z serwerem konfiguracji: Błąd usługi D-Bus: Usługa GConf jest obecnie wyłączana. Błąd GConf: Nie można nawiązać połączenia z serwerem konfiguracji: Błąd usługi D-Bus: Usługa GConf jest obecnie wyłączana. Błąd GConf: Nie można nawiązać połączenia z serwerem konfiguracji: Błąd usługi D-Bus: Usługa GConf jest obecnie wyłączana. ** ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Przerwane (core dumped) Translation from polish: Error GConf: Cannot connect to the configuration server: D-Bus service error: Service GConf is unavailable So I think that gnome-terminal will not work if something goes wrong on boot and the GConf service is unavailable on DBus. When this happens I also get a the exactly same error message on Firefox when it starts.
Created attachment 569472 [details] /var/log/messages from this type of boot /var/log/messages from this type of boot
could some one plz add the: CommonBugs keyword here ?
when open the gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 569535 [details] File: backtrace
Started terminal after system reboot using icon in favourites menu. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 571244 [details] File: backtrace
I'm almost sure this bug is caused by: https://bugzilla.redhat.com/show_bug.cgi?id=756245 Please keep a lookout for update: https://admin.fedoraproject.org/updates/GConf2-3.2.3-4.fc16 If this bug happens on GConf with this version or higher please leave a comment on bug 756245.
Install it using: yum --enablerep=updates-testing install GConf2
poped out after last updating frequently backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 571274 [details] File: backtrace
poped out frequently backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 571298 [details] File: backtrace
Simply I tried to start gnome-terminal. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 571473 [details] File: backtrace
*** Bug 782906 has been marked as a duplicate of this bug. ***
*** Bug 742824 has been marked as a duplicate of this bug. ***
*** Bug 789451 has been marked as a duplicate of this bug. ***
*** Bug 679607 has been marked as a duplicate of this bug. ***
*** Bug 744126 has been marked as a duplicate of this bug. ***
+1 backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 572383 [details] File: backtrace
opening backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 572802 [details] File: backtrace
open backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 572803 [details] File: backtrace
Try to start Gnome terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 573358 [details] File: backtrace
*** Bug 659920 has been marked as a duplicate of this bug. ***
Opening the terminal caused it to crash. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 574333 [details] File: backtrace
1. Downloaded file in Firefox 2. Selected 'Open Containing Folder' in Downloads. Nautilus opened folder. 3. Right-clicked on folder and selected 'Open in Terminal' backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 574387 [details] File: backtrace
System cannot open the terminal Clicking on terminal icon results carshing terminal prompt backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 574525 [details] File: backtrace
executing gnome-terminal via gnome menu or keyboard shortcut backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 574794 [details] File: backtrace
THIS IS A BIG PAIN TO REPORT ERRORS AT HTTPS://BUGZILLA.REDHAT.COM . CRITICAL SHOW STOPPER ERRORS SUCH AS GNOME-TERMINAL NOT WORKING OR KERNEL CRASH.. NEVER MOVE FROM NEW STATE.. AND WHEN 100S OF OTHER PEOPLE REPORT THE SAME ERROR YOUR MAIL BOX GETS FLOODED WITH STATUS MAILS.. FEDORA SUCKS..
I suggest that anyone still seeing this problem reads the text in https://bugzilla.redhat.com/show_bug.cgi?id=755992#c161 and installs the updated package. I have done this and the problem has not occurred again, it would seem that the update needs some more karma votes to make it into updates instead of updates-testing. I don't find that Fedora sucks at all....
Throwing stone at fedora actually worked.. some one responded. If the issue is resolved then the state should change accordingly.. I am not sure about you but the state of this error forced me to say so.. I am a user of Fedora / Redhat from 1997 .. & I enjoy it a lot..
attempting to launch backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 575227 [details] File: backtrace
I attempted to launch Gnome-Terminal from the Gnome-Shell Dock. backtrace_rating: 4 Package: gnome-terminal-3.4.0.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
launch terminal from gnome-shell menu backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 575494 [details] File: backtrace
Tried to start the program via Activities menu. ABRT alert pops up. I have not modified gnome-terminal in any way. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 575779 [details] File: backtrace
(In reply to comment #199) > Tried to start the program via Activities menu. ABRT alert pops up. > I have not modified gnome-terminal in any way. > > > backtrace_rating: 4 > Package: gnome-terminal-3.2.1-2.fc16 > OS Release: Fedora release 16 (Verne) I tryed start the program by Activities menu, but I had not success.
crashed on launch backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 575950 [details] File: backtrace
Started terminal backtrace_rating: 4 Package: gnome-terminal-3.4.0.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I clicked the gnome terminal logo in the dropdown menu backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 576461 [details] File: backtrace
Try to open gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 576633 [details] File: backtrace
When accessing gnome-terminal by using Activities-Applications-Terminal and clicking on the icon it appears to run but it disappears and never brings up the window. If I use x-term and execute gnome-terminal as root the window comes right up but if I execute it as my user I get this output: GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. ** ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_pro file_id != NULL) Aborted (core dumped) backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 577349 [details] File: backtrace
Launched gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.4.0.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
gnome terminal does not start. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 577556 [details] File: backtrace
Using the gnome shell and Nautalis to manage the desktop I right clicked and chose open terninal here backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 577942 [details] File: backtrace
Open gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 579319 [details] File: backtrace
just starting terminal after reboot backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 579468 [details] File: backtrace
trying to start gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 579492 [details] File: backtrace
backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 580264 [details] File: backtrace
try to lunch a terminal backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle)
Applied latest F16 maintenance. After that, any attempt to start the gnome terminal restuls in signal 6 (SIGABRT). backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 581976 [details] File: backtrace
Clicked on applications/system tools/terminal. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 582254 [details] File: backtrace
Wanted to start terminal under Gnome backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 582414 [details] File: backtrace
Opened gnome-terminal from dash... backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 584163 [details] File: backtrace
crashes at startup backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 584170 [details] File: backtrace
Simply try and start After latest yum update with a new kernel backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 584368 [details] File: backtrace
Hi All, just my experience.... I've installed Fedora 16 in virtual box VM, the VM was configured with ONE processor and I/O apic DISABLED, and gnome terminal always works some day ago, I change VM settings to use TWO processors and I was forced to ENABLE I/O apic after these changes the gnome terminal stop working, and the only way to get it works again is to kill the gconfd-2 process (/usr/libexec/gconfd-2) today I updated the kernel with yum update, and see that gnome terminal works, but maybe an isolated case after this I reinstalled virtual box guest addtions, and reboot again the gnome terminal stop working if I back to work with only ONE processor and i/o apic disabled the terminal works fine every time I open it so, I suppose the bug is related to the i/o apic I hope this info helps bye Gaetano
1. click on a file with running permissions 2. click on "run in terminal" 3. error backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Just starting terminal. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Just started Fedora 17 backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
just try to run terminal backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Tried to launch gnome-terminal from Gnome3 (press the system button and type 'term'). It crashed without ever appearing. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
terminal is still broken since F16. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Just tried to open a terminal backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Ran an update and after reboot all went south. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I attempted to open a terminal using the nautilus-open-terminal extension. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
try to run the application backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Works for me now: $ uname -r 3.3.7-1.fc16.x86_64 $ yum info gnome-terminal ... Installed Packages Name : gnome-terminal Arch : x86_64 Version : 3.2.1 Release : 2.fc16 Size : 8.1 M Repo : installed ... Thanks
Simply by clicking on the Termina icon added favourite on the activities bar in GNU backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Same problem (F17 lxde spin): ~ $ rpm -q gnome-terminal gnome-terminal-3.4.1.1-1.fc17.i686 ~ $ uname -r 3.3.4-5.fc17.i686 (gdb) run Starting program: /usr/bin/gnome-terminal [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0xb7de2b40 (LWP 968)] [New Thread 0xb73ffb40 (LWP 971)] [New Thread 0xb69ffb40 (LWP 991)] ** ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Program received signal SIGABRT, Aborted. 0x00111416 in __kernel_vsyscall ()
just open gnome-terminal as usual. its the third time it happens backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
1.-click in icon terminal 2.-not open 3.-appear message error backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Tried to start gnome-terminal from the Gnome menu backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I simply clicked "Activities" in the upper-left corner in the Gnome 3 upper bar, and clicked "Terminal" in my favorites on the right. It immediately crashed on launch without even displaying a window. This is concerning to me. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
tried to start it from the gnome-shell menu. Freshly booted system. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I was trying to launch gnome terminal from the dock backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
1. Boot 2. Logon 3. Run gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Is killed when simply trying to open a (Gnome) terminal. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Started gterm from favorites. Failed immediately. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Just wanted to open terminal backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Crash on start. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Tried to initiate a session backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
type to open the terminal backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
this is the 6 month in which a whole lot of people have their terminal crashing backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
bug is show stopper. had to move to xfce terminal. When will this be actioned? Thanks.
to run the program via dash backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Wanted to open gnome-terminal out of gnome shell. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I think: 1.install gnome-commander 2. terminal not work from gnome-commander 3. install gnome-terminal 4. set up Default Application terminal to gnome-terminal 5. from gnome-commander start terminal 6.crash backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
(In reply to comment #161) > I'm almost sure this bug is caused by: > https://bugzilla.redhat.com/show_bug.cgi?id=756245 > > Please keep a lookout for update: > https://admin.fedoraproject.org/updates/GConf2-3.2.3-4.fc16 > > If this bug happens on GConf with this version or higher please leave a > comment on bug 756245. I'm running GConf2-3.2.5-1.fc17.x86_64 and I still have problems launching gnome-terminal more often than not.
Simply started terminal from the activities menu. Was immediatley presented with the abrt. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I tried to access the terminal from the side dock after I clicked on the activities menu. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Started terminal from nautilus plugin backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Crash when starting gnome-terminal. Has happened on multiple occasions. After crash, unable to restart terminal until I log out and login of the desktop, or restart the pc. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I opened Terminal from the menu after booting up from sleep state. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Tried to launch gnome-terminal after resuming from suspend. If trying from a console I get the message: GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down. (6x) Then an "assertion failed: (app->default_profile!=NULL)" followed by a core dump. If I kill the running gconfd-2 process I can start a terminal again. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Booted machine. Logged on and attempted to start gnome terminal. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Was running a large R job within Emacs that chewed up all my RAM. top was running in a guake terminal and I used it to kill the R process then emacs to recover my session. guake and gnome-terminal seeingly crashed. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Upated to Kernel-3.5.0 and it broke my display and is probably lacking video support, or the Kmod drivers for kernel-3.5.0 aren't ready yet. At least gnome starts in fallback-mode after the update. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I usually get these SIGABRT signals. Most of the times when i try to launch gnome-terminal, I'll be getting this. Don't know the reason for this. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Hello everyone, a solution that worked for me: Kill the gconfd-2 process, it restarts instantly and you can use your device. A note that this solution also works for launching a bug with gnome-journal-activity.
Problem happened when I tried to open the terminal on an MS-DOS volume. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Opened terminal via nautilus menu plugin thingy backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Simply I started the Gnome Terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
1. open terminal using "Open terminal" context menu (see package "nautilus-open-terminal") 2.crash backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
(In reply to comment #280) > Hello everyone, a solution that worked for me: Kill the gconfd-2 process, it > restarts instantly and you can use your device. A note that this solution > also works for launching a bug with gnome-journal-activity. Thx - killing gconfd-2 did solve it ;-) So in the first place we should find out why gconfd seams to hang... In case anyone wonders how to do that without terminal: Alt+F2 : killall gconfd-2
Used open from in terminal from nautilus. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I'm building a workaround patch that I think may help. I'll push an update to updates-testing and would appreciate feedback.
GConf2-3.2.5-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/GConf2-3.2.5-2.fc17
To give you some feedback cocerning your patch: Right now I receive some crashes in GConf2 during system startup (once per boot, not always but regularly). I was trying to report these crashes but unfortunately reporting system stops with a message like "Reporting stopped because traceback is not usable" ( - translated from German) The one good thing I can report is, that terminal does not seem to crash any more ;-) Any Idea how I can give you more information on your build?
Again I tried to send a bug report for gconf2 crashes but unfortunately the submitting process ended with: "Berichterstattung deaktiviert, da der Backtrace unbrauchbar ist." This is what I got: --- Running report_uReport --- (exited with 0) --- Running analyze_RetraceServer --- Servereinstellungen werden abgefragt Archiv wird zur Übertragung vorbereitet 108664 Byte werden übertragen Übertragung war erfolgreich Retrace-Vorgang wurde gestartet Initializing virtual root Initializing virtual root Initializing virtual root Initializing virtual root Initializing virtual root Initializing virtual root Initializing virtual root Retrace job finished successfully SRY Ray...
Package GConf2-3.2.5-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing GConf2-3.2.5-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14031/GConf2-3.2.5-2.fc17 then log in and leave karma (feedback).
Updated to GConf2-3.2.5-2.fc17 and it seem to be better (next day will tell if I'm right or wrong) :-)
Opened the application backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
I clicked on "Open in Terminal" on a folder in Nautilus and the terminal crashed. The folder is on an external hard disk. Not related but there seem to be a lot of issues with what really should have been a relatively simple piece of software... That's just me ranting on the terminal, ctrl+alt+f1 ftw :) backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
FWIW, I have a link to xterm in "favorites" - when I log in, I open xterm, do "pkill gconfd-2," and then gnome-terminal works just fine. It's a PITA to have to do that, but it works every time.
Package GConf2-3.2.5-3.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing GConf2-3.2.5-3.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14031/GConf2-3.2.5-3.fc17 then log in and leave karma (feedback).
I applied the patch in comment 296, and I thought it had fixed it, but I just had it happen again. I'll upload an sosreport in a minute.
Created attachment 623756 [details] sosreport taken just after the crash
lumch a terminal from nautilus with a nautilus-config-tool command : gnome-terminal --working-directory=%d backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I simply tried to start gnome-terminal and it crashed immediately. backtrace_rating: 4 Package: gnome-terminal-3.6.0-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
GConf2-3.2.5-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/GConf2-3.2.5-3.fc18
Launch gnome-terminal. This almost always is fixed by rebooting. It seems to have something to do with the gnome-settings-daemon incorrectly letting other apps that it is shutting down. So Revelation password app starts to fail, terminals won't start, etc. Rebooting stops this temporarily. I don't know what to do to trigger this, and abrt is not reporting a crash in any gnome-settings-daemon so just repoting in case it is a known issue and I can fix it. backtrace_rating: 4 Package: gnome-terminal-3.4.1.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
opening terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
opened terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Opened gnome-terminal backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
I've just tried to open gnome-terminal. backtrace_rating: 4 Package: gnome-terminal-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Just happened again for me in F18 x86_64 beta.
GConf2-3.2.5-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
works for me now on F17 64bit. Thanks
I have had again this problem on F17: gnome-terminal 3.4.1.1-1.fc17 GConf2 3.2.5-3.fc17
It just happened again on my F17, too. GConf2-3.2.5-3.fc17.x86_64 gnome-terminal-3.4.1.1-1.fc17.x86_64
Still happens in F18 x64 with all updates $ gnome-terminal ** ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Aborted
Fedora release 18 (Spherical Cow) 3.8.7-201.fc18.x86_64 Installing : gnome-terminal-3.6.1-2.fc18.x86_64 $ gnome-terminal ** ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Aborted (core dumped)