[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: Konqueror too enthousiastic
From:       David Faure <faure () kde ! org>
Date:       2000-01-20 19:17:30
[Download RAW message or body]

On Thu, Jan 20, 2000 at 07:10:16PM +0100, Simon Hausmann wrote:
> 
> 
> On Thu, 20 Jan 2000, Waldo Bastian wrote:
> 
> > Hiya,
> > 
> > When I start konqy I get windows all over the place (they replicate 
> > like rabbits so to say..)
:-}

> > Any ideas?
> > 
> > > konqueror
> > charset file invalide or not found. Defaulting to latin 1
> > DCOPClient: setup DCOP protocol. Major opcode = 2
> > libkonq: Invalid bookmark : found mimetype='text/html' for 
> > file='/home1/kde2.0/.
> > kde/share/apps/kfm/bookmarks/http:%2f%2fkt.linuxcare.com%2fkt19991206_45.html'!DCOPClient: 
> > setup DCOP protocol. Major opcode = 2
> > DCOPClient: setup DCOP protocol. Major opcode = 2
> > KCookieJar already running.
> > libkonq: Instance konqueror has no about data
> > DOCTYPE viewmodexml
> > QObject::connect: Cannot connect QAction::activated() to (null)::(null)
> > QObject::connect: Cannot connect QAction::activated() to (null)::(null)
> > QGDict::hashStringKey: Invalid null key
> > QObject::connect: Cannot connect QAction::activated() to (null)::(null)
> > QObject::connect: Cannot connect QAction::activated() to (null)::(null)
> > QObject::connect: Cannot connect QAction::activated() to (null)::(null)
> > libkonq: Instance konq_searcher has no about data
> > DOCTYPE QConfig
> > kparts: [kpartsmainwindow.cpp:274] MainWindow::createGUI for 0L
> > konqueror: [konq_mainview.cc:294] KonqMainView::openURL : _url = 
> > 'file:/home1/kd
> > e2.0'
> > konqueror: Creating new konqrun for file:/home1/kde2.0
> > XFocusIn for 'KonqMainView', mode = 0, detail = 3
> > kparts: No part made active although 
> > konqueror-mainwindow#1/KonqMainView got eve
> > nt
> 
> <here>
> 
> Hrm, there must be something very strange, as *that* is the place where
> something like "FILTERING mime_type_here" should appear as debug output,
> as soon as KRun found the mimetype of the given URL (file:/home1/kde2.0) .
Strange indeed.

> Waldo, could you change your kdebugrc to make kdebug spew out the debug
> info of KRun and send the output once again?

Of course he means : "use kdebugdialog to" make kdebug spew out the debug
info of KRun.
:-)

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]