Bug 381206

Summary: Knetwalk starts up but the content of the screen is not visible (black screen)
Product: [Applications] knetwalk Reporter: HERVE MOENS <herve.moens>
Component: generalAssignee: Ashwin Rajeev <ashwin_rajeev>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aacid, kde-games-bugs, ped
Priority: NOR    
Version: 3.3.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description HERVE MOENS 2017-06-14 15:13:02 UTC
Starting program: /usr/bin/knetwalk 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe3e7e700 (LWP 18048)]
[New Thread 0x7fffdbfff700 (LWP 18049)]
[New Thread 0x7fffdadee700 (LWP 18050)]
[New Thread 0x7fffd940d700 (LWP 18051)]
[Thread 0x7fffd940d700 (LWP 18051) exited]
[New Thread 0x7fffd940d700 (LWP 18053)]
[Thread 0x7fffd940d700 (LWP 18053) exited]
[New Thread 0x7fffd940d700 (LWP 18054)]
[New Thread 0x7fffe0207700 (LWP 18055)]
Module 'org.kde.games.core' does not contain a module identifier directive - it cannot be protected from external registrations.
games.ui: KStandardGameAction::create(  1 = game_new , KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
games.ui: KStandardGameAction::create(  7 = game_pause , KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
games.ui: KStandardGameAction::create(  25 = move_solve , KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
games.ui: KStandardGameAction::create(  8 = game_highscores , KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
games.ui: KStandardGameAction::create(  11 = game_quit , KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
[New Thread 0x7fffb8c17700 (LWP 18056)]
[New Thread 0x7fffb08e5700 (LWP 18057)]
[New Thread 0x7fffaf454700 (LWP 18058)]
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings
[Thread 0x7fffdadee700 (LWP 18050) exited]
[Thread 0x7fffaf454700 (LWP 18058) exited]
[Thread 0x7fffe3e7e700 (LWP 18048) exited]
[Thread 0x7fffb08e5700 (LWP 18057) exited]
[Thread 0x7fffb8c17700 (LWP 18056) exited]
[Thread 0x7fffe0207700 (LWP 18055) exited]
[Thread 0x7fffd940d700 (LWP 18054) exited]
[Thread 0x7fffdbfff700 (LWP 18049) exited]
[Inferior 1 (process 18043) exited normally]
(gdb)
Comment 1 Albert Astals Cid 2017-06-14 20:48:07 UTC

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