-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 05 April 2002 7:00 am, Borsenkow Andrej wrote: > > kicker freeze when launching konsole, and wait for konsole process > > termination. Moreover, it returns an error message: kdeinit can not > > launch > > > konsole-noxft. > easiest work around for the short run is to add "special button" called "Terminal Sessions" by right clicking on kicker. This works without issue and is the same as dragging konsole onto kicker in effect. > Oh, my ... > > If you search archives you find that I wrote about it several times and > finally I also posted the reason, and some crude hand-crafting solution. > > What happens is > > - you install both KDE2 and KDE3 > - both install menu files. _Different_ menu files, e.g. kdebase-konsole > and kdebase3-konsole > - the _output_ files (i.e. the actual file that is generated during > update-menus run) is the same in both cases, something like > Terminals/console.desktop > - so what happens is - update-menus generates _two_ entries in the same > file. Look into console.desktop - you will see two, not one entry there. > - Now, depending on the order of these entries, either KDE2 or KDE3 > kicker will hang. > > I do not see any way to resolve it. The very crude solution was > something like > > - make all KDE3 menu files require kde3 not plain kde > - modify KDE2 menu methods to ignore kde3 > - modify KDE3 menu methods to ignore plain kde > > but that is not general solution actually and you have a problem then > with KDE3 menus under Gnome that is not prepared. > > Remove either KDE2 or KDE3 and rerun update-menus. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE8rfIvQ3BM1ElJCVIRAq+5AJ4oPkq0Oaf0Wjxo2cjKT8Wqq+NB5wCfQrG6 MJfBacFJD8+gj2GFWz4+y7s= =7QAa -----END PGP SIGNATURE-----
