[kde] [Bug 480633] New: Crash in Baloo::DocumentDataDB::del() / mdb_node_search
https://bugs.kde.org/show_bug.cgi?id=480633 Bug ID: 480633 Summary: Crash in Baloo::DocumentDataDB::del() / mdb_node_search Classification: I don't know Product: kde Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: chith...@gentoo.org Target Milestone: --- Application: baloo_file_extractor (5.113.0) (Compiled from sources) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: Linux 6.6.13-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Baloo constantly crashes and restarts when trying to index files, I believe playlist files. The crash can be reproduced every time. -- Backtrace: Application: Baloo-Dateiinfosammler (baloo_file_extractor), signal: Bus error [KCrash Handler] #4 mdb_node_search (mc=mc@entry=0x7ffc3ed2a8e0, key=key@entry=0x7ffc3ed2acd0, exactp=exactp@entry=0x7ffc3ed2a7ec) at mdb.c:5367 #5 0x7fceb438f420 in mdb_page_search_root (mc=0x7ffc3ed2a8e0, key=0x7ffc3ed2acd0, flags=0) at mdb.c:5557 #6 0x7fceb438fdb5 in mdb_cursor_set (mc=mc@entry=0x7ffc3ed2a8e0, key=key@entry=0x7ffc3ed2acd0, data=data@entry=0x0, op=MDB_SET, exactp=exactp@entry=0x7ffc3ed2a8cc) at mdb.c:6175 #7 0x7fceb4396aa4 in mdb_del0 (txn=0x556363f389b0, dbi=10, key=0x7ffc3ed2acd0, data=, flags=32) at mdb.c:8611 #8 0x7fceb4bd2624 in Baloo::DocumentDataDB::del(unsigned long long) () from /usr/lib64/libKF5BalooEngine.so.5 #9 0x7fceb4bed95b in Baloo::WriteTransaction::removeDocument(unsigned long long) () from /usr/lib64/libKF5BalooEngine.so.5 #10 0x5563633653c4 in ?? () #11 0x556363366385 in ?? () #12 0x7fceb40cb3a2 in ?? () from /usr/lib64/libQt5Core.so.5 #13 0x7fceb40beeab in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x7fceb4093f28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #15 0x7fceb40e4e69 in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5 #16 0x7fceb40e5731 in ?? () from /usr/lib64/libQt5Core.so.5 #17 0x7fceb2f10e82 in ?? () from /usr/lib64/libglib-2.0.so.0 #18 0x7fceb2f14077 in ?? () from /usr/lib64/libglib-2.0.so.0 #19 0x7fceb2f1469c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #20 0x7fceb40e5ac6 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #21 0x7fceb409294b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #22 0x7fceb409accd in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #23 0x556363364440 in ?? () #24 0x7fceb3846f0a in ?? () from /lib64/libc.so.6 #25 0x7fceb3846fc5 in __libc_start_main () from /lib64/libc.so.6 #26 0x5563633644b1 in ?? () [Inferior 1 (process 12251) detached] Reported using DrKonqi This report was filed against 'kde' because the product 'frameworks-baloo' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426003] Implementing object detection
https://bugs.kde.org/show_bug.cgi?id=426003 --- Comment #7 from Thanh Trung Dinh --- Hi, As @markd said, it may be useful for users who want to search for images relating to 'sushi' or some specific objects, but in my opinion, the scope of this project needs to be reviewed carefully. Since YOLO is designed for object detection in general, there will be plenty of results for some trivial objects such as: table, spoon, banana, etc. Moreover, I've seen many cases where objects detected by YOLO are in the corners or not clearly visible. So, maybe an image tagged with sushi but it's far away from the view. Moreover, for specific objects (like sushi, plants, monuments, etc.) I suppose we need a YOLO version trained on specific datasets for those objects (or users may train the network themselves). Therefore, we really need to define clearly the objects that we aim to include in digikam for object detection. So the project is really interesting, but I would propose to create a poll from digikam users to get an idea on what object detection we want to support. Otherwise, a more extensible way but requiring some work from users is to design code templates for object detection (extending from facesengine). Then, users only need to train and provide the weights for the network to run the detection on their own. Best, Trung On Mon, Aug 31, 2020 at 12:43 AM markd wrote: > https://bugs.kde.org/show_bug.cgi?id=426003 > > --- Comment #6 from markd --- > Hi Nghia, > > Very happy to hear that you work on that topic. Sounds so great, thanks for > your hard work. > > As I am a Digikam User and a iphone user it would be great to have the > following use case. > > 1. Each picture run to the yolo model and get assign 0, 1 or more than 1 > object > > 2. If an object is wrong then the user can delete or update it (by update i > mean chosing 1 of the many existing object of the yolo model). But it > would be > very annoying that i have to verify if each predicted object is correct or > not!!! > > > With my iphone the use case is the following. > > I take a picture of something lets say a sushis. > > Then several days later i want to see all picture of sushi i took > So I go to the reseach bar and type 'sushi' then i see all the picture of > sushi. > > Would be great to have this feature. > > > In addition would be also great to have tags of each assigned object [like > for > people + manual tags], so there would be a category 'objects' with its > subcat > 'tree' 'sushi' etc then i could simply click on sushi to see all picture > of > sushis > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408589] Notification duplicates showing from SMS
https://bugs.kde.org/show_bug.cgi?id=408589 Thanh changed: What|Removed |Added CC||than...@vivaldi.net --- Comment #3 from Thanh --- Created attachment 120976 --> https://bugs.kde.org/attachment.cgi?id=120976=edit Media player duplicate notifications I'm also using KDE Neon 5.16, but I only get duplicate notifications with VLC media player. Others are normal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 Thanh changed: What|Removed |Added CC||than...@vivaldi.net --- Comment #9 from Thanh --- Created attachment 120955 --> https://bugs.kde.org/attachment.cgi?id=120955=edit (KSysGuard) kwin_wayland memory I can confirm this on KDE Neon 5.16. When I switched to Wayland session at login screen, kwin_wayland was running with a load of ~25% (KSysGuard) CPU and memory ram was increase, cursor was sluggish moving, GUI was sluggish responding. Here my machine info: SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.16 User Edition KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-21-generic Graphics: Card-1: Intel Skylake GT2 [HD Graphics 520] Card-2: NVIDIA GM108M [GeForce 930M] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1366x768@60.32hz OpenGL: renderer: GeForce 930M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.116 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406319] Hangs/freezes when drag windows to top, right or left edges of the screen
https://bugs.kde.org/show_bug.cgi?id=406319 --- Comment #10 from Thanh --- I followed this guide https://community.kde.org/KWin/Debugging, here is stacktrace: [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fb85f6859f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560b85a9b7c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 88 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory. (gdb) bt #0 0x7fb85f6859f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560b85a9b7c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb85f6859f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x560b85a9b770, cond=0x560b85a9b798) at pthread_cond_wait.c:502 #2 0x7fb85f6859f3 in __pthread_cond_wait (cond=0x560b85a9b798, mutex=0x560b85a9b770) at pthread_cond_wait.c:655 #3 0x7fb863a29b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb863a29e59 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb85e81411d in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fb85e816685 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fb85e816d09 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fb8641ceac5 in QWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7fb85e875285 in QQuickWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fb8649f183c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fb8649f8dd0 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fb863bfb328 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb8641c44ca in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7fb8641c471d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7fb86419d14b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7fb84ed326a3 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #17 0x7fb863bf964a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fb863c02800 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fb8669d2dbb in kdemain(int, char**) (argc=, argv=0x7fff0b9498e8) at ./main_x11.cpp:469 #20 0x7fb8665fab97 in __libc_start_main (main= 0x560b83e89720 , argc=1, argv=0x7fff0b9498e8, init=, fini=, rtld_fini=, stack_end=0x7fff0b9498d8) at ../csu/libc-start.c:310 #21 0x560b83e8975a in _start () (gdb) info thread Id Target Id Frame * 1Thread 0x7fb866d8a880 (LWP 1800) "kwin_x11" 0x7fb85f6859f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560b85a9b7c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 2Thread 0x7fb84e01f700 (LWP 1832) "QXcbEventQueue" 0x7fb8666edbf9 in __GI___poll (fds=0x7fb84e01ec38, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 3Thread 0x7fb847fff700 (LWP 1858) "QDBusConnection" 0x7fb8666edcf6 in __GI_ppoll (fds=0x7fb8400124a8, nfds=4, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 4Thread 0x7fb845287700 (LWP 1917) "QQmlThread" 0x7fb8666edcf6 in __GI_ppoll (fds=0x7fb83c000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 5Thread 0x7fb82700 (LWP 1921) "kwin_x11" 0x7fb85f6859f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fb862c39fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 6Thread 0x7fb837ddb700 (LWP 2110) "QSGRenderThread" 0x7fb8666edbf9 in __GI___poll (fds=0x7fb837dda6b0, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 7Thread 0x7fb834901700 (LWP 4135) "QQmlThread" 0x7fb8666edcf6 in __GI_ppoll (fds=0x7fb828001af8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 8Thread 0x7fb845ee7700 (LWP 4136) "QSGRenderThread" 0x7fb85f6859f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560b85dfb6b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 (gdb) thread 2 [Switching to thread 2 (Thread 0x7fb84e01f700 (LWP 1832))] #0 0x7fb8666edbf9 in __GI___poll (fds=0x7fb84e01ec38, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. (gdb) bt #0 0x7fb8666edbf9 in __GI___poll (fds=0x7fb84e01ec38, nfds=1, tim
[kwin] [Bug 406319] Hangs/freezes when drag windows to top, right or left edges of the screen
https://bugs.kde.org/show_bug.cgi?id=406319 --- Comment #6 from Thanh --- Update: - On my laptop (OpenGL renderer: NVIDIA), I cliked on System Settings > Display and Monitor > Compositor, change Rendering backend to "XRender", Log out and Log in again, the hang/freeze doesn't occur anymore. - Then, I tried changing Rendering backend to OpenGL 2.0 or OpenGL 3.1, then Log out and Log in, the hang/freeze happened again. Is it related to "Compositor Settings for Desktop Effects", "OpenGL" and "NVIDIA"? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 406319] New: Hangs/freezes when drag windows to top, right or left edges of the screen
https://bugs.kde.org/show_bug.cgi?id=406319 Bug ID: 406319 Summary: Hangs/freezes when drag windows to top, right or left edges of the screen Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: than...@vivaldi.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 119292 --> https://bugs.kde.org/attachment.cgi?id=119292=edit Animation (gif file) SUMMARY When I drag windows to top, right or left edges of the screen, these windows hangs/freezes (5-10s) then they are maximized or tiled. STEPS TO REPRODUCE 1. Open any application (like Firefox, KSysGuard...) 2. Drag any window to top, left or right edges of the screen 3. Window hangs/freezes (5-10s) then maximized or tiled. OBSERVED RESULT Window hangs/freezes (5-10s) then maximized or tiled. EXPECTED RESULT Drag any window to top, left or right edges of the screen without experiencing hangs/freezes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.15 User Edition KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-47-generic Graphics: Card-1: Intel Skylake GT2 [HD Graphics 520] Card-2: NVIDIA GM108M [GeForce 930M] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1366x768@60.32hz OpenGL: renderer: GeForce 930M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.116 ADDITIONAL INFORMATION I also experienced window hangs/freezes before (just randomly) but now is serious, it happened every time I drag window to edges of screen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373304] google picasa photo import
https://bugs.kde.org/show_bug.cgi?id=373304 --- Comment #4 from Thanh Trung Dinh --- Gilles, I didn't have enough time for this during GSoC 2018. However, this is a very promising features though, so I think that it should be on TODO list. There are just a few things making me consider and I mentioned one of them in the discussion about bug #383174. It is about APIs quota. As each time listing contents of an album, we will have to download thumbnails for all of them. So if someone has more than 1000 images in an album, we will run out of API calls easily. Besides, performance should be considered as a factor too, otherwise network will be overloaded with thumbnail download. Best, Thanh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383174] google photo, export stops after a random quantity of photos
https://bugs.kde.org/show_bug.cgi?id=383174 --- Comment #7 from Thanh Trung Dinh --- Gilles, I don't think that 2 bugs are about the same thing. This bug is about upload limit, which is 50 photos. I solved it by calling API several times if uploading more than 50 photos. Bug #396671 is about download limit, which is 100 by default (up to 500). So, I can try to solve that bug in the same way. However, there is a quota of 2500 API calls per day and that is what I am worried about. Solving these bugs leads to increase in API call and if the quota is exceeded, it will be impossible to use Goolge Photos APIs anymore, even those used for authentication and even from other users. Hence, these solutions above should be really considered. Best, Thanh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397126] fail to replace a photo in google photo
https://bugs.kde.org/show_bug.cgi?id=397126 --- Comment #3 from Thanh Trung Dinh --- Gilles, It's like what Maik mentioned. Google Photos API now still doesn't support this function. So I guess we cannot do anything here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 175327] Flickr import tool wishlist [patch]
https://bugs.kde.org/show_bug.cgi?id=175327 --- Comment #22 from Thanh Trung Dinh --- In my point of view, option 1 is better. It's true that our plan is uniting all web services to the new common wizard, and Flickr import will not be an exception. However, the core codes for import is method listPhotos(), which was written and tested (I think) by Anselmo. Since that method has API call inside (which is specific for each service as you already know), it will remain unchanged when we integrate Flickr import to the new wizard in the future. Moreover, the old patch posted here is for listPhotos(), so reviewing it in order to reuse and adapt it to new wizard will save time. Best, Thanh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 309508] Export to Flickr does not send the geodata
https://bugs.kde.org/show_bug.cgi?id=309508 Thanh Trung Dinh changed: What|Removed |Added Version Fixed In||6.0.0 Resolution|WAITINGFORINFO |FIXED --- Comment #10 from Thanh Trung Dinh --- Gilles, Sorry, I nearly forgot this entry. I have just made a patch for this bug, so it will be fixed from now on. Best, Thanh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387422] Flickr export authorization does not work
https://bugs.kde.org/show_bug.cgi?id=387422 --- Comment #5 from Thanh Trung Dinh --- Antonio, I cannot reproduce that. Is what you mean changing between 2 different accounts? Thanks, Thanh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383174] google photo, export stops after a random quantity of photos
https://bugs.kde.org/show_bug.cgi?id=383174 --- Comment #5 from Thanh Trung Dinh --- Hi, I found a way to work around. I don't have too many images to test, but I think that this bug will be fixed in 6.0.0. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383174] google photo, export stops after a random quantity of photos
https://bugs.kde.org/show_bug.cgi?id=383174 --- Comment #4 from Thanh Trung Dinh --- Hi, I think it's a problem of Google API quota. I will find a way to work around. Thanh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348274] "Change Account" immediately opens web page in browser, before I click Continue
https://bugs.kde.org/show_bug.cgi?id=348274 Thanh Trung Dinh changed: What|Removed |Added Version Fixed In||6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374476] Exporting to Google Photos changes File modified timestamp
https://bugs.kde.org/show_bug.cgi?id=374476 --- Comment #6 from Thanh Trung Dinh --- Gilles, I saw the same problem when I tried to export to Google Photo. I unintentionally discovered that timestamp is modified because at the final phase of exporting, the image id is written to the metadata. I think that if the XMP is load and then save again, timestamp will be modified to that moment. Could you confirm my theory? Best Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348275] Album combobox selection does not survive clicking Reload
https://bugs.kde.org/show_bug.cgi?id=348275 --- Comment #2 from Thanh Trung Dinh --- Gilles, I don't know if that is really a bug or not, since I observe the same thing in other tools (ex: smugmug, facebook, gphoto)? I think it's an intention that current album is always the newest one which has been created, (or the root). Best Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348274] "Change Account" immediately opens web page in browser, before I click Continue
https://bugs.kde.org/show_bug.cgi?id=348274 --- Comment #2 from Thanh Trung Dinh --- Gilles, No, this won't be still valid. Best Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348277] Please focus auth code input field in the GDrive authentication dialog
https://bugs.kde.org/show_bug.cgi?id=348277 --- Comment #2 from Thanh Trung Dinh --- Gilles, I think no, since we don't have to copy-paste code anymore. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386141] Export to Google Photos not responding
https://bugs.kde.org/show_bug.cgi?id=386141 --- Comment #5 from Thanh Trung Dinh --- Gilles, This might be something relating to the app bundle? Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376913] can't create a new album in picasa/googlephoto
https://bugs.kde.org/show_bug.cgi?id=376913 --- Comment #16 from Thanh Trung Dinh --- Gilles, The situation now is a little bit stranger when I port code from Picasa API v3 to Google Photos. So Available functions: - list album - list photos - create album - upload new images/videos to albums created by digiKam Not available functions: - upload images to ablums created on Google Photos - update images - delete images - comments, tags However, I don't know how new functions affect user with account on Picasa web. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368262] Google services tool does not use kaccounts
https://bugs.kde.org/show_bug.cgi?id=368262 --- Comment #5 from Thanh Trung Dinh --- Gilles, I think yes, because O2 always brings user to login page and it doesn't take care of account stored locally by any means. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374294] Be able to export photos from host application to the google photos pool
https://bugs.kde.org/show_bug.cgi?id=374294 --- Comment #2 from Thanh Trung Dinh --- Gilles, I don't have that many photos to test :-)). But I guess that it's still valid, and even more strict. Moreover, the problem is also about API quota. Google Photos API is still in version 1.0 so the quota must be much smaller. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395199] Uploading large video files to flickr fails [patch]
https://bugs.kde.org/show_bug.cgi?id=395199 Thanh Trung Dinh changed: What|Removed |Added Version Fixed In||6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373304] google picasa photo import
https://bugs.kde.org/show_bug.cgi?id=373304 --- Comment #2 from Thanh Trung Dinh --- Gilles, Yes, it's still valid. I will work on it for the factorization codes. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373678] Videos exported in google photos are not available (still processing state)
https://bugs.kde.org/show_bug.cgi?id=373678 --- Comment #3 from Thanh Trung Dinh --- Gilles, I have just tested uploading videos to my account and it worked without errors. However, those should be exported to an album created on Google Photos by digiKam, or to main page of user account (not belonging to any albums), otherwise it won't work. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395199] Uploading large video files to flickr fails [patch]
https://bugs.kde.org/show_bug.cgi?id=395199 --- Comment #8 from Thanh Trung Dinh --- Gilles, Yes, I saw it. I'm writing an answer with as most details as possible so that you can decide. About "this file can be closed with "Version Fixed set to 6.0.0" and NEWS file patched with this entry title", I'm not really sure about what you mean? So I will make change in NEWS file and mark that this bug has been solved? Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385363] Digikam crashes when authorizing access to Google photo because of SSL error in AppImage
https://bugs.kde.org/show_bug.cgi?id=385363 --- Comment #36 from Thanh Trung Dinh --- Gilles, I'm not sure about this, since I cannot reproduce this on arch linux. So, I guess we should wait for confirmation from user. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387422] Flickr export authorization does not work
https://bugs.kde.org/show_bug.cgi?id=387422 --- Comment #3 from Thanh Trung Dinh --- Gilles, I'm not sure if I reproduced the bug that @Karl might encounter, but here is what I found : right-click on an album -> export to Flickr will now bring me to Login page of Flickr, Login and "I'll authorize" will take me to blank page (which is normal, since O2 captures redirect Url to extract access token). However, the album won't appear automatically in export window as I expected. So, I think that if it's is reproducible, it should be resolved in the next phase when I will work on factorization code. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395199] Uploading large video files to flickr fails [patch]
https://bugs.kde.org/show_bug.cgi?id=395199 --- Comment #5 from Thanh Trung Dinh --- Gilles, I applied this patch. I have committed it to gsoc2018-exporttools-o2. Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395199] Uploading large video files to flickr fails
https://bugs.kde.org/show_bug.cgi?id=395199 --- Comment #2 from Thanh Trung Dinh --- @jgoerzen Thank you for the patch! @Gilles I will commit this patch to gsoc18-exporttools-o2 branch? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 182838] Facebook tool does not work any more
https://bugs.kde.org/show_bug.cgi?id=182838 --- Comment #18 from Thanh Trung Dinh --- Gilles, Yes, I can confirm that. Best, Thanh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363859] digiKam core port from QWebKit to QWebEngine [patch]
https://bugs.kde.org/show_bug.cgi?id=363859 --- Comment #34 from Thanh Trung Dinh <dinhthanhtrung1...@gmail.com> --- Created attachment 87 --> https://bugs.kde.org/attachment.cgi?id=87=edit portWebEngine_patch Hi Maik, I have created a new patch by shrinking the previous one. In this patch: 1/ I keep the WelcomePageViewPage class as we had discussed. 2/ I didn't modify much the backend-googlemaps-js.js. I kept the 2 js functions used for sending message to old QWebView via status bar, so that this file is still compatible with old QWebView. I added the console.log(...) at the end so that there is no problem either with QWebEngineView. 3/ I understood that if all js functions had a return, we would be able to use only runScript() (in which we would add QEventLoop) as we had used in the old QWebView, and that would help to shrink the patch. However, all functions would become synchronous and we might have worse performance. So, I worked around by using a boolean variable (async) and an "if-else" to turn what we had before (setToScript() and getFromScript()) into one function runScript() and shrink the patch. Besides, it seemed to me that map works much slower with QWebEngineView than with QWebView, didn't it? Thanh. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363859] digiKam core port from QWebKit to QWebEngine [patch]
https://bugs.kde.org/show_bug.cgi?id=363859 --- Comment #32 from Thanh Trung Dinh <dinhthanhtrung1...@gmail.com> --- Maik, About your first point that WelcomePageViewPage class should be deleted, that was right since we can access by QWebEngineView::page(). However, I found that the class was created in order to overload method QWebEnginePage::acceptNavigationRequest(const QUrl &, NavigationType , bool ), so that when a link on the welcome page is clicked, it will open a browser for that link. Since QWebEngineView doesn't support any signal to capture an event linkClicked as QWebView did, overloading that method is the best way to work around. Besides, if we don't open link in another browser, I don't know how to return to welcome page except closing and reopening application. So, I guess we should keep that class? Thanh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363859] digiKam core port from QWebKit to QWebEngine [patch]
https://bugs.kde.org/show_bug.cgi?id=363859 --- Comment #30 from Thanh Trung Dinh <dinhthanhtrung1...@gmail.com> --- Maik, I saw the lines that used QEventLoop to wait for return from JavaScript functions. But as you said that " we should implement it more elegantly ", I don't really understand your idea. So I thought of 2 options: 1/ We should find another way to implement the waiting loop instead of using QEventLoop. If so, what were the disadvantages of using QEventLoop? 2/ We should find a way to replace the lambda function there so that the codes are more readable. Thanh-Trung Dinh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363859] digiKam core port from QWebKit to QWebEngine [patch]
https://bugs.kde.org/show_bug.cgi?id=363859 Thanh Trung Dinh <dinhthanhtrung1...@gmail.com> changed: What|Removed |Added CC||dinhthanhtrung1...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380360] New: Plasmashell crashes after update to kde plasma 5.10
https://bugs.kde.org/show_bug.cgi?id=380360 Bug ID: 380360 Summary: Plasmashell crashes after update to kde plasma 5.10 Product: plasmashell Version: 5.10.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: darklord.h...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.0) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.12.0-041200rc3-generic x86_64 Distribution: Linux Mint 18.1 Serena -- Information about the crash: - What I was doing when the application crashed: If I open any application plasmashell will be stopped. It happens just after I update from kde 5.9.5 to 5.10 with repo: deb http://archive.neon.kde.org/user xenial main My distro: Linux Mint 18.1 KDE Edtition The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8a4cb198c0 (LWP 8377))] Thread 9 (Thread 0x7f8983414700 (LWP 8704)): #0 0x7f8a42c43a94 in g_mutex_unlock (mutex=0x7f8974000990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gthread-posix.c:1347 #1 0x7f8a42bfe9a0 in g_main_context_prepare (context=context@entry=0x7f8974000990, priority=priority@entry=0x7f8983413bc0) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3507 #2 0x7f8a42bff2bb in g_main_context_iterate (context=context@entry=0x7f8974000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3820 #3 0x7f8a42bff49c in g_main_context_iteration (context=0x7f8974000990, may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f8a47d8f75b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8a47d3a0ba in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8a47b69f64 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8a47b6eb48 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8a46a0c6ba in start_thread (arg=0x7f8983414700) at pthread_create.c:333 #9 0x7f8a4747382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f8983c15700 (LWP 8703)): #0 0x7f8a47467b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8a42bff38c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f897c0013c0, timeout=, context=0x7f897c000990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135 #2 0x7f8a42bff38c in g_main_context_iterate (context=context@entry=0x7f897c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f8a42bff49c in g_main_context_iteration (context=0x7f897c000990, may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f8a47d8f75b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8a47d3a0ba in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8a47b69f64 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f89882cc975 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #8 0x7f8a47b6eb48 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f8a46a0c6ba in start_thread (arg=0x7f8983c15700) at pthread_create.c:333 #10 0x7f8a4747382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f8988d0f700 (LWP 8695)): #0 0x7f8a42c43a79 in g_mutex_lock (mutex=mutex@entry=0x7f8984000990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gthread-posix.c:1335 #1 0x7f8a42bff372 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f89840048c0, timeout=, context=0x7f8984000990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4130 #2 0x7f8a42bff372 in g_main_context_iterate (context=context@entry=0x7f8984000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f8a42bff49c in g_main_context_iteration (context=0x7f8984000990, may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f8a47d8f75b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8a47d3a0ba in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8a47b69f64 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f898b1ed587 in KCupsConnection::run() () at
