Bug 555529

Summary: [abrt] crash in me-tv-1.1.3-1.fc12
Product: [Fedora] Fedora Reporter: zimon <zimon>
Component: me-tvAssignee: Zarko (grof) <zarko.pintar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: zarko.pintar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:c1c1f7c8bc0026d639971387ffb6465e3f2bae88
Fixed In Version: 1.1.6-1.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-22 22:32:27 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
me-tv run log with parameters which make it crash
none
backtrace of me-tv v1.1.5 crashing none

Description zimon 2010-01-14 17:55:38 UTC
abrt 1.0.3 detected a crash.

How to reproduce
-----
1. Just started me-tv
2. It crashed. Abrt noticed the crash and wanted to make a bug report

Comment
-----
me-tv version (me-tv-1.0.0-2.fc12.x86_64) used to work OK just in previous boot session.
Now after updates machine wanted to be rebooted. After the boot, new version me-tv crashes.

Attached file: backtrace
cmdline: me-tv --sm-config-prefix /me-tv-XRlY3V/ --sm-client-id 1016a6feb9f9fb46c126058864845484100000024370031 --screen 0
component: me-tv
executable: /usr/bin/me-tv
kernel: 2.6.31.9-174.fc12.x86_64
package: me-tv-1.1.3-1.fc12
rating: 4
reason: Process was terminated by signal 8 (Floating point exception)

Comment 1 zimon 2010-01-14 17:55:41 UTC
Created attachment 384399 [details]
File: backtrace

Comment 2 zimon 2010-01-14 18:33:55 UTC
Created attachment 384411 [details]
me-tv run log with parameters which make it crash

Well, I tried to reproduce and me-tv works now if started normally.
I have me-tv starting when I log in (start metacity session).

So I logged off, logged back in, and me-tv still crashes.
metacity is trying to run me-tv with parameters:
$ me-tv --sm-config-prefix /me-tv-XRlY3V/ --sm-client-id 1016a6feb9f9fb46c126058864845484100000024370031 --screen 0

When run this way, it crashes every time.

(Maybe  after I save new settings what programs should autostart when I log in, this problem goes away. System/Preferences/Startup_applications:Options/Automatically_remember_running_applications_when_logging_out)

But if it will crash this way every time the me-tv version and package is updated, I think it is a problem and bug to be fixed.

Comment 3 zimon 2010-01-17 21:58:35 UTC
Created attachment 384968 [details]
backtrace of me-tv v1.1.5 crashing

me-tv v 1.1.5 still crashes with the same (bogus) parameters. The backtrace is also the same (at least the function callstack)
$ me-tv --sm-config-prefix /me-tv-XRlY3V/ --sm-client-id 1016a6feb9f9fb46c126058864845484100000024370031 --screen 0

Comment 4 Zarko (grof) 2010-01-18 07:10:56 UTC
I reported bug to upstream here:

https://bugs.launchpad.net/me-tv/+bug/509029

Comment 5 Fedora Update System 2010-01-22 11:09:23 UTC
me-tv-1.1.6-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/me-tv-1.1.6-1.fc12

Comment 6 Fedora Update System 2010-01-22 11:09:28 UTC
me-tv-1.1.6-1.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/me-tv-1.1.6-1.fc11

Comment 7 Fedora Update System 2010-01-22 22:32:22 UTC
me-tv-1.1.6-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2010-01-22 22:33:15 UTC
me-tv-1.1.6-1.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.