Results 1 to 3 of 3

Thread: mysql-workbench segfaults

  1. #1
    Join Date
    May 2015
    Location
    Italy
    Posts
    377

    Default mysql-workbench segfaults

    Hi all, I cannot start mysql-workbench anymore: it segfaults.
    I am not sure when it began misbehaving, because I've not been using it for some time.

    This is information about the package:
    Code:
    cristiano@xmper8q3 [~/public_html/bookmarker]$ LANG=C zypper info mysql-workbench
    Loading repository data...
    Reading installed packages...
    
    
    Information for package mysql-workbench:
    ----------------------------------------
    Repository     : repo-oss
    Name           : mysql-workbench
    Version        : 6.3.7-5.8
    Arch           : x86_64
    Vendor         : openSUSE
    Installed Size : 87.5 MiB
    Installed      : Yes
    Status         : up-to-date
    Source package : mysql-workbench-6.3.7-5.8.src
    Summary        : A MySQL visual database modeling, administration and querying tool
    Description    :
        MySQL Workbench is a modeling tool that allows you to design
        and generate MySQL databases graphically. It also has administration
        and query development modules where you can manage MySQL server instances
        and execute SQL queries.
        This is the community build.
    And here is the output I get when I try to start it.

    Anybody else?

    Thank you in advance
    Cris
    Desktop: OpenSUSE Tumbleweed (x86_64) - AMD FX-8350 Eight-Core Processor, 16Gb RAM, 120GB Samsung Evo 840 SSD
    Laptop: OpenSUSE Tumbleweed (x86_64) - Thinkpad T440 - Intel i5-4210U, 12Gb RAM, 250GB Samsung EVO 750 SSD

  2. #2

    Default AW: mysql-workbench segfaults

    Works fine here, but I'm on Leap 42.2.

    Quote Originally Posted by Cris70 View Post
    And here is the output I get when I try to start it.
    I see this:
    Code:
    Backtrace:
    
    /lib64/libcrypto.so.1.0.0(OPENSSL_ia32_cpuid+0x5)[0x7fd94b7562e5]
    
    ...
    7fd941051000-7fd941251000 ---p 001ba000 00:27 766313 /usr/lib64/libcrypto.so.33.0.0
    7fd941251000-7fd94126f000 r--p 001ba000 00:27 766313 /usr/lib64/libcrypto.so.33.0.0
    7fd94126f000-7fd941279000 rw-p 001d8000 00:27 766313 /usr/lib64/libcrypto.so.33.0.0
    Apparently there are two libcrypto's loaded at the same time, the one from openssl and the one from libressl.
    I'd find it likely that this is the reason for your crash.

    I'd suggest to uninstall libcrypto33 and see if it helps.
    Though you probably have some other libs built against libressl installed too, and that's what actually pulls in libcrypto.so.33.0.0. So you'd either need to remove them too or switch them to the openssl versions.

    Btw, libcrypto33 is outdated anyway, Tumbleweed only has libcrypto41 currently...

  3. #3
    Join Date
    May 2015
    Location
    Italy
    Posts
    377

    Default Re: mysql-workbench segfaults

    Thank you very much wolfi323, that was the problem.

    After removing libcrypto33 I had another segfault, and it turned out I had libcrypto32 installed too.
    After removing libcrypto32 mysql-workbench started without problems.

    Cris
    Desktop: OpenSUSE Tumbleweed (x86_64) - AMD FX-8350 Eight-Core Processor, 16Gb RAM, 120GB Samsung Evo 840 SSD
    Laptop: OpenSUSE Tumbleweed (x86_64) - Thinkpad T440 - Intel i5-4210U, 12Gb RAM, 250GB Samsung EVO 750 SSD

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •