abrt 1.0.4 detected a crash. architecture: i686 cmdline: /usr/bin/python /usr/bin/terminator component: terminator executable: /usr/bin/terminator kernel: 2.6.31.12-174.2.3.fc12.i686 package: terminator-0.13-3.fc12 release: Fedora release 12 (Constantine) backtrace ----- Summary: TBff3dff74 terminatorterm.py:730:reconfigure_vte:TypeError: Vte.Terminal.set_background_image_file() argument 1 must be string, not None Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/terminatorlib/prefs_profile.py", line 345, in apply self.term.reconfigure_vtes() File "/usr/lib/python2.6/site-packages/terminatorlib/terminator.py", line 1353, in reconfigure_vtes term.reconfigure_vte () File "/usr/lib/python2.6/site-packages/terminatorlib/terminatorterm.py", line 730, in reconfigure_vte self._vte.set_background_image_file (self.conf.background_image) TypeError: Vte.Terminal.set_background_image_file() argument 1 must be string, not None Local variables in innermost frame: palette: [gtk.gdk.Color('#000'), gtk.gdk.Color('#cdcb00000000'), gtk.gdk.Color('#0000cdcb0000'), gtk.gdk.Color('#cdcbcdcb0000'), gtk.gdk.Color('#1e1a908fffff'), gtk.gdk.Color('#cdcb0000cdcb'), gtk.gdk.Color('#0000cdcbcdcb'), gtk.gdk.Color('#e5e2e5e2e5e2'), gtk.gdk.Color('#4ccc4ccc4ccc'), gtk.gdk.Color('#f00'), gtk.gdk.Color('#0f0'), gtk.gdk.Color('#ff0'), gtk.gdk.Color('#46458281b4ae'), gtk.gdk.Color('#f0f'), gtk.gdk.Color('#0ff'), gtk.gdk.Color('#fff')] fg_color: gtk.gdk.Color('#021102110211') color: '#ffffffffffff' widget: None self: <TerminatorTerm object at 0xb729a93c (GtkVBox at 0x9064f30)> background_type: 'image' delbind: 3 cursor_color: '#021102110211' bg_color: gtk.gdk.Color('#a318a318a318') colors: ['#000000000000', '#cdcb00000000', '#0000cdcb0000', '#cdcbcdcb0000', '#1e1a908fffff', '#cdcb0000cdcb', '#0000cdcbcdcb', '#e5e2e5e2e5e2', '#4ccc4ccc4ccc', '#ffff00000000', '#0000ffff0000', '#ffffffff0000', '#46458281b4ae', '#ffff0000ffff', '#0000ffffffff', '#ffffffffffff'] backbind: 2 backspace: 'ascii-del' delete: 'escape-sequence'
Created attachment 388392 [details] File: backtrace
Would it be possible to give some information on what you did while this crash occured?
Can you please also check your ~/.config/terminator/config if it includes the background_image setting with a valid path? Leaving it empty or setting it to any other value won't work. If you don't like to have a background image in terminator at all, delete or comment out the concerning line.
the only thing I had done was change the transparency, used it for about an hour, and switched transparency off. I have been playing around with a lot of the settings since then so I'm not sure my config file useful.
It would be helpful to have a look at your configuration file, yes. I'd appreciate it, if it is possible to attach it here.
Created attachment 389254 [details] Default profile for gnome-terminal I was using the profile editor in gnome-terminal to make changes to terminator so I don't have a terminator config file. Sorry this may have been useful earlier but I didn't rememeber that until I went looking for a config file.
You're sure there is no ~/.config/terminator/config in your home? I actually can not see any setting in the gnome-terminal profile which may concerns to a background image. So if the terminator config file is not there, there shouldn't be any cause for the crash anymore (since it claimed about a non-existing background image). In that case - could you try to reproduce the crash?
terminator-0.14-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/terminator-0.14-1.fc11
terminator-0.14-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/terminator-0.14-1.fc12
The update to terminator 0.14 may fixes this issue. Could you please confirm?
terminator-0.14-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update terminator'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-1851
terminator-0.14-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update terminator'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1882
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.