[kdeconnect] [Bug 362990] Add feature: android as external microphone
https://bugs.kde.org/show_bug.cgi?id=362990 Connor changed: What|Removed |Added CC||ligert...@hotmail.com --- Comment #4 from Connor --- id like this feature aswell, being able to send audio inputs and outputs to other devices would be very useful -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 432365] New: Proxy Clips Concurrent Thread limit doesn't work?
https://bugs.kde.org/show_bug.cgi?id=432365 Bug ID: 432365 Summary: Proxy Clips Concurrent Thread limit doesn't work? Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: bi...@ivdc.com Target Milestone: --- Created attachment 135337 --> https://bugs.kde.org/attachment.cgi?id=135337&action=edit Error When using proxy clips, my GPU is limited to 3 encoders. I set the proxy concurrent thread limit to 1 and it still tries to run multiple proxy threads resulting in attached error. I have to cancel the job, and do proxy on individual clips. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 432365] Proxy Clips Concurrent Thread limit doesn't work?
https://bugs.kde.org/show_bug.cgi?id=432365 --- Comment #1 from Connor --- Created attachment 135338 --> https://bugs.kde.org/attachment.cgi?id=135338&action=edit Thread limit in Enironment -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441451] New: Normalize (2 pass) doesn't work on channel level or cut audio clips.
https://bugs.kde.org/show_bug.cgi?id=441451 Bug ID: 441451 Summary: Normalize (2 pass) doesn't work on channel level or cut audio clips. Product: kdenlive Version: 21.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: bi...@ivdc.com Target Milestone: --- The normalize (2 pass) effect doesn't work at all when applied at the channel or master level. You click the Analyse button, it processes, then it comes back with the Analyse button vs a reset and no changes in the audio level. Additionally, it doesn't work correctly when you apply it to a clip that is been cut up into segments. Again, It processes, then comes back with the Analyse button vs a reset, and no changes in the audio levels. It looks like it ONLY works with complete, unaltered clips. This is unfortunate, as I want to apply it to a whole track/channel to normalize my audio levels. The single pass version can be applied to at the channel level, however, it's a sliding scale, and when you Upload to YouTube, your video still undergoes additional normalization that may not be what you want. (YouTube normalizes at -14LUFS, bringing everything down to that, but nothing up to it). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441452] New: Audio Mixer VU meter doesn't reflect levels on effects applied at channel level.
https://bugs.kde.org/show_bug.cgi?id=441452 Bug ID: 441452 Summary: Audio Mixer VU meter doesn't reflect levels on effects applied at channel level. Product: kdenlive Version: 21.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: bi...@ivdc.com Target Milestone: --- Audio Mixer VU meter doesn't reflect levels on effects applied at channel level. If for example, you apply a Volume, or Normalize effect on a channel, the channels VU bars still show the clips values before applying those effects. The Master VU bar DOES reflect the changes. This makes it hard to review peak values and confirm that your effects are working. If you apply the effects on the individual clips, then the VU meter reflects the proper levels. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441452] Audio Mixer VU meter doesn't reflect levels on effects applied at channel level.
https://bugs.kde.org/show_bug.cgi?id=441452 --- Comment #1 from Connor --- Also, if you apply the effects at the master level, the Master VU will not reflect the the proper levels. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439658] New: Align to Audio Reference sometimes is off.
https://bugs.kde.org/show_bug.cgi?id=439658 Bug ID: 439658 Summary: Align to Audio Reference sometimes is off. Product: kdenlive Version: 21.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: bi...@ivdc.com Target Milestone: --- While aligning a external audio clip to a video with embedded audio, it sometimes can be off by a frame or two. (or half a frame). I just edited a video and didn't bother to listen to the in-video audio track vs my separately recorded audio track and found lip sync issues after render (didn't really notice them with proxy clips and 540p video in the preview monitor). When I turned on the embedded audio track, and played both audio clips together, It produced a echo. Manually adjusting the audio clip back/forward by 1 or 2 frames typically fixed it. Although, being able to adjust by 1/4 or 1/2 a frame would prove useful too as it still had a hint of a echo on one clip. This didn't happen with every clip. Also, I use a Clap board with all my takes as well, so, shouldn't be ambiguous. Additional info: Files are .MOV files including the audio only (which appear as full video but, I just ungroup and delete the video channel) Hardware: iPhone 12 Pro MAX and iPhone 8 for Camera's, iPad Air (Gen 3) as the audio recorder with a RODE GO II Wireless mic. 1080p 30fps. -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 479006] New: gp undecrytable
https://bugs.kde.org/show_bug.cgi?id=479006 Bug ID: 479006 Summary: gp undecrytable Classification: Miscellaneous Product: unknown Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: crmcrm2...@outlook.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. 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 -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 479006] gp undecrytable
https://bugs.kde.org/show_bug.cgi?id=479006 --- Comment #1 from Connor --- Created attachment 164445 --> https://bugs.kde.org/attachment.cgi?id=164445&action=edit kleopatra -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474154] Crashes When Clicking on Second Clip with Effect
https://bugs.kde.org/show_bug.cgi?id=474154 --- Comment #4 from Connor --- Created attachment 162065 --> https://bugs.kde.org/attachment.cgi?id=162065&action=edit Kdenlive screenshot with a split clip in the timeline, each clip having effects -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474154] Crashes When Clicking on Second Clip with Effect
https://bugs.kde.org/show_bug.cgi?id=474154 --- Comment #5 from Connor --- I'm applying the effects to the clips in the timeline, not in the bin. Sorry, I wasn't clear about that in my original post. I threw together a quick example in the screenshot I attached. There's one clip in the bin, but it's been cut in the timeline, and each section of the clip has a transform effect. The bug occurs for other effects and kinds of clips as well. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474154] Crashes When Clicking on Second Clip with Effect
https://bugs.kde.org/show_bug.cgi?id=474154 --- Comment #7 from Connor --- I tried the newest AppImage again, and it still crashes unless I open the app in the terminal with sudo. And the Flatpak version behaves the same after updating it and all its related libraries. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474154] New: Crashes When Clicking on Second Clip with Effect
https://bugs.kde.org/show_bug.cgi?id=474154 Bug ID: 474154 Summary: Crashes When Clicking on Second Clip with Effect Classification: Applications Product: kdenlive Version: 23.08.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: connorwmcgona...@gmail.com Target Milestone: --- SUMMARY Kdenlive is crashing whenever I try to click between clips with effects. More accruately, if I've clicked on a clip with an effect, then the next clip that I click on that also has an effect will cause the application to crash. So if I click on clip 1 with an effect then click on clip 2 that has nothing, it won't crash, but then if I click on clip 3 that has an effect, Kdenlive will freeze as it's trying to load whatever effect it is, then will crash. This bug originally occurred for me on a 23.08.0 Flatpak install, but the issue persisted when I downgraded to 23.04.3 and even when I tried AppImages of different versions. ***Backtrace and extra gdb context: // SHOW KEYFRAMES: true MUTEX LOCK setmodel MUTEX UNLOCK setmodel MUTEX LOCK loadEffects COUNT: 1 // // // RESULTING REQUIRED SCENE: 1 MUTEX UNLOCK loadEffects - // SHOW KEYFRAMES: true deleting collapsibleeffectview terminate called after throwing an instance of 'std::out_of_range' what(): unordered_map::at Thread 1 "kdenlive" received signal SIGABRT, Aborted. 0x74a6f204 in __pthread_kill_implementation () from /usr/lib/x86_64-linux-gnu/libc.so.6 (gdb) thread apply all bt full Thread 222 (Thread 0x7ffe8effd640 (LWP 257) "QQuickContext2D"): Couldn't get registers: No such process. (gdb) STEPS TO REPRODUCE 1. Make a new Kdenlive project. 2. Import two different clips of whatever kind (video/image/audio) into the project bin. 3. Apply an effect to both clips. 4. Click between them. OBSERVED RESULT Kdenlive freezes then crashes. EXPECTED RESULT The effects of the selected clip load successfully in the Effect/Composition Stack window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Mint 21.1 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 MLT Version: 7.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474154] Crashes When Clicking on Second Clip with Effect
https://bugs.kde.org/show_bug.cgi?id=474154 --- Comment #1 from Connor --- Just discovered this is similar to Bug 467515, but it seems like that one was never completely resolved. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474154] Crashes When Clicking on Second Clip with Effect
https://bugs.kde.org/show_bug.cgi?id=474154 --- Comment #2 from Connor --- Also just found this reddit post that talks about the same issue: https://www.reddit.com/r/kdenlive/comments/116809e/kdenlive_22122_appimageflatpak_crashes_when/ And, like them, when I run the Kdenlive AppImage with sudo, it does not crash. At the very least, it's comforting to have that workaround until the real problem is found. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 431603] New: When searching for applications results are not as expected.
https://bugs.kde.org/show_bug.cgi?id=431603 Bug ID: 431603 Summary: When searching for applications results are not as expected. Product: krunner Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: cjbornak...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When searching for Konsole after typing "ko" Konsole suggested. When typing "kon" another application is the first result. (In my case Atom Text Editor) Similar behavior is observed when searching for About and other applications. STEPS TO REPRODUCE 1. Open Krunner (or kickoff) 2. Search for applications using different amounts of letters 3. Observe results OBSERVED RESULT Wrong application suggested when searching with 3 characters EXPECTED RESULT Correct application suggested when using any amount of characters (within reason) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon Unstable (available in About System) KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION * This bug may be filed in the wrong place because the new kickoff replacement has the same issue. * -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 431603] When searching for applications results are not as expected.
https://bugs.kde.org/show_bug.cgi?id=431603 --- Comment #5 from Connor --- I will as soon as I’m back on my computer. (In reply to Alexander Lohnau from comment #4) > I fear this is once again an issue with the RunnerContext relevance logic. > > @Connor could you please share your ~/.config/krunnerrc file? (Only if that > is okay with you, please check if there is any sensitive information > contained). The [PlasmaRunnerManager] group might help reproducing this > issue. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 431603] When searching for applications results are not as expected.
https://bugs.kde.org/show_bug.cgi?id=431603 --- Comment #6 from Connor --- Created attachment 134872 --> https://bugs.kde.org/attachment.cgi?id=134872&action=edit krunnerrc file as requested by Alexander Lohnau -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 431603] When searching for applications results are not as expected.
https://bugs.kde.org/show_bug.cgi?id=431603 --- Comment #7 from Connor --- I would also like to note that as of right now I am no longer having this issue with Konsole and Atom, but now when using 3 (or 4) characters to search for Firefox the first suggestion is System Settings. -- You are receiving this mail because: You are watching all bug changes.
[kbackup] [Bug 425693] New: KUP Backup cant be loaded
https://bugs.kde.org/show_bug.cgi?id=425693 Bug ID: 425693 Summary: KUP Backup cant be loaded Product: kbackup Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kol...@aon.at Reporter: ligert...@hotmail.com Target Milestone: --- SUMMARY The backup created by KUP can not be accessed, if from kup-filedigger "open" is selected then dolphin gives the error "No bup repository found. bup:///kup//"" This stops the backups from being used or accessed at all. STEPS TO REPRODUCE 1. Use kup-filedigger in a kup backup 2. Select "open" on a folder OBSERVED RESULT Dolphin opens and gets the error "No bup repository found. bup:///kup//". EXPECTED RESULT The backuped folder to be openned. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 425693] KUP Backup cant be loaded
https://bugs.kde.org/show_bug.cgi?id=425693 --- Comment #3 from Connor --- Sorry about the lack of info for reproducing, there wasnt a lot i could say sadly. How do i open filedigger without a path argument? if this is attempted it says that a path argument is required. Do i not have something installed? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422652] New: Minimizing in multi-monitor environment buggy / Clip monitor disappears after loading view.
https://bugs.kde.org/show_bug.cgi?id=422652 Bug ID: 422652 Summary: Minimizing in multi-monitor environment buggy / Clip monitor disappears after loading view. Product: kdenlive Version: 20.04.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: bi...@ivdc.com Target Milestone: --- Created attachment 129146 --> https://bugs.kde.org/attachment.cgi?id=129146&action=edit Video of the issue SUMMARY When using in Multi-Monitor environment, the Clip monitor and Project monitor do not minimize or maximize when min/maxing the main kdenlive gui. If you Load Layout, it will work. But, then I found, that you have to Load layout TWICE to get the clip monitor to re-appear. See video attached. STEPS TO REPRODUCE 1. Launch kdenlive - Move Clip monitor to one screen, project monitor to the other 2. Minimize kdenlive 3. Note that only the main gui minimized 4. Restore kdenlive 5. Load Layout 6. Observe Clip monitor not showing. 7. Minimize kdenlive - it minimizes everything correctly 7. Load layout again - Clip monitor shows up - Minimizing works correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410675] Artistic color selector gets out of sync in HSV/HSL mode
https://bugs.kde.org/show_bug.cgi?id=410675 Connor changed: What|Removed |Added CC||iamnotaju...@gmail.com --- Comment #3 from Connor --- Confirm. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365372] HSY' square color selector does not display the correct square content for a given hue
https://bugs.kde.org/show_bug.cgi?id=365372 Connor changed: What|Removed |Added CC||iamnotaju...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421301] New: Color select with stylus causes loss of focus/prevents other keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=421301 Bug ID: 421301 Summary: Color select with stylus causes loss of focus/prevents other keyboard shortcuts Product: krita Version: 4.3.0-beta1 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: iamnotaju...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Press Shift I, and select a color with your stylus OBSERVED RESULT No other shortcuts work, the toolbar at the top which contains the erase icon shows as having lost focus. EXPECTED RESULT Ctrl-z and other shortcuts would work. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION When I use my mouse there is no issue, only when I select with stylus. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421301] Color select with stylus causes loss of focus/prevents other keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=421301 --- Comment #1 from Connor --- To add more detail: Specifically when I move the cursor outside of the select window (after choosing a color), then the focus is lost, and shortcuts are no longer received by krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421301] Color select with stylus causes loss of focus/prevents other keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=421301 --- Comment #2 from Connor --- It looks like when I try with just a mouse, the focus is lost when the cursor leaves the color select window. However, my next mouse click/paint causes focus to be recaptured. It remains uncaptured when using my stylus. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421301] Color select with stylus causes loss of focus/prevents other keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=421301 --- Comment #5 from Connor --- I’m using the XMonad WM. Focus does return for me when I use the mouse, it does not with the stylus. Thanks for looking into this. It may just be an xmonad issue. On Thu, May 14, 2020 at 4:08 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=421301 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #4 from Boudewijn Rempt --- > What window manager are you using? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377410] New: Option "Open archives as folder" mounts read-only
https://bugs.kde.org/show_bug.cgi?id=377410 Bug ID: 377410 Summary: Option "Open archives as folder" mounts read-only Product: dolphin Version: 15.04.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: cnnr_dh...@live.com Target Milestone: --- I was searching for a way to get the convenient archive mounting found in nautilus, and wound up making an annoying script with the package "archivemount" which did the trick. Little did I know, Dolphin has this option in Preferences > Navigation > "Open archives as folder". Great! (Should be default IMHO) Anyway, the automount seems to be read-only for some reason. There is no technical reason it needs to be read-only - mounting archives as a writable filesystem works just fine with archivemount - so this decision is rather arbitrary, which is why I've classed it a bug rather than feature request. I can think of some plausible social and psychological reasons why mounting read-only might be a good default, but that doesn't mean full access shouldn't be possible even as an option. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #11 from connor --- Created attachment 182343 --> https://bugs.kde.org/attachment.cgi?id=182343&action=edit log from startup digikam to end -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #14 from connor --- Created attachment 182345 --> https://bugs.kde.org/attachment.cgi?id=182345&action=edit image folder size -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #12 from connor --- Created attachment 182344 --> https://bugs.kde.org/attachment.cgi?id=182344&action=edit highlighted cursor loading all images -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #13 from connor --- After finished adding new items, digikam still not responding why ? I guess the digikam is loading all images. The highlighted cursor is on the top level folder. How many images ? 1.76 million . 22.62 GB. The user can't switch highlight cursor to other folder. If don't load all images when highlighted cursor, the issue will be solved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #7 from connor --- The further log is repeated by adding and adding image files. Every alphabet has 85000+ preview font image files built in python script.Yes. There's not any metadata. I removed my own Exiftools from "C:/Program Files/exiftool/exiftool.exe. However, the GUI has been in an unresponsive state unless all image files are loaded. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #8 from connor --- Log is repeating and adding new items: [11820] digikam.database: Finishing took 1429 ms [11820] digikam.metaengine: Check ExifTool availability: false [11820] digikam.metaengine: ExifTool is not available to load metadata... [11820] digikam.metaengine: Loading metadata with "Exiv2" backend from "H:/ABC.digikam/Jj/1-7/Jj_Poppins-BoldItalic-v3.010PS1.000hotconv16.6.54makeotf.lib2.5.65590.png" [11820] digikam.dimg: "H:/ABC.digikam/Jj/1-7/Jj_Poppins-BoldItalic-v3.010PS1.000hotconv16.6.54makeotf.lib2.5.65590.png" : "PNG" file identified [11820] digikam.dimg.png: Opening file "H:/ABC.digikam/Jj/1-7/Jj_Poppins-BoldItalic-v3.010PS1.000hotconv16.6.54makeotf.lib2.5.65590.png" [11820] digikam.database: Adding new item "H:/ABC.digikam/Jj/1-7/Jj_Poppins-BoldItalic-v3.010PS1.000hotconv16.6.54makeotf.lib2.5.65590.png" [11820] digikam.database: Scanning took 4 ms [11820] digikam.database: Finishing took 2299 ms [11820] digikam.metaengine: Check ExifTool availability: false [11820] digikam.metaengine: ExifTool is not available to load metadata... [11820] digikam.metaengine: Loading metadata with "Exiv2" backend from "H:/ABC.digikam/Jj/1-7/Jj_Poppins-ExtraBold-ExtraBold-Italic.png" [11820] digikam.dimg: "H:/ABC.digikam/Jj/1-7/Jj_Poppins-ExtraBold-ExtraBold-Italic.png" : "PNG" file identified [11820] digikam.dimg.png: Opening file "H:/ABC.digikam/Jj/1-7/Jj_Poppins-ExtraBold-ExtraBold-Italic.png" [11820] digikam.database: Adding new item "H:/ABC.digikam/Jj/1-7/Jj_Poppins-ExtraBold-ExtraBold-Italic.png" [11820] digikam.database: Scanning took 4 ms [11820] digikam.database: Finishing took 1928 ms [11820] digikam.metaengine: Check ExifTool availability: false [11820] digikam.metaengine: ExifTool is not available to load metadata... [11820] digikam.metaengine: Loading metadata with "Exiv2" backend from "H:/ABC.digikam/Jj/1-7/Jj_Poppins-ExtraBold-ExtraBold.png" [11820] digikam.dimg: "H:/ABC.digikam/Jj/1-7/Jj_Poppins-ExtraBold-ExtraBold.png" : "PNG" file identified [11820] digikam.dimg.png: Opening file "H:/ABC.digikam/Jj/1-7/Jj_Poppins-ExtraBold-ExtraBold.png" [11820] digikam.database: Adding new item "H:/ABC.digikam/Jj/1-7/Jj_Poppins-ExtraBold-ExtraBold.png" [11820] digikam.database: Scanning took 4 ms [11820] digikam.database: Finishing took 4879 ms [11820] digikam.metaengine: Check ExifTool availability: false [11820] digikam.metaengine: ExifTool is not available to load metadata... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #4 from connor --- Created attachment 182297 --> https://bugs.kde.org/attachment.cgi?id=182297&action=edit freeze no responding and digikam stopped scan image file. freeze no responding and digikam stopped scanning image files. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #9 from connor --- Created attachment 182301 --> https://bugs.kde.org/attachment.cgi?id=182301&action=edit Not responding Still waiting finished adding new items. [11820] digikam.database: Adding new item "H:/ABC.digikam/Jj/1-7/Jj_Pyrabet.png" [11820] digikam.database: Scanning took 5 ms [11820] digikam.database: Finishing took 2467 ms [11820] digikam.metaengine: Check ExifTool availability: false [11820] digikam.metaengine: ExifTool is not available to load metadata... [11820] digikam.metaengine: Loading metadata with "Exiv2" backend from "H:/ABC.digikam/Jj/1-7/Jj_PyriformTonesNF.png" [11820] digikam.dimg: "H:/ABC.digikam/Jj/1-7/Jj_PyriformTonesNF.png" : "PNG" file identified [11820] digikam.dimg.png: Opening file "H:/ABC.digikam/Jj/1-7/Jj_PyriformTonesNF.png" [11820] digikam.database: Adding new item "H:/ABC.digikam/Jj/1-7/Jj_PyriformTonesNF.png" [11820] digikam.database: Scanning took 4 ms -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #6 from connor --- Created attachment 182300 --> https://bugs.kde.org/attachment.cgi?id=182300&action=edit preview font file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 505631] No responding when loading large image files
https://bugs.kde.org/show_bug.cgi?id=505631 --- Comment #10 from connor --- Summary Report: During the process of adding new image files, the program became unresponsive, and during this period, all other functions were unavailable. It was not until all new images were added that the unresponsive state of the program was lifted and it could be used normally. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450662] New: Unable to install or change cursors via any method
https://bugs.kde.org/show_bug.cgi?id=450662 Bug ID: 450662 Summary: Unable to install or change cursors via any method Product: systemsettings Version: 5.24.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: cekunzm...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Attempt to install a cursor by navigating to System Settings > Appearance > Cursors, clicking Get New Cursors..., and clicking Install next to any of the results. 2. Attempt to install a cursor by navigating to System Settings > Appearance > Cursors, clicking Get New Cursors... and clicking the search result, then clicking the Install button in the upper right-hand portion of the window 3. Manually place a cursor theme into ~/.local/share/icons/ and look for it in the aforementioned section of System Settings. OBSERVED RESULT 1. The cursor theme will appear to install successfully, but when closing the search results screen the new cursor theme will have the default Breeze cursors and not the new ones. Clicking the theme and then clicking Apply has no effect. 2. A dialog box saying "Could not determine the type of archive of the downloaded file /tmp/NameOfTheme.tar. When closing it, another appears saying "File not found". 3. The theme does not appear in the list of cursor themes at all. EXPECTED RESULT The cursor themes should install as usual; this feature worked in a prior installation of KDE Plasma I had been using. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User 5.24 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.13.3 ADDITIONAL INFORMATION Anecdotally, I have seen that other KDE Plasma users on Reddit are posting about issues applying and searching for themes (color schemes, icons). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450662] Unable to install or change cursors via any method
https://bugs.kde.org/show_bug.cgi?id=450662 --- Comment #2 from Connor Kunzmann --- (In reply to Nate Graham from comment #1) > Hmm, those methods all work for me with a few random cursor themes I tested. > Can you provide an example of a cursor theme that is broken for you? > > If you use method 1 and then reboot, is the cursor theme applied as you > expect? A good example would be "X11 DEFAULT BLACK CURSOR SET"; I am unable to install this theme successfully with any method, though I'm unable to install any cursor theme. All cursor themes do this for me - occasionally, I'll find one that will appear to install successfully, but the theme will still show the default Breeze set in its preview. Clicking and applying the theme does nothing. Rebooting does not seem to make any difference in any configuration. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455572] New: "Present Windows" task action does nothing
https://bugs.kde.org/show_bug.cgi?id=455572 Bug ID: 455572 Summary: "Present Windows" task action does nothing Product: lattedock Version: 0.10.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: connor.t...@tuta.io Target Milestone: --- SUMMARY After update to plasma 5.25, the task action "Present Windows" on left click does not do anything. STEPS TO REPRODUCE 1. Plasma/Kwin 5.25.0-1 2. run `latte-dock -rd --default-layout` 3. Open multiple instances of any app 4. Click on the latte icon for that app OBSERVED RESULT The default left click action for tasks is to present windows. Windows are not presented and nothing is printed to the debug log. EXPECTED RESULT Functionality matching that of KWin's "Toggle Present Windows" should be observed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.5-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464899] Incorrect visuals in the log out dialog
https://bugs.kde.org/show_bug.cgi?id=464899 Connor Farrell changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467857] New: Inconsistent drag-by-toolbar behavior in Discover
https://bugs.kde.org/show_bug.cgi?id=467857 Bug ID: 467857 Summary: Inconsistent drag-by-toolbar behavior in Discover Classification: Applications Product: Discover Version: 5.27.3 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: kb...@connorcarney.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When the breeze theme is configured to allow dragging windows by the toolbar, the home and application detail pages support toolbar dragging, while the category and search result pages do not. This is particularly an issue in multi-column mode: the toolbars in the list and detail panes are visually continuous, but can only be dragged from the detail side. (More generally, dragging by the toolbar doesn't work on pages where the content item is a list view) STEPS TO REPRODUCE 1. In system settings > Application Style > Configure Breeze, make sure the Window Drag Mode is set to "Titlebar, Menu Bars and Toolbars" or "All Empty Areas" (this is the default setting) 2. Launch discover, enter a search term, and select an application from the search results 3. Resize the window so that both the search results and the application details are visible in the window 4. Attempt to drag the window by the toolbar above each pane OBSERVED RESULT The window can be dragged by the toolbar on the application detail side, but not on the search result side. EXPECTED RESULT The window should be draggable by both sides of the toolbar (or, failing that, by neither side of the toolbar; the behavior should be consistent). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.10 with KDE 5 from source KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 467857] Inconsistent drag-from-empty-areas-of-toolbar behavior in Discover
https://bugs.kde.org/show_bug.cgi?id=467857 --- Comment #3 from Connor Carney --- Created attachment 157857 --> https://bugs.kde.org/attachment.cgi?id=157857&action=edit list vs layout toolbar behavior I think that the pattern there is something like "pages where the main item is a ListView" which I can reproduce with this minimal example. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464899] Dark bar appears between logout screens when more than one is shown at a time in a multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=464899 Connor Farrell changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Connor Farrell --- I just retested and this also occurs with a homogeneous white wallpaper, all windows closed and a single white panel. While testing I did however notice a few more things: - It only occurs on wayland sessions - It only occurs with the blur effect enabled - It is barely noticeable unless the background contrast effect is also enabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448567] [Wayland] Text in Overview effect for desktops list and window titles is blocky on scaled displays
https://bugs.kde.org/show_bug.cgi?id=448567 --- Comment #13 from Connor Carney --- This issue is fixed for me on master as of https://invent.kde.org/plasma/kwin/-/commit/3aa16bd1ca7720924bbbd2ddf448c51f1589367e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464898] New: Misplaced popups when screen is added after plasma started
https://bugs.kde.org/show_bug.cgi?id=464898 Bug ID: 464898 Summary: Misplaced popups when screen is added after plasma started Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: conf...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY When a new display is added after plasmashell has already started, any popups and tooltips will be placed on the new screen instead of their intended location. STEPS TO REPRODUCE 1. Start Plasma with a single screen active 2. Add a panel to the active screen 3. Add the system tray to the panel 4. Plug in or power on a new screen 5. Click any entry in the system tray excluding the night color control OBSERVED RESULT The popup appears on the leftmost edge of the new screen disconnected from its panel. EXPECTED RESULT The popup appears directly above the panel containing clicked entry. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20230125 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.15.8 Qt Version: 5.15.8 ADDITIONAL INFORMATION On very rare occasions, the bug does not occur when performing the steps below. To reproduce, the steps may have to be repeated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464898] Misplaced popups when screen is added after plasma started
https://bugs.kde.org/show_bug.cgi?id=464898 --- Comment #1 from Connor Farrell --- I made a small mistake regarding the Frameworks Version. The actual version used is: 5.102.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464899] New: Incorrect visuals in the log out dialog
https://bugs.kde.org/show_bug.cgi?id=464899 Bug ID: 464899 Summary: Incorrect visuals in the log out dialog Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: conf...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY The log out dialog has an excessively darkened bar on multi-screen setups STEPS TO REPRODUCE 1. Have more than one screen active 2. Start the log out dialog OBSERVED RESULT An almost completely black bar appears on the edge of all screens. Which edge is affected changes depending on the relative placement of the screens. EXPECTED RESULT All areas of the screen are equally darkened. The visuals are independent of the amount and placement of the screens attached. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230125 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Mesa: 22.3.3 (AMD) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464899] Incorrect visuals in the log out dialog
https://bugs.kde.org/show_bug.cgi?id=464899 --- Comment #2 from Connor Farrell --- Created attachment 155705 --> https://bugs.kde.org/attachment.cgi?id=155705&action=edit Screenshot of the problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464899] Incorrect visuals in the log out dialog
https://bugs.kde.org/show_bug.cgi?id=464899 Connor Farrell changed: What|Removed |Added Attachment #155705|Screenshot of the problem |Side by Side description|| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464899] Incorrect visuals in the log out dialog
https://bugs.kde.org/show_bug.cgi?id=464899 --- Comment #3 from Connor Farrell --- Created attachment 155706 --> https://bugs.kde.org/attachment.cgi?id=155706&action=edit Stacked -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 464429] Kirigami ScrollablePage has empty space above content when refreshing
https://bugs.kde.org/show_bug.cgi?id=464429 --- Comment #4 from Connor Carney --- It was tested enough for the breakage to be noted on the relevant merge request (https://invent.kde.org/frameworks/kirigami/-/merge_requests/732#note_528670). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478680] New: Automatic VRR and Tearing stop working once a WINE window is displayed.
https://bugs.kde.org/show_bug.cgi?id=478680 Bug ID: 478680 Summary: Automatic VRR and Tearing stop working once a WINE window is displayed. Classification: Plasma Product: kwin Version: git master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: cnr@gmail.com Target Milestone: --- SUMMARY Automatic VRR and Tearing stop working once a WINE window is displayed. STEPS TO REPRODUCE 1. Enable Automatic VRR or Tearing in systemsettings6 2. Open a Steam game (Proton) or WINE application 3. Observe immediate effects of auto VRR and Tearing failing. OBSERVED RESULT The refresh rate of both VRR compatible monitors locks to the highest possible value (70 Hz, 165 Hz) even though VRR is still enabled in systemsettings6. Non-automatic VRR is not affected by this. Tearing stops working immediately on all monitors even though Tearing is still enabled in systemsettings6. This only fixes itself once the session is reloaded. EXPECTED RESULT Both automatic VRR and Tearing continue to work as expected. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231215 / (openSuSE Tumbleweed + Krypton repos) KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.6.6-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Mesa version is 23.2.1-1699.364.pm.3 XWayland version is 23.2.2-3.1 ADDITIONAL INFORMATION KWIN_DRM_NO_AMS=1 was set in /etc/environment MESA_VK_WSI_PRESENT_MODE=immediate was set in local shell -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478680] Automatic VRR and Tearing stop working once a WINE window is displayed.
https://bugs.kde.org/show_bug.cgi?id=478680 --- Comment #2 from Connor Jenzsch --- (In reply to Zamundaaa from comment #1) > Please check if there's any weird X11 windows from Wine on your system. You > can do that in the kwin debug console, which you can open with krunner. Nope, nothing. The issue also persists after all WINE processes have closed. I should probably mention that this wasn't the case on the same system with Plasma 5. On Plasma 5 both automatic VRR and Tearing have worked flawlessly both with WINE and native software. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 452883] New: PageRow::lastItem is not updated when a page is removed
https://bugs.kde.org/show_bug.cgi?id=452883 Bug ID: 452883 Summary: PageRow::lastItem is not updated when a page is removed Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: kb...@connorcarney.com Target Milestone: Not decided Created attachment 148311 --> https://bugs.kde.org/attachment.cgi?id=148311&action=edit qml example When the last page is removed from a PageRow using pop(), the lastItem property continues to point to the now-removed page (or null, if that page gets garbage collected), instead of being updated to point to the new last page. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 452883] PageRow::lastItem is not updated when a page is removed
https://bugs.kde.org/show_bug.cgi?id=452883 --- Comment #1 from Connor Carney --- Underlying issue seems to be that ColumnView doesn't notify on contentChildren when a page is removed, so dependent QML bindings don't get re-evaluated. Submitted a pull request that fixes the issue: https://invent.kde.org/frameworks/kirigami/-/merge_requests/528 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 452986] Window decorations unconditionally become oversized when convertible is flipped
https://bugs.kde.org/show_bug.cgi?id=452986 Connor Carney changed: What|Removed |Added CC||kb...@connorcarney.com --- Comment #4 from Connor Carney --- I flip my convertible in order to use it with a bluetooth keyboard and mouse. Having the system optimize for touch is kind of annoying in that use case as well. Tablet mode does trigger the orientation sensor in the wayland session, so I wouldn't necessarily want it disabled entirely. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument
https://bugs.kde.org/show_bug.cgi?id=429408
Connor Schunk changed:
What|Removed |Added
CC||k...@peeves.pro
--- Comment #6 from Connor Schunk ---
I'm not extremely familiar with the inner workings of Qt, but encountered this
problem and decided to dig into it a bit in hopes of helping this bug get
resolved. From what I can tell from the code kde-open5 seems to use
(https://invent.kde.org/plasma/kde-cli-tools/-/blob/master/kioclient/kioclient.cpp#L235),
QURL is involved
(https://invent.kde.org/plasma/kde-cli-tools/-/blob/master/kioclient/urlinfo.h).
In QUrl (https://code.woboq.org/qt5/qtbase/src/corelib/io/qurl.cpp.html), I
notice "nameprepping" and RFCs related to normalization are mentioned a few
times, e.g.
> Note that the case folding rules in \l{RFC 3491}{Nameprep}, which QUrl
> conforms to, require host names to always be converted to lower case,
> regardless of the Qt::FormattingOptions used
If I had to guess (with my limited understanding), I would assume the problem
lies in the call to setHost, which in turn calls qt_ACE_do
(https://code.woboq.org/qt5/qtbase/src/corelib/io/qurl.cpp.html#1365) - the
normalization to lowercase probably lies somewhere in that chain.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 456280] When dragged to another VD in the grid effect, window no longer update in real-time but instead shows last frame
https://bugs.kde.org/show_bug.cgi?id=456280 Connor Carney changed: What|Removed |Added CC||kb...@connorcarney.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448567] [Wayland] Text in Overview effect for desktops list and window titles is blocky on scaled displays
https://bugs.kde.org/show_bug.cgi?id=448567 Connor Carney changed: What|Removed |Added CC||kb...@connorcarney.com --- Comment #9 from Connor Carney --- I see the same issue on the lower-DPI screen in a mixed-dpi wayland session. No fractional scaling here (100%+200%). I wrote a quick patch that fixes my specific issue with the overview effect (https://invent.kde.org/ccarney/kwin/-/commit/2de0d9562ed44f3cdd57ca6ab479a2e20736fe20). But I'm not sure that's really the right place to fix this, since there are similar texture filtering issues in QML *applications* that it doesn't fix. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457675] New: AboutItem freezes with certain font/content combinations
https://bugs.kde.org/show_bug.cgi?id=457675 Bug ID: 457675 Summary: AboutItem freezes with certain font/content combinations Product: frameworks-kirigami Version: Master Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: kb...@connorcarney.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 151192 --> https://bugs.kde.org/attachment.cgi?id=151192&action=edit qml example SUMMARY Certain font settings cause Kirigami::AboutItem (and AboutPage) to enter an infinite loop when the homepage URL is the widest thing in the form. STEPS TO REPRODUCE 1. run the attached file with qmlscene OBSERVED RESULT Test application freezes with repeated warnings: Qt Quick Layouts: Polish loop detected. Aborting after two iterations. file:///home/connor/Projects/kde/usr/lib/x86_64-linux-gnu/qml/org/kde/kirigami.2/AboutItem.qml:150:5: QML FormLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredHeight" file:///home/connor/Projects/kde/usr/lib/x86_64-linux-gnu/qml/org/kde/kirigami.2/AboutItem.qml:150:5: QML FormLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredHeight" file:///home/connor/Projects/kde/usr/lib/x86_64-linux-gnu/qml/org/kde/kirigami.2/AboutItem.qml:150:5: QML FormLayout: Binding loop detected for property "implicitHeight" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.24 KDE Frameworks Version: master Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457675] AboutItem freezes with certain font/content combinations
https://bugs.kde.org/show_bug.cgi?id=457675 Connor Carney changed: What|Removed |Added CC||kb...@connorcarney.com --- Comment #2 from Connor Carney --- This looks similar to that discover bug, but I don't think it's actually a duplicate: that one was working around binding loops with the scroll bar in AboutPage. My attached example just has a raw AboutItem in a window with no pages or scroll bars in sight. (It happens with AboutPage too, it's just not necessary to trigger the bug) In any case, it's not fixed: I tested it against a source build of master, and I can also reproduce it in the current flatpak runtime e.g. flatpak run --socket=x11 --device=dri --filesystem=home org.kde.Sdk [📦 org.kde.Sdk ~]$ qmlscene about-page-freeze.qml -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457675] AboutItem freezes with certain font/content combinations
https://bugs.kde.org/show_bug.cgi?id=457675 --- Comment #4 from Connor Carney --- Created attachment 151226 --> https://bugs.kde.org/attachment.cgi?id=151226&action=edit formlayout-freeze I dug into the AboutItem QML and it seems like all that's necessary to recreate the freeze is FormLayout+UrlButton. I've attached an even more minimal example. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457675] AboutItem freezes with certain font/content combinations
https://bugs.kde.org/show_bug.cgi?id=457675 --- Comment #6 from Connor Carney --- That QML file explicitly sets Ubuntu 10 pt on the ApplicationWindow, so it shouldn't depend on your font settings, although it does depend on having that font installed. I normally use kwin-wayland @ 100%, but it also happens in an X session. It takes some trial and error to find specific combinations of font+size+text that trigger the issue for me, but when I find one it freezes consistently. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457675] AboutItem freezes with certain font/content combinations
https://bugs.kde.org/show_bug.cgi?id=457675 Connor Carney changed: What|Removed |Added Attachment #151226|0 |1 is obsolete|| --- Comment #7 from Connor Carney --- Created attachment 151234 --> https://bugs.kde.org/attachment.cgi?id=151234&action=edit formlayout-freeze-notosans Here's a case that freezes for me with Noto Sans. It's interesting that Noto Sans is much less prone to this issue than the Ubuntu font. I could find cases for Ubuntu by just randomly typing stuff; with Noto Sans I had to actually write a script to find one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478680] Automatic VRR and Tearing stop working once a WINE window is displayed.
https://bugs.kde.org/show_bug.cgi?id=478680 Connor Jenzsch changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Connor Jenzsch --- (In reply to Connor Jenzsch from comment #2) > (In reply to Zamundaaa from comment #1) > > Please check if there's any weird X11 windows from Wine on your system. You > > can do that in the kwin debug console, which you can open with krunner. > > Nope, nothing. > > The issue also persists after all WINE processes have closed. > > I should probably mention that this wasn't the case on the same system with > Plasma 5. On Plasma 5 both automatic VRR and Tearing have worked flawlessly > both with WINE and native software. Status updated to REPORTED. Forgot to do it earlier, sorry! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478680] Automatic VRR and Tearing stop working once a WINE window is displayed.
https://bugs.kde.org/show_bug.cgi?id=478680 --- Comment #7 from Connor Jenzsch --- (In reply to Zamundaaa from comment #6) > Git commit 7f9cbbaa98c4cd633319e45e9a1100ea58f12840 by Xaver Hugl. > Committed on 09/01/2024 at 18:06. > Pushed by zamundaaa into branch 'master'. > > core/renderloop: improve frame scheduling heuristics with VRR > > Instead of checking for fullscreen windows and deciding whether or not to > schedule repaints > based on that, check if the active window is refreshing fast enough to be > reasonable for vrr. > For automatic mode, vrr is also enabled with the active window instead of > the direct scanout > candidate. > Related: bug 477199 > > M +9-6src/compositor.cpp > M +1-0src/core/output.h > M +10 -6src/core/renderloop.cpp > M +1-6src/core/renderloop.h > M +2-1src/core/renderloop_p.h > M +21 -0src/scene/surfaceitem.cpp > M +7-0src/scene/surfaceitem.h > > https://invent.kde.org/plasma/kwin/-/commit/ > 7f9cbbaa98c4cd633319e45e9a1100ea58f12840 Awesome! Will definitely check that out shortly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478680] Automatic VRR and Tearing stop working once a WINE window is displayed.
https://bugs.kde.org/show_bug.cgi?id=478680 --- Comment #8 from Connor Jenzsch --- (In reply to Zamundaaa from comment #6) > Git commit 7f9cbbaa98c4cd633319e45e9a1100ea58f12840 by Xaver Hugl. > Committed on 09/01/2024 at 18:06. > Pushed by zamundaaa into branch 'master'. > > core/renderloop: improve frame scheduling heuristics with VRR > > Instead of checking for fullscreen windows and deciding whether or not to > schedule repaints > based on that, check if the active window is refreshing fast enough to be > reasonable for vrr. > For automatic mode, vrr is also enabled with the active window instead of > the direct scanout > candidate. > Related: bug 477199 > > M +9-6src/compositor.cpp > M +1-0src/core/output.h > M +10 -6src/core/renderloop.cpp > M +1-6src/core/renderloop.h > M +2-1src/core/renderloop_p.h > M +21 -0src/scene/surfaceitem.cpp > M +7-0src/scene/surfaceitem.h > > https://invent.kde.org/plasma/kwin/-/commit/ > 7f9cbbaa98c4cd633319e45e9a1100ea58f12840 Can confirm, this fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 464429] Kirigami ScrollablePage has empty space above content when refreshing
https://bugs.kde.org/show_bug.cgi?id=464429 Connor Carney changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Connor Carney --- Fixed with merge of !1404 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 464429] New: Kirigami ScrollablePage has empty space above content when refreshing
https://bugs.kde.org/show_bug.cgi?id=464429 Bug ID: 464429 Summary: Kirigami ScrollablePage has empty space above content when refreshing Classification: Frameworks and Libraries Product: frameworks-kirigami Version: Master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: kb...@connorcarney.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 155392 --> https://bugs.kde.org/attachment.cgi?id=155392&action=edit qml to reproduce bug with qmlscene SUMMARY When ScrollablePage has refreshing: true (see attached qml), space is reserved at the top of the page for the busy indicator, but the busy indicator isn't shown leaving a blank space. GammaRay shows that the busy indicator is positioned off the top of the screen and scrolls farther off the top of the screen as the list is scrolled down. The bug in it's current state bisects at commit 497330c5 , but backing out that commit still leaves an issue where the indicator scrolls up with the content, but the reserved space doesn't. STEPS TO REPRODUCE 1. run attached qml file with qmlscene OBSERVED RESULT blank space at the top of the page EXPECTED RESULT busy indicator at the top of the page SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 w/ KDE from source KDE Plasma Version: master (5.26.80) KDE Frameworks Version: master (5.102.0) Qt Version: 5.15.6 (from Kubuntu) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 464429] Kirigami ScrollablePage has empty space above content when refreshing
https://bugs.kde.org/show_bug.cgi?id=464429 --- Comment #1 from Connor Carney --- Created attachment 155393 --> https://bugs.kde.org/attachment.cgi?id=155393&action=edit gammaray showing busy indicator positioned offscreen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416933] New: Plasmashell crashes on launching Thunderbird
https://bugs.kde.org/show_bug.cgi?id=416933 Bug ID: 416933 Summary: Plasmashell crashes on launching Thunderbird Product: plasmashell Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cam-o-...@live.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.15-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Hit the Super key to open the application browser. Searched for Thunderbird and pressed Enter to launch - Unusual behavior I noticed: While I was typing, Plasmashell had frozen and information entered was not reflected in the search bar Plasmashell froze for a few seconds and then crashed soon after hitting "Enter" Plasmashell was performing particularly badly before the crash (very slow) The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f935a62fcc0 (LWP 748))] Thread 32 (Thread 0x7f92d0ff9700 (LWP 4741)): #0 0x7f935e0fec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f935ecbecc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f935ecbeda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f9360a2c18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7f9360a2c41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7f935ecb8fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7f935e0f84cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f935e93b2d3 in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f92a700 (LWP 4618)): #0 0x7f935e92c42c in read () at /usr/lib/libc.so.6 #1 0x7f9333548732 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-13.0.so #2 0x7f93335b2f8f in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7f93335b32f1 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f93335b33b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f93335a361e in () at /usr/lib/libpulse.so.0 #6 0x7f9333521d1c in () at /usr/lib/pulseaudio/libpulsecommon-13.0.so #7 0x7f935e0f84cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f935e93b2d3 in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f92d17fa700 (LWP 4369)): #0 0x7f935e0fec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f935ecbecc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f935ecbeda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f9344071289 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f9344074d1b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f9344074d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f9344074d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f9344074d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f9344074d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f9344074d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f9344074d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f9344074d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f9344074d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f934407047e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5T
[plasmashell] [Bug 401481] New: Taskbar & Desktop disappear when adjusting volume
https://bugs.kde.org/show_bug.cgi?id=401481 Bug ID: 401481 Summary: Taskbar & Desktop disappear when adjusting volume Product: plasmashell Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: connor.meredith0...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.6) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I had recently plugged in a Logitech C920 webcam, which comes with a microphone. The microphone was not working, and someone said in their case, the microphone was muted. I clicked on the volume control in my taskbar (all of this is while the webcam is attached via USB) and then the taskbar and my desktop disappeared. However, I was still able to use ALT+F2 to use the konsole, open programs, reboot, etc. - Unusual behavior I noticed: My taskbar and desktop disappeared. When I say the taskbar disappeared, I mean it was simply no longer present. Programs appeared like they were in fullscreen. When I say the desktop disappeared, I mean that the desktop was suddenly a blank gray screen with no folders/widgets/etc. Programs (e.g., Chrome) were still functioning, however. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f75d7e55f00 (LWP 2151))] Thread 15 (Thread 0x7f74c7bff700 (LWP 9056)): #0 0x7f75d0cb79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5586c007f2c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5586c007f270, cond=0x5586c007f298) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5586c007f298, mutex=0x5586c007f270) at pthread_cond_wait.c:655 #3 0x7f75d1b3159b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f75d58b66a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f75d58b6b0a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f75d1b3016d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f75d0cb16db in start_thread (arg=0x7f74c7bff700) at pthread_create.c:463 #8 0x7f75d142b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f74ea4ee700 (LWP 9051)): #0 0x7f75d0cb79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5586bf319500) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5586bf3194b0, cond=0x5586bf3194d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5586bf3194d8, mutex=0x5586bf3194b0) at pthread_cond_wait.c:655 #3 0x7f75d1b3159b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f75d58b66a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f75d58b6b0a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f75d1b3016d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f75d0cb16db in start_thread (arg=0x7f74ea4ee700) at pthread_create.c:463 #8 0x7f75d142b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f74e93fc700 (LWP 2589)): #0 0x7f75d0cb79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5586befa0ec4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5586befa0e70, cond=0x5586befa0e98) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5586befa0e98, mutex=0x5586befa0e70) at pthread_cond_wait.c:655 #3 0x7f75d1b3159b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f75d58b66a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f75d58b6b0a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f75d1b3016d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f75d0cb16db in start_thread (arg=0x7f74e93fc700) at pthread_create.c:463 #8 0x7f75d142b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f74e9ced700 (LWP 2564)): #0 0x7f75d0cb79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5586bef5c194) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5586bef5c140, cond=0x5586bef5c168) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5586bef5c168, mutex=0x5586bef5c140) at p
[systemsettings] [Bug 464868] Create UI to generate and use a custom Libinput acceleration profile
https://bugs.kde.org/show_bug.cgi?id=464868 Connor Speers changed: What|Removed |Added CC||k...@speers.dev -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 376026] New: Block selection does not respect trim trailing spaces profile option
https://bugs.kde.org/show_bug.cgi?id=376026 Bug ID: 376026 Summary: Block selection does not respect trim trailing spaces profile option Product: konsole Version: 16.12.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: kevina...@gmail.com Target Milestone: --- "Block selection" means: Ctrl+Alt+LeftMouseButton "Trim trailing spaces profile option" means: Settings -> Edit Current Profile.. -> Mouse (tab) -> Trim trailing spaces -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 495854] Missing Digit Grouping for Decimals
https://bugs.kde.org/show_bug.cgi?id=495854 --- Comment #3 from Kevin Connor Arpe --- (In reply to Gabriel Barrantes from comment #1) > they default to 3 digits, would make sense to have it configurable? I uploaded another screenshot to show that my decimal numbers are not grouped by 3 digits. Am I doing something wrong? Also, my version of KCalc is Version 24.12.0. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 495854] Missing Digit Grouping for Decimals
https://bugs.kde.org/show_bug.cgi?id=495854 Kevin Connor Arpe changed: What|Removed |Added CC||kevina...@gmail.com --- Comment #2 from Kevin Connor Arpe --- Created attachment 179963 --> https://bugs.kde.org/attachment.cgi?id=179963&action=edit Screenshot that shows decimal numbers are not grouped by 3 digits -- You are receiving this mail because: You are watching all bug changes.
