Me TV

lucid 10.04 me-tv 1.2.1 crashed

Bug #575860 reported by zarzycki.andrzej@googlemail.com on 2010-05-05

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Me TV	Invalid	Undecided	Unassigned

Bug Description

May 3 21:04:04 linux kernel: [ 120.946120] me-tv[5890]: segfault at 7f6400000001 ip 00007f6400000001 sp 00007ffff5baf820 error 14
May 3 21:04:17 linux kernel: [ 134.480037] DiB0070 I2C read failed
May 3 21:04:17 linux kernel: [ 134.480042] DiB0070 I2C write failed
May 3 21:07:06 linux kernel: [ 303.457145] tvtime[12864]: segfault at 840 ip 0000000000407400 sp 00007ffff0d0cb08 error 4 in tvtime[400000+7e000]
May 3 21:07:28 linux kernel: [ 324.760090] DiB0070 I2C read failed
May 3 21:07:28 linux kernel: [ 324.760095] DiB0070 I2C write failed
May 3 21:07:33 linux kernel: [ 330.022318] me-tv[20549]: segfault at 7fbe00000001 ip 00007fbe00000001 sp 00007fff898de920 error 14

May 4 17:03:25 linux kernel: [ 3865.225451] me-tv[4314]: segfault at 2d ip 00007fd7e616601b sp 00007fff4117ba70 error 4 in libstdc++.so.6.0.13[7fd7e60bd000+f6000]

me-tv forget configuration path to store records

Andy

Revision history for this message

zarzycki.andrzej@googlemail.com (zarzycki-andrzej) wrote on 2010-05-05:

ubuntu ultimate edition 2.6 64bit, AMD 3-Core, Terratec USB XXS, 4GB Memory

Revision history for this message

Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote on 2010-05-05:

Needs a backtrace, stacktrace or core file.

Changed in me-tv:
status:	New → Incomplete

Revision history for this message

elfrench (elfrench) wrote on 2010-05-07:

I think this error is the same as mine

Me TV 1.2.2
07/05/10 20:08:55: Scanning DVB devices ...
07/05/10 20:08:55: Opening frontend device: /dev/dvb/adapter0/frontend0
07/05/10 20:08:55: Device: 'DiBcom 7000PC' (DVB-T) at "/dev/dvb/adapter0/frontend0"
07/05/10 20:08:55: Application constructor
07/05/10 20:08:55: sqlite3_threadsafe() = 1
07/05/10 20:08:55: Database 'exists'
07/05/10 20:08:55: Opening database file '/home/frenchi/.local/share/me-tv/me-tv.db'
07/05/10 20:08:55: Loading UI files
07/05/10 20:08:56: Application constructed
07/05/10 20:08:56: Initialising table 'version'
07/05/10 20:08:56: Required Database version: 6
07/05/10 20:08:56: Actual Database version: 6
07/05/10 20:08:56: Me TV database initialised
07/05/10 20:08:56: StatusIcon constructor started
07/05/10 20:08:56: StatusIcon constructed
07/05/10 20:08:56: MainWindow constructor
07/05/10 20:08:56: Setting integer combo box size to 0
07/05/10 20:08:56: MainWindow constructed
07/05/10 20:08:56: Loading channels ...
07/05/10 20:08:56: Channels loaded
07/05/10 20:08:56: Creating stream manager
07/05/10 20:08:56: Creating frontend thread
07/05/10 20:08:56: Thread 'Frontend' created
07/05/10 20:08:56: Creating FrontendThread (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: FrontendThread created (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Starting frontend thread
07/05/10 20:08:56: Starting frontend thread (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Waiting for 'Frontend' to start
07/05/10 20:08:56: Frontend thread running (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Opening frontend device '/dev/dvb/adapter0/dvr0' for reading ...
07/05/10 20:08:56: Frontend device opened (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Entering FrontendThread loop (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Frontend is not tuned, waiting (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Thread 'Frontend' started
07/05/10 20:08:56: Loading scheduled recordings
07/05/10 20:08:56: Scheduled recordings loaded
07/05/10 20:08:56: Setting geometry (0, 0, 0, 0)
07/05/10 20:08:56: Exception: Failed to get display stream
07/05/10 20:08:57: Frontend is not tuned, waiting (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:57: Updating EPG
07/05/10 20:08:57: EPG update complete
07/05/10 20:08:57: Checking scheduled recordings
07/05/10 20:08:57: Removing scheduled recordings older than 1273255737
07/05/10 20:08:57: Saving 0 scheduled recordings
07/05/10 20:08:57: Deleting old scheduled recordings ending before 1273255737
07/05/10 20:08:57: Scheduled recordings saved
07/05/10 20:08:57: Saving channels
07/05/10 20:08:57: Channels saved
07/05/10 20:08:57: Deleting old EPG events
07/05/10 20:08:57: EPG events saved
07/05/10 20:08:57: Exception: No channel selected

(me-tv:3580): GLib-CRITICAL **: g_main_loop_is_running: assertion `g_atomic_int_get (&loop->ref_count) > 0' failed
Fallo de segmentación

I think this error is the same as mine

Me TV 1.2.2
07/05/10 20:08:55: Scanning DVB devices ...
07/05/10 20:08:55: Opening frontend device: /dev/dvb/adapter0/frontend0
07/05/10 20:08:55: Device: 'DiBcom 7000PC' (DVB-T) at "/dev/dvb/adapter0/frontend0"
07/05/10 20:08:55: Application constructor
07/05/10 20:08:55: sqlite3_threadsafe() = 1
07/05/10 20:08:55: Database 'exists' 
07/05/10 20:08:55: Opening database file '/home/frenchi/.local/share/me-tv/me-tv.db'
07/05/10 20:08:55: Loading UI files
07/05/10 20:08:56: Application constructed
07/05/10 20:08:56: Initialising table 'version'
07/05/10 20:08:56: Required Database version: 6
07/05/10 20:08:56: Actual Database version: 6
07/05/10 20:08:56: Me TV database initialised
07/05/10 20:08:56: StatusIcon constructor started
07/05/10 20:08:56: StatusIcon constructed
07/05/10 20:08:56: MainWindow constructor
07/05/10 20:08:56: Setting integer combo box size to 0
07/05/10 20:08:56: MainWindow constructed
07/05/10 20:08:56: Loading channels ...
07/05/10 20:08:56: Channels loaded
07/05/10 20:08:56: Creating stream manager
07/05/10 20:08:56: Creating frontend thread
07/05/10 20:08:56: Thread 'Frontend' created
07/05/10 20:08:56: Creating FrontendThread (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: FrontendThread created (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Starting frontend thread
07/05/10 20:08:56: Starting frontend thread (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Waiting for 'Frontend' to start
07/05/10 20:08:56: Frontend thread running (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Opening frontend device '/dev/dvb/adapter0/dvr0' for reading ...
07/05/10 20:08:56: Frontend device opened (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Entering FrontendThread loop (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Frontend is not tuned, waiting (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:56: Thread 'Frontend' started
07/05/10 20:08:56: Loading scheduled recordings
07/05/10 20:08:56: Scheduled recordings loaded
07/05/10 20:08:56: Setting geometry (0, 0, 0, 0)
07/05/10 20:08:56: Exception: Failed to get display stream
07/05/10 20:08:57: Frontend is not tuned, waiting (/dev/dvb/adapter0/frontend0)
07/05/10 20:08:57: Updating EPG
07/05/10 20:08:57: EPG update complete
07/05/10 20:08:57: Checking scheduled recordings
07/05/10 20:08:57: Removing scheduled recordings older than 1273255737
07/05/10 20:08:57: Saving 0 scheduled recordings
07/05/10 20:08:57: Deleting old scheduled recordings ending before 1273255737
07/05/10 20:08:57: Scheduled recordings saved
07/05/10 20:08:57: Saving channels
07/05/10 20:08:57: Channels saved
07/05/10 20:08:57: Deleting old EPG events
07/05/10 20:08:57: EPG events saved
07/05/10 20:08:57: Exception: No channel selected

(me-tv:3580): GLib-CRITICAL **: g_main_loop_is_running: assertion `g_atomic_int_get (&loop->ref_count) > 0' failed
Fallo de segmentación

Revision history for this message

Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote on 2010-05-07:

I don't think that these issues are related. Can you please create another bug.

Revision history for this message

elfrench (elfrench) wrote on 2010-05-08:

UPSSS...I was wrong bug sorry

Revision history for this message

Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote on 2010-05-09:

So, can I close this? Does this still happen?

Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) on 2010-05-11

Changed in me-tv:
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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