Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc 3.2 OS: Solaris If I try to start Konqueror from the panel or the K-menu, my mouse changes to indicate status, stays that way for 2 seconds, and goes back to normal. And konqueror never starts. If I attempt to start from alt-f2, I get the message "KDEInit: Could not launch "konqueror". I can launch other things from there. I can, however, launch it from the command line. It has been this way for months, despite numerous CVS builds and rebuilding my .kde directory several times.
which branch are you talking about? do you have another KDE installation in parallel? is it reachable via path? start "kdeinit" in an xtern and check the debug output when you click on the konqueror icon.
Subject: Re: kdeinit could not launch konqueror No other installation of KDE here. Here's the debug info: From clicking in kicker: kio (KLauncher): KLauncher: Got start_service_by_desktop_path('/home/ms126519/kde312/share/applications/konqbrowser.desktop', ...) klauncher: WARNING: KRun::processDesktopExec: Multiple or no URLs supplied to single-URL service kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-ms126519/ksycoca kdeinit: Got EXT_EXEC 'kfmclient' from launcher. X Error of failed request: BadAtom (invalid Atom parameter) Major opcode of failed request: 18 (X_ChangeProperty) Atom id in failed request: 0x0 Serial number of failed request: 10 Current serial number in output stream: 11 From mini-commander thingie: "Klauncher could not be started by DCOP" [ms126519@starkitty ms126519]$ klauncher: Exiting on read_socket errno: 0 On Mon, 14 Jul 2003, Dirk Mueller wrote: > Date: 14 Jul 2003 23:10:45 -0000 > From: Dirk Mueller <mueller@kde.org> > Reply-To: 60998@bugs.kde.org > To: misty@cban.com > Subject: [Bug 60998] kdeinit could not launch konqueror > > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=60998 > mueller@kde.org changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |UNCONFIRMED > > > > ------- Additional Comments From mueller@kde.org 2003-07-15 01:10 ------- > which branch are you talking about? > > do you have another KDE installation in parallel? > > is it reachable via path? > > start "kdeinit" in an xtern and check the debug output > when you click on the konqueror icon. > > Misty Stanley-Jones ------------------------- What lies before us and what lies beyond us is tiny com- pared to what lies within us. -- Oliver Wendell Holmes
The problem is that kdeinit dies on X errors such as "BadAtom". These BadAtom errors can happen due to quirks with startup-info. Fixed kdeinit in HEAD and 3.1-branch to ignore these kinds of problems. Reassigning the bugreport to Seli because the BadAtom errors may indicate a problem with startup info. BR55522 is most likely the same problem. It can easily be reproduced by forcing the net_current_desktop Atom in kinit.cpp to 0. What is remarkable is that in that case, in HEAD, the started application will not appear until you press a mouse button. No idea why this only happens with one specific application (konqueror in this case, in BR55522 it seemed to be caused by gnome-terminal)
Should be fixed.