[digikam] [Bug 433766] New: Flickr export does not work (7.1.0 appimage)
https://bugs.kde.org/show_bug.cgi?id=433766 Bug ID: 433766 Summary: Flickr export does not work (7.1.0 appimage) Product: digikam Version: 7.1.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Plugin-WebService-Flickr Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- Created attachment 136268 --> https://bugs.kde.org/attachment.cgi?id=136268=edit error SUMMARY Flickr export does not work (7.1.0 appimage) STEPS TO REPRODUCE 1. Select export to flickr 2. In 'Choose the flickr account to use for exporting images', dropdown is blank, so I select 'Add another account' 3. A popup error immediately appears (see below) OBSERVED RESULT This site can’t be reachedThe webpage at https://www.flickr.com/services/oauth/authorize?perms=write_token=7215771847137-a154f3e0addabb35_callback=https://www.flickr.com might be temporarily down or it may have moved permanently to a new web address. ERR_CERT_AUTHORITY_INVALID EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430995] No video preview or thumbnails for any video content
https://bugs.kde.org/show_bug.cgi?id=430995 --- Comment #4 from Rob Brown --- Thank you Gilles for the information. I shall try it now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430995] No video preview or thumbnails for any video content
https://bugs.kde.org/show_bug.cgi?id=430995 --- Comment #2 from Rob Brown --- Thank you, I think I will try the appimage method instead. Question: If I uninstall the snap, then install the appimage, are my digikam application settings transferable to the appimage installation? ie are the application setting stored in the library, or somewhere else so that I may transfer them? Thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430995] New: No video preview or thumbnails for any video content
https://bugs.kde.org/show_bug.cgi?id=430995 Bug ID: 430995 Summary: No video preview or thumbnails for any video content Product: digikam Version: 7.1.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Preview-Video Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- Created attachment 134410 --> https://bugs.kde.org/attachment.cgi?id=134410=edit no thumbnails SUMMARY No video preview or thumbnails for any video content STEPS TO REPRODUCE Look at video in library (thumbnail view). OBSERVED RESULT Preview shows no thumbnail. When double clicking on each video, nothing happens. No video is shown, and no application is launched. EXPECTED RESULT Thumbnails and previews for common video types (mov, avi, mp4 etc...) SOFTWARE/OS VERSIONS Linux version: Zorin 15.3 (Ubuntu 18.04) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430918] New: digikam application crashes when importing images into a new empty library
https://bugs.kde.org/show_bug.cgi?id=430918 Bug ID: 430918 Summary: digikam application crashes when importing images into a new empty library Product: dolphin Version: 20.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.0) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.4.0-58-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: 1. Created new digikam library. 2. Pointed digikam at a folder under my home/user directory. This folder happens to be a ZFS file system (https://zfsonlinux.org/). Underneath each folder are separate folders roughly 2000 images per folder. Each one contains image types of raw, jpeg, xmp, tif, png 3. After initial import was working for about 5 mins, digikam crashed. 4. I keep trying to relaunch digikam, including restarting my computer, but digikam crashes again after just a few seconds The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [New LWP 24610] [New LWP 24611] [New LWP 24612] [New LWP 24613] [New LWP 24614] [New LWP 24615] [New LWP 24616] [New LWP 24622] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f4157b8daff in __GI___poll (fds=0x7ffe674bc928, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f4150c408c0 (LWP 24608))] Thread 9 (Thread 0x7f413a168700 (LWP 24622)): #0 __GI___libc_read (nbytes=16, buf=0x7f413a167ad0, fd=23) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=23, buf=0x7f413a167ad0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f415368e89f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4153645cfe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4153646152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f41536462e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f41558d4fbb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f41558791ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4155693a12 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f4155694bac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f4154013609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f4157b9a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f414517e700 (LWP 24616)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561ca2ef23f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561ca2ef23a8, cond=0x561ca2ef23d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561ca2ef23d0, mutex=0x561ca2ef23a8) at pthread_cond_wait.c:638 #3 0x7f4146dfe62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f4146dfe23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f4154013609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f4157b9a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f414597f700 (LWP 24615)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561ca2ef23f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561ca2ef23a8, cond=0x561ca2ef23d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561ca2ef23d0, mutex=0x561ca2ef23a8) at pthread_cond_wait.c:638 #3 0x7f4146dfe62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f4146dfe23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f4154013609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f4157b9a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f4146180700 (LWP 24614)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561ca2ef23f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561ca2ef23a8, cond=0x561ca2ef23d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561ca2ef23d0, mutex=0x561ca2ef23a8) at pthread_cond_wait.c:638 #3 0x7f4146dfe62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f4146dfe23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f4154013609 in start_thread (arg=) at
[digikam] [Bug 426659] thumbnails for tagged faces not useful
https://bugs.kde.org/show_bug.cgi?id=426659 --- Comment #2 from Rob Brown --- Have you asked all the users? I completely disagree with you. In other applications with such functionality the thumbnails for a given 'face' show the whole photo so the user can understand WHICH photo they are clicking on before they click on it. Having 500+ photos of the cropped face of a person is really quite useless in order to get to the right photo. I already clicked on person A. If I click on person A and see 500 pictures of their face, how do I know which one was them at the beach, vs the party (which I was looking for)? If I have to click on each one to find it, that really defeats the object of a faces feature. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426664] Cannot tell different between an opened or closed group of images
https://bugs.kde.org/show_bug.cgi?id=426664 --- Comment #4 from Rob Brown --- The red indicator is highlighting (an edit was made after the screenshot was made) that there's a distinct visual difference between an open stack and a closed stack. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426664] Cannot tell different between an opened or closed group of images
https://bugs.kde.org/show_bug.cgi?id=426664 --- Comment #1 from Rob Brown --- See www.lifeafterphotoshop.com/wp-content/uploads/2014/01/organise-07.jpg for example of how lightroom shows open stacks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426664] New: Cannot tell different between an opened or closed group of images
https://bugs.kde.org/show_bug.cgi?id=426664 Bug ID: 426664 Summary: Cannot tell different between an opened or closed group of images Product: digikam Version: 7.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-IconView Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- Created attachment 131738 --> https://bugs.kde.org/attachment.cgi?id=131738=edit Attaching a pic of my library. Spot the open stack? I can't SUMMARY In the Thumbnails view, when I have a group of images (e.g. I group by time or filename to group JPG and RAW), it is extremely difficult to understand whether I opened the stack of images, or which ones belong to the group when a group is opened. STEPS TO REPRODUCE 1. Click on a grouped set of images using the folder icon 2. Group opens up OBSERVED RESULT Difficult to tell if it is open or closed. Attaching a pic of my library. Spot the open stack? I can't EXPECTED RESULT Would be nice to have a thick bounding box around the opened stack Also, the presentation of the 'stacked' images is quite ugly and 2000 looking. Can that look more like a neat stack as opposed to a messy pile of prints on a coffee table?? Attaching a pic of Lightroom (found on the web). - An open stack has very clear representation that differs it to a closed stack. - A closed stack has more obvious iconography than digikam SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426662] File naming - extension aware does not work?
https://bugs.kde.org/show_bug.cgi?id=426662 --- Comment #1 from Rob Brown --- Related to https://bugs.kde.org/show_bug.cgi?id=246938 ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426662] New: File naming - extension aware does not work?
https://bugs.kde.org/show_bug.cgi?id=426662 Bug ID: 426662 Summary: File naming - extension aware does not work? Product: digikam Version: 7.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Files Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- SUMMARY My expectation of 'extension aware' file numbering would be that when selected, if I have a RAW and JPEG pair of files, each file would get the same numeric sequence. When I check this option, instead each file is given a new number. Is this the expected result? STEPS TO REPRODUCE 1. Select a number of images. Go to Item >> rename 2. Enter the format of name in my case I started with a date, then wanted to put a number after it 3. Press Number... 4. Select Extension Aware Naming, press OK 5. The format of the name for batch looks something like: [date:"MMdd_"]###[e] where the [e} is supposed to represent extension aware. OBSERVED RESULT A pair of RAW+JPEG (same image, different file type) has a DIFFERENT unique name. e.g. 20200810_012.RAF 20200810_013.JPG EXPECTED RESULT Files of same image, different type should be like this: 20200810_012.RAF 20200810_012.JPG SOFTWARE/OS VERSIONS Linux: 7.1.0 Flatpak (ubuntu) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 246938] Extension aware rename (maintain raw file and jpg association by basename)
https://bugs.kde.org/show_bug.cgi?id=246938 Rob Brown changed: What|Removed |Added CC||brownphotograp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426659] New: thumbnails for tagged faces not useful
https://bugs.kde.org/show_bug.cgi?id=426659 Bug ID: 426659 Summary: thumbnails for tagged faces not useful Product: digikam Version: 7.1.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- SUMMARY The faces feature works well, but is let down by the resulting presentation of the tagged faces. When viewing a person, I expect to see a thumbnail of the whole picture; instead I see a thumbnail of the face crop (blown up. This is really not very useful to the user and not how other applications work with this functionality. Tagged faces should be a shortcut method of finding photos of a person. The current result doesn't let the user understand which photo they were looking for. EXPECTED RESULT Feature suggestion: show the thumbnail as the full uncropped photo. ADDITIONAL INFORMATION Running 7.1.0 on Linux (ubuntu) via Flatpak -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424553] New: Authenticating to flickr does not work
https://bugs.kde.org/show_bug.cgi?id=424553 Bug ID: 424553 Summary: Authenticating to flickr does not work Product: digikam Version: 6.4.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Plugin-WebService-Flickr Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- Created attachment 130326 --> https://bugs.kde.org/attachment.cgi?id=130326=edit screenshot of error SUMMARY Authenticating to flickr fails for digikam STEPS TO REPRODUCE 1. Export menu >> Export to Flickr 2. Add another account 3. Flickr Launches, I click 'ok I'll authorize' 4. flickr fails OBSERVED RESULT I get following error message: Secure Connection Failed An error occurred during a connection to 127.0.0.1:1965. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. EXPECTED RESULT After authorizing, I should be sent back to digikam and account is added. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-26-generic OS Type: 64-bit Processors: 16 × Intel® Xeon® CPU E5520 @ 2.27GHz Memory: 11.7 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 381620] Is not authenticating user
https://bugs.kde.org/show_bug.cgi?id=381620 Rob Brown changed: What|Removed |Added CC||brownphotograp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424501] Right click >> Open in File Manager does not work
https://bugs.kde.org/show_bug.cgi?id=424501 --- Comment #6 from Rob Brown --- Ok, the issue lies with the OS. I tried kubuntu 20.04 with the stable digikam 6.4 release and it works fine. I suggest to close this and mark this down to issue with a particular distribution (Zorin). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424501] Right click >> Open in File Manager does not work
https://bugs.kde.org/show_bug.cgi?id=424501 --- Comment #4 from Rob Brown --- Tried installing the 7.0.0-rc release via software store (flathub). it will not launch. I cannot figure out how to install via that link sent. I'd rather figure out what is going on with the stable 6.4.0 version. Is there a way of forcing it to use the file manager? My OS is ubuntu based (Zorin). I'm using the default file explorer that comes with OS. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424501] New: Right click >> Open in File Manager does not work
https://bugs.kde.org/show_bug.cgi?id=424501 Bug ID: 424501 Summary: Right click >> Open in File Manager does not work Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Files Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- SUMMARY When I try to use the right click option to 'Open in File Manager', nothing happens. STEPS TO REPRODUCE 1. On an image, right click and select 'Open in File Manager' OBSERVED RESULT (Application does nothing, no feedback that this operation failed. System file manager does not open) EXPECTED RESULT Open file manager, highlight selected file. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 410962] kdiff3 vs svn (subversion)
https://bugs.kde.org/show_bug.cgi?id=410962 --- Comment #6 from Rob Brown --- I cloned and built. The resulting executable properly handles the -L options. Looks good. I'll look forward to this getting into the next release. Thanks. - - - Some off-topic observations: 1. The INSTALL file says "cmake && make". This didn't work for me. I eventually found that "cmake . && make" worked. 2. I have no idea if this is expected, or if it is my environment, but the "cmake . && make" command produced 1681 lines of output, including 218 warnings (apparently 1 from cmake and 217 from make) and 214 "... is deprecated". -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 410962] New: kdiff3 vs svn (subversion)
https://bugs.kde.org/show_bug.cgi?id=410962 Bug ID: 410962 Summary: kdiff3 vs svn (subversion) Product: kdiff3 Version: 1.7.90 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: br...@gmcl.com Target Milestone: --- SUMMARY The command line sent to kdiff3 by svn used to work. Now it doesn't. The command line from svn is apparently: kdiff3 -u -L "filename (revision n)" -L "filename (revision m)" /tmp/svn-mumble /tmp/svn-mumble STEPS TO REPRODUCE 1. create or find some useful text file for testing, such as fox.txt 2. in the shell, type kdiff3 -u -L "Left" -L "Right" fox.txt fox.txt OBSERVED RESULT From 1.7.90, a three-way diff of Left, Right, and fox.txt, and complaints that it cannot open Left and Right. From 1.8.1, a Severe Internal Error: "Data loss error: If is it reproducible please contact the author." EXPECTED RESULT a two-way diff of fox.txt and fox.txt, the two files labelled "Left" and "Right" (naturally showing no differences). This is what we saw with kdiff3 0.9.98. SOFTWARE/OS VERSIONS Kubuntu 19.04, which has 1.7.90. Also loaded the 1.8.1 package from Kubuntu 19.10. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356787] New: Akonadi crash soon after login
https://bugs.kde.org/show_bug.cgi?id=356787 Bug ID: 356787 Summary: Akonadi crash soon after login Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: br...@gmcl.com Application: akonadi_kalarm_resource (4.89.0) Qt Version: 5.4.2 Operating System: Linux 4.2.0-19-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Yakuake and two PuTTY sessions open. Typing in one PuTTY session, command line editing "^H r-arrow r-arrow rarrow" when crash info appeared. -- Backtrace: Application: Akonadi Resource (akonadi_kalarm_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8cba67a840 (LWP 4355))] Thread 2 (Thread 0x7f8cb8257700 (LWP 4360)): #0 0x7f8cca50e8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f8cc27edbd2 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f8cc27ef74f in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f8cba1ada39 in QXcbEventReader::run() (this=0x24a0e50) at qxcbconnection.cpp:1105 #4 0x7f8ccae182be in QThreadPrivate::start(void*) (arg=0x24a0e50) at thread/qthread_unix.cpp:337 #5 0x7f8cc56646aa in start_thread (arg=0x7f8cb8257700) at pthread_create.c:333 #6 0x7f8cca519eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f8cba67a840 (LWP 4355)): [KCrash Handler] #6 0x0041f257 in KAlarmResource::writeToFile(QString const&) () #7 0x00414861 in Akonadi::SingleFileResource::writeFile(bool) () #8 0x7f8ccd7a754d in () at /usr/lib/x86_64-linux-gnu/libakonadi-singlefileresource.so.5 #9 0x7f8ccb002c02 in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const (this=this@entry=0x7ffd3e28ccb8, object=object@entry=0x24dd3d0, connectionType=Qt::DirectConnection, connectionType@entry=1042861376, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:2183 #10 0x7f8ccb007d2d in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) (obj=0x24dd3d0, member=0x2586538 "writeFile", type=1042861376, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1478 #11 0x7f8ccd56eae1 in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5 #12 0x7f8ccd56f435 in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5 #13 0x7f8ccb029651 in QObject::event(QEvent*) (this=0x2558510, e=) at kernel/qobject.cpp:1245 #14 0x7f8ccc003b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x2488a50, receiver=receiver@entry=0x2558510, e=e@entry=0x25395f0) at kernel/qapplication.cpp:3720 #15 0x7f8ccc009230 in QApplication::notify(QObject*, QEvent*) (this=0x7ffd3e28d790, receiver=0x2558510, e=0x25395f0) at kernel/qapplication.cpp:3503 #16 0x7f8ccaff7f1b in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffd3e28d790, receiver=0x2558510, event=event@entry=0x25395f0) at kernel/qcoreapplication.cpp:935 #17 0x7f8ccaffa057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x25395f0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228 #18 0x7f8ccaffa057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x247fac0) at kernel/qcoreapplication.cpp:1552 #19 0x7f8ccaffa588 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410 #20 0x7f8ccb04ee73 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x24c8c70) at kernel/qeventdispatcher_glib.cpp:271 #21 0x7f8cc5144ff7 in g_main_context_dispatch (context=0x7f8cb00016f0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3154 #22 0x7f8cc5144ff7 in g_main_context_dispatch (context=context@entry=0x7f8cb00016f0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3769 #23 0x7f8cc5145250 in g_main_context_iterate (context=context@entry=0x7f8cb00016f0, block=block@entry=1,
