I filled a bug upstream: https://sourceforge.net/tracker/index.php?func=detail&atid=558150&group_id=79945&aid=1471830 Everytime I enter a view like ViewPDF, ViewDVI,... and then exit it, KDE prompt me after a few seconds whether I want to terminate the "non responding application". I guess that KDE (my version is 3.5.2) detects I want to close the application since I use top-right close button or ALT+F4 to close the view. Quitting the view using "File > Quit" does not have this problem. This bug exists with kile-1.8.1 and kile-1.9 emerge --info Portage 2.1_pre7-r5 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.14-gentoo-r5 x86_64) ================================================================= System uname: 2.6.14-gentoo-r5 x86_64 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.6.14 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-Os -march=k8 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/env.d" CXXFLAGS="-Os -march=k8 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://mirror.ovh.net/gentoo-distfiles/ ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo " LDFLAGS="-Wl,-O1" LINGUAS="fr" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X alsa apache2 arts avi bash-completion berkdb bitmap-fonts browserplugin cairo cdr cli crypt ctype cups curl dba directfb divx4linux dri eds emboss encode enscript esd expat fastbuild foomaticdb force-cgi-redirect ftp gd gif glitz gpm gstreamer gtk gtk2 hal howl imlib isdnlog java javascript jpeg kde kdeenablefinal lzw lzw-tiff matroska memlimit motif mozilla mp3 mpeg msn mysql ncurses nls nptl nptlonly nsplugin nvidia offensive ogg opengl pam pcre pdflib php pic png posix pppd python qt quicktime readline sdl session simplexml soap sockets spell spl ssl tcpd tetex tidy tiff tokenizer truetype truetype-fonts type1-fonts unicode usb utf8 vhosts vim-with-x vorbis xml xml2 xmms xpm xsl xv xvid zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_fr userland_GNU video_cards_nv video_cards_nvidia video_cards_vesa" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, PORTDIR_OVERLAY
Do you have the same problem, after upgrading to kdelibs-3.5.2-r4?
(In reply to comment #1) > Do you have the same problem, after upgrading to kdelibs-3.5.2-r4? Yes, I have kde-base/kdelibs-3.5.2-r4 and the problem is still there :( I am using the same version of kile on my laptop with the same version of KDE and Xorg (almost a clone) except that my laptop is an x86 and not an amd64, I don't have this problem on it but I doubt it is related to the arch!
> I doubt it is related to the arch! I have the same problem, but also only on Amd64, not on the x86 installation of Gentoo (both are on the same PC), so probably it does have something to do with the arch.
I think the issue has to be reported upstream as it doesn't sound like a Gentoo only problem. FWIW, the problem is present even with KDE 3.5.4.
And neither is it a Kile problem. The same thing happens, for instance, if you try to close kcontrol and wait a few seconds before clicking Apply.
Similar bug upstream: http://bugs.kde.org/show_bug.cgi?id=113145
I know I could reproduce this, but can't with kdelibs-3.4.5-r1 and kile-1.9.2. What about you?
For me, the bug has gone. Maybe (but I'm not sure) it's because I upgraded from KDE 3.5.2 to KDE 3.5.5.
(In reply to comment #8) > For me, the bug has gone. Maybe (but I'm not sure) it's because I upgraded from > KDE 3.5.2 to KDE 3.5.5. I had the problem with KDE 3.5.2 -> 3.5.4, but I confirm I can't reproduce it anymore with KDE 3.5.5, maybe related to the upgrade, don't know... Not sure I can change the resolution to "FIXED" as the problem maybe still exists if not using last and bleeding edge version of KDE ! (KDE 3.5.2 still in the tree)
Closing as fixed, see comment 9.
