[digikam] [Bug 487822] New: "Wipe all tags from Database only" crashes digiKam

2024-05-30 Thread CM
https://bugs.kde.org/show_bug.cgi?id=487822

Bug ID: 487822
   Summary: "Wipe all tags from Database only" crashes digiKam
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Tags-Manager
  Assignee: digikam-bugs-n...@kde.org
  Reporter: carlo.m...@outlook.com
  Target Milestone: ---

SUMMARY
"Wipe all tags from Database only" crashes digiKam

STEPS TO REPRODUCE
1. Go to Tag Manager
2. Click Sync Export
3. Click Wipe all tags from Database only

OBSERVED RESULT
The wipe seems to complete, but it crashes digiKam

EXPECTED RESULT
The wipe should complete, but keep digiKam running

SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[digikam] [Bug 444394] Rejected face suggestions reappear for the same person the next time recognition is run

2024-05-30 Thread CM
https://bugs.kde.org/show_bug.cgi?id=444394

CM  changed:

   What|Removed |Added

 CC||carlo.m...@outlook.com

--- Comment #7 from CM  ---
I'd like this feature also.

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

[digikam] [Bug 487821] New: Keep People/Face Tag, but Mark Them to be Ignored in Further Recognition Suggestions

2024-05-30 Thread CM
https://bugs.kde.org/show_bug.cgi?id=487821

Bug ID: 487821
   Summary: Keep People/Face Tag, but Mark Them to be Ignored in
Further Recognition Suggestions
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Faces-Recognition
  Assignee: digikam-bugs-n...@kde.org
  Reporter: carlo.m...@outlook.com
  Target Milestone: ---

I understand there is an "Ignored" function.

What I'd like to have is the ability to mark a face or person tag so that the
app will no longer try to recognize the face and make further suggestions as
potential matches. I want to keep the tags therefore simply putting them as
"Ignored" is not ideal.

Assume the scenario where the person has passed away and no more photos of that
person are expected. 

I've been able to achieve the same effect by manually editing the Sqlite
database and delete certain rows from the 'FaceMatrices' table.

Can a similar function be added?

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

[digikam] [Bug 470694] Some Face Regions are Rotated

2023-10-20 Thread CM
https://bugs.kde.org/show_bug.cgi?id=470694

--- Comment #5 from CM  ---
Gilles Caulier, are you saying or asking?

FYI, I've since confirmed that this problem appears on photos taken on iPhones
(12 Pro Max and XS Max for reference). I am not 100% sure, but appears to be
prevalent on portrait photos.

I wish there was a way to rotate ONLY the tags since they appear to be correct
if only rotated 90/270 deg.

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

[digikam] [Bug 470694] Some Face Regions are Rotated

2023-06-08 Thread CM
https://bugs.kde.org/show_bug.cgi?id=470694

--- Comment #3 from CM  ---
Learning new things. After clearing the faces on the photos and having digiKam
find faces, it's behaving as expected (correctly).

I think the existing face tags must have been there already (added by the
iPhone).

regions/mwg-rs:AppliedToDimensions/stDim:w
regions/mwg-rs:AppliedToDimensions/stDim:h
(and several others)

I'll clear and rescan as suggested.

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

[digikam] [Bug 470694] Some Face Regions are Rotated

2023-06-07 Thread CM
https://bugs.kde.org/show_bug.cgi?id=470694

--- Comment #2 from CM  ---
I have to confirm later, but it also appears that digiKam detects faces, but
the Face Regions are oriented as if the photos are 90deg or 270deg rotated. The
photos are ones never touched by Windows Photo Gallery.

Is it possible digiKam is showing the Face Regions with respect to an
orientation flag in metadata or some other assumption?

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

[digikam] [Bug 470694] New: Some Face Regions are Rotated

2023-06-06 Thread CM
https://bugs.kde.org/show_bug.cgi?id=470694

Bug ID: 470694
   Summary: Some Face Regions are Rotated
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Faces-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: carlo.m...@outlook.com
  Target Milestone: ---

SUMMARY
I have photos that have been face tagged with Windows Photo Gallery. Now that
I'm using digiKam, I just noticed that for some photos the Face Regions are
rotated 90 or 180 degrees. I assume there are others rotated 270 degrees also.


STEPS TO REPRODUCE
1. Add Photos to digiKam 
2. Browse People Tags

OBSERVED RESULT
Some People Tags show portions of the photo that don't have faces, but clearly
map to faces if the Face Regions are rotated.

EXPECTED RESULT
digiKam should recognize when the Face Regions are potentially rotated and are
not or no longer over actual faces.

SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kate] [Bug 387100] please restore tab order and zoom levels when opening session

2020-04-30 Thread cm
https://bugs.kde.org/show_bug.cgi?id=387100

--- Comment #4 from cm  ---
As Bug 419778 mentions, there is still a tab order issue.
This bug also talks about zoom level, and that's not the case.

Is there some fix to the tab order issue ?. Kate is still opening a session
with some kind of random tab order, not as I left them.

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

[kate] [Bug 419778] New: Session files, tabs order

2020-04-07 Thread cm
https://bugs.kde.org/show_bug.cgi?id=419778

Bug ID: 419778
   Summary: Session files, tabs order
   Product: kate
   Version: 17.12.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: c...@eldestino.es
  Target Milestone: ---

SUMMARY
Can not keep the files order in the tabs as previously ordered. Session reorder
the tabs when starting Kate again.

STEPS TO REPRODUCE
1. Open several files and move the file tabs as your wish 
2. Save session and close
3. Load the session again Kate has re-ordered the tabs. No way to keep the tabs
as you set manually

OBSERVED RESULT
Kate has re-ordered the tabs. The manual order is not preserved

EXPECTED RESULT
Keep the tabs order as you set manually

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 347195] Panel disappears after an external monitor is unplugged

2016-06-17 Thread CM via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=347195

CM <rosencra...@gmx.net> changed:

   What|Removed |Added

 CC||rosencra...@gmx.net

--- Comment #15 from CM <rosencra...@gmx.net> ---
I'm getting the following behaviour: 
Laptop with either µHDMI->VGA or µHDMI->HDMI external monitor configuration.
Kubuntu 16.04 with Plasma 5.6.4 from backports.
Panel pop-ups on wrong monitor or not showing at all, sometimes panel moving to
the secondary monitor. krunner runs on the secondary display.
This happens only  if I change anything in the kscreen virtual display
arrangement. I also had the problem of my primary screen being black with the
mouse stuck at the top edge when I didn't have the µHDMI dongle attached. 
Things go back to normal if I delete everything in ~/.local/share/kscreen and
restart sddm. 
Here's an example of a file in ~/.local/share/kscreen named
0a4880943d4a3dca33a04c4f97f64b64, there are usually a couple of them.

[
{
"enabled": true,
"id": "e4c60c052c579303ac024f21f1683d98",
"metadata": {
"fullname": "xrandr-unknown",
"name": "eDP1"
},
"mode": {
"refresh": 60.00103759765625,
"size": {
"height": 1080,
"width": 1920
}
},
"pos": {
"x": 0,
"y": 1080
},
"primary": true,
"rotation": 1
},
{
"enabled": true,
"id": "9f7021b9c1848e2544d27a4f656cf07d",
"metadata": {
"fullname": "xrandr-D09VR33E1KVL",
"name": "HDMI1"
},
"mode": {
"refresh": 60,
"size": {
"height": 1080,
"width": 1920
}
},
"pos": {
"x": 0,
"y": 0
},
"primary": false,
"rotation": 1
}
]

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