howto: Create a new file in lyx. Make a table containing one line and two columns. Now set the width of the second column to a value - lets say 3 centimeters. Then type a text in that column, press enter and type a text again. Now mark the whole line -> crash. Can somebody reproduce this? Portage 2.0.54-r2 (default-linux/amd64/2005.1, gcc-3.4.5-vanilla, glibc-2.4-r3, 2.6.16-gentoo-r7 x86_64) ================================================================= System uname: 2.6.16-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 dev-python/pycrypto: 2.0.1-r4 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 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-r2 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="-march=athlon64 -O3 -ffast-math -funroll-all-loops -fpeel-loops -ftracer -funswitch-loops -funit-at-a-time -pipe -fomit-frame-pointer -fno-stack-protector" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /usr/X11R6/bin/startx /etc/env.d" CXXFLAGS="-march=athlon64 -O3 -ffast-math -funroll-all-loops -fpeel-loops -ftracer -funswitch-loops -funit-at-a-time -pipe -fomit-frame-pointer -fno-stack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig candy distlocks sandbox severe sfperms strict" GENTOO_MIRRORS="http://pandemonium.tiscali.de/pub/gentoo/ ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp://ftp.gentoo.mesh-solutions.com/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/" LANG="de_DE.utf8" LC_ALL="de_DE.utf8" LINGUAS="de" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="7zip X a52 aac acpi alsa amd64 artworkextra asf audiofile avi berkdb bidi bitmap-fonts bzip2 bzlib cairo cdda cdio cdparanoia cdr cli crypt css cups curl dbus dga directfb dlloader dmalloc dnd dpms dri dts dvb dvd dvdr dvdread dvi eds effects emacs emboss encode esd exif expat fam fame fat fbcon ffmpeg firefox foomaticdb freetype gcj gdbm ggi gif gimpprint glut gmp gnome gnutls gpm gs gstreamer gtk gtk2 gtkhtml hal hardened howl hpn httpd idn imagemagick imlib ipv6 isdnlog ithreads javascript jpeg jpeg2k kde lcms libsamplerate libwww linuxthreads-tls live lzo lzw lzw-tiff mad matroska mbox memlimit milter mjpeg mmap mng mozcalendar mozdevelop mozsvg mp3 mpeg mpi nautilus ncurses nls nptl nptlonly nsplugin ntfs nvidia offensive ogg oggvorbis on-the-fly-crypt openal openexr opengl pam pcre pdflib perl png ppds pppd python qt quicktime readline reflection reiserfs rle sasl screen sdl session slang sndfile spell spl ssl stream svg symlink tcltk tcpd test tetex tga theora threads tidy tiff toolbar truetype truetype-fonts type1-fonts udev unicode usb userlocales v4l vcd video_cards_nvidia videos vlm vorbis wmf wxwindows xine xml xml2 xmms xorg xosd xpm xprint xtermtoolbar xv xvid xvmc yv12 zlib linguas_de userland_GNU kernel_linux elibc_glibc" Unset: CTARGET, INSTALL_MASK, LDFLAGS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS, PORTAGE_RSYNC_OPTS, PORTDIR_OVERLAY
Created attachment 87754 [details] output of gdb lyx ... run, up, down, bt
build FLAGS was CFLAGS ="-march=athlon64 -O1 -pipe -g -ggdb -fomit-frame-pointer -fno-inline -fno-pie -fno-stack-protector" LDFLAGS ="-Wl,-O1" FEATURES ="candy severe sfperms test nostrip splitdebug" CXXFLAGS ="${CFLAGS}"
I'm able to reproduce this (also on amd64, but with less "exotic" flags) I'll try to look into it later, but i'm short on time currently so if you need a quick fix then feel free to debug this yourself and report back :) Please also report this bug upstream and attach the URL to this bug.
Created attachment 87915 [details] strace output What I did: I opened the file "/home/atti/Desktop/bug.lyx" containing table (see howto in this bugs description) and marked the row.
Created attachment 88130 [details] lyx file containing such a table I don't think that I'm able to debug (and least of all to fix) it. :-| I haven't got any webspace yet, so I can't give an URL. Can't we just refer to this bug report - if it fits - in another document?
marked upstream
Please don't close this bug until it is fixed. What I meant by my previous comment was that I confirm that the bug is actual there, but I currently have no time to debug and fix it. Hence, the suggestion about trying to debug it yourself, but if you don't know how to do that then you will have to wait until I do it or some lyx developer do it. What I meant by "Please also report this bug upstream and attach the URL to this bug." was that I would suggest that you go to http://bugzilla.lyx.org, search for this bug there. If you can't find a similar bug report then open a new bug report there. I either case I wanted you to paste the URL of that bug report into this bug report in the URL field above (just over the Summary field). Btw. please never contact me by email about a bug, since all communication about bugs should go into bugzilla (for future reference, and because mails just gets lost in my mailbox :-)
aye aye, Sir ;-)
Have you tried the patch from the upstream bug report? If you have, did it work? If you haven't, can you please try it out? (If you don't know how to do it, I can guide you through it)
Hi Martin, your help is very much appreciated! :) Up to now I downloaded (SVN) the devel source but - because of getting low in space in my home directory - make wasn't successful. Can you please contact me on my email address so I can contact you in case of problems?
there is a fix for this bug on this site: http://www.lyx.org/trac/changeset/14678 I hope it will be 'applied' soon to the portage tree. :)
fixed in 1.4.3. since 1.4.4 is stable now we can close it.
(In reply to comment #12) > fixed in 1.4.3. since 1.4.4 is stable now we can close it. > good
