Segmentation fault

Bug #1312473 reported by HemantMS
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Terminator
Invalid
Undecided
Unassigned

Bug Description

After first install of terminator 0.97 on a fresh ubuntu 12.04LTS, can not launch terminator. It crashes with segmentation fault.

Tags: no-response
Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

Hi, thanks for the bug report, but having read through it, it seems to be lacking enough detail to enable me to reproduce.

Please see http://gnometerminator.blogspot.de/p/introduction.html for additional instructions specific to Terminator in the Bugs/Problems/Help section.
Also see http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for good advice on providing effective bug reports.

Changed in terminator:
status: New → Incomplete
Revision history for this message
HemantMS (hemantms) wrote :

Appreciate the quick turn around.

Here is some more info :
Version: terminator 0.97

OS : Ubuntu 12.04LTS

Steps to Reproduce:
- Install terminator using <sudo apt-get install terminator>
- Invoke terminator from the prompt. <terminator>

Actual Result:
terminator does not launch. Ends with a Segmentation fault.

Debug output :

$ terminator --debug
ConfigBase::__init__: Borg::__init__: Preparing borg state for ConfigBase
noclass::get_config_dir: Found config dir: /home/hemant/.config
ConfigBase::load: looking for config file: /home/hemant/.config/terminator/config
ConfigBase::load: config validated successfully
ConfigBase::load: ConfigBase::load: Processing section: global_config
ConfigBase::load: ConfigBase::load: Processing section: keybindings
ConfigBase::load: ConfigBase::load: Processing section: profiles
ConfigBase::load: ConfigBase::load: Processing section: layouts
ConfigBase::load: ConfigBase::load: Processing section: plugins
Config::set_profile: Config::set_profile: Changing profile to default
noclass::parse_options: OptionParse::parse_options: command line options: {'nodbus': None, 'classname': None, 'working_directory': None, 'fullscreen': None, 'layout': 'default', 'debug_classes': None, 'version': None, 'role': None, 'forcedicon': None, 'config': '/home/hemant/.config/terminator/config', 'profile': None, 'debug_methods': None, 'maximise': None, 'debug': 1, 'borderless': None, 'new_tab': None, 'hidden': None, 'dummy': None, 'execute': None, 'geometry': None, 'command': None, 'forcedtitle': None}
ConfigBase::load: ConfigBase::load: config already loaded
Config::set_profile: Config::set_profile: Changing profile to default
ConfigBase::get_item: ConfigBase::get_item: dbus found in globals: False
noclass::<module>: dbus disabled
noclass::<module>: dbus not imported
Factory::__init__: Borg::__init__: Preparing borg state for Factory
Terminator::__init__: Borg::__init__: Preparing borg state for Terminator
ConfigBase::load: ConfigBase::load: config already loaded
Config::set_profile: Config::set_profile: Changing profile to default
noclass::get_pid_cwd: Using Linux get_pid_cwd
Terminator::attempt_gnome_client: GNOME session support enabled and registered
ConfigBase::get_item: ConfigBase::get_item: handle_size found in globals: -1
noclass::<module>: Creating a terminal with layout: default
Terminator::create_layout: Creating a window
Factory::make: Factory::make: created a Window
Terminator::register_window: Terminator::register_window: registering 20373584:<class 'terminatorlib.window.Window'>
ConfigBase::load: ConfigBase::load: config already loaded
Config::set_profile: Config::set_profile: Changing profile to default
Segmentation fault (core dumped)

Changed in terminator:
status: Incomplete → New
Revision history for this message
HemantMS (hemantms) wrote :

This crash report might help

Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

Hi Bug subscribers, this is the maintainer (Steve Boddy) of Terminator, who took over from Chris.

In case you were not aware there has been a new release 0.98 of Terminator in the last few days which has many changes, fixes and updates. We also have an ongoing GTK3 port which uses a much more up-to-date libvte.

Even with the ~50 issues closed by that release, and discounting the ~90 outstanding wishlist items, we still have an unwieldy 95 bugs. With the oldest approaching it's 6th birthday and some that haven't seen any updates in nearly 5, it is time for a purge.

My intention is to try and get this list down to a minimum, and for that I need your help.

First I'm going to work through, oldest to newest, setting bugs to Incomplete, pending confirmation that they are still an issue. If after a month there is no feedback, the issue will get closed as Invalid. Here's where you come in. I can't always reproduce, or setting up (i.e. other distros) to even test takes a long time, so I'm going to try crowdsourcing this.

1. Get the latest release. Is it still an issue? If yes, set the confirmed-0.98 tag. For bonus points follow the guide http://gnometerminator.blogspot.com/2015/09/so-you-want-to-try-terminator-gtk3.html and see if the GTK3 branch has same issue, and set the confirmed-gtk3 or notaffected-gtk3 tag.

2. Can you reproduce with an empty/default config file? You can pass "-g temp_config" to do this without affecting your existing config. If you already have Terminator running, you'll need to pass -u as well to disable the DBus.

3. If able to, can you reproduce with another user/guest account?

4. If the issue does not already have clear, precise instructions to reproduce with minimal setup/steps, add them.

5. Put as much info about what you are running.
   * Software/library versions (libvte, gtk, pango, cairo, distro, desktop environment, language)
   * Screens (single or multi)
   * Any unusual / custom packages or configs that might be interacting.

6. If possible attach the config file, unless the issue also happens with an empty one, but mention that.

7. Attach the "-d" debug output from 0.98.

Some common things that cause incidents.

* Strange sizing issues or rapidly shrinking windows - Try turning off Window geometry hints.
* Input (esp. broadcasting duplicate chars etc) problems - Try killing IBus.
* Hand editing of the config file can cause various issues - Due to misunderstanding, incorrect structure or typos.
* Some issues are actually in libvte - This is why testing GTK3 is so important.
* segfaults - Unfortunately these are dying inside the C libraries, and it is usually beyond me to fix those.

Many thanks for your assistance, and hopefully this will get us closer to a bug-free Terminator.

Changed in terminator:
status: New → Incomplete
Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

Very old bug. Codebase has moved on a long way. Segfaults were always because of something funky happening in the gtk2 libraries, and it was usually impossible (or very difficult) to figure out what was going wrong. Since the move to gtk3 I don't recall any segfaults in the gtk3 libraries. On top of that the OP has never returned to the bug.

Marking as Invalid/no-response.

tags: added: no-response
Changed in terminator:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.