[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-08-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405519

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
   Version Fixed In||6.3.0

--- Comment #14 from Maik Qualmann  ---
Thanks for the feedback, I close the bug, if necessary reopen it.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-08-10 Thread Kristian
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #13 from Kristian  ---
Sorry, I never commented this bug again, but it's gone since one of the last
versions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-04-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #12 from caulier.gil...@gmail.com ---
Ok thanks for the feedback.

There is 2 appimage 6.1.0 bundles to test : one using qtwebkit, and one other
with QtWebEngine.

QtWebKit will be used to release next 6.1.0 officially. QtWebEngine is for the
future version.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-04-01 Thread Kristian
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #11 from Kristian  ---
I didn't have much time, so I just made a quick check:

digikam currently crashes when I open Geolocation Editor, no matter if I add 
export QT_XCB_FORCE_SOFTWARE_OPENGL=1 first or not.

[..]
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options
QFlags(), depthBufferSize 24, redBufferSize -1,
greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8,
samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::NoProfile) 
Received signal 6
#0 0x7f43ae041e0e 
#1 0x7f43ae03efc3 
#2 0x7f43ae041d85 
#3 0x7f43b9447e00 
#4 0x7f43b9447d7f __GI_raise
#5 0x7f43b9432672 __GI_abort
#6 0x7f43b9a297fc QMessageLogger::fatal()
#7 0x7f43aa3cd036 
#8 0x7f43aa3cd374 
#9 0x7f43aa3cf5b6 QQuickWidget::resizeEvent()
#10 0x7f43b93205ce 
#11 0x7f43ba62a63e QWidget::event()
#12 0x7f43aa3d029e QQuickWidget::event()
#13 0x7f43b9320951 
#14 0x7f43ba5e8e24 QApplicationPrivate::notify_helper()
#15 0x7f43ba5f05f1 QApplication::notify()
#16 0x7f43b9c1fdf9 QCoreApplication::notifyInternal2()
#17 0x7f43ba622430 QWidgetPrivate::sendPendingMoveAndResizeEvents()
#18 0x7f43ba626464 QWidgetPrivate::show_helper()
#19 0x7f43ba62640c QWidgetPrivate::showChildren()
#20 0x7f43ba626482 QWidgetPrivate::show_helper()
#21 0x7f43ba629775 QWidgetPrivate::setVisible()
#22 0x7f43ba626421 QWidgetPrivate::showChildren()
#23 0x7f43ba626482 QWidgetPrivate::show_helper()
#24 0x7f43ba629775 QWidgetPrivate::setVisible()
#25 0x7f43ba60cdf6 QStackedLayout::setCurrentIndex()
#26 0x7f43bb9a06f9 Digikam::MapWidget::slotBackendReadyChanged()
#27 0x7f43b9c4a980 QMetaObject::activate()
#28 0x7f43bb9aa3e3 
#29 0x7f43bb973f00 
#30 0x7f43bb9abc2e 
#31 0x7f43b9c4a82c QMetaObject::activate()
#32 0x7f43bb9a74bb 
#33 0x7f43bb9abf5d 
#34 0x7f43b9c4a82c QMetaObject::activate()
#35 0x7f43b931d953 QWebEngineView::loadFinished()
#36 0x7f43b9c4a980 QMetaObject::activate()
#37 0x7f43b930c8a3 QWebEnginePage::loadFinished()
#38 0x7f43b9c56b07 
#39 0x7f43b9c4b0bb QObject::event()
#40 0x7f43ba5e8e24 QApplicationPrivate::notify_helper()
#41 0x7f43ba5f05f1 QApplication::notify()
#42 0x7f43b9c1fdf9 QCoreApplication::notifyInternal2()
#43 0x7f43b9c75045 QTimerInfoList::activateTimers()
#44 0x7f43b9c758d2 
#45 0x7f43aa91e7bf g_main_context_dispatch
#46 0x7f43aa920739 
#47 0x7f43aa92077e g_main_context_iteration
#48 0x7f43b9c75c99 QEventDispatcherGlib::processEvents()
#49 0x7f43b9c1ea8c QEventLoop::exec()
#50 0x7f43ba7e19be QDialog::exec()
#51 0x7f43bc2f2c6d Digikam::DigikamApp::slotEditGeolocation()
#52 0x7f43bc3b4e6b 
#53 0x7f43b9c4a82c QMetaObject::activate()
#54 0x7f43ba5e2633 QAction::triggered()
#55 0x7f43ba5e4d1a QAction::activate()
#56 0x7f43ba5e5625 QAction::event()
#57 0x7f43ba5e8e24 QApplicationPrivate::notify_helper()
#58 0x7f43ba5f05f1 QApplication::notify()
#59 0x7f43b9c1fdf9 QCoreApplication::notifyInternal2()
#60 0x7f43ba01dee0 QShortcutMap::dispatchEvent()
#61 0x7f43ba01dfc3 QShortcutMap::tryShortcut()
  r8:   r9: 7ffe95d39000 r10: 0008 r11:
0246
 r12: 7ffe95d39348 r13: 56233686c4e0 r14: 0001 r15:
7ffe95d39950
  di: 0002  si: 7ffe95d39000  bp: 56233686c4e0  bx:
0006
  dx:   ax:   cx: 7f43b9447d7f  sp:
7ffe95d39000
  ip: 7f43b9447d7f efl: 0246 cgf: 002b0033 erf:

 trp:  msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Will try the AppImage in the next days.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #10 from caulier.gil...@gmail.com ---
Kristian,

Please try to disable all opengl features in QtWebEngine with is command line :

export QT_XCB_FORCE_SOFTWARE_OPENGL=1

... before to run digiKam. This must fix your problem.

You can try also the special AppImage bundle for digiKam 6.1.0 pre release
compiled with QtWebEngine and available here :

https://files.kde.org/digikam/

Current file is digikam-6.1.0-git-20190331T162849-qtwebengine-x86-64.appimage

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #9 from caulier.gil...@gmail.com ---
I start to become crazy, with Qt web component :

Look here :

https://github.com/qt/qtwebengine/blob/5.12/configure.pri#L87

QtWebEngine require at least Glibc 2.17. CentOS 6.x is frozen to Glibc 2.12.
Updateing to more recent Glibc will require to rebuild the whole system. I will
never do that.

This want mean that we will to use CentOS 7 when we want to switch to
QWebEngine.

I solved the QtWebKit huge memory allocation while compiling. This is now
stabilized to 1 Gb to max.

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #8 from Maik Qualmann  ---
The poor quality of Nouveau and due to the quite frequent kernel updates on
openSUSE Tumbleweed and recompilation of the proprietary NVIDIA driver, I
switched to AMD.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #7 from caulier.gil...@gmail.com ---
Maik,

It work, even if i can see these kernel warnings on the console :

digikam.geoiface: 
digikam.geoiface: located data:
QUrl("file:///usr/local/share/digikam/geoiface/backend-googlemaps.html")
digikam.geoiface: Maps Loading Progress:  10 %
digikam.geoiface: Maps Loading Progress:  70 %
digikam.geoiface: Maps Loading Progress:  90 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Map Loading Completed:  true
digikam.geoiface: "SATELLITE"
digikam.geoiface: "backend googlemaps is ready!"
digikam.geoiface: "googlemaps:17"
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: "(event)MTSATELLITE"
digikam.geoiface: "(event)ZC"
digikam.geoiface: Maps Loading Progress:  10 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Maps Loading Progress:  10 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: "(event)id"
digikam.geoiface: "created cluster 0: 1 tiles"
digikam.geoiface: "level 7: 1 non empty tiles sorted into 1 clusters (1
searched)"
digikam.geoiface: start updateclusters
digikam.geoiface: end updateclusters
digikam.geoiface: QVariant(QPersistentModelIndex,
QModelIndex(0,0,0x397fb00,QStandardItemModel(0x24c7590))) QSize(44, 58)
nouveau: kernel rejected pushbuf: Aucun fichier ou dossier de ce type
nouveau: ch13: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch13: buf  0002 0004 0004 
nouveau: kernel rejected pushbuf: Aucun fichier ou dossier de ce type
nouveau: ch13: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch13: buf  0004 0004 0004 
nouveau: ch13: buf 0001 0006 0004  0004
digikam.geoiface: "(event)id"
digikam.geoiface: "created cluster 0: 1 tiles"
digikam.geoiface: "level 7: 1 non empty tiles sorted into 1 clusters (1
searched)"
digikam.geoiface: start updateclusters
digikam.geoiface: end updateclusters
digikam.geoiface: "(event)id"
digikam.geoiface: "created cluster 0: 1 tiles"
digikam.geoiface: "level 7: 1 non empty tiles sorted into 1 clusters (1
searched)"
digikam.geoiface: start updateclusters
digikam.geoiface: end updateclusters

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread Kristian
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #6 from Kristian  ---
I'm using NVIDIA with proprietary driver on Arch Linux (extra/nvidia-340xx
340.107-68).

$ glxinfo | grep -i "vendor\|rendering"
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
client glx vendor string: NVIDIA Corporation
OpenGL vendor string: NVIDIA Corporation
GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 
GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 

$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [NVS 3100M] (rev
a2)

$ lsmod | grep "kms\|drm"
drm   499712  3 nvidia
agpgart53248  3 intel_agp,intel_gtt,drm

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #5 from caulier.gil...@gmail.com ---
NVIDIA with Nouveau driver from Mageia 6.1.

[gilles@localhost 6.x]$ glxinfo | grep -i "vendor\|rendering"
direct rendering: Yes
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
Vendor: nouveau (0x10de)
OpenGL vendor string: nouveau
[gilles@localhost 6.x]$ grep LoadModule /var/log/Xorg.0.log
[28.273] (II) LoadModule: "v4l"
[28.274] (II) LoadModule: "glx"
[28.276] (II) LoadModule: "nouveau"
[28.278] (II) LoadModule: "dri2"
[28.429] (II) LoadModule: "fb"
[28.430] (II) LoadModule: "shadowfb"
[28.479] (II) LoadModule: "exa"
[28.715] (II) LoadModule: "libinput"

[gilles@localhost 6.x]$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750
Ti] (rev a2)
[root@localhost 6.x]# lsmod | grep "kms\|drm"
drm_kms_helper135168  2 nouveau,i915
drm   335872  15 nouveau,i915,ttm,drm_kms_helper

I will test your patch tomorrow morning.

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #4 from Maik Qualmann  ---
Gilles, if you have time, please test.

https://commits.kde.org/digikam/d469c6d8e1868fb7492d6ebd69c167a66838a64a

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #3 from Maik Qualmann  ---
Ok, that's interesting. NVIDIA with proprietary driver? I only use QWebEngine
and absolute no problems at all. I had crashes with NVIDIA only with the
Nouveau drivers. Meanwhile, I am using an AMD graphics card with the Open
Source Radeon drivers.

We can disable some hardware acceleration also OpenGL.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405519

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #2 from caulier.gil...@gmail.com ---
Maik,

I can also confirm this problem with QWebEngine on my native Linux with NVIDIA
card and OpenGL support.

I never use QWebEngine here, it crash since a very long time. Ths is why
QtWebkit support is important : this one never crash here...

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405519

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
This is a packages problem. DigiKam is compiled with QWebEngine support. The
hardware accelerated output over OpenGL does not work for you. Is your desktop
OpenGL capable? Presumably, e.g. KMail also have a problem.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.