mythtv-setup.real assert failure: *** glibc detected *** /usr/bin/mythtv-setup.real: malloc(): memory corruption: 0x0000000001768480 ***

Bug #995941 reported by JanCeuleers
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Undecided
Unassigned

Bug Description

Attempting to run mythtv-setup -O ThemePainter=qt over an ssh -X connection causes myhtv-setup.real to crash with a memory corruption error.

The problem also occurs if I don't specify the Theme Painter manually (Michael T. Dean suggested that I do so).

Mythtv-setup works fine when I go over to the machine and run it there.

root@zotac:~# mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.24.2-30-ge9a0ecb
MythTV Branch : fixes/0.24
Network Protocol : 63
Library API : 0.24.20110505-1
QT Version : 4.7.2
Options compiled in:
 linux profile using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: mythtv-backend 2:0.24.2+fixes.20120409.e9a0ecb-0ubuntu0mythbuntu3
ProcVersionSignature: Ubuntu 2.6.38-14.58-generic 2.6.38.8
Uname: Linux 2.6.38-14-generic x86_64
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/mythtv-setup.real: malloc(): memory corruption: 0x0000000001768480 ***
CrashDB: mythbuntu
Date: Mon May 7 14:56:27 2012
ExecutablePath: /usr/bin/mythtv-setup.real
Installed_mythtv_dbg: 2:0.24.2+fixes.20120409.e9a0ecb-0ubuntu0mythbuntu3
ProcCmdline: /usr/bin/mythtv-setup.real -O ThemePainter=qt
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: mythtv
StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x7fed927230a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (av=0x7fed9295d1c0, bytes=<value optimised out>) at malloc.c:6283
 _int_malloc (av=0x7fed9295d1c0, bytes=<value optimised out>) at malloc.c:4396
Title: mythtv-setup.real assert failure: *** glibc detected *** /usr/bin/mythtv-setup.real: malloc(): memory corruption: 0x0000000001768480 ***
UpgradeStatus: Upgraded to natty on 2012-03-18 (50 days ago)
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin mythtv plugdev sambashare

Revision history for this message
JanCeuleers (jan-ceuleers) wrote :
visibility: private → public
Revision history for this message
JanCeuleers (jan-ceuleers) wrote :

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x7fed927230a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (av=0x7fed9295d1c0, bytes=<value optimised out>) at malloc.c:6283
 _int_malloc (av=0x7fed9295d1c0, bytes=<value optimised out>) at malloc.c:4396

Revision history for this message
JanCeuleers (jan-ceuleers) wrote : Stacktrace.txt
Revision history for this message
JanCeuleers (jan-ceuleers) wrote : ThreadStacktrace.txt
Revision history for this message
Andrew Stevens (andrew-stevens) wrote :

I got hit with this Issue too. I suspect a common factor is that X server to which mythtv-setup is being forward is hosted on 12.04.

The Problem only arose after and update on the the mythtv client side to 12.04 from 11.10, The server is (for now) still an 11.10 host.
 the

Revision history for this message
j spam (knowtrash2009) wrote :

The client and server are on the same machine. when not being used. the mythtv server crashed on its own.

Revision history for this message
Thomas Mashos (tgm4883) wrote :

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.

Changed in mythbuntu:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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