Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-31389

"QXcbConnection: Failed to get the primary output of the screen" when launching applications when using X forwarding

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P2: Important
    • 5.5.0 Beta
    • 5.0.2
    • Core: Plugins
    • Windows 7 with Xming installed and X forwarding enabled in Putty + Ubuntu 12.04 64-bit
    • ebdf9916600f0b0cd4d25b538d1fd0fef6e89077

    Description

      This issue can be reproduced only if launching applications remotely.

      Steps to reproduce
      1. Install Putty and Xming on the Windows 7 machine.
      2. Launch Xming
      3. Launch Putty (from "ssh", check "enable X forwarding")
      4. Connect to the Ubuntu 12.04 machine
      5. Launch e.g Qt Designer or any other Qt application e.g. analogclock

      Expected outcome:
      No warnings or errors are shown

      Actual outcome:
      These warnings are shown:
      QXcbConnection: Failed to get the primary output of the screen
      QXcbConnection: XCB error: 170 (Unknown), sequence: 147, resource id: 90, major
      code: 146 (Unknown), minor code: 20
      QXcbConnection: Failed to get the primary output of the screen
      QXcbConnection: XCB error: 170 (Unknown), sequence: 230, resource id: 8388614,
      major code: 146 (Unknown), minor code: 20

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-45081 Crashes when swapping screens

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-45025 [Reg] QXcbConnection:: no screens available

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          is required for

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. QTBUG-39695 deal better with dynamic screen adding/removal, including the "no screen" case

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-38326 Qt Creator window disappears when plugging out second monitor

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-31354 XCB: QApplication crashes when there is no monitor connected using QT5

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-32973 Windows disappear when X monitor is disconnected

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-42985 Qt GUI application disappear or crash when no screens are available

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTCREATORBUG-11173 Crashes when using through X11 forwarding

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              srutledg Shawn Rutledge
              qtcomsupport Qt Support
              Votes:
              8 Vote for this issue
              Watchers:
              21 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes