Bug 1291371 - konsole does not start reliably
Summary: konsole does not start reliably
Keywords:
Status: CLOSED DUPLICATE of bug 1291260
Alias: None
Product: Fedora
Classification: Fedora
Component: konsole5
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-14 17:26 UTC by long
Modified: 2016-01-28 11:54 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-01-28 11:54:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description long 2015-12-14 17:26:31 UTC
Description of problem:
When I start konsole I have to start two or more instances before it actually works.  The first instance or two displays a transparent window and title bar and does nothing.  

Version-Release number of selected component (if applicable):
konsole5-15.08.3-1.fc23.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Login to kde
2. Right click desktop, "Konsole" or open an xterm and run "konsole"
3.

Actual results:
Transparent konsole window with title bar is created.  In the xterm it says:
[long@kite .config]$ konsole
QCoreApplication::arguments: Please instantiate the QApplication object first
[long@kite .config]$ The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly.
0x5631602bc1a0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x56315ff9ea40) ): Attempt to set a screen on a child window.
0x563160313730 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x56315ff9ea40) ): Attempt to set a screen on a child window.
0x563160313b80 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x56315ff9ea40) ): Attempt to set a screen on a child window.
0x563160332af0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x56315ff9ea40) ): Attempt to set a screen on a child window.
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1620, resource id: 23068769, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1628, resource id: 23068769, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1636, resource id: 23068769, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1642, resource id: 23068769, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1650, resource id: 23068769, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1663, resource id: 23068769, major code: 130 (Unknown), minor code: 3


Expected results:
A working konsole window

Additional info:

Comment 1 Rex Dieter 2015-12-14 17:48:03 UTC
Do you have multiple displays?  Are you using nvidia drivers?

Comment 2 long 2015-12-14 17:51:14 UTC
Hi, I do have two displays.  I am not using nvidia drivers, it is intel drivers.

Comment 3 Martin Kho 2015-12-28 10:18:42 UTC
Hi,

Same issue here with 2 monitors and AMD graphics card (R600g driver). When I start several instances of konsole (>5) plasmashell is getting very unstable. For instance, this shows up when switching desktops.

HTH

Martin Kho

Comment 4 Martin Kho 2015-12-28 12:42:35 UTC
Hi,

Update: It seems that this issue has indeed to do with two-monitor setup. When konsole opens on my primary screen it works as expected, on the secondary screen it fails.

Martin Kho

Comment 5 Rex Dieter 2016-01-28 11:54:26 UTC

*** This bug has been marked as a duplicate of bug 1291260 ***


Note You need to log in before you can comment on or make changes to this bug.