> I've been crashing Lyx 1.6.5 by accidentally pressing Command + S + D
> instead of just Command + S to save...
> This highlights the "View" menu then hangs until I need to force quit.
Command + S + D creates a DVI preview of your file. This might take some time because if you have
many images
Hi JMarc,
your recent color resetting commit doesn't work on Windows. It looks horrible, see the attached
screenshot.
I see that you changed the RGB values of your standard colors. E.g. our default background color is
250,240,230 (r,g,b) and you changed it to 236,233,216. Why that? The new co
Anyone?
Original Message
Subject:Command + S + D = crash
Date: Fri, 6 Aug 2010 20:51:07 -0400
From: Benjamin Deschamps
To: lyx-users
While I'm on the list... I've been crashing Lyx 1.6.5 by accidentally pressing
Command + S + D
instead of just Command + S
On 08/06/2010 07:57 PM, Jean-Marc Lasgouttes wrote:
Le 7 août 10 à 01:54, lasgout...@lyx.org a écrit :
Log:
Fix bug #3733: 'undo' does not revert 'changed' status for file
If was not very complicated after all. This could potentially go to
branch
if people feel it is important, but there is n
Le 7 août 10 à 01:54, lasgout...@lyx.org a écrit :
Log:
Fix bug #3733: 'undo' does not revert 'changed' status for file
If was not very complicated after all. This could potentially go to
branch
if people feel it is important, but there is no hurry IMO. The issue
is cosmetic.
JMarc
On Fri, 6 Aug 2010 19:08:14 +0100
Liviu Andronic wrote:
> And another one. This time, same Sweave document with no typo, I
>
Yet another backtrace. This time Sweave wasn't involved, and I only
tried to compile a very simple document. See attached.
Liviu*** glibc detected *** lyx-svn: free(): inva
On Fri, 6 Aug 2010 19:01:56 +0100
Liviu Andronic wrote:
> I got another crash, where LyX pops up a info box
> "LyX has caught an exception, it will now attempt to save all unsaved
> documents and exit.
>
And another one. This time, same Sweave document with no typo, I simply
tried to save it via
On Fri, 06 Aug 2010 16:24:08 +0200
Jean-Marc LASGOUTTES wrote:
> Under valgrind, I get no interesting message, except that I have X
> Errors (that I cannot parse :( ) and an assertion.
>
> It is bad, but I have no idea about what it is.
>
I got another crash, where LyX pops up a info box
"LyX h
Liviu Andronic writes:
> On Fri, 6 Aug 2010 14:41:57 +0100
> Liviu Andronic wrote:
>> I don't know if this is reproducible, but the attached document caused
>> a crash here. I compiled via pdflatex. Does this help or should I
>> attempt more sophisticated debugging?
>>
> Because of the crash I
Jean-Marc LASGOUTTES writes:
> It looks like these session file stored via qt cause problem. It looks
> like every time I do a "make install", I lose some session information
> like toolbar position (on a mac).
>
> How come it is so fragile? Do we really need to have it in a place that
> is differ
On Fri, 6 Aug 2010 14:41:57 +0100
Liviu Andronic wrote:
> I don't know if this is reproducible, but the attached document caused
> a crash here. I compiled via pdflatex. Does this help or should I
> attempt more sophisticated debugging?
>
Because of the crash I didn't save the document. The one
On Fri, 06 Aug 2010 15:27:03 +0200
Jean-Marc LASGOUTTES wrote:
> Is the problem related to the fact that you have a SWeave error?
>
I am not very sure (since I'm currently working only on Sweave
documents), but it seems so. Thinking about it, I was actually
getting crashes in previous alphas, on
Helge Hafting writes:
> Removing .lyx/ did not help. So I used "strace" to find the difference
> between the two users.
>
> I found there is also a per-user .config/LyX/ directory. I removed this,
> and now LyX worked fine!
It looks like these session file stored via qt cause problem. It looks
li
Liviu Andronic writes:
> Now I've got a freeze. Here are the last debug lines:
> Liviu
>
> [..]
> 4 : keep.source term tex
>
> Error: chunk 4
> Error in parse(text = chunk) : unexpected '}' in:
> "cat("\\newpage{}")
> }"
Is the problem related to the fact that you have a SWeave error?
On Fri, 6 Aug 2010 13:28:50 +0100
Liviu Andronic wrote:
> Dear devels
> I'm getting regular crashes in alpha5, something I didn't encounter
> in previous alpha releases. I'll start posting crash messages here,
> when they happen. I attach the backtrace of the latest crash.
>
Now I've got a freez
Liviu Andronic writes:
> Dear devels
> I'm getting regular crashes in alpha5, something I didn't encounter
> in previous alpha releases. I'll start posting crash messages here,
> when they happen. I attach the backtrace of the latest crash.
This would be more usable if it had debug information
Dear devels
I'm getting regular crashes in alpha5, something I didn't encounter
in previous alpha releases. I'll start posting crash messages here,
when they happen. I attach the backtrace of the latest crash.
Regards
Liviu 4 : keep.source term tex
Error: chunk 4
Error in cat(list(...), file,
Richard Heck writes:
> On 08/06/2010 06:55 AM, xPol wrote:
>> Using lyx 1.6.5, as a change is made to the open file, the warning
>> '(changed)' appears on the window bar.
>> Yet, as the change has been undone (by ctrl-z) the warning '(changed)' does
>> not disappear, although the undo command has
On 08/06/2010 06:55 AM, xPol wrote:
Using lyx 1.6.5, as a change is made to the open file, the warning
'(changed)' appears on the window bar.
Yet, as the change has been undone (by ctrl-z) the warning '(changed)' does
not disappear, although the undo command has been disabled, therefore the
(buff
On 08/06/2010 04:02 AM, Kornel Benko wrote:
...
cd /Creatable/BUILD/BuildLyx/src/frontends/qt4&& /usr/bin/c++ -DHAVE_GETTEXT
-DQT_GENUINE_STR -DLYX_BUILD_QT4_FRONTEND -Wall -fno-strict-aliasing -Wall -O3
-DNDEBUG -I/Creatable/BUILD/BuildLyx -I/usr/src/lyx/lyx-devel/src
-I/usr/include/Aiksa
On 08/06/2010 04:02 AM, Kornel Benko wrote:
...
cd /Creatable/BUILD/BuildLyx/src/frontends/qt4&& /usr/bin/c++ -DHAVE_GETTEXT
-DQT_GENUINE_STR -DLYX_BUILD_QT4_FRONTEND -Wall -fno-strict-aliasing -Wall -O3
-DNDEBUG -I/Creatable/BUILD/BuildLyx -I/usr/src/lyx/lyx-devel/src
-I/usr/include/Aiksa
On Fri, Aug 06, 2010 at 12:29:34PM +0200, Helge Hafting wrote:
Hi,
> Any idea what might have happened?
I guess I should've forwarded
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524332
but I never found a way to reproduce it. :(
And yes it would be interesting to shed some light on the iss
I started up Debian's lyx 1.6.7 today. The menus didn't work. Neither
did they work for my self-compiled lyxes. Very strange. The main menu
was there, but it was impossible to pull anything down!
So I logged in as another user, and LyX worked fine there. So, a user
setup problem.
Removing .l
On 06. aug. 2010 10:02, Kornel Benko wrote:
...
cd /Creatable/BUILD/BuildLyx/src/frontends/qt4&& /usr/bin/c++ -DHAVE_GETTEXT
-DQT_GENUINE_STR -DLYX_BUILD_QT4_FRONTEND -Wall -fno-strict-aliasing -Wall -O3
-DNDEBUG -I/Creatable/BUILD/BuildLyx -I/usr/src/lyx/lyx-devel/src
-I/usr/include/Aiksa
...
cd /Creatable/BUILD/BuildLyx/src/frontends/qt4 && /usr/bin/c++ -DHAVE_GETTEXT
-DQT_GENUINE_STR -DLYX_BUILD_QT4_FRONTEND -Wall -fno-strict-aliasing -Wall -O3
-DNDEBUG -I/Creatable/BUILD/BuildLyx -I/usr/src/lyx/lyx-devel/src
-I/usr/include/Aiksaurus -I/usr/src/lyx/lyx-devel/po
-I/usr/src/l
25 matches
Mail list logo
