[digikam] [Bug 372683] New: void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1285d40) ): Attempt to set a screen on a child window

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

            Bug ID: 372683
           Summary: void QWindowPrivate::setTopLevelScreen(QScreen*, bool)
                    ( QScreen(0x1285d40) ): Attempt to set a screen on a
                    child window
           Product: digikam
           Version: 5.3.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

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

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|Other                       |Ubuntu Packages
            Summary|void                        |Attempt to set a screen on
                   |QWindowPrivate::setTopLevel |a child window and
                   |Screen(QScreen*, bool) (    |DBusMenuExporterPrivate::fi
                   |QScreen(0x1285d40) ):       |llLayoutItem No id for
                   |Attempt to set a screen on  |action
                   |a child window              |

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from [hidden email] ---
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

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

--- Comment #2 from [hidden email] ---
Hello,

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

I'll check package list.

Thanks,

Eric

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

--- Comment #3 from [hidden email] ---
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

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

--- Comment #4 from [hidden email] ---
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.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

--- Comment #5 from [hidden email] ---
This happened only once at start, then each time Digikam configuration manager
is closed.

Try now with AppImage

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

--- Comment #6 from [hidden email] ---
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.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |UPSTREAM
             Status|UNCONFIRMED                 |RESOLVED
   Version Fixed In|                            |5.4.0

--- Comment #7 from [hidden email] ---
>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

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

--- Comment #8 from [hidden email] ---
Hello,

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

Thanks,

Eric

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Portability

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=372683

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Attempt to set a screen on  |Attempt to set a screen on
                   |a child window and          |a child window : No id for
                   |DBusMenuExporterPrivate::fi |action
                   |llLayoutItem No id for      |
                   |action                      |

--
You are receiving this mail because:
You are the assignee for the bug.