https://bugs.kde.org/show_bug.cgi?id=413893
Bug ID: 413893
Summary: Crash, when transparency mask is added to filter layer
and manipulated
Product: krita
Version: 4.2.7.1
Platform: Mint (Ubuntu based)
OS: Li
https://bugs.kde.org/show_bug.cgi?id=371831
--- Comment #6 from Marcus Christopher ---
I just searched for this issue and found this thread:
http://lists.qt-project.org/pipermail/interest/2015-September/018694.html
So, sorry for posting this problem here. It seems, this has been a
long-standing
https://bugs.kde.org/show_bug.cgi?id=371831
--- Comment #4 from Marcus Christopher ---
Thanks for your help.
I just installed gwenview (based on Qt 5.5.1) for testing this. Yes, indeed, I
do have the same problem there. What does that mean for my system?
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=371831
--- Comment #2 from Marcus Christopher ---
Yes, I have the same problem with all print functions. Do I have to install
anything else (like another Qt library) to make this work in Qt5?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=368734
--- Comment #11 from Marcus Christopher ---
Any news on this? Can anyone confirm the phenomenon that I'm describing?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371831
Bug ID: 371831
Summary: Digikam 5 missing Printer Driver Properties in Image
Printing Dialog
Product: digikam
Version: 5.2.0
Platform: Mint (Ubuntu based)
OS: Linu
https://bugs.kde.org/show_bug.cgi?id=368734
--- Comment #10 from Marcus Christopher ---
Thanks for your help.
Ok, so I removed literally *everything* (configuration files, databases etc.)
that had to do with digikam (version 5.1) and started with a fresh install.
- Started digikam.
- digikam
https://bugs.kde.org/show_bug.cgi?id=368734
--- Comment #8 from Marcus Christopher ---
- Removed all configuration files, and all databases.
- Started from scratch (version 5.1) and let Digikam import the files in one
directory tree.
- Changed nothing in the configuration.
- Opened the tag
https://bugs.kde.org/show_bug.cgi?id=368734
--- Comment #7 from Marcus Christopher ---
Hmm, I now removed the old database files and let Digikam create new ones. Same
problem! Should I also deleted the configuration directory?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=368734
--- Comment #6 from Marcus Christopher ---
Alright, thanks. Creating a new database shouldn't be a problem. However... Is
there a way to transfer my tag hierarchy (a controlled vocabulary containing
hundreds of tags) from the old database to th
https://bugs.kde.org/show_bug.cgi?id=368734
--- Comment #4 from Marcus Christopher ---
I suppose you mean the options that are activated for metadata in the
preferences. Okay... the following options are currently ticked in Configure >
Metadata > Behavior (I also tried other configuration
https://bugs.kde.org/show_bug.cgi?id=368734
--- Comment #2 from Marcus Christopher ---
I didn't change the default that was defined by the software, i.e. SQLite.
Would you suggest I try a different one?
Marcus
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368734
Bug ID: 368734
Summary: Moving a hierarchy of tags (a tag with subtags)
doesn't work and can lead to losing the complete
hierarchy
Product: digikam
Version: 5.1.0
13 matches
Mail list logo