qt4 mythphone: ASSERT failure in QWidget: "Widgets must be created in the GUI thread."

[nigel@…]

Hi guys.

Trying an update on the .21 branch (compiling from source, commit 16841). Compilation goes okay, but the frontend doesn't run successfully:

2008-03-30 20:59:23.478 Registering Internal as a media playback plugin. 2008-03-30 20:59:23.878 MonitorRegisterExtensions?(0x100, gif,jpg,png) 2008-03-30 20:59:25.292 MythMusic adding CD-Writer: ATA:0,0,0 -- DVD-RW DVRKD08 2008-03-30 20:59:25.487 MythMusic adding CD-Writer: ATAPI:0,0,0 -- DVD-RW DVRKD08 2008-03-30 20:59:25.675 MonitorRegisterExtensions?(0x40, ogg,mp3,aac,flac) ASSERT failure in QWidget: "Widgets must be created in the GUI thread.", file kernel/qwidget.cpp, line 959

[Roo <roo.watt@…>]

This may be a known issue, you can try removing mythphone if you have it installed and see if it fixes the issue.

[Niki]

I can confirm it on clean trunk with multiproto (dvb-s2) patch.

When I try to scan for a channels with mythtv-setup it crashes

2008-03-30 14:10:16.634 DiSEqCDevTree, Warning: No device tree for cardid 1
2008-03-30 14:10:16.636 New DB connection, total: 3
2008-03-30 14:10:16.637 Connected to database 'mythtv' at host: 192.168.0.100
2008-03-30 14:10:16.642 New DB connection, total: 4
2008-03-30 14:10:16.644 Connected to database 'mythtv' at host: 192.168.0.100
2008-03-30 14:10:16.645 New DB connection, total: 5
2008-03-30 14:10:16.646 Connected to database 'mythtv' at host: 192.168.0.100
2008-03-30 14:10:25.252 XMLParse::LoadTheme using /usr/local/share/mythtv/themes/default/keyboard/en_us_ui.xml
2008-03-30 14:10:29.134 DVBSM(0), Warning: Can not count Uncorrected Blocks
			eno: Operation not supported (95)
ASSERT failure in QWidget: "Widgets must be created in the GUI thread.", file kernel/qwidget.cpp, line 959
Aborted (core dumped)

[stuartm]

Sorry, are we talking trunk or 0.21? The OP says 0.21 which would definately not be a known bug. Trunk it might be a side effect of QT4, in which case it will be dealt with in time but isn't such a high priority.

Can I have --version output from anyone seeing this bug with 0.21-fixes.

[anonymous]

The ticket is posted in the wrong category as far as I can tell. The owner tried to update from 0.21 to 16841, which is trunk.

MythTV Version   : 16842M
MythTV Branch    : trunk
Library API      : 0.22.20080320-2
Network Protocol : 40
Options compiled in:
 linux release using_oss using_alsa using_arts using_jack using_backend using_dbox2
using_directfb using_dvb using_firewire using_frontend using_hdhomerun using_iptv using_ivtv
using_joystick_menu using_lirc using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmcw
using_xvmc_vld using_bindings_perl using_bindings_python using_opengl using_ffmpeg_threads
using_libavc_5_3 using_live

[Roo <roo.watt@…>]

Replying to stuartm:

Sorry, are we talking trunk or 0.21? The OP says 0.21 which would definately not be a known bug.

Sorry, I should know better than to reply to tickets without enough sleep. :(

[nigel@…]

Actually, I think you're right, Roo. When I run svn log, it's showing trunk commits. I'm not svn expert, so perhaps I ran the wrong command when checking out the source. Could the branch therefore be changed to trunk and/or the bug marked as a dup if necessary?

FWIW, building plugins without MythPhone? didn't help.

Nigel

[Janne Grunau]

The old plugin is probably still around. After deleting $PREFIX/lib/mythtv/plugins/libmythphone.so the frontend should start.

svn info displays information about the repository. If the URL contains trunk, it is a trunk checkout. if it contains branches/release-0-21-fixes it is a checkout of the 0.21 release branch.

[wiz561@…]

Had the same exact problem. I checked out the latest svn (Revision: 16978), cleaned EVERYTHING out mythtv related except the source. I didn't do a make uninstall, but actually rm'ed all the files. Compiled the svn, installed, and the same error message on the frontend.

I then deleted the libmythphone.so and that did the trick.

Thanks!

[Roo <roo.watt@…>]

Commit log seems to indicate that [17168] should fix this, unable to test it at the moment though.

[danielk]

Yup, fixed. Didn't know about this ticket...