[digikam] [Bug 372041] New: "Add Folders" attempts to import parent directory AND target dir.
https://bugs.kde.org/show_bug.cgi?id=372041 Bug ID: 372041 Summary: "Add Folders" attempts to import parent directory AND target dir. Product: digikam Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: watershe...@gmail.com Target Milestone: --- Created attachment 102017 --> https://bugs.kde.org/attachment.cgi?id=102017&action=edit Import dialog screenshot I am working on a prototype install of digiKam on Windows to show to my company. My album collection is located in a folder on the Desktop. I placed another folder of images on the Desktop and opened DK's "Add Folders" tool under the Import menu. I navigated to the folder I wanted imported, but DK by default also selected the parent (in this case C:\Users\library\Desktop). As seen in the attachment, the Directory field says '"Desktop" "target folder"', indicating that both will be imported. In addition, if I click other folders also on the Desktop, DK selects them all, instead of just the most recent click. If I want to deselect some I can ctrl-click them, but there's no way to deselect "Desktop" unless I navigate into a subfolder and then back out. Then, when I click my target folder, it is the only one that is selected. Importing both caused a full system crash, because Desktop contains the target folder, and both are being copied into a folder that also lives on the desktop. DigiKam started trying to copy my archive into the new subfolder within the archive, over and over, creating recursive subdirectories. I did a hard reboot and used robocopy (http://superuser.com/a/1048242) to delete the new subdirectory. Now I know how to avoid this problem, but it could easily happen to others. I have a feeling the problem may be specific to the Windows version of DK. Thanks for your work on digiKam! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450674] It's too easy to accidentally delete virtual desktops
https://bugs.kde.org/show_bug.cgi?id=450674 Brian changed: What|Removed |Added CC||aeon.descrip...@gmail.com --- Comment #8 from Brian --- Came here for this -- it would be nice to have an option to disable creation/deletion of virtual desktops altogether. I have a known and liked virtual desktop configuration that I don't want altered. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450676] Changing desktops from desktop bar should play desktop switching animation after closing Overview
https://bugs.kde.org/show_bug.cgi?id=450676 Brian changed: What|Removed |Added CC||aeon.descrip...@gmail.com --- Comment #4 from Brian --- I've also found this jarring. I think it's important for visual consistency to use the animation that is normally used for switching desktops. This matters even more when mixing a desktop arrangement that is spatially presented during switching -- as with sliding desktops when arranged as a grid. ..and once someone does Desktop Cube in the new framework, it'll be helpful there, too. But consistency matters a lot, and having a consistent animation makes the association on a visceral level that 'desktop switching' is happening, and happening normally. The animations can both be done, and there are a number of reasonable ways to do that -- playing both chained together as an InOutCubic (if that's possible) would make sense. But also, if mixing is possible, that could be done -- the windows return to their normal positions as that desktop slides away. Even playing one right after the other (as an option) would be ok. In any case, I suppose you could consider this another vote in favor of addressing this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 Brian changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||bcej...@gmail.com --- Comment #25 from Brian --- >From the comments above, the root cause of the issue is in the KDE Connect Android app which bundles an obsolete version of a library, sshd-core 0.14.0, which in turn offers only one insecure signature algorithm -- "ssh-rsa". Many desktop environments depend on OpenSSH, which has (2 years ago) since dropped default support for "ssh-rsa" -- thus, desktop apps (like KDEConnect-Desktop and GSConnect) will fail to establish SSH/SFTP sessions with KDE Connect Android. The current workaround has been to quietly enable the use of "ssh-rsa" in the KDE Connect Desktop app: https://invent.kde.org/network/kdeconnect-kde/commit/204207f2e66e87e7696ff1c98d70ce41b3e2d396 But this is problematic: * It obviously enables a known insecure algorithm, as mentioned earlier. Personally, I don't consider this a huge deal, given the tradeoff is to greatly increase user-coverage, for the meantime till ssh-rsa recedes into history. The real problem is ... * There seem to be a few separate desktop apps which implement the KDEConnect protocol, whereas there is only one KDEConnect Android app of note. **Not all desktop apps will have the same easy control over SSH config as KDEConnect Desktop**, thus they cannot enable "ssh-rsa" at will -- GSConnect, for instance. So this issue should ideally be fixed in KDEConnect Android, not just because it is the source of the issue, but also because the alternative workaround is not feasibly implementable in all desktop apps. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #26 from Brian --- Following that -- Why does KDEConnect Android still bundle an obsolete sshd-core (0.14.0)? The reason given so far has been backward-compatibility with older Android versions, specifically Android 7 and below. This is a relevant commit that gives a bit of detail -- https://invent.kde.org/network/kdeconnect-android/-/commit/ef3fd68f7378398273cb476581bc4f28c6b89515 However, I think this decision should be re-evaluated: * Android 7 was first released 7 years ago, and its final update was in 2019. What is the source of the requirement to support Android <=7? Is this really still required, especially to the detriment of security? * If it is, then is there a way to achieve that backward compatibility, without sacrificing security or usability with newer phones/desktops? For instance, a comment in the above commit says (in the removed lines) that newer versions of sshd-core require the NIO package, which is only available in Android 8+. It sounds like this is the main reason KDE-Connect Android isn't using newer sshd-core. However, that commit also says (in the newly added lines), that adding mina-core somehow makes sshd-core work **without requiring NIO** any longer. So far, this combination seems to have been tested with only sshd-core 0.14.0 -- but perhaps this workaround should also work for newer sshd-core as well, latest being 2.9.2. https://mvnrepository.com/artifact/org.apache.sshd/sshd-core/2.9.2. If that is the case, then it should now be possible to upgrade the sshd-core for all Android, once and for all. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 454693] Okular throws error when saving to mounted Samba share
https://bugs.kde.org/show_bug.cgi?id=454693
Brian changed:
What|Removed |Added
CC||fowl...@gmail.com
--- Comment #13 from Brian ---
When opening Okular from terminal I get a...
Couldn't rename "filename.pdf.part" to "filename.pdf" ( Permission denied )
The document hasn't been reloaded/swapped correctly
Context:
brian@Gig2Deb12:/media/test$ okular Okular-test.pdf
QSocketNotifier: Can only be used with threads started with QThread
kf.kio.widgets: Failed to check which JobView API is supported "The name
org.kde.kuiserver was not provided by any .service files"
kf.kio.workers.file: copy() QUrl("file:///tmp/okular.WxqvUE") to
QUrl("file:///media/test/Okular-test.pdf") mode= -1
kf.kio.workers.file: the file doesn't have any xattr
kf.kio.workers.file: Couldn't rename "/media/test/Okular-test.pdf.part" to
"/media/test/Okular-test.pdf" ( Permission denied )
The document hasn't been reloaded/swapped correctly
brian@Gig2Deb12:/media/test$
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 459072] New: When launching KDEnlive from the latest app image, the screen font of the user interface is jagged (no antialiasing)
https://bugs.kde.org/show_bug.cgi?id=459072 Bug ID: 459072 Summary: When launching KDEnlive from the latest app image, the screen font of the user interface is jagged (no antialiasing) Product: kdenlive Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: btspamdu...@gmail.com Target Milestone: --- Created attachment 152036 --> https://bugs.kde.org/attachment.cgi?id=152036&action=edit Screenshot of display Launching from the latest app image, the user interface fonts are jagged / not antialised ... see attached screen shot -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405335] KDevelop crashes when reopening a project
https://bugs.kde.org/show_bug.cgi?id=405335 brian changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #2 from brian --- Yes, I was able to reproduce it in 'Version 5.9.220800 (22.08.0)' Looks like this is also bug 422241 and bug 335412 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405335] KDevelop crashes when reopening a project
https://bugs.kde.org/show_bug.cgi?id=405335
--- Comment #3 from brian ---
This is what the crash looks like when running from a terminal:
~ $ kdevelop
kdevplatform.shell: Could not load plugin "kdevperforce" , it reported the
error: "The variable P4CONFIG is not set. Is perforce installed on the system?"
Disabling the plugin now.
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
/bin/cat:
/home/brian/.local/share/kdevelop/sessions/{46199e2d-b3a6-4556-baa3-294f6e633a4f}/default.sh:
No such file or directory
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4181, resource
id: 23069278, major code: 40 (TranslateCoords), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4368, resource
id: 23069283, major code: 40 (TranslateCoords), minor code: 0
kf.kio.slaves.file: copy()
QUrl("file:///home/brian/projects/median/median.kdev4") to
QUrl("file:///tmp/kdevelop.SktrYI") mode= -1
kf.kio.slaves.file: the file doesn't have any xattr
kf.kio.widgets.kdirmodel: No node found for item that was just removed:
QUrl("file:///home/brian/projects/qtqml.qml")
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6431, resource
id: 23069289, major code: 40 (TranslateCoords), minor code: 0
[[[[ crash happens here: ]]
kf.kio.slaves.file: copy()
QUrl("file:///home/brian/projects/median/median.kdev4") to
QUrl("file:///tmp/kdevelop.upNPEg") mode= -1
kf.kio.slaves.file: the file doesn't have any xattr
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kdevelop path = /usr/bin pid = 8674
KCrash: Arguments: /usr/bin/kdevelop
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 69 and type 'Read', disabling...
[1]+ Stopped kdevelop
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 --- Comment #63 from Brian --- This specific issue is about #1. The other issues were brought up here due to their close similarity, but this is really about issue 1. Sorting by krunner type is most simply done by a reorderable list, as it was in KDE a while back. If more complexity is desired, a list with weights on the right hand side. But the first is all that was originally asked for. This issue stalled on addendums. On Tue, Apr 18, 2023, 3:46 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=340283 > > --- Comment #62 from stephan.leinewe...@t-online.de --- > (In reply to Peter Hoeg from comment #61) > > I'm not sure what the best way is to move this forward is - and if we > > possibly should be splitting this into multiple tickets since there are > > multiple issues (although obviously related). > > > > 1. the ordering of groups > >a. statically, or > >b. with weights > > 2. the ordering of items within groups > >a. statically, or > >b. with weights > > 3. issues with the "smarts" where the automatic ordering doesn't seem to > > actually take use frequency into consideration > > > > What's the best way forward from here? > > Sorry guys, I've forgotten to tell here. Issue 3 doesn't exist anymore > since, > at least for me. Since an update the ordering of the mail client is as > expected. Thanks for refining the order of the results! Don't know about > issue > 1 and 2, since those were asked by other persons... > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #29 from Brian --- No, as far as I can tell, the situation is still unchanged -- sshd-core is still stuck at the obsolete version 0.14.0, carrying only "ssh-rsa" support: https://invent.kde.org/network/kdeconnect-android/-/blob/master/build.gradle. Any desktop apps that don't/can't enable support for this algorithm, will fail to establish SFTP/mount sessions with the Android app. As mentioned earlier, we need to get the sshd-core version bumped up to the most recent as possible (likely 2.9.2 or greater) and confirm that it resolves this standing issue of SSH negotiation, while retaining support for Android <= 7 if relevant and possible. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #31 from Brian --- SSH-RSA was enabled here in the KDE-Connect desktop app, as a work-around for this issue: https://invent.kde.org/network/kdeconnect-kde/-/commit/204207f2e66e87e7696ff1c98d70ce41b3e2d396 I'm using GSConnect on GNOME, which lacks the APIs to make similar changes, and so is presently unable to SFTP with the Android app. There are other such desktop apps that support the KDE Connect protocol, as mentioned here: https://userbase.kde.org/KDEConnect The security aspect is also a concern, even if a lesser one. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464992] New: I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7
https://bugs.kde.org/show_bug.cgi?id=464992 Bug ID: 464992 Summary: I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7 Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fla...@pm.me 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. Run Zoom. Test mic. No sound. 2. Run Cheese; record video; No Sound 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.5... KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464992] I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7
https://bugs.kde.org/show_bug.cgi?id=464992 --- Comment #2 from Brian --- Many thanks for getting back to me. Any idea how I report it to Feren OS? My apologies for this: I thought my report to you was in fact going to Feren. Brain On 06/02/2023 18:12, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=464992 > > Nate Graham changed: > > What|Removed |Added > > Status|REPORTED|RESOLVED > CC||n...@kde.org > Resolution|--- |DOWNSTREAM > > --- Comment #1 from Nate Graham --- > This would be something to report to your distro, not KDE. Our code wouldn't > be > able to cause this. Can you report it to Feren OS? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464992] I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7
https://bugs.kde.org/show_bug.cgi?id=464992 --- Comment #4 from Brian --- Thanks, Nate, Brian On 06/02/2023 18:34, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=464992 > > --- Comment #3 from Nate Graham --- > There's a help button at https://ferenos.weebly.com/ that looks helpful. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464992] I am using Feren OS 2023,01. I can't get Zoom or Cheese to recognise my mic. It works in Linux Mint 21. I am using HP Pro Book 430 G7
https://bugs.kde.org/show_bug.cgi?id=464992 --- Comment #5 from Brian --- Many thanks for getting back to me. Any idea how I report it to Feren OS? My apologies for this: I thought my report to you was in fact going to Feren. Brain On 06/02/2023 18:12, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=464992 > > Nate Graham changed: > > What|Removed |Added > > Status|REPORTED|RESOLVED > CC||n...@kde.org > Resolution|--- |DOWNSTREAM > > --- Comment #1 from Nate Graham --- > This would be something to report to your distro, not KDE. Our code wouldn't > be > able to cause this. Can you report it to Feren OS? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0
https://bugs.kde.org/show_bug.cgi?id=481993 Brian changed: What|Removed |Added CC||br...@rachal.us --- Comment #10 from Brian --- I also have the same issue where the 'Discover Notifier' runs, stating I have updates without 'Discover' operating. Without 'Discover' functioning properly, it looks as though no updates are capable of easily being installed. Therefore, besides 'pkcon' and 'Discover', a third method for determining/obtaining necessary updates, such as a web-based solution that is not dependent on 'Discover', may need to be considered - if not already available -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 487999] New: Manual Inout of Region Points causes lockup and crash
https://bugs.kde.org/show_bug.cgi?id=487999 Bug ID: 487999 Summary: Manual Inout of Region Points causes lockup and crash Classification: Applications Product: kstars Version: 3.7.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bvin...@icloud.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Using Artificial Horizon - create new region 2. add ALT/AZ points 3. Apply OBSERVED RESULT spinning wheel - resulting in crash for Force Quit EXPECTED RESULT Artificial Horizon created SOFTWARE/OS VERSIONS macOS: 14.5 M2 Max chip ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 487999] Manual Inout of Region Points causes lockup and crash
https://bugs.kde.org/show_bug.cgi?id=487999 Brian changed: What|Removed |Added CC||bvin...@icloud.com --- Comment #1 from Brian --- Created attachment 170123 --> https://bugs.kde.org/attachment.cgi?id=170123&action=edit Kstars Crash Backtrace -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 487999] Manual Inout of Region Points causes lockup and crash
https://bugs.kde.org/show_bug.cgi?id=487999 --- Comment #2 from Brian --- Inout (in the title) should be Input -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 488091] New: HiPS overlay cause bitmapping , stuttering and general unsuitability
https://bugs.kde.org/show_bug.cgi?id=488091 Bug ID: 488091 Summary: HiPS overlay cause bitmapping , stuttering and general unsuitability Classification: Applications Product: kstars Version: 3.7.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bvin...@icloud.com Target Milestone: --- Created attachment 170180 --> https://bugs.kde.org/attachment.cgi?id=170180&action=edit Scrambling of HiPS DSS *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Enable HiPS DSS 2. 3. OBSERVED RESULT Scrambled graphics , globe wide, EXPECTED RESULT SOFTWARE/OS VERSIONS macOS: 14.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 488091] HiPS overlay cause bitmapping , stuttering and general unsuitability
https://bugs.kde.org/show_bug.cgi?id=488091 --- Comment #1 from Brian --- Created attachment 170181 --> https://bugs.kde.org/attachment.cgi?id=170181&action=edit No actual DSS images, this is Orion Along with scrambling, no images appear. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 488091] HiPS overlay cause bitmapping , stuttering and general unsuitability
https://bugs.kde.org/show_bug.cgi?id=488091 --- Comment #2 from Brian --- Created attachment 170182 --> https://bugs.kde.org/attachment.cgi?id=170182&action=edit Terrain rendering The terrain is often in motion as the user zooms in and out or moves around the globe. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 488091] HiPS overlay cause bitmapping , stuttering and general unsuitability
https://bugs.kde.org/show_bug.cgi?id=488091 Brian changed: What|Removed |Added CC||bvin...@icloud.com --- Comment #3 from Brian --- Created attachment 170183 --> https://bugs.kde.org/attachment.cgi?id=170183&action=edit Globe totally scrambled This is typical rendering. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 488091] HiPS overlay cause bitmapping , scramble, stuttering and general unusability
https://bugs.kde.org/show_bug.cgi?id=488091 Brian changed: What|Removed |Added Summary|HiPS overlay cause |HiPS overlay cause |bitmapping , stuttering and |bitmapping , scramble, |general unsuitability |stuttering and general ||unusability -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452935] I18N_ARGUMENT_MISSING in CSV import Columns screen
https://bugs.kde.org/show_bug.cgi?id=452935 Brian changed: What|Removed |Added CC||macph...@btinternet.com --- Comment #8 from Brian --- I am seeing this error on Package: kmymoney Version: 5.1.2-4 Priority: optional Section: universe/kde Origin: Ubuntu Very similar scenario re CSV import -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 455761] New: Failed loading page on a specific page, always
https://bugs.kde.org/show_bug.cgi?id=455761 Bug ID: 455761 Summary: Failed loading page on a specific page, always Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: aeon.descrip...@gmail.com Target Milestone: --- Title says it. STEPS TO REPRODUCE 1. go to https://www.home-assistant.io/blog/2021/07/07/release-20217/ 2. 3. OBSERVED RESULT " Failed loading page Something went wrong while loading this page. Try reloading the page or closing some tabs to make more memory available. " EXPECTED RESULT page loads SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04, Linux 5.15.0-39-generic (64-bit) Falkon Application version: 3.2.0 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION QtWebEngine version 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455770] New: Arranging icons by rows places the icons in columns.
https://bugs.kde.org/show_bug.cgi?id=455770 Bug ID: 455770 Summary: Arranging icons by rows places the icons in columns. Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: brian.ur...@outlook.com Target Milestone: --- Created attachment 150033 --> https://bugs.kde.org/attachment.cgi?id=150033&action=edit Screen capture of the selected options, and the icorrectly arranged icons. 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. Right Click on desktop > Arrange In > Rows/Columns OBSERVED RESULT Icons are placed in the wrong order. If Arrange In rows is chosen, the icons are placed column-wise. If arrange in Columns is chosen, the icons are placed row-wise EXPECTED RESULT Icons are arranged in the order the label indicates. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.5-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455770] Arranging icons by rows places the icons in columns.
https://bugs.kde.org/show_bug.cgi?id=455770 Brian changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455770] Arranging icons by rows places the icons in columns instead
https://bugs.kde.org/show_bug.cgi?id=455770 Brian changed: What|Removed |Added Summary|Arranging icons by rows |Arranging icons by rows |places the icons in |places the icons in columns |columns.|instead -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455770] Arranging icons by rows places the icons in columns instead
https://bugs.kde.org/show_bug.cgi?id=455770 --- Comment #2 from Brian --- (In reply to Nate Graham from comment #1) > Your screenshot shows a column of icons and the "arrange in columns" option > selected. Looks to me like everything is working properly. Can yo clarify > what the problem is, exactly? The icons in the picture are arranged row-wise. Rows go along the y-axis, columns along the x-axis. My problem is that the labels are backwards. When "arrange in columns" is selected I would expect to see a line of icons going along the x-axis, instead of the y-axis like it is on the screenshot. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456728] New: Lattedock
https://bugs.kde.org/show_bug.cgi?id=456728
Bug ID: 456728
Summary: Lattedock
Product: lattedock
Version: 0.10.8
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: aeon.descrip...@gmail.com
Target Milestone: ---
When application previews are enabled (whether or not 'preview window behaves
as a popup' is checked), I have no images in the previews.
I don't know if this is a system configuration problem, or if this is a latte
issue.
STEPS TO REPRODUCE
1. Enable window previews on tasks mouse hover
2. Hover over a task icon so that the preview appears
3.
OBSERVED RESULT
Preview images are present, but blank.
EXPECTED RESULT
Preview images aren't blank.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-41-generic (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Vega 3 Graphics
ADDITIONAL INFORMATION
On hover for Dolphin with one window open, `latte-dock --debug` gives:
[Warning : 15:10:49.889889] - "\"0 instead of 1 arguments to message {On %1}
supplied before conversion.\""
[Warning : 15:10:49.889889] - "\"0 instead of 1 arguments to message {On %1}
supplied before conversion.\""
[Warning : 15:10:49.8989] - "Couldn't create KWindowShadow for
Latte::Quick::Dialog_QML_302(0x556bb0985980)"
[Warning : 15:10:49.8989] - "Couldn't create KWindowShadow for
Latte::Quick::Dialog_QML_302(0x556bb0985980)"
[Warning : 15:10:49.8989] - "Couldn't create KWindowShadow for
Latte::Quick::Dialog_QML_302(0x556bb0985980)"
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 456728] Lattedock
https://bugs.kde.org/show_bug.cgi?id=456728 --- Comment #2 from Brian --- (In reply to Michail Vourlakos from comment #1) > use latte git version Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 Brian changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|NEEDSINFO --- Comment #27 from Brian --- https://bugzilla.mozilla.org/show_bug.cgi?id=1631061 Seems to have been fixed now? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] Wayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 Brian changed: What|Removed |Added Status|RESOLVED|REOPENED Summary|XWayland application focus |Wayland application focus |extremely inconsistent |extremely inconsistent Resolution|WORKSFORME |--- --- Comment #48 from Brian --- Appears this bug has not gone away, or if it did, it's back. I've tested Void Linux, Arch Linux, Kubuntu, Neon, Arch with 5.20 beta from kde-unstable, and KDE Neon git unstable with 5.20... All of which have the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438700] New: No menu bar in kmymoney
https://bugs.kde.org/show_bug.cgi?id=438700 Bug ID: 438700 Summary: No menu bar in kmymoney Product: kmymoney Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: br...@g2growth.com Target Milestone: --- Created attachment 139356 --> https://bugs.kde.org/attachment.cgi?id=139356&action=edit Screenshot of the missing menus SUMMARY When switching to the Global Menu bar, and then back to the in-app menu, the file menu in KMyMoney disappears and can't be made to come back. Only switching to the global menu brings back the file menu. STEPS TO REPRODUCE 1. Enable Global Menu 2. Disable Global Menu (switch back to the in-app menu) OBSERVED RESULT File, Settings, Edit, etc. menus are all hidden and can't be shown through a key combo or any other way. The only way to get access to these menus is to re-enable the global menu bar. 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.
[kmymoney] [Bug 438700] No menu bar in kmymoney
https://bugs.kde.org/show_bug.cgi?id=438700 Brian changed: What|Removed |Added CC||br...@g2growth.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438700] No menu bar in kmymoney
https://bugs.kde.org/show_bug.cgi?id=438700 Brian changed: What|Removed |Added CC|br...@g2growth.com | -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438700] No menu bar in kmymoney
https://bugs.kde.org/show_bug.cgi?id=438700 --- Comment #2 from Brian --- (In reply to Thomas Baumgart from comment #1) > Does the solution provided in > https://forum.kde.org/viewtopic.php?f=17&t=167547#p440768 help here? And > it's not only the file menu but the menubar that is hidden. Yes, this did help. I was also able to resolve the issue by deleting the kmymoney directory in ~/.config/. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438700] No menu bar in kmymoney
https://bugs.kde.org/show_bug.cgi?id=438700 Brian changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438700] No menu bar in kmymoney
https://bugs.kde.org/show_bug.cgi?id=438700 Brian changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 436058] New: Muon isn't prompting for su password and won't install packages
https://bugs.kde.org/show_bug.cgi?id=436058 Bug ID: 436058 Summary: Muon isn't prompting for su password and won't install packages Product: muon Version: 5.8.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: muon Assignee: unassigned-b...@kde.org Reporter: r3cl...@r3cluse.net CC: echidna...@kubuntu.org, silh...@gmail.com Target Milestone: --- SUMMARY I'm sure this is something simple and I'm completely oblivious to the right way. When I used to open muon it would prompt me for the su password. I tried yesterday to install flatpak and when I click on "mark for installation" the "apply changes" button remains greyed out. I've tried running muon from the command prompt using sudo but it still won't allow me to install packages. The "undo" button lights up so I know it's registering something. I've removed the application, rebooted, and then re-added it with no success. 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: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417939] Task context menu disappears when Task's tooltip disappears
https://bugs.kde.org/show_bug.cgi?id=417939 --- Comment #21 from Brian --- (In reply to Vlad Zahorodnii from comment #20) > https://invent.kde.org/qt/qt/qtwayland/-/blob/ > 00b9c558886945bd9b37671732d14e3982fe3da5/src/client/qwaylandwindow.cpp#L459 > > It looks like QtWaylandClient is at fault! Do you think you could try fixing it? This bug is basically a showstopper for Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] Wayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #52 from Brian --- (In reply to Kyle Tirak from comment #51) > (In reply to Brian from comment #41) > > (In reply to Roman Gilg from comment #39) > > > I'm not able to reproduce it. Is there a way to reproduce it > > > consistently? I > > > tried method in comment 13, but didn't fail for me. > > > > Been doing testing and i think what might be happening is the window below > > is randomly getting input such as mouse clicks (the desktop?), leading to > > kwin mistakenly thinking you clicked something else, and therefor stopping > > you from inputing text. Meanwhile kwin renders the last thing the window was > > showing, leading to the still content seen. > > > > This surface glitching seems to happen most often with Firefox in Xwayland. > > In my experience when it happens, dialogs will open but not show, but if you > > use kwin's present window hotcorner you can see that it did infact open and > > that it's artifacted and invisble. > > > > Interestingly i just had the surface glitching happen randomly when > > downloading a file. The dialog opened, but it was artifacted and almost > > fully invisible, yet i could still click on it's titlebar. > > > > As a matter of fact, i know extremely similar behavior to this can be > > reproduced easily if you open Firefox with it's Wayland backend enabled. You > > will not only see tons of artfacting and misplaced UI elements should you > > move it or interact with it, but you will also find that some of your clicks > > are not registered and that windows below it are clipped up through it, > > giving you a mangled mess. > > This sounds similar to the issue I've seen for a long time. The easiest way > to reproduce this behavior for me is to: > > 1. Open one XWayland application (e.g. Thunderbird) and minimize it > 2. Open another XWayland application (e.g. VLC) > 3. In the second XWayland application, hammer on a menu bar option (e.g. in > VLC you could continuously click on the Help menu to activate and deactivate > the menu). You should be able to see invisible activations of the menu. > > This only happens for me when I have an XWayland window minimized. It also > seems to stop happening with "Keep Window Thumbnails" set to "Always". > > Note that if needing to turn off the "Always" setting to reproduce this, the > minimized XWayland window needs to be minimized *after* changing the setting > off of "Always". I have suspicion it's not just XWayland applications affected. But yes, the main problem is XWayland ones. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428680] kwin crashes after opening krita
https://bugs.kde.org/show_bug.cgi?id=428680 Brian changed: What|Removed |Added CC||brianabe...@gmail.com --- Comment #12 from Brian --- (In reply to Vlad Zahorodnii from comment #9) > Git commit d91da41cef17e34841ad307041fc00f76c105ba6 by Vlad Zahorodnii. > Committed on 04/11/2020 at 13:35. > Pushed by vladz into branch 'master'. > > wayland: Fix binding of xwayland surfaces to windows > > Surface ids are not unique across clients. If the underlying surface of > an XdgToplevelClient is replaced with an Xwayland's surface, you may see > weird results such as a desktop window having the contents of an X11 > window or even worse a crash. > > M +18 -5wayland_server.cpp > > https://invent.kde.org/plasma/kwin/commit/ > d91da41cef17e34841ad307041fc00f76c105ba6 I'm curious if this could have been the cause of 400987 ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] Wayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #54 from Brian --- (In reply to Vlad Zahorodnii from comment #53) > I have never seen this bug. Do you know a way to reproduce it? The main way to reproduce it is to restore and minimize a XWayland window such as spotify, discord, or Firefox XWayland a couple times... You'll notice it will stop accepting input, and if you try to resize the window while the focus is out of whack, the border resizes but the content does not, as it's no longer updated. The bug is very random, and i recall it happening as far back as 5.12 Sadly because of how random it is you can go a while before even encountering it, and some developers here said they couldn't replicate the bug i assume due to that. That's actually why i marked this as solved for a while, thinking it was resolved, when in reality i was just lucky to not encounter it for a while. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 428983] New: Fail to compile
https://bugs.kde.org/show_bug.cgi?id=428983
Bug ID: 428983
Summary: Fail to compile
Product: kate
Version: Git
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: application
Assignee: kwrite-bugs-n...@kde.org
Reporter: brian.o...@gmail.com
Target Milestone: ---
Fails to compile on debian buster, with default packages, cmake passes, but
fails at make.
STEPS TO REPRODUCE
1. cmake ../ -DCMAKE_BUILD_TYPE=RelWithDebInfo
-DCMAKE_INSTALL_PREFIX=~/Apps/Kate/
2. make
OBSERVED RESULT
[ 0%] Automatic MOC for target katebacktracebrowserplugin
[ 0%] Built target katebacktracebrowserplugin_autogen
Scanning dependencies of target katebacktracebrowserplugin
[ 0%] Building CXX object
addons/backtracebrowser/CMakeFiles/katebacktracebrowserplugin.dir/katebacktracebrowser.cpp.o
In file included from
/home/brian/Git-Repos/kate/addons/backtracebrowser/katebacktracebrowser.cpp:13:
In file included from /usr/include/KF5/KConfigCore/KConfigGroup:1:
/usr/include/KF5/KConfigCore/kconfiggroup.h:734:16: error: expected expression
Q_FOREACH (const T &value, defaultValue) {
^
/usr/include/KF5/KConfigCore/kconfiggroup.h:739:16: error: expected expression
Q_FOREACH (const QVariant &value, readEntry(key, data)) {
^
/usr/include/KF5/KConfigCore/kconfiggroup.h:760:16: error: expected expression
Q_FOREACH (const T &value, list) {
^
3 errors generated.
make[2]: ***
[addons/backtracebrowser/CMakeFiles/katebacktracebrowserplugin.dir/build.make:71:
addons/backtracebrowser/CMakeFiles/katebacktracebrowserplugin.dir/katebacktracebrowser.cpp.o]
Error 1
make[1]: *** [CMakeFiles/Makefile2:901:
addons/backtracebrowser/CMakeFiles/katebacktracebrowserplugin.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
EXPECTED RESULT
Complete to 100%
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Buster
(available in About System)
KDE Plasma Version: 5.54
KDE Frameworks Version: None
Qt Version: 5.11
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 428983] Fail to compile
https://bugs.kde.org/show_bug.cgi?id=428983 --- Comment #1 from Brian --- I mean framework version is 5.54. Plasma is the one not installed. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 428983] Fail to compile
https://bugs.kde.org/show_bug.cgi?id=428983 --- Comment #5 from Brian --- Okay, done as sudgested, removed the line from CMakeLists.txt about add_definitions(-DQT_NO_FOREACH) But, now there is a new problem: [ 0%] Automatic MOC for target katebacktracebrowserplugin [ 0%] Built target katebacktracebrowserplugin_autogen [ 3%] Built target katebacktracebrowserplugin [ 3%] Automatic MOC for target btbrowser_test [ 3%] Built target btbrowser_test_autogen [ 4%] Built target btbrowser_test [ 4%] Automatic MOC for target katecloseexceptplugin [ 4%] Built target katecloseexceptplugin_autogen [ 6%] Built target katecloseexceptplugin [ 6%] Automatic MOC for target katefilebrowserplugin [ 7%] Built target katefilebrowserplugin_autogen Scanning dependencies of target katefilebrowserplugin [ 7%] Building CXX object addons/filebrowser/CMakeFiles/katefilebrowserplugin.dir/katefilebrowser.cpp.o /home/brian/Git-Repos/kate/addons/filebrowser/katefilebrowser.cpp:46:10: fatal error: 'KApplicationTrader' file not found #include ^~~~ 1 error generated. make[2]: *** [addons/filebrowser/CMakeFiles/katefilebrowserplugin.dir/build.make:89: addons/filebrowser/CMakeFiles/katefilebrowserplugin.dir/katefilebrowser.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:1183: addons/filebrowser/CMakeFiles/katefilebrowserplugin.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 It appears the file KApplicationTrader or kapplicationtrader.h isn't part of KDE 5.54, as on doing search it is supposed to be shipped with the libkf5service-dev in debian, but Debian Buster doesn't ship with it, appears to be only in newer versions, I don't really know starting from which version of KDE was this added. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 Brian changed: What|Removed |Added Summary|Wayland application focus |XWayland application focus |extremely inconsistent |extremely inconsistent -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #55 from Brian --- I was testing the latest Plasma from Git, and the bug is still there. I can now say for certain however that the bug only affects XWayland applications, as I've done extensive testing to see if it happens with normal Wayland apps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450674] It's too easy to accidentally delete virtual desktops
https://bugs.kde.org/show_bug.cgi?id=450674 --- Comment #11 from Brian --- What about a gear icon that takes you to the settings to add/delete virtual desktops? Deleting the label is pretty unintuitive. In any case, still strongly agree that the trash icon is rough. On Tue, Dec 26, 2023 at 8:49 PM Denilson F. de Sá wrote: > https://bugs.kde.org/show_bug.cgi?id=450674 > > Denilson F. de Sá changed: > >What|Removed |Added > > > CC||denilso...@gmail.com > > --- Comment #10 from Denilson F. de Sá --- > Created attachment 164460 > --> https://bugs.kde.org/attachment.cgi?id=164460&action=edit > Screenshot of the "Trash" button when the user has vertical screens > > The "trash" button is surprising. The UI shows "look at this rectangle, > you can > click on me!". Then when the user clicks on it, "Surprise! There was an > invisible button that showed up as you moved the mouse cursor, and now your > virtual desktop is gone!". Hidden buttons are just bad UX. > > This effect is even worse if the user has a 16:9 vertical screen. (i.e. If > the > monitor is rotated 90°.) Take a look at the attached screenshot, the > invisible > button takes up about 40% of the area. That's a very large danger zone. So > large that I'm always scared to click on it. > > It is so annoying that this person came up with his own "solution" (that > gets > overwritten on each update): > https://romangeber.com/blog/tech/kde-plasma-desktop-delete-button-fix > > ——— > > As alternatives, I would suggest having a drag-and-drop feature, so that > we can > easily reorder the virtual desktops, and so that dragging to a trash area > would > delete the virtual desktop. (And dragging from the "plus" area would > create a > new virtual desktop.) > > I can understand implementing drag-and-drop can be complicated, so I'm > proposing an alternative behavior that is easier to implement: If the user > deletes the label (i.e. clicks on the label and deletes the text), then the > virtual desktop is deleted. In other words, an empty label would trigger a > deletion. This sounds intuitive-ish, as the user is already deleting > something; > while also being very hard to trigger by accident. > > Whatever the solution, please get rid of that trash button. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #46 from Brian --- We can probably disregard tests done with the stable version in the Store. For now, we're focused on the latest builds, containing tentative fixes in both KDEConnect-Android and GSConnect. @Albert, do you have any logs (both KDEConnect and GSConnect) and Wireshark traces of your recent failures (using *all* the changes you've made so far)? With these, we should be able to determine at what precise stage the key negotiation fails, and see where the applications still fall short. (FYI, you can decrypt GSConnect's TLS traffic in Wireshark using steps explained here: https://github.com/GSConnect/gnome-shell-extension-gsconnect/discussions/1548#discussioncomment-4682656 and https://github.com/GSConnect/gnome-shell-extension-gsconnect/discussions/1548#discussioncomment-5273879) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #48 from Brian --- "Permission denied" sounds a lot like a different issue I've had before -- https://bugs.kde.org/show_bug.cgi?id=432368 To fix it, you just need to set the Custom Destination in KDE-C Android to your Downloads folder, navigating there. (Repeat this even if the path looks already set). Also to capture useful traces, you'll need to follow the steps at the first link I sent earlier to configure Wireshark to decrypt the TLS traffic between GSConnect and KDE-C Android. The steps are fairly straightforward -- one-liner modifying GSConnect's daemon.js to add an SSLKEYLOGFILE path, pointing Wireshark to that same path, reboot, and begin logging with Wireshark. (I'm not sure if/how the decryption can be done with a tcpdump cmdline.) Any saved traces should now contain the decrypted traffic -- a decrypted packet should look like the image at that first link. Your phone's live "adb logcat" would also be very useful to see app-level errors. If you like, you can limit both traces and logcat to just the rough time period when you run the tests. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 Brian changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|NEEDSINFO --- Comment #60 from Brian --- So far i have not had this issue occur with a git build of Plasma which has the compositing rework patches. I tentatively want to say this was fixed, however the only way to know for sure will be to continue using it for some time and testing it on other distros. Anyone else able to confirm if the issue is gone with the latest git? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429757] Firefox 83 Wayland: clipboard - copy from firefox & paste to kate not working
https://bugs.kde.org/show_bug.cgi?id=429757 Brian changed: What|Removed |Added CC||brianabe...@gmail.com --- Comment #2 from Brian --- (In reply to Martin Kostolný from comment #1) > After more testing I can see that this problem is only related to address > bar in firefox. Copying from within browser viewport is fine. Even from > native GTK widgets (such as textfields) rendered in page. > > I will investigate further. It's not just Firefox's address bar. The password vault also does not allow you to copy (in my case to XWayland applications). Copying from the main viewport works however. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 Brian changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #46 from Brian --- I haven't had any major issues with window focus in 5.19 as of recently. I believe this bug is finally resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 423529] New: Right side of the screen clipping in plasma mobile
https://bugs.kde.org/show_bug.cgi?id=423529 Bug ID: 423529 Summary: Right side of the screen clipping in plasma mobile Product: frameworks-kirigami Version: Master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: brianabe...@gmail.com Target Milestone: Not decided Created attachment 129688 --> https://bugs.kde.org/attachment.cgi?id=129688&action=edit photo of clipping issue in discover SUMMARY The right side of the screen is clipping in KWeather and discover in kde neon on the Pinephone. OBSERVED RESULT Right side of the screen is clipped and not visible SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413034] Cursor flickers/artifacts with fractional scaling on wayland
https://bugs.kde.org/show_bug.cgi?id=413034 Brian changed: What|Removed |Added CC||brianabe...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Brian --- I experience this issue with or without fractional scaling on Wayland in Plasma 5.19.3 with QT 5.15 on Arch Linux (AMDGPU driver). Not only does the cursor flicker, but the shadows look odd, and there is often artifacts on it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429748] New: Wayland Clicking icon task button does not cycle windows
https://bugs.kde.org/show_bug.cgi?id=429748 Bug ID: 429748 Summary: Wayland Clicking icon task button does not cycle windows Product: plasmashell Version: 5.20.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: brianabe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY With click to cycle windows enabled, in wayland if you click on a group of window icons in the taskbar to cycle through them, it does not cycle them and doesn't do anything for that matter. Observed on Arch Linux and KDE Neon User Stable in Wayland. OBSERVED RESULT Nothing happens. EXPECTED RESULT Clicking grouped icons only task should cycle the windows and cycle through them as if you did a alt-tab. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.10-zen1-1-zen OS Type: 64-bit Processors: 4 × Intel® Core™ i3-10110U CPU @ 2.10GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 Brian changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Ever confirmed|1 |0 CC||brianabe...@gmail.com --- Comment #19 from Brian --- Built from git master, i am still encountering this issue, and infact i think it's worse than before. I am completely unable to copy or paste between a Wayland and XWayland application now. Before this i used to be able to paste sometimes by using the middle mouse button, but even that doesn't work at all now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429750] New: Wayland window thumbnail covers right click menu
https://bugs.kde.org/show_bug.cgi?id=429750 Bug ID: 429750 Summary: Wayland window thumbnail covers right click menu Product: plasmashell Version: 5.20.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: brianabe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Right clicking on a icon-only task manager button so that you can pin an app or do some other action does not work in Wayland because the window thumbnail preview covers the right-click menu. Observed in Arch Linux and KDE Neon User Stable on Wayland. STEPS TO REPRODUCE 1. Right click a icons-only task manager button 2. Observe the window thumbnail popups covers the right click menu EXPECTED RESULT The window thumbnails should not popup if you've right clicked on the window button to access the app pinning and new instance options. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.10-zen1-1-zen OS Type: 64-bit Processors: 4 × Intel® Core™ i3-10110U CPU @ 2.10GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429748] Wayland Clicking icon task button does not cycle windows
https://bugs.kde.org/show_bug.cgi?id=429748 --- Comment #1 from Brian --- I've discovered the cause for this bug. It's the Xwayland window focus bug causing this to happen. When an XWayland application such as spotify is in focus and you try to focus say firefox wayland, it will not pop over the spotify window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #57 from Brian --- Is there a focus check done in kwin to see if a window is open and being used? The clipboard not working with Xwayland apps, the window cycling breaking when an XWayland application is in main focus, and XWayland windows loosing input after a while... Is there perhaps an issue with Kwin's focus checks? Perhaps it's bugging out and stops realizing that an XWayland application is in focus, and therefor the clipboard, window input, etc no longer operate correctly? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429748] Wayland Clicking icon task button does not cycle windows
https://bugs.kde.org/show_bug.cgi?id=429748 --- Comment #2 from Brian --- https://www.youtube.com/watch?v=LjHwT1f2u7M At least that's what i think is the cause. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #58 from Brian --- https://www.youtube.com/watch?v=LjHwT1f2u7M -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421131] Wayland: cursor lags under heavy CPU load
https://bugs.kde.org/show_bug.cgi?id=421131 Brian changed: What|Removed |Added CC||brianabe...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #10 from Brian --- Wayland definitely becomes laggy and slow when the system is under load (I've tested various distros and builds from git). It's not just the cursor however, but with that said gnome seems to have moved the cursor rendering to a seperate CPU thread... Perhaps the same might be good for Plasma Wayland? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #59 from Brian --- The isssues i've had with the clipboard must be related to the focus breaking. https://invent.kde.org/plasma/kwin/-/blob/0549c14588e0ccdbd4d78bb710e1c7569b409247/xwl/clipboard.cpp (Line 141 checks window focus before allowing clipboard actions... but if the focus is broken, then it obviously can't access the clipboard.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 Brian changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #21 from Brian --- I think there's more to this bug than just the race condition, especially since i still encounter this. I think a partial cause is that window focus issues make it so that the clipboard cannot be accessed. At line 141 in https://invent.kde.org/plasma/kwin/-/blob/0549c14588e0ccdbd4d78bb710e1c7569b409247/xwl/clipboard.cpp it seems it's checking for XWayland application focus before allowing the use of the clipboard. However, if the window focus is broken, then this would not work obviously, hence why it is still breaking despite this patch? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 --- Comment #23 from Brian --- (In reply to Nate Graham from comment #22) > Would you be interested in hacking on it a bit and submitting a merge > request? I wish i could, but i have no idea how Kwin works, and it isn't an issue with the clipboard code i shared but rather window handling. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346519] System Settings crashes on launch in QSGRenderLoop::handleContextCreationFailure()
https://bugs.kde.org/show_bug.cgi?id=346519 Brian changed: What|Removed |Added CC||bagood...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346519] System Settings crashes on launch in QSGRenderLoop::handleContextCreationFailure()
https://bugs.kde.org/show_bug.cgi?id=346519 --- Comment #93 from Brian --- Created attachment 133909 --> https://bugs.kde.org/attachment.cgi?id=133909&action=edit New crash information added by DrKonqi kcmshell5 (5.18.4) using Qt 5.12.8 - What I was doing when the application crashed: Tried to open network settings from right click menu. Same crash happens if I try to get to any system settings from application menu. -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fb083e2c859 in __GI_abort () at abort.c:79 #8 0x7fb082759aad in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #11 0x7fb0824eb036 in QQuickWidget::resizeEvent(QResizeEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #12 0x7fb0833b5947 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434663] New: Unable to create a full external disk ext4 partition
https://bugs.kde.org/show_bug.cgi?id=434663 Bug ID: 434663 Summary: Unable to create a full external disk ext4 partition Product: partitionmanager Version: 20.12.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: bk_b...@use.startmail.com Target Milestone: --- Created attachment 136878 --> https://bugs.kde.org/attachment.cgi?id=136878&action=edit step 4 SUMMARY Tried to format the hard drive to ext4, 1 full partition. Every time, the partition is smaller than the full disk size. Every other program sees the partition as the correct size (I also ran out of space when copying). Gnome disks shows what I think is the correct partition size is. STEPS TO REPRODUCE 1. Open KDE Partition Manager 2. Select disk 3. Delete existing partition (I only had 1, it is now all unallocated/unknown) 4. Right click > New. Filesystem: ext4 (attached, don't think I changed anything else) 5. [Apply] on KDE Partition Manager, top left OBSERVED RESULT The 3TB hard drive has 1 partition of 802GB. KDE Partition Manager seems to think that it has applied one partition for the whole disk. There doesn't seem to be a problem with the functioning of the created small partition. EXPECTED RESULT 1 partition of 2,861,568.00 MiB size, ext4 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.10.0-4-amd64 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Gnome Disks formatted the drive correctly, it doesn't seem to be a hardware issue. Hard drive specs: Seagate Backup Plus Desktop Drive Model: SRD0SD0 PN:1DXAD7-500 3 TB Thanks for your work -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434663] Unable to create a full external disk ext4 partition
https://bugs.kde.org/show_bug.cgi?id=434663 --- Comment #1 from Brian --- Created attachment 136879 --> https://bugs.kde.org/attachment.cgi?id=136879&action=edit what KDE Partition Manager creates -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434663] Unable to create a full external disk ext4 partition
https://bugs.kde.org/show_bug.cgi?id=434663 --- Comment #2 from Brian --- Created attachment 136880 --> https://bugs.kde.org/attachment.cgi?id=136880&action=edit difference between what KDE partition manager thinks it created and what everything else sees -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434668] New: When opening KDE Partition Manager, there should be a focus on the Authentication window
https://bugs.kde.org/show_bug.cgi?id=434668 Bug ID: 434668 Summary: When opening KDE Partition Manager, there should be a focus on the Authentication window Product: partitionmanager Version: 20.12.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: bk_b...@use.startmail.com Target Milestone: --- Created attachment 136884 --> https://bugs.kde.org/attachment.cgi?id=136884&action=edit Present SUMMARY When opening KDE Partition Manager, there should be a focus on the Authentication window (you can't do anything else with it) 1. Open KDE Partition Manager (from Plasma menu or Cairo-Dock) OBSERVED RESULT The Authentication window is not in focus (Image 1). It has to be clicked in the taskbar. EXPECTED RESULT Image two. The Authentication window should be in focus. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.10.0.4-amd-64 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Many thanks -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434668] When opening KDE Partition Manager, there should be a focus on the Authentication window
https://bugs.kde.org/show_bug.cgi?id=434668 --- Comment #1 from Brian --- Created attachment 136885 --> https://bugs.kde.org/attachment.cgi?id=136885&action=edit after clicking the tab in the taskbar (bottom left) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434668] When opening KDE Partition Manager, there should be a focus on the Authentication window
https://bugs.kde.org/show_bug.cgi?id=434668 --- Comment #3 from Brian --- Sorry about that, I missed that. I am on X11 I believe On Saturday, March 20, 2021 2:02 PM, "Andrius Štikonas" wrote: > > https://bugs.kde.org/show_bug.cgi?id=434668 > > Andrius Štikonas changed: > >What|Removed |Added > > > Resolution|--- |LATER > Status|REPORTED|RESOLVED > > --- Comment #2 from Andrius Štikonas --- > On plasma wayland this is not possible yet. It's WIP on Plasma side. > > There is an already reported bug for X11. > > But it might be that once Plasma Wayland supports raising windows, the > same > solution would work for both Wayland and X11. > > -- > You are receiving this mail because: > You reported the bug. > > > -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434663] Unable to create a full external disk ext4 partition
https://bugs.kde.org/show_bug.cgi?id=434663 --- Comment #4 from Brian --- Delete partition ‘/dev/sdb1’ (2.73 TiB, ext4) Job: Delete file system on ‘/dev/sdb1’ Command: wipefs --all /dev/sdb1 Delete file system on ‘/dev/sdb1’: Success Job: Delete the partition ‘/dev/sdb1’ Command: sfdisk --force --delete /dev/sdb 1 Delete the partition ‘/dev/sdb1’: Success Delete partition ‘/dev/sdb1’ (2.73 TiB, ext4): Success Create a new partition (2.73 TiB, ext4) on ‘/dev/sdb’ Job: Create new partition on device ‘/dev/sdb’ Command: sfdisk --force --append /dev/sdb Create new partition ‘/dev/sdb1’: Success Job: Set the attributes on partition ‘/dev/sdb1’ to "66003200640066" Partition table of partition ‘/dev/sdb1’ does not support setting attributes. Job ignored. Set the attributes on partition ‘/dev/sdb1’ to "66003200640066": Success Job: Create file system ‘ext4’ on partition ‘/dev/sdb1’ Command: mkfs.ext4 -qF /dev/sdb1 Command: sfdisk --part-type /dev/sdb 1 83 Create file system ‘ext4’ on partition ‘/dev/sdb1’: Success Job: Set the file system label on partition ‘/dev/sdb1’ to "" Command: e2label /dev/sdb1 Set the file system label on partition ‘/dev/sdb1’ to "": Success Job: Check file system on partition ‘/dev/sdb1’ Command: e2fsck -f -y -v /dev/sdb1 Check file system on partition ‘/dev/sdb1’: Success Create a new partition (2.73 TiB, ext4) on ‘/dev/sdb’: Success -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434663] Unable to create a full external disk ext4 partition
https://bugs.kde.org/show_bug.cgi?id=434663
--- Comment #7 from Brian ---
user@tuxedo:~$ sudo sfdisk /dev/sdb -l
Disk /dev/sdb: 2.73 TiB, 3000592977920 bytes, 732566645 sectors
Disk model: Backup+ Desk
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 268431360 bytes
Disklabel type: dos
Disk identifier: 0x20cf7de4
Device Boot Start End Sectors Size Id Type
/dev/sdb12048 732563455 732561408 2.7T 83 Linux
user@tuxedo:~$ dumpe2fs -h /dev/sdb1 |& awk -F: '/Block count/{count=$2} /Block
size/{size=$2} END{print count*size}'
0
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 434663] Complain if trying to create MBR partitiion table that is larger than 2 TiB - 512B
https://bugs.kde.org/show_bug.cgi?id=434663 --- Comment #10 from Brian --- (In reply to Alois Wohlschlager from comment #8) > > Disklabel type: dos > > That's what I suspected. MBR partition tables do not work properly with > disks larger than 2TB. I recommend creating a new partition table in GPT > format. > > @Andrius, do you think partitionmanager should complain here? Thanks. I'll search how to GPT, I didn't even know there was an option. Cheers -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 493091] New: Dolphin crash handler report
https://bugs.kde.org/show_bug.cgi?id=493091
Bug ID: 493091
Summary: Dolphin crash handler report
Classification: Applications
Product: dolphin
Version: 24.08.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: bjrosm...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (24.08.0)
Qt Version: 6.7.2
Frameworks Version: 6.5.0
Operating System: Linux 6.10.6-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.1.4 [CoredumpBackend]
-- Information about the crash:
Was transferring data from a local drive to a mounted remote drive over SMB
while also writing files to the local drive. Drive performance started to
degrade until dolphin locked up entirely, then minutes later the crash
handler/reporter popped up. After the crash, drive performance returned to a
more reasonable level.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/dolphin...
Downloading executable for /usr/lib/libgallium-24.2.1-arch1.1.so (deleted)...
Downloading executable for /usr/lib/libglapi.so.0.0.0 (deleted)...
Downloading executable for /usr/lib/libEGL_mesa.so.0.0.0 (deleted)...
Downloading executable for /usr/lib/libgbm.so.1.0.0 (deleted)...
[New LWP 2543458]
[New LWP 5174]
[New LWP 5176]
[New LWP 5179]
[New LWP 5177]
[New LWP 5180]
[New LWP 5183]
[New LWP 5181]
[New LWP 115283]
[New LWP 5175]
[New LWP 5178]
[New LWP 5199]
[New LWP 2541037]
[New LWP 2543434]
[New LWP 2543087]
[New LWP 2541068]
[New LWP 5182]
Downloading separate debug info for /usr/lib/libdolphinprivate.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOFileWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6NewStuffWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6Parts.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6Completion.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOGui.so.6...
Downloading separate debug info for /usr/lib/libKF6JobWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6WindowSystem.so.6...
Downloading separate debug info for /usr/lib/libKF6BalooWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOCore.so.6...
Downloading separate debug info for /usr/lib/libKF6Crash.so.6...
Downloading separate debug info for /usr/lib/libKF6Baloo.so.6...
Downloading separate debug info for /usr/lib/libKF6Solid.so.6...
Downloading separate debug info for /usr/lib/libKF6Service.so.6...
Downloading separate debug info for /usr/lib/libKF6KCMUtils.so.6...
Downloading separate debug info for /usr/lib/libKF6XmlGui.so.6...
Downloading separate debug info for /usr/lib/libKF6IconThemes.so.6...
Downloading separate debug info for /usr/lib/libKF6KCMUtilsCore.so.6...
Downloading separate debug info for /usr/lib/libKF6DBusAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6Notifications.so.6...
Downloading separate debug info for /usr/lib/libKF6BookmarksWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6Bookmarks.so.6...
Downloading separate debug info for /usr/lib/libQt6Xml.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6WidgetsAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6CoreAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6ColorScheme.so.6...
Downloading separate debug info for /usr/lib/libKF6I18n.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigGui.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigCore.so.6...
Downloading separate debug info for /usr/lib/libQt6DBus.so.6...
Downloading separate debug info for /usr/lib/libphonon4qt6.so.4...
Downloading separate debug info for /usr/lib/libKF6UserFeedbackWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6UserFeedbackCore.so.6...
Downloading separate debug info for /usr/lib/libQt6Widgets.so.6...
Downloading separate debug info for /usr/lib/libQt6Gui.so.6...
Downloading separate debug info for /usr/lib/libQt6Core.so.6...
Downloading separate debug info for /usr/lib/libc.so.6...
Downloading separate debug info for /usr/lib/libdolphinvcs.so.6...
Downloading separate debug info for /usr/lib/libKF6TextWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6Codecs.so.6...
Downloading separate debug info for /usr/lib/libKF6FileMetaData.so.3...
Downloading separate debug info for /usr/lib/libm.so.6...
Downloading separate debug info for /usr/lib/libKF6ItemViews.so.6...
Downloading separat
[kdeconnect] [Bug 492471] New: Sharing links to phone always opens the link in default browser/app
https://bugs.kde.org/show_bug.cgi?id=492471 Bug ID: 492471 Summary: Sharing links to phone always opens the link in default browser/app Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 14.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: bcej...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Sharing a link to KDE Connect inevitably causes that link to get opened in a browser, which is often not what a user wants. STEPS TO REPRODUCE 1. Use the Share URL option from a PC to send a link to KDE Connect 2. A notification appears on the phone, showing the shared link. 3. Tap the notification. OBSERVED RESULT The link is automatically opened in the default browser, or the relevant default app (which could be Google Docs, or similar, with all the tracking therein). EXPECTED RESULT KDE Connect should at least offer the option to either *copy* the link or open it in the default browser/app. This is especially important in Android 13 onwards where users are forced to pick a default browser and can no longer use "Open With" to choose a browser for opening each link. Very often, you don't want to open the links you're sharing -- you just want to share them in some chat or paste them somewhere or similar. After all, if you're sharing a link to your phone, chances are you already opened the thing on your PC, so merely opening it again on your phone is unlikely to be the goal of your sharing. Or if you want to open it, you want to do so in an app of your own choosing. SOFTWARE/OS VERSIONS Android 14 Ubuntu 21.10 + GSConnect on the PC (though this is irrelevant) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 492471] Sharing links to phone always opens them in the default browser/app
https://bugs.kde.org/show_bug.cgi?id=492471 Brian changed: What|Removed |Added Summary|Sharing links to phone |Sharing links to phone |always opens the link in|always opens them in the |default browser/app |default browser/app -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 400320] New: Some emails stays in outgoing folder
https://bugs.kde.org/show_bug.cgi?id=400320 Bug ID: 400320 Summary: Some emails stays in outgoing folder Product: amarok Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: bc314...@gmail.com CC: kdepim-b...@kde.org, t.ki...@gmail.com Depends on: 400195 Target Milestone: kf5 +++ This bug was initially created as a clone of Bug #400195 +++ SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION SUMMARY KMail is not able to send some emails using properly set-up gmail account STEPS TO REPRODUCE 1. Add google account, send some emails 2. After some point, it stop to work (emails will stay in Outgoing folder) 3. Reboot, it helps until it breaks again. OBSERVED RESULT Some emails stays in Outgoing folder until I reboot. EXPECTED RESULT At least to tell me there is some kind of problem, i use KMail in business environment. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14 KDE Frameworks Version: 5.51 Qt Version: 5.11.1 KMail 5.9.2 ADDITIONAL INFORMATION Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=400195 [Bug 400195] Some emails stays in outgoing folder -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 400195] Some emails stays in outgoing folder
https://bugs.kde.org/show_bug.cgi?id=400195 Brian changed: What|Removed |Added Blocks||400320 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=400320 [Bug 400320] Some emails stays in outgoing folder -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407848] New: Add AMD Variable Refresh Rate toggle (Freesync) in display settings for Xorg
https://bugs.kde.org/show_bug.cgi?id=407848 Bug ID: 407848 Summary: Add AMD Variable Refresh Rate toggle (Freesync) in display settings for Xorg Product: systemsettings Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: brianabe...@gmail.com Target Milestone: --- I saw the report asking for support in kwin for variable refresh rate. Games and some applications are able to take advantage of it, even if Kwin cannot. It would be nice as a stop-gap measure to offer a toggle switch in the system settings which would enable the Xorg VRR setting for AMDGPU and therefor turn on Freesync. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #25 from Brian --- Created attachment 120366 --> https://bugs.kde.org/attachment.cgi?id=120366&action=edit Logfile which includes period when the focus issue occured. Not sure if this has any related errors to the focus bug, however there was some other issues during the time that i was testing, and i did encounter the focus bug with Minecraft, Steam, And Firefox. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness
https://bugs.kde.org/show_bug.cgi?id=385522 Brian changed: What|Removed |Added CC||brianabe...@gmail.com --- Comment #41 from Brian --- Agreed. This bug definitely needs to be fixed. At least set the brightness a tad higher. A better solution however would be to offer the ability to change the brightness of the feature. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 Brian changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #27 from Brian --- Yup. All versions of plasma. I'm really hoping it will get resolved for 5.17, but because nobody knows what's causing it, i imagine it wont be fixed for a while unfortunately. I've since switched back to Xorg with Kwin-lowlatency to get the smoothest experience. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #36 from Brian --- Can bug priority be changed? This is a pretty big issue, and i think it should get some attention before 5.18. Otherwise, Wayland will continue to be essentially unusable on AMD graphics cards (Vega 8 & 11 APUs, and Radeon RX 400 & 500s from my testing). I've tested it on a bunch of hardware and have reproduced it each time. Intel hardware doesn't seem affected at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #38 from Brian --- (In reply to Patrick Silva from comment #37) > I use intel hd graphics and this issue affects my system. Ah sorry. I didn't recall the people reporting it on Intel too. As i showed from my comment, it's not easy to detect sometimes because of how random it can be. So it could definitely be some kind of race condition in kwin, or a bug in XWayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #40 from Brian --- (In reply to Roman Gilg from comment #39) > I'm not able to reproduce it. Is there a way to reproduce it consistently? I > tried method in comment 13, but didn't fail for me. No, that's the issue. It's extremely random. The way i an eventually reproduce it on various machines is to use a bunch of Xwayland applications and minimize them, restore them, and right click inside them. Eventually you should notice some odd behavior, like firefox not showing the right click menu, a website frozen in firefox after restoring a minimized window, discord showing someone is typing frozen and not letting you input anything after restoring it, and spotify not letting you click on anything in it's UI because it's window is frozen after restoring it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378144] Hiding mouse cursor causes black flash
https://bugs.kde.org/show_bug.cgi?id=378144 Brian changed: What|Removed |Added CC||brianabe...@gmail.com --- Comment #3 from Brian --- Can reproduce black flash in Wayland on 5.17.80 Operating System: Arch Linux KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 5.3.6-arch1-1-fsync OS Type: 64-bit Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor Memory: 15.7 GiB of RAM GPU: Sapphire RX 560 8GB Mesa 19.3.0-devel (git-fe930ad92a) (Valve ACO) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #42 from Brian --- Probably not mouse clicks actually. But either way, my guess is that something is wrong with the window surface handling. Windows might glitching between each other leading to the surface clipping symptoms, and also the input/content rendering issues of this bug report (Maybe the input is actually being recieved, just not either A: to the right application (because of focus being sent to the wrong application), or B: not rendered because of clipping/surface issues). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #41 from Brian --- (In reply to Roman Gilg from comment #39) > I'm not able to reproduce it. Is there a way to reproduce it consistently? I > tried method in comment 13, but didn't fail for me. Been doing testing and i think what might be happening is the window below is randomly getting input such as mouse clicks (the desktop?), leading to kwin mistakenly thinking you clicked something else, and therefor stopping you from inputing text. Meanwhile kwin renders the last thing the window was showing, leading to the still content seen. This surface glitching seems to happen most often with Firefox in Xwayland. In my experience when it happens, dialogs will open but not show, but if you use kwin's present window hotcorner you can see that it did infact open and that it's artifacted and invisble. Interestingly i just had the surface glitching happen randomly when downloading a file. The dialog opened, but it was artifacted and almost fully invisible, yet i could still click on it's titlebar. As a matter of fact, i know extremely similar behavior to this can be reproduced easily if you open Firefox with it's Wayland backend enabled. You will not only see tons of artfacting and misplaced UI elements should you move it or interact with it, but you will also find that some of your clicks are not registered and that windows below it are clipped up through it, giving you a mangled mess. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Brian changed: What|Removed |Added CC||brianabe...@gmail.com --- Comment #35 from Brian --- I've seen this on Manjaro and KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078
--- Comment #42 from Brian ---
(In reply to Carson Black from comment #39)
> Git commit b1649126c8c6d1af746a8472939fcda40a260095 by Carson Black.
> Committed on 29/10/2019 at 00:26.
> Pushed by cblack into branch 'Plasma/5.17'.
>
> [GTK3] Revert checkbox recolouring
>
> Summary:
> This reverts the effects of commit 7b3d0777ea6c10dd430ed686434d3a4e2d072632
> and some effects of commit 987f750ea16a6f82d29cd6504a69d93575c895d4,
> meaning that checkboxes and radiobuttons will no longer attempt to follow
> the colourscheme.
>
> This is necessary because the facilities used to recolour checkboxes are now
> glitchy in GTK
> and result in usability issues. See
> https://gitlab.gnome.org/GNOME/gtk/issues/2217
> FIXED-IN: 5.17.2
>
> Test Plan:
> Before: https://bugs.kde.org/show_bug.cgi?id=412078
> After: {F7675941}
>
> Reviewers: #vdg, ngraham
>
> Reviewed By: #vdg, ngraham
>
> Subscribers: ngraham, plasma-devel
>
> Tags: #plasma
>
> Differential Revision: https://phabricator.kde.org/D24994
>
> M +58 -34 src/gtk3/widgets/_checkboxes.scss
> M +8-21 src/gtk3/widgets/_menus.scss
>
> https://commits.kde.org/breeze-gtk/b1649126c8c6d1af746a8472939fcda40a260095
Will this ever be re-enabled?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 Brian changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #24 from Brian --- It seems the bug is still present to a lesser degree for some apps in wayland. The act of minimizing and maximizing windows to fix the focus no long works very well for it either. Also now affects Kwin titlebars of the affected applications. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406485] KDE forgets my display settings after reboot
https://bugs.kde.org/show_bug.cgi?id=406485 Brian changed: What|Removed |Added CC||brianabe...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Brian --- Can confirm this bug affects Solus as well. -- You are receiving this mail because: You are watching all bug changes.
