When I launch gaim by clicking on a button in the bottom panel (in "Application Launcher", I guess), the bottom panel is frozen, does not react to input, and the little rubber band that is animated around a launching icon stays drawn around the gaim button. The gaim window opens and it works just fine, but the KDE bottom panel is frozen; this means the whole panel, including the pager and taskbar and system tray, and the panel-hiding button. All mouse clicks in it are ignored. Alt-tab window switching works normally. If I ctrl-alt-F1 to the console at this point (whence I startxed), nothing has been printed in it. If I now close gaim, a dialog titled "Sorry - KDE Panel" appears, with the message "KDEInit could not launch 'gaim'". Once I close that dialog box, the panel is fine. If I now ctrl-alt-F1 to the console, it is full of repetitions of this: WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) \x09 Major opcode: \x0e I am not noticing such behavior with any other application than gaim, but I'm still reporting this on KDE because it seems to me that the KDE panel should not lock up on misbehavior of an application (I may VERY well be wrong :), and gaim is working fine. Relevant versions: kdebase, kdelibs, etc.: 3.1.1a xfree: 4.3.0-r1 gaim: 0.61 Will attach gaim.desktop. Following is the result of emerge info: Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) ================================================================= System uname: 2.4.20-gentoo-r2 i686 AMD Athlon(tm) XP 2000+ GENTOO_MIRRORS="http://ftp.linux.is/gentoo http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts tetex svga tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla apache2" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe -fforce-addr -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4" CXXFLAGS="-march=athlon-xp -O3 -pipe -fforce-addr -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
Created attachment 10856 [details] The applnk .desktop file whose launch locks up the panel
launching it from a terminal gives the same problem?
Nope. When started from a terminal, all is well.
try to manually create the .desktop file and put it again on the kicker, also this could be a gaim/xfree problem (i.e gaim does something unexpected, X fails handling it, kicker which run on top of X is affected) but i don't know if this makes sense (the -r2 of xfree solve this?)
I manually created the .desktop file in the first place, by copying it from something that was working (I think it was mozilla). I have already emerged xfree-4.3.0-r2, it did not resolve this.
What if you remove these lines from the ebuild? X-KDE-StartupNotify=true X-DCOP-ServiceType=Unique
They are not present in the ebuild, so you probably meant remove them from the .desktop file, and that worked! I clipped these last two lines off the gaim.desktop installed by the gaim-0.62 ebuild, and that did the trick. There is no file in net-im/gaim/files for this, so I guess this calls for a patch against the gaim source tree, or at least a bug report on the Gaim project. Thanks!
if you created this using the mozilla .desktop, is not a gaim problem then, anyway deleting such lines fixed the problem, so closing as fixed
