Le 12/03/2023 à 15:18, Wolfgang Engelmann a écrit :
Am 12.03.23 um 15:14 schrieb Jean-Marc Lasgouttes:
Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit :
did I send the correct infos? I am still not sure what I should do in
case of a crash in gdb. Was 'where' helpful?
I did not find the ou
Am 12.03.23 um 15:14 schrieb Jean-Marc Lasgouttes:
Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit :
did I send the correct infos? I am still not sure what I should do in
case of a crash in gdb. Was 'where' helpful?
I did not find the output very useful, but it is probably not you fault.
Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit :
did I send the correct infos? I am still not sure what I should do in
case of a crash in gdb. Was 'where' helpful?
I did not find the output very useful, but it is probably not you fault.
Is the problem reproducible? What were you doing at th
Am 12.03.23 um 01:42 schrieb Richard Kimberly Heck:
On 3/11/23 08:05, Wolfgang Engelmann wrote:
This I got in the terminal
and in the gdb
Wolfgang
>>>
insets/InsetCommandParams.cpp (278): InsetCommand: Incompatible
command name Standard.
That will lead to an assertion, at least. It also
On 3/11/23 08:05, Wolfgang Engelmann wrote:
This I got in the terminal
and in the gdb
Wolfgang
>>>
insets/InsetCommandParams.cpp (278): InsetCommand: Incompatible
command name Standard.
That will lead to an assertion, at least. It also should not happen.
"Standard" sounds like a layout nam
Am 11.03.23 um 13:31 schrieb José Matos:
On Sat, 2023-03-11 at 10:16 +0100, Wolfgang Engelmann wrote:
To whom should I report a 2.4.0 crash?
I use
Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022)
Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb)
Qt-Version (bei Erstellung): 5.15.2
OS-Version (bei
On Sat, 2023-03-11 at 10:16 +0100, Wolfgang Engelmann wrote:
> To whom should I report a 2.4.0 crash?
> I use
> Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022)
> Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb)
> Qt-Version (bei Erstellung): 5.15.2
> OS-Version (bei Erstellung): Debian GNU/Linux 11
To whom should I report a 2.4.0 crash?
I use
Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022)
Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb)
Qt-Version (bei Erstellung): 5.15.2
OS-Version (bei Erstellung): Debian GNU/Linux 11 (bullseye)
Python-Aufruf: python3 -tt
and started the document with
gd
Rich Shepard wrote:
> That did the trick! I applied the patch, rebuilt the tarball, and re-ran
> the SlackBuild script. Re-installed the application and it imported the
> text file as usual.
Excellent.
> I still have a few keyboard quirks to fix (e.g., pressing the [Del] key
> displays the spa
On Fri, 9 Jan 2009, Jürgen Spitzmüller wrote:
No, I was referring to the File filter list set by LyX for this file dialog. I
assume you are building LyX yourself. Could you apply the attached patch and
check if this helps?
Jürgen,
That did the trick! I applied the patch, rebuilt the tarball
Rich Shepard wrote:
> I assume that you refer to the file filters on my system.
No, I was referring to the File filter list set by LyX for this file dialog. I
assume you are building LyX yourself. Could you apply the attached patch and
check if this helps?
(to apply: put the file in the upperm
On Thu, 8 Jan 2009, Jürgen Spitzmüller wrote:
Doesn't crash for me. However, the file filters are not correctly set.
Jürgen,
I assume that you refer to the file filters on my system. When I navigate
to Edit -> Preferences -> File handling I see two choices: Converters and
File Formats. The
Rich Shepard wrote:
> Open existing document. Select from menu Insert -> Insert File -> Plain
> text join lines (or just Plain text). Instant crash; lyx shuts down.
Doesn't crash for me. However, the file filters are not correctly set.
> Invoking from the command line with the -dbg switch tells m
Cue the music, please. This is a repeatable error -- a fatal flaw, in fact
-- with lyx-1.6.1 on Slackware-12.1.
Open existing document. Select from menu Insert -> Insert File -> Plain
text join lines (or just Plain text). Instant crash; lyx shuts down.
Invoking from the command line with the
On Fri, 26 May 2006, Georg Baum wrote:
If the cursor was inside a table during the class change then this is a
known bug that is already fixed in 1.4.2svn.
Georg,
It may well have been that situation. I set up a 2 row/1 column table in
the title environment so I could put the company logo a
Rich Shepard wrote:
>Situation: LyX-1.4.1 on Slackware-10.2/teTeX-3.0-i486-2_10.2. Document
> type was Koma-report and I changed it to article. As soon as I clicked on
> the Apply button the application instantly shut down.
>
>Re-invoked it and opened the emergency save. Just thought you
Situation: LyX-1.4.1 on Slackware-10.2/teTeX-3.0-i486-2_10.2. Document
type was Koma-report and I changed it to article. As soon as I clicked on the
Apply button the application instantly shut down.
Re-invoked it and opened the emergency save. Just thought you developers
would like to be awar
17 matches
Mail list logo