[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra
https://bugs.kde.org/show_bug.cgi?id=362797 --- Comment #19 from victoria.re...@gmail.com --- (In reply to gedgepaul from comment #18) > Created attachment 102384 [details] > attachment-16707-0.html > > But I simply did as suggested with the .kra file and turned > it to .Jpeg and worked onre doing the stuff I lost on the > newer version of Krita, which seems to have fixed the issue as I > have yet to have the same problem again with anything else. > > On Tue, Nov 22, 2016 at 9:10 AM, Thousand sonwrote: > > > If I am able, I will send a copy of the file once I return home from > > sixth form. > > > > On Tue, Nov 22, 2016 at 8:56 AM, wrote: > > > >> https://bugs.kde.org/show_bug.cgi?id=362797 > >> > >> --- Comment #16 from victoria.re...@gmail.com --- > >> (In reply to victoria.ren64 from comment #15) > >> > (In reply to gedgepaul from comment #14) > >> > > Created attachment 102382 [details] > >> > > attachment-15446-0.html > >> > > > >> > > This has been sorted, I simply downloaded the newer version > >> and > >> > > worked on replacing what I had lost. > >> > > > >> > > On Tue, Nov 22, 2016 at 8:48 AM, wrote: > >> > > > >> > > > https://bugs.kde.org/show_bug.cgi?id=362797 > >> > > > > >> > > > victoria.re...@gmail.com changed: > >> > > > > >> > > >What|Removed |Added > >> > > > > >> > > > > >> > > > CC|| > >> victoria.re...@gmail.com > >> > > > > >> > > > -- > >> > > > You are receiving this mail because: > >> > > > You reported the bug. > >> > > > > >> > > >> > May you send me a link to the newest version (if you want, I don't want > >> to > >> > push you)? If you can, it would be greatly appreciated! > >> > >> > >> Also another problem would be that the file would not show up anywhere in > >> my > >> saved files, whilst the majority of other files would be saved, autosaved > >> or > >> not. > >> > >> -- > >> You are receiving this mail because: > >> You reported the bug. > >> > > > > I have installed the newest version of Krita and I tried to upload the file up there, but it still isn't loading. Do you think the file may be damaged? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369549] Crash while applying a transform
https://bugs.kde.org/show_bug.cgi?id=369549 --- Comment #3 from Raghavendra kamath--- I am using Qt version 5.7.0. I'll do a memory test and report back. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 372469] Scheduled split transactions in foreign currency
https://bugs.kde.org/show_bug.cgi?id=372469 --- Comment #4 from Stephane MANKOWSKI--- Do you have time to provide me more information because I don't understand what is the issue? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 372780] replay to mail crashed Kontact
https://bugs.kde.org/show_bug.cgi?id=372780 --- Comment #1 from michel munnix--- Created attachment 102385 --> https://bugs.kde.org/attachment.cgi?id=102385=edit mail received this is the mail which replying to generated the crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366289] When mirroring canvas (Mirror View) is ON - tilt direction for brush rotation works incorrectly
https://bugs.kde.org/show_bug.cgi?id=366289 Dmitry Kazakovchanged: What|Removed |Added Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit |a/1b88a3d2886a4e82b14ea4ebd |a/ef4cec6f8f4626b7815c5ceaf |8884cfc797f9641 |1bb208c867ead93 --- Comment #5 from Dmitry Kazakov --- Git commit ef4cec6f8f4626b7815c5ceaf1bb208c867ead93 by Dmitry Kazakov. Committed on 22/11/2016 at 09:09. Pushed by dkazakov into branch 'rempt/impex-refactoring'. Fix Tilt-elevation to work with rotated/mirrored canvas We should pass already normalized base angle values to the sensor Related: bug 369451 M +2-2plugins/paintops/libpaintop/kis_curve_option.cpp M +10 -3plugins/paintops/libpaintop/kis_curve_option.h M +1-1plugins/paintops/libpaintop/kis_pressure_hsv_option.cpp M +6-4plugins/paintops/libpaintop/kis_pressure_rotation_option.cpp http://commits.kde.org/krita/ef4cec6f8f4626b7815c5ceaf1bb208c867ead93 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 372780] New: replay to mail crashed Kontact
https://bugs.kde.org/show_bug.cgi?id=372780 Bug ID: 372780 Summary: replay to mail crashed Kontact Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: michel.mun...@skynet.be Target Milestone: --- Application: kontact (4.14.10) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: replying to a particular mail replying to a previous email from the same sender produced the same problem so it it probably dependent of the formating of the system that sent the mail i was replying to The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1b63ae5800 (LWP 4010))] Thread 6 (Thread 0x7f1af48ba700 (LWP 4022)): #0 0x7f1b60fbbbfd in poll () at /lib64/libc.so.6 #1 0x7f1b5aa7ce64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1b5aa7cf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1b617baf9e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f1b6178cd0f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f1b6178d005 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f1b6168a49f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f1b6176e613 in () at /usr/lib64/libQtCore.so.4 #8 0x7f1b6168cb7f in () at /usr/lib64/libQtCore.so.4 #9 0x7f1b5b0490a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f1b60fc402d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1ae700 (LWP 4021)): #0 0x7f1b5b04d3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b6168d044 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f1b61680b9a in () at /usr/lib64/libQtCore.so.4 #3 0x7f1b6168cb7f in () at /usr/lib64/libQtCore.so.4 #4 0x7f1b5b0490a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f1b60fc402d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f1af6f10700 (LWP 4016)): #0 0x7f1b617bc7c0 in () at /usr/lib64/libQtCore.so.4 #1 0x7f1b617bae4c in () at /usr/lib64/libQtCore.so.4 #2 0x7f1b617baef5 in () at /usr/lib64/libQtCore.so.4 #3 0x7f1b5aa7c4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #4 0x7f1b5aa7cd80 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1b5aa7cf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f1b617baf9e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f1b6178cd0f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7f1b6178d005 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #9 0x7f1b6168a49f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #10 0x7f1b6168cb7f in () at /usr/lib64/libQtCore.so.4 #11 0x7f1b5b0490a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f1b60fc402d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f1b06338700 (LWP 4012)): #0 0x7f1b5b04d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b5ff46b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f1b601fba06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f1b5b0490a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f1b60fc402d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f1b46c53700 (LWP 4011)): #0 0x7f1b5b04d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b601d3eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f1b601d3ee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f1b5b0490a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f1b60fc402d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f1b63ae5800 (LWP 4010)): [KCrash Handler] #6 0x0012 in () #7 0x7f1b563ba4be in KMime::Content::contentID(bool) () at /usr/lib64/libkmime.so.4 #8 0x7f1afaec7167 in TemplateParser::TemplateParser::createMultipartRelated(MessageCore::ImageCollector const&, KMime::Content*) const () at /usr/lib64/libtemplateparser.so.4 #9 0x7f1afaec8049 in TemplateParser::TemplateParser::addProcessedBodyToMessage(QString const&, QString const&) const () at /usr/lib64/libtemplateparser.so.4 #10 0x7f1afaec9eeb in TemplateParser::TemplateParser::processWithTemplate(QString const&) () at
[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra
https://bugs.kde.org/show_bug.cgi?id=362797 --- Comment #18 from gedgep...@gmail.com --- But I simply did as suggested with the .kra file and turned it to .Jpeg and worked onre doing the stuff I lost on the newer version of Krita, which seems to have fixed the issue as I have yet to have the same problem again with anything else. On Tue, Nov 22, 2016 at 9:10 AM, Thousand sonwrote: > If I am able, I will send a copy of the file once I return home from > sixth form. > > On Tue, Nov 22, 2016 at 8:56 AM, wrote: > >> https://bugs.kde.org/show_bug.cgi?id=362797 >> >> --- Comment #16 from victoria.re...@gmail.com --- >> (In reply to victoria.ren64 from comment #15) >> > (In reply to gedgepaul from comment #14) >> > > Created attachment 102382 [details] >> > > attachment-15446-0.html >> > > >> > > This has been sorted, I simply downloaded the newer version >> and >> > > worked on replacing what I had lost. >> > > >> > > On Tue, Nov 22, 2016 at 8:48 AM, wrote: >> > > >> > > > https://bugs.kde.org/show_bug.cgi?id=362797 >> > > > >> > > > victoria.re...@gmail.com changed: >> > > > >> > > >What|Removed |Added >> > > > >> > > > >> > > > CC|| >> victoria.re...@gmail.com >> > > > >> > > > -- >> > > > You are receiving this mail because: >> > > > You reported the bug. >> > > > >> > >> > May you send me a link to the newest version (if you want, I don't want >> to >> > push you)? If you can, it would be greatly appreciated! >> >> >> Also another problem would be that the file would not show up anywhere in >> my >> saved files, whilst the majority of other files would be saved, autosaved >> or >> not. >> >> -- >> You are receiving this mail because: >> You reported the bug. >> > > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra
https://bugs.kde.org/show_bug.cgi?id=362797 --- Comment #17 from gedgep...@gmail.com --- If I am able, I will send a copy of the file once I return home from sixth form. On Tue, Nov 22, 2016 at 8:56 AM,wrote: > https://bugs.kde.org/show_bug.cgi?id=362797 > > --- Comment #16 from victoria.re...@gmail.com --- > (In reply to victoria.ren64 from comment #15) > > (In reply to gedgepaul from comment #14) > > > Created attachment 102382 [details] > > > attachment-15446-0.html > > > > > > This has been sorted, I simply downloaded the newer version > and > > > worked on replacing what I had lost. > > > > > > On Tue, Nov 22, 2016 at 8:48 AM, wrote: > > > > > > > https://bugs.kde.org/show_bug.cgi?id=362797 > > > > > > > > victoria.re...@gmail.com changed: > > > > > > > >What|Removed |Added > > > > > > > > > > > > CC|| > victoria.re...@gmail.com > > > > > > > > -- > > > > You are receiving this mail because: > > > > You reported the bug. > > > > > > > > May you send me a link to the newest version (if you want, I don't want > to > > push you)? If you can, it would be greatly appreciated! > > > Also another problem would be that the file would not show up anywhere in > my > saved files, whilst the majority of other files would be saved, autosaved > or > not. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra
https://bugs.kde.org/show_bug.cgi?id=362797 --- Comment #16 from victoria.re...@gmail.com --- (In reply to victoria.ren64 from comment #15) > (In reply to gedgepaul from comment #14) > > Created attachment 102382 [details] > > attachment-15446-0.html > > > > This has been sorted, I simply downloaded the newer version and > > worked on replacing what I had lost. > > > > On Tue, Nov 22, 2016 at 8:48 AM,wrote: > > > > > https://bugs.kde.org/show_bug.cgi?id=362797 > > > > > > victoria.re...@gmail.com changed: > > > > > >What|Removed |Added > > > > > > > > > CC||victoria.re...@gmail.com > > > > > > -- > > > You are receiving this mail because: > > > You reported the bug. > > > > > May you send me a link to the newest version (if you want, I don't want to > push you)? If you can, it would be greatly appreciated! Also another problem would be that the file would not show up anywhere in my saved files, whilst the majority of other files would be saved, autosaved or not. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra
https://bugs.kde.org/show_bug.cgi?id=362797 --- Comment #15 from victoria.re...@gmail.com --- (In reply to gedgepaul from comment #14) > Created attachment 102382 [details] > attachment-15446-0.html > > This has been sorted, I simply downloaded the newer version and > worked on replacing what I had lost. > > On Tue, Nov 22, 2016 at 8:48 AM,wrote: > > > https://bugs.kde.org/show_bug.cgi?id=362797 > > > > victoria.re...@gmail.com changed: > > > >What|Removed |Added > > > > > > CC||victoria.re...@gmail.com > > > > -- > > You are receiving this mail because: > > You reported the bug. > > May you send me a link to the newest version (if you want, I don't want to push you)? If you can, it would be greatly appreciated! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra
https://bugs.kde.org/show_bug.cgi?id=362797 --- Comment #14 from gedgep...@gmail.com --- This has been sorted, I simply downloaded the newer version and worked on replacing what I had lost. On Tue, Nov 22, 2016 at 8:48 AM,wrote: > https://bugs.kde.org/show_bug.cgi?id=362797 > > victoria.re...@gmail.com changed: > >What|Removed |Added > > > CC||victoria.re...@gmail.com > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 372731] If tags 'Artist' & 'Album Artist' content is equal, both tags are not displayed in playlist
https://bugs.kde.org/show_bug.cgi?id=372731 Myriam Schweingruberchanged: What|Removed |Added Component|Playlist|Playlist/Playlist Layout ||Editor Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Myriam Schweingruber --- Where do you add the fields (Head, Body, single?), which layout variation do you use? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra
https://bugs.kde.org/show_bug.cgi?id=362797 --- Comment #13 from victoria.re...@gmail.com --- I also experience the same problems as the people below. My file "C:/Users/Victoria/AppData/Local/Temp/.krita-5604-document_0-autosave.kra" will not load, even if I've restarted my computer and closed and re-opened Krita multiple times. I would like to know what the problem is and why it is causing this. I have read some articles in an attempt to recover the files, all leading to no success. Please help me. It would be really appreciated if you do so. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra
https://bugs.kde.org/show_bug.cgi?id=362797 victoria.re...@gmail.com changed: What|Removed |Added CC||victoria.re...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366289] When mirroring canvas (Mirror View) is ON - tilt direction for brush rotation works incorrectly
https://bugs.kde.org/show_bug.cgi?id=366289 Dmitry Kazakovchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/krit ||a/1b88a3d2886a4e82b14ea4ebd ||8884cfc797f9641 Status|CONFIRMED |RESOLVED --- Comment #4 from Dmitry Kazakov --- Git commit 1b88a3d2886a4e82b14ea4ebd8884cfc797f9641 by Dmitry Kazakov. Committed on 21/11/2016 at 10:41. Pushed by dkazakov into branch 'krita/3.1'. Fix Tilt-elevation to work with rotated/mirrored canvas We should pass already normalized base angle values to the sensor Related: bug 369451 M +2-2plugins/paintops/libpaintop/kis_curve_option.cpp M +10 -3plugins/paintops/libpaintop/kis_curve_option.h M +1-1plugins/paintops/libpaintop/kis_pressure_hsv_option.cpp M +6-4plugins/paintops/libpaintop/kis_pressure_rotation_option.cpp http://commits.kde.org/krita/1b88a3d2886a4e82b14ea4ebd8884cfc797f9641 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369451] brush angle tied to canvas rotation instead of being absolute
https://bugs.kde.org/show_bug.cgi?id=369451 Dmitry Kazakovchanged: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/1b88a3d2886a4e82b14ea4ebd ||8884cfc797f9641 Resolution|DUPLICATE |FIXED --- Comment #5 from Dmitry Kazakov --- Git commit 1b88a3d2886a4e82b14ea4ebd8884cfc797f9641 by Dmitry Kazakov. Committed on 21/11/2016 at 10:41. Pushed by dkazakov into branch 'krita/3.1'. Fix Tilt-elevation to work with rotated/mirrored canvas We should pass already normalized base angle values to the sensor Related: bug 366289 M +2-2plugins/paintops/libpaintop/kis_curve_option.cpp M +10 -3plugins/paintops/libpaintop/kis_curve_option.h M +1-1plugins/paintops/libpaintop/kis_pressure_hsv_option.cpp M +6-4plugins/paintops/libpaintop/kis_pressure_rotation_option.cpp http://commits.kde.org/krita/1b88a3d2886a4e82b14ea4ebd8884cfc797f9641 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 --- Comment #65 from Teunizz--- You are right. I thought I changed the theme but somehow it wasn't completely changed. After solving that, Kwin didn't crash anymore. Sorry for the confusion. I hope you'll find the cause. And to be honest I do like the new Plasma 5 desktop. It's only a pitty that it's just not "snappy". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372739] Vsync disabled: slowmotion effects or wrong fps?
https://bugs.kde.org/show_bug.cgi?id=372739 --- Comment #5 from Antonio Orefice--- Hi again, maybe there is a misunderstanding here, sorry. The problem i have with limited framerate does not depend on the driver settings, I'm able to reproduce it even without nvidia's ForceFullCompositionPipeline=On What happens, is that if i remove MaxFPS= line from kwinrc and disable any "tearing prevention" in the compositor settings, kwin seems to render things at 60..62fps. I gather this information: 1- From the kwin's "Show FPS" effect: it shows 60..62 fps 2- by observing the windows edges while i drag it: If kwin's render rate were close to the display refresh, i'd expect to see smooth window dragging with a single "tearing" line, and this is indeed what happens if i specify MaxFPS=75 OR if i switch to a 60hz mode. But what happens is that the movement is jerky and there are several tearing lines/artifacts. As soon as i enable kwin's Tearing prevention ON (the method doesn't matter), the fps effect jumps to 75, i repeat, this happens with AND without any special driver configuration. Thanks for your attention. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate
https://bugs.kde.org/show_bug.cgi?id=261417 Mario Frankchanged: What|Removed |Added Attachment #102157|0 |1 is obsolete|| --- Comment #23 from Mario Frank --- Created attachment 102381 --> https://bugs.kde.org/attachment.cgi?id=102381=edit The patch that triggers an update of involved SAlbums on deletion of images. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372690] Font blurry in text editor
https://bugs.kde.org/show_bug.cgi?id=372690 --- Comment #2 from Teunizz--- I was about to write a comment because I just managed to solve the problem but I believe there's still some kind of bug. The problem is, Kate (the editor, the menu is fine) is not honouring the anti-aliasing settings for the font as set in Plasma 5 settings. Instead, it's using the systems anti-aliasing settings, in my case: Yast -> System -> Fonts. By changing the settings there, I was able to solve the problem. If it's technically not possible to let Kate use the Plasma 5 settings for anti-aliasing (in the text editor, the menu's are fine), shouldn't be there an advise in Kate's font setting about how/where to change anti-aliasing? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate
https://bugs.kde.org/show_bug.cgi?id=261417 --- Comment #22 from Mario Frank--- Okay, I looked for other ways to signal the AlbumManager about the deleted images and I did not find performant ways to do this in another way. Thus, I will upload the patch. Here is the commit message: "[PATCH] This commit fixes bug 261417. When images are deleted, the ImageViewUtilities give the ImageInfos to the DIO. In the ImageViewUtilities, the ids of the deleted images are buffered in a list and given to the AlbumManager via Signal-Slot-communication. I do that since in database layer, only the URIs of the images are present and getting the image ids is unnecessary effort. Since the AlbumManager already has all SAlbums, it is easy to first get all SAlbums that represent DuplicateSearches (I implemented a method to get all SAlbums by type) and then get all those albums that contain the deleted images (SearchXmlReader is needed here). In order to have a good performance and do no unnecessary work, the AlbumManager unites all image ids from the SAlbums to update and subtracts the ids of the deleted images (set operations). This way, I am able to communicate the set of images to rescan to the FindDuplicatesView. Before notifying the FindDuplicatesView, I delete all SAlbums that should be updated. The reason: Consider an SAlbum that contained two duplicates - the original image and the now deleted image. If I start a normal duplicates search, no SAlbum will be created for the original image and the SAlbum will thus not be updated and should not be in the final result set. Since I now know the ids of the images to rescan, I notify the FindDuplicatesView. But now I do not have albums to search in - and in fact this would not really be performant since uninvolved images would be scanned. Thus, I extended the DuplicatesFinder with a new constructor for searching for duplicates in a set of images. This could be applicable in other situations, too. To make this work, I extended the DB-Jobinfo with a switch for update of duplicates where the set of images is and not the albums and tags is used for duplicates search. This way, I can set the image ids and the update flag in the job info. The DBJob triggers a new variant of rebuildDuplicates in haariface where the image ids are taken directly. With this approach, only the SAlbums that need to be updated are updated. SAlbums are only lost, if no duplicates exist due to deletion which is appropriate. Previously not existing SAlbums cannot be created since no new images are involved. " By the way, I found some flaw that can lead to an unexpected set of SAlbums. I'll open another file soon. Cheers, Mario -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372779] valgrind will hang
https://bugs.kde.org/show_bug.cgi?id=372779 --- Comment #1 from Martin zhao--- It is hanging after reporting : "UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 16 times)" My program is large and links many other 3rd parties libraries. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370143] Desktop Settings doesn't save changes after logout
https://bugs.kde.org/show_bug.cgi?id=370143 --- Comment #7 from Adrian Piotrowicz--- When I'm not docked (no external monitors attached) nothing happens to config file after full reboot or plasmashell restart. However: When i docked plasma created new Containment - 66 Desktop was a mess so "kquitapp5 plasmashell && kstart5 plasmashell" Plasma removed Containment 65 "kquitapp5 plasmashell && kstart5 plasmashell" * N Situation is stable - no changes to configuration file -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372779] valgrind will hang
https://bugs.kde.org/show_bug.cgi?id=372779 Martin zhaochanged: What|Removed |Added CC||zhaoming...@163.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372779] New: valgrind will hang
https://bugs.kde.org/show_bug.cgi?id=372779 Bug ID: 372779 Summary: valgrind will hang Product: valgrind Version: 3.12 SVN Platform: Other OS: OS X Status: UNCONFIRMED Severity: critical Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: zhaoming...@163.com Target Milestone: --- atfs-mac-mini:valgrind fuja$ valgrind --tool=memcheck --suppressions=/Users/fuja/Desktop/ATFMemory.supp --gen-suppressions=yes /Users/fuja/ATFGit/XCodeATF/Bin/Debug/atf_test /Users/fuja/ATFGit/testdev/atf_tests/Regression/Consumer/Alias/Camera/Camera.atftest ==31806== Memcheck, a memory error detector ==31806== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==31806== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info ==31806== Command: /Users/fuja/ATFGit/XCodeATF/Bin/Debug/atf_test /Users/fuja/ATFGit/testdev/atf_tests/Regression/Consumer/Alias/Camera/Camera.atftest ==31806== --31806-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option --31806-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times) --31806-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times) --31806-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8 times) --31806-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 16 times) Killed: 9 atfs-mac-mini:valgrind fuja$ valgrind --tool=memcheck --suppressions=/Users/fuja/Desktop/ATFMemory.supp --gen-suppressions=yes /Users/fuja/ATFGit/XCodeATF/Bin/Debug/atf_test /Users/fuja/ATFGit/testdev/atf_tests/Regression/Consumer/Alias/Camera/Camera.atftest -v ==31845== Memcheck, a memory error detector ==31845== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==31845== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info ==31845== Command: /Users/fuja/ATFGit/XCodeATF/Bin/Debug/atf_test /Users/fuja/ATFGit/testdev/atf_tests/Regression/Consumer/Alias/Camera/Camera.atftest -v ==31845== Unsupported argument -v ==31845== ==31845== HEAP SUMMARY: ==31845== in use at exit: 805,113 bytes in 2,355 blocks ==31845== total heap usage: 5,741 allocs, 3,386 frees, 1,329,459 bytes allocated ==31845== ==31845== LEAK SUMMARY: ==31845==definitely lost: 4 bytes in 1 blocks ==31845==indirectly lost: 0 bytes in 0 blocks ==31845== possibly lost: 3,920 bytes in 93 blocks ==31845==still reachable: 433,547 bytes in 1,931 blocks ==31845== suppressed: 367,642 bytes in 330 blocks ==31845== Rerun with --leak-check=full to see details of leaked memory ==31845== ==31845== For counts of detected and suppressed errors, rerun with: -v ==31845== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 4) atfs-mac-mini:valgrind fuja$ valgrind --tool=memcheck --suppressions=/Users/fuja/Desktop/ATFMemory.supp --gen-suppressions=yes -v /Users/fuja/ATFGit/XCodeATF/Bin/Debug/atf_test /Users/fuja/ATFGit/testdev/atf_tests/Regression/Consumer/Alias/Camera/Camera.atftest ==31858== Memcheck, a memory error detector ==31858== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==31858== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info ==31858== Command: /Users/fuja/ATFGit/XCodeATF/Bin/Debug/atf_test /Users/fuja/ATFGit/testdev/atf_tests/Regression/Consumer/Alias/Camera/Camera.atftest ==31858== --31858-- Valgrind options: --31858----tool=memcheck --31858----suppressions=/Users/fuja/Desktop/ATFMemory.supp --31858----gen-suppressions=yes --31858---v --31858-- Output from sysctl({CTL_KERN,KERN_VERSION}): --31858-- Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 --31858-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-rdtscp-sse3-avx --31858-- Page sizes: currently 4096, max supported 4096 --31858-- Valgrind library directory: /usr/local/lib/valgrind --31858-- /Users/fuja/ATFGit/XCodeATF/Bin/Debug/atf_test (rx at 0x1, rw at 0x100134000) --31858--reading syms from primary file (19 8604) --31858--dSYM= /Users/fuja/ATFGit/XCodeATF/Bin/Debug/atf_test.dSYM/Contents/Resources/DWARF/atf_test --31858--reading dwarf3 from dsyms file --31858-- /usr/lib/dyld (rx at 0x7fff5fc0, rw at 0x7fff5fc38000) --31858--reading syms from primary file (6 1226) --31858-- Scheduler: using generic scheduler lock implementation. --31858-- Reading suppressions file: /Users/fuja/Desktop/ATFMemory.supp --31858-- Reading suppressions file: /usr/local/lib/valgrind/default.supp ==31858== embedded gdbserver: reading from /var/folders/st/ptn7nwtd01d2gg8bdfdfp7rcgn/T//vgdb-pipe-from-vgdb-to-31858-by-fuja-on-??? ==31858== embedded gdbserver: writing to /var/folders/st/ptn7nwtd01d2gg8bdfdfp7rcgn/T//vgdb-pipe-to-vgdb-from-31858-by-fuja-on-??? ==31858== embedded gdbserver: shared mem
[kwin] [Bug 372015] kwin_x11 crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=372015 --- Comment #10 from Sven Eden--- (In reply to Martin Gräßlin from comment #7) > @Sven: because KWin writes out the current runtime configuration. It loads > with that from your config and writes it back. If you manually want to > change the config you need to stop KWin. I am very sorry that I did not make this clear enough. I'll try with a list of actions. - Machine booted to console after one of those crashes. - Edit ~/.config/kwinrc and set OpenGLIsUnsafe to "false" and GLPlatformInterface to "glx". (Without the quotation marks of course) - Start SDDM via xdm and log into Plasma. - Compositor is off, systemsettings5 states that it crashed kwin in the past. - Reactivate OpenGL detection. - All decorations disappear with kwin crashing. - Open Yakuake with F12 and "grep GLPlatform ~/.config/kwinrc" reveals, that it is back to "egl". So no, it did not write back a configuration it read, it just decided that egl is a good thing to use. I have scanned all my system and user files whether I have accidentally set KWIN_OPENGL_INTERFACE="egl" somewhere, but my search revealed nothing. So I have solved this particular part for me by simply adding KWIN_OPENGL_INTERFACE="glx" to the environment. I am back on mesa-12.0.4 and kwin uses the glx back end. Everything is stable. But another question: Is the "Standard Aurorae/QML" thing something that is worked on? Actually I do use Oxygen with Helium Design and air-oxygen decorations. It is okay if people like Breeze, but I do not. It is too flat, too monochromatic and is more in my way than it helps. The desings based on Breeze do not mix well with the Oxygen icons, and the breeze icons are a nightmare. It is like being back on an Amiga 500 Workbench 1.3 with a monochrome monitor. However, kwin crashes too with everything set to "Breeze" when mesa-13+ is installed. But I guess forcing "glx" might fix that, I'll try this out today and report back. Meaning: kwin-5.8.3 + mesa-13.0.1 + forced "glx" PlatformInterface + "Breeze everywhere". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 353062] Freeze/failure to start when "show tray icon" is enabled
https://bugs.kde.org/show_bug.cgi?id=353062 godel9changed: What|Removed |Added CC||god...@mailinator.com --- Comment #7 from godel9 --- I have found one way to avoid the problem (I have tried it with xmonad and it works for opening klipper). Just use in a terminal > export QT_QPA_PLATFORMTHEME=generic before launching klipper > klipper -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372735] imposible dibujar
https://bugs.kde.org/show_bug.cgi?id=372735 --- Comment #7 from gundema...@hotmail.com --- Effectively. I just tried to disable openGL as you told me and now it works. I can not try the other option because I have a problem on the computer that does not let me install the updates, but it seems that this works. Thank you very much. De: QuiraltaEnviado: lunes, 21 de noviembre de 2016 18:18 Para: gundema...@hotmail.com Asunto: [krita] [Bug 372735] imposible dibujar https://bugs.kde.org/show_bug.cgi?id=372735 --- Comment #5 from Quiralta --- @gundemaro5 El OpenGL generalmente va incluido en las actualizaciones de tu computadora, cerciorate que este al día, especialmente en los "drivers" de la tarjeta de video, ya sean intel, nvidia o amd (depende cual tengas). si tu pc esta al día y aun se presenta el problema, puedes desactivar el OpenGL en Krita en la ventana de configuraciones, la cuarta opción del menú a la izquierda "display". -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370143] Desktop Settings doesn't save changes after logout
https://bugs.kde.org/show_bug.cgi?id=370143 --- Comment #6 from Adrian Piotrowicz--- So... I've done some testing/observations on ".config/plasma-org.kde.plasma.desktop-appletsrc" file. I've created a simple reader for that file which creates JSON data from it's contents and I've noticed that after each reboot plasma adds a new 'Containment' to that config. Situation changes after calling "kquitapp5 plasmashell && kstart5 plasmashell" which I'm using to sanitize plasma. After first call after reboot Plasma adds another Containment in that config. After second call Plasma removes two Containments from that config. And here is what is odd - Plasma removes not those two newly created Containments but rather two previous (leaving newest one). Numbers will be easier: I've got few Containments and highest number is 61 FULL REBOOT Plasma adds Containment 62 "kquitapp5 plasmashell && kstart5 plasmashell" Plasma adds Containment 63 "kquitapp5 plasmashell && kstart5 plasmashell" Plasma removes Containment 61 & 62 "kquitapp5 plasmashell && kstart5 plasmashell" * N Situation is stable - no changes to configuration file FULL REBOOT Plasma adds Containment 64 "kquitapp5 plasmashell && kstart5 plasmashell" Plasma adds Containment 65 "kquitapp5 plasmashell && kstart5 plasmashell" Plasma removes Containment 63 & 64 "kquitapp5 plasmashell && kstart5 plasmashell" * N Situation is stable - no changes to configuration file This situation is under 3 monitor setup. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372735] imposible dibujar
https://bugs.kde.org/show_bug.cgi?id=372735 --- Comment #6 from gundema...@hotmail.com --- thank you De: QuiraltaEnviado: lunes, 21 de noviembre de 2016 18:18 Para: gundema...@hotmail.com Asunto: [krita] [Bug 372735] imposible dibujar https://bugs.kde.org/show_bug.cgi?id=372735 --- Comment #5 from Quiralta --- @gundemaro5 El OpenGL generalmente va incluido en las actualizaciones de tu computadora, cerciorate que este al día, especialmente en los "drivers" de la tarjeta de video, ya sean intel, nvidia o amd (depende cual tengas). si tu pc esta al día y aun se presenta el problema, puedes desactivar el OpenGL en Krita en la ventana de configuraciones, la cuarta opción del menú a la izquierda "display". -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 372778] KRDC should propose a desktop resolution option like "Always fit to screen size"
https://bugs.kde.org/show_bug.cgi?id=372778 guerinichanged: What|Removed |Added CC||sebastien.guerin.news@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 372778] New: KRDC should propose a desktop resolution option like "Always fit to screen size"
https://bugs.kde.org/show_bug.cgi?id=372778 Bug ID: 372778 Summary: KRDC should propose a desktop resolution option like "Always fit to screen size" Product: krdc Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: sebastien.guerin.n...@gmail.com Target Milestone: --- In a multiple screens configuration with different screen resolutions, we must change desktop resolution each time we open a connection in a different screen because KRDC saves only a fixed desktop resolution. -- You are receiving this mail because: You are watching all bug changes.