Bug 37295 - "invalid request, socket fd %d not open" but no disconnected signal
Summary: "invalid request, socket fd %d not open" but no disconnected signal
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: 1.4.x
Hardware: Other Linux (All)
: medium normal
Assignee: Havoc Pennington
QA Contact: John (J5) Palmieri
Keywords: NEEDINFO
Depends on:
Reported: 2011-05-17 11:01 UTC by tuqiang2009
Modified: 2014-09-11 10:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description tuqiang2009 2011-05-17 11:01:08 UTC
with dbus 1.4.6, after about 10M calls, I got the error "invalid request, socket fd 7 not open".But never get a disconnected signal. There are 2 issue here:
1. why the fd become invalid
2. If the fd become invalid, need a disconnected signal so app can try to reconnect.
It reproducible without verbose log, but take too long to reproduce it with verbose log.
Any suggestion?
Comment 1 tuqiang2009 2011-05-17 13:38:14 UTC
looks the reason the connection is disconnected is:
before I use DBusConnection *, I use dbus_connection_ref and later dbus_connection_unref, somehow dbus_connection_unref will call _dbus_connection_last_unref even I'm sure I call dbus_connection_ref and dbus_connection_unref in pair.
Comment 2 Simon McVittie 2011-06-07 02:18:54 UTC
Can you provide source code that reproduces this issue?

You might find it useful to apply the patches from Bug #37286 and run under valgrind with DBUS_CONNECTION_TRACE=1 in the environment. (This will take a long time, but will indicate where your connections are reffed/unreffed.)
Comment 3 Simon McVittie 2014-09-11 10:09:08 UTC
More information requested 3 years ago and not supplied; there isn't enough here to diagnose or fix a bug, so closing as WORKSFORME.

If you have this symptom, please open a new bug (or reopen, if you are the original reporter) with more information.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.