[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 --- Comment #19 from Silver Salonen --- (In reply to Andrey from comment #18) > (In reply to Denis Lisov from comment #14) > > (In reply to Andrey from comment #13) > > > The OSD when you start typing in window with another layout is expected > > > feature for Wayland. > > > > Would it make more sense to show the layout indicator right after switching > > windows, without waiting for the next keystroke? > That would unnecessary show OSD if you switch windows without typing. > Anyway, the feature implementation details should go to another report, > thanks. I actually just recently noticed this happening in Plasma 5 with X11 on Ubuntu, so this seems to be implemented already. Or is it only with X11 and not with Wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 --- Comment #17 from Silver Salonen --- (In reply to Denis Lisov from comment #16) > (In reply to Silver Salonen from comment #15) > > (In reply to Andrey from comment #13) > > > If you don't like it, you can disable the OSD in Keyboard KCM. > > > > Where exactly is that setting? Sorry, I can't find it (in Plasma 5). > > For me there's a checkbox "OSD on layout change" in Settings - Keyboard - > Layouts tab, in the "Shortcuts for switching layouts" group. For me there's not. Are you on Plasma 6 perhaps? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 --- Comment #15 from Silver Salonen --- (In reply to Andrey from comment #13) > If you don't like it, you can disable the OSD in Keyboard KCM. Where exactly is that setting? Sorry, I can't find it (in Plasma 5). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 --- Comment #12 from Silver Salonen --- I've now noticed that sometimes the displayed OSD even manages to steal focus from the application. For example, when switching quickly with ALT+TAB from browser to editor with a different keyboard layout and starting typing right away, you may notice a few seconds later that the text cursor focus is not in the editor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476831] Per application Keyboard Layout not remembered under Wayland
https://bugs.kde.org/show_bug.cgi?id=476831 --- Comment #3 from Silver Salonen --- I'm not sure what component handles this, but it does not seem to me it's related to session. The use-case I described is done during the same session, not over several sessions. Although previously, I think per application keyboard layouts indeed were remembered across sessions too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 --- Comment #12 from Silver Salonen --- (In reply to Nate Graham from comment #11) > This seems like either a code error in the applet, or a packaging error in > the distro. Andrey, do you have any idea which one it could be? FWIW on > Fedora KDE in a Plasma 6 Wayland session I see no such error. No issue for > me in the past on Plasma 5 Wayland either. I don't think it's a packaging issue as it works OK in another computer with the same versions distro and packages. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 --- Comment #10 from Silver Salonen --- (In reply to Andrey from comment #9) > Can you try to reproduce in VM? I tried out using Wayland session in my other Manjaro computer and in there the keyboard layout icon works OK, although the installed software is pretty much the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 --- Comment #8 from Silver Salonen --- (In reply to Andrey from comment #7) > Please try this workaround: > https://bugs.kde.org/show_bug.cgi?id=470737#c15 That does not help in my case. Error is still the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 --- Comment #6 from Silver Salonen --- Nope, the widget doesn't work either. The error copied from it: file:///usr/share/plasma/plasmoids/org.kde.plasma.keyboardlayout/contents/ui/main.qml:14:1: KeyboardLayoutButton is not a type -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 --- Comment #4 from Silver Salonen --- (In reply to Nate Graham from comment #2) > Ah, it's just Bug 449531, which is fixed in Plasma 6 I did read through that bug first too, and it seemed to me that what I hit was not that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 --- Comment #3 from Silver Salonen --- > Does it appear if you restart plasmashell with `systemctl restart --user > plasma-plasmashell.service`? No, it does not. I've restarted plasmashell many times after starting using Wayland, but I've never once seen the keyboard layout icon at system tray under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476832] New: Layout switching OSD displayed when starting typing in an application with different layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=476832 Bug ID: 476832 Summary: Layout switching OSD displayed when starting typing in an application with different layout under Wayland Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: silver.salo...@gmail.com CC: butir...@gmail.com Target Milestone: 1.0 SUMMARY Layout switching OSD displayed when starting typing in an application with different layout. STEPS TO REPRODUCE 1. Use Wayland session 2. Configure multiple (I have 2) keyboard layouts 3. Use Application Switching Policy 4. Open applications and use different keyboard layouts for them 5. Type something in an application with one keyboard layout 6. Switch to an application with another keyboard layout and type something there OBSERVED RESULT When starting typing in an application that has different keyboard layout than the application where typing was done before, keyboard layout OSD is displayed at the center of the screen. EXPECTED RESULT No OSD is displayed - maybe only when switching keyboard layout manually? I don't know what is the expected behaviour. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476831] New: Per application Keyboard Layout not remembered under Wayland
https://bugs.kde.org/show_bug.cgi?id=476831 Bug ID: 476831 Summary: Per application Keyboard Layout not remembered under Wayland Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: silver.salo...@gmail.com CC: butir...@gmail.com Target Milestone: 1.0 SUMMARY I use "Application" Switching Policy for keyboard layouts. When used under X11, layout mappings for applications were always remembered, even across sessions. Under Wayland they are not remembered, even within the same session. STEPS TO REPRODUCE 1. Use Wayland session 2. Configure multiple (I use 2) keyboard layouts OBSERVED RESULT I always switch to US layout when using Konsole. When closing Konsole and starting it again, it uses my first layout instead. EXPECTED RESULT After switching layout for an application and closing the application, re-opening the application should also switch to the layout used last with this application. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] New: Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 Bug ID: 476830 Summary: Keyboard layout applet not shown on Wayland Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: silver.salo...@gmail.com CC: butir...@gmail.com Target Milestone: 1.0 SUMMARY I've always used keyboard layouts and always had the layout icon displayed in system tray. Now I switched to Wayland and in there the icon is not displayed, even though Keyboard Layout is set to "Always shown" under Entries. STEPS TO REPRODUCE 1. Use Wayland session 2. Configure multiple (I have 2) keyboard layouts OBSERVED RESULT Keyboard Layout icon is not shown in system tray. EXPECTED RESULT Keyboard Layout icon is shown in system tray. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 293543] vlookup does not work with indirect
https://bugs.kde.org/show_bug.cgi?id=293543 Silver Salonen changed: What|Removed |Added Platform|OpenSUSE|Manjaro Resolution|WAITINGFORINFO |--- Version|2.4.1 |3.2.1 Status|NEEDSINFO |REPORTED --- Comment #5 from Silver Salonen --- Confirmed that still does not work in Calligra Sheets. -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 293614] referencing to another sheet does not work correctly
https://bugs.kde.org/show_bug.cgi?id=293614 Silver Salonen changed: What|Removed |Added Version|2.4.1 |3.2.1 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Platform|OpenSUSE|Manjaro --- Comment #4 from Silver Salonen --- Still valid. Also another unexpected behaviour I noticed: right after renaming an active/selected tab, selection of the tab is not highlighted in the tab bar. -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 293529] undo is not reflected in active cell's formula
https://bugs.kde.org/show_bug.cgi?id=293529 Silver Salonen changed: What|Removed |Added Version|2.4-snapshots |3.2.1 Status|RESOLVED|REPORTED Platform|OpenSUSE|Manjaro Resolution|UPSTREAM|--- --- Comment #5 from Silver Salonen --- Sorry, this seems to be happening still as discovered when reproducing https://bugs.kde.org/show_bug.cgi?id=222843 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 222843] content with multiple rows are shown on other cells
https://bugs.kde.org/show_bug.cgi?id=222843 Silver Salonen changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Platform|OpenSUSE|Manjaro Version|2.5.0 |3.2.1 --- Comment #12 from Silver Salonen --- Yes, I can still reproduce it and it acts really weird. See the screenshots - following their order by filenames, I did the following: 1. Entered 3-line text into A2 and selected A2 2. Entered some text into B2 3. Undo - text was removed from B2, but contents of A2 is displayed partially only 4. Entered some text into B3 5. Undo - the same as in point 3 6. Undo - text was left in cell editor, although removed from A2 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 222843] content with multiple rows are shown on other cells
https://bugs.kde.org/show_bug.cgi?id=222843 --- Comment #11 from Silver Salonen --- Created attachment 154742 --> https://bugs.kde.org/attachment.cgi?id=154742&action=edit Screenshot 5 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 222843] content with multiple rows are shown on other cells
https://bugs.kde.org/show_bug.cgi?id=222843 --- Comment #10 from Silver Salonen --- Created attachment 154741 --> https://bugs.kde.org/attachment.cgi?id=154741&action=edit Screenshot 4 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 222843] content with multiple rows are shown on other cells
https://bugs.kde.org/show_bug.cgi?id=222843 --- Comment #9 from Silver Salonen --- Created attachment 154740 --> https://bugs.kde.org/attachment.cgi?id=154740&action=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 222843] content with multiple rows are shown on other cells
https://bugs.kde.org/show_bug.cgi?id=222843 --- Comment #8 from Silver Salonen --- Created attachment 154739 --> https://bugs.kde.org/attachment.cgi?id=154739&action=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 222843] content with multiple rows are shown on other cells
https://bugs.kde.org/show_bug.cgi?id=222843 --- Comment #7 from Silver Salonen --- Created attachment 154738 --> https://bugs.kde.org/attachment.cgi?id=154738&action=edit Screenshot 1 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 295921] cut-pasting formulas changes referencing formulas
https://bugs.kde.org/show_bug.cgi?id=295921 Silver Salonen changed: What|Removed |Added Version|2.4.1 |3.2.1 Platform|OpenSUSE|Manjaro -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 293541] column-only references don't work
https://bugs.kde.org/show_bug.cgi?id=293541 Silver Salonen changed: What|Removed |Added Platform|OpenSUSE|Manjaro -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 293541] column-only references don't work
https://bugs.kde.org/show_bug.cgi?id=293541 Silver Salonen changed: What|Removed |Added Version|2.4-snapshots |3.2.1 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 295921] cut-pasting formulas changes referencing formulas
https://bugs.kde.org/show_bug.cgi?id=295921 Silver Salonen changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Silver Salonen --- Still an issue. -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 293541] column-only references don't work
https://bugs.kde.org/show_bug.cgi?id=293541 Silver Salonen changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Silver Salonen --- Does not work still. -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 293529] undo is not reflected in active cell's formula
https://bugs.kde.org/show_bug.cgi?id=293529 Silver Salonen changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #4 from Silver Salonen --- Seems to be working as expected now -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 297960] deleting multiple cells with delete does not work
https://bugs.kde.org/show_bug.cgi?id=297960 Silver Salonen changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #4 from Silver Salonen --- Seems to be working as expected now -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 344579] remember resolution setting for current krdc size
https://bugs.kde.org/show_bug.cgi?id=344579 Silver Salonen changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #4 from Silver Salonen --- I just tried it again and I see it's actually fixed now. I'll set the Status to Resolved + Upstream. I hope it's correct? -- 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 #35 from Glassed Silver --- (In reply to caulier.gilles from comment #31) > About Apple Live Photo, Samsung's Motion Photos, and Huawei's Moving > Picture, i'm not sure where the differences are located. > > I'm sure that Apple Live Photo is HEIF based. > > in all cases libheif must support these format to access to image and video > data in container. About metadata, libexiv2 will support Base Media Format > (HEIF and AVIF containers) with next 0.27.4 release planed for June 2021. Modern implementations yes, but before Apple adopted HEIF Live Photos existed as well and there's plenty of JPEG-based Live Photo backlog that would be in I bet many users' libraries. :) -- 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 #30 from Glassed Silver --- Just checked the release notes for 7.2 and noticed that Apple Live Photo Support has been scheduled for 7.4, which is fantastic! I have one question though, are competing, similar formats like Samsung's Motion Photos, Huawei's Moving Picture and possibly other contenders that may be relevant in later feedback still on track for release as well? Personally for my own needs I am using Apple and Samsung's formats, so those would be my main concern, but Huawei is also pretty popularly used. Not sure what other manufacturers put out there, but having Apple, Huawei, Google and Samsung included would cover a large share of the market. Photo enthusiasts with mobile device choices around their creative needs may even go for some other brands, but I'm pretty sure those need not be the focus for now and could get added once the main share of the market is implemented and has gone through some wider trialing in the field I guess? Also, if desired I could add a new Samsung Motion Photo sample taken with a newer device (Note20 Ultra) just in case there are alterations to Samsung's implementation. (doubt it, but I want to be as assisting in this implementation as possible and providing samples is something I can do pretty nicely as someone who doesn't develop themselves) -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 222840] "Goto Cell" selects wrong cell when cell's width is zero
https://bugs.kde.org/show_bug.cgi?id=222840 --- Comment #2 from Silver Salonen --- I just tried again with Calligra Sheets 3.2.1 on Manjaro. It still happens, but you need to really hide the column instead of resizing it. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 316962] use external addressbook for storing recent addresses
https://bugs.kde.org/show_bug.cgi?id=316962 --- Comment #2 from Silver Salonen --- I've not been following KDE PIM for a while, but I guess it's not been implemented. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 180275] Profile support in dolphin
https://bugs.kde.org/show_bug.cgi?id=180275 --- Comment #5 from Silver Salonen --- I think it's still relevant as Dolphin doesn't have profile support yet. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 399232] Add linux pass backend to KDE Wallet service
https://bugs.kde.org/show_bug.cgi?id=399232 Silver Salonen changed: What|Removed |Added CC||silver.salo...@gmail.com --- Comment #1 from Silver Salonen --- This universal password manager's backend in KWallet would be indeed very welcome! -- 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 #28 from Glassed Silver --- (In reply to caulier.gilles from comment #27) > Don't be afraid. HEIF and CR3 support are popular format, and Bugzilla is > here to remember the important entry (you can vote for this support here > too). > > HEIF is Android and Apple used format -> very popular > CR3 is Canon RAW file -> a major actor in photography. > > So... > > Gilles Caulier Well, I'm a CR2 user thanks to my 60D, I know it's pretty much inevitable a solution will be found. HEIF isn't just Apple and Android though, I think in the future demand for it will rise quite a bit more, because it does provide substantial space savings which can be applied elsewhere too. Oh also I wanted to let you know that I've donated to Digikam a few days ago because seeing the Live Photo format getting picked up alerted me to help out a bit myself. When this issue gets resolved I'll be looking at weeks if not months of carefully moving data to Digikam and trialing productive use with a large library. Finally a home for my photography and videoclips again. Much love from Germany! :) -- 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 #26 from Glassed Silver --- Thank you so much for your input. I wasn't trying to advocate for a work-around, I was just trying to make sense of why you're optimistic, since this seems like it could go either way over at that project. At least from what I read regarding the potential legal implications. I gave the OP post a thumbs up, I guess that's what you meant by voting for it. Again thank you so much and I'll just adopt your hopefulness and anticipate the release, hopefully with CR3 and HEIC metadata support. I guess one way or another a way has to be found either way eventually, so if I don't completely misinterpret this, if the feature doesn't make it into 7.0, hope wouldn't be completely lost? Cheers! -- 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 #24 from Glassed Silver --- (In reply to caulier.gilles from comment #23) > yes, HEIF is supported in digiKam 7.0.0 right now, but not yet the video > embeded. > > The problem is with Exiv2 which refuse to support HEIF due to possible > patents. > > If HEIF will host video, we will need to be able to extract this data, and > Exiv2 sound like the best way to operate. > > > The problem between HEIF and EXiv2 do not touch only HEIF, but all formats > based on ISO base media format: > > https://en.wikipedia.org/wiki/ISO/IEC_base_media_file_format > > This include also the famous Canon CR3 raw files, and it's very problematic > for the future... > > https://github.com/Exiv2/exiv2/issues/236 > > So we need to have a plain support of ISO/IEC 14496-12 format first before > to support extra video from this kind of container... > > Gilles Caulier Maybe I'm missing something here, but if we rely on a third-party dependency to resolve this and they don't release a solution in code before July (and even that isn't certain) how can you be sure that this feature is on track for 7.0 final scheduled to release on or around July 12? Do you have an intermediary workaround in mind to use until this gets resolved? Thanks for the wealth of background info as well! Very interesting to see this unfold and at the same time I cannot stop but cry over software patents being a thing... ESPECIALLY for things like file formats. Real innovation stifling at work... -- 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 #22 from Glassed Silver --- (In reply to caulier.gilles from comment #21) > Thanks Ritesh. I will take a look. > > Gilles Caulier Forgive me if I may come across as impatient, I am just very thankful for finally being close to getting the long awaited Aperture replacement... (yep... I held out this long!) My question is: is this feature still on track for 7.0 final? Again, thank you so so much for even getting on this, bridging the different kinds of live photo-like implementations no less. I really think it's a very transformative format of our time and I cannot tell you how often I've been enjoying the little bit of extra life Live Photos and similar approaches have brought to me. -- 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 #17 from Glassed Silver --- https://drive.google.com/drive/folders/1PgxB3JBql7kRzOkEzhBwqKQUXtddcLAj?usp=sharing The filesize limit doesn't allow me to include the files directly, which is a shame, not a fan of link rot and I gotta admit, this link WILL go down once this issue is resolved, because I don't like lingering public links on my Drive account. Either way, I included a sample for Huawei's "Moving Picture" implementation. (consumer info page: https://consumer.huawei.com/uk/support/faq/how-to-take-moving-pictures/) The pic was taken on my MediaPad M5 8.4" tablet. Not amazing quality on that one, but should do the trick of showing the file's logic. I also included a sample for Samsung's "Motion Photo". (consumer info page: https://www.samsung.com/global/galaxy/what-is/motion-photo/ (it doesn't list S20 as compatible device, but it's been reported that it is indeed still a maintained feature, guess they forgot to update that page so far) That pic was taken with my Galaxy Note9. Forgive the dirty keyboard... -- 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 Glassed Silver changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #15 from Glassed Silver --- Why is this item flagged as resolved? Live Photos are still just presented as a separate JPG/HEIC and a .mov. Here's some further reading if it helps grasp the concept of how it all works how it's designed to be a) detected b) treated/viewed. 1) Very nice conclusive overview post on Reddit, also links to sample images for Apple's version, but also Google's. https://www.reddit.com/r/DataHoarder/comments/cuk06h/help_preserving_iphone_live_photos_how_they_seem/exx2rj6/ 2) This is another program written in C++ that to my knowledge correctly implements Live Photos: https://github.com/LycheeOrg/Lychee-Laravel/issues/378 3) Apple's HIG on how Live Photos should be treated: https://developer.apple.com/design/human-interface-guidelines/live-photos/overview/ If desired I can provide a sample for Samsung's implementation, too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415171] I try to save art, at this time Crete is closed
https://bugs.kde.org/show_bug.cgi?id=415171 Silver changed: What|Removed |Added URL||ylitka...@gmail.com Keywords||release_blocker -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415171] New: I try to save art, at this time Crete is closed
https://bugs.kde.org/show_bug.cgi?id=415171 Bug ID: 415171 Summary: I try to save art, at this time Crete is closed Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: grave Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ylitka...@gmail.com Target Milestone: --- SUMMARY I can't save art in any format. I open the file, click "save as", select the format. Then on the process of saving Krita is closed. Thus I cannot finish art STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows:7 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.
[krita] [Bug 410793] Settings dialog is too high for very space constrained screens
https://bugs.kde.org/show_bug.cgi?id=410793 --- Comment #7 from Galaxy Silver --- Hello! I appreciate that the both of you are replying to my bug, but I don't know what can I do with the latest info/link you provided to me? Should I change the app's code? I mean, I'm fine with the buttons being blocked rather than ruining the whole app because I'm not tech-savvy enough, I never changed or copied and pasted code to Krita before, despite it being open source. (Also, yes, the display scaling isn't helping, mine is in the lowest setting, if you're wondering...)On Monday, August 12, 2019, 02:08:48 PM GMT+7, Boudewijn Rempt wrote: https://bugs.kde.org/show_bug.cgi?id=410793 Boudewijn Rempt changed: What |Removed |Added Latest Commit| |https://invent.kde.org/kde/ | |krita/commit/14d3ca274c700d | |369b7f3094e35dcc4a45cfc509 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Boudewijn Rempt --- Git commit 14d3ca274c700d369b7f3094e35dcc4a45cfc509 by Boudewijn Rempt. Committed on 12/08/2019 at 07:08. Pushed by rempt into branch 'master'. Split the display settings page in tabs M +545 -458 libs/ui/forms/wdgdisplaysettings.ui https://invent.kde.org/kde/krita/commit/14d3ca274c700d369b7f3094e35dcc4a45cfc509 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410793] Settings dialog is too high for very space constrained screens
https://bugs.kde.org/show_bug.cgi?id=410793 --- Comment #2 from Galaxy Silver --- My screen resolution is 1366 x 768, and I don't know where to check my font and display scaling, unless it's a setting on Krita and not Windows? On Aug 11, 2019 12:49 AM, Boudewijn Rempt wrote: https://bugs.kde.org/show_bug.cgi?id=410793 Boudewijn Rempt changed: What |Removed |Added Severity|normal |minor CC| |b...@valdyas.org Summary|Confirm Buttons are Blocked |Settings dialog is too high |by Taskbar |for very space constrained | |screens --- Comment #1 from Boudewijn Rempt --- Looks like your screen's resolution is too low, or your display scaling set too high. What is the resolution of your screen and what is the display scaling and font scaling set to? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410793] New: Confirm Buttons are Blocked by Taskbar
https://bugs.kde.org/show_bug.cgi?id=410793 Bug ID: 410793 Summary: Confirm Buttons are Blocked by Taskbar Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: argentinecos...@yahoo.com Target Milestone: --- Created attachment 122048 --> https://bugs.kde.org/attachment.cgi?id=122048&action=edit Image is "OK" and "Cancel" buttons of Configure Krita window being blocked by Windows taskbar. SUMMARY The "OK" and "Cancel" buttons of the preferences/Configure Krita window are too low, they're off screen, thus it's not possible to press them unless I change the taskbar setting so it's on other side and not on bottom. STEPS TO REPRODUCE 1. Go to Settings 2. Choose Configure Krita... 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 Home Single Language macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
https://bugs.kde.org/show_bug.cgi?id=385726 --- Comment #12 from Glassed Silver --- I think if we're going to implement a unified view for the JPG (or HEIF) and movie pair we shouldn't use the regular grouping function, because then we couldn't group multiple Live Photos without creating a messy situation when you ungroup them again. So in a way, we'd probably need a "level zero grouping" so to say. (sorry, can't find a good way to phrase it) You say we should create a new ticket for that then? Not sure about that, but I could do that. Whilst we're at it we might as well implement other popular Live Photo-like implementations as well and use the same unified view for that. Samsung has Motion Photos, Google has Motion Photos as well on Pixel devices and some Android One phones as well I think (I know the Nokia 3.1 has that too for example) and then Huawei has an implementation very much like Apple's too. They all work a little different, but technically it's always a pair of image and movie files being fused into one element visually. Samsung for example embeds the video into the image file itself (making the JPG bigger in size). I know this might sound like a lot at once, but I swear to God, despite me owning a nice and lovely Canon DSLR often times I will at least take a picture a second time with my smartphone just to capture a Live Photo. It really adds that much more to pictures and lets you relieve moments a bit more vividly that didn't seem like a "video moment" but the little bit of motion can often times add a lot. -- 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 #10 from Glassed Silver --- Created attachment 120775 --> https://bugs.kde.org/attachment.cgi?id=120775&action=edit Apple Photos Live Photo View -- 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 #9 from Glassed Silver --- Created attachment 120774 --> https://bugs.kde.org/attachment.cgi?id=120774&action=edit Screenshot digikam Live Photo as two separate entries -- 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 #8 from Glassed Silver --- Wooops, no not 2 for each, I changed my phrasing mid-sentence and then that happened. Sorry. It's one entry for the image and video part each. So it shows the technically correct two files as what they are - technically - 2 files. However the whole point of Live Photos isn't that the capture process is bundled, but also viewing the image alongside the video seamlessly. Default settings basically beyond some preferences during install wizard. SQLite db, locally stored. No sidecar files. Attached screenshot of digikam and a short video screencap of Apple Photos viewing a Live Photo. As you can see it only displays one entry visually for the IMG_nnn.JPG & IMG_nnn.MOV pair and on mouse hover it will start playing the video bit without sound and if you go into view mode you can play with sound there. (latter not shown) -- 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 Glassed Silver changed: What|Removed |Added CC||glassedsil...@gmail.com --- Comment #6 from Glassed Silver --- Just tried adding a Live Photo to digikam 6.1 on macOS and all it produces is two entries for the image and the video part each. It doesn't show the two files as one entry as you'd expect coming from Apple Photos. If this is how it's supposed to work, it's a wrong implementation and not doing anything more than just importing the two files as presented by ANY other software. I would not call this Live Photo support then. However I assume this might be an incompatibility with the macOS port yet? Should I try the GNU/Linux version or is there any other thing to keep in mind? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402462] New: Gradient effect that I make custom isn't saved, so when I reopen the file, Krita takes the current foreground color and background color as gradient effect, and also the mode
https://bugs.kde.org/show_bug.cgi?id=402462 Bug ID: 402462 Summary: Gradient effect that I make custom isn't saved, so when I reopen the file, Krita takes the current foreground color and background color as gradient effect, and also the mode is back to Normal/Multiply with 75% opacity (the default gradient effect setting Product: krita Version: unspecified Platform: unspecified OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: argentinecos...@yahoo.com Target Milestone: --- SUMMARY Gradient effect that I make custom isn't saved, so when I reopen the file, Krita takes the current foreground color and background color as gradient effect, and also the mode is back to Normal/Multiply with 75% opacity (the default gradient effect settings. STEPS TO REPRODUCE 1. Make a custom gradient layer style 2. Save the file, then close the file 3. Reopen the file OBSERVED RESULT Custom gradient isn't saved, Krita instead picks new colors from foreground and background colors as the gradient, and gradient style is always back to Normal/Multiply. EXPECTED RESULT Gradient colors and mode stays the same (doesn't pick new colors) after the file is saved, closed, and reopened. SOFTWARE/OS VERSIONS Windows: 10 MacOS: - Linux/KDE Plasma: - (available in About System) KDE Plasma Version: - KDE Frameworks Version: - Qt Version: - ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #23 from Silver Salonen --- I don't know now... to me it has really boiled down to Keyring blocking the input. Is there something that can be done about it from KDE/Plasma side? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #20 from Silver Salonen --- One additional weird nuance - on startup both KWallet and Gnome Keyring are asking for input (the latter because of Skype). Even if KWallet is focused then keyboard input does not work until I haven't inserted password for Keyring. Also it seems that keyboard input does not work within the whole environment, eg. Alt+Tab, Alt+F2, Launcher menu search. After I submit anything into Keyring dialog, keyboard input starts working for both Plasma and KWallet dialog. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #17 from Silver Salonen --- To my mind it's somewhat clear that it is related to ibus, but is it really clear how? As I understand on one case ibus crashes and this causes keyboard input issues, but on another case (mine) the issue is solved when this solves issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #15 from Silver Salonen --- Sorry, I'm giving inconsistent information :/ I did full upgrade of all my software (did not re-install ibus) and restarted my computer, and now keyboard input works also for KWallet right after login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #14 from Silver Salonen --- For me it doesn't indeed change a thing - I removed everything related to ibus and after logging out and in again the state is exactly the same. Ie. input in KWallet input request does not work, but to some other applications input works. This has somehow improved since some time (as I reported at some point, input in KRunner dialog or in launcher menu didn't work, but now it does), but I have no idea with what and when exactly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 Silver Salonen changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED --- Comment #11 from Silver Salonen --- Okay, I cheered to soon. For me ibus-daemon doesn't actually crash - it's running fine after I log into Plasma5. When I don't have it running then input just doesn't work in even more applications. But killing or restarting it doesn't make everything work still :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 Silver Salonen changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #10 from Silver Salonen --- Ok, I'll mark it as duplicate then. *** This bug has been marked as a duplicate of bug 379930 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379930] kcm_keyboard kills ibus daemon, entirely breaking the keyboard
https://bugs.kde.org/show_bug.cgi?id=379930 Silver Salonen changed: What|Removed |Added CC||silver.salo...@gmail.com --- Comment #10 from Silver Salonen --- *** Bug 376966 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #7 from Silver Salonen --- Wow, that totally fixes the problem for me! Thank you very much Theo! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #3 from Silver Salonen --- One interesting nuance I've noticed lately is that after logging in KWallet password prompt input works only a while - if I enter my password within 5 seconds or so then it works, but after that not anymore. Also, it sometimes happens in Konsole that input works in the newly opened window for some time, but then stops working. I then need to open a new window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] New: Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 Bug ID: 376966 Summary: Keyboard input does not work for some applications Product: plasmashell Version: 5.9.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: silver.salo...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Keyboard input in some KDE applications just does not work sometimes. 2 certain applications where it does not work during every session are: - The menu widget (does not matter whether Application Launcher or Application Menu) - in there the first letter is reflected, but after no more letters are accepted. - Alt+F2 launcher - no input works whatsoever It seems that it's most likely so for any KDE applications that are started at session startup (eg. Konsole from the last session). I have not seen this problem in any non-KDE applications (Thunderbird, LibreOffice, VLC, terminal applications, ...). I have had this problem already like a year or so, but have been just living with it (work-arounds like copy-pasting phrases written in some other application). Also, some weeks ago I upgraded to some beta release by accident (when playing around with repositories) and in there the problem was gone, but as soon as I downgraded to stable release again, it re-appeared. -- You are receiving this mail because: You are watching all bug changes.
