[mythtv] transcode hangs after finishing with 0.22

[Sid Boyce]

On 24/12/09 14:52, Martin Koller wrote:
> I'm running mythtv-0_22-common-0.22-0.pm.6.1 on openSuse 11.0 and since upgrading from 0.21
> I've always a lot of transcode tasks hanging obviously after they finished their job.
> 
> E.g. today:
> 
> root      7532     1  0 06:15 ?        00:00:00 /usr/bin/mythtranscode -j 3524 -V 4194307 -p autodetect
> root      7685     1  0 07:26 ?        00:00:00 /usr/bin/mythtranscode -j 3526 -V 4194307 -p autodetect
> root      8687     1  0 14:04 ?        00:00:00 /usr/bin/mythtranscode -j 3528 -V 4194307 -p autodetect
> root      8749     1  0 14:29 ?        00:00:00 /usr/bin/mythtranscode -j 3530 -V 4194307 -p autodetect
> root      8881     1  0 14:59 ?        00:00:00 /usr/bin/mythtranscode -j 3532 -V 4194307 -p autodetect
> root      9427     1  0 17:24 ?        00:00:00 /usr/bin/mythtranscode -j 3535 -V 4194307 -p autodetect
> root     15948     1  0 18:31 ?        00:00:00 /usr/bin/mythtranscode -j 3537 -V 4194307 -p autodetect
> 
> Doing an strace -p 7532 shows:
> Process 7532 attached - interrupt to quit
> futex(0x80a3584, FUTEX_WAIT_PRIVATE, 1, NULL
> 
> So it seems a thread is hanging waiting for something which does not happen ...
> 
> In the mythtv logfile, I see that the jobs have finished, e.g.
> ...
> 2009-12-18 17:24:49.224 JobQueue: Transcode Finished: Hinterm Sofa an der Front: Autodetect (1.2 GB)                  
> 2009-12-18 18:31:40.452 transcode: Transcode Finished: Still Standing: Autodetect (1.4 GB)
> (which correspond to the last 2 jobs from the above ps output)
> 
> Anybody here having the same problem ?
> Any developer with an idea what could be wrong ?
> 
> 
> 

The same problem under KDE4 only, but not under KDE3 or Gnome or as user
under KDE4.
Starting quite a few apps (e.g VirtualBox, qjackctl and others) as root
caused this to happen. It was reckoned to be a KDE problem with dbus,
fixed at 11.2.
If you intend to launch the application as root from a terminal under
openSUSE 11.0, using "su -" instead of just "su" to log in as root is
the work around.
Hope this helps.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks