[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

[Ryokun]

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

--- Comment #33 from Ryokun  ---
I had high hopes for your workaround but sadly it doesn't work for me. I tried
with the latest 3.2.0 version and even when I check/uncheck a box in the PNG
dialog box it still freezes randomly.

@Boudewijn, just an idea here if it can help: the krita version I compiled from
source myself doesn't crash when I export a file, but when I try to scale the
picture (again, with my self-compiled version), I have a message telling me
that it has been compiled without the support of the GNU scientific Library.
Could this library be related to our export problem ? (explaining why on the
same computer my compiled version exports files OK but not the downloaded one
?)

Other idea: maybe only people with a specific software installed encounter the
problem ? (I think particularly about XCode and the XCode additions) Maybe each
person with this problem should send you a system report ? (Apple menu -> about
this Mac -> System Report -> File Menu -> save...)

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

[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

[Ryokun]

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

--- Comment #34 from Ryokun  ---
(In reply to Boudewijn Rempt from comment #31)
> After some more tests, this seems to happen exclusively to Apple computers
> with a Radeon graphics card. Disabling OpenGL in the Krita settings/display
> page works around the issue.
> 
> No Krita developers has a mac with a Radeon card, so we will need work from
> owners with such hardware to find a workaround that doesn't mean opengl has
> to be disabled.

Sorry I didn't see this message. I indeed have a Radeon card on the 2 macs that
give me this problem (my third mac is a MacBook Air with an Intel Chipset and
it works ok on it). I tried to uncheck the opengl support in the Krita settings
page then quit and launched Krita again. I'm sure OpenGL is deactivated because
the mouse cursor moves ultra-slowly. Unfortunately, I tried to export multiple
times and still got the bug (although it seems less frequent).

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

[krita] [Bug 373676] Bent lines showing up on OSX.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||jdre...@web.de

--- Comment #5 from Boudewijn Rempt  ---
*** Bug 384052 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 384052] angular jagged lines when OPEN GL is turned on

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Boudewijn Rempt  ---
Hi,

Yes, this does happen -- though weirdly enough not on my macbook pro. I really
wonder what's up there, but it looks like on OSX, we're not getting
tablet/mouse events if the gpu is redrawing. It's pretty well-known that opengl
on OSX is Apple's red-headed stepchild :-(

*** This bug has been marked as a duplicate of bug 373676 ***

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

[kstars] [Bug 384034] Adding a point to the artificial horizon crashes kstars 2.8.1

[Jasem Mutlaq]

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

Jasem Mutlaq  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kst
   ||ars/bc2fb2d5da38a6c3248c24c
   ||9226eaa953b2c27c2
 Resolution|--- |FIXED

--- Comment #1 from Jasem Mutlaq  ---
Git commit bc2fb2d5da38a6c3248c24c9226eaa953b2c27c2 by Jasem Mutlaq.
Committed on 26/08/2017 at 14:59.
Pushed by mutlaqja into branch 'master'.

Fix crash in HorizonManager

M  +1-1kstars/tools/horizonmanager.cpp

https://commits.kde.org/kstars/bc2fb2d5da38a6c3248c24c9226eaa953b2c27c2

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

[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

[OneCept Games]

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

--- Comment #38 from OneCept Games  ---
With this build (4.0.0-prealpha.2) I can save .png files without toggle any
option in the .png save dialog :-)
It might be solved anyway in 4.0.0, because i encounter the freeze issue in
3.2.0.

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

[krita] [Bug 384026] G'MIC unresponsive when using unsupported output mode, and crashes Krita if force-closed

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Platform|Windows CE  |MS Windows
 Ever confirmed|0   |1
Summary|G'MIC crash with Array  |G'MIC unresponsive when
   |faded filter (Krita 3.2.1 - |using unsupported output
   |Windows 10 64bit)   |mode, and crashes Krita if
   ||force-closed

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

[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

[Ryokun]

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

--- Comment #40 from Ryokun  ---
(In reply to Boudewijn Rempt from comment #39)
> That sounds like it's indeed fixed by the new asynchronous/background saving
> feature then (which clones the image before saving, so you can go on editing
> the original image). But it's going to be _really_ tough to backport that to
> 3.x, which leaves us with a quandary...

I confirm it too, it works perfectly ! (tried 20 times in a row)

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

[kwin] [Bug 384041] Compositor falls back to non compositor

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Flöser  ---
This is expected: the games tell KWin to turn off the compositor and KWin does
so. If you don't like this behavior, there is an option in the compositor
settings to disable it.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Julien Muchembled]

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

Julien Muchembled  changed:

   What|Removed |Added

 CC||j...@jmuchemb.eu

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

[krita] [Bug 384019] 3.2.1 textured brush use freezes krita and corrupts install [prefer close thread; app too broken]

[01nanovolt]

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

01nanovolt  changed:

   What|Removed |Added

Summary|3.2.1 textured brush use|3.2.1 textured brush use
   |freezes krita and corrupts  |freezes krita and corrupts
   |install |install [prefer close
   ||thread; app too broken]

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

[krita] [Bug 384019] 3.2.1 textured brush use freezes krita and corrupts install

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|3.2.1 textured brush use|3.2.1 textured brush use
   |freezes krita and corrupts  |freezes krita and corrupts
   |install [prefer close   |install
   |thread; app too broken] |
 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #10 from Boudewijn Rempt  ---
It is still something broken _on your system_ -- it's not that Krita is too
broken to work in general... But if you want to, I can close the bug, of
course.

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

[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

[Boudewijn Rempt]

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

--- Comment #39 from Boudewijn Rempt  ---
That sounds like it's indeed fixed by the new asynchronous/background saving
feature then (which clones the image before saving, so you can go on editing
the original image). But it's going to be _really_ tough to backport that to
3.x, which leaves us with a quandary...

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

[krita] [Bug 384026] G'MIC crash with Array faded filter (Krita 3.2.1 - Windows 10 64bit)

[Alvin Wong]

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

--- Comment #5 from Alvin Wong  ---
(In reply to Silvio Grosso from comment #4)
> Hello Alvin !
> 
> First off, thanks a lot indeed for your help.
> You were right !
> Yesterday, my g'mic path was:
> C:/gmic-krita-qt-2.0.3_pre-win64/gmic_krita_qt.exe
> G'mic Version was: 2.0.3 170811 
> 
> After your message new path is set by me manually as:
> C:/Program Files/Krita (x64)/bin/gmic_krita_qt.exe
> 
> I don't know why Krita 2.3.1 picked up the wrong path because I have
> installed it through the x64.exe installer *without* getting a different
> version from the G'MIC websit.
> My wild guess is that maybe Krita picked up the wrong setting through some
> old configuration file still present on my computer (e.g. kritarc etc).

That's actually a weakness of the way Krita is handling the gmic-qt
configuration... if you have ever set a custom path before in the earlier beta
versions it will not be overridden, because use the same configuration entry.


> To make it short though the crash is still there even with the new setting
> :-(
> Here it is the new log crash file on Windows 10 - 64 bit:
> https://www.dropbox.com/s/0snontzroktebp5/kritacrash_2.0.4_new_gmic_settings.
> txt?dl=0
> 
> To force this crash it looks like you must close the  main G'mic window with
> all filters settings and only *afterwards* the secondary window which
> informs you that "the option to add a new layer is not implemented yet on
> Krita". If you close this secondary window at first most of the time only
> G'MIC crashes but Krita 2.3.1 continues working.

Thanks for the info, now I can get a crash in Krita but I'm getting a different
backtrace than yours...



(technical details below)

I'm actually getting a slightly different backtrace for the few times I've
tried, but they all fail at plugins\extensions\qmic\QMic.cpp:293 (frame #4 in
the below backtrace), which I suppose would be due to Krita trying to write a
message reply to the closed QLocalSocket (due to gmic-qt being closed early).

There are several issues that contributes to this:

1. The gmic-qt plugin does the QLocalSocket IPC on the UI thread (so does
Krita, but it's not really relevant here)
2. Krita shows a message box during the IPC (lien 270) and did not send a
response before that, which in turn blocked gmic-qt due to #1
3.Since gmic-qt is blocked, Windows will kindly offer to force-close it, and
thus the QLocalSocket will be killed
4. Krita tries to send the reply after the message box is dismissed, but the
socket is closed so it causes a crash (doesn't really make sense that the write
call doesn't check if the socket is closed...)


A possible quick fix is to defer the message box to show *after* the IPC is
completed (i.e. replyis sent back to gmic-qt and socket is closed normally)


#0  0x68975100 in QIODevicePrivate::~QIODevicePrivate() () from
F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#1  0x6897731c in QIODevice::write(char const*, long long) () from
F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#2  0x6896270a in QDataStream::operator<<(int) () from
F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#3  0x68962a21 in QDataStream::writeBytes(char const*, unsigned int) ()
from F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#4  0x07fe815981f2 in QMic::connected (this=0x168cd5c0) at
F:\dev\krita\src_3.2\plugins\extensions\qmic\QMic.cpp:293
#5  0x07fe815abcf5 in QMic::qt_static_metacall (_o=0x168cd5c0,
_c=, _id=, _a=)
at
F:/dev/krita/b_mgw54_x64_3.2/build_krita/plugins/extensions/qmic/moc_QMic.cpp:118
#6  0x68a2e3fa in QMetaObject::activate(QObject*, int, int, void**) ()
from F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#7  0x05156fa3 in
QLocalSocket::connectToServer(QFlags) () from
F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Network.dll
#8  0x68a2e3fa in QMetaObject::activate(QObject*, int, int, void**) ()
from F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#9  0x68a96f50 in QWinEventNotifier::activated(void*,
QWinEventNotifier::QPrivateSignal) () from
F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#10 0x68a5072f in QWinEventNotifier::event(QEvent*) () from
F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#11 0x00e2a33c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Widgets.dll
#12 0x00e2f6a0 in QApplication::notify(QObject*, QEvent*) () from
F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Widgets.dll
#13 0x07feb7d67f86 in KisApplication::notify (this=,
receiver=0x310daf50, event=0x22c110)
at F:\dev\krita\src_3.2\libs\ui\KisApplication.cpp:543
#14 0x68a0e312 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from F:\dev\krita\b_mgw54_x64_3.2\install\bin\Qt5Core.dll
#15 0x68a5404b in
QEventDispatcherWin32Private::activateEventNotifier(QWinEventNotifier*) () from

[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"

[Cristian Aravena Romero]

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

--- Comment #19 from Cristian Aravena Romero  ---
Created attachment 107535
  --> https://bugs.kde.org/attachment.cgi?id=107535=edit
bd_mediainfo.txt

Hello Leslie Zhai,

[...]


> Hi Cristian,
> 
> > dvd+rw-mediainfo /dev/sr0 2>&1 | tee -i >/tmp/bd_mediainfo.txt
> 
> Please try and attach the bd_mediainfo.txt, thanks!

Ok

Regards,
--
Cristian

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

[kwin] [Bug 384045] Task switcher does not render with compositing enabled

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Flöser  ---
I'm sorry, but this is a problem in Qt, not in KWin. QtQuick requests a shader
language version which is not supported.

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

[kstars] [Bug 384057] Feature request : Apparent size of an object in the observation planner

[Sebastien]

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

--- Comment #4 from Sebastien  ---
Yes ok, this is already what I'm doing so forget the graphical part of my wish.
But imagine you have dozen of object in your list, then you have to select one
by one to compare object size with your sensor size.
It would be great to add one more criteria to reduce the size of the list.

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

[krita] [Bug 384060] Open GL causes brush strokes to be laggy and jerky

[Cristina]

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

Cristina  changed:

   What|Removed |Added

 CC||thesilverdo...@gmail.com

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

[krita] [Bug 384060] New: Open GL causes brush strokes to be laggy and jerky

[Cristina]

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

Bug ID: 384060
   Summary: Open GL causes brush strokes to be laggy and jerky
   Product: krita
   Version: 3.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: OpenGL Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: thesilverdo...@gmail.com
  Target Milestone: ---

I found that with no previous problems, my brush strokes began acting up and
acting jerky and laggy. I tried researching the problem, but to no avail. Many
forums mentioned turning on Open GL, which I checked, and noticed that I did
have on. Just to check, I turned it off and then tested the strokes. The
jerkiness stopped, but the brush is now slow and has the problems mentioned
when Open GL was off. I turned on Open GL again in an attempt to resolve the
issue but then was back to the original problem. I would liken it to video game
lag. This is very frustrating as I have a project to finish this weekend and I
am not able to use krita, my preferred program, to finish it.

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

[krita] [Bug 384060] Open GL causes brush strokes to be laggy and jerky

[Cristina]

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

Cristina  changed:

   What|Removed |Added

   Severity|normal  |critical

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

[krita] [Bug 384061] New: Can't See What I'm Doing

[Amy Thompson]

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

Bug ID: 384061
   Summary: Can't See What I'm Doing
   Product: krita
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: atkitty2...@gmail.com
  Target Milestone: ---

No matter what tool I use, I can't see what I'm doing. I try to sketch, but I
can't see anything. Once I click outside of the canvas, I can see what I did. I
haven't had any success trying to fix this. I can't sketch without being able
to see my art.

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

[sparhawk]

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

--- Comment #118 from sparhawk  ---
(In reply to Antonio Rojas from comment #117)
> Arch users, please test qt5-declarative 5.9.1-5

I guess this relates to the memory leak. FWIW this doesn't fix the original CPU
bug.

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

[krita] [Bug 384061] Can't See What I'm Doing

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
This is an bug with openGL on laptops that use intel graphics cards. We're
currently testing an alternative way of handling the openGL here:

https://krita.org/en/item/angle-and-windows-ink-a-new-test-version-of-krita-for-windows/

It would be super useful if you could give that a spin(and fill out the survey
:) ). If you don't want to try it, you can also try to go to
settings->configure Krita->display and toggle openGL.

(Though, it be really really really super useful if you could at the very least
check, we really want to fix this bug once and for all :) )

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

[krita] [Bug 384060] Open GL causes brush strokes to be laggy and jerky

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
Hm... which version of Linux are you using? And could you also tell us which
graphics card and driver you are running?

Also, can I tempt you to check if the same issue still happens when using the
3.2.1 appimage?

https://krita.org/en/item/krita-3-2-1-released/

And if you're not familiar with appimages a quick guide:

http://www.davidrevoy.com/article322/krita-appimage-for-cats

It'd help a lot to see if it is not a bug we might have fixed past year.

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

[kmymoney4] [Bug 354944] Line/bar Chart Reports Unavailable for Full Period Spanning Years

[flywire]

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

--- Comment #4 from flywire  ---
This is an aside to the whole issue of not using the Fiscal year setting which
still stands.

@Ralf Habacker - Can you confirm the bug?

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

[frameworks-kcoreaddons] [Bug 384037] DesktopFileParser::convert: incorrect service file name?

[Michael Pyne]

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

Michael Pyne  changed:

   What|Removed |Added

 CC||arichardson@gmail.com,
   ||mgraess...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Michael Pyne  ---
Hi Sandro,

It looks like you've mixed up the bug report with some attempt at
troubleshooting, but without enough detail on either of those to lead us to a
fix.

As I understand it, the actual issue is that kwin has "some functionality not
working", task switcher in particular.

You think this may be related to Desktop File Parser, I'm guessing based on a
review of logs and console output.  But we don't have enough detail here to
show whether the warning message you saw is really a kwin bug, or perhaps kwin
searching for an old-style kwin-effects as a fallback after properly searching
for kwineffects.desktop.

In other words, KWin might be doing the right thing and DesktopFileParser might
be doing the right thing, with a packaging error of some sort thrown in.  But
it's hard to tell, a lot of the "normal looking" logs we don't have here would
help us to eliminate potential problems.

I'm CC'ing the maintainers for both of these in case either have seen this, but
I would recommend at the very least to attach the full kwin output logs you
have from where you're experiencing issues, and to provide additional detail
about what exactly the problems are (including related issues), what parts of
KWin are still working, graphics drivers in use, the last working version of
kwin and when things stopped working right, etc.  Thanks.

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

[kscreenlocker] [Bug 384005] With Latest Nvidia Drivers (384.69), Kscreenlocker has a segfault

[bugzilla_noreply]

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

bjoe...@arcor.de changed:

   What|Removed |Added

 CC||bjoe...@arcor.de

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

[amarok] [Bug 384016] Amarok Crash

[Myriam Schweingruber]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Myriam Schweingruber  ---
Sadly your crash report doesn't have debugging symbols, so there is little we
can do about. If this crash is reproducible, please install debugging symbols
and provide a better backtrace. See also
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

[Antonio Rojas]

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

--- Comment #117 from Antonio Rojas  ---
Arch users, please test qt5-declarative 5.9.1-5

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

[digikam] [Bug 384059] New: Album > Reread metadata from images does not work correctly

[Richard Ash]

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

Bug ID: 384059
   Summary: Album > Reread metadata from images does not work
correctly
   Product: digikam
   Version: 5.5.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags-Captions
  Assignee: digikam-bugs-n...@kde.org
  Reporter: rich...@audacityteam.org
  Target Milestone: ---

Whilst I was on holiday, I went through some images on my laptop, adding
captions (no tags) to them and deleting some. I now want to transfer the images
back to my main desktop PC, taking the new captions with me. The two machines
do not share a database, both use the default sqlite database. Images are
from-camera JPEGs.

Album 1:
1. I verified on the laptop (source machine) that captions had been written to
all the configured fields in the file (default list including
Xmp.tiff.ImageDescription and Xmp.dc.description).
2. I then copied the image files using scp to the desktop PC
3. I started Digikam and let it scan for new items (set to happen at startup)
4. I went to the newly copied album, and did "Album > Reread metadata from
images". In the past I have used this to read in the captions from the file
data.
5. It didn't work, and neither did the same entry on the Item menu. The
"completed" message popped up so quickly and with no disk activity that I don't
think it actually checked the images at all. Certainly much quicker than
generating a thumbnail.
6.Opening the metadata editor window at this point showed all the fields filled
in with the caption, but even after clicking OK, the image thumbnail and
captions tab of the right-hand side bar had no caption available.
7. After much cursing, I tried selecting one image, and using the "More > Read
metadata from file to Database" button in the captions tab of the right-hand
side bar. This worked, read the file and populated the thumbnail / sidebar.
Manually working through each file in the album got the information into the
database.
So this has a work-around, but a painful one for any number of images.

Album 2:
I went to repeat this, but found the other two albums have not had the captions
written to the files on the source machine. So I am stuck even earlier:
- No amount of Album > Write Metadata to Images writes it out
- Again the completed notification is instant, far faster than disk access
times on this machine.
- More > Write Metadata to each file button in the right-hand side bar is
greyed out
- I have tried turning lazy synchronisation off, no change.
- I tried altering the preferences so that an XMP sidecar is written as well as
to the image file, but no sidecar files are written!
- If I edit the caption again and then click Apply the changed caption is
written out, but this means manually altering (no-op) every single caption by
hand (as they are different to each other).
A potential work-around exists but is very labour intensive.

I think I am correct to say that when I completed editing captions on this
album (with lazy sync turned on) I just quit Digikam, without manually telling
it to sync changes, where as I synced changes by hand on Album 1. Does this
mean that sync-pending-changes-on-exit is broken as well?

I am in the process of updating to Digikam 5.6.0 to see if anything changes.

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

[digikam] [Bug 384059] Album > Reread metadata from images does not work correctly

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Instead 5.6.0, test 5.7.0 pre-release where ore patches have been applied
recently.

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[frameworks-kio] [Bug 372207] kwrite file open dialog, filenames overwrite icons (probably all apps)

[Arthur Țițeică]

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

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@cloud.titeica.ro

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

[digikam] [Bug 384059] Album > Reread metadata from images does not work correctly

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---


*** This bug has been marked as a duplicate of bug 378098 ***

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

[digikam] [Bug 378098] update meta data from selected images (generated outside digikam) does not work anymore

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||rich...@audacityteam.org

--- Comment #2 from Maik Qualmann  ---
*** Bug 384059 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 383675] highlight makes text disappear

[Germano Massullo]

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

--- Comment #4 from Germano Massullo  ---
Created attachment 107537
  --> https://bugs.kde.org/attachment.cgi?id=107537=edit
screenshot2

(In reply to Yuri Chornoivan from comment #3)
> 
> Ok. Does it happen for every file or just a particular file you cannot share?

For this file. Instead on other files I am getting invisible highlights.

> Is there any way to produce some other file with this issue so you can share
> it?

I will send you the file by e-mail, so it will not shared publicly

> What is the way the faulty file has been produced (File -> Properties)?

See attachment

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

[plasmashell] [Bug 383581] Mis-rendering of file and icon names on desktop following sleep-wake cycle

[Joe]

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

Joe  changed:

   What|Removed |Added

 CC||jchevar...@gmail.com

--- Comment #1 from Joe  ---
I also experience this issue: 

arch linux (not testing) - Frameworks 5.37.0, QT 5.9.1, Plasma 5.10.5
NVIDIA GTX 1070  (384.59)
FX-8350

If I select all the icons on my desktop and move them (really just wiggle them
around with the mouse and even drop them back in the same spot), the corruption
goes away. Also, the SDDM login screen has the same corruption in the user
profile picture. I  can also reproduce this on my laptop (same software stack,
but an Intel Xenon and mobile NVidia Quadro chip).

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

[okular] [Bug 361408] Okular crashed while zooming vectorial image

[Germano Massullo]

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

Germano Massullo  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #2 from Germano Massullo  ---
(In reply to Albert Astals Cid from comment #1)
> Can you reproduce the problem?

No I am sorry

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

[okular] [Bug 383675] highlight makes text disappear

[Germano Massullo]

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

--- Comment #5 from Germano Massullo  ---
Moreover, when I try to erase the strange highlight/revision, Okular crashes
with the following crashreport


[user@machine ~]$ gdb okular
GNU gdb (GDB) Fedora 8.0-22.fc26
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from okular...Reading symbols from
/usr/lib/debug/usr/bin/okular.debug...done.
done.
(gdb) run
Starting program: /usr/bin/okular 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fd2706ee700 (LWP 17423)]
[New Thread 0x7fd2609ed700 (LWP 17424)]
[New Thread 0x7fd24c107700 (LWP 17436)]
[New Thread 0x7fd24b7c5700 (LWP 17437)]
[New Thread 0x7fd24adbf700 (LWP 17438)]
[New Thread 0x7fd24a5be700 (LWP 17439)]
[New Thread 0x7fd249dbd700 (LWP 17440)]
[New Thread 0x7fd2495bc700 (LWP 17441)]
[New Thread 0x7fd246714700 (LWP 17472)]
[New Thread 0x7fd245f13700 (LWP 17473)]
[Thread 0x7fd246714700 (LWP 17472) exited]
[New Thread 0x7fd246714700 (LWP 17474)]
[Thread 0x7fd245f13700 (LWP 17473) exited]
[Thread 0x7fd246714700 (LWP 17474) exited]
[New Thread 0x7fd246714700 (LWP 17475)]
[New Thread 0x7fd245f13700 (LWP 17476)]
[Thread 0x7fd246714700 (LWP 17475) exited]
[Thread 0x7fd245f13700 (LWP 17476) exited]
[New Thread 0x7fd245f13700 (LWP 17477)]
[New Thread 0x7fd246714700 (LWP 17478)]
[Thread 0x7fd245f13700 (LWP 17477) exited]
[Thread 0x7fd246714700 (LWP 17478) exited]
[New Thread 0x7fd246714700 (LWP 17479)]
[Thread 0x7fd246714700 (LWP 17479) exited]
Illegal icon group:  7
[New Thread 0x7fd246714700 (LWP 17481)]
[Thread 0x7fd246714700 (LWP 17481) exited]
[New Thread 0x7fd246714700 (LWP 17490)]
okular: Annot.cc:1898: int Annot::getRotation() const: Assertion `pageobj !=
NULL' failed.

Thread 19 "Okular::PixmapG" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fd246714700 (LWP 17490)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  }
Missing separate debuginfos, use: dnf debuginfo-install
compat-openssl10-1.0.2j-6.fc26.x86_64
(gdb) thread apply all backtrac

Thread 19 (Thread 0x7fd246714700 (LWP 17490)):
#0  0x7fd2794ef69b in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7fd2794f14a0 in __GI_abort () at abort.c:89
#2  0x7fd2794e7d5a in __assert_fail_base (fmt=0x7fd2796514a8 "%s%s%s:%u:
%s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fd247dd5624
"pageobj != NULL", file=file@entry=0x7fd247dd55cb "Annot.cc",
line=line@entry=1898, function=function@entry=0x7fd247dd9590
 "int Annot::getRotation()
const") at assert.c:92
#3  0x7fd2794e7dd2 in __GI___assert_fail
(assertion=assertion@entry=0x7fd247dd5624 "pageobj != NULL",
file=file@entry=0x7fd247dd55cb "Annot.cc", line=line@entry=1898,
function=function@entry=0x7fd247dd9590  "int Annot::getRotation() const") at assert.c:101
#4  0x7fd247cc92a1 in Annot::getRotation() const (this=0x102ffc2c0) at
Annot.cc:1898
#5  0x7fd247cc9af3 in AnnotTextMarkup::draw(Gfx*, bool) (this=0x102ffc2c0,
gfx=0x7fd240004e00, printing=) at Annot.cc:3917
#6  0x7fd247d55627 in Page::displaySlice(OutputDev*, double, double, int,
bool, bool, int, int, int, int, bool, bool (*)(void*), void*, bool (*)(Annot*,
void*), void*, bool) (this=0x1008b3190, out=0x7fd2467139f0, out@entry=0x130,
hDPI=112.47058823529412, hDPI@entry=0, vDPI=112.54545454545453, 
vDPI@entry=2.1219957909652723e-314, rotate=0, rotate@entry=1,
useMediaBox=useMediaBox@entry=13, crop=crop@entry=true, sliceX=-1, 
sliceX@entry=32722, sliceY=, sliceW=,
sliceH=, printing=false, abortCheckCbk=,
abortCheckCbkData=, annotDisplayDecideCbk=,
annotDisplayDecideCbkData=, copyXRef=true) at Page.cc:622
#7  0x7fd247d59df9 in PDFDoc::displayPageSlice(OutputDev*, int, double,
double, int, bool, bool, bool, int, int, int, int, bool (*)(void*), void*, bool
(*)(Annot*, void*), void*, bool) (this=, out=0x130,
out@entry=0x7fd2467139f0, page=-1382767675, hDPI=0, 
hDPI@entry=112.47058823529412, vDPI=2.1219957909652723e-314,
vDPI@entry=112.54545454545453, rotate=1, 
rotate@entry=0, useMediaBox=useMediaBox@entry=false, crop=crop@entry=true,
printing=, sliceX=, sliceY=,
sliceW=, sliceH=, 

[kstars] [Bug 384057] Feature request : Apparent size of an object in the observation planner

[Sebastien]

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

--- Comment #2 from Sebastien  ---
Exactly.
Like in dso-browser website. Actually in kstars, filter includes type of
object, magnitude, height in the sky. Size in the sky is missing and would help
to choose a target. 

To be perfect, it would be great to visualise the fov with an overlay square. 
It's a shame to use an external tool like dso-browser, then a python script to
convert into ekos, while everything you need can be done with one software. 

Are you a user of dso-browser Jasem. If it is, you certainly know what I mean.

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

[kstars] [Bug 384057] Feature request : Apparent size of an object in the observation planner

[Jasem Mutlaq]

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

--- Comment #3 from Jasem Mutlaq  ---
You can do this now. Create an FOV indicator for your camera, then in your
observation list, center each desired target in the sky map. Enable HiPS with
DSS Colored overlay, and you will get a pretty good idea on how the target will
appear in your field of view.

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

[kmymoney4] [Bug 384062] New: Printing Reports

[James]

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

Bug ID: 384062
   Summary: Printing Reports
   Product: kmymoney4
   Version: 4.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: jpf4...@outlook.com
  Target Milestone: ---

When I try and print a Report to my HP Wireless printer I get a message saying
report can not print. 
Dose this software support the HP deskjet 2600 series Printers

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

[krita] [Bug 384063] New: Painting problems

[Cado9819]

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

Bug ID: 384063
   Summary: Painting problems
   Product: krita
   Version: 3.1.4
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: cado9...@gmail.com
  Target Milestone: ---

When i was painting it suddenly stoped and the next try it dont move until the
wacom screen or button is released

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

[konsole] [Bug 369496] KPart doesn't respect Scrollback File Location for "Unlimited Scrollback"

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Kurt Hindenburg  ---
Thanks for the ping, I had forgotten about this bko; I'll fix this for next
release

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

[kscreenlocker] [Bug 384064] New: kscreenlocker is broken after locking

[Scott]

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

Bug ID: 384064
   Summary: kscreenlocker is broken after locking
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: ssadow...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

Locking the screen by any means produces a black screen with white text
reporting that "The screen locker is broken and unlocking is not possible
anymore". This began after installing a bunch of KDE Neon updates yesterday.

When run from the terminal, the following is output:

$ /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
org.kde.kcoreaddons: Failed to establish shared memory mapping, will fallback
to private memory -- memory usage will increase
Locked at 1503795497
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kscreenlocker_greet path =
/usr/lib/x86_64-linux-gnu/libexec pid = 26328
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
Segmentation fault

System info:

System:Host: NeonBox Kernel: 4.12.8-041208-generic x86_64 (64 bit gcc:
7.1.0)
   Desktop: KDE Plasma 5.10.5 (Qt 5.9.1) dm: sddm,sddm Distro: neon
16.04 xenial
CPU:   Quad core Intel Core i7-6700HQ (-HT-MCP-) cache: 6144 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 20736
   clock speeds: min/max: 800/3500 MHz 1: 3143 MHz 2: 3198 MHz 3: 3180
MHz 4: 3134 MHz 5: 3190 MHz
   6: 3188 MHz 7: 3146 MHz 8: 3174 MHz
Graphics:  Card: NVIDIA GM107GLM [Quadro M600M] bus-ID: 01:00.0 chip-ID:
10de:13b2
   Display Server: X.Org 1.19.3 drivers: nvidia (unloaded:
fbdev,vesa,nouveau)
   Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
   GLX Renderer: Quadro M600M/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA
384.69 Direct Rendering: Yes
Audio: Card-1 NVIDIA Device 0fbc driver: snd_hda_intel bus-ID: 01:00.1
chip-ID: 10de:0fbc
   Card-2 Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID:
00:1f.3 chip-ID: 8086:a170
   Sound: Advanced Linux Sound Architecture v: k4.12.8-041208-generic

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

[krita] [Bug 384065] New: lag

[bugzilla_noreply]

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

Bug ID: 384065
   Summary: lag
   Product: krita
   Version: 3.2.0
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: ashu.d...@gmail.com
  Target Milestone: ---

it worked just fine before seven pm. Than closed the pc, it did some upgrade
(mandatory by windows 10) and now it just doesn't work!it's slow, it doesn't
show the stoke unless i select something else, thank it magically appears on
the screen. I just loved this program so much, the fact thata now it isn't
workin is making me cry. 
Yes, i did upgrade my intel drivers!


OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.15063
  Pretty Productname: Windows 10
  Product Type: windows
  Product Version: 10

OpenGL Info
  Vendor: Intel
  Renderer: Intel(R) HD Graphics 4000
  Version: 3.0.0 - Build 10.18.10.4653
  Shading language: 1.30 - Build 10.18.10.4653
   Version: 3.0
 Supports deprecated functions: true

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

[kscreenlocker] [Bug 384064] kscreenlocker is broken after locking

[Scott]

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

--- Comment #1 from Scott  ---
Also:

$ /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --version
kscreenlocker_greet 0.1

(This version is not among the options on the drop-down list above)

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

[Kishore Gopalakrishnan]

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

--- Comment #119 from Kishore Gopalakrishnan  ---
(In reply to Antonio Rojas from comment #117)
> Arch users, please test qt5-declarative 5.9.1-5

Unfortunately, it doesn't fix the bug. RAM usage still increases with time.
however, the version you linked in comment 60 fixes it.

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

[frameworks-kdbusaddons] [Bug 384066] New: Auto-rotate screen not working for Accelerometer sensors

[sac]

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

Bug ID: 384066
   Summary: Auto-rotate screen not working for Accelerometer
sensors
   Product: frameworks-kdbusaddons
   Version: 5.37.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: j1563...@trbvm.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

When the tablet / convertible is rotated Fedora 26 & Ubuntu 17.04 & 17.10 are
automatically rotating the screen as well, which is not working in KDE :/

- Rotation is possible with iio-sensor-proxy (IIO sensors to D-Bus proxy,
https://github.com/hadess/iio-sensor-proxy) that comes pre-shipped with Kubuntu
& Neon.
- executing "monitor-sensor" generates proper d-bus messages ("Accelerometer
orientation changed: left-up"), Yoga 900s tablet Kernel 4.11.12

"With gnome this is picked up by gnome-settings-daemon if I'm correct. How do I
inform lightdm to use this information to auto-rotate the screen? Although it's
definitely possible to run my own script to pull all the time for changes, I
prefer to have it in an event loop that checks d-bus anyway, so I'm not
suddenly creating some kind of battery drain."
https://ubuntuforums.org/showthread.php?t=2343374
https://superuser.com/questions/1147784/how-to-auto-rotate-the-screen-using-yoga-900s-accelerometer

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

[konsole] [Bug 369496] KPart doesn't respect Scrollback File Location for "Unlimited Scrollback"

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kon
   ||sole/a70ff34d28e061bec33513
   ||c21fa710f426721fd0

--- Comment #4 from Kurt Hindenburg  ---
Git commit a70ff34d28e061bec33513c21fa710f426721fd0 by Kurt Hindenburg.
Committed on 27/08/2017 at 01:51.
Pushed by hindenburg into branch 'master'.

For KParts, read Scrollback File Location from konsolerc

Apps using KonsolePart will now use Konsole's setting for the
scrollback file location.  There is also a check in the apprc for this
info.
Note that for the 2nd option "Use user specific location", the app
name will be used (e.g. /home/user/.cache/yakuake).

M  +11   -1src/History.cpp

https://commits.kde.org/konsole/a70ff34d28e061bec33513c21fa710f426721fd0

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

[krita] [Bug 384067] New: Internal canvas freezes up and is completely unusable when the text vector tool is used.

[Isa]

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

Bug ID: 384067
   Summary: Internal canvas freezes up and is completely unusable
when the text vector tool is used.
   Product: krita
   Version: 3.2.0
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Vector Objects and Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: isa...@live.com
  Target Milestone: ---

After you've used the text tool, adding as many text as you want, the canvas
freezes (not the GUI though, the zoom sliders and etc work fine)and is
unusable. You can't draw, pan, zoom in or out, nothing. The cursor is also
invisible in the canvas. The artistic text editor is quite unpredictable,
because under certain parameters it allowed to edit the text, but in some other
tries it didn't. The bug can only be resolved by reopening krita, and desaving
OpenGL doesn't work.

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

[kdenlive] [Bug 381110] Consistent Crashing in Kdenlive when using Custom Wipe Transition

[Michael Tunnell]

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

--- Comment #1 from Michael Tunnell  ---
Anyone interested in addressing this?

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

[kmymoney4] [Bug 358129] Changing dividend transaction to reinvested dividend transaction after import of QIF/QFX file on online banking update.

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UNMAINTAINED
 CC||lukasz.wojnilow...@gmail.co
   ||m

--- Comment #6 from NSLW  ---
KMM 4.7.1 is old and unmaintained. Please update to 4.8. Besides:

(In reply to Jack from comment #3)
> [...]  I have plenty of
> OFX transactions that import as dividend, that I change to
> reinvest-dividend, and it works fine for me.  [...]

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

[krfb] [Bug 340411] krfb does not save user settings

[Alexey Min]

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

Alexey Min  changed:

   What|Removed |Added

 CC||alexey@gmail.com

--- Comment #13 from Alexey Min  ---
(In reply to Michael Earle from comment #12)
> This is still a bug on:
> KDE Neon Latest
> Plasma Version: 5.10.4
> KDE Frameworks Version: 5.37.0
> Kernel Version 4.10.0-32-generic

And krfb version is? Both from "About.." window and from package manager?

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

[digikam] [Bug 383989] Cannot create panoramas

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.7.0

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

[Breeze] [Bug 381407] SDDM's Breeze theme should have a prettier background than just a flat blue color

[bugzilla_noreply]

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

matheus4...@hotmail.com changed:

   What|Removed |Added

 CC||matheus4...@hotmail.com

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

[kmymoney4] [Bug 363824] Crash when i save a new budget report

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 CC||lukasz.wojnilow...@gmail.co
   ||m
 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from NSLW  ---
KMM 4.7.2 is old and unmaintained. Please update to 4.8. There is no problem on
master version.

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

[kmymoney4] [Bug 343291] backup fail

[NSLW]

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

NSLW  changed:

   What|Removed |Added

Product|kmymoney|kmymoney4
  Component|General |general
 CC||lukasz.wojnilow...@gmail.co
   ||m

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

[kmymoney] [Bug 345113] KMyMoney crashes when trying to retrieve deleted account details

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||lukasz.wojnilow...@gmail.co
   ||m

--- Comment #2 from NSLW  ---
(In reply to Thomas Baumgart from comment #1)
> This looks like an AqBanking problem to me[...]

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