Menu

#82 2007-12-16 xVidcap now requiring dbus to be present?

SVN
open-works-for-me
5
2007-12-20
2007-12-17
No

Yesterday's change "* src/Makefile.am: fix build without dbus". Seems to have had almost the opposite of the intended effect.

Previously, I did *not* have the dbus-x11 package installed, but I could compile and run xvidcap on my system (Kubuntu 8.04 - Hardy Heron, AMD64) with no problems.

After this 2007-12-16 patch, the program *still* compiles fine, but I get the crash below when running it. Installing the dbus-X11 package makes the problem go away, but (if I understood the changelog correctly) dbus shouldn't really be necessary?

evil@pluto:~/src/xvidcap/trunk$ xvidcap

** (xvidcap:23220): WARNING **: Unable to connect to dbus: Failed to execute dbus-launch to autolaunch D-Bus session

** (xvidcap:23220): CRITICAL **: dbus_g_connection_register_g_object: assertion `connection != NULL' failed

** (xvidcap:23220): CRITICAL **: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed

** (xvidcap:23220): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
Segmentation fault (core dumped)

Discussion

  • Jesse Litton

    Jesse Litton - 2007-12-17
    • labels: --> build system
    • milestone: --> SVN
    • assigned_to: nobody --> charly4711
     
  • Karl H. Beckers

    Karl H. Beckers - 2007-12-17

    Logged In: YES
    user_id=782084
    Originator: NO

    funny,
    for me it did still try to compile xvidcap-dbus-client related files and failed. Can you provide an output of configure and your config.h?

     
  • Karl H. Beckers

    Karl H. Beckers - 2007-12-18

    Logged In: YES
    user_id=782084
    Originator: NO

    I cannot reproduce this.
    I have done this:

    remove dbus from pkgconfig, so autogen won't find it:
    # mv /usr/lib/pkgconfig/dbus*.pc /root

    do a fresh build:
    # make distclean
    # ./autogen.sh --prefix=/home/<username>/xvidcap
    # make && make install

    see what autogen found:
    # grep -i dbus config.h
    /* define if libdbus-1 and libdbus-glib-1 are usable */
    /* #undef USE_DBUS */
    looks good!

    double check that xvidcap is not linked to dbus libs still around:
    # ldd /home/kb87850/xvidcap/bin/xvidcap | grep -i bus
    this returns nothing, which is as desired.

    And lo, xvidcap runs fine, xvidcap-dbus-client has not been built.

     
  • Karl H. Beckers

    Karl H. Beckers - 2007-12-18
    • status: open --> pending-works-for-me
     
  • Jesse Litton

    Jesse Litton - 2007-12-20
    • status: pending-works-for-me --> open-works-for-me
     
  • Jesse Litton

    Jesse Litton - 2007-12-20

    Logged In: YES
    user_id=210111
    Originator: YES

    On my system, /usr/lib/pkgconfig/dbus-1.pc exists, even when dbus-x11 (which contains dbus-launch) is not installed. This seems to be the cause of the problem.

    If I remove/rename that file, it will have the proper #undef (and build/run correctly). If I don't, I get "#define USE_DBUS 1" instead.

    Maybe there needs to be a check for dbus-launch itself, instead?

    Thanks,
    J

     
  • Karl H. Beckers

    Karl H. Beckers - 2007-12-20

    Logged In: YES
    user_id=782084
    Originator: NO

    hmmm, on ubuntu gutsy dbus-launch is also in the "dbus" package. I don't have dbus-x11 installed. Could you let me know what dbus related packages and development packages are installed on your system, then also this:

    $ for i in /usr/lib/pkgconfig/dbus* ; do dpkg -S ${i} ; done
    libdbus-1-dev: /usr/lib/pkgconfig/dbus-1.pc
    libdbus-glib-1-dev: /usr/lib/pkgconfig/dbus-glib-1.pc
    python-dbus: /usr/lib/pkgconfig/dbus-python.pc

    Also, hasn't KDE also replaced dcop with dbus?

     
  • Mike Weston

    Mike Weston - 2008-03-20

    Logged In: YES
    user_id=2041374
    Originator: NO

    The program 'xvidcap' received an X Window System
    error.
    This probably reflects a bug in the program.
    The error was 'BadMatch (invalid parameter
    attributes)'.
    (Details: serial 512450 error_code 8 request_code 161
    minor_code 1)
    (Note to programmers: normally, X errors are reported
    asynchronously;
    that is, you will receive the error a while after
    causing it.
    To debug your program, run it with the --sync command
    line
    option to change this behavior. You can then get a
    meaningful
    backtrace from your debugger if you break on the
    gdk_x_error() function.)

    This Errormessage will appear when Audioinput is set:
    to /dev/dsp.
    XVIDCAP crashing!!!
    ___________________________________________________
    xtoffmpeg.c add_audio_stream(): Cannot open /dev/adsp:
    -2

    This Errormessage will appear when Audioinput is set:
    to /dev/adsp.
    Xvidcap renders but without audio!

    HTH
    Mike

     
  • Mike Weston

    Mike Weston - 2008-03-20

    Logged In: YES
    user_id=2041374
    Originator: NO

    The program 'xvidcap' received an X Window System
    error.
    This probably reflects a bug in the program.
    The error was 'BadMatch (invalid parameter
    attributes)'.
    (Details: serial 512450 error_code 8 request_code 161
    minor_code 1)
    (Note to programmers: normally, X errors are reported
    asynchronously;
    that is, you will receive the error a while after
    causing it.
    To debug your program, run it with the --sync command
    line
    option to change this behavior. You can then get a
    meaningful
    backtrace from your debugger if you break on the
    gdk_x_error() function.)

    This Errormessage will appear when Audioinput is set:
    to /dev/dsp.
    XVIDCAP crashing!!!
    ___________________________________________________
    xtoffmpeg.c add_audio_stream(): Cannot open /dev/adsp:
    -2

    This Errormessage will appear when Audioinput is set:
    to /dev/adsp.
    Xvidcap renders but without audio!

    HTH
    Mike

     
  • Karl H. Beckers

    Karl H. Beckers - 2008-03-20

    Logged In: YES
    user_id=782084
    Originator: NO

    Please do not hijack existing bug reports

     

Log in to post a comment.