When I use the visual mode in vim (using 'v') in the Konsole it causes a crash of Klipper so that it will disappear and opens the KDE-Crashmanager. Furthermor Kicker crashes too, but respawns. In Konsole I get the following output from the crashed vim: XIO: fatal IO error 14 (Bad address) on X server ":0.0" after 41 requests (40 known processed) with 0 events remaining. The output of the Crashmanager: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 5064)] 0x0ec53d5c in waitpid () from /lib/libpthread.so.0 #0 0x0ec53d5c in waitpid () from /lib/libpthread.so.0 #1 0x0f7acc04 in KCrash::defaultCrashHandler(int) () from /usr/kde/3.1/lib/libkdecore.so.4 #2 0x0ec52788 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x0f07b0dc in qt_xclb_read_incremental_property(_XDisplay*, unsigned long, unsigned long, int, bool) () from /usr/qt/3/lib/libqt-mt.so.3 #5 0x0f07b150 in qt_xclb_read_incremental_property(_XDisplay*, unsigned long, unsigned long, int, bool) () from /usr/qt/3/lib/libqt-mt.so.3 #6 0x0f07c6d4 in QClipboardWatcher::encodedData(char const*) const () from /usr/qt/3/lib/libqt-mt.so.3 #7 0x0f0dbe6c in QTextDrag::decode(QMimeSource const*, QString&, QCString&) () from /usr/qt/3/lib/libqt-mt.so.3 #8 0x0f0d59c4 in QClipboard::text(QCString&, QClipboard::Mode) const () from /usr/qt/3/lib/libqt-mt.so.3 #9 0x0f0d5ab8 in QClipboard::text(QClipboard::Mode) const () from /usr/qt/3/lib/libqt-mt.so.3 #10 0x0f0d5b1c in QClipboard::text() const () from /usr/qt/3/lib/libqt-mt.so.3 #11 0x0e58a5b4 in KlipperWidget::clipboardSignalArrived(bool) () from /usr/kde/3.1/lib/klipper.so #12 0x0e58b404 in KlipperWidget::qt_invoke(int, QUObject*) () from /usr/kde/3.1/lib/klipper.so #13 0x0e5c6294 in KlipperAppletWidget::qt_invoke(int, QUObject*) () from /usr/kde/3.1/lib/kde3/klipper_panelapplet.so #14 0x0f131958 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/qt/3/lib/libqt-mt.so.3 #15 0x0f131754 in QObject::activate_signal(int) () from /usr/qt/3/lib/libqt-mt.so.3 #16 0x0f40b01c in QClipboard::selectionChanged() () from /usr/qt/3/lib/libqt-mt.so.3 #17 0x0f07b2f4 in QClipboard::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #18 0x0f0ce224 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #19 0x0f0cd9b8 in QApplication::notify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #20 0x0f71e8bc in KApplication::notify(QObject*, QEvent*) () from /usr/kde/3.1/lib/libkdecore.so.4 #21 0x0f0719d8 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #22 0x0f087230 in QEventLoop::processEvents(unsigned) () from /usr/qt/3/lib/libqt-mt.so.3 #23 0x0f0e31e8 in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3 #24 0x0f0e2fe8 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #25 0x0f0ce4c0 in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #26 0x0ffdc3bc in main () from /usr/kde/3.1/lib/appletproxy.so #27 0x0e8abc04 in __libc_start_main () from /lib/libc.so.6 I'm using KDE-3.1.1 (but had the problem in KDE-3.1 too) with qt 3.1.0-r3. I will upgrade to the newer qt and look, if this error happens there too.
I'm not a vim guy... I tested the default vim install briefly and it worked ok (with qt 3.1.2). Do you do something beyond just switching to visual mode to cause the crash? Maybe you have some rlevant nondefault vim configuration? Something that causes it to interact with the clipboard (assuming the kliiper crash isn't merely caused by the kicker one)? Maybe some konsoel configuration (like a special TERM setting or keymap)? Finally, what are your cflags?
Okay, more information ;-) : I run a screen in Konsole, but that doesn't matter. It will also crash without screen. Any special term-settings I can't see. Also I started vim with -T xterm -u /dev/null so that my .vimrc won't be loaded. Same error. Least, my emerge info: Portage 2.0.47-r10 (default-ppc-1.4, gcc-3.2.2, glibc-2.3.2-r0,2.3.1-r2) ================================================================= System uname: 2.4.20-ben8 ppc GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/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/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="oss dvd xv jpeg nls gif kde png truetype ppc directfb gdbm berkdb readline arts tetex aalib tcltk guile mysql X sdl tcpd pam libwww ssl perl python imlib oggvorbis gtk qt motif mozilla cdr apm avi crypt cups dga esd fbcon gnome gnome-libs -gpm gtk2 ipv6 maildir -mitshm mpeg ncurses opengl pdflib qtmt quicktime samba -slang slp spell xml xmms" COMPILER="gcc3" CHOST="powerpc-unknown-linux-gnu" CFLAGS="-O3 -pipe" CXXFLAGS="-O3 -pipe -fsigned-char" ACCEPT_KEYWORDS="ppc ~ppc" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" FEATURES="ccache userpriv" Maybe I should change to -O2 on ppc again. This seems to cause some errors.
OK, try that. I don't know anything about ppc actually. ppc@gentoo.org people: do you think this might be something ppc-specific? Can the kde users among you reproduce it? BTW, I looked up that fsigned-char parameter you use and info gcc says it's only relevant to c, not c++. However you have it in CXXFLAGS but not in CFLAGS. How come? (Probably unrelated to this issue, but I don't like things I don't uderstand...)
I can't understand it, too ;-) As you can read, I have only the -O3 -pipe in CFLAGS. CXXFLAGS isn't set in /etc/make.conf, so it should point to the default CXXFLAGS="${CFLAGS}", as set in /etc/make.globals. I can't find any fsigned-char parameter in all the config-files.
Okay, tried it with the new qt-3.1.1-r2 (compiled -O2) -- same error. Also the same error when I use xterm instead of Konsole.
Found the issue with the fsigned-char. It's caused by /usr/portage/profiles/default-ppc-1.4/make.defaults where are those lines: # C Compiler flags CFLAGS="-O3 -pipe -fsigned-char" # C++ Compiler flags CXXFLAGS=${CFLAGS} So it will take those settings, because I commented out CXXFLAGS in my /etc/make.conf. emerge info shows me still CXXFLAGS="-O3 -pipe -fsigned-char", although I have CFLAGS="-O2 -pipe". When I set CXXFLAGS=${CFLAGS} in my /etc/make.conf everything is right. Nevertheless, I don't think, this will harm this bug ;-)
I reemerged kdelibs and kdebase with -O2 -pipe. The error is still there...
Important update: I had this fatal IO error now also on gterm while I paste something into vim in INSERT-mode. Now the situations seems be different and I guess, it's an XFree-error. I'll compile XFree and its libraries new this night.
problem still present with the new XFree version?
emerging the -r3 ended just some minutes ago ;-) I'll try to reproduce this error . As I wrote in my last comment, this problem is not only KDE-related!
Some more comments to this bug. I have now the xfree-4.3.0-r2 installed (the -r3 in the last comment was a typo). The problem is still there :-( But I found out, when it occurs: Only if you have something in your mouse-buffer _and_ also something in the vim-buffer (yanking from visual mode). I ran a strace vim. Here are the last lines of its output: writev(4, [{"\22\0\377\354\1i2\26\0\0\0\355\0\0\0\353\10\0\0\7\0\3\377"..., 24}, {ptrace: umoven: Input/output error 0xfff5214, 262040}], 2) = -1 EFAULT (Bad address) write(2, "XIO: fatal IO error 14 (Bad add"..., 58XIO: fatal IO error 14 (Bad address) on X server ":0.0" ) = 58 write(2, " after 40 requests (39 know"..., 71 after 40 requests (39 known processed) with 0 events remaining. ) = 71 exit(1) = ? Should the bug still be assigned to the kde-team, as it is not a kde-only-problem?
I had the same problem here (pentium4). Re-emerged vim and the problem went away.
Now as I have vim62a emerged, the problem seems to be gone... Suggested SOLUTION: Re-emerge vim Closing this bug now. Thanks for all your help.
