https://bugs.kde.org/show_bug.cgi?id=436318
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=419171
Bug ID: 419171
Summary: tagging multiple images at once broken with commit
"modified CoreDB to perform recordChangeSet operation
on tags"
Product: digikam
Version: unspe
https://bugs.kde.org/show_bug.cgi?id=386098
--- Comment #15 from Johannes Hirte ---
I haven't seen this crash for a long time. So I think we can consider it as
fixed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409440
Johannes Hirte changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=409440
--- Comment #4 from Johannes Hirte ---
(In reply to Kai Uwe Broulik from comment #3)
> That patch will just leak the instance. A proper fix would be in
> KModifierKeyInfo.
Yes, I've mixed something up when reading the code.
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=409440
--- Comment #2 from Johannes Hirte ---
possible fix
diff --git a/src/eventfilter.cpp b/src/eventfilter.cpp
index 62dc724e..5ad1d514 100644
--- a/src/eventfilter.cpp
+++ b/src/eventfilter.cpp
@@ -32,7 +32,7 @@
LaTeXEventFilter::LaTeXEventFilter
https://bugs.kde.org/show_bug.cgi?id=409440
--- Comment #1 from Johannes Hirte ---
the bad behaviour was introduced with this change in kguiaddons:
commit 0fe2990dbad992a4925a7b7bee09b1cdfbe5a7a7
Author: Aleix Pol
Date: Fri Jun 21 15:57:22 2019 +0200
Move to runtime the decision to use
https://bugs.kde.org/show_bug.cgi?id=409440
Bug ID: 409440
Summary: Kile crash when closing files
Product: kile
Version: master
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: crash
https://bugs.kde.org/show_bug.cgi?id=407454
--- Comment #4 from Johannes Hirte ---
added review request https://phabricator.kde.org/D21562
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407454
--- Comment #3 from Johannes Hirte ---
This can't work. s_cookieJar is declared static, but QWebEngineProfile *prof is
set as parent QObject, that will try to delete it on shutdown. Following patch
fixed it for me:
diff --git a/webenginepar
https://bugs.kde.org/show_bug.cgi?id=407454
--- Comment #2 from Johannes Hirte ---
workaround: disabling Synchronize cookies between QWebEngine and KCookieServer
diff --git a/webenginepart/src/webenginepart.cpp
b/webenginepart/src/webenginepart.cpp
index bfd16ff4a..eaadda781 100644
--- a
https://bugs.kde.org/show_bug.cgi?id=406895
--- Comment #7 from Johannes Hirte ---
(In reply to tcanabrava from comment #6)
> Created attachment 120028 [details]
> attachment-29619-0.html
>
> This is a different bug, unrelated to shortcuts
>
Is there already a bugreport or shou
https://bugs.kde.org/show_bug.cgi?id=406895
Johannes Hirte changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=407454
--- Comment #1 from Johannes Hirte ---
Created attachment 120004
--> https://bugs.kde.org/attachment.cgi?id=120004&action=edit
full crash log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407454
Bug ID: 407454
Summary: konqueror crash on shutdown
Product: konqueror
Version: Git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priorit
https://bugs.kde.org/show_bug.cgi?id=400983
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=404893
--- Comment #3 from Johannes Hirte ---
Just for info, I have the bug with Gentoo:
Qt5: 5.12.1
KF5: git master (>v5.55.0-rc1)
Plasma: git master (>v5.15.0)
Digikam: 6.0.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404893
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=386098
--- Comment #12 from Johannes Hirte ---
Last crashes I've seen were without a backtrace, so I can't say what happened.
I've added kcrash for catching a trace when the next crash happens. Hopefully
this gives some more infos.
--
You are
https://bugs.kde.org/show_bug.cgi?id=386098
--- Comment #7 from Johannes Hirte ---
Ok, just starting digikam spits me 47 ThreadSanitizer warnings. Maybe false
positives, cause not all code was instrumented. For Example, glib and dbus
wasn't compiled with -fsanitize=thread. I've stopped
https://bugs.kde.org/show_bug.cgi?id=386098
--- Comment #6 from Johannes Hirte ---
Yes, it's a very nasty bug, and I'm still not sure if this may be a bug in Qt
or some other component. But I've seen this only with digikam.
And it smells like some race condition to me. In the
https://bugs.kde.org/show_bug.cgi?id=386098
--- Comment #4 from Johannes Hirte ---
(In reply to caulier.gilles from comment #3)
> Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle
> available here :
>
> https://files.kde.org/digikam/
>
> Gilles Caulie
https://bugs.kde.org/show_bug.cgi?id=386098
--- Comment #2 from Johannes Hirte ---
(In reply to Denis Kurz from comment #1)
> Johannes, do you recall the Qt version you experienced this with? If it was
> before Qt 5.8, someone might want to consider if this was caused by a Qt bug
>
https://bugs.kde.org/show_bug.cgi?id=387373
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=386659
--- Comment #12 from Johannes Hirte ---
see https://phabricator.kde.org/D8777
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386659
--- Comment #8 from Johannes Hirte ---
(In reply to Michail Vourlakos from comment #7)
> (In reply to Rik Mills from comment #6)
> > (In reply to Michail Vourlakos from comment #5)
> > > in Neon Stable edition plasma-desktop
https://bugs.kde.org/show_bug.cgi?id=386659
Bug ID: 386659
Summary: plasma-desktop/kcms/phonon/ broken: undefined
reference to `pa_stream_is_suspended'
Product: Phonon
Version: unspecified
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=386098
Bug ID: 386098
Summary: crash when adding pictures to a running digikam
Product: digikam
Version: 5.8.0
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
S
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #20 from Johannes Hirte ---
Had another segfault, this time outside of a gdb session, so I don't have a
backtrace. It happened when moving pictures with dolphin into a collection
during a running digikam. So I'm not sure this i
https://bugs.kde.org/show_bug.cgi?id=370223
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #18 from Johannes Hirte ---
Looks good, I wasn't able to reproduce a crash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385768
Johannes Hirte changed:
What|Removed |Added
Platform|Other |Gentoo Packages
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=385768
Johannes Hirte changed:
What|Removed |Added
Version|unspecified |git master
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=385768
Bug ID: 385768
Summary: segfault on parsing project: in
clang::Decl::setInvalidDecl(bool) () from
/usr/lib64/llvm/5/lib64/../lib64/libclangAST.so.5
Product: kdevelop
Ver
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #11 from Johannes Hirte ---
And now SIGSEGV is back. The backtrace is similar to the one above. I can
provide it, if you need it. Here is the workflow, how I reproduced it:
1. put 30 images into an album
2. rename the images crashtest-001
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #10 from Johannes Hirte ---
(In reply to Johannes Hirte from comment #9)
> I can confirm, that the error changed from SIGSEGV to SIGBUS. I can't
> reproduce the error reliable, but when it happens, it is SIGBUS now.
Okay, I hav
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #9 from Johannes Hirte ---
I can confirm, that the error changed from SIGSEGV to SIGBUS. I can't reproduce
the error reliable, but when it happens, it is SIGBUS now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #8 from Johannes Hirte ---
(In reply to Maik Qualmann from comment #7)
> Created attachment 108290 [details]
> ImageInfo.patch
>
> Johannes,
>
> can you apply this patch and test it? This crash I have never seen or
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #6 from Johannes Hirte ---
(In reply to Johannes Hirte from comment #5)
> (In reply to Maik Qualmann from comment #4)
> > I do not see an probleme in the ImageInfo::filePath() function. And it
> > crashes in system or Qt. Whi
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #5 from Johannes Hirte ---
(In reply to Maik Qualmann from comment #4)
> I do not see an probleme in the ImageInfo::filePath() function. And it
> crashes in system or Qt. Which distribution do you use?
>
> Maik
I'm using
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #3 from Johannes Hirte ---
Btw. I've seen those segfaults and hangs on renaming pictures several times
before. It's only the first time I digged into this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385592
--- Comment #2 from Johannes Hirte ---
(In reply to caulier.gilles from comment #1)
> Which digiKam version do you use exactly ?
>
> Gilles Caulier
>From git at commit 841cd2947cccfff1b541e97e5a626ccdc2cef979
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=385592
Bug ID: 385592
Summary: digikam segfaults occasionally, when renaming/moving
multiple images
Product: digikam
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=325224
--- Comment #74 from Johannes Hirte ---
I can confirm this with the latest git sources. Tested with Open XChange,
pushing to the server works, pull doesn't.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=325224
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=376149
Johannes Hirte changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #13 from Johannes Hirte ---
(In reply to Kevin Funk from comment #12)
> Sorry, one remark missing: if you use -DCMAKE_BUILD_TYPE=Release or
> ...=RelWithDebInfo, NDEBUG will be defined.
clang/llvm was build with -DCMAKE_BUIL
https://bugs.kde.org/show_bug.cgi?id=376149
Johannes Hirte changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #7 from Johannes Hirte ---
(In reply to Kevin Funk from comment #6)
> Note: We don't recommend to build Clang/LLVM with assertions enabled. It
> triggers on a lot of issues in our experience, most of them non-fatal for us.
>
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #5 from Johannes Hirte ---
two clang bugreports that seem related:
https://bugs.llvm.org//show_bug.cgi?id=22938
https://bugs.llvm.org//show_bug.cgi?id=21905
Still not sure if this is a clang-bug or kdevelop is miss-using something. At
https://bugs.kde.org/show_bug.cgi?id=376149
Johannes Hirte changed:
What|Removed |Added
Summary|segfault in |KDevelop crash during
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #4 from Johannes Hirte ---
Since llvm/clang-4.0 is released now, this problem becomes urgent. The
background parser fails now with different projects. As far as I can see it's
always the same assert:
[KCrash Handler]
#6 __GI_raise
https://bugs.kde.org/show_bug.cgi?id=376815
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=376505
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=367575
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #3 from Johannes Hirte ---
I've noticed that the segfault happened with llvm/clang-4.0 branch. Before the
bugreport I downgraded it to 3.9.1 but didn't realize that there were some
leftovers kdevelop was still using. After cleanin
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #2 from Johannes Hirte ---
Removed the cache (again). Now the crash is another (what I've observed first):
Thread 18 "Queue(0x1ebb850" received signal SIGABRT, Aborted.
[Switching to Thread 0x7f1d07fff700 (LWP 15332)]
0x
https://bugs.kde.org/show_bug.cgi?id=376149
Bug ID: 376149
Summary: segfault in KDevelop::TypeSystem::dynamicSize
(this=0x7fda2af2c100
, data=...)
Product: kdevelop
Version: git master
Platform: Gentoo P
https://bugs.kde.org/show_bug.cgi?id=372062
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=375195
Bug ID: 375195
Summary: Pass -fno-operator-names when supported breaks build
of several packages
Product: extra-cmake-modules
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=363697
--- Comment #16 from Johannes Hirte ---
(In reply to swatilodha27 from comment #15)
> Is it possible to already have a "Fake Album" row when the DB is initially
> created?
> In the DB schema file, adding a query:
> //
> INSERT
https://bugs.kde.org/show_bug.cgi?id=364797
Johannes Hirte changed:
What|Removed |Added
Platform|Other |Gentoo Packages
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=364797
Bug ID: 364797
Summary: after editing metadata, rename hangs
Product: digikam
Version: 5.0.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=363697
--- Comment #13 from Johannes Hirte ---
Patch works for me with MySQL/MariaDB.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363697
--- Comment #8 from Johannes Hirte ---
(In reply to Johannes Hirte from comment #7)
> Of course, foreign key checks is part of the problem. Disabling this with:
>
> d->db->execSql(QString("SET FOREIGN_KEY_CHECKS = 0;"
https://bugs.kde.org/show_bug.cgi?id=363697
--- Comment #7 from Johannes Hirte ---
Of course, foreign key checks is part of the problem. Disabling this with:
d->db->execSql(QString("SET FOREIGN_KEY_CHECKS = 0;"));
d->db->execSql(QString("UPDATE Albums SE
https://bugs.kde.org/show_bug.cgi?id=363697
--- Comment #6 from Johannes Hirte ---
some more debugging:
void CoreDB::makeStaleAlbum(int albumID) does not work. After this function,
albumRoot of the deleted album has to be 0 and relativePath has to be prefixed
with "1-", where 1 is the
https://bugs.kde.org/show_bug.cgi?id=363697
--- Comment #5 from Johannes Hirte ---
After some digging into the code, I've seen that deleted images are finally
removed from the db. It's just done asynchronously, deferred for some days:
bool CollectionScanner::checkDel
https://bugs.kde.org/show_bug.cgi?id=363697
--- Comment #3 from Johannes Hirte ---
As my report is marked as a duplicate of this, please see my description there:
https://bugs.kde.org/show_bug.cgi?id=364614
It't not only the album shouldn't be visible anymore after deletion, th
https://bugs.kde.org/show_bug.cgi?id=364614
Bug ID: 364614
Summary: images/albums not deleted in database when
deleting/moving in digikam
Product: digikam
Version: 5.0.0
Platform: Gentoo Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=364141
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=352278
Johannes Hirte changed:
What|Removed |Added
CC||johannes.hirte@datenkhaos.d
https://bugs.kde.org/show_bug.cgi?id=360171
Bug ID: 360171
Summary: orphaned and hanging kf5/plasma-processes after
session end
Product: frameworks-kded
Version: unspecified
Platform: Other
OS: other
https://bugs.kde.org/show_bug.cgi?id=358588
Bug ID: 358588
Summary: backlight not restored properly, after it was reduced
on inactivity
Product: Powerdevil
Version: unspecified
Platform: Gentoo Packages
OS:
74 matches
Mail list logo