http://bugzilla.suse.com/show_bug.cgi?id=1102764 http://bugzilla.suse.com/show_bug.cgi?id=1102764#c6 Dave Howorth changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(novell@howorth.or | |g.uk) | --- Comment #6 from Dave Howorth --- (In reply to Josef Reidinger from comment #5)

I check logs and I see that it failed due to SIGTERM. Which means that something send signal to application. Usual suspicions are:

1) user send it 2) oomkiller when there is not enough memory 3) desktop after some notice about unresponsive process

Dave - so to find what can be reason can you please write if:

1) can you reproduce failure?

No, it hasn't failed again that I know of.

2) how much memory machine has?

It has 8 GB RAM and 30 GB swap.

3) you do not send any kill neither confirm any desktop unresponsive popup?

Not that I remember.

Thanks

-- You are receiving this mail because: You are on the CC list for the bug.