me-tv-development team mailing list archive
-
me-tv-development team
-
Mailing list archive
-
Message #00429
[Bug 269911] Re: Runtime glibmm exception in me-tv 0.6
I've found (using a backtrace) that the problem is something to do with the channels dialog (not sure exactly what though). If I change line 216 in main_window.cc from:
gint dialog_result = channels_dialog.run();
to:
gint dialog_result = 1; //channels_dialog.run();
me-tv will actually start up, though no channels are listed in the EPG
etc (probably because I killed the channels dialog).
I'll attach the backtrace aswell.
** Attachment added: "Backtrace"
http://launchpadlibrarian.net/17942154/bt
--
Runtime glibmm exception in me-tv 0.6
https://bugs.launchpad.net/bugs/269911
You received this bug notification because you are a member of Me TV
Development, which is subscribed to Me TV.
Status in Me TV, it's TV for me computer: Incomplete
Bug description:
Hi,
I configured me-tv-0.6 with --disabled-static --enable-shared --prefix=/tmp/rpm/me-tv in order to see if everything would build fine.
During make there were mostly no problems, except a few 'is depreciated warning's @see attached metv-0.6-compile-warning.txt.
But when launching me-tv (from BUILDDIR/src/me-tv, that is) it crashed with the following message:
<quote>
glibmm-ERROR **:
unhandled exception (type unknown) in signal handler
aborting...
Cannot access memory at address 0x150a8404
Killed
</quote>
I also attached the suprisingly slim backtrace and infos about installed glibmm packages, as well as the output of /proc/cpuinfo to help you understand where the problem could be.
Cheers,
Matthias
P.S. By the way, xine-lib currently in use is version 1.1.15
References