Bug#753993: lyx: SIGSEGV when saving a new LyX file resulting in data loss

2014-07-09 Thread Georg Baum
The development of the 2.0.x series of LyX was closed with the release of 
2.0.8.1. There will be no further bug fixes upstream, and I don't think it 
makese sense to try debian specific fixes.

Unfortunately LyX 2.1.0 suffers from a more serious crash which is 
extremely difficult to reproduce, but has been seen by several people, see 
http://www.lyx.org/trac/ticket/9049. I doubt it has anything to do with 
this report, but I mention it for completeness.

Thanks,
Georg


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#428967: [Pkg-lyx-devel] Bug#428967: Bug#428967: lyx: main window does not repaint with Qt 4.3

2007-06-16 Thread Georg Baum
Am Freitag, 15. Juni 2007 12:06 schrieb Per Olofsson:
 Hi,
 
 On 2007-06-15 Laurent Bonnaud wrote:
  since I upgraded this system with Qt 4.3 from experimental, lyx does 
  not
  work any longer.  It opens its main window but is not able to draw it:
  
  $ lyx
  QWidget::repaint: Recursive repaint detected
  QWidget::repaint: Recursive repaint detected
  [...]

This problem has been reported some time ago on the Mac (and fixed), search 
the LyX devel mailing list archives.

 Thank you for reporting this. We are going to upload LyX 1.5.0rc1 soon,
 I will check if the bug is still present in that version.

I don't think that using rc1 it will make a difference. Maybe Qt 4.3 is not 
as binary compatible to 4.2 as supposed and recompiling against Qt 4.3 
helps?


Georg


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#415636: Fixed upstream

2007-03-22 Thread Georg . Baum
Fixed upstream: http://www.lyx.org/trac/changeset/17506


Georg



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#402148: Fwd: Re: Source for latex-xft-fonts?

2007-01-16 Thread Georg Baum
Forgot to CC the bug tracker.

--  Weitergeleitete Nachricht  --

Subject: Re: Source for latex-xft-fonts?
Date: Dienstag, 16. Januar 2007 20:59
From: Georg Baum [EMAIL PROTECTED]
To: lyx-devel@lists.lyx.org

Am Dienstag, 16. Januar 2007 20:36 schrieb John Levon:
 On Tue, Jan 16, 2007 at 08:11:22PM +0100, Per Olofsson wrote:
 
  There is a bug filed against the latex-xft-fonts Debian package about
  the lack of source code for it (http://bugs.debian.org/402148). This
  prevents the package from entering etch (the upcoming stable release
  of Debian).
  
  Apparently the fonts have been converted from the corresponding LaTeX
  .pfb fonts. Does anyone know how this was done? Is it possible to
  automate?
 
 I've entirely forgotten how I did it, but it definitely involved some
 manual fixing of the fonts. I used some popular open-source font editor,
 which I've also forgotten, and I had to fix some stuff up if I remember
 rightly.

You probably used fontforge (formerly called PFAEdit IIRC).

 I have no idea what sources they're looking for. It's like complaining
 a .jpg doesn't have sources when it's a scanned in photo.

No, it is rather like looking for the source of a jpeg that somebody 
created by manually modifying another one. This cannot be automated 
either.

To me the ttf fonts look like a derived work of the original pfb versions. 
So, these could be considered as source, but the normal way of automated 
building from source would not work, so it would be pointless. AFAIK the 
original pfb fonts are under the LPPL, so I think the following would 
work:

- The ttf files are considered as source technically.
- The README documents that they were converted from the .pfb files and 
polished manually after that.
- The README documents where to get the .pfb files (required by the LPPL).

IANAL, but I see no reason why this would not work.


Georg



---



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]