#4835 closed defect (fixed)
lyx: SIGSEGV signal caught - can't launch LyX anymore
Reported by: | Owned by: | lasgouttes | |
---|---|---|---|
Priority: | high | Milestone: | 1.5.5 |
Component: | general | Version: | 1.5.4 |
Severity: | critical | Keywords: | |
Cc: | j.spitzmueller@…, mfg@…, vonkad@…, lyx@…, edwin@…, martin.orlob@…, raoulsch@…, minetroux@…, fede_m@…, echerlin@…, epatton@…, jarecke@…, lenz@…, faure@…, scorpiondb@…, sridharsahu@… |
Description
Hello,
I ran into this problem for the first time today (2008 May 7). I've been using
my lyx version for long, but always worked OK. I could not find any bug on that
already reported.
I call the severity of this problem critical, although it's catastrophic for me:
I just can't launch LyX.
Following, the relative information. If you need more, don't hesitate to ask.
My LyX problem:
pietro@t42-ibm:phd_thesis$ lyx
QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions
in Help->Introduction and send us a bug report, if necessary. Thanks !
Bye.
Aborted
My Linux distribution and version:
pietro@t42-ibm:phd_thesis$ uname -a
Linux t42-ibm 2.6.24 #1 PREEMPT Thu Apr 3 11:24:32 CEST 2008 i686 GNU/Linux
My LyX version:
pietro@t42-ibm:phd_thesis$ lyx -version
LyX 1.5.4 (Mon, Feb 25, 2008)
Built on Mar 13 2008, 16:15:40
Configuration
Host type: i486-pc-linux-gnu
Special build flags: aiksaurus pch warnings use-aspell use-ispell
C Compiler: gcc
C Compiler LyX flags:
C Compiler flags: -Wextra -Wall -g -O2
C++ Compiler: g++ (4.2.3)
C++ Compiler LyX flags:
C++ Compiler flags: -Wextra -Wall -g -O2
Linker flags:
Linker user flags: -Wl,-z,defs -Wl,--as-needed
Qt 4 Frontend:
Qt 4 version: 4.3.4
Packaging: posix
LyX binary dir: /usr/bin
LyX files dir: /usr/share/lyx
Thanks in advance for your effort,
Pietro Binetti
Change History (58)
comment:1 by , 16 years ago
Cc: | added |
---|
comment:2 by , 16 years ago
Subject: Re: lyx: SIGSEGV signal caught - can't launch LyX
anymore
On 07-May-2008, bugzilla-daemon@… wrote:
j.spitzmueller@… changed:
What |Removed |Added
CC| |j.spitzmueller@…
Is it possible that you updated qt or glibc or something, and that your LyX
version is compiled against some old libraries?
Hi,
Well, I update my debian-lenny almost every day. However, I
tried to remove the lyx package and reinstall it again, but I get the
same error.
Or I should do something different?
Pietro
You reported the bug, or are watching the reporter.
comment:3 by , 16 years ago
which version of qt do you have installed?
Can you build the sources yourself?
comment:4 by , 16 years ago
Subject: Re: lyx: SIGSEGV signal caught - can't launch LyX
anymore
On 07-May-2008, bugzilla-daemon@… wrote:
which version of qt do you have installed?
Can you build the sources yourself?
I have qt4 installed. In my repositories of the debian package manager I
don't see the qt4 source, at a first glance. But I can always find that
source code and recompile it myself, if necessary.
Is that the way to go? It's still not clear to me, why lyx doesn't work
if I remove the package from my system and install it again from
scratch...
Pietro
You reported the bug, or are watching the reporter.
comment:5 by , 16 years ago
I suspect that the lyx binary you use does not match the libraries on your
system. If so, this is an issue of your distribution.
If you can build lyx from scratch, such problems would be excluded.
However, my question about qt was if you use qt 4.4 (not qt4 in general). There
are known problems with LyX and qt 4.4 that have been resolved for forthcoming
LyX 1.5.5.
comment:6 by , 16 years ago
Cc: | added |
---|
comment:8 by , 16 years ago
I also filed a bug in kubuntu and it seems that incompatibility with new
version of qt4 is the problem
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/228067
there is a possible solution proposed there removing new version of qt4.
comment:9 by , 16 years ago
I had the same problem when qt4 got updated to 4.4 yesterday. Solved it by
moving Trolltech.conf, just as for #4835
(#4819)
More details:
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/228067
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/197950
comment:10 by , 16 years ago
Subject: Re: lyx: SIGSEGV signal caught - can't launch LyX
anymore
On 09-May-2008, bugzilla-daemon@… wrote:
I had the same problem when qt4 got updated to 4.4 yesterday. Solved it by
moving Trolltech.conf, just as for #4835
(#4819)
Hi,
Unfortunately, this doesn't halp in my case. After removing ~/.config/Trolltech.conf
and creating in again with qtconfig-qt4, lyx crashing exactly the same
way.
Pietro
More details:
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/228067
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/197950
You reported the bug, or are watching the reporter.
comment:11 by , 16 years ago
Subject: Re: lyx: SIGSEGV signal caught - can't launch LyX
anymore
On 08-May-2008, bugzilla-daemon@… wrote:
I also filed a bug in kubuntu and it seems that incompatibility with new
version of qt4 is the problem
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/228067
there is a possible solution proposed there removing new version of qt4.
Hi,
Yes, it seems that's the bug I ran into. I checked, and qt4.4 is indeed
the version I have installed on my distribution (Debian Testing - Linux 2.6.24).
In the link you provide I see that the problem should be solved by
moving back to qt4.3. However, this is something I've never done: how
can I install a package (libqt4-core and libqt4-gui) at a version (4.3) older
than the one released in my distribution repositories (4.4)?
Pietro
You reported the bug, or are watching the reporter.
comment:12 by , 16 years ago
Milestone: | → 1.5.5 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
OK, the instability with qt 4.4 is a known bug that will be resolved in 1.5.5.
comment:13 by , 16 years ago
Cc: | added |
---|
comment:15 by , 16 years ago
Cc: | added |
---|
comment:17 by , 16 years ago
It is mentioned that version 1.5.5 will solve but ...
WE NEED TO WORK IN THE MEANWHILE!
please do not mark as resolved.- reopen bug please!!
Is there a way to batch process files from lyx to latex?
in command line so that we can work with kile or another processor.
I am now very worried with lyx since this issue proves that the processor is
very vulnerable and leaves us users in the dark. For future releases: Is it
possible for lyx to use .tex files as default rather than .lyx so that in a
similar failure users can continue working.
comment:18 by , 16 years ago
LyX 1.5.5 will be released in a few days.
In the meantime, you can use the debian unstable version of LyX 1.5.4, which
apparently includes the fix:
http://packages.debian.org/sid/i386/lyx/download
The command to export LyX files to latex is "lyx -e latex file.lyx"
And please don't shout. I am aware that this is frustrating, but everybody here
is doing his best (the failure, btw, is on the side of your distributor).
comment:19 by , 16 years ago
command line is most useful, thank you.
version 1.5.4 does not solve the bug, see
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/228067
please realize that from the user side the bug is NOT resolved fixed.
comment:20 by , 16 years ago
This bug tracker indicates the status of the bugs in the current development
cycle.
This bug is (fortunately) fixed in what becomes 1.5.5, that's why it is marked
FIXED. Note the "Target Milestone". It indicates to both the developers and the
users that the bug is resolved as of the indicated version.
Note that this bug has the highest priority for us, and we try to get out 1.5.5
as soon as possible.
Did you really try the 1.5.4 version from _debian unstable_ (sid) I referred
to? People affected by this bug have reported that this version does not crash.
comment:21 by , 16 years ago
I just tried to install 1.5.4 version from _debian unstable_ (sid)
However, the package installer (Gdebi) returns
"Error:Dependency not satisfiable:
libboost-filesystem1.34.1
However, checked with adept and libboost-filesystem1.34.1 is installed
when is 1.5.5 expected?
comment:23 by , 16 years ago
excelent!
I shall live without lyx till monday.
keep the good work, congratulations!
comment:24 by , 16 years ago
Cc: | added |
---|
comment:26 by , 16 years ago
lyx 1.5.5 compiles ok in kubuntu hardy, works nicely with
qt4.4.0-1ubuntu3~hardy1, without crashes (so far!)
comment:27 by , 16 years ago
Cc: | added |
---|
comment:29 by , 16 years ago
Cc: | added |
---|
comment:31 by , 16 years ago
lyx 1.5.5 also compiles ok in xeon EMT64 bits, kubuntu hardy, works nicely
with qt4.4.0-1ubuntu3~hardy1, without crashes! congratulations!
comment:32 by , 16 years ago
hi, I tried to compile 1.5.5 and I still got the error message that qt4 was not
found. But qt4 is installed (qt4.4.0-1ubuntu3). Here an extract from "./configure"
...
checking for gzopen in -lz... yes
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for pkg-config... no
checking for Qt 4 library name... failed <---------------------
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking whether we are using the GNU C Library 2 or newer... yes
checking for ranlib... (cached) ranlib
...
Configuration
Host type: i686-pc-linux-gnu
Special build flags: pch use-ispell
C Compiler: gcc
C Compiler LyX flags:
C Compiler flags: -O2
C++ Compiler: g++ (4.2.3)
C++ Compiler LyX flags:
C++ Compiler flags: -O2
Linker flags:
Linker user flags:
Qt 4 Frontend:
Qt 4 version:
Packaging: posix
LyX binary dir: /usr/local/bin
LyX files dir: /usr/local/share/lyx
The following problems have been detected by configure.
Please check the messages below before running 'make'.
(see the section 'Problems' in the INSTALL file)
qt 4 library not found !
I also tried it with
"./configure --with-qt4-dir=/usr/lib/qt4". But same result,
I run xubuntu 8.04.
more info:
taram@marlux:~/Desktop$ uname -a
Linux marlux 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
Finally I used "alien lyx-1.5.5-1_openSuse10-3.i586.rpm"
and then "dpkg -i lyx_1.5.5-2_i386.deb"
So lyx was installed and is working fine. No crashes when opening or compiling
lyx files.
Martin
comment:33 by , 16 years ago
Martin, do you have the qt4 header files (named qt4-devel on most distros)
files installed?
comment:34 by , 16 years ago
hi,
yes, "libqt4-dev" - Qt 4 development files - are installed.
here the complete output of
$./configurext-with-qt4-dir=/usr/lib/qt4
configuring LyX version 1.5.5
checking for build type... release
checking for version suffix...
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking what packaging should be used... posix
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... (cached) mawk
checking for kpsewhich... kpsewhich
checking for gm4... no
checking for gnum4... no
checking for m4... m4
checking for a Python interpreter with version >= 2.3... python
checking for python... /usr/bin/python
checking for python version... 2.5
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.5/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.5/site-packages
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for strerror in -lcposix... no
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for AIX... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking what frontend should be used for the GUI... qt4
checking for a good enough C++ compiler... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether the C++ compiler understands explicit... yes
checking whether C library functions are already in the global namespace... no
checking for conforming std::count... yes
checking how to run the C++ preprocessor... g++ -E
checking ostream usability... yes
checking ostream presence... yes
checking for ostream... yes
checking istream usability... yes
checking istream presence... yes
checking for istream... yes
checking sstream usability... yes
checking sstream presence... yes
checking for sstream... yes
checking locale usability... yes
checking locale presence... yes
checking for locale... yes
checking limits usability... yes
checking limits presence... yes
checking for limits... yes
checking ios usability... yes
checking ios presence... yes
checking for ios... yes
checking for modern STL streams... yes
checking for sin in -lm... yes
checking for extra library directory... NONE
checking for extra include directory... NONE
checking for extra lib+include directory... NONE
checking for main in -lshlwapi... no
checking for main in -lgdi32... no
checking for main in -lAiksaurus... no
checking Aiksaurus.h usability... no
checking Aiksaurus.h presence... no
checking for Aiksaurus.h... no
checking Aiksaurus/Aiksaurus.h usability... no
checking Aiksaurus/Aiksaurus.h presence... no
checking for Aiksaurus/Aiksaurus.h... no
checking for wchar_t... yes
checking size of wchar_t... 4
checking for a sed that does not truncate output... /bin/sed
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for iconv... yes
checking for iconv declaration...
extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft,
char * *outbuf, size_t *outbytesleft);
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for gzopen in -lz... yes
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for pkg-config... no
checking for Qt 4 library name... failed
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking whether we are using the GNU C Library 2 or newer... yes
checking for ranlib... (cached) ranlib
checking for an ANSI C-conforming const... yes
checking for signed... yes
checking for inline... inline
checking for off_t... yes
checking for size_t... yes
checking for long long... yes
checking for long double... yes
checking for wchar_t... yes
checking for wint_t... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for intmax_t... yes
checking whether printf() supports POSIX/XSI format strings... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking whether we are using the GNU C Library 2.1 or newer... yes
checking whether integer division by zero raises SIGFPE... yes
checking for unsigned long long... yes
checking for inttypes.h... yes
checking whether the inttypes.h PRIxNN macros are broken... no
checking for stdint.h... (cached) yes
checking for SIZE_MAX... yes
checking for stdint.h... (cached) yes
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for ptrdiff_t... yes
checking argz.h usability... yes
checking argz.h presence... yes
checking for argz.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for asprintf... yes
checking for fwprintf... yes
checking for getcwd... yes
checking for getegid... yes
checking for geteuid... yes
checking for getgid... yes
checking for getuid... yes
checking for mempcpy... yes
checking for munmap... yes
checking for putenv... yes
checking for setenv... yes
checking for setlocale... yes
checking for snprintf... yes
checking for stpcpy... yes
checking for strcasecmp... yes
checking for strdup... yes
checking for strtoul... yes
checking for tsearch... yes
checking for wcslen... yes
checking for argz_count... yes
checking for argz_stringify... yes
checking for argz_next... yes
checking for fsetlocking... yes
checking whether _snprintf is declared... no
checking whether _snwprintf is declared... no
checking whether feof_unlocked is declared... yes
checking whether fgets_unlocked is declared... no
checking whether getc_unlocked is declared... yes
checking for iconv... (cached) yes
checking for iconv declaration... (cached)
extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft,
char * *outbuf, size_t *outbytesleft);
checking for nl_langinfo and CODESET... yes
checking for LC_MESSAGES... yes
checking for bison... no
checking for CFPreferencesCopyAppValue... (cached) no
checking for CFLocaleCopyCurrent... (cached) no
checking whether NLS is requested... yes
checking whether included gettext is requested... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking whether sys/types.h defines makedev... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for sys/types.h... (cached) yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking for strings.h... (cached) yes
checking for locale.h... (cached) yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking sys/utime.h usability... no
checking sys/utime.h presence... no
checking for sys/utime.h... no
checking io.h usability... no
checking io.h presence... no
checking for io.h... no
checking process.h usability... no
checking process.h presence... no
checking for process.h... no
checking NewAPIs.h usability... no
checking NewAPIs.h presence... no
checking for NewAPIs.h... no
checking whether stat file-mode macros are broken... no
checking whether time.h and sys/time.h may both be included... yes
checking for mode_t... yes
checking for off_t... (cached) yes
checking for pid_t... yes
checking return type of signal handlers... void
checking for size_t... (cached) yes
checking for uid_t in sys/types.h... yes
checking for strerror... yes
checking if istreambuf_iterator is declared by header iterator... yes
checking if mkstemp is declared by header unistd.h... no
checking if mkstemp is declared by header stdlib.h... yes
checking for mkdir... yes
checking for _mkdir... no
checking whether mkdir takes one argument... no
checking for chmod... yes
checking for close... yes
checking for _close... no
checking for getpid... yes
checking for _getpid... no
checking for lstat... yes
checking for mkfifo... yes
checking for mkstemp... yes
checking for mktemp... yes
checking for open... yes
checking for _open... no
checking for pclose... yes
checking for _pclose... no
checking for popen... yes
checking for _popen... no
checking for readlink... yes
checking aspell.h usability... no
checking aspell.h presence... no
checking for aspell.h... no
checking aspell/aspell.h usability... no
checking aspell/aspell.h presence... no
checking for aspell/aspell.h... no
checking for new_aspell_config in -laspell... no
checking whether to use aspell... no
checking pspell/pspell.h usability... no
checking pspell/pspell.h presence... no
checking for pspell/pspell.h... no
checking for main in -lpspell... no
checking whether to use pspell... no
checking for fork... yes
checking whether to use ispell... yes
checking for fcntl... yes
checking for library containing gethostbyname... none required
checking for library containing socket... none required
checking for sys/select.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking types of arguments for select... int,fd_set *,struct timeval *
configure: creating ./config.status
config.status: creating Makefile
config.status: creating boost/Makefile
config.status: creating boost/libs/Makefile
config.status: creating boost/libs/filesystem/Makefile
config.status: creating boost/libs/filesystem/src/Makefile
config.status: creating boost/libs/iostreams/Makefile
config.status: creating boost/libs/iostreams/src/Makefile
config.status: creating boost/libs/regex/Makefile
config.status: creating boost/libs/regex/src/Makefile
config.status: creating boost/libs/signals/Makefile
config.status: creating boost/libs/signals/src/Makefile
config.status: creating config/Makefile
config.status: creating development/Makefile
config.status: creating development/MacOSX/Makefile
config.status: creating development/MacOSX/Info.plist
config.status: creating development/MacOSX/lyxrc.dist
config.status: creating development/MacOSX/spotlight/Makefile
config.status: creating development/lyx.spec
config.status: creating intl/Makefile
config.status: creating lib/Makefile
config.status: creating lib/doc/Makefile
config.status: creating lib/lyx2lyx/lyx2lyx_version.py
config.status: creating lib/lyx2lyx/Makefile
config.status: creating m4/Makefile
config.status: creating po/Makefile.in
config.status: creating sourcedoc/Doxyfile
config.status: creating sourcedoc/Makefile
config.status: creating src/client/Makefile
config.status: creating src/Makefile
config.status: creating src/version.cpp-tmp
config.status: creating src/tex2lyx/Makefile
config.status: creating src/mathed/Makefile
config.status: creating src/graphics/Makefile
config.status: creating src/insets/Makefile
config.status: creating src/support/Makefile
config.status: creating src/support/tests/Makefile
config.status: creating src/frontends/Makefile
config.status: creating src/frontends/controllers/Makefile
config.status: creating src/frontends/controllers/tests/Makefile
config.status: creating src/frontends/qt4/Makefile
config.status: creating src/frontends/qt4/ui/Makefile
config.status: creating src/config.h
config.status: src/config.h is unchanged
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
Configuration
Host type: i686-pc-linux-gnu
Special build flags: pch use-ispell
C Compiler: gcc
C Compiler LyX flags:
C Compiler flags: -O2
C++ Compiler: g++ (4.2.3)
C++ Compiler LyX flags:
C++ Compiler flags: -O2
Linker flags:
Linker user flags:
Qt 4 Frontend:
Qt 4 version:
Packaging: posix
LyX binary dir: /usr/local/bin
LyX files dir: /usr/local/share/lyx
The following problems have been detected by configure.
Please check the messages below before running 'make'.
(see the section 'Problems' in the INSTALL file)
qt 4 library not found !
comment:35 by , 16 years ago
Regarding comment 17:
This bug is (fortunately) fixed in what becomes 1.5.5, that's why it is marked
FIXED. Note the "Target Milestone". It indicates to both the developers and the
users that the bug is resolved as of the indicated version.
Juergen, I suggest that you create a keyword "fixedinbranch" and use that instead
of closing bugs. The bugs could then be closed when the release is done.
comment:36 by , 16 years ago
Subject: Re: lyx: SIGSEGV signal caught - can't launch LyX anymore
It works perfectly except that to execute it under Ubuntu 8.04 you
need to create a "lien" named libpcre.so.0 to libpcre.so.3
2008/5/13 <bugzilla-daemon@…>:
------- Additional Comments From martin.orlob@… 2008-05-13 03:00 -------
hi, I tried to compile 1.5.5 and I still got the error message that qt4 was not
found. But qt4 is installed (qt4.4.0-1ubuntu3). Here an extract from "./configure"
...
checking for gzopen in -lz... yes
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for pkg-config... no
checking for Qt 4 library name... failed <---------------------
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking whether we are using the GNU C Library 2 or newer... yes
checking for ranlib... (cached) ranlib
...
Configuration
Host type: i686-pc-linux-gnu
Special build flags: pch use-ispell
C Compiler: gcc
C Compiler LyX flags:
C Compiler flags: -O2
C++ Compiler: g++ (4.2.3)
C++ Compiler LyX flags:
C++ Compiler flags: -O2
Linker flags:
Linker user flags:
Qt 4 Frontend:
Qt 4 version:
Packaging: posix
LyX binary dir: /usr/local/bin
LyX files dir: /usr/local/share/lyx
The following problems have been detected by configure.
Please check the messages below before running 'make'.
(see the section 'Problems' in the INSTALL file)
qt 4 library not found !
I also tried it with
"./configure --with-qt4-dir=/usr/lib/qt4". But same result,
I run xubuntu 8.04.
more info:
taram@marlux:~/Desktop$ uname -a
Linux marlux 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
Finally I used "alien lyx-1.5.5-1_openSuse10-3.i586.rpm"
and then "dpkg -i lyx_1.5.5-2_i386.deb"
So lyx was installed and is working fine. No crashes when opening or compiling
lyx files.
Martin
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
comment:37 by , 16 years ago
I have introduced "fixedinbranch". This will hopefully limit confusion such as
Manuel's in the future.
comment:38 by , 16 years ago
Cc: | added |
---|
comment:40 by , 16 years ago
Cc: | added |
---|
comment:42 by , 16 years ago
Cc: | added |
---|
comment:44 by , 16 years ago
Cc: | added |
---|
comment:46 by , 16 years ago
Cc: | added |
---|
comment:48 by , 16 years ago
Cc: | added |
---|
comment:50 by , 16 years ago
Cc: | added |
---|
comment:52 by , 16 years ago
Cc: | added |
---|
comment:54 by , 16 years ago
Cc: | added |
---|
comment:56 by , 16 years ago
Cc: | added |
---|
comment:58 by , 16 years ago
Cc: | removed |
---|
Is it possible that you updated qt or glibc or something, and that your LyX
version is compiled against some old libraries?