Hi, all
After upgrading to qt 4.4.2-1, I found that some qt4 program became broken, such as VirtualBox, and Qterm. All of these programs get a error like this:
process 4272: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details. Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection. D-Bus not built with -rdynamic so unable to print a backtrace Aborted
Is it really a bug of application, or just a bug of qt, or just a bug for this package?
Lee MaRS schrieb:
Hi, all
After upgrading to qt 4.4.2-1, I found that some qt4 program became broken, such as VirtualBox, and Qterm. All of these programs get a error like this:
process 4272: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details. Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection. D-Bus not built with -rdynamic so unable to print a backtrace Aborted
Is it really a bug of application, or just a bug of qt, or just a bug for this package?
My suspect here is qt. All the talk above comes from dbus, talking about "an application" doing things wrong. From the programmer of a qt application, dbus should be invisible.
Can be, but must not be.
But you're right, most likely it's a bug in QT.
On Fri, Sep 19, 2008 at 7:37 PM, Thomas Bächler thomas@archlinux.orgwrote:
Lee MaRS schrieb:
Hi, all
After upgrading to qt 4.4.2-1, I found that some qt4 program became broken, such as VirtualBox, and Qterm. All of these programs get a error like this:
process 4272: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details. Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection. D-Bus not built with -rdynamic so unable to print a backtrace Aborted
Is it really a bug of application, or just a bug of qt, or just a bug for this package?
My suspect here is qt. All the talk above comes from dbus, talking about "an application" doing things wrong. From the programmer of a qt application, dbus should be invisible.
The qt package has been rebuilt to 4.4.2-2 . But it seems nothing changed... Qterm and VirtualBox are still broken.
On Sat, Sep 20, 2008 at 1:51 AM, Georg Grabler ggrabler@gmail.com wrote:
Can be, but must not be.
But you're right, most likely it's a bug in QT.
On Fri, Sep 19, 2008 at 7:37 PM, Thomas Bächler thomas@archlinux.org wrote:
Lee MaRS schrieb:
Hi, all
After upgrading to qt 4.4.2-1, I found that some qt4 program became broken, such as VirtualBox, and Qterm. All of these programs get a error like this:
process 4272: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details. Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection. D-Bus not built with -rdynamic so unable to print a backtrace Aborted
Is it really a bug of application, or just a bug of qt, or just a bug for this package?
My suspect here is qt. All the talk above comes from dbus, talking about "an application" doing things wrong. From the programmer of a qt application, dbus should be invisible.
Am Samstag 20 September 2008 11:25:50 schrieb Lee MaRS:
The qt package has been rebuilt to 4.4.2-2 . But it seems nothing changed... Qterm and VirtualBox are still broken.
This was just a security update. Can anybody else confirm this problem? Virtualbox is running fine here (the closed source version). Qterm seems not to be in our repos.
Hmm, I found that most of the qt4 program broken on my system. I am using the testing repository. I am using the closed source version Virtualbox also, which is broken here.
So how can I do a self checking? Build dbus with -rdynamic option to get a backtrace?
On Sat, Sep 20, 2008 at 5:50 PM, Pierre Schmitz pierre@archlinux.de wrote:
Am Samstag 20 September 2008 11:25:50 schrieb Lee MaRS:
The qt package has been rebuilt to 4.4.2-2 . But it seems nothing changed... Qterm and VirtualBox are still broken.
This was just a security update. Can anybody else confirm this problem? Virtualbox is running fine here (the closed source version). Qterm seems not to be in our repos.
--
Pierre Schmitz
Clemens-August-Straße 76 53115 Bonn
Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
I'm so sorry to disturb your guys. It is the problem of ibus, an input method engine. I'll file a bug report to its developer.
On Sat, Sep 20, 2008 at 6:46 PM, Lee MaRS leemars@gmail.com wrote:
Hmm, I found that most of the qt4 program broken on my system. I am using the testing repository. I am using the closed source version Virtualbox also, which is broken here.
So how can I do a self checking? Build dbus with -rdynamic option to get a backtrace?
On Sat, Sep 20, 2008 at 5:50 PM, Pierre Schmitz pierre@archlinux.de wrote:
Am Samstag 20 September 2008 11:25:50 schrieb Lee MaRS:
The qt package has been rebuilt to 4.4.2-2 . But it seems nothing changed... Qterm and VirtualBox are still broken.
This was just a security update. Can anybody else confirm this problem? Virtualbox is running fine here (the closed source version). Qterm seems not to be in our repos.
--
Pierre Schmitz
Clemens-August-Straße 76 53115 Bonn
Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
Depends on if the application itself or QT drops the dbus connection. A backtrace would be interesting where the errors occur. Kind regards, Georg On Fri, Sep 19, 2008 at 6:43 PM, Lee MaRS leemars@gmail.com wrote:
Hi, all
After upgrading to qt 4.4.2-1, I found that some qt4 program became broken, such as VirtualBox, and Qterm. All of these programs get a error like this:
process 4272: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details. Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection. D-Bus not built with -rdynamic so unable to print a backtrace Aborted
Is it really a bug of application, or just a bug of qt, or just a bug for this package?
arch-general@lists.archlinux.org