#84 GUI locks up while recording

closed-invalid
Gtk2 GUI (20)
5
2008-05-23
2008-02-02
Elliot Murphy
No

Hi!
Xvidcap is great. I've been trying to use it to record screencasts, and have hit a problem on several Ubuntu machines (compiled the latest version from svn) where the GUI just locks up a few seconds after I start recording.

Is there any kind of debug information I can provide?

Discussion

  • Logged In: YES
    user_id=782084
    Originator: NO

    what version of ubuntu? Hardy?
    I'm on gutsy with no such problems. Have heard about Fedora 8, though where such problems were related to bugs in libX11 and libxcb.
    Please provide the output of "ldd <path-to-xvidcap>/xvidcap"

     
  • crotalus
    crotalus
    2008-02-03

    Logged In: YES
    user_id=1373726
    Originator: NO

    Hi,

    I had the same problem in Fedora 8, and it was related to this bug:

    Bugzilla Bug #254144 (not thread-safe?), which made me
    to downgrade to the libX11 from F7.

    https://bugzilla.redhat.com/show_bug.cgi?id=254144

    I packaged xvidcap-1.1.7 rc1 for F8, but I did not test it yet
    with an updated libX11. But it is working fine with the downgraded
    libX11.

    /Paulo Roma

     
    • assigned_to: nobody --> charly4711
    • status: open --> pending-invalid
     
  • Logged In: YES
    user_id=782084
    Originator: NO

    Please provide feedback.
    Otherwise this will automatically close in two weeks.

     
  • Elliot Murphy
    Elliot Murphy
    2008-03-13

    Logged In: YES
    user_id=452698
    Originator: YES

    yes, this is on hardy. sorry it took me so long to respond. I'm attaching the ldd output.
    File Added: xvidcap_ldd.txt

     
  • Elliot Murphy
    Elliot Murphy
    2008-03-13

    output from ldd /usr/local/bin/xvidcap

     
    Attachments
  • Elliot Murphy
    Elliot Murphy
    2008-03-13

    • status: pending-invalid --> open-invalid
     
  • Logged In: YES
    user_id=782084
    Originator: NO

    Can reproduce this behaviour on hardy now (that I have a hardy machine).
    It can be solved by the following before starting xvidcap:
    export LIBXCB_ALLOW_SLOPPY_LOCK=1
    This also confirms that the underlying issue is the known xcb issue, not an xvidcap issue. Fedora e. g. has sloppy lock on by default, now.

     
    • status: open-invalid --> closed-invalid