[Kde-bindings] Closing problem after upgrade to kde-redhat kdebindigs-2.5.1 fc4

[Richard Dale]

On Tuesday 07 February 2006 21:55, Han Holl wrote:
> Hello,
>
> _all_ korundum programs have the following problem:
> After closing the main window I get messages about kdcopserver and ksycoca.
> Like this:
>
> #!/usr/bin/ruby -w
> require 'Korundum'
>
> aboutdata = KDE::AboutData.new("kdepaper", "", '', '', 0)
> KDE::CmdLineArgs.init(aboutdata)
> app = KDE::Application.new
> background = Qt::Widget.new()
> app.setMainWidget(background)
> background.show
> Qt.debug_level = Qt::DebugLevel::High
> Qt::Internal::setDebug Qt::QtDebugChannel::QTDB_VIRTUAL
>
> Qt::Internal::setDebug Qt::QtDebugChannel::QTDB_GC
> app.exec
> ### end of program
>
>
>
> classname    == KApplication
>
> :: method == exec
>
> -> methodIds == [17974]
> candidate list:
>         int QApplication::exec()  (17974)
> matching => 17974
> match => 17974 score: 0
> Resolved to id: 17974
> setCurrentMethod(17974)
> kdeinit: Shutting down running client.
> ---------------------------------
> It looks like dcopserver is already running. If you are sure
> that it is not already running,
> remove /home/han/.DCOPserver_optiplex.diemen.home__0
> and start dcopserver again.
> ---------------------------------
>
> KDE Daemon (kded) already running.
> kbuildsycoca running...
> Reusing existing ksycoca
> Deleting (KApplication*)0x92cd468
> unmapPointer (KApplication*)0x92cd468 -> 0x92652e0
> unmapPointer (KApplication*)0x92cd4b0 -> 0x93bd698
> 0x92cd468->~KApplication()
> Checking for delete (QMetaObject*)0x93c1ac8 allocated: true
>
> Checking for delete (QMetaObject*)0x9394bd8 allocated: false
>
> Checking for delete (QMetaObject*)0x93bd868 allocated: true
>
> Checking for delete (QMetaObject*)0x939e3e8 allocated: false
>
> Checking for delete (QWidget*)0x93bb9a0 allocated: true
>
> Checking for delete (QWidget*)(nil) allocated: false
>
> Checking for delete (KApplication*)(nil) allocated: false
>
> Checking for delete (KApplication*)(nil) allocated: false
>
> Checking for delete (KAboutData*)0x91e4598 allocated: true
>
> Checking for delete (KAboutData*)(nil) allocated: false
>
>
> Any suggestions? Is anyone else seeing this ?
I've just tried it (on Kubuntu with KDE 3.5.1) and don't get any messages at 
all - it looks like a problem with your kde installation to me.

-- Richard