Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Qt Creator fresh install Ubuntu 18.04, will open and close
Qt 6.11 is out! See what's new in the release blog

Qt Creator fresh install Ubuntu 18.04, will open and close

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
ubuntu 18.04errorinstall ubuntu
3 Posts 2 Posters 1.8k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    biaspoint
    wrote on last edited by
    #1

    Did a fresh re-install of 18.04 and then installed Qt with:
    sudo apt-get install build-essential
    sudo apt-get install qtcreator
    sudo apt-get install qt5-default

    now when I launch it closes within seconds, and when launched from the terminal:

    SOFT ASSERT: "!tcd.tcs.isEmpty()" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/cmakeprojectmanager/cmakeprojectimporter.cpp, line 336
    SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
    SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
    SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
    SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
    SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
    SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
    SOFT ASSERT: "!tcd.tcs.isEmpty()" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/cmakeprojectmanager/cmakeprojectimporter.cpp, line 336
    Segmentation fault (core dumped)

    Interestingly I did not format my home directory, and the first time Qt Creator launched I saw a few of my old workspaces written in red, like they were still being referenced even though everything should have been new?

    B 1 Reply Last reply
    0
    • B biaspoint

      Did a fresh re-install of 18.04 and then installed Qt with:
      sudo apt-get install build-essential
      sudo apt-get install qtcreator
      sudo apt-get install qt5-default

      now when I launch it closes within seconds, and when launched from the terminal:

      SOFT ASSERT: "!tcd.tcs.isEmpty()" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/cmakeprojectmanager/cmakeprojectimporter.cpp, line 336
      SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
      SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
      SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
      SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
      SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
      SOFT ASSERT: "k" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/projectexplorer/targetsettingspanel.cpp, line 315
      SOFT ASSERT: "!tcd.tcs.isEmpty()" in file /build/qtcreator-4mibqh/qtcreator-4.5.2/src/plugins/cmakeprojectmanager/cmakeprojectimporter.cpp, line 336
      Segmentation fault (core dumped)

      Interestingly I did not format my home directory, and the first time Qt Creator launched I saw a few of my old workspaces written in red, like they were still being referenced even though everything should have been new?

      B Offline
      B Offline
      biaspoint
      wrote on last edited by
      #2

      @biaspoint
      So I decided to remove and start over. After looking at the packages that are installed:
      dpkg -l | grep qt | awk '{print $2}' | xargs -n1 echo

      only included items that "looked" like Qt, I used the following to get rid of all the Qt items:
      sudo apt-get --purge remove 'qt.*'

      Note: that can take a lot of things out that you do not intend... use carefully!

      I then retried using the same steps above, however this time I read the reports and added:

      sudo apt autoremove

      after the

      sudo apt-get install build-essential

      step.

      Now when I launch I get a "Cannot overwrite file /home/.../.config/QTProject/qtcreator/toolchains.xml: Permission denied."

      I then removed any "QT" folder in that path.

      and Voila... working QT!

      JonBJ 1 Reply Last reply
      1
      • B biaspoint

        @biaspoint
        So I decided to remove and start over. After looking at the packages that are installed:
        dpkg -l | grep qt | awk '{print $2}' | xargs -n1 echo

        only included items that "looked" like Qt, I used the following to get rid of all the Qt items:
        sudo apt-get --purge remove 'qt.*'

        Note: that can take a lot of things out that you do not intend... use carefully!

        I then retried using the same steps above, however this time I read the reports and added:

        sudo apt autoremove

        after the

        sudo apt-get install build-essential

        step.

        Now when I launch I get a "Cannot overwrite file /home/.../.config/QTProject/qtcreator/toolchains.xml: Permission denied."

        I then removed any "QT" folder in that path.

        and Voila... working QT!

        JonBJ Offline
        JonBJ Offline
        JonB
        wrote on last edited by
        #3

        @biaspoint
        I am pleased you have your situation sorted.

        Purely OOI, because I like shell scripting, why did you bother to put the xargs into your command when
        dpkg -l | grep qt | awk '{print $2}'
        would deliver the same result? :) | xargs -n1 echo is a bit of a no-op?

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved