https://bugs.kde.org/show_bug.cgi?id=480277
--- Comment #4 from Ritesh Raj Sarraf ---
Dear Maik,
THank you so much for your swift responses. I'm glad this is all sorted out
already. I verified the fixes with the latest AppImage bundle:
digiKam-8.3.0-20240125T080925-x86-64.appimage
And all
https://bugs.kde.org/show_bug.cgi?id=480277
Ritesh Raj Sarraf changed:
What|Removed |Added
Platform|Other |Flatpak
--
You are receiving this mail
: 0
Color Label : 0
Categories : PeopleFamilyKiran
Santosh SarrafPriya Raj
SarrafRitesh Raj SarrafAnshika Raj Sarraf
Tags List : People/Family/Anshika Raj Sarraf,
People/Family/Ritesh Raj Sarraf, People/Family/Priya Raj Sarraf,
People
https://bugs.kde.org/show_bug.cgi?id=479182
--- Comment #3 from Ritesh Raj Sarraf ---
(In reply to Maik Qualmann from comment #2)
> What is a “remote storage” to you, an FTP/HTTP server? Or a mounted SMB
> share? You can add images of a mounted SMB share using “Add images” via the
> im
https://bugs.kde.org/show_bug.cgi?id=479182
--- Comment #1 from Ritesh Raj Sarraf ---
Remote Storage Import Window
* https://docs.digikam.org/en/import_tools/remote_import.html
Camera Device Import Window
* https://docs.digikam.org/en/import_tools/camera_import.html
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=479182
Bug ID: 479182
Summary: Organizer features for Import from Remote Storage
Classification: Applications
Product: digikam
Version: 8.2.0
Platform: Appimage
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=328504
--- Comment #3 from Ritesh Raj Sarraf ---
(In reply to Ritesh Raj Sarraf from comment #2)
> KBreakOut
> Version 22.08.3
>
> THe bug is still valid and spoils the entire experience of the game.
On 22.12.0, The experience has substantia
https://bugs.kde.org/show_bug.cgi?id=328504
Ritesh Raj Sarraf changed:
What|Removed |Added
CC||kde-b...@researchut.com
Ever confirmed
https://bugs.kde.org/show_bug.cgi?id=426293
--- Comment #29 from Ritesh Raj Sarraf ---
(In reply to Nicolas Fella from comment #28)
> These are new symptoms, please open a new report for this
Great. You want to let go of all the information and context that was reported
with the bug rep
https://bugs.kde.org/show_bug.cgi?id=426293
Ritesh Raj Sarraf changed:
What|Removed |Added
CC||kde-b...@researchut.com
Status
https://bugs.kde.org/show_bug.cgi?id=419728
--- Comment #30 from Ritesh Raj Sarraf ---
I have just tested with the latest kwin. While the issue has significantly
improved, it is not fixed completely.
The applications do not crash any more. But most KDE applications (dolphin,
konsole) which were
https://bugs.kde.org/show_bug.cgi?id=436876
--- Comment #1 from Ritesh Raj Sarraf ---
It could possibly be that the Facial Recognition library detects the faces in
video files too, but is not able to write facial data to the file.
I don't know how it is supposed to write but in a generic term
https://bugs.kde.org/show_bug.cgi?id=436876
Bug ID: 436876
Summary: cannot write exif data to mp4 video files
Product: digikam
Version: 7.2.0
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=403409
Ritesh Raj Sarraf changed:
What|Removed |Added
CC||kde-b...@researchut.com
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=434279
--- Comment #8 from Ritesh Raj Sarraf ---
For this bug's complete information, I would like to add that the issue is
neither with Plasama or Latte-Dock.
The problem is with the web-portal that has a bunch of specific requirements to
get
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #34 from Ritesh Raj Sarraf ---
(In reply to Ritesh Raj Sarraf from comment #20)
> (In reply to Ritesh Raj Sarraf from comment #19)
> > @Gilles Caulier
> >
> > Here's a link to Google Motion Photo.
> >
&g
https://bugs.kde.org/show_bug.cgi?id=419728
--- Comment #26 from Ritesh Raj Sarraf ---
(In reply to Ritesh Raj Sarraf from comment #25)
> I'm hit by this issue. And this is on the latest as of today, which is:
>
> Operating System: Debian GNU/Linux
> KDE Plasma Version: 5.21.3
>
https://bugs.kde.org/show_bug.cgi?id=419728
Ritesh Raj Sarraf changed:
What|Removed |Added
CC||kde-b...@researchut.com
--- Comment #25
https://bugs.kde.org/show_bug.cgi?id=434279
Ritesh Raj Sarraf changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UPSTREAM
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=434279
--- Comment #6 from Ritesh Raj Sarraf ---
(In reply to Michail Vourlakos from comment #1)
> Probably applet issue, close Latte add in plasma panels the same widgets and
> if the problem remains report it to Plasma.
This is something yet to try.
https://bugs.kde.org/show_bug.cgi?id=434279
--- Comment #5 from Ritesh Raj Sarraf ---
This is the weirdest of the behaviors I've seen in recent past.
When the Home WiFi was off and I was directly connected to the ISP router,
things were fine. I just got the following in the system logs
https://bugs.kde.org/show_bug.cgi?id=434279
--- Comment #2 from Ritesh Raj Sarraf ---
Looking at the logs and knowing that port.cc is not from latte-dock, it just
hit my mind that the name latte-dock in the logs could just be a red herring.
It could very well be a problem of the Chrome browser
https://bugs.kde.org/show_bug.cgi?id=434279
Bug ID: 434279
Summary: lattedock network broadcasts makes entire desktop
unresponsive
Product: lattedock
Version: git (master)
Platform: Debian unstable
OS:
https://bugs.kde.org/show_bug.cgi?id=421853
--- Comment #3 from Ritesh Raj Sarraf ---
(In reply to Maik Qualmann from comment #2)
> The refresh button not only refreshes the thumbnails, but also searches for
> new items. You can put the refresh button on the toolbar. There is a key
> co
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #20 from Ritesh Raj Sarraf ---
(In reply to Ritesh Raj Sarraf from comment #19)
> @Gilles Caulier
>
> Here's a link to Google Motion Photo.
>
> https://photos.app.goo.gl/g37hyTahF69qqQ2n6
In case Google post-processes a
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #19 from Ritesh Raj Sarraf ---
@Gilles Caulier
Here's a link to Google Motion Photo.
https://photos.app.goo.gl/g37hyTahF69qqQ2n6
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421853
--- Comment #1 from Ritesh Raj Sarraf ---
Oh!! And currently, Digikam does have the "Maintenance" path to scan new items.
But it is not a single button workflow and has many more options, which may not
be intuitive enough for novice users
https://bugs.kde.org/show_bug.cgi?id=421853
Bug ID: 421853
Summary: single button to refresh collection
Product: digikam
Version: 7.0.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=405135
Ritesh Raj Sarraf changed:
What|Removed |Added
CC||kde-b...@researchut.com
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=385726
Ritesh Raj Sarraf changed:
What|Removed |Added
CC||kde-b...@researchut.com
--- Comment #13
https://bugs.kde.org/show_bug.cgi?id=401400
--- Comment #9 from Ritesh Raj Sarraf ---
Created attachment 120084
--> https://bugs.kde.org/attachment.cgi?id=120084=edit
kate clipboard
No need to confirm for any one. It does look like kate has its own clipboard
for `vi-mode`
--
https://bugs.kde.org/show_bug.cgi?id=401400
--- Comment #8 from Ritesh Raj Sarraf ---
(In reply to Ahmad Samir from comment #7)
> In vi-mode, kate behaves like this, IIUC:
> - if you copy text via Ctrl+C or yanking (which is specific to vi-mode), you
> can paste the text with Ctrl+V (i
https://bugs.kde.org/show_bug.cgi?id=401400
--- Comment #6 from Ritesh Raj Sarraf ---
In this video, I have tried to explain the bug.
https://www.youtube.com/watch?v=sUG4FaPoStk
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401400
--- Comment #5 from Ritesh Raj Sarraf ---
(In reply to Ritesh Raj Sarraf from comment #4)
> (In reply to Ahmad Samir from comment #3)
> > Also by "vi-mode paste" you mean just using Ctrl+v, right?
>
> NO. "vi-mode pas
https://bugs.kde.org/show_bug.cgi?id=401400
--- Comment #4 from Ritesh Raj Sarraf ---
(In reply to Ahmad Samir from comment #3)
> I couldn't reproduce this issue. You're using klipper from the system tray
> widget (Configure system tray -> Clipboard).
>
Yes, I'm using klipper. I
https://bugs.kde.org/show_bug.cgi?id=401400
--- Comment #2 from Ritesh Raj Sarraf ---
(In reply to Ahmad Samir from comment #1)
> Can you still reproduce this issue?
Yes. Very very reproducible. Are you not able to reproduce it with the steps I
have outlined ?
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=401400
Bug ID: 401400
Summary: kate vi mode does not synchronize content from
clipboard
Product: kate
Version: 18.08.0
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=384807
--- Comment #15 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
I just tested 5.8 pre-build of Digikam from files.kde.org and now, even ssl
support is broken.
Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl:
QSsl
https://bugs.kde.org/show_bug.cgi?id=384807
--- Comment #12 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
(In reply to caulier.gilles from comment #11)
> QtAV, or ffmpeg codec used in background ?
>
I have no clue about this.
> Did you tried the stand alone QtAV player to
https://bugs.kde.org/show_bug.cgi?id=384807
--- Comment #10 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
I have a gut feel that QtAV has issues with h265 HEVC codec videos.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384807
--- Comment #9 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
(In reply to caulier.gilles from comment #5)
> Look here :
> https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
I tried that out and the issues are th
https://bugs.kde.org/show_bug.cgi?id=384807
--- Comment #7 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
(In reply to caulier.gilles from comment #6)
> Can you check also if media player (video) support is enabled in
> Help/Components Info dialog from digiKam ?
Yes. It
https://bugs.kde.org/show_bug.cgi?id=384807
--- Comment #4 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
(In reply to Maik Qualmann from comment #3)
> Strange, no call to the video thumbnailer in the log file. At the moment, I
> do not know why. Can you test the pre-release d
https://bugs.kde.org/show_bug.cgi?id=384807
--- Comment #2 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
(In reply to Maik Qualmann from comment #1)
> Video thumbnailer work here fine with the AppImage. Post your console output
> if processing video thumbnails.
>
>
https://bugs.kde.org/show_bug.cgi?id=384807
Bug ID: 384807
Summary: minor issues with digikam 5.7.0 AppImage bundle
Product: digikam
Version: 5.7.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=373284
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=158484
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=377597
--- Comment #7 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
It seems that the 5.5.0 release lost Keyboard Shortcuts too. Can others, who've
successfully built, confirm ?
I'm running Digikam under GNOME 3.22
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=377739
Bug ID: 377739
Summary: index.docbook:13: element link: validity error : IDREF
attribute linkend references an unknownID
"using-mainwindow-mapview"
Product: digikam
https://bugs.kde.org/show_bug.cgi?id=373572
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=373572
Bug ID: 373572
Summary: file synchronization
Product: digikam
Version: 5.3.0
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #11 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
As for the initial crash, for which the steps to reproduce I have, I'm not sure
if I have a better trace. It looks like Debian doesn't have the necessary
dbgsym symbols pa
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #10 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
I'm not sure if I have clear steps to reproduce, for this crash [1]. But, now
I've installed some more debug packages. If the crash occurs again, and I have
a better trace, I'll
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #8 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
No. I'm still on Xorg.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #6 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
I got one more crash, just now, in a different subsystem. In case you need the
full report, let me know. I have it locally.
ProcStatus:
Name: digikam
Umask: 0022
St
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #5 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
By the way, I'm seeing this not just with Album deletion, but also with
deleting Tags through Tag Manager.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #4 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
Yes. You seem to be correct. On another machine, with the same digikam
packages, I am not able to reproduce the issue with the same steps.
On the other hand, I removed the coll
https://bugs.kde.org/show_bug.cgi?id=373304
Bug ID: 373304
Summary: google picasa photo import
Product: digikam
Version: 5.3.0
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #2 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
Hello Gilles,
Yes. I was able to crash the AppImage build too.
digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digi
https://bugs.kde.org/show_bug.cgi?id=373284
Bug ID: 373284
Summary: digikam crashed with SIGSEGV in
QSortFilterProxyModel::parent()
Product: digikam
Version: 5.3.0
Platform: Debian unstable
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=332829
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=316543
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=316736
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=179149
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|NEEDSINFO |RE
https://bugs.kde.org/show_bug.cgi?id=298488
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORK
https://bugs.kde.org/show_bug.cgi?id=285856
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|NEEDSINFO |RE
https://bugs.kde.org/show_bug.cgi?id=175122
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|ASSIGNED|RE
https://bugs.kde.org/show_bug.cgi?id=151201
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|CONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=187303
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=128848
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=188032
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|CONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=208243
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=343617
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=327486
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=197012
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=339812
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=316135
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=315739
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=241533
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=317245
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=145640
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=206611
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=202903
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=188838
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=224728
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=177330
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Resolution|--- |WORK
https://bugs.kde.org/show_bug.cgi?id=123808
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=158264
Ritesh Raj Sarraf <kde-b...@researchut.com> changed:
What|Removed |Added
CC|kde-b...@researchut.com |
-
https://bugs.kde.org/show_bug.cgi?id=187303
--- Comment #5 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
(In reply to Denis Kurz from comment #4)
> Actually, so do I, in version 5.3.2. Thanks for your feedback, Carioca
7 years in getting a bug confirmed. @Denis Kurz, your com
https://bugs.kde.org/show_bug.cgi?id=338176
--- Comment #77 from Ritesh Raj Sarraf <kde-b...@researchut.com> ---
(In reply to Peter from comment #76)
> This memory blow-out occurs during face tagging on my digikam 4.0 that came
> with Linux Mint 17.3 KDE and also on digikam 4.14 which
https://bugs.kde.org/show_bug.cgi?id=365768
Bug ID: 365768
Summary: show preview of versioned images
Product: digikam
Version: 5.0.0
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Severity:
91 matches
Mail list logo