it crashes after upgrading to gnome 3

Bug #869826 reported by damjan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Terminator
Fix Released
Undecided
Unassigned

Bug Description

Using terminator heavily with tiled windows and vim in each, tileing even further, I've expirienced pretty often crash of the terminator (it is zombie in process table). I don't know exactly to reproduce it, but it seems control / super / alt key were always involved in the event causing the trouble.

Feel free to instruct how to produce logs for a help.

I'm using Ubuntu 11.04, but thrown away Unity and using Gnome 3 (so, it is kind of broken set-up).

Revision history for this message
Chris Jones (cmsj) wrote :

Please run Terminator from another terminal (for example GNOME Terminal). When it crashes you should see some messages in the other terminal about what happened. Please attach them to this bug. Thanks!

Revision history for this message
damjan (damjan-zemljic) wrote :

I've followed the start of the terminator as instructed. Apart from that, regular updates of the system are done as well. It seems with the updates, the fix for the problem has been received too.

So, I've tested it but cannot reproduce the problem anymore and as for me, it can be closed (not reproducable).

Revision history for this message
damjan (damjan-zemljic) wrote :

Hi,
back again, unfortunately. In last two working days terminator crashed two times again. It is not that often as it used to be, but it is annoying (since the rest of the SW is great ;).

Nothing can be seen in the console / terminal from where the terminator is started.
Nothing is logged in the system logs (checked kernel & syslog).

In the process table:
damjan 4113 3905 0 09:50 pts/0 00:00:41 /usr/bin/python /usr/bin/terminator
damjan 4116 4113 0 09:50 pts/0 00:00:00 [/usr/bin/termin] <defunct>

Terminator flashes cursor normally (it detects focus correctly), but that's all what's left from it.

Br,
Damjan

Revision history for this message
damjan (damjan-zemljic) wrote :

Another point:
while crashed I was using multiple tabs. Closing the one that crashed allows me to work with the rest without the problem.

Revision history for this message
Chris Jones (cmsj) wrote :

Are you still getting these crashes? If so could you please follow the instructions in my first comment, to get some debugging info?

Changed in terminator:
status: New → Incomplete
Revision history for this message
damjan (damjan-zemljic) wrote : Re: [Bug 869826] Re: it crashes after upgrading to gnome 3

Hi,
no crashes any more (I'm on latest Ubuntu LTS - always just upgraded
(never done a clean install)).

It can be said "not reproducable".

Thanks for very usefull terminal.

Br,
Damjan

On 30. 01. 2013 11:04, Chris Jones wrote:
> Are you still getting these crashes? If so could you please follow the
> instructions in my first comment, to get some debugging info?
>
> ** Changed in: terminator
> Status: New => Incomplete
>

Chris Jones (cmsj)
Changed in terminator:
status: Incomplete → Fix Released
Revision history for this message
damjan (damjan-zemljic) wrote :

Hi, I've reopened this one since it appeared again and I finnaly found out how to reproduce it:
- open vim with some text file and press "CTRL + S" (I did this by mistake using different editors).

After that terminal tab hangs.
Using Ubuntu LTS, 64 bit.

Changed in terminator:
status: Fix Released → New
Revision history for this message
damjan (damjan-zemljic) wrote :

Tried the same on Debian Wheezy (64 bit) and no problems.

However, problem might not be in terminator. The difference between Debian and Ubuntu I've noticed:
- keyboard shortcuts do work with Terminator on Debian (i.e. ALT + F10, 'arrow up' to revoke last command in sqlite3 shell etc.), while they don't in Ubuntu.

Revision history for this message
Chris Jones (cmsj) wrote :

Ctrl S is "Scroll Lock". Hit Ctrl Q and your terminal will come back to life, this is ancient terminal behaviour that is stupid and unhelpful, but it is what it is.

Changed in terminator:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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