Version: unspecified (using KDE 4.6.2) OS: Linux Three error messages of the form KXMLGUIClient::~KXMLGUIClient: 0xb76d88 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. Appear on exit if kate is launched from the terminal Reproducible: Always Steps to Reproduce: 1) Launch kate from termial 2) exit kate Actual Results: Error messages appear.
Fixed just a few hours before for KDE 4.6.3. *** This bug has been marked as a duplicate of bug 266538 ***
(In reply to comment #1) > Fixed just a few hours before for KDE 4.6.3. > > *** This bug has been marked as a duplicate of bug 266538 *** This is not a dup. kate is not the same as kwrite they are not even in the same package. The kdesdk package was not touched in 266538. Just make sure I wasn't missing something I actually built and installed krite with the patch from 266538. This does not resolve the issue mentioned here.
This command line excerpt should help. @:~/Documents/kde-source/kdebase-4.6.2/build/kwrite$ sudo make install [ 0%] Built target kdeinit_kwrite_automoc [100%] Built target kdeinit_kwrite [100%] Built target kwrite :~/Documents/kde-source/kdebase-4.6.2/build/kwrite$ sudo make install [ 0%] Built target kdeinit_kwrite_automoc [100%] Built target kdeinit_kwrite [100%] Built target kwrite Install the project... -- Install configuration: "RelWithDebInfo" -- Installing: /usr/bin/kwrite -- Removed runtime path from "/usr/bin/kwrite" -- Installing: /usr/lib/libkdeinit4_kwrite.so -- Installing: /usr/share/applications/kde4/kwrite.desktop -- Installing: /usr/share/kde4/apps/kwrite/kwriteui.rc :~/Documents/kde-source/kdebase-4.6.2/build/kwrite$ kate kate(4940)/kate-filetree KateFileTreePluginView::KateFileTreePluginView: BEGIN: mw: Kate::MainWindow(0x1b6cbd0) ... Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon kate(4940)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x1e82c98 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kate(4940)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x1fa1f70 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kate(4940)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x1edbaf8 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kate(4940)/kate-filetree KateFileTreePluginSettings::save: save config! michael@BC:~/Documents/kde-source/kdebase-4.6.2/build/kwrite$ kwrite QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /home/michael/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon As you can see the patch does resolve the kwrite error but not the messages from kate. If this is a dup the original needs to be reopened as we are still producing errors from the kate evocation.
I fixed it in the KDE/4.6 branch in the git module kde-baseapps. Is that the wrong place? https://projects.kde.org/projects/kde/kdebase/kde-baseapps/repository/show/kwrite?rev=KDE%2F4.6
Not sure what we're missing here. kwrite is fixed. kate is in the kdesdk module in kubuntu and has not been touched. kate can functions without kwrite itself being installed. I can't help but feel there's a commutations gap here. Was there something else changed? kwritemain.cpp is not part of kate's source code or any of its plugins. I initially thought the bugs were the same myself but they aren't. kate compiles without any dependance on kwrite.
The following modules were changed: 1. git: Kate git module = trunk (kate + kwrite) 2. git: kde-baseapps KDE/4.6 = 4.6 branch of kwrite kate plugins: 3a. branches/KDE/4.6/kdesdk/kate/plugins/filetree/katefiletreeplugin.cpp 3b. branches/KDE/4.6/kdesdk/kate/plugins/filetemplates/plugin/filetemplates.cpp What else do you expect? Just try it, there should be no message anymore...
thanks missed those. On Apr 19, 2011 11:59 AM, "Dominik Haumann" <dhdev@gmx.de> wrote: > > https://bugs.kde.org/show_bug.cgi?id=271136 > > > > > > --- Comment #6 from Dominik Haumann <dhdev gmx de> 2011-04-19 17:51:46 --- > The following modules were changed: > 1. git: Kate git module = trunk (kate + kwrite) > 2. git: kde-baseapps KDE/4.6 = 4.6 branch of kwrite > > kate plugins: > 3a. branches/KDE/4.6/kdesdk/kate/plugins/filetree/katefiletreeplugin.cpp > 3b. branches/KDE/4.6/kdesdk/kate/plugins/filetemplates/plugin/filetemplates.cpp > > What else do you expect? Just try it, there should be no message anymore... > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. thanks missed those.
*** Bug 275833 has been marked as a duplicate of this bug. ***
The version fixed is "4.6.3" which I assume corresponds to the KDE version. I still see this bug in Kate on my Fedora14 machine. here are the details: (Pl. ignore, this comment, if corresponds to the "kate" version.) kate(2888)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x17310f8 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kate(2888)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x18f1740 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kate(2888)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x21b92f8 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. # kate --v Qt: 4.7.3 KDE Development Platform: 4.6.5 (4.6.5) Kate: 3.6.5 # rpm -qa | grep kate libkate-0.3.7-2.fc14.x86_64 # rpm -qa | grep kdesdk kdesdk-utils-4.6.5-2.fc14.x86_64 kdesdk-4.6.5-2.fc14.x86_64 kdesdk-libs-4.6.5-2.fc14.x86_64 #
Can you build Kate according to http://kate-editor.org/get-it/ and then test again?