Kicker dcop error

Kicker dcop error

Post by Anto » Sun, 09 Jun 2002 20:47:02



I just installed Kde 3.0.1 with the Slackware .tgz's (using slackware 8.0).
When i start Kde the startup procedure goes by without any problems until
the panel (kicker) crashes at startup. The kicker error message is:

/usr/lib/qt-3.0.4//plugins/imageformats/libqjpeg.so: Feature JPEG already
defined in /usr/lib/qt-3.0.4/plugins/imageformats/libqjpeg.so!
/usr/lib/qt-3.0.4//plugins/imageformats/libqmng.so: Feature MNG already
defined in /usr/lib/qt-3.0.4/plugins/imageformats/libqmng.so!
libpng error: Not a PNG file
libpng error: Not a PNG file
kdecore (KLibLoader): library libkminipagerapplet.la not found under
'module' but under 'lib'
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = kicker path = <unknown> pid = 674
ERROR: KUniqueApplication: DCOP communication error!

When looking for a soulution for this problem on the www i've found that
it's fairly common, and the solutions mostly given are adding        
export KDEDIR='/opt/kde3/'
export QTDIR='/usr/lib/qt3'
to the .bashrc or to the startkde script, i've tried both of these, but they
haven't worked.
I hope you can help, because I love kde.

 
 
 

Kicker dcop error

Post by Lee J. Moor » Sun, 09 Jun 2002 21:19:04


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Anton!

On Sat, 08 Jun 2002 at 11:47 GMT,

you addressed comp.windows.x.kde as follows:

Quote:> I just installed Kde 3.0.1 with the Slackware .tgz's (using slackware 8.0).
> When i start Kde the startup procedure goes by without any problems until
> the panel (kicker) crashes at startup. The kicker error message is:

Did you turn font anti-aliasing on?  If you can launch kcontrol
from X, try turning them off.  There are of course many problems
for kicker not working.  This is one I bumped into a few weeks
ago with KDE 3.0 on one of the binary distributions.  :-)

No such problems in Gentoo though.  Even with anti-aliasing.
- --
Lee J. Moore
Gentoo Linux/Portage 1.9.13

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iEYEARECAAYFAj0B9i8ACgkQ6k8to8I6M0xX0ACgonYgYtF3aTMJm6FTvlL+IyTK
//AAoI/4IwFK5jHM9fBbgNMkBJ1mFd8F
=m2Ob
-----END PGP SIGNATURE-----

 
 
 

Kicker dcop error

Post by Anto » Sun, 09 Jun 2002 21:57:47



> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Hey Anton!

> On Sat, 08 Jun 2002 at 11:47 GMT,

> you addressed comp.windows.x.kde as follows:

>> I just installed Kde 3.0.1 with the Slackware .tgz's (using slackware
>> 8.0). When i start Kde the startup procedure goes by without any problems
>> until the panel (kicker) crashes at startup. The kicker error message is:

> Did you turn font anti-aliasing on?  If you can launch kcontrol
> from X, try turning them off.  There are of course many problems
> for kicker not working.  This is one I bumped into a few weeks
> ago with KDE 3.0 on one of the binary distributions.  :-)

> No such problems in Gentoo though.  Even with anti-aliasing.
> - --
> Lee J. Moore
> Gentoo Linux/Portage 1.9.13

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)

> iEYEARECAAYFAj0B9i8ACgkQ6k8to8I6M0xX0ACgonYgYtF3aTMJm6FTvlL+IyTK
> //AAoI/4IwFK5jHM9fBbgNMkBJ1mFd8F
> =m2Ob
> -----END PGP SIGNATURE-----

I have tried with both user and superuser accounts and antialiasing on and
off. I have no idea what's causing this.
 
 
 

Kicker dcop error

Post by Lee J. Moor » Sun, 09 Jun 2002 22:00:27


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Anton!

On Sat, 08 Jun 2002 at 12:57 GMT,

you addressed comp.windows.x.kde as follows:

[..]

Quote:>> No such problems in Gentoo though.  Even with anti-aliasing.
[..]
> I have tried with both user and superuser accounts and antialiasing on and
> off. I have no idea what's causing this.

Have you deleted the .DCOP* files in the user directories too?

- --
Lee J. Moore
Gentoo Linux/Portage 1.9.13

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iEYEARECAAYFAj0B/+IACgkQ6k8to8I6M0yiKQCgzsgnQOdyBl8VDjHMueTFv4P1
FqsAoN4y+gv0GqUT5/ThJ+Jqa5RVibrO
=FglJ
-----END PGP SIGNATURE-----

 
 
 

Kicker dcop error

Post by Anto » Sun, 09 Jun 2002 22:12:11



> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Hey Anton!

> On Sat, 08 Jun 2002 at 12:57 GMT,

> you addressed comp.windows.x.kde as follows:

> [..]
>>> No such problems in Gentoo though.  Even with anti-aliasing.
> [..]
>> I have tried with both user and superuser accounts and antialiasing on
>> and off. I have no idea what's causing this.

> Have you deleted the .DCOP* files in the user directories too?

> - --
> Lee J. Moore
> Gentoo Linux/Portage 1.9.13

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)

> iEYEARECAAYFAj0B/+IACgkQ6k8to8I6M0yiKQCgzsgnQOdyBl8VDjHMueTFv4P1
> FqsAoN4y+gv0GqUT5/ThJ+Jqa5RVibrO
> =FglJ
> -----END PGP SIGNATURE-----

thanks, but it doesn't work. It seems this is a global error, because the
same thing happens with a brand new user.
 
 
 

Kicker dcop error

Post by Robert_ » Sun, 09 Jun 2002 22:18:13



>> I have tried with both user and superuser accounts and antialiasing on
>> and off. I have no idea what's causing this.

> Have you deleted the .DCOP* files in the user directories too?

He may also want to try renaming his kickerrc for a rather painless
troubleshooting step.  $HOME/.kde/share/config/kickerrc  
(or .kde3 or .kde? )

all the best,
Robert_L

--
Debian 3.0
KDE-3.0.1
XFree-4.1

 
 
 

Kicker dcop error

Post by Robert_ » Sun, 09 Jun 2002 22:19:27



> thanks, but it doesn't work. It seems this is a global error, because the
> same thing happens with a brand new user.

Ah, well then my advice about the kickerrc is not going to work then.

all the best,
Robert_L
--
Debian 3.0
KDE-3.0.1
XFree-4.1

 
 
 

1. Lots of errors in .xsession-errors when launching xterm from kicker

I put a button for xterm in kicker (with drag and drop from konqueror).
Every time I start xterm from this button I get lots of entries in
.xsession-errors starting with

Invalid entry (missing ']') at /usr/bin/X11/xterm:1
Invalid entry (missing '=') at /usr/bin/X11/xterm:2
Invalid entry (missing ']') at /usr/bin/X11/xterm:5
...

It seems that kicker is expecting a script instead of a binary, but why?
What's wrong with my system? It's KDE 3.0.5, Suse 8.0

Greetings,
--
Burkhard Schultheis
Tele Data Electronic, Wagnerstr. 10, D-76448 Durmersheim

Phone: +49-7245-9287-21, Fax: +49-7245-9287-30

2. LS120 Help

3. DCOP Error

4. SunOS kvm_getu() loses on sun4m architecture - any workarounds?

5. kde3 rsh start application error (konqueror dcop)

6. GDB and assert(0)

7. DCOP error reinstalling KDE3.01

8. Dead ISA Bus?

9. Problem installing KDE 2.0.1: DCOP communiction error

10. Fix for DCOP error "Could not read network connection list"

11. DCOP communication error starting KDE 2.2

12. dcop compilation error in solaris 2.6 (KDE 2.0)

13. Klauncher DCOP error