Bug 372683 - Attempt to set a screen on a child window : No id for action
Summary: Attempt to set a screen on a child window : No id for action
Status: RESOLVED UPSTREAM
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: 5.3.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-20 04:15 UTC by e.longuemare
Modified: 2017-07-13 13:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.4.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description e.longuemare 2016-11-20 04:15:18 UTC
Hello,

I'm testing migration from my Digikam 3.5.0 setup to 5.3.0 (from Philips ppa) and Ubuntu 16.04.

On my notebook I see some of those messages on Digikam  :

0x42e3670 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1285d40) ): Attempt to set a screen on a child window.

void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action

No crash, but I can't find similar ones except foor Kate : https://bugs.kde.org/show_bug.cgi?id=368903

I use standard Desktop Ubuntu with Unity.

Thanks,

Eric

PS : all have been right for mysql shared database
Comment 1 caulier.gilles 2016-11-20 12:37:18 UTC
The problem sound like a packaging issue, not a digiKam problem, and in all case it's not relevant of database.

Just to try, use digiKam AppImage bundle instead system version :

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM
Comment 2 e.longuemare 2016-11-20 13:49:08 UTC
Hello,

Do you mean like this : https://www.digikam.org/node/743#comment-21099 ?

I'll check package list.

Thanks,

Eric
Comment 3 caulier.gilles 2016-11-20 13:54:18 UTC
I don't know. I don't use Kubuntu.

Download and run digiKam AppImage Linux Bundle to verify if problem come from really than Kubuntu package or not. I given the link on comment #1

Gilles Caulier
Comment 4 e.longuemare 2016-11-20 14:51:44 UTC
Ok I will do it.

Some more clues : http://stackoverflow.com/questions/33545006/qt5-attempt-to-set-a-screen-on-a-child-window-many-runtime-warning-messages
--
digikam version 5.3.0
CPU cores: 8
Eigen: 3.2.92
Exiv2: 0.25
Exiv2 can write to Jp2: Oui
Exiv2 can write to Jpeg: Oui
Exiv2 can write to Pgf: Oui
Exiv2 can write to Png: Oui
Exiv2 can write to Tiff: Oui
Exiv2 supports XMP metadata: Oui
KF5: 5.18.0
LensFun: 0.3.2-0
LibCImg: 130
LibJPEG: 80
LibJasper: 1.900.1
LibLCMS: 2060
LibLqr support: Yes
LibPGF: 7.15.32
LibPNG: 1.2.54
LibRaw: 0.18.0-Beta1
LibTIFF: LIBTIFF, Version 4.0.6 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble: 0.22.20 (0.23 development version)
Parallelized demosaicing: Oui
Qt: 5.5.1
AkonadiContact support: Oui
Calendar support: oui
DBus support: Oui
LibGphoto2: 2.5.9
LibKipi: 5.2.0
LibOpenCV: 2.4.9.1
Modules externes KIPI: 5.3.0
Moteur de base de données: QMYSQL
Panorama support: oui
Prise en charge de Baloo: Oui
QtMultimedia support: Oui
Serveur interne de base de données: Non
--

Display is 2x 1920x1080 screens.
Comment 5 e.longuemare 2016-11-20 15:01:05 UTC
This happened only once at start, then each time Digikam configuration manager is closed.

Try now with AppImage
Comment 6 e.longuemare 2016-11-20 15:22:26 UTC
Hello,

Just tryed with linked appImage : 

got some of messages :

digikam.general: User of DWItemDelegate should not delete widgets created by createItemWidgets!

But only on opening and closing Digikam configuration manager

Those have disappeared (was only on package Digikam startup):
0x42e3670 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1285d40) ): Attempt to set a screen on a child window.
Comment 7 caulier.gilles 2016-11-20 16:19:49 UTC
>digikam.general: User of DWItemDelegate should not delete widgets created by >createItemWidgets!

This are also present here and are relevant of a wrong parent passed in constructor somewhere in Collection widget from setup dialog. It's completely different than origina problem from Ubuntu.

So, as expected, your problem is an UPSTREAM dysfunction from Ubuntu. Please report this problem to Ubuntu team.

Note : the error come from Qt5, so the problem is certainly located in Qt5 package.

Gilles Caulier
Comment 8 e.longuemare 2016-11-20 17:15:42 UTC
Hello,

This has been reported here : https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009

Thanks,

Eric