Am 26.04.2020 um 23:58 schrieb Enrico Forestieri:
On Sun, Apr 26, 2020 at 11:22:55AM +0200, Marco Atzeri wrote:
Am 26.04.2020 um 08:56 schrieb Marco Atzeri:
Hi,

Hi Marco

I am trying to move the Cygwin lyx package from
QT4 4.8.x to QT5 5.9.4

The build is fine but the "open file" and other windows come
completly blank and black

It seems to work fine for me.

I do not see any specific error report, the only log is

QXcbShmImage: shmget() failed (88: Function not implemented) for size
1407600 (690x510)
QXcbShmImage: shmget() failed (88: Function not implemented) for size
518976 (318x408)
Gtk-Message: GtkDialog mapped without a transient parent. This is
discouraged.
QXcbShmImage: shmget() failed (88: Function not implemented) for size
12000 (100x30)

I also see these warnings but they do not seem to cause any misbehavior.

I have not found any specific bug report on similar issue.

Any suggestion ?

I have none, unfortunately.

Forgot 1 point:

the only not trivial warning at build seems:

/usr/include/qt5/QtGui/qtransform.h:81:46: warning: ‘void* memcpy(void*,
const void*, size_t)’ writing to an object of type ‘class QTransform’ with
no trivial copy-assignment; use copy-assignment or copy-initialization
instead [-Wclass-memaccess]
    81 |     { memcpy(this, &other, sizeof(QTransform)); return *this; }
       |                                              ^
/usr/include/qt5/QtGui/qtransform.h:57:20: note: ‘class QTransform’ declared
here
    57 | class Q_GUI_EXPORT QTransform
       |                    ^~~~~~~~~~

I don't see this specific warning. Only a lot of

/usr/include/qt5/QtCore/qdatastream.h:346:21: warning: ‘QDataStream& 
QDataStream::operator>>(quint32&)’ redeclared without dllimport attribute after 
being referenced with dll linkage
  inline QDataStream &QDataStream::operator>>(quint32 &i)

That is usual on Cygwin builds, the compiler has workaround
for dllimport if not used, so it is usually innocuous.


and some hunspell warnings about deprecated declarations.

no such warning with latest hunspell 1.7.0


Anyway, I solved the issue.
It seems the script for running the X Server that I was using was not
anymore in sync with the latest version of the X Server.
After removing the .startxwinrc file, the problem was gone.

Strange that it was impacting only Lyx, I have not seen it with other programs.

Regards
Marco
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Reply via email to