SCIENTIFIC-LINUX-USERS Archives

July 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Sommerseth <[log in to unmask]>
Reply To:
Date:
Thu, 13 Jul 2017 01:16:47 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
On 12/07/17 21:04, ToddAndMargo wrote:
> Hi All,
> 
> SL 7.3
> 
> Whenever I "su" to root, I get this message.
> 
>     ABRT has detected 1 problem(s). For more info
>     run: abrt-cli list --since 1499813517
> 
>     # abrt-cli list --since 1499813517
>     id cb5d0f1321370b5113631236cf6788374b5508ac
>     reason:         file-roller killed by SIGSEGV
>     time:           Tue 11 Jul 2017 10:12:47 PM PDT
>     cmdline:        /usr/bin/file-roller '/tmp/mozilla_tony0/Part 1-2.2'
>     package:        file-roller-3.14.2-10.el7
>     uid:            500 (todd)
>     count:          1
>     Directory:      /var/spool/abrt/ccpp-2017-07-11-22:12:47-31925
> 
> File-roller seems to be running fine.  I use it a lot. Is this
> anything to be concerned about?

"killed by SIGSEGV" means "the program crashed unexpectedly", also known
as segmentation fault.  From the file path, it looks like a Thunderbird
process whacked the file file-roller was using, leading to a crash.

Now this isn't a nice behaviour, a program should account for something
being swept under its feet - at least the trivial things.  But unless
you've noticed any issues extracting contents from files opened with
file-roller, there's not much to worry about.

But a far more deep debug dump is needed to better understand why the
program segfaults.


-- 
kind regards,

David Sommerseth

ATOM RSS1 RSS2