https://bugs.kde.org/show_bug.cgi?id=348171
Ferry changed:
What|Removed |Added
CC||ft...@telfort.nl
--- Comment #2 from Ferry ---
This
https://bugs.kde.org/show_bug.cgi?id=363788
Ferry changed:
What|Removed |Added
CC||ft...@telfort.nl
--- Comment #11 from Ferry ---
This
https://bugs.kde.org/show_bug.cgi?id=467299
Bug ID: 467299
Summary: Screenlocker becomes active on wakeup
Classification: Plasma
Product: kscreenlocker
Version: 5.25.5
Platform: Kubuntu
OS: Linux
Status: REPORTE
https://bugs.kde.org/show_bug.cgi?id=455805
Ferry <06f13.41...@mailbox.org> changed:
What|Removed |Added
CC||06f13.41...@mailb
https://bugs.kde.org/show_bug.cgi?id=455805
--- Comment #6 from Ferry <06f13.41...@mailbox.org> ---
(In reply to Maik Qualmann from comment #5)
> No, this change does not affect adding GPX data either. Can you describe
> your problem when adding GPX data?
> There is a change due
https://bugs.kde.org/show_bug.cgi?id=455805
--- Comment #7 from Ferry <06f13.41...@mailbox.org> ---
I did not find the bug, but my digikam 7.7.0 works again regarding geodata
entry in photos from GMX files. No further action is required. Sorry for my
false report.
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=429121
Bug ID: 429121
Summary: No context menu when drag and drop file / directory
from Dolfin
Product: konsole
Version: 20.08.2
Platform: Ubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=429121
--- Comment #3 from Ferry ---
I see. Something is mixed up with the profiles.
I used Settings->Manage Profile->default and
"edit"->Mouse->Miscellaneous->uncheck
default is the checked profile (and the only visible profile
https://bugs.kde.org/show_bug.cgi?id=429121
Ferry changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=429346
Bug ID: 429346
Summary: Rotating and cropping: Concentration of the cropping
frame on the real image area.
Product: digikam
Version: 7.1.0
Platform: Microsoft Windows
https://bugs.kde.org/show_bug.cgi?id=429346
--- Comment #2 from Ferry <06f13.41...@mailbox.org> ---
Thanks Maik, the rotation tool is much more powerful than I expected. My
problem is now solved.
Am 2020-11-19 um 19:27 schrieb Maik Qualmann:
> https://bugs.kde.org/show_bug.cgi?
https://bugs.kde.org/show_bug.cgi?id=374890
Ferry changed:
What|Removed |Added
CC||ferry.t...@elsinga.info
--- Comment #25 from Ferry
https://bugs.kde.org/show_bug.cgi?id=386238
--- Comment #4 from Ferry ---
Unfortunately (or fortunately?) I never had the issue again since removing the
autosave file.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422347
Bug ID: 422347
Summary: Program crash when clone repair
Product: digikam
Version: 7.0.0
Platform: MS Windows
OS: Microsoft Windows
Status: REPORTED
Severity: maj
https://bugs.kde.org/show_bug.cgi?id=423004
Bug ID: 423004
Summary: Stringent up or down order for croping shapes
Product: digikam
Version: 7.0.0
Platform: MS Windows
OS: Other
Status: REPORTED
Severity: n
https://bugs.kde.org/show_bug.cgi?id=422347
--- Comment #2 from Ferry <06f13.41...@mailbox.org> ---
The error (id = 422347) has not yet been completely corrected in 'Version 7.0.0
rc'. I apologize because I forgot to say that I am using a 'Logitech Anywhere
MX' mouse, w
https://bugs.kde.org/show_bug.cgi?id=423004
--- Comment #3 from Ferry <06f13.41...@mailbox.org> ---
Created attachment 129393
--> https://bugs.kde.org/attachment.cgi?id=129393&action=edit
Falling or rising trend of formats instead of alternating landscape / portrait
Ok, your s
https://bugs.kde.org/show_bug.cgi?id=422347
--- Comment #4 from Ferry <06f13.41...@mailbox.org> ---
PROBLEM SOLVED
On the contrary to my message (Comment # 2), I accidentally installed the wrong
version.
The digikam version '7.0.0 rc' works correctly with regard to the lateral im
https://bugs.kde.org/show_bug.cgi?id=40892
--- Comment #2 from Ferry ---
Unfortunately this is still not implemented in 17.12.3 (Kubuntu Bionic).
I'll try to make the case for this functionality: on a shared file server
(obviously sharing with Windows users), just giving the group read/
https://bugs.kde.org/show_bug.cgi?id=368796
Ferry <06f13.41...@mailbox.org> changed:
What|Removed |Added
Version|5.8.0 |5.9.0
https://bugs.kde.org/show_bug.cgi?id=368796
--- Comment #8 from Ferry <06f13.41...@mailbox.org> ---
(In reply to hardy.public from comment #7)
> (In reply to Ferry from comment #6)
> > Capion input is not possible with digikam 5.9; I can tag only (German
> > version 5.9). If
https://bugs.kde.org/show_bug.cgi?id=368796
--- Comment #12 from Ferry <06f13.41...@mailbox.org> ---
Created attachment 111876
--> https://bugs.kde.org/attachment.cgi?id=111876&action=edit
US version
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368796
--- Comment #13 from Ferry <06f13.41...@mailbox.org> ---
Created attachment 111877
--> https://bugs.kde.org/attachment.cgi?id=111877&action=edit
DE version
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368796
--- Comment #14 from Ferry <06f13.41...@mailbox.org> ---
(In reply to caulier.gilles from comment #9)
> Really... Can you take a screenshot to see exactly where is the problem ?
I found the problem: There are inproper namings in the German ve
"de_CH", "es_PE", "fr_CH", "es_GT", "es_PR", "sv_FI", "en_CA", "es_CL",
"es_CU", "es_DO", "es_SV", "es_CR", "de_LU", "nl_BE", "es_PY", "es_
https://bugs.kde.org/show_bug.cgi?id=386238
--- Comment #1 from Ferry ---
I just upgraded to kubuntu backport ppa:
~$ kmail -v
kmail2 5.5.3
Still kontact (and kmail) crash on each start. I think it tries to recover an
e-mail and then crashes again and again. How do I stop this?
Starting from
https://bugs.kde.org/show_bug.cgi?id=386238
Ferry changed:
What|Removed |Added
CC||ft...@telfort.nl
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=386238
--- Comment #2 from Ferry ---
OK I managed to work around this in the following way:
- I went into ~ferry/.local/share/kmail2/autosave
- removed the file there
Started kmail, problem gone.
May I suggest that if kmail is repeatedly trying to recover
https://bugs.kde.org/show_bug.cgi?id=384891
Ferry changed:
What|Removed |Added
CC||ft...@telfort.nl
--- Comment #5 from Ferry ---
There
https://bugs.kde.org/show_bug.cgi?id=377505
Bug ID: 377505
Summary: Let Kate automatically reload
Product: kate
Version: 16.04
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Pri
https://bugs.kde.org/show_bug.cgi?id=440874
Ferry changed:
What|Removed |Added
CC||k...@kn0x.org
--- Comment #4 from Ferry ---
*** Bug
https://bugs.kde.org/show_bug.cgi?id=440874
Ferry changed:
What|Removed |Added
CC||ferry.t...@elsinga.info
--- Comment #3 from Ferry
https://bugs.kde.org/show_bug.cgi?id=444108
Ferry changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=448985
Bug ID: 448985
Summary: In Digital Clock 3.0 - Custom date format shows
incorrect month - M01 instead of Jan
Product: Active Window Control
Version: unspecified
Platform: openSUSE
https://bugs.kde.org/show_bug.cgi?id=448985
--- Comment #3 from Bruce Ferry ---
Created attachment 145810
--> https://bugs.kde.org/attachment.cgi?id=145810&action=edit
Screenshot showing the config and what I see
Should have attached this before.
I'm in the eastern US time
https://bugs.kde.org/show_bug.cgi?id=448985
Bruce Ferry changed:
What|Removed |Added
Resolution|WAITINGFORINFO |NOT A BUG
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=326803
--- Comment #2 from Ferry ---
Can be closed
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344319
Ferry changed:
What|Removed |Added
CC||ft...@telfort.nl
--- Comment #25 from Ferry ---
To my
https://bugs.kde.org/show_bug.cgi?id=346961
Ferry changed:
What|Removed |Added
CC||ft...@telfort.nl
--- Comment #33 from Ferry ---
I
https://bugs.kde.org/show_bug.cgi?id=346961
--- Comment #34 from Ferry ---
I tried the script above and with kscreen2 disabled. That didn't work well as I
have 2 1920x1200 monitors and both monitors showed the same thing, except
vertically displayed on one.
After I enabled kscreen2 (wi
https://bugs.kde.org/show_bug.cgi?id=353987
--- Comment #5 from Ferry ---
In my case updating owncloud to a bit higher point release solved the issue.
--
You are receiving this mail because:
You are watching all bug changes.
41 matches
Mail list logo
