[Bug 48081] New: kate crashes on startup

[email protected] 20 Sep 2002 13:01:26 -0000
Newsgroups gmane.comp.kde.devel.kate
Message-ID <[email protected]>
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
   
http://bugs.kde.org/show_bug.cgi?id=48081   
           Summary: kate crashes on startup
           Product: kate
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: [email protected]
        ReportedBy: [email protected]


Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 2.95.3 (whole of KDE compiled using "ccache" -- everything else works fine)
OS:          Linux

I can't start kate without it crashing during startup. I've been running CVS since nearly a year now,
with weekly updates. My user "kdehead" has a complete CVS environment of its own. Last update was 
last night. 

kate has a problem on my box since ~ two months. The crashes occured initially only when launching 
kate from the kicker button, but it started fine from a konsole or xterm window.

Now it also crashes when starting from konsole. Here is what happens:

     kdehead@kde-bitshop:~> kate&
     [1] 30381
     kdehead@kde-bitshop:~> kio (KTrader): KServiceTypeProfile::offers( KTextEditor/Plugin, )
     kio (KTrader): No profile, using KServiceType::offers, result: 3 offers
     kio (KTrader): KServiceTypeProfile::offers( Kate/Plugin, )
     kio (KTrader): No profile, using KServiceType::offers, result: 8 offers
     kio (KDirLister): +KDirLister
     kio (KDirListerCache): +KDirListerCache
     kio (KDirWatch): Can't use FAM (fam daemon not running?)
     kio (KDirWatch): Available methods: Stat
     kio (KDirLister): [bool KDirLister::openURL(const KURL &, bool = false, bool = false)] file:/home/kdehead/ keep=false reload=false
     kio (KDirListerCache): [void KDirListerCache::listDir(KDirLister *, const KURL &, bool, bool)] 0x82aacd8 url=file:/home/kdehead keep=false reload=false
     kio (KDirListerCache): [void KDirListerCache::stop(KDirLister *)] lister: 0x82aacd8
     kio (KDirListerCache): [void KDirListerCache::forgetDirs(KDirLister *)] 0x82aacd8
     kio (KDirListerCache): listDir: Entry not in cache or reloaded: file:/home/kdehead
     kio (KDirWatch): Added Dir /home/kdehead [KDirWatch-1]
     kio (KDirWatch): Global Poll Freq is now 500 msec
     kio (KDirWatch):  Started Polling Timer, freq 500
     kio (KDirWatch):  Setup Stat (freq 500) for /home/kdehead
     kdecore (KAction): WARNING: KAction::plug(): has no KAccel object; this = 0x82d7878 name = add_bookmark parentCollection = (nil)
     ERROR: KUniqueApplication: DCOP communication error!

Then the kate crash handler dialog appears. The backtrace is this:

  [New Thread 1024 (LWP 30382)]
  0x41025079 in wait4 () from /lib/libc.so.6
  #0  0x41025079 in wait4 () from /lib/libc.so.6
  #1  0x4109fb98 in __DTOR_END__ () from /lib/libc.so.6
  #2  0x40ea6072 in waitpid () from /lib/libpthread.so.0
  #3  0x406c506b in KCrash::defaultCrashHandler ()
     from /opt/kdehead/lib/libkdecore.so.4
  #4  0x40ea3a74 in pthread_sighandler () from /lib/libpthread.so.0
  #5  <signal handler called>
  #6  0x409b3eea in QObject::setProperty () from /opt/qt3/lib/libqt-mt.so.3
  #7  0x414b8b9d in PluginKateInsertCommand::addView ()
     from /opt/kdehead/lib/kde3/kateinsertcommandplugin.so
  #8  0x40068545 in KatePluginManager::enablePluginGUI ()
     from /opt/kdehead/lib/libkateinterfaces.so
  #9  0x400683e4 in KatePluginManager::enableAllPluginsGUI ()
     from /opt/kdehead/lib/libkateinterfaces.so
  #10 0x4006153c in KateMainWindow::KateMainWindow ()
     from /opt/kdehead/lib/libkateinterfaces.so
  #11 0x400537fe in KateApp::newMainWindow ()
     from /opt/kdehead/lib/libkateinterfaces.so
  #12 0x40052602 in KateApp::KateApp ()
     from /opt/kdehead/lib/libkateinterfaces.so
  #13 0x40071dcb in main () from /opt/kdehead/lib/libkateinterfaces.so
  #14 0x40f9a9ed in __libc_start_main () from /lib/libc.so.6

Please tell me if you can derive s.th. from this. What other tests can I run to track it down?
This is probably just s.th. wrong on my particular system. (I've upgraded the qt-copy 2 days ago), 
as this seems not to have occurred to anybody else.
 
Cheers,
Kurt