Bug 607312

Summary: [abrt] crash in me-tv-1.2.4-1.fc12: raise: Process /usr/bin/me-tv was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jan ONDREJ <ondrejj>
Component: me-tvAssignee: Thomas Janssen <thomasj>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: thomasj
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:7aa8918685958a920515e0f7030a3dc63d564b76
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-27 20:20:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Jan ONDREJ 2010-06-23 18:56:30 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: me-tv
component: me-tv
crash_function: raise
executable: /usr/bin/me-tv
global_uuid: 7aa8918685958a920515e0f7030a3dc63d564b76
kernel: 2.6.32.14-127.fc12.i686.PAE
package: me-tv-1.2.4-1.fc12
rating: 4
reason: Process /usr/bin/me-tv was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. first time crashed after channels have been added (required after update)
2. now craching when trying to change channel
Comment 1 Jan ONDREJ 2010-06-23 18:56:33 UTC 
Created attachment 426360 [details]
File: backtrace
Comment 2 Thomas Janssen 2010-06-26 20:03:17 UTC 
Upstreamed Bugurl: https://bugs.launchpad.net/me-tv/+bug/598889
Comment 3 Jan ONDREJ 2010-06-26 22:14:37 UTC 
Problem fixed after update to me-tv-1.2.6-1.fc12.i686.rpm.
I think you should close both bugs.

But when changing channel, I get always this message:

Failed to call Inhibit method

But it's still much better like before.
Comment 4 Thomas Janssen 2010-06-27 20:14:09 UTC 
Hi, good to read it's fixed :)

Upstream gave me the hint --no-screensaver-inhibit for you.