[valgrind] [Bug 454346] [PATCH] ARM fixes from the Yocto project
https://bugs.kde.org/show_bug.cgi?id=454346 --- Comment #10 from Khem Raj --- (In reply to Paul Floyd from comment #9) > On my RPi 5 with Raspberry Pi OS > Linux raspberrypi 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 > (2024-01-25) aarch64 GNU/Linux > > Build fails with > > m_dispatch/dispatch-arm-linux.S:102: Error: selected processor does not > support `movw r1,#47' in ARM mode > m_dispatch/dispatch-arm-linux.S:103: Error: selected processor does not > support `movw r2,#0' in ARM mode > m_dispatch/dispatch-arm-linux.S:155: Error: selected processor does not > support `movw r4,#:lower16:vgPlain_stats__n_xIndirs_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:156: Error: selected processor does not > support `movt r4,#:upper16:vgPlain_stats__n_xIndirs_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:173: Error: selected processor does not > support `ubfx r6,r6,#0,#13' in ARM mode > m_dispatch/dispatch-arm-linux.S:176: Error: selected processor does not > support `movw r4,#:lower16:vgPlain_tt_fast' in ARM mode > m_dispatch/dispatch-arm-linux.S:177: Error: selected processor does not > support `movt r4,#:upper16:vgPlain_tt_fast' in ARM mode > m_dispatch/dispatch-arm-linux.S:204: Error: selected processor does not > support `movw r4,#:lower16:vgPlain_stats__n_xIndir_hits1_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:205: Error: selected processor does not > support `movt r4,#:upper16:vgPlain_stats__n_xIndir_hits1_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:226: Error: selected processor does not > support `movw r4,#:lower16:vgPlain_stats__n_xIndir_hits2_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:227: Error: selected processor does not > support `movt r4,#:upper16:vgPlain_stats__n_xIndir_hits2_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:248: Error: selected processor does not > support `movw r4,#:lower16:vgPlain_stats__n_xIndir_hits3_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:249: Error: selected processor does not > support `movt r4,#:upper16:vgPlain_stats__n_xIndir_hits3_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:258: Error: selected processor does not > support `movw r4,#:lower16:vgPlain_stats__n_xIndir_misses_32' in ARM mode > m_dispatch/dispatch-arm-linux.S:259: Error: selected processor does not > support `movt r4,#:upper16:vgPlain_stats__n_xIndir_misses_32' in ARM mode > > and also > > gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../include -I../VEX/pub > -I../VEX/pub -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1 > -DVGPV_arm_linux_vanilla=1-O2 -g -Wall -Wmissing-prototypes -Wshadow > -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-qual > -Wwrite-strings -Wempty-body -Wformat -Wformat-signedness -Wformat-security > -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wenum-conversion > -Wimplicit-fallthrough=2 -Wold-style-declaration -finline-functions > -fno-stack-protector -fno-strict-aliasing -fno-builtin -marm -O2 -MT > memcheck_arm_linux-mc_main.o -MD -MP -MF > .deps/memcheck_arm_linux-mc_main.Tpo -c -o memcheck_arm_linux-mc_main.o > `test -f 'mc_main.c' || echo './'`mc_main.c > /tmp/ccY1NRlM.s: Assembler messages: > /tmp/ccY1NRlM.s:27: Error: selected processor does not support `movw > r3,#:lower16:primary_map' in ARM mode > /tmp/ccY1NRlM.s:29: Error: selected processor does not support `movt > r3,#:upper16:primary_map' in ARM mode > /tmp/ccY1NRlM.s:68: Error: selected processor does not support `movw > r3,#:lower16:primary_map' in ARM mode > /tmp/ccY1NRlM.s:70: Error: selected processor does not support `movt > r3,#:upper16:primary_map' in ARM mode > > gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../include -I../VEX/pub > -I../VEX/pub -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1 > -DVGPV_arm_linux_vanilla=1-O2 -g -Wall -Wmissing-prototypes -Wshadow > -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-qual > -Wwrite-strings -Wempty-body -Wformat -Wformat-signedness -Wformat-security > -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wenum-conversion > -Wimplicit-fallthrough=2 -Wold-style-declaration -finline-functions > -fno-stack-protector -fno-strict-aliasing -fno-builtin -marm -O2 -MT > memcheck_arm_linux-mc_main_asm.o -MD -MP -MF > .deps/memcheck_arm_linux-mc_main_asm.Tpo -c -o > memcheck_arm_linux-mc_main_asm.o `test -f 'mc_main_asm.c' || echo > './'`mc_main_asm.c > /tmp/cclkrIER.s: Assembler messages: > /tmp/cclkrIER.s:25: Error: selected processor does not support `movw > r3,#:lower16:primary_map' in ARM mode > /tmp/cclkrIER.s:28: Error: selected processor does not support `movt > r3,#:upper16:primary_map' in ARM mode > /tmp/cclkrIER.s:31: Error: selected processor does not support `movw > r3,#0x' in ARM mode > /tm
[valgrind] [Bug 454346] [PATCH] ARM fixes from the Yocto project
https://bugs.kde.org/show_bug.cgi?id=454346 --- Comment #8 from Khem Raj --- (In reply to Paul Floyd from comment #4) > (And I have made some changes recently - have the patches been rebased?) @paul, I have rebased on master and uploaded latest 2 patches, dropping -mcpu makes it working on wider arm systems ( it seems to work on different versions of rpi boards ). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 454346] [PATCH] ARM fixes from the Yocto project
https://bugs.kde.org/show_bug.cgi?id=454346 Khem Raj changed: What|Removed |Added Attachment #149172|0 |1 is obsolete|| Attachment #149173|0 |1 is obsolete|| Attachment #149174|0 |1 is obsolete|| --- Comment #7 from Khem Raj --- Created attachment 169452 --> https://bugs.kde.org/attachment.cgi?id=169452=edit potential fix 2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 454346] [PATCH] ARM fixes from the Yocto project
https://bugs.kde.org/show_bug.cgi?id=454346 --- Comment #6 from Khem Raj --- Created attachment 169451 --> https://bugs.kde.org/attachment.cgi?id=169451=edit proposed fix. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480277] Missing XMP Subject field in image metadata
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 is working back a charm like before. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480277] Missing XMP Subject field in image metadata
https://bugs.kde.org/show_bug.cgi?id=480277 Ritesh Raj Sarraf changed: What|Removed |Added Platform|Other |Flatpak -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480277] New: Missing XMP Subject field in image metadata
https://bugs.kde.org/show_bug.cgi?id=480277 Bug ID: 480277 Summary: Missing XMP Subject field in image metadata Classification: Applications Product: digikam Version: 8.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Xmp Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- SUMMARY Something seems to have broken in Digikam 8.2.0. In Digikam 8.1 or before, metadata written to images have a Subject field ``` rrs@xps:.../.Pictures$ exiftool 2023/November/PXL_20231104_094352406.jpg ExifTool Version Number : 12.70 File Name : PXL_20231104_094352406.jpg Directory : 2023/November File Size : 3.3 MB File Modification Date/Time : 2023:11:04 15:14:03+05:30 File Access Date/Time : 2024:01:23 17:07:16+05:30 File Inode Change Date/Time : 2023:11:04 15:14:03+05:30 File Permissions: -rwxrwxr-x File Type : JPEG File Type Extension : jpg MIME Type : image/jpeg JFIF Version: 1.02 Exif Byte Order : Little-endian (Intel, II) Image Description : Make: Google Camera Model Name : Pixel 7 Orientation : Horizontal (normal) X Resolution: 72 Y Resolution: 72 Resolution Unit : inches Software: HDR+ 1.0.561695621zd Modify Date : 2023:11:04 15:13:52 Y Cb Cr Positioning : Centered Exposure Time : 1/100 F Number: 1.9 Exposure Program: Program AE ISO : 50 Exif Version: 0232 Date/Time Original : 2023:11:04 15:13:52 Create Date : 2023:11:04 15:13:52 Offset Time : +05:30 Offset Time Original: +05:30 Offset Time Digitized : +05:30 Components Configuration: Y, Cb, Cr, - Shutter Speed Value : 1/100 Aperture Value : 1.9 Brightness Value: 4.42 Exposure Compensation : 0 Max Aperture Value : 1.9 Subject Distance: 4.399 m Metering Mode : Center-weighted average Flash : Off, Did not fire Focal Length: 6.8 mm Sub Sec Time: 406 Sub Sec Time Original : 406 Sub Sec Time Digitized : 406 Flashpix Version: 0100 Color Space : sRGB Exif Image Width: 4032 Exif Image Height : 2268 Interoperability Index : R98 - DCF basic file (sRGB) Interoperability Version: 0100 Sensing Method : One-chip color area Scene Type : Directly photographed Custom Rendered : Custom Exposure Mode : Auto White Balance : Auto Digital Zoom Ratio : 0 Focal Length In 35mm Format : 24 mm Scene Capture Type : Standard Contrast: Normal Saturation : Normal Sharpness : Normal Subject Distance Range : Distant Lens Make : Google Lens Model : Pixel 7 back camera 6.81mm f/1.85 Composite Image : Composite Image Captured While Shooting GPS Version ID : 2.2.0.0 GPS Altitude Ref: Above Sea Level GPS Time Stamp : 09:42:19 GPS Img Direction Ref : Magnetic North GPS Img Direction : 210 GPS Map Datum : WGS-84 GPS Date Stamp : 2023:11:04 Compression : JPEG (old-style) Thumbnail Offset: 1436 Thumbnail Length: 31607 Warning : [minor] Fixed incorrect URI for xmlns:MicrosoftPhoto Has Extended XMP: 5DAE0D1BBA322FA93BE282905C2D05BD Date/Time Modified : 2023:11:04 15:13:52 Urgency : 0 (reserved) Metadata Date : 2023:11:04 15:13:52 Pick Label : 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/Family/Kiran Santosh Sarraf Last Keyword XMP: People/Family/Anshika Raj Sarraf, People/Family/Ritesh Raj Sarraf, People/Family/Priya Raj Sarraf, People/Family/Kiran Santosh Sarraf
[digikam] [Bug 479182] Organizer features for Import from Remote Storage
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 > import tool. > > Maik That's exactly what my current setup is like. My Pictures collection is on a remote SMB storage with 2 different ROOTS * Main * TO_ENCODE Main holds all the images. TO_ENCODE is where I dump all my images, filter/classify, and then import into Main. Both Collection ROOTS are smb mounted from the very same Samba server. When I import via the Camera Devices interface, I get the nice UI to organize. TO_ENCODE is emulated as Camera Device. And so, when I import to Main, I get the nice organize window. To downside is that, even though both the remote storages are on the very same samba server, the imports are inefficiently done over the network. Note: Both the collections are marked "Remote Storage", though I'm not sure if DigiKam really treats it any different than local storage. I was only testing the `Import from remote storage` feature, with the wishful hope that it would overcome the inefficient performance I've explained above. And in doing that I noticed this anomaly. I believe you could have consistency about imports, providing the same feature for all Import types, whether Camera Device and/or Remote Storage. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479182] Organizer features for Import from Remote Storage
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 this mail because: You are watching all bug changes.
[digikam] [Bug 479182] New: Organizer features for Import from Remote Storage
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 Status: REPORTED Severity: wishlist Priority: NOR Component: AdvancedRename-Import Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- SUMMARY The Digikam Import Tool, that imports image from a Camera device is fantastic. There are options in it that nicely allow the user to define what structure the import should be like. This is very handy to organize images. Like, I can set folder structure to `yyy/` and have images be imported into correct folders. This very feature is missing in the app window, when importing from a Remote Storage. It would be very nice to have the same Image Organizer Import Window that you have for Camera Devices, to be available for Remote Storage imports as well. STEPS TO REPRODUCE 1. Import images from Remote Storage 2. The pop-up window is missing all the features I explained above. OBSERVED RESULT * The pop-up window is missing all the features I explained above. EXPECTED RESULT * The pop-up window should have same/similar features available in Camera Import window -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382034] Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 --- Comment #12 from Khem Raj --- (In reply to Paul Floyd from comment #11) > If you don't beat me to it I'll probably go ahead and try this tonight. OK. I wont get to this till weekend. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464859] Build failures with GCC-13
https://bugs.kde.org/show_bug.cgi?id=464859 --- Comment #1 from Khem Raj --- Created attachment 155672 --> https://bugs.kde.org/attachment.cgi?id=155672=edit fix -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464859] New: Build failures with GCC-13
https://bugs.kde.org/show_bug.cgi?id=464859 Bug ID: 464859 Summary: Build failures with GCC-13 Classification: Developer tools Product: valgrind Version: 3.21 GIT Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: drd Assignee: bart.vanassche+...@gmail.com Reporter: raj.k...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Build tests 2. 3. OBSERVED RESULT Compile failure tsan_thread_wrappers_pthread.h:91:9: error: 'int64_t' does not name a type EXPECTED RESULT 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.
[valgrind] [Bug 382034] Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 --- Comment #8 from Khem Raj --- (In reply to Paul Floyd from comment #6) > Could you update the patches with expecteds that won't break glibc Linux? Paul, I do not understand what 'expecteds' you are refrerring to here. If I understand it better, I will be able to make the needed change -- You are receiving this mail because: You are watching all bug changes.
[kbreakout] [Bug 328504] Difficulty controlling paddle with mouse
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 substantially improved when playing in full-screen mode. -- You are receiving this mail because: You are watching all bug changes.
[kbreakout] [Bug 328504] Difficulty controlling paddle with mouse
https://bugs.kde.org/show_bug.cgi?id=328504 Ritesh Raj Sarraf changed: What|Removed |Added CC||kde-b...@researchut.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Ritesh Raj Sarraf --- KBreakOut Version 22.08.3 THe bug is still valid and spoils the entire experience of the game. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455095] New: NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
https://bugs.kde.org/show_bug.cgi?id=455095 Bug ID: 455095 Summary: NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. Product: Spectacle Version: 22.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: yadabvi...@gmail.com CC: k...@david-redondo.de Target Milestone: --- STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION ffsdfas djs dkjfj dfrj -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455094] New: NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
https://bugs.kde.org/show_bug.cgi?id=455094 Bug ID: 455094 Summary: NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. Product: Spectacle Version: 22.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: yadabvi...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION ffsdfas djs dkjfj dfrj -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426293] All my Qt clients die when I disconnect my display
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 report. And just because a claimed fix changed the reflection of the bug, you are calling it a fixed one. I am not going to file another bug report. The devs asked to report bugs with the beta release and so I did. You can choose to self-proclaim that this issue is fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426293] All my Qt clients die when I disconnect my display
https://bugs.kde.org/show_bug.cgi?id=426293 Ritesh Raj Sarraf changed: What|Removed |Added CC||kde-b...@researchut.com Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #27 from Ritesh Raj Sarraf --- (In reply to Vlad Zahorodnii from comment #26) > With > https://invent.kde.org/plasma/kwayland-server/-/commit/ > 589e339da06da6237d19218baf6822ac0016220f being merged, Qt clients should > stay alive when an output is disconnected. The fix will be available only in > 5.22. If apps still crash, please reopen this bug report. @Vlad 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 already running while the HDMI display cable was unplugged, go into a frozen state consuming 100% CPU cycles. Those applications do not recover at all. I'd really love to see this issue fixed before the final 5.22 release. So please, help me help you with whatever information you may need. Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-7-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
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 already running while the HDMI display cable was unplugged, go into a frozen state consuming 100% CPU cycles. Those applications do not recover at all. I'd really love to see this issue fixed before the final 5.22 release. So please, help me help you with whatever information you may need. Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-7-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436876] cannot write exif data to mp4 video files
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, using a free flow field, it should be possible to write the exif data. And then other tools (like Digikam) can parse that special header and interpret the data as Facial Data for a Video File. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436876] New: cannot write exif data to mp4 video files
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 Priority: NOR Component: Metadata-ExifTool Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- SUMMARY Digikam reports that: Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot save metadata to image using Exiv2 (Error # 11 : "/media/SSHD/.Pictures/Processed/rmi-note-6/VID_20210419_211910.mp4: The file contains data of an unknown image type" But the fact remains that I can manually add exif data to an mp4 file using something like the following command: exiftool -overwrite_original -tagsFromFile "$line" -All:All "$line"".converted.mp4" -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 403409] Cannot switch tabs using keyboard shortcut (Control (Ctrl) + Page Up/Down or Alt+n) in some situations (like when one of the tabs is TweetDeck)
https://bugs.kde.org/show_bug.cgi?id=403409 Ritesh Raj Sarraf changed: What|Removed |Added CC||kde-b...@researchut.com --- Comment #4 from Ritesh Raj Sarraf --- (In reply to Philippe Cloutier from comment #3) > I failed to reproduce this on TweetDeck. However, I must report having > experienced the same, on this very site. For example: > 1. If one goes to https://bugs.kde.org/query.cgi?format=advanced and clicks > for example Akonadi in the Product field, Ctrl+Page Up/Down stop working (as > long as the field has focus). > 2. On this very page, if one clicks "edit" to change the ticket summary, > direct access shortcuts (such as Alt+1 to go to the first tab) stop working > (as long as the field has focus). > > Presumably, this reproduces for all input fields of certain types (at least > text and select multiple). I have the same problem for point #2 I was filing the bug report but then saw this as a possible duplicate. So I'll just paste here what I've drafted. SUMMARY The keyboard shortcut, about switching tabs with `Alt + Tab Number` do not work when the curson is in the current tab's text input field. Under such circumstances, instead of switching the tab, it instead inputs the corresponding number into the text fie.d STEPS TO REPRODUCE 1. Open multiple tabs in Falkon 2. Stay in a tab where there is a text input field and your key curson is in the text input filed. 3. Try to switch to another tab with the `Alt + Tab Number` shortcut OBSERVED RESULT Does not switch to the requested tab. EXPECTED RESULT Should witch to the requested tab. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-6-amd64 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434279] lattedock network broadcasts makes entire desktop unresponsive
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 the conferencing web app to work proper. https://help.uberconference.com/hc/en-us/articles/115001552826-System-Requirements Under section, Routers and Port. In particular, * Routers and Ports You'll want to make sure your router/gateway has the SIP ALG disabled and that you've opened the following ports on your firewall: ProtocolPorts Direction TCP 80/443 Out TCP 6800/5222/5223/7060 Out UDP 5060/5061/7060/11000/16600 to 16998/19305 Out UDP stun.l.google.com/19302 UDP outbound "" "" UDP bidirectional UDP 16384 to 32768 Out You can also restrict outbound traffic to the following domains: dialpad.com dialpadcdn.com highfive.com ubervoip.net stun.i.google.com What are these ports used for? 80/443: WebSockets to communicate with our servers 6800/5222/5223/7060: Outbound calls 5060/5061/7060/11000/16600 to 16998/19305: Outbound calls stun.l.google.com/19302: ICE protocol to determine public address 16384 to 32768: Only open these if your network doesn't use D-NAT Usually, there's no need to turn on QoS on your router unless you have a large network with several thousand employees. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 435732] New: memcheck/tests/leak_cpp_interior fails with gcc11
https://bugs.kde.org/show_bug.cgi?id=435732 Bug ID: 435732 Summary: memcheck/tests/leak_cpp_interior fails with gcc11 Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: raj.k...@gmail.com Target Milestone: --- SUMMARY Test fails with gcc 11 STEPS TO REPRODUCE 1. compile whole system with gcc11 2. build valgrind from master 3. make tests OBSERVED RESULT memcheck/tests/leak_cpp_interior.stderr.diff --- leak_cpp_interior.stderr.exp +++ leak_cpp_interior.stderr.out @@ -9,7 +9,7 @@ definitely lost: x bytes in 1 blocks indirectly lost: 0 bytes in 0 blocks possibly lost: 0 bytes in 0 blocks - still reachable: x bytes in 8 blocks + still reachable: x bytes in 9 blocks of which reachable via heuristic: stdstring : x bytes in 2 blocks length64 : x bytes in 1 blocks @@ -23,7 +23,7 @@ definitely lost: x (+0) bytes in 1 (+0) blocks indirectly lost: 0 (+0) bytes in 0 (+0) blocks possibly lost: x (+x) bytes in 4 (+4) blocks - still reachable: x (-x) bytes in 4 (-4) blocks + still reachable: x (-x) bytes in 5 (-4) blocks of which reachable via heuristic: stdstring : 0 (-x) bytes in 0 (-2) blocks length64 : 0 (-x) bytes in 0 (-1) blocks @@ -35,10 +35,10 @@ LEAK SUMMARY: definitely lost: x (+0) bytes in 1 (+0) blocks indirectly lost: 0 (+0) bytes in 0 (+0) blocks - possibly lost: x (-x) bytes in 5 (+1) blocks - still reachable: x (+x) bytes in 3 (-1) blocks + possibly lost: x (-x) bytes in 4 (+0) blocks + still reachable: x (+x) bytes in 5 (+0) blocks of which reachable via heuristic: -newarray : x (+x) bytes in 1 (+1) blocks +newarray : x (+x) bytes in 2 (+2) blocks multipleinheritance: 0 (-x) bytes in 0 (-2) blocks To see details of leaked memory, give 'full' arg to leak_check @@ -46,11 +46,11 @@ LEAK SUMMARY: definitely lost: x (+0) bytes in 1 (+0) blocks indirectly lost: 0 (+0) bytes in 0 (+0) blocks - possibly lost: x (-x) bytes in 5 (+0) blocks - still reachable: x (+x) bytes in 3 (+0) blocks + possibly lost: x (+x) bytes in 5 (+1) blocks + still reachable: x (-x) bytes in 4 (-1) blocks of which reachable via heuristic: length64 : x (+x) bytes in 1 (+1) blocks -newarray : 0 (-x) bytes in 0 (-1) blocks +newarray : 0 (-x) bytes in 0 (-2) blocks To see details of leaked memory, give 'full' arg to leak_check leak_check summary heuristics stdstring @@ -58,7 +58,7 @@ definitely lost: x (+0) bytes in 1 (+0) blocks indirectly lost: 0 (+0) bytes in 0 (+0) blocks possibly lost: x (-x) bytes in 4 (-1) blocks - still reachable: x (+x) bytes in 4 (+1) blocks + still reachable: x (+x) bytes in 5 (+1) blocks @@ -82,7 +82,7 @@ definitely lost: x (+0) bytes in 1 (+0) blocks indirectly lost: 0 (+0) bytes in 0 (+0) blocks possibly lost: 0 (+0) bytes in 0 (+0) blocks - still reachable: x (+0) bytes in 8 (+0) blocks + still reachable: x (+0) bytes in 9 (+0) blocks of which reachable via heuristic: stdstring : x (+0) bytes in 2 (+0) blocks length64 : x (+0) bytes in 1 (+0) blocks @@ -95,7 +95,7 @@ definitely lost: x (+0) bytes in 1 (+0) blocks indirectly lost: 0 (+0) bytes in 0 (+0) blocks possibly lost: x (+x) bytes in 6 (+6) blocks - still reachable: x (-x) bytes in 2 (-6) blocks + still reachable: x (-x) bytes in 3 (-6) blocks of which reachable via heuristic: stdstring : 0 (-x) bytes in 0 (-2) blocks length64 : 0 (-x) bytes in 0 (-1) blocks === Test Summary === TOTAL: 736 PASSED: 695 FAILED: 1 SKIPPED: 40 EXPECTED RESULT No differences SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Yocto ( master ) (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 385726] Add Support For Apple Live Photos (HEIF)
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. > > > > https://photos.app.goo.gl/g37hyTahF69qqQ2n6 > > In case Google post-processes and messes it up. > > https://drive.google.com/file/d/1EFsJBFL1ZTNhIq5J_EqkOuLcDb8jpATo/ > view?usp=sharing Sorry. It seems that the picture that I linked, for whatever reason, is not what I intended to share as a motion photo from an Android phone. Please see this one instead: https://photos.app.goo.gl/rcmuoCg6ZifZo4jD8 As of today, I have verified that this indeed is an Android motion photo and is accessible anonymously. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
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 > KDE Frameworks Version: 5.80.0 > Qt Version: 5.15.2 > Kernel Version: 5.10.0-5-amd64 > OS Type: 64-bit > Graphics Platform: X11 > Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz > Memory: 15.4 GiB of RAM > Graphics Processor: Mesa Intel® UHD Graphics 620 Just to mention, the reporting is done from X11 because without multi-monitor setup, kwin_wayland is not ready for me for daily use. The crash was persistently seen when running under Wayland with a multi-monitor setup. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
https://bugs.kde.org/show_bug.cgi?id=419728 Ritesh Raj Sarraf changed: What|Removed |Added CC||kde-b...@researchut.com --- Comment #25 from Ritesh Raj Sarraf --- 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 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-5-amd64 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434279] lattedock network broadcasts makes entire desktop unresponsive
https://bugs.kde.org/show_bug.cgi?id=434279 Ritesh Raj Sarraf changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #7 from Ritesh Raj Sarraf --- AFter around a week of testing, I can now safely conclude that the problem has vanished after upgrade to plasma 5.21.3. I did not check what may have changed but the data point is the upgrade to 5.21.3. Thus, closing this bug report. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434279] lattedock network broadcasts makes entire desktop unresponsive
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. So far what I tried was to Unpin Google Chrome from Latte-Dock and then start it again. But as explained in the previous comment, the problem surfaced back again. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434279] lattedock network broadcasts makes entire desktop unresponsive
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. But overall the system was behaving normal. Mar 12 16:01:13 priyasi systemd[1]: snapperd.service: Succeeded. Mar 12 16:01:14 priyasi latte-dock[145353]: [684020:16:0312/160114.023380:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 Mar 12 16:01:14 priyasi latte-dock[145353]: [684020:16:0312/160114.023464:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 Mar 12 16:01:21 priyasi kwin_x11[7494]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12992, resource id: 17231891, major code: 3 (GetWindowAttributes), minor code: 0 Mar 12 16:01:21 priyasi kwin_x11[7494]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 12993, resource id: 17231891, major code: 14 (GetGeometry), minor code: 0 Mar 12 16:01:33 priyasi latte-dock[145353]: [684020:16:0312/160133.508841:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 Mar 12 16:01:33 priyasi latte-dock[145353]: [684020:16:0312/160133.508944:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 Mar 12 16:01:36 priyasi latte-dock[145353]: [684020:16:0312/160136.530339:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 Mar 12 16:01:36 priyasi latte-dock[145353]: [684020:16:0312/160136.530523:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 Mar 12 16:01:52 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:02:31 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:02:39 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:02:46 priyasi plasmashell[357060]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/PresentationModeItem.qml:99:9: QML Label: Binding loop detected for property "verticalAlignment" THen, I switched on my Home WiFi network (which is a Mesh network) while I still remained connected on my machine to the ISP router. And boom, I ran into the same problem again. Mar 12 16:16:30 priyasi plasmashell[357060]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/PresentationModeItem.qml:99:9: QML Label: Binding loop detected for property "verticalAlignment" Mar 12 16:16:30 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:16:34 priyasi kwin_x11[7494]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28617, resource id: 17376633, major code: 3 (GetWindowAttributes), minor code: 0 Mar 12 16:16:34 priyasi kwin_x11[7494]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28618, resource id: 17376633, major code: 14 (GetGeometry), minor code: 0 Mar 12 16:16:40 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:16:48 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:16:50 priyasi plasmashell[357060]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/PresentationModeItem.qml:99:9: QML Label: Binding loop detected for property "verticalAlignment" Mar 12 16:16:52 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:17:00 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:17:01 priyasi CRON[688248]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Mar 12 16:17:01 priyasi CRON[688249]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 12 16:17:01 priyasi CRON[688248]: pam_unix(cron:session): session closed for user root Mar 12 16:17:02 priyasi kded5[7492]: Registering ":1.1885/StatusNotifierItem" to system tray Mar 12 16:17:03 priyasi kded5[7492]: Service ":1.1885" unregistered Mar 12 16:17:03 priyasi plasmashell[357060]: qml: recreating buttons Mar 12 16:17:08 priyasi plasmashell[357060]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/PresentationModeItem.qml:99:9: QML Label: Binding loop detected for property "verticalAlignment" Mar 12 16:17:13 priyasi kded5[7492]: Registering ":1.1887/StatusNotifierItem" to system tray Mar 12 16:17:18 priyasi latte-dock[145353]: [687920:17:0312/161718.926093:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 Mar 12 16:17:18 priyasi latte-dock[145353]: [687920:17:0312/161718.934871:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 Mar 12 16:17:18 priyasi latte-dock[145353]: [687920:17:0312/161718.935984:ERROR:webrtc_video_engine.cc(3366)] Absent receive stream; ignoring clearing encoded fra
[lattedock] [Bug 434279] lattedock network broadcasts makes entire desktop unresponsive
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 + Plasma Integration extension, which I have now disabled. I will test it again in my video conference setup tomorrow, which is where this problem was easily seen. And then I'll report back on this bug report. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434279] New: lattedock network broadcasts makes entire desktop unresponsive
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: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kde-b...@researchut.com Target Milestone: --- SUMMARY I run into this nasty problem of the entire desktop session going sluggish whenever I connect to my ISP's router directly. When I connect to the internet via my Home network gateway (which still in turn connecs to the same ISP router), the problem does not happen. ``` Mar 11 17:32:25 priyasi latte-dock[145353]: [361323:17:0311/173225.188315:ERROR:stun_port.cc(308)] Port[18144400:video:1:0:local:Net[wlan0:192.168.0.x/16:Wifi:id=1]]: UDP send of 112 bytes failed with error 11 Mar 11 17:32:25 priyasi plasmashell[357060]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:231: TypeError: Cannot read property 'visible' of null Mar 11 17:32:25 priyasi plasmashell[357060]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:231: TypeError: Cannot read property 'visible' of null Mar 11 17:32:25 priyasi plasmashell[357060]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:231: TypeError: Cannot read property 'visible' of null Mar 11 17:32:25 priyasi plasmashell[357060]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:231: TypeError: Cannot read property 'visible' of null Mar 11 17:32:25 priyasi latte-dock[145353]: [361323:17:0311/173225.237170:ERROR:stun_port.cc(308)] Port[18144400:video:1:0:local:Net[wlan0:192.168.0.x/16:Wifi:id=1]]: UDP send of 112 bytes failed with error 11 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.585971:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.586595:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.587202:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.587699:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.619596:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.620290:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.620989:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.621536:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.622164:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.644510:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.644812:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.645031:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from unknown address: 170.10.194.x:18862 Mar 11 17:32:31 priyasi latte-dock[145353]: [361323:17:0311/173231.645349:ERROR:port.cc(379)] Port[169d6000:audio:1:0:relay:Net[wlan0:2409:4071:e80:x:x:x:x:x/64:Wifi:id=2]]: Received non-STUN packet from
[amarok] [Bug 424969] The link can not be opened
https://bugs.kde.org/show_bug.cgi?id=424969 Raj changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Raj --- The bug was fixed. Let me know if you have any problems. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 424969] The link can not be opened
https://bugs.kde.org/show_bug.cgi?id=424969 Raj changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Raj --- You are right I will fix it -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421853] single button to refresh collection
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 > combination that only searches for new items: Ctrl + F5. There is also the > option to automatically update the album when external changes detected > (Collections-> album monitoring). I don't think we need another button. > > Maik It does not seem to be working proper then. I have some collections over the network (Samba Share), with monitoring enabled in Digikam. But new items in the network share are not detected by Digikam with just the "Refresh" button. I need to restart Digikam to reflect those new files. And Digikam does so because it has the "Scan for New Items" on start-up option enabled. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
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 and messes it up. https://drive.google.com/file/d/1EFsJBFL1ZTNhIq5J_EqkOuLcDb8jpATo/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
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.
[digikam] [Bug 421853] single button to refresh collection
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. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421853] New: single button to refresh collection
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 Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- SUMMARY Digikam should have a single button to "Scan for New Items" in its collection. Right now, it has the "Refresh" button, which from the behavior looks like it just refreshes the thumbnails. This bug report is a feature request to add the "Scan for New Items" functionality, either into the "Refresh" button, or into its own separate single button. STEPS TO REPRODUCE 1. Click on Refresh 2. Only ThumbNails refresh OBSERVED RESULT Only ThumbNails refresh EXPECTED RESULT Need a single button workflow to refresh the Digikam Collections SOFTWARE/OS VERSIONS KDE Frameworks 5.69.0 Qt 5.14.2 (built against 5.14.2) The xcb windowing system digikam version 7.0.0-beta3 CPU cores: 8 Eigen: 3.3.3 Exiv2: 0.27.2 Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Pgf: Yes Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 supports XMP metadata: Yes HEIF encoding support: Yes ImageMagick codecs: 6.9.10 KF5: 5.69.0 LensFun: 0.3.95-0 LibCImg: 130 LibJPEG: 80 LibJasper: 1.900.23 LibLCMS: 2080 LibLqr support: Yes LibPGF: 7.19.03 LibPNG: 1.6.35 LibRaw: 0.20.0 LibTIFF: 4.0.10 Marble: 0.27.20 Parallelized demosaicing: Yes Qt: 5.14.2 Qt WebEngine support: Yes VKontakte support: No AkonadiContact support: No Baloo support: No Calendar support: Yes DBus support: No Database backend: QSQLITE HTML Gallery support: Yes LibAVCodec: 57.89.100 LibAVFormat: 57.71.100 LibAVUtil: 55.58.100 LibGphoto2: 2.5.14 LibOpenCV: 3.4.10 LibQtAV: 1.13.0 Media player support: Yes Panorama support: Yes -- You are receiving this mail because: You are watching all bug changes.
[plasma-pass] [Bug 405135] The entire clipboard is cleared out rather than just the last password
https://bugs.kde.org/show_bug.cgi?id=405135 Ritesh Raj Sarraf changed: What|Removed |Added CC||kde-b...@researchut.com --- Comment #1 from Ritesh Raj Sarraf --- I have run into almost the same problem. plasma-pass: 1.1.0 Plasma: 5.17.5 Distribution: Debian Unstable plasma-pass not only does not copy the password to the clipboard but instead it clears up my entire clipboard. I see below messages in the logs. rrs@priyasi:~/rrs-home/Community/plasma-pass (master)$ org.kde.plasma.pass: ServiceJob for clipboard failed internally, falling back to clearClipboard() -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
https://bugs.kde.org/show_bug.cgi?id=385726 Ritesh Raj Sarraf changed: What|Removed |Added CC||kde-b...@researchut.com --- Comment #13 from Ritesh Raj Sarraf --- Google has a similar feature in the form of motion images. Should I file a separate but report? Our can we track it on this report? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
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` -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
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 (in and out of kate) or a plain command p > - if you copy text from outside kate, you can paste it in kate via Ctrl+v, > but if you want to paste it via the vi-mode commands you'd have to use "+p > Can you please elaborate a little about using "+p ? If that is a special case and works, that still is a good thing. > So, if there's a bug here, I'd say that kate shouldn't copy the text to the > clipboard if the user yanks the text in vi-mode, that would match the > behaviour in vim. But I am by no means an expert when it comes to vim or the > vi-mode in kate, so... I agree. But that is something for you or the other developers to confirm. Even in vim, there's the +clipboard feature wherein when you yank something in vim, it gets copied to the clipboard. Now, like you said, it could very well be that kwrite/kate is internally having its own clipboard when run in 'vi mode'. And it copies the buffer to that clipboard when something is yanked in kate's 'vi mode'. Doesn't feel like that is what the kate devs must have done, but there is the possibility. And if that is the case, it'd be nice to have this bug report turned into a Feature Request to have an option to sync 'vi-mode' copy buffers to the Klipper clipboard. Essentially, implement the equivalent of vim's +clipboard feature. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
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.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
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 paste" would mean you paste using the 'p' key for whatever is > in the buffer. Using the 'p' key in "vi-mode's" 'command mode'. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
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'm surprised that you are not able to reproduce the issue. > Also by "vi-mode paste" you mean just using Ctrl+v, right? NO. "vi-mode paste" would mean you paste using the 'p' key for whatever is in the buffer. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
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 mail because: You are watching all bug changes.
[valgrind] [Bug 402480] Do not use %rsp in clobber list
https://bugs.kde.org/show_bug.cgi?id=402480 --- Comment #4 from Khem Raj --- (In reply to Mark Wielaard from comment #3) > (In reply to Khem Raj from comment #2) > > (In reply to Mark Wielaard from comment #1) > > > So how about just removing the clobber, but keeping stack pointer change > > > itself: > > > > OK that seems fine to me. It will work. > > Thanks. Pushed that to master as: > > commit 022f5af61bc3cbfa2b74ab355b0d2d30b3dab027 > Author: Khem Raj > Date: Sat Dec 22 15:28:40 2018 -0800 > > tests/amd64: Do not clobber %rsp register > > This is seen with gcc-9.0 compiler now which is fix that gcc community > did recently > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52813 > > Signed-off-by: Khem Raj Superb Mark, that was quick. Merry Christmas -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402480] Do not use %rsp in clobber list
https://bugs.kde.org/show_bug.cgi?id=402480 --- Comment #2 from Khem Raj --- (In reply to Mark Wielaard from comment #1) > Comment on attachment 117070 [details] > Patch to fix the issue > > While I agree that trying to clobber the stack pointer doesn't make sense > (and it only "works" because we never return from the asm), the changing of > the stack pointer itself is deliberate and part of the test (bug #345887 was > about checking the stack pointer was bogus and not crashing valgrind, even > though the test program itself does crash). > > Also without the bogus stack pointer the expected output doesn't match > anymore (because now we get a full backtrace because we can follow the > stack). > > So how about just removing the clobber, but keeping stack pointer change > itself: > > diff --git a/none/tests/amd64-linux/bug345887.c > b/none/tests/amd64-linux/bug345887.c > index 0f9237d..269bd70 100644 > --- a/none/tests/amd64-linux/bug345887.c > +++ b/none/tests/amd64-linux/bug345887.c > @@ -20,13 +20,17 @@ static void inner(void) >"movq $0x10d, %%r14\n" >"movq $0x10e, %%r15\n" >// not %rbp as mdb is then not able to reconstruct stack trace > + // Do change %rsp (to test a bogus stack pointer), > + // but don't add %rsp to the clobber list since gcc ignores it > + // and since gcc >= 9.0 errors about it > + // see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52813 >"movq $0x10f, %%rsp\n" >"movq $0x1234, (%%rax)\n" // should cause SEGV here >"ud2" // should never get here >: // no output registers >: // no input registers >: "memory", "%rax", "%rbx", "%rcx", "%rdx", "%rsi", "%rdi", > -"%r8", "%r9", "%r10", "%r11", "%r12", "%r13", "%r14", "%r15", > "%rsp"); > +"%r8", "%r9", "%r10", "%r11", "%r12", "%r13", "%r14", "%r15"); > } > > __attribute__((noinline)) OK that seems fine to me. It will work. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402480] New: Do not use %rsp in clobber list
https://bugs.kde.org/show_bug.cgi?id=402480 Bug ID: 402480 Summary: Do not use %rsp in clobber list Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: raj.k...@gmail.com Target Milestone: --- Created attachment 117070 --> https://bugs.kde.org/attachment.cgi?id=117070=edit Patch to fix the issue SUMMARY This is a testcase where we are expecting %rsp to be clobbered but its a fixed register that compiler does not save. This was silently ignored thus far by gcc, however gcc 9.0 has fixed it and now generates a dignostics error see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52813 STEPS TO REPRODUCE 1. build valgrind with gcc trunk ( would be gcc 9 soon) OBSERVED RESULT Compiler error ../../../../valgrind-3.14.0/none/tests/amd64-linux/bug345887.c | ../../../../valgrind-3.14.0/none/tests/amd64-linux/bug345887.c: In function 'inner': | ../../../../valgrind-3.14.0/none/tests/amd64-linux/bug345887.c:7:4: error: Stack Pointer register clobbered by '%rsp' in 'a sm' | 7 |__asm__ __volatile__( | |^~~ | make[5]: *** [Makefile:667: bug345887.o] Error 1 EXPECTED RESULT No compile error ADDITIONAL INFORMATION Seeing this with OpenEmbedded/Yocto cross compile system when upgrading gcc to trunk -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401457] Krita freeze when using huion h610Pro tablet
https://bugs.kde.org/show_bug.cgi?id=401457 Raj changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Raj --- (In reply to Bug Janitor Service from comment #2) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! After updating krita the issue is resolved. Thank you so much.(In reply to Boudewijn Rempt from comment #1) > I'm sorry, but we need more information. Photoshop is, of course, > irrelevant. > > Have you checked that with Krita 4.0 there are no freezes? If so, this might > be a regression. If you have the same problems with older versions of Krita, > it might be a problem caused by a windows or tablet driver update. > > > Could you please check > https://docs.krita.org/en/reference_manual/dr_minw_debugger.html and see if > there is a crash log that has some information? > > Could you check whether switching to the Windows Pointer API in krita's > settings makes a difference? > > Could you download the latest nightly build, check whether the problem > persists and add the output of help/system information for bug reports to > this bug? (Regular 4.1.5 output is broken). > > Does this also happen if you clear your settings > (https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration)? The problem is solved. Thank you so much. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401457] New: Krita freeze when using huion h610Pro tablet
https://bugs.kde.org/show_bug.cgi?id=401457 Bug ID: 401457 Summary: Krita freeze when using huion h610Pro tablet Product: krita Version: 4.1.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: raj860...@gmail.com Target Milestone: --- SUMMARY My huion h610 tablet is not working with recent Krita updates. It freeze from time to time. My tablet has been hanging since 4.1.0 updates. I rechecked my tablet with Photoshop and it works fine in it. OBSERVED RESULT Freeze from time to time when using huion h610 tablet SOFTWARE/OS VERSIONS Windows: 10 64bit -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] New: kate vi mode does not synchronize content from clipboard
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: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- SUMMARY kate vi mode does not synchronize content from clipboard STEPS TO REPRODUCE 1. Open kate. 2. write some text in vi mode and then also copy it 3. quite kate 4. Open a web browser and open some page 5. select and copy some text to klipper clipboard 6. Open kate again. (in vi mode) 7. Do a vi-mode paste. 8. You should have pasted the buffer from the clipboard. 9. But what was pasted to kate ? OBSERVED RESULT Stale buffer from old kate session loaded and pasted EXPECTED RESULT Buffer from clipboard should be pasted SOFTWARE/OS VERSIONS KDE Plasma: 5.13.5 KDE Framework: 5.49.0 Qt: 5.11.2 Linux, Debian -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395446] Seekbar in the media player plasmoid only starts after clicking for spotify
https://bugs.kde.org/show_bug.cgi?id=395446 Raj Amal changed: What|Removed |Added Version|5.13.0 |5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395446] Seekbar in the media player plasmoid only starts after clicking for spotify
https://bugs.kde.org/show_bug.cgi?id=395446 Raj Amal changed: What|Removed |Added CC||raj.am...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Raj Amal --- I am facing the same issue. When playing a song in Spotify the progress bar in the media widget is displaying incorrect progress. Here is the Screenshot: https://i.imgur.com/N5l2sR1.png You can see the progress from Spotify and the media widget is not in sync. I am on Kubuntu 18.10 with KDE 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382034] Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 --- Comment #4 from Khem Raj --- musl is an alternative system C library implementation for linux, like glibc or uclibc and others. see https://www.musl-libc.org/ -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 393631] Paired Bluetooth devices not connecting when resumed from sleep after upgrading to Kubuntu 18.04
https://bugs.kde.org/show_bug.cgi?id=393631 --- Comment #2 from Raj Amal <raj.am...@gmail.com> --- Thanks David. Looks like fix will be released soon. https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 393631] New: Paired Bluetooth devices not connecting when resumed from sleep after upgrading to Kubuntu 18.04
https://bugs.kde.org/show_bug.cgi?id=393631 Bug ID: 393631 Summary: Paired Bluetooth devices not connecting when resumed from sleep after upgrading to Kubuntu 18.04 Product: Bluedevil Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: daemon Assignee: now...@gmail.com Reporter: raj.am...@gmail.com Target Milestone: --- I recently upgraded to Kubuntu 18.04 from 17.10. After Wakeup from Suspend my paired Bluetooth device (Headphone) do not connect with the system. This was working fine in 17.10. After reboot it connects fine. Temporary fix, Restarting the Bluetooth service after each wakeup fixes this issue, sudo service bluetooth restart Or I need to remove the paired device and re pair it each time. -- You are receiving this mail because: You are watching all bug changes.
[ksystraycmd] [Bug 393630] New: System tray icons not clickable and collapsible when a entry visibility is changed to hidden
https://bugs.kde.org/show_bug.cgi?id=393630 Bug ID: 393630 Summary: System tray icons not clickable and collapsible when a entry visibility is changed to hidden Product: ksystraycmd Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: raj.am...@gmail.com Target Milestone: --- When the visibility of a system tray entry is changed from Auto to hidden, the rest of the visible icons are not clickable and the expanded hidden icons popup cannot be closed via down arrow icon. To replicate, 1. Open System tray settings 2. Select clipboard visibility to hidden and apply. 3. Now try clicking any other visible icons like Network or Wifi, it just expands the hidden icons instead of opening the specific system tray setting. Temporary fix, Reboot fixes this issue. OS: Kubuntu 18.04 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384807] digikam 5.7.0 AppImage bundle : provide a more recent ffmpeg version for video support
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: QSslSocket: cannot resolve CRYPTO_num_locks Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve sk_new_null Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve sk_push Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve sk_free Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve sk_num Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve sk_pop_free Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve sk_value Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSL_library_init Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSLeay Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot resolve SSLeay_version Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: Incompatible version of OpenSSL Dec 20 18:25:35 priyasi org.gnome.Shell.desktop[9174]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2c7 specified for 0x2c00194 (Export to ). Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method Dec 20 18:25:35 priyasi alacarte-made-4.desktop[11240]: qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384807] minor issues with digikam 5.7.0 AppImage bundle
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 see if problem exists ? > How I concluded so if by running the same video files under standalone mplayer/mpv, where they are working perfectly. > Also, you must know that ffmpeg build on Centos 6 used for the AppImage can > be a little bit old. > Hmm. That may be the reason then. Are there good reasons why you are using such an old distribution ? I thought AppImage had, everything that it depends upon, archived into its bundle. So I fail to see any merit on using such old distributions. RHEL/Cent 6 is way old. If I had to really choose a stable base, perhaps Debian Stable or Ubuntu LTS would be better candidates. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384807] minor issues with digikam 5.7.0 AppImage bundle
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.
[digikam] [Bug 384807] minor issues with digikam 5.7.0 AppImage bundle
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 the same. So, then, I re-downloaded the 5.6.0 build. And things are back to normal. This looks like a QtAV bug to me. Because, not just the thumbnailer, but also the video playback is broken in 5.7.0 and 5.8.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384807] minor issues with digikam 5.7.0 AppImage bundle
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 is mentioned as enabled. Please see comment #0 in this bug report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384807] minor issues with digikam 5.7.0 AppImage bundle
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 digiKam-5.8.0 AppImage? > > Maik Yes. I can do that. Can you please provide the download link ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384807] minor issues with digikam 5.7.0 AppImage bundle
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. > > Maik Hello Maik, Here's a snippet of what you asked. -- digiKam AppImage Bundle -- Use 'help' as CLI argument to know all available options QtAV 1.12.0(Jul 20 2017, 17:39:32) Multimedia framework base on Qt and FFmpeg. Distributed under the terms of LGPLv2.1 or later. Shanghai University->S3 Graphics->Deepin->PPTV, Shanghai, China Copyright (C) 2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com Donate: http://qtav.org/donate.html Source: https://github.com/wang-bin/QtAV Home page: http://qtav.org capi::version: 0.6.0 Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified kf5.kservice.sycoca: Parse error in "/home/rrs/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" The desktop entry file "/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" has Type= "Application" but no Exec line kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" digikam.metaengine: Cannot load metadata from file (Error # 11 : /media/SSHD/rrs-home/Data/Pictures/Digikam Managed/VID_20160106_133410_HandBrake.mp4: The file contains data of an unknown image type digikam.metaengine: Cannot load metadata using Exiv2 (Error # 11 : /media/SSHD/rrs-home/Data/Pictures/Digikam Managed/VID_20160106_133410_HandBrake.mp4: The file contains data of an unknown image type digikam.dimg.qimage: Can not load " "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/VID_20160106_133410_HandBrake.mp4" " using DImg::QImageLoader! digikam.general: Cannot create thumbnail for "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/VID_20160106_133410_HandBrake.mp4" digikam.general: Thumbnail is null for "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/VID_20160106_133410_HandBrake.mp4" digikam.metaengine: Cannot load metadata from file (Error # 11 : /media/SSHD/rrs-home/Data/Pictures/Digikam Managed//MOVIE-1.mp4: The file contains data of an unknown image type And a bigger log is available at: https://people.debian.org/~rrs/tmp/digikam-thumbnail-qtav-bug.txt -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384807] New: minor issues with digikam 5.7.0 AppImage bundle
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: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- On the 5.7.0 AppImage bundle of Digikam, so far I've come across the following issues: 1. Desktop Integration: The AppImage file does not prompt for integration into the Menu system. Earlier, the 5.6.0 AppImage bundle did provide the prompt and integrated properly with my Desktop (GNOME) system. 2. Video thumbnailer: Video thumbnailer is completely missing/broken in this release. 5.6.0 worked perfect. Below is the component information. digikam version 5.7.0 CPU cores: 4 Eigen: 3.2.5 Exiv2: 0.26 Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Pgf: Yes Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 supports XMP metadata: Yes KF5: 5.36.0 LensFun: 0.3.2-0 LibCImg: 130 LibJPEG: 80 LibJasper: 1.900.29 LibLCMS: 2080 LibLqr support: No LibPGF: 7.15.32 LibPNG: 1.6.26 LibRaw: 0.18.2 LibTIFF: 4.0.6 Marble: 0.27.1 Parallelized demosaicing: Yes Qt: 5.9.1 AkonadiContact support: no Baloo support: no Calendar support: no DBus support: Yes Database backend: QSQLITE HTML Gallery support: yes Kipi-Plugins: LibGphoto2: 2.5.14 LibKipi: 5.2.0 LibOpenCV: 3.2.0 LibQtAV: 1.12.0 Media player support: Yes Panorama support: yes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
https://bugs.kde.org/show_bug.cgi?id=373284 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #13 from Ritesh Raj Sarraf <kde-b...@researchut.com> --- (In reply to caulier.gilles from comment #12) > This problem still reproducible with last 5.6.0 ? No. I haven't seen this crash for the past couple of months. Hence closing. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382034] Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 Khem Raj <raj.k...@gmail.com> changed: What|Removed |Added Attachment #106454|application/mbox|text/plain mime type|| Attachment #106454|0 |1 is patch|| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382034] Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 --- Comment #2 from Khem Raj <raj.k...@gmail.com> --- Created attachment 106456 --> https://bugs.kde.org/attachment.cgi?id=106456=edit syscall fix -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382034] Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 --- Comment #1 from Khem Raj <raj.k...@gmail.com> --- Created attachment 106455 --> https://bugs.kde.org/attachment.cgi?id=106455=edit x86 fix -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382034] New: Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 Bug ID: 382034 Summary: Testcases build fixes for musl Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: raj.k...@gmail.com Target Milestone: --- Created attachment 106454 --> https://bugs.kde.org/attachment.cgi?id=106454=edit aarch64 fix While building tests on x86/aarch64 it fails to build few tests. Attached patches solve the problem, hopefully in a portable way, while keeping the functionality intact. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381769] New: Use ucontext_t instead of struct ucontext
https://bugs.kde.org/show_bug.cgi?id=381769 Bug ID: 381769 Summary: Use ucontext_t instead of struct ucontext Product: valgrind Version: 3.13 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: raj.k...@gmail.com Target Milestone: --- Created attachment 106359 --> https://bugs.kde.org/attachment.cgi?id=106359=edit proposed fix glibc 2.26 does not expose struct ucontext anymore. Attached patch fixes it -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 158484] SCHEMA : add album filter settings saved to database
https://bugs.kde.org/show_bug.cgi?id=158484 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added CC||kde-b...@researchut.com --- Comment #15 from Ritesh Raj Sarraf <kde-b...@researchut.com> --- Calibre (written in PyQt) has this feature implemented. Perhaps mockups and implementation ideas could be taken from there. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377597] digikam 5.5 fails to build @ docs/sv
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 this mail because: You are watching all bug changes.
[digikam] [Bug 377739] New: index.docbook:13: element link: validity error : IDREF attribute linkend references an unknownID "using-mainwindow-mapview"
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 Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- Hello Giles, The 5.5.0 release of Digikam fails to build on Debian. Below is a snippet of the build failure. [ 37%] Generating showfoto/index.cache.bz2 cd /build/digikam-5.5.0/doc-translated/sv && /usr/bin/meinproc5 --check --cache /build/digikam-5.5.0/obj-x86_64-linux-gnu/doc-translated/sv/showfoto/index.cache.bz2 showfoto/index.docbook [ 37%] Built target doc-translated-nl-digikam-index-cache-bz2 make -f doc-translated/uk/CMakeFiles/doc-translated-uk-digikam-index-cache-bz2.dir/build.make doc-translated/uk/CMakeFiles/doc-translated-uk-digikam-index-cache-bz2.dir/depend make[3]: Entering directory '/build/digikam-5.5.0/obj-x86_64-linux-gnu' cd /build/digikam-5.5.0/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/digikam-5.5.0 /build/digikam-5.5.0/doc-translated/uk /build/digikam-5.5.0/obj-x86_64-li nux-gnu /build/digikam-5.5.0/obj-x86_64-linux-gnu/doc-translated/uk /build/digikam-5.5.0/obj-x86_64-linux-gnu/doc-translated/uk/CMakeFiles/doc-translated-uk-digikam-index-cache-bz2.dir/Depend Info.cmake --color= Scanning dependencies of target doc-translated-uk-digikam-index-cache-bz2 make[3]: Leaving directory '/build/digikam-5.5.0/obj-x86_64-linux-gnu' make -f doc-translated/uk/CMakeFiles/doc-translated-uk-digikam-index-cache-bz2.dir/build.make doc-translated/uk/CMakeFiles/doc-translated-uk-digikam-index-cache-bz2.dir/build make[3]: Entering directory '/build/digikam-5.5.0/obj-x86_64-linux-gnu' [ 37%] Generating digikam/index.cache.bz2 cd /build/digikam-5.5.0/doc-translated/uk && /usr/bin/meinproc5 --check --cache /build/digikam-5.5.0/obj-x86_64-linux-gnu/doc-translated/uk/digikam/index.cache.bz2 digikam/index.docbook index.docbook:13: element link: validity error : IDREF attribute linkend references an unknownID "using-mainwindow-mapview" index.docbook:30: element link: validity error : IDREF attribute linkend references an unknownID "using-mainwindow-mapview" Error: `xmllint --noout` outputted text doc-translated/sv/CMakeFiles/doc-translated-sv-showfoto-index-cache-bz2.dir/build.make:64: recipe for target 'doc-translated/sv/showfoto/index.cache.bz2' failed make[3]: *** [doc-translated/sv/showfoto/index.cache.bz2] Error 1 make[3]: Leaving directory '/build/digikam-5.5.0/obj-x86_64-linux-gnu' CMakeFiles/Makefile2:15356: recipe for target 'doc-translated/sv/CMakeFiles/doc-translated-sv-showfoto-index-cache-bz2.dir/all' failed make[2]: *** [doc-translated/sv/CMakeFiles/doc-translated-sv-showfoto-index-cache-bz2.dir/all]Error 2 make[2]: *** Waiting for unfinished jobs Generating moc source digikamgui_src_automoc.dir/moc_datefolderview_HH2D2PE4NVIOH4.cpp Generating moc source digikamgui_src_automoc.dir/moc_ddateedit_NT4QK2B5LOB6OM.cpp Generating moc source digikamgui_src_automoc.dir/moc_ddatepicker_54PZEAKNOUEXEG.cpp Generating moc source digikamgui_src_automoc.dir/moc_ddatepicker_p_SSSA7QU66UE2ZW.cpp Generating moc source digikamgui_src_automoc.dir/moc_ddatepickerpop_SYOXOOGAO26PLJ.cpp Generating moc source digikamgui_src_automoc.dir/moc_ddatetable_PW2ART5HUDAF5A.cpp Generating moc source digikamgui_src_automoc.dir/moc_ddatetable_p_MTOWJPYWNX3XFZ.cpp Generating moc source digikamgui_src_automoc.dir/moc_ddatetimeedit_Z5PQWGONVTXQLV.cpp -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373572] file synchronization
https://bugs.kde.org/show_bug.cgi?id=373572 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Ritesh Raj Sarraf <kde-b...@researchut.com> --- I am not able to reproduce this bug. I am disappointed in this bug report because it looks like I hurried upon. Neither the bug report has clear steps to reproduce, nor have I been able to reproduce it again, which may imply I did not double check. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373572] New: file synchronization
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 Priority: NOR Component: Usability Assignee: digikam-de...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- Created attachment 102744 --> https://bugs.kde.org/attachment.cgi?id=102744=edit misleading file synchronization tooltip Hello Gilles, Please see attached screenshot for details. In Digikam 5.3.x, there does not seem to be a straight way to instruct the software to write queued/pending metadata to files. To the best of my knowledge, the queue gets written only during digikam shutdown. So there are 2 problems. 1. The tooltip is misleading. because if I click, it reloads metadata, rather than writing it. 2. There is no interface in the digikam menu to trigger the write(), other than quitting digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
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 packaged. :-( (gdb) bt #0 0x74c4b178 in QSortFilterProxyModel::parent(QModelIndex const&) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x74c4b00c in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74c4b1b8 in QSortFilterProxyModel::parent(QModelIndex const&) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x757f702b in QTreeView::isIndexHidden(QModelIndex const&) const () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x757f96ef in QTreeView::visualRect(QModelIndex const&) const () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x757a161a in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x757a1b6a in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fffca391269 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #8 0x7fffca391919 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7fffca395d2c in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x71137e88 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x7113a8ee in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #12 0x74cafb39 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7556ab2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x755722e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x74c83090 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x74c8581d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x74cd72d3 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fffebb2d7f7 in g_main_context_dispatch (context=0x7fffc40016f0) at ././glib/gmain.c:3203 #19 0x7fffebb2d7f7 in g_main_context_dispatch (context=context@entry=0x7fffc40016f0) at ././glib/gmain.c:3856 #20 0x7fffebb2da60 in g_main_context_iterate (context=context@entry=0x7fffc40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3929 #21 0x7fffebb2db0c in g_main_context_iteration (context=0x7fffc40016f0, may_block=1) at ././glib/gmain.c:3990 #22 0x74cd76df in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x74c8107a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x74c897ec in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0xa111 in main(int, char**) (argc=, argv=) at ./core/app/main/main.cpp:237 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
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 share it with you As for the video card, this is a very standard setup. Intel Haswell box with an Intel on-board graphics. [1] digikam crashed with SIGSEGV in QMetaObject::cast() -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
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.
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
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
State: S (sleeping)
Tgid: 15434
Ngid: 0
Pid: 15434
PPid: 1
TracerPid: 0
Uid: 1000100010001000
Gid: 1000100010001000
FDSize:128
Groups:4 24 25 27 29 30 44 46 50 101 102 108 119 147 1000
NStgid:15434
NSpid: 15434
NSpgid:5146
NSsid: 5146
VmPeak: 4437916 kB
VmSize: 4226752 kB
VmLck:0 kB
VmPin:0 kB
VmHWM: 312396 kB
VmRSS: 308848 kB
RssAnon: 171040 kB
RssFile: 126900 kB
RssShmem: 10908 kB
VmData: 323124 kB
VmStk: 136 kB
VmExe: 40 kB
VmLib: 255884 kB
VmPTE: 2184 kB
VmPMD: 28 kB
VmSwap: 0 kB
HugetlbPages: 0 kB
Threads: 14
SigQ: 0/31265
SigPnd:
ShdPnd:
SigBlk:
SigIgn:01001000
SigCgt:00018001
CapInh:
CapPrm:
CapEff:
CapBnd:003f
CapAmb:
Seccomp: 0
Cpus_allowed: ff
Cpus_allowed_list: 0-7
Mems_allowed: ,0001
Mems_allowed_list: 0
voluntary_ctxt_switches: 21906
nonvoluntary_ctxt_switches:9802
Registers:
rax0x12e539610011 1361557551124054033
rbx0x55c2bb497600 94294854170112
rcx0x7fba6d0f29d0 140438670354896
rdx0x2739
rsi0x55c2bb497600 94294854170112
rdi0x55c2bb497600 94294854170112
rbp0x7fba6d1c68a0 0x7fba6d1c68a0
rsp0x7ffc07333c50 0x7ffc07333c50
r8 0x55c2bb497600 94294854170112
r9 0x7fba700a8a10 140438720383504
r100x1ccc 7372
r110x7fba6f9fb430 140438713381936
r120x2 2
r130x7fba6f9fd040 140438713389120
r140x3b59
r150x7ffc07333dd0 140720429284816
rip0x7fba6cf89bd7 0x7fba6cf89bd7 <QMetaObject::cast(QObject
const*) const+23>
eflags 0x10206 [ PF IF RF ]
cs 0x3351
ss 0x2b43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
SegvAnalysis:
Segfault happened at: 0x7fba6cf89bd7 <_ZNK11QMetaObject4castEPK7QObject+23>:
callq *(%rax)
PC (0x7fba6cf89bd7) ok
source "*(%rax)" ok
destination "(%rsp)" (0x7ffc07333c50) ok
SP (0x7ffc07333c50) ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: digikam
Stacktrace:
#0 0x7fba6cf89bd7 in QMetaObject::cast(QObject const*) const () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x7fba6f9fb48c in Digikam::ActionItemModel::actionForIndex(QModelIndex
const&) (object=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:495
#2 0x7fba6f9fb48c in Digikam::ActionItemModel::actionForIndex(QModelIndex
const&) (v=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:709
#3 0x7fba6f9fb48c in Digikam::ActionItemModel::actionForIndex(QModelIndex
const&) (a=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:102
#4 0x7fba6f9fb48c in Digikam::ActionItemModel::actionForIndex(QModelIndex
const&) (v=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:835
#5 0x7fba6f9fb48c in Digikam::ActionItemModel::actionForIndex(QModelIndex
const&) (this=0x7ffc07333c80) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:352
#6 0x7fba6f9fb48c in Digikam::ActionItemModel::actionForIndex(QModelIndex
const&) (index=...) at ./core/libs/models/categorizeditemmodel.cpp:232
#7 0x7fba6f9fb779 in Digikam::ActionItemModel::trigger(QModelIndex
const&) (this=, index=...) at
./core/libs/models/categorizeditemmodel.cpp:274
action =
#8 0x7fba6cfacc89 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x7fba6dab2075 in QAbstractItemView::clicked(QModelIndex const&) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7fba6dab5623 in QAbstractItemView::mouseReleaseEvent(QMouseEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7fba6dade4be in QListView::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7fba6ec4d8ab in
Digikam::DCategorizedView::mouseReleaseEvent(QMouseEvent*)
(this=0x55c2bd2d0c20, event=0x7ffc07334680) at
./core/libs/widgets/itemview/dcategorizedview.cpp:1324
initialPressPosition =
rect = {x1 = 103, y1 = 0, x2 = 120799728, y2 = 32764}
#13 0x7fba6d8b01d8 in QWidget::
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
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.
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
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 collection, deleted old .db files, re-initialized everything, and still see the crash on the primary machine. The only thing I've not done is to delete the current digikam settings (~/.kde/), something I don't want to do. It'd be frustrating to know if that could be the cause of the crash. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373304] New: google picasa photo import
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 Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- Hi, I hope I've chosen the right bugzilla components. In its current implementation, the "Import from Picasa/Google" feature only gives a listing of the available albums. It does not give any idea about the contents of the album. My Feature Request is that, it would be nice to have a widget show the picasa web albums and their contents, along with thumbnails. You could have this as an optional secondary feature. THis will allow users to decide what all pics they'd want to download. Otherwise, it is a "Catch All" implementation currently. And with Videos (auto) backed up, this becomes a sheer waste of network resources. Take another example: Google Picasaweb has an Album called "Auto Backup", where it backs up all pictures taken over your Google a/c. WHen importing with Digikam, the entire "Auto Backup" contents will be imported. Where as, with the requested Feature, users will have a choice to look and decide what all they want to import. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
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" digikam.iojob: Trash folder for collection: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/" digikam.iojob: DTrash: Image album root path: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed" digikam.iojob: Trash folder for collection: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/" digikam.iojob: DTrash: Image album root path: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed" digikam.iojob: Trash folder for collection: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/" digikam.iojob: DTrash: Image album root path: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed" digikam.iojob: Trash folder for collection: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/" digikam.iojob: DTrash: Image album root path: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed" digikam.iojob: Trash folder for collection: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/" digikam.iojob: DTrash: Image album root path: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed" digikam.iojob: Trash folder for collection: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/" digikam.iojob: DTrash: Image album root path: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed" digikam.iojob: Trash folder for collection: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/" digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb" digikam.iojob: Thread Finished digikam.general: One job is done digikam.general: Detected change, triggering rescan of "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed//" digikam.database: Starting scan! digikam.database: Removed items: (16645, 16646, 16647, 16648, 16649, 16650, 16651, 16652, 16653, 16654, 16655, 16656, 16657, 16658, 16659, 16660, 16661, 16662, 16663, 16664, 16665, 1, 16667, 16668, 16669, 16670, 16671, 16672, 16673, 16674, 16675, 16676, 16677, 16678, 16679, 16680, 16681, 16682, 16683, 16684, 16685, 16686, 16687, 16688, 16689, 16690) related items: () digikam.database: Folder does not exist or is not readable: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb" digikam.database: Folder does not exist or is not readable: "/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb" digikam.geoiface: digikam.geoiface: digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs /tmp/.mount_ZMCjVu/AppRun: line 37: 20599 Segmentation fault (core dumped) digikam.wrapper $@ 2016-12-05 / 22:27:05 ♒♒♒ ☹ => 139 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373284] New: digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
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 Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- Package: digikam Version: 4:5.3.0-1.1 Hello Giles, I frequently get this crash when deleting an album folder in Digikam. The stacktrace may not be complete. I'm not sure. But I thought of letting you decide that. Thanks, Ritesh = ProblemType: Crash Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 5 15:54:29 2016 Dependencies: acl 2.2.52-3 adduser 3.115 adwaita-icon-theme 3.22.0-1 apt 1.4~beta1 apt-utils 1.4~beta1 at-spi2-core 2.22.0-4 avahi-daemon 0.6.32-1 base-files 9.7 bind9-host 1:9.10.3.dfsg.P4-10.1 ca-certificates 20161102 catdoc 1:0.94.3~git20160113.dbc9ec6+dfsg-1 coreutils 8.25-2+b1 cpp 4:6.2.1-1 cpp-6 6.2.1-5 dbus 1.10.14-1 dconf-gsettings-backend 0.26.0-2 dconf-service 0.26.0-2 debconf 1.5.59 debconf-i18n 1.5.59 debian-archive-keyring 2014.3 debianutils 4.8.1 digikam-data 4:5.3.0-1.1 [origin: unknown] digikam-private-libs 4:5.3.0-1.1 [origin: unknown] dirmngr 2.1.16-2 dmsetup 2:1.02.136-1 dpkg 1.18.15 ffmpegthumbs 4:16.08.0-1 fontconfig 2.11.0-6.7 fontconfig-config 2.11.0-6.7 fonts-dejavu-core 2.37-1 gcc-6-base 6.2.1-5 geoclue-2.0 2.4.4-1 geoip-database 20161109-1 glib-networking 2.50.0-1 glib-networking-common 2.50.0-1 glib-networking-services 2.50.0-1 gnome-icon-theme 3.12.0-2 gnupg 2.1.16-2 gnupg-agent 2.1.16-2 gpgv 2.1.16-2 gsettings-desktop-schemas 3.22.0-1 gstreamer1.0-plugins-base 1.10.2-1 gtk-update-icon-cache 3.22.4-1 hicolor-icon-theme 0.15-1 ifupdown 0.8.16 iio-sensor-proxy 1.3-2 init-system-helpers 1.46 iproute2 4.8.0-1 isc-dhcp-client 4.3.5~b1-1 isc-dhcp-common 4.3.5~b1-1 iso-codes 3.71-1 kio 5.27.0-2 liba52-0.7.4 0.7.4-18 libaa1 1.4p5-44 libaacs0 0.8.1-2 libacl1 2.2.52-3 libapparmor1 2.10.95-6 libapt-inst2.0 1.4~beta1 libapt-pkg5.0 1.4~beta1 libasound2 1.1.2-1 libasound2-data 1.1.2-1 libass5 0.13.4-1 libassuan0 2.4.3-2 libastro1 4:16.08.2-1 libasyncns0 0.8-6 libatk-bridge2.0-0 2.22.0-1 libatk1.0-0 2.22.0-1 libatk1.0-data 2.22.0-1 libatm1 1:2.5.1-1.6 libatomic1 6.2.1-5 libatspi2.0-0 2.22.0-4 libattr1 1:2.4.47-2 libaudit-common 1:2.6.7-1 libaudit1 1:2.6.7-1 libauthen-sasl-perl 2.1600-1 libavahi-client3 0.6.32-1 libavahi-common-data 0.6.32-1 libavahi-common3 0.6.32-1 libavahi-core7 0.6.32-1 libavahi-glib1 0.6.32-1 libavc1394-0 0.5.4-4 libavcodec57 7:3.2.1-1 libavfilter6 7:3.2.1-1 libavformat57 7:3.2.1-1 libavresample3 7:3.2.1-1 libavutil55 7:3.2.1-1 libbasicusageenvironment1 2016.11.17-1 libbdplus0 0.1.2-2 libbind9-140 1:9.10.3.dfsg.P4-10.1 libblkid1 2.29-1 libbluetooth3 5.43-1 libbluray1 1:0.9.3-3 libbs2b0 3.1.0+dfsg-2.2 libbsd0 0.8.3-1 libbz2-1.0 1.0.6-8 libc6 2.24-7 libcaca0 0.99.beta19-2+b1 libcairo-gobject2 1.14.6-1.1 libcairo2 1.14.6-1.1 libcap-ng0 0.7.7-3 libcap2 1:2.25-1 libcap2-bin 1:2.25-1 libcddb2 1.3.2-5 libcdio13 0.83-4.2+b1 libcdparanoia0 3.10.2+debian-11 libchromaprint1 1.3.2-2 libcolord2 1.3.3-2 libcomerr2 1.43.3-1 libcroco3 0.6.11-2 libcryptsetup4 2:1.7.3-2 libcrystalhd3 1:0.0~git20110715.fdd2f19-11+b1 libcups2 2.2.1-2 libdaemon0 0.14-6 libdatrie1 0.2.10-4 libdb5.3 5.3.28-12 libdbus-1-3 1.10.14-1 libdbusmenu-qt5-2 0.9.3+16.04.20160218-1 libdc1394-22 2.2.4-1 libdca0 0.0.5-10 libdconf1 0.26.0-2 libdevmapper1.02.1 2:1.02.136-1 libdirectfb-1.2-9 1.2.10.0-5.2+b1 libdns-export162 1:9.10.3.dfsg.P4-10.1 libdns162 1:9.10.3.dfsg.P4-10.1 libdrm-amdgpu1 2.4.74-1 libdrm-intel1 2.4.74-1 libdrm-nouveau2 2.4.74-1 libdrm-radeon1 2.4.74-1 libdrm2 2.4.74-1 libdvbpsi10 1.3.0-5 libdvdnav4 5.0.3-2 libdvdread4 5.0.3-2 libebml4v5 1.3.4-1 libebur128-1 1.2.0-1 libedit2 3.1-20160903-2 libegl1-mesa 13.0.2-1 libelf1 0.166-2.2 libencode-locale-perl 1.05-1 libepoxy0 1.3.1-1 libepub0 0.2.2-4+b1 libevdev2 1.5.4+dfsg-2 libexif12 0.6.21-2 libexiv2-14 0.25-3 libexpat1 2.2.0-1 libfaad2 2.8.0~cvs20161113-1 libfam0 2.7.0-17.2 libfdisk1 2.29-1 libffi6 3.2.1-6 libfftw3-double3 3.3.5-1 libfile-basedir-perl 0.07-1 libfile-desktopentry-perl 0.22-1 libfile-listing-perl 6.04-1 libfile-mimeinfo-perl 0.27-1 libflac8 1.3.1-4 libflite1 2.0.0-release-3 libfont-afm-perl 1.20-2 libfontconfig1 2.11.0-6.7 libfontenc1 1:1.1.3-1 libfreetype6 2.6.3-3+b1 libfribidi0 0.19.7-1 libgail-common 2.24.31-1 libgail18 2.24.31-1 libgbm1 13.0.2-1 libgcc1 1:6.2.1-5 libgcrypt20 1.7.3-2 libgd3 2.2.3-87-gd0fec80-3 libgdbm3 1.8.3-14 libgdk-pixbuf2.0-0 2.36.0-1 libgdk-pixbuf2.0-common 2.36.0-1 libgeoclue-2-0 2.4.4-1 libgeoip1
[homerun] [Bug 332829] directory names with space not rendered correct
https://bugs.kde.org/show_bug.cgi?id=332829 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 316543] session auto save feature
https://bugs.kde.org/show_bug.cgi?id=316543 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 316736] rekonq seems to be power hungry
https://bugs.kde.org/show_bug.cgi?id=316736 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[nepomuk] [Bug 179149] nepomuk crash when enabling strigi
https://bugs.kde.org/show_bug.cgi?id=179149 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Ritesh Raj Sarraf <kde-b...@researchut.com> --- I don't have the resources to follow-up on KDE bugs any more. I'm marking this closed because I'm sure a lot would have changed in 8 years, making this bug obsolete/invalid. -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 298488] please return the upload url upon successful upload
https://bugs.kde.org/show_bug.cgi?id=298488 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 285856] ark doesn't detect unrar errors
https://bugs.kde.org/show_bug.cgi?id=285856 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kbreakout] [Bug 175122] please provide save game option
https://bugs.kde.org/show_bug.cgi?id=175122 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 151201] kde should have a forceful shutdown policy
https://bugs.kde.org/show_bug.cgi?id=151201 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 187303] Sorting of events is not in order
https://bugs.kde.org/show_bug.cgi?id=187303 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[knode] [Bug 128848] KNode doesn't detect the signature delimiter when replying to GPG signed messages
https://bugs.kde.org/show_bug.cgi?id=128848 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 188032] deleting files in external hard disk moves them to trash
https://bugs.kde.org/show_bug.cgi?id=188032 Ritesh Raj Sarraf <kde-b...@researchut.com> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
