Opened 12 years ago

Closed 11 years ago

#411 closed Bug Report (worksforme)

incorrect arguments to dbus_connection_get_data()

Reported by: anntoin Owned by: David Robillard
Priority: trivial Component: Patchage
Keywords: Cc:


Installed patchage via the archaudio repositries (so this might not be a problem on your side) but anyhow might be good to be aware of this behaviour.

When I start patchage I get this error;

Loading configuration file /home/user/.patchagerc
Unable to load file /home/user/.patchagerc[[BR]] process 2312: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5758.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace

When I create a blank file in my home called .patchagerc

Loading configuration file /home/user/.patchagerc
Caught exception, aborting. Error message was: Corrupt settings file: expected "zoom_level", found ""

Would it be possible to get an example patchagerc to see if this is the problem - googling has returned nothing.

Change History (3)

comment:1 Changed 12 years ago by David Robillard

Summary: No .patchagerc in homeincorrect arguments to dbus_connection_get_data()

Missing .patchagerc is not a problem, it just holds module positions and such.

The second error message is correct, since you made a corrupt one by hand ;)

comment:2 in reply to:  1 Changed 12 years ago by anntoin

True, worth a shot though.

If I can help out with this let me know what I can do, looking forward to using patchage.

Here's the strace:
Only thing I noticed in it is this call
read(3, 0x24986b4, 4096)
which always gives the error

-1 EAGAIN (Resource temporarily unavailable)

kernel version: 2.6.30-ARCH

comment:3 Changed 11 years ago by David Robillard

Resolution: worksforme
Status: newclosed

Current version of Patchage code doesn't (directly) call this function, and I'm told this problem is not happening for others.

If this is still a problem, please attach a backtrace and re-open the bug.

Note: See TracTickets for help on using tickets.