/klayout

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ SALT package manager ] Item description in Salt package manager missing on Linux #144

Closed
philippm1988 opened this Issue Jul 16, 2018 · 8 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@philippm1988 @klayoutmatthias
@philippm1988
Copy link

philippm1988 commented Jul 16, 2018

In Salt package manager on Linux, the item description for all items is missing.
On Windows this problem does not exist.
KLayout was built with the sources from https://github.com/klayoutmatthias/klayout/tree/v0.25.3
with the following command: ./build.sh ( -qt5 )

Here is how it looks like on Linux ( openSUSE Leap 42.3 / openSuse Leap 15 ):

item_description_missing

... and how it looks like on Windows ( Windows 10 ):

salt_package_manager_windows

What is the reason for this strange behavior ?
@klayoutmatthias

This comment has been minimized.

Sign in to view
Copy link
Collaborator

klayoutmatthias commented Jul 16, 2018

Hi,

this is strange - I do see the descriptions. I use Ubuntu 16.04.

Maybe it's specific to Qt5 and/or OpenSuSE. I'll take a look.

Thanks,

Matthias

@philippm1988 philippm1988 changed the title Item description in Salt package manager missing on Linux [ SALT package manager ] Item description in Salt package manager missing on Linux Jul 27, 2018

@klayoutmatthias

This comment has been minimized.

Sign in to view
Copy link
Collaborator

klayoutmatthias commented Jul 27, 2018 •
edited

Hi Phillip,

I have just built KLayout on plain OpenSuSE 42.3 with Qt 4.8.6, Ruby 2.1.0 and Python 3.4. I don't see that issue myself.

I have postponed OpenSuSE 42.3 support because I saw some issues in the test suite. They seem to be fixed now, so I may be able to provide an RPM for this.

But this means it's not OpenSuSE or the compiler, but my guess is Qt5. Which is the Qt5 version you used?

Thanks,

Matthias
@klayoutmatthias

This comment has been minimized.

Sign in to view
Copy link
Collaborator

klayoutmatthias commented Jul 28, 2018

I have established a OpenSuSE 42.3 build on the CI system. If will become active for 0.25.4. Maybe you want to try this "official" RPM: http://www.klayout.org/downloads/staging/opensuse42_3/klayout-0.25.4-0.x86_64.rpm

It's based on the standard packages of OpenSuSE 42.3. With theses packages I don't see the issue you show in the screenshots.

Matthias
@philippm1988

This comment has been minimized.

Sign in to view
Copy link

philippm1988 commented Jul 30, 2018 •
edited

Hi Matthias,

I build it on openSuse Leap 15 with the standard packages and Qt 5.9 ( libqt5-qtbase, libqt5-qtmultimedia, ... ) with the option -qt5.
I got the same result when using Qt4 ( libqt4, libqt4-devel )

Would be great if you can have a look and if possible provide an rpm for openSuse Leap 15 too !

Thanks,

Philipp
@klayoutmatthias

This comment has been minimized.

Sign in to view
Copy link
Collaborator

klayoutmatthias commented Jul 30, 2018

I just found how to reproduce the issue!

It's related to Motif style. Apparently you're on Motif style by default. If you use a different style (e.g. "klayout -style gtk+" or "klayout -style cleanlooks"), the descriptions become visible.

I'll check whether I can fix this quickly.

Best regards,

Matthias

P.S: Wenn Du derjenige bist, den ich im Netz finde, dann sind wir quasi Nachbarn - ich wohne südlich vom Rosenheimer Platz :-)

@klayoutmatthias klayoutmatthias closed this in a272cd3 Jul 30, 2018

@klayoutmatthias

This comment has been minimized.

Sign in to view
Copy link
Collaborator

klayoutmatthias commented Jul 31, 2018

For OpenSuSE Leap 15, please try http://www.klayout.org/downloads/staging/opensuse15/klayout-0.25.4-0.x86_64.rpm

Matthias
@philippm1988

This comment has been minimized.

Sign in to view
Copy link

philippm1988 commented Aug 1, 2018

Hi Matthias,

for OpenSuse 15, the item descriptions in package manager are shown now, but after I installed the above rpm on the latest OpenSuse 15 version, i get the following error each time I close klayout (x):

ERROR: Signal number: 11
Address: 0x0
Program Version: KLayout 0.25.4 (2018-07-31 r5efe5d20)

Backtrace:
/usr/lib64/klayout/libklayout_lay.so.0 +0x2b58e0 lay::enable_signal_handler_gui(bool) [??:?]
/lib64/libpthread.so.0 +0x122e0 __restore_rt [??:?]
/usr/lib64/qt4/plugins/inputmethods/libqimsw-multi.so +0x2c93 ?? [??:0]
/usr/lib64/qt4/plugins/inputmethods/libqimsw-multi.so +0x2d3e ?? [??:0]
/usr/lib64/libQtGui.so.4 +0x24b2be QApplicationPrivate::_q_alertTimeOut() [??:?]
/usr/lib64/libQtGui.so.4 +0x1da12d QApplication::~QApplication() [??:?]
/usr/lib64/klayout/libklayout_lay.so.0 +0xeb8e9 lay::GuiApplication::~GuiApplication() [??:?]
klayout +0x2d15
/usr/lib64/klayout/libklayout_rba.so.0 +0x1e970
/usr/lib64/libruby2.5.so.2.5 +0x1ab9d1
/usr/lib64/libruby2.5.so.2.5 +0x1bed83
/usr/lib64/libruby2.5.so.2.5 +0x1b5a40
/usr/lib64/libruby2.5.so.2.5 +0x1bafed
/usr/lib64/libruby2.5.so.2.5 +0x97454
/usr/lib64/libruby2.5.so.2.5 +0x9928d ruby_exec_node
/usr/lib64/libruby2.5.so.2.5 +0x9b65e ruby_run_node
/usr/lib64/klayout/libklayout_rba.so.0 +0x1eec4 _ZN3rba15RubyInterpreter10initializeERiPPcPFiS1_S3_E
klayout +0x2674
/lib64/libc.so.6 +0x20f4a __libc_start_main
klayout +0x278a
@klayoutmatthias

This comment has been minimized.

Sign in to view
Copy link
Collaborator

klayoutmatthias commented Aug 12, 2018

netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this issue Sep 22, 2018

mef
Updated cad/klayout to 0.25.4 
0.25.4          (2018-08-25):
* Bugfix: KLayout/klayout#121
       Issue with multiple reads of GDS2 layouts including PCells
* Bugfix: KLayout/klayout#134
       Error in cell.fill_region caused by big polygon with
       spikes
* Bugfix: KLayout/klayout#139
       Libraries have not been reassigned when loading a GDS file
       from command line (does not happen on File/Open)
* Bugfix: KLayout/klayout#141
       Issue with RBA::QHostAddress (ambiguous overload) on Qt5
* Bugfix: KLayout/klayout#142
       Issue with RBA::RecursiveShapeIterator#region=
* Bugfix: KLayout/klayout#144
       The Salt package descriptions are not shown with Motif
       style
* Bugfix: KLayout/klayout#148
       Wrong font is used
* Bugfix: KLayout/klayout#152
       Shapes#size reported a wrong shape count in viewer mode
* Bugfix: KLayout/klayout#153
       Application crash when editing guiding shape properties
* Bugfix: KLayout/klayout#155
       Program freezes after replacing nothing by something in
       Macro editor
* Bugfix: KLayout/klayout#157
       "Replace cell with ..." rejected cell names with a library
       prefix
* Bugfix: KLayout/klayout#158
       Repaint issue on cell context
* Bugfix: KLayout/klayout#159
       Tech specific macros and DRC scripts were not shown in tech
       manager
* Bugfix: 8 bit indexed GIF images can be used for package icons now
* Enhancement: Provide a way to specify the type of a macro
       This feature is mainly useful for command line arguments.
       If you run KLayout with "klayout -b -r myscript"
       it will not be able to determine the type of macro without
       a suffix.

       You can now explicitly specify a certain type by
       giving the suffix implicitly like: "klayout -b -r myscript[rb]"
       This will read "myscript" but pretend it was "myscript.rb"
       and execute it as Ruby script.

       This feature is handy if you need to run a file with a
       specific interpreter but cannot modify the file name.
* Enhancement: Selection now shows PCell display names
       Before, the internal name was shown for instances
* Enhancement: There is an option in the View menu to show or hide markers
       Markers may hide layout under them. With this feature you can
       quickly disable all markers and the layout becomes visible.
325629a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment