[okular] [Bug 443909] Feature request: Horizontal Scroll Page
https://bugs.kde.org/show_bug.cgi?id=443909 Ryan changed: What|Removed |Added Resolution|--- |DUPLICATE CC||r...@interoctiv.com Status|REPORTED|RESOLVED --- Comment #1 from Ryan --- *** This bug has been marked as a duplicate of bug 343910 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 343910] horizontal continuous scrolling
https://bugs.kde.org/show_bug.cgi?id=343910 Ryan changed: What|Removed |Added CC||peter.meilst...@gmail.com --- Comment #7 from Ryan --- *** Bug 443909 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443909] Feature request: Horizontal Scroll Page
https://bugs.kde.org/show_bug.cgi?id=443909 --- Comment #2 from Ryan --- (In reply to Peter Meilstrup from comment #0) > I am reading material that has a multicolumn layout, or a book scanned from > facing pages. To read it I need to zoom in so that a column is legible, then > read down the page, then scroll up and to the right to find where the column > continues. The last part, scrolling right, is the difficulty. Same use-case, same issue for me. There is more discussion in the older bug (343910), so I marked this one as a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454902] New: Display Port Monitor Does Not Activate Past Login Screen In Fedora 36
https://bugs.kde.org/show_bug.cgi?id=454902 Bug ID: 454902 Summary: Display Port Monitor Does Not Activate Past Login Screen In Fedora 36 Product: kwin Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: dasg...@protonmail.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 *** I have a 3 monitor setup on a AMD 6900XT GPU. All three have been working recently. However, after an update the one monitor using Display Port does not get a signal AFTER login to KDE Plasma in Fedora 36. Tried in Fedora 36 in KDE 5.24.5. With kernel 5.17.12-300 and also trying kernel 5.17.11 and 5.17.9. This issue happens in Wayland and X11 The monitor does appear to show once logged in in Display Configuration (it's there as in a space for it but it's blank space). Tried installing LXQT DE and all three monitors work fine. It's just an issue in KDE Plasma as far as I can test. STEPS TO REPRODUCE 1. Login to KDE Plasma (X11 or Wayland) OBSERVED RESULT 2. After logging in two monitor (HDMI) initiate. The third monitory DP connection gets a 'no signal' error and remains blank. EXPECTED RESULT 3. 3rd monitor initializes SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.24.5 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION xrandr output: Screen 0: minimum 320 x 200, current 7840 x 2560, maximum 16384 x 16384 DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 disconnected (normal left inverted right x axis y axis) HDMI-A-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 698mm x 393mm 2560x1440143.97*+ 120.0059.95 1920x1200143.97 1920x1080120.00 119.8860.0060.0050.0059.94 1600x1200143.97 1680x1050119.9959.88 1280x1024119.9675.0260.02 1440x900 119.8559.90 1280x800 143.97 1280x720 60.0050.0059.94 1440x576 50.00 1024x768 75.0370.0760.00 1440x480 60.0059.94 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 HDMI-A-1 connected 1440x2560+6400+0 left (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 74.60 + 59.95* 1920x1200 74.60 1920x1080 60.0050.0059.94 1600x1200 74.60 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1440x576 50.00 1024x768 75.0370.0760.00 1440x480 60.0059.94 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0066.6760.0059.94 720x400 70.08 DisplayPort-2 connected (normal left inverted right x axis y axis) 3840x2160 60.00 + 60.0050.0059.9430.0025.0024.00 29.9723.9829.97 2560x1440 59.95 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1600x1200 60.00 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1280x800 59.81 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0360.00 1440x480 60.0059.94 832x624 74.55 800x600 75.0060.32 720x576 50.00 720x480 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 DisplayPort-3 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454902] Display Port Monitor Does Not Activate Past Login Screen In Fedora 36
https://bugs.kde.org/show_bug.cgi?id=454902 --- Comment #2 from Ryan --- (In reply to Zamundaaa from comment #1) > This sounds like KScreen is disabling the output for some reason. Can you > try renaming (not deleting) the folder "~/.local/share/kscreen"? Renaming the folder worked. I got all 3 screens working now. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454902] Display Port Monitor Does Not Activate Past Login Screen In Fedora 36
https://bugs.kde.org/show_bug.cgi?id=454902 --- Comment #4 from Ryan --- Created attachment 149579 --> https://bugs.kde.org/attachment.cgi?id=149579&action=edit New and old kscreen configuration files Per your request here are the new and original kscreen folders -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #8 from ryan --- (In reply to Halcyoen from comment #7) > i have what i think is the same issue on kde neon. the issue appears > whenever i press ctrl+alt or ctrl+shift. after this my canvas input command > for the color sampler (alt+left click) or resizing the brush (alt+right > click) stops working. the quickest way to "unblock" my canvas inputs is by > pressing ctrl again. > > this only seems to happen in the version downloaded from the official repos > though. i do not experience this issue on windows, not with the appimage > version and not with the flatpak version. is it tied to plasma somehow? > > as for the bug where you lose input after holding alt and selecting a new > brush preset, it seems to go back quite some time. at least krita 4.2. the > OS wouldnt let me open krita 4.0 for some reason. The problem happens to me with a fresh Ubuntu install on a virtual machine. I have used Kde for roughly 3 years now, and the problem has been consistent with every version past krita 5.0.2. In 5.0.2, there appears to be some version of this bug, but like you described, the key locking disappears after a short period of time. It's annoying, but still usable. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467993] New: konsole cannot run other apps
https://bugs.kde.org/show_bug.cgi?id=467993 Bug ID: 467993 Summary: konsole cannot run other apps Classification: KDE Neon Product: neon Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: sgmo...@kde.org Reporter: jryan.dani...@gmail.com CC: neon-b...@kde.org Target Milestone: --- SUMMARY *** I have upgraded the Kate snap to the latest. Since then I cannot run custom scripts on the built in konsole. *** STEPS TO REPRODUCE Try to start any of a number of apps from within Konsole (in kate). e.g. type in the Konsole inkscape gimp latex htop OBSERVED RESULT Nothing happens. EXPECTED RESULT Something happens. In the previous version of the snap I could run custom scripts and start other apps from kate. SOFTWARE/OS VERSIONS snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/stable refresh-date: today at 10:18 SAST channels: latest/stable:22.12.3 2023-03-27 (135) 212MB - latest/candidate: 22.12.3 2023-03-27 (135) 212MB - latest/beta: ↑ latest/edge: ↑ installed: 22.12.3(135) 212MB - ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467993] konsole cannot run other apps
https://bugs.kde.org/show_bug.cgi?id=467993 Ryan changed: What|Removed |Added Product|neon|kate Component|Snaps |general Assignee|sgmo...@kde.org |kwrite-bugs-n...@kde.org Version|unspecified |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467993] konsole cannot run other apps
https://bugs.kde.org/show_bug.cgi?id=467993 --- Comment #2 from Ryan --- (In reply to Waqar Ahmed from comment #1) > There was a change related to the snap store release recently, perhaps this > is due that? Yes, that is what has happened. I think the updates have been fantastic so far. It looks and works amazing. The only problem I have been having thus far is the problem with running almost anything in Konsole. I guess in creating the snap some plug needs to be specified to allow it to run things listed in the PATH. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467993] konsole cannot run other apps
https://bugs.kde.org/show_bug.cgi?id=467993 --- Comment #4 from Ryan --- (In reply to Scarlett Moore from comment #3) > Can you please update to the recent release 23.04.0 and see if the issue > still exists. It will need the --classic flag to install. > Thanks > Scarlett Hello I apologise for replying so late. Yes, with the --classic flag kate can run external programs. My external tools and the spelling checker are working again. Thank you for the help! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469858] New: Classic and confined snap don't use the same 'hidden' files
https://bugs.kde.org/show_bug.cgi?id=469858 Bug ID: 469858 Summary: Classic and confined snap don't use the same 'hidden' files Classification: Applications Product: kate Version: 23.04.0 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: jryan.dani...@gmail.com Target Milestone: --- SUMMARY *** I have moved from the confined snap to the classic snap. The keyboard shortcuts, external tools and sessions have reverted to a set-up from several months ago. I guess because the classic snap is not reading the information from the same place the confined snap was saving info to. *** STEPS TO REPRODUCE 1. ''' sudo snap refresh kate --classic''' 2. open kate via the terminal. OBSERVED RESULT The presented session information is from several months ago (when I refreshed to the confined snap). The external tools listed and the keyboard shortcuts appear to have reverted to that of several months ago as well. EXPECTED RESULT Kate initiates with the settings I was using most recently (i.e. before I refreshed to the classic snap). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu Sway 22.10 x86_64, 5.19.0-42-generic kernel (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.
[kate] [Bug 469884] New: snap fails to start
https://bugs.kde.org/show_bug.cgi?id=469884 Bug ID: 469884 Summary: snap fails to start Classification: Applications Product: kate Version: 23.04.1 Platform: Snap OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: jryan.dani...@gmail.com Target Milestone: --- SUMMARY *** Start kate via terminal, nothing happens. Yesterday before the snap was automatically refreshed, kate worked. Today, it doesn't. *** STEPS TO REPRODUCE 1. Start kate via terminal OBSERVED RESULT Nothing happens. There is nothing printed to the terminal either. EXPECTED RESULT Kate starts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu Sway 22.10 x86_64 , 5.19.0-42-generic kernel (available in About System) ADDITIONAL INFORMATION I was on 23.04.0 yesterday and it worked. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469884] snap fails to start
https://bugs.kde.org/show_bug.cgi?id=469884 --- Comment #1 from Ryan --- When I run '''snap revert kate''', kate works again. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 --- Comment #49 from Ryan --- Not using the app anymore. Go ahead and close. Ryan On Fri, Oct 7, 2022, at 17:38, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=378513 > > Justin Zobel changed: > >What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REOPENED|NEEDSINFO > > --- Comment #47 from Justin Zobel --- > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! > > -- > 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.
[ktorrent] [Bug 388966] Enabling "Search" plugin freezes KTorrent application
https://bugs.kde.org/show_bug.cgi?id=388966 --- Comment #20 from Ryan --- No longer freezes as in my Comment above. Debian testing ktorrent 21.12.3-1 amd64 But when I search for something I get This site can’t be reached ktorrent.searchplugin’s server IP address could not be found. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465499] New: Docs need screenshots
https://bugs.kde.org/show_bug.cgi?id=465499 Bug ID: 465499 Summary: Docs need screenshots Classification: Applications Product: krita Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: rj.amdphr...@gmail.com Target Milestone: --- ### SUMMARY The docs are not very useful and need screenshots. I'm trying to figure out where in the heck the rectangle corner rounding setting is, but I can't find it in the app, and the docs are next to useless for showing me where to look for it. https://docs.krita.org/en/reference_manual/tools/rectangle.html -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465499] Docs need screenshots
https://bugs.kde.org/show_bug.cgi?id=465499 --- Comment #1 from Ryan --- The "Size" properties shown in this video on Youtube do not show up for me with rectangles. https://www.bing.com/videos/search?q=krita+rounded+rectangle&&view=detail&mid=4FD5DEFE3796CDDC26EF4FD5DEFE3796CDDC26EF&&FORM=VRDGAR&ru=%2Fvideos%2Fsearch%3Fq%3Dkrita%2Brounded%2Brectangle%26FORM%3DHDRSC3 @ 4:35 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446874] Crash in QSGOpaqueTextureMaterialShader::updateState()
https://bugs.kde.org/show_bug.cgi?id=446874 Ryan changed: What|Removed |Added Flags||X11+ CC||mercy.sp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] New: Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 Bug ID: 489629 Summary: Add AsciiDoc MIME-type icons to Breeze Classification: Plasma Product: Breeze Version: 6.0.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: r...@interoctiv.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 171297 --> https://bugs.kde.org/attachment.cgi?id=171297&action=edit MIME-type icon for Asciidoc SUMMARY AsciiDoc files do not have a branded MIME-type icon in the Breeze icon theme. STEPS TO REPRODUCE 1. Create a file with the .adoc extension 2. View directory in Dolphin OBSERVED RESULT AsciiDoc files appear with a generic text icon. Non-empty files are treated as text, and empty files have no associated application. EXPECTED RESULT Empty and non-empty files with the .adoc or .asciidoc extension will appear with an AsciiDoc-specific icon and be associated with a text editor by default. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240605 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION See AsciiDoc brand guidelines here: https://gitlab.eclipse.org/eclipse-wg/asciidoc-wg/asciidoc-wg/-/tree/main/brand. I have created AsciiDoc icons for Breeze light in 16, 22, 32, and 64 pixels. See attached 64-pixel example. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 Ryan changed: What|Removed |Added Attachment #171297|MIME-type icon for Asciidoc |Asciidoc icon (64px) for description||Breeze light -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 --- Comment #1 from Ryan --- Created attachment 171298 --> https://bugs.kde.org/attachment.cgi?id=171298&action=edit Asciidoc icon (32px) for Breeze light -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 --- Comment #2 from Ryan --- Created attachment 171299 --> https://bugs.kde.org/attachment.cgi?id=171299&action=edit Asciidoc icon (22px) for Breeze light -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 --- Comment #3 from Ryan --- Created attachment 171300 --> https://bugs.kde.org/attachment.cgi?id=171300&action=edit AsciiDoc icon (16px) for Breeze light -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 Ryan changed: What|Removed |Added Attachment #171299|Asciidoc icon (22px) for|AsciiDoc icon (22px) for description|Breeze light|Breeze light -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 Ryan changed: What|Removed |Added Attachment #171298|Asciidoc icon (32px) for|AsciiDoc icon (32px) for description|Breeze light|Breeze light -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 Ryan changed: What|Removed |Added Attachment #171297|Asciidoc icon (64px) for|AsciiDoc icon (64px) for description|Breeze light|Breeze light -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 Ryan changed: What|Removed |Added CC||r...@interoctiv.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 --- Comment #5 from Ryan --- (In reply to Nate Graham from comment #4) > Nice, wanna submit them in the form of a merge request to > https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/? > > In the future you can just do that immediately; no need to submit a bug > report/feature request first. Sure. My account was closed previously, so thanks if you reactivated it. Should I create an issue first? -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 487169] Available answer buttons do not register the answer.
https://bugs.kde.org/show_bug.cgi?id=487169
--- Comment #2 from Ryan ---
ExerciseView.qml is the code in question:
https://github.com/KDE/minuet/blob/ab3fcedec21096ed1166e6872b9160705538bb84/src/app/qml/ExerciseView.qml#L317
Based on the documentation documentation here
https://doc.qt.io/qt-6/qml-qtquick-mousearea.html, here
https://doc.qt.io/qt-6/qtqml-syntax-objectattributes.html, and here
https://doc.qt.io/qt-6/qtqml-syntax-signals.html#property-change-signal-handlers),
my best guesses as a non-developer are these:
(a) Line 317 is missing an object declaration needed to explicitly point to the
onExit handler or set a property.
(b) Line 317 should use the `exited()` signal instead of `onExited` handler.
(c)
>313 MouseArea {
>314 anchors.fill: parent
>315 onClicked: {
>316 if (exerciseView.state == "waitingForAnswer" &&
>!animation.running) {
>317 onExited()
>...
>322 }
>323 }
ExerciseView.qml also includes the onExited handler. I think this is
irrelevant, because hovering over and exiting the button area work as expected
(activate/deactivate shading and the piano animation).
> onExited: {
> answerRectangle.color =
> internal.colors[answerRectangle.index%internal.colors.length]
> if (currentExercise["playMode"] != "rhythm") {
> if (parent.parent == answerGrid) {
> if (!animation.running)
> model.sequence.split(' ').forEach(function(note) {
> pianoView.noteUnmark(0,
> core.exerciseController.chosenRootNote() + parseInt(note), 0)
> })
> sheetMusicView.model =
> [core.exerciseController.chosenRootNote()]
> }
> }
> else {
> var rightAnswers = core.exerciseController.selectedExerciseOptions
> if (parent.parent == yourAnswersParent &&
> internal.userAnswers[position].name != rightAnswers[position].name) {
> parent.border.color = "red"
> parent.color = internal.userAnswers[position].color
> rhythmImage.source = "exercise-images/" +
> internal.userAnswers[position].name + ".png"
> }
> }
> }
> }
--
You are receiving this mail because:
You are watching all bug changes.
[Network Management] [Bug 215080] KNetworkManager crashes when VPN or static network selected (QAction::isSeparator)
https://bugs.kde.org/show_bug.cgi?id=215080 Ryan changed: What|Removed |Added CC||jgrul...@redhat.com, ||ryansalsbury...@gmail.com OS|Linux |All Platform|Unlisted Binaries |Android Component|knetworkmanager |Wireless -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484451] New: translation errors(zh_CN) in Kwin
https://bugs.kde.org/show_bug.cgi?id=484451 Bug ID: 484451 Summary: translation errors(zh_CN) in Kwin Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: spring...@outlook.com Target Milestone: --- SUMMARY In System Settings -> Keyboard -> Shortcuts -> Kwin, the Simplified Chinese translation of "Expand Window Vertically" and "Maximize Window Vertically" are both "垂直最大化窗口(Maximize Window Vertically)", and the Chinese translation of "Expand Window Horizontally" and " Maximize Window Horizontally" are both "水平最大化窗口(Maximize Window Vertically)". EXPECTED RESULT Expand Window Vertically -> 垂直扩展窗口 Maximize Window Vertically -> 垂直最大化窗口 Expand Window Horizontally -> 水平扩展窗口 Maximize Window Horizontally -> 水平最大化窗口 SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 478358] Agenda items should display contents from General textbox, not just Title
https://bugs.kde.org/show_bug.cgi?id=478358 Ryan changed: What|Removed |Added CC||denu...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 479760] Process becomes uninterruptable; requires forced reboot
https://bugs.kde.org/show_bug.cgi?id=479760 Ryan changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Ryan --- I completely forgot I filed the bug. It seems to have been an issue with my zpool set-up and my wavlink external drive. Drawing power from the wavlink hub resulted in the device transiently disconnecting. This caused zpool to stop responding and kate seemed to be worst affected by this but the problem is not a kate issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483688] New: keyboard shortcuts don't work
https://bugs.kde.org/show_bug.cgi?id=483688 Bug ID: 483688 Summary: keyboard shortcuts don't work Classification: Plasma Product: plasmashell Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: spring...@outlook.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY: Keyborad shortcuts set to meta+x, but don't work when pressed SOFTWARE/OS VERSIONS: Linux/KDE Plasma: ArchLinux(kernel: 6.7.9-arch1-1) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483688] keyboard shortcuts don't work
https://bugs.kde.org/show_bug.cgi?id=483688 --- Comment #2 from Ryan --- (In reply to duha.bugs from comment #1) > What shortcut did you bind to meta+x ? Every widget in the system tray > seemed to work fine for me. System Settings -> Keyboard -> Shortcuts -> plasmashell -> Activate System Tray Widget I bind the shortcut to Meta+x, but it doesn't seem to work. This problem only appeared after I upgraded to plasma 6, before that everything was fine -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 487169] New: Available answer buttons do not register the answer.
https://bugs.kde.org/show_bug.cgi?id=487169 Bug ID: 487169 Summary: Available answer buttons do not register the answer. Classification: Applications Product: minuet Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: user-interface Assignee: sandroandr...@kde.org Reporter: r...@interoctiv.com Target Milestone: --- SUMMARY Clicking or tapping on any of the buttons under 'available answers' does not register the answer. STEPS TO REPRODUCE 1. Open Minuet and navigate to any of the exercises in the left navigation. 2. Click, tap, or press space to 'Play Question'. 3. Click or tap on any of the available answers. OBSERVED RESULT * Hovering over the answer button activates shading and the visualisations on the keyboard and musical staff below * Answers cannot be focused using the key (unlike the `Play Question` `Give Up`, and `Start Test` buttons) * Clicking or tapping any of the answer buttons fails to register the answer. * Ouput in the terminal shows this error when the answer button is clicked: `qrc:/ExerciseView.qml:317: TypeError: Property 'onExited' of object QQuickMouseArea(0x7fd104002830) is not a function` EXPECTED RESULT * should move focus to the answers, and to submit, just like the `Play Question`, `Give Up`, and `Start Test` buttons. * Clicking or tapping should register the answer and allow advancement to the next question. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240509 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-1-default (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION * The answer buttons worked in the past few weeks before I last updated the operating system. Minuet may have been updated at that time. * I am also getting intermittent static noises briefly during some mouse interactions, such as moving the Minuet window and even when Minuet is not in focus. This stops when I exit Minuet. * Graphics could be an issue as I am using the proprietary Nvidia driver in a Plasma Wayland session. However, intel is currently active whereas Nvidia was in use the last time the buttons worked in Minuet. Device-1: Intel UHD Graphics 620 vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: DP-1,eDP-1 empty: DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300 Device-2: NVIDIA GP108M [GeForce MX150] vendor: Hewlett-Packard driver: nvidia v: 550.78 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of 2024-04; EOL~2026-12-xx) arch: Maxwell code: GMxxx process: TSMC 28nm built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1d10 class-ID: 0302 Device-3: Suyin HP TrueVision FHD RGB-IR driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:2 chip-ID: 064e:3401 class-ID: 0e02 serial: HF2066-P98B-OV07-REV0101 Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 23.2.6 compositor: kwin_wayland driver: X: loaded: modesetting,nvidia alternate: intel dri: iris gpu: i915,nvidia d-rect: 4480x2520 display-ID: 0 Monitor-1: DP-1 pos: primary,top-left res: 2560x1440 size: N/A modes: N/A Monitor-2: eDP-1 pos: bottom-r res: 1920x1080 size: N/A modes: N/A -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 487169] Available answer buttons do not register the answer.
https://bugs.kde.org/show_bug.cgi?id=487169 --- Comment #1 from Ryan --- Correction: The current video driver is nvidia. > prime-select get-current Driver configured: nvidia NVIDIA modules are loaded -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395131] Akonadi consumes all memory
https://bugs.kde.org/show_bug.cgi?id=395131 Ryan changed: What|Removed |Added CC||r...@interoctiv.com --- Comment #19 from Ryan --- (In reply to sombriks from comment #18) > Hi, i can confirm that bug still occurs ... > using openSUSE Tumbleweed kernel 6.5.6-1-default Also occurs with: openSUSE Tumbleweed 20240509 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 343910] horizontal continuous scrolling
https://bugs.kde.org/show_bug.cgi?id=343910 Ryan changed: What|Removed |Added CC||r...@interoctiv.com --- Comment #4 from Ryan --- Continuous horizontal scrolling is an important feature for me. It is available in PDF-XChange, which I pay for and use mainly because of this feature. However, PDF-XChange is a commercial application for Windows only. My primary use case is reading and adding annotations to scientific journal articles. Typically, these have a two-column layout that makes vertical scrolling awkward. In contrast, continuous horizontal scrolling: - always places related columns adjacent to each other; - allows use of the full horizontal space of a wide screen, making it easier, for instance, to view a graph or table on one page while referring to related text on another page; - provides the flexibility to view even-odd page-pairs (with the even-numbered page on the left); and - the reading experience is more natural than vertical scrolling (for material that represents printed media), because left/right scrolling moves in the same direction as a physical page-turn. In PDF-XChange, rolling the mouse wheel up/down scrolls left/right (or right/left) if the page view is zoomed to page height or less. When the zoom is greater than full page height, the wheel changes to up/down scrolling. Left/right scrolling is still possible with a tilting mouse wheel or using the grabber (pan tool). Continuous horizontal scrolling is remarkably useful, yet not found in any other PDF application, to my knowledge, other than PDF-XChange. It would be great to see this added to Okular. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 343910] horizontal continuous scrolling
https://bugs.kde.org/show_bug.cgi?id=343910 --- Comment #5 from Ryan --- (In reply to Ryan from comment #4) > Continuous horizontal scrolling is remarkably useful, yet not found in any > other PDF application, to my knowledge, other than PDF-XChange. Correction: the PDF viewer in Firefox (94.0.1) includes horizontal scrolling. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 343910] horizontal continuous scrolling
https://bugs.kde.org/show_bug.cgi?id=343910 --- Comment #6 from Ryan --- (In reply to David Hurka from comment #2) > Fit Width wouldn’t make sense for horizontal continuous mode Fit Width should fit the width of exactly one page -- the current page -- regardless of its orientation, and not the total width of a multi-page document. > Fit Width and Fit Height could be the same option This would depend on size and orientation of the monitor and page displayed. With a 16x9 monitor, for example, in landscape orientation, vertical space is usually the constraint (if the page is of A4 or letter size and in portrait orientation), so Fit Page and Fit Height would produce the same result. With the monitor in portrait orientation, horizontal space would become the constraint, meaning that Fit Page and Fit Width would now produce the same result, whereas Fit Height would fill the screen vertically, leaving one or both sides of the page out of view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454057] New: Executable: plasmashell PID: 2647
https://bugs.kde.org/show_bug.cgi?id=454057 Bug ID: 454057 Summary: Executable: plasmashell PID: 2647 Product: plasmashell Version: 5.24.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: itsbugf...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.5) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.13.0-41-generic x86_64 Windowing System: X11 Distribution: Feren OS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: every time i login/turn on computer and get inside Feren OS The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [New LWP 2677] [New LWP 2681] [New LWP 2682] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f6eddb3a99f in poll () from /lib/x86_64-linux-gnu/libc.so.6 __preamble__ [Current thread is 1 (Thread 0x7f6ed9c7c9c0 (LWP 2647))] Thread 4 (Thread 0x7f6ed1052700 (LWP 2682)): #0 0x7f6edd865376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f6ed1c375eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7f6ed1c371eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7f6edd85e609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f6eddb47133 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f6ed19a8700 (LWP 2681)): #0 0x7f6edd865376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f6ed1c375eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7f6ed1c371eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7f6edd85e609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f6eddb47133 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f6ed3fff700 (LWP 2677)): #0 0x7f6edc41d4dd in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6edc3cf8fa in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6edc3d029b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6edc3d04a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6ede10b65b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6ede0af87b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6eddec9442 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6edea45f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f6eddeca623 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f6edd85e609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f6eddb47133 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f6ed9c7c9c0 (LWP 2647)): [KCrash Handler] #4 0x7f6edda6b00b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x7f6edda4a859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7f6edde8ebd7 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6edde8dfe3 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x55c720272ed3 in ScreenPool::handleScreenRemoved (this=0x55c721653870, screen=0x55c721448d30) at /tmp/git-sources/plasma-workspace/shell/screenpool.cpp:438 #9 0x55c7202790a3 in QtPrivate::FunctorCall, QtPrivate::List, void, void (ScreenPool::*)(QScreen*)>::call (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x55c720272b1c , o=0x55c721653870, arg=0x7ffd1db60610) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152 #10 0x55c720278b7d in QtPrivate::FunctionPointer::call, void> (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x55c720272b1c , o=0x55c721653870, arg=0x7ffd1db60610) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185 #11 0x55c720277e1d in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x55c7214f2f00, r=0x55c721653870, a=0x7ffd1db60610, ret=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:418 #12 0x7f6ede0e7dfe in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f6ede488d66 in QGuiApplication::screenRemoved(QScreen*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7f6ede4bf1dc in QScreen::~QScreen() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f6ede4bf32d in QScreen::~QScreen() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f6ede46ebeb in QWindowSystemInterface::handleScreenRemoved(QPlatf
[plasmashell] [Bug 453151] New: Left-handed mouse setting changes to right-handed after being unplugged and cannot be changed back until reboot.
https://bugs.kde.org/show_bug.cgi?id=453151 Bug ID: 453151 Summary: Left-handed mouse setting changes to right-handed after being unplugged and cannot be changed back until reboot. Product: plasmashell Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Input Method Assignee: plasma-b...@kde.org Reporter: kea...@hotmail.co.uk CC: aleix...@kde.org Target Milestone: 1.0 SUMMARY In plugging and plugging back in a left-handed mouse causes the buttons to switch to right-handed, and then cannot be changed back until a reboot STEPS TO REPRODUCE 1. Switch mouse settings to left-handed 2. unplug then replug the mouse OBSERVED RESULT the mouse has been switch back to right-handed and the settings no longer do anything EXPECTED RESULT the mouse buttons remain in left-handed mode SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.17.4-arch1-1 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Bug is also present on previous versions on KDE Plasma -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453151] Left-handed mouse setting changes to right-handed after being unplugged and cannot be changed back until reboot.
https://bugs.kde.org/show_bug.cgi?id=453151 --- Comment #1 from Ryan --- possibly similar to Bug 435113 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Ryan changed: What|Removed |Added Ever confirmed|1 |0 Status|RESOLVED|REPORTED Resolution|FIXED |--- --- Comment #117 from Ryan --- Not fixed for me on 5.25.5 (mouse returning to right-hand mode after unplugging and plugging back in) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442501] New: Brushes stopped working. I saved my work, closed the program and reopened it, and the brushes still did not work. My key bindings also stopped working.
https://bugs.kde.org/show_bug.cgi?id=442501 Bug ID: 442501 Summary: Brushes stopped working. I saved my work, closed the program and reopened it, and the brushes still did not work. My key bindings also stopped working. Product: krita Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: venusvantas...@gmail.com Target Milestone: --- SUMMARY Brushes stopped working. I saved my work, closed the program and reopened it, and the brushes still did not work. My key bindings also stopped working. STEPS TO REPRODUCE 1. save work. 2. close program. 3. reopen program OBSERVED RESULT Problem continued. EXPECTED RESULT Problem discontinues. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.12.8 ADDITIONAL INFORMATION Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.14393 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429834] Panel and windows flickering
https://bugs.kde.org/show_bug.cgi?id=429834 Ryan changed: What|Removed |Added CC||byanbyanror...@yahoo.com --- Comment #8 from Ryan --- Debian Bullseye user here. Just installed elisa for the first time with sudo apt install elisa --install recommends and upon first run it is constantly flickering. Not a KDE/plasma user, I just use OpenBox. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429834] Panel and windows flickering
https://bugs.kde.org/show_bug.cgi?id=429834 --- Comment #9 from Ryan --- sorry for that last comment, I thought I was looking at elisa bugzilla -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429834] Panel and windows flickering
https://bugs.kde.org/show_bug.cgi?id=429834 Ryan changed: What|Removed |Added CC|byanbyanror...@yahoo.com| -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439820] New: Antialiasing broken in Windows Store version.
https://bugs.kde.org/show_bug.cgi?id=439820 Bug ID: 439820 Summary: Antialiasing broken in Windows Store version. Product: okular Version: 20.12.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: rj.amdphr...@gmail.com Target Milestone: --- Created attachment 140039 --> https://bugs.kde.org/attachment.cgi?id=140039&action=edit screenshot of store vs chocolatey SUMMARY Antialiasing broken in Windows Store version. STEPS TO REPRODUCE 1. Install via Windows Store, and again via Chocolatey. 2. Open PDF 3. Compare 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 Not tested with other file formats. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Ryan changed: What|Removed |Added CC||ryangood...@protonmail.com --- Comment #217 from Ryan --- Something I have noticed that I haven't sen mentioned is that the "lines" are actually more like "tears" in the program. On a large monitor I notice my wallpaper pattern in the "lines". I am using Kubuntu 20.04, 4k monitor, 125% scaling, problems in Konsole and Kate. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435401] New: Wacom Art Pen Rotation half-way unresponsive
https://bugs.kde.org/show_bug.cgi?id=435401 Bug ID: 435401 Summary: Wacom Art Pen Rotation half-way unresponsive Product: krita Version: 4.4.2 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: ryancor...@yahoo.com Target Milestone: --- SUMMARY The Wacom Art pen has the ability to change brush orientation by rotating its barrel. In Krita, only half a rotation (180 degrees) is registered, while the other half remains unresponsive. This bug only happens in Krita and on the linux version. Windows version is fine. STEPS TO REPRODUCE 1. Select the 'Bristles-2_Flat_Rough' brush preset. 2. In 'edit brush settings', change rotation from 'drawing angle' to 'rotation'. 3. Spin the Wacom Art pen on the canvas. OBSERVED RESULT Half a rotation of the Art Pen translates as a complete rotation(360 degrees) of brush tip(should be 180 degrees). Any further rotation beyond the 180 degrees results in no change to brush tip rotation. EXPECTED RESULT Rotation of art pen correlates to accurate rotation of the brush tip, and is completely responsive at all angles. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435401] Wacom Art Pen Rotation half-way unresponsive
https://bugs.kde.org/show_bug.cgi?id=435401 ryan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from ryan --- Disabling the option 'share curve across all settings' in the brush settings enables full and accurate rotation for the Art Pen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475864] Error on switch from yandex browser to desktop
https://bugs.kde.org/show_bug.cgi?id=475864 Ryan changed: What|Removed |Added CC||jenkinsr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475864] Error on switch from yandex browser to desktop
https://bugs.kde.org/show_bug.cgi?id=475864 --- Comment #7 from Ryan --- Created attachment 164766 --> https://bugs.kde.org/attachment.cgi?id=164766&action=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 This may not be useful System has 3 monitors (2560x1440, DVI, DP, HDMI) driven by a nvidia 1660Super. System was working as expected, then I put the system to sleep for a few hours. When I turned it back on and logged in, the plasma shell stopped responding. I cloud move the mouse, however I could not switch to any of the open applications ( Konsole, Google Chrome x3 and Visual Studio Code). sav sa After about 30 seconds the system recovered, however, my monitor setup had changed. My primary monitor is different, and all panel and widgets have moved between the 3 different monitors. The left, center and right monitor layout did not change ( I can move the mose correctly from the left to center to right montor), just the panels are now in a different montor than they were configured for. This occurs each time I resume from sleep. I've not yet tried to resume from hibernate. -- Backtrace (Reduced): #4 0x7fca4c9be3d0 in QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fca4c9be446 in QSGAreaAllocator::deallocate(QRect const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #10 0x7fca4ca67c09 in QQuickWindowPrivate::runAndClearJobs(QList*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #2 0x7fca4aad1a2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #2 0x7fca4aad1a2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 479760] New: Process becomes uninterruptable; requires forced reboot
https://bugs.kde.org/show_bug.cgi?id=479760 Bug ID: 479760 Summary: Process becomes uninterruptable; requires forced reboot Classification: Applications Product: kate Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: jryan.dani...@gmail.com Target Milestone: --- SUMMARY While working with Kate, some open sessions may become frozen. Trying to kill the frozen sessions does not work. Looking at the 'properties' with system monitor shows that they are uninterruptable. Attempting to reboot/shutdown the computer does not complete. I need to hold the power button to get the computer to reboot/shutdown (I am assuming the uninterruptable kate session prevents the computer from shutting down). STEPS TO REPRODUCE 1. Open Kate, start a session from the session manager window. 2. Work. 3. Session (sometimes) freezes. OBSERVED RESULT Session becomes uninterruptable. EXPECTED RESULT No freeze or that the session can be killed if it does freeze. SOFTWARE/OS VERSIONS snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/stable refresh-date: 18 days ago, at 22:30 CET channels: latest/stable:23.08.4 2023-12-10 (171) 276MB classic latest/candidate: 23.08.4 2023-12-09 (171) 276MB classic latest/beta: ↑ latest/edge: ↑ installed: 23.08.4(171) 276MB classic ADDITIONAL INFORMATION My home user directory is a zfs pool mounted inside the /home dir. I am accessing text files on an external drive (zpool) mounted inside my user home directory So it is a zfs pool mounted inside another zfs pool. I would guess that this may have something to do with the issue but it is a guess. I bring zfs up because in the past I have had problems shutting down when zfs would not unmount/export/whatever-it-does-at-shutdown and I could not power down. I don't know if zfs is stuck because of kate or if kate is stuck for some other reason. No other snaps /apps have produced similar issues to date. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 479760] Process becomes uninterruptable; requires forced reboot
https://bugs.kde.org/show_bug.cgi?id=479760 --- Comment #1 from Ryan --- OS: Ubuntu 23.10 x86_64 Host: ASUS TUF Gaming A15 FA506IH_FA506IH 1.0 Kernel: 6.5.0-14-generic Uptime: 4 hours, 20 mins Packages: 2264 (dpkg), 70 (snap) Shell: bash 5.2.15 Resolution: 1920x1080 WM: sway Terminal: kitty CPU: AMD Ryzen 7 4800H with Radeon Graphics (16) @ 2.900GHz GPU: AMD ATI 05:00.0 Renoir GPU: NVIDIA 01:00.0 NVIDIA Corporation TU117M [NOT IN USE] Memory: 37176MiB / 39516MiB -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #11 from Ryan --- Created attachment 160442 --> https://bugs.kde.org/attachment.cgi?id=160442&action=edit performance settings All my settings are standard except for key bindings set to photoshop. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 Ryan changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472576] New: Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows.
https://bugs.kde.org/show_bug.cgi?id=472576 Bug ID: 472576 Summary: Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows. Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rcavit...@gmail.com Target Milestone: --- Created attachment 160501 --> https://bugs.kde.org/attachment.cgi?id=160501&action=edit That isn't Touhou! SUMMARY *** So I've noticed this on both my main PC and my Steam Deck, but when Touhou 17 is installed and an application does not have its own icon, it will be assigned Touhou 17's icon instead rather than a generic X.org icon. *** STEPS TO REPRODUCE 1. Own Touhou 17 via Steam and have it installed. 2. Open a window which does not have its own icon? I can reproduce this reliably by using a Chromium-based web browser to pop out a video in a floating window (see attachment). OBSERVED RESULT It's all Touhou EXPECTED RESULT Generic X.org icon assigned to windows. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION As given away above, this does happen on X11, I will test on Wayland too and see if the behavior is the same. I will edit this bug report (if possible) or add a comment with the results of that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472576] Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows.
https://bugs.kde.org/show_bug.cgi?id=472576 --- Comment #2 from Ryan --- Nvidia and Wayland are not on speaking terms right now, so I can't confirm this on Wayland currently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472576] Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows.
https://bugs.kde.org/show_bug.cgi?id=472576 --- Comment #3 from Ryan --- (In reply to Fushan Wen from comment #1) > Can you run `ls -al ~/.local/share/applications` and post the output here ``` total 62 drwxr-xr-x 3 ryan ryan 8192 Jul 11 13:25 . drwxr-xr-x 70 ryan ryan 3452 Jul 24 09:47 .. -rwxr-xr-x 1 ryan ryan 175 May 26 20:01 'Borderlands 3.desktop' -rwxr-xr-x 1 ryan ryan 580 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Database Compare.desktop' -rwxr-xr-x 1 ryan ryan 616 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Office Language Preferences.desktop' -rwxr-xr-x 1 ryan ryan 622 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Office Upload Center.desktop' -rwxr-xr-x 1 ryan ryan 642 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Skype for Business Recording Manager.desktop' -rwxr-xr-x 1 ryan ryan 585 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Spreadsheet Compare.desktop' -rwxr-xr-x 1 ryan ryan 666 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Telemetry Dashboard for Office.desktop' -rwxr-xr-x 1 ryan ryan 687 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Telemetry Log for Office.desktop' -rwxr-xr-x 1 ryan ryan 548 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Access.desktop -rwxr-xr-x 1 ryan ryan 556 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Excel.desktop -rwxr-xr-x 1 ryan ryan 615 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Microsoft OneDrive.desktop' -rwxr-xr-x 1 ryan ryan 554 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-OneNote 2016.desktop' -rwxr-xr-x 1 ryan ryan 551 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Outlook.desktop -rwxr-xr-x 1 ryan ryan 574 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-PowerPoint.desktop -rwxr-xr-x 1 ryan ryan 558 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Publisher.desktop -rwxr-xr-x 1 ryan ryan 605 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Skype for Business.desktop' -rwxr-xr-x 1 ryan ryan 567 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Word.desktop -rwxr-xr-x 1 ryan ryan 174 May 20 08:22 'Dead Space.desktop' -rwxr-xr-x 1 ryan ryan 175 Apr 15 20:26 'Evolution RTS.desktop' -rwxr-xr-x 1 ryan ryan 175 May 1 16:55 'Factorio Demo.desktop' -rwxr-xr-x 1 ryan ryan 171 Feb 17 20:47 Frostpunk.desktop -rw-r--r-- 1 ryan ryan 340 Apr 5 21:22 iDrive-Test.desktop -rwxr-xr-x 1 ryan ryan 170 Apr 5 17:41 'Just Cause 2.desktop' -rwxr-xr-x 1 ryan ryan 174 Mar 24 15:53 'Just Cause 3.desktop' -rwxr-xr-x 1 ryan ryan 182 Mar 30 17:08 'Kerbal Space Program.desktop' -rw-r--r-- 1 ryan ryan 1040 Apr 23 07:22 mimeinfo.cache -rw-r--r-- 1 ryan ryan 479 Jul 3 18:33 ModOrganizer-steamtinkerlaunch-dl.desktop-off -rw-r--r-- 1 ryan ryan 486 Jul 3 18:27 ModOrganizer-steamtinkerlaunch-dl.desktop-old -rwxr-xr-x 1 ryan ryan 174 Apr 5 18:10 'Pathologic 2.desktop' -rwxr-xr-x 1 ryan ryan 163 Apr 15 20:07 'Quake II RTX.desktop' -rwxr-xr-x 1 ryan ryan 168 Jun 9 20:33 'RAGE 2.desktop' -rwxr-xr-x 1 ryan ryan 162 Jun 9 20:33 RAGE.desktop -rwxr-xr-x 1 ryan ryan 174 Apr 5 18:10 'Rebel Galaxy.desktop' -rwxr-xr-x 1 ryan ryan 173 May 1 20:39 Retrowave.desktop -rwxr-xr-x 1 ryan ryan 178 Jul 1 20:23 'SONG OF HORROR.desktop' -rwxr-xr-x 1 ryan ryan 174 Apr 5 18:43 'Space Colony.desktop' -rwxr-xr-x 1 ryan ryan 191 Apr 29 15:36 'S.T.A.L.K.E.R. Call of Pripyat.desktop' -rwxr-xr-x 1 ryan ryan 185 Apr 29 15:36 'S.T.A.L.K.E.R. Clear Sky.desktop' -rwxr-xr-x 1 ryan ryan 193 Apr 29 15:37 'S.T.A.L.K.E.R. Shadow of Chernobyl.desktop' -rwxr-xr-x 1 ryan ryan 180 May 29 11:32 'Starpoint Gemini 2.desktop' -rwxr-xr-x 1 ryan ryan 214 Jul 11 13:25 'Touhou Kikeijuu ~ Wily Beast and Weakest Creature..desktop' -rw--- 1 ryan ryan 8168 Apr 24 20:35 vivaldi-stable.desktop -rw-r--r-- 1 ryan ryan 517 Jul 3 18:36 vortex-steamtinkerlaunch-dl.desktop drwxr-xr-x 3 ryan ryan 3452 Jul 3 17:29 wine -rw-r--r-- 1 ryan ryan 202 Apr 23 07:22 wine-extension-chm.desktop -rw-r--r-- 1 ryan ryan 209 Apr 23 07:22 wine-extension-gif.desktop -rw-r--r-- 1 ryan ryan 204 Apr 23 07:22 wine-extension-hlp.desktop -rw-r--r-- 1 ryan ryan 202 Apr 23 07:22 wine-extension-htm.desktop -rw-r--r-- 1 ryan ryan 216 Apr 23 07:22 wine-extension-ini.desktop -rw-r--r-- 1 ryan ryan 212 Apr 23 07:22 wi
[plasmashell] [Bug 472576] Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows.
https://bugs.kde.org/show_bug.cgi?id=472576 --- Comment #5 from Ryan --- (In reply to Fushan Wen from comment #4) > Can you post the content of 'Touhou Kikeijuu ~ Wily Beast and Weakest > Creature..desktop' in that folder? [Desktop Entry] Name=Touhou Kikeijuu ~ Wily Beast and Weakest Creature. Comment=Play this game on Steam Exec=steam steam://rungameid/1079160 Icon=steam_icon_1079160 Terminal=false Type=Application Categories=Game; -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 --- Comment #11 from Ryan --- (In reply to Dmitry Kazakov from comment #9) > Hi, Ryan! > > By "recording" I meant not "recording of your fingers", but recording of > your screen (via, e.g., OBS Studio) :) You can actually also summon the > on-screen-keyboard so we could see what keys are pressed at the moment. That > is needed so we could see how Krita reacts to your shortcuts and what > actually happens. > > It might also be a good idea to reset your Krita configurations. Try to move > these files/folders into some safe space: > > %LOCALAPPDATA%\kritarc > %APPDATA%\krita\input > > There used to be some bugs that could cause clashes with shortcuts during > some of updates of Krita No offense, but how is a screen recording supposed to show anything when the keyboard shortcuts do not work and are not visible? You're just going to be staring at a fixed frame the entire video and/or listening to me gripe. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 --- Comment #12 from Ryan --- (In reply to Dmitry Kazakov from comment #9) > Hi, Ryan! > > By "recording" I meant not "recording of your fingers", but recording of > your screen (via, e.g., OBS Studio) :) You can actually also summon the > on-screen-keyboard so we could see what keys are pressed at the moment. That > is needed so we could see how Krita reacts to your shortcuts and what > actually happens. > > It might also be a good idea to reset your Krita configurations. Try to move > these files/folders into some safe space: > > %LOCALAPPDATA%\kritarc > %APPDATA%\krita\input > > There used to be some bugs that could cause clashes with shortcuts during > some of updates of Krita It was a fresh install of Krita from Microsoft App Store. Yeah, I paid for the store version bc I like the software. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475421] New: Dynamic Wallpaper Plugin Broken
https://bugs.kde.org/show_bug.cgi?id=475421 Bug ID: 475421 Summary: Dynamic Wallpaper Plugin Broken Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: rcavit...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 162184 --> https://bugs.kde.org/attachment.cgi?id=162184&action=edit Dynamic Wallpapers settings menu is blank SUMMARY *** Starting a few weeks ago, the Dynamic Wallpapers plugin seems to be totally broken. I noticed this initially when my wallpaper displayed as just a black screen, and upon attempting to reset my dynamic wallpaper to see if it'd reload I noticed that the plugin itself is broken. *** STEPS TO REPRODUCE 1. Attempt to set a dynamic wallpaper 2. Observe that the menu for it is broken. OBSERVED RESULT The settings menu for the Dynamic Wallpapers plugin is broken (blank, there's no option to select a dynamic wallpaper), and the plugin itself seems broken as the previously set wallpaper failed to display upon the breaking of the plugin. EXPECTED RESULT To be able to configure and select a dynamic wallpaper. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION I am running the open source version of the Nvidia kernel module, though I imagine even if that broke displaying the actual wallpapers the settings menu for it would still function? This is on X11, I have not tested on Wayland given the state of affairs that still exists between Wayland and Nvidia's drivers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] New: Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 Bug ID: 471294 Summary: Pan tool shortcuts not working Classification: Applications Product: krita Version: 5.1.5 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: rj.amdphr...@gmail.com Target Milestone: --- SUMMARY Pan tool does not work via its default shortcuts (Space + leftclick, and middleclick). STEPS TO REPRODUCE 1. Open Krita 2. Open big document 3. Try to navigate. OBSERVED RESULT The mouse cursor does not change from the currently-selected tool EXPECTED RESULT Mouse cursor changes, and can pan. SOFTWARE/OS VERSIONS Windows: 11 Stable ADDITIONAL INFORMATION Installed via Microsoft Windows Store -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471295] New: Zoom tool zooms in while zoom out is selected
https://bugs.kde.org/show_bug.cgi?id=471295 Bug ID: 471295 Summary: Zoom tool zooms in while zoom out is selected Classification: Applications Product: krita Version: 5.1.5 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: rj.amdphr...@gmail.com Target Milestone: --- SUMMARY Zoom tool always zooms in, even when Ctrl is held. The mouse cursor changes to a minus sign, but the tool still zooms in, instead of zooming out. STEPS TO REPRODUCE 1. Open Krita 2. 3. OBSERVED RESULT Zoom in EXPECTED RESULT Zoom out. 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.
[krita] [Bug 471295] Zoom tool zooms in while zoom out is selected
https://bugs.kde.org/show_bug.cgi?id=471295 --- Comment #1 from Ryan --- Windows 11 stable -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 --- Comment #2 from Ryan --- 1. I didn't change anything. 2. It is in fact set to those things. 3. There are more bugs than just this with the shortcuts. Zoom doesn't work either. Using the Zoom tool itself is also bugged: it only zooms in, never out. I have to set the Zoom factor in the bottom right control in the window. Ryan Johnson | 🔗My Profile<https://linkr.bio/AMDphreak> | GSO<https://www.germantownsymphony.org> member, FSF, EFF supporter From: sh_zam Sent: Wednesday, June 21, 2023 8:45 AM To: rj.amdphr...@gmail.com Subject: [krita] [Bug 471294] Pan tool shortcuts not working https://bugs.kde.org/show_bug.cgi?id=471294 sh_zam changed: What|Removed |Added Keywords||triaged CC||sh...@sdf.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from sh_zam --- Hi! Can you check if the Canvas Input Profile (Settings -> Configure Krita) has these shortcut assigned to Pan Canvas action (check if you are using Krita Default profile/or something else that you made yourself). If it is assigned, and it still doesn't work, can you please share the file in C:\Users\\AppData\Roaming\krita\input corresponding to the profile name that is active. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 --- Comment #6 from Ryan --- A video recording of a keyboard shortcut not working? I can give you logs if you tell me what to give you. You can't just trust that I know when my finger is typing? I have a WPM of over 100, and a computer science degree, and have been using programs since 1997. I think I know when a keyboard shortcut isn't working. Especially when other keyboard shortcuts are working in the same program. I had a problem with another software like this, due to AMD Software Adrenalin Edition capturing the key combinations, however those shortcuts have been disabled in AMD Software, and the other application now responds appropriately. I don't have any other applications that capture keyboard input running in the background. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jun 22, 2023 at 9:47 AM Dmitry Kazakov wrote: > https://bugs.kde.org/show_bug.cgi?id=471294 > > Dmitry Kazakov changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > CC||dimul...@gmail.com > Status|REPORTED|NEEDSINFO > > --- Comment #5 from Dmitry Kazakov --- > Hi, Ryan! > > Could you please make a video recording of the problem? I cannot reproduce > it > here. > > It would also be helpful if you could try the nightly build of Krita from > here: > > https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/lastSuccessfulBuild/artifact/krita-nightly-x64-5.2.0-prealpha-6d578e3bbb.zip > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] New: Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 Bug ID: 472120 Summary: Move tool reverts previous transform operation Classification: Applications Product: krita Version: 5.1.4 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: rocif...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Paste an image as a new layer into a blank document 2. Ctrl+T free transform the layer, drag the corner to resize it to roughly 50% smaller in width and height. Press enter to commit the transform. Optional: wait for the progress bar in the layers window to finish (this does not significantly affect the reproduction steps). 3. Press keyboard shortcut for move tool (V in photoshop hotkeys) and drag the layer to move it OBSERVED RESULT At least 50% of the time the pixels in the layer revert to before step 2 was committed, the layer is the original size. It can be observed in many ways that this is real pixel data and not a rendering artifact. I cannot find any surefire way to reproduce this every time, but if the keyboard shortcuts are used quickly then it (frustratingly) happens almost every time. EXPECTED RESULT The layer should move with the mouse and the previous transform should have been permanent, ie. the layer should remain around 50% of the original size and not resize at all when moved. SOFTWARE/OS VERSIONS Windows: 10 Mac OSX ADDITIONAL INFORMATION The behaviour is consistent between windows and mac (multiple os versions) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 Ryan changed: What|Removed |Added CC||rocif...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #1 from Ryan --- Created attachment 160219 --> https://bugs.kde.org/attachment.cgi?id=160219&action=edit reproduction steps instead of reduction by 50% this video increases the size of the truck layer. on the instant the canvas is clicked with the move tool, it reverts its size to before it was transformed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #2 from Ryan --- Note: I have built krita from the latest master branch locally and I have sofar been unable to reproduce this problem. does anyone know if it was addressed intentionally as a fix recently? I will keep this posted, if I don't then I haven't been able to reproduce it as I use the latest version daily. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #3 from Ryan --- I reproduced it on latest master (splash screen says 5.2.0 prealpha). Once I did this enough times on enough layers it just started happening almost every time. (around 30 times on 40+ layers) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #7 from Ryan --- Sure. I didn't think to try those options. It seems to happen consistently if I have it set to Accurate with Instant Preview. If I set it to the other 2 options then it doesn't happen. I have recorded all options and used undo between each one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #8 from Ryan --- Created attachment 160327 --> https://bugs.kde.org/attachment.cgi?id=160327&action=edit full screen reproduction all transform tool modes -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] New: Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 Bug ID: 463135 Summary: Keyboard keys lose focus/stop working. Classification: Applications Product: krita Version: 5.1.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ryans...@yahoo.com Target Milestone: --- SUMMARY Ever since the release of Krita 5, the keyboard keys will periodically stop responding. For instance, I will be painting and selecting a color or panning a canvas, and all of a sudden it won't work anymore. It's getting progressively worse with each new release. It seems to happen randomly, but it might be triggered when another app does something significant while painting, like a browser changing a song, or playing a new video automatically. In 5.0.2, Krita would occasionally lose keyboard input, however, changing a brush or alt tabbing would regain focus. In the newer version of Krita, this solution to regain focus seems to be less effective and aggressive alt tabbing/program switching is required. Switching brushes doesn't seem to work anymore. STEPS TO REPRODUCE 1. Start krita 2. Paint in krita OBSERVED RESULT Eventually, keyboard keys no longer work. EXPECTED RESULT Keyboard keys always respond. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I've reinstalled my operating system multiple times since version 5 of Krita has been released, and in every iteration this problem remains. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #2 from ryan --- (In reply to Halla Rempt from comment #1) > Can you check whether this is also the case with the appimage, or only with > your distribution packages? I've tested and found this issue with all versions, as I have been wanting to move beyond 5.0.2 for awhile now. I believe I have found what triggers the issue. If I test the program with the default Canvas Input Settings, everything seems to work well. However, if I change the alternate invocation to 'alt+left button' (sample foreground color from merged image) and change primary setting to 'ctrl+alt+left button' (brush size), the issue starts. I also remove all other actions in alternate invocation that would conflict with this setup. Basically I change the keys for resize brush and color picker away from defaults which trigger the issue. All I did was change these settings and start painting. Within minutes of panning, selecting brushes, using the above hotkeys, and doing it in a random order, the problem manifests. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #4 from ryan --- I may have isolated a part of the issue. While using the changes to the Canvas Input Settings that I've discussed already, press and hold the key to sample the canvas color (alt) and then select a brush from the brush preset window. While still holding the alt-key, left click on the canvas. You can now let go of alt. The effect will be that you can no longer use the alt-key. The default settings seem to not be affected by this bug. While this is similar to the issue I am experiencing, this particular method still allows one to use other keys like the spacebar for panning the canvas. The problem I originally described doesn't even allow one to use the spacebar, so I'm still unsure of how that bug comes about, but the cause might be related. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #5 from ryan --- After further testing, I believe the subject of my last reply is the issue. I tested version 5.1.5 and I can see that I lose function of the keyboard until I select another brush. I'm unsure why I was still able to before. It seems that the alt key is the only modifier that will cause the keyboard to lock-up. There is also no need to change any settings as I discovered that the alt key is what triggers the issue, regardless of what is bound to it. Again, the steps to reproduce the bug is: while holding the alt key, select a different brush and then click the canvas window. Let go of the alt key and try to use the keyboard (also affects mouse). You can resolve the bug by selecting a new brush or by clicking on a different window (layers, toolbox, etc). While I have discovered the problem, this bug is probably not something a lot of people experience because it takes human error to even bring it out (selecting a brush while holding a modifier key), and then it also takes someone who doesn't use the default bindings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #6 from ryan --- In addition, there is a small window of time where if one presses the alt key after selecting a brush and then left clicks the canvas, that the same bug will appear. In my instance, since I often select color right after selecting a brush, I see this bug a lot. I actually think this is how I am triggering the bug rather than when pressing the alt key during brush selection. There is one little bit information that may help, if you press the alt key after selecting a brush, and then wait for the color picker icon to appear, then it becomes safe to left click to sample a color. If done before the transition, the keyboard keys will become stuck. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 447957] New: Sendcode integration on sublime text
https://bugs.kde.org/show_bug.cgi?id=447957
Bug ID: 447957
Summary: Sendcode integration on sublime text
Product: rkward
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: R Console
Assignee: rkward-de...@kde.org
Reporter: jryan.dani...@gmail.com
Target Milestone: ---
SUMMARY
I am trying to find a replacement for Rstudio as I am now on sway (wayland) on
Ubuntu 22.04 and Rstudio does not support wayland.
RKWard seems to work well so far but I cannot send R code from sublime text to
RKWard.
Is there something I can do to get this up and running?
STEPS TO REPRODUCE
1. I installed rkward from the apt repo.
2. I have added the following to my 'sendcode' settings in sublime text, in the
hope that it would that simple:
"R": { "bracketed_paste_mode": false, "prog": "rkward", }, "rmd" : { "prog":
"rkward", "bracketed_paste_mode": false },
OBSERVED RESULT
I get an error message "rkward is not supported for current syntax'.
EXPECTED RESULT
The code from sublime text is magically transported to the RKWard R console and
the code runs.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
Linux 5.15.0-14-generic #14-Ubuntu SMP Tue Dec 14 10:08:09 UTC 2021 x86_64
GNU/Linux
Sublime text build 4126
RKWard v0.7.2
--
You are receiving this mail because:
You are watching all bug changes.
[rkward] [Bug 447957] Sendcode integration on sublime text
https://bugs.kde.org/show_bug.cgi?id=447957 --- Comment #2 from Ryan --- Hello Thomas Thank you for the super quick response! I had a look as well and it seems do-able. I have filed a feature request with Sendcode. I can see possible complication that might change the process for Sendcode on wayland: - using ydotool instead of xdotool - the change in clipboard management utils on wayland - granting privileges to GUIs on sway Unfortunately I have just moved everything from x to wayland and I am still putting out all the fires that come with that to get my desktop in working order so I don't want to be too adventurous with new projects. For the time being I can use the terminal and sublime text. *Best Wishes* Ryan Daniels On Wed, 5 Jan 2022 at 03:23, Thomas Friedrichsmeier < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=447957 > > Thomas Friedrichsmeier changed: > >What|Removed |Added > > > CC| > |thomas.friedrichsmeier@kdem >||ail.net > > --- Comment #1 from Thomas Friedrichsmeier < > thomas.friedrichsme...@kdemail.net> --- > I am not familiar with sublime text / sendcode (*), but had look at some > of the > documentation just now. It seems sendcode needs specific instructions for > each > program it has to deal with, even though, at least on linux, most programs > could really be treated alike. > > After a cursory look, it appears you'll essentially have to duplicate this > part > (wherever that gets installed): > > https://github.com/randy3k/SendCode/blob/master/code_sender/rstudio/__init__.py > > At least for linux, no special adjustments should be needed, here. You > might > want to send "Alt+1", then "Alt+5" before "Ctrl+V" to make sure the R > Console > window is active inside RKWard. > > Apparently, you'll also have to add a few lines, here: > https://github.com/randy3k/SendCode/blob/master/code_sender/sender.py > again taking the lines for rstudio as a template. > > If that works for you, consider contributing it to sendcode. I am not sure, > whether anything special is needed to support sendcode to RKWard on > Windows/OS > X, but at least for linux, it's the support inside sendcode, not inside > RKWard > that is missing. > > --- > > (*) Consider giving the integrated editor a try. It's based on kate(part), > which provides a really powerful text editing component. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 446784] New: Calendar sources window only half displayed when Kalendar minimised or at lower resolutions
https://bugs.kde.org/show_bug.cgi?id=446784 Bug ID: 446784 Summary: Calendar sources window only half displayed when Kalendar minimised or at lower resolutions Product: kalendar Version: 0.3.1 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: im_drac...@hotmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 144431 --> https://bugs.kde.org/attachment.cgi?id=144431&action=edit Kalendar sources display issue 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 *** When opening kalendar sources from settings it only shows the sources from openchange to the bottom of the dialog. In order to view the rest of the window you must click and drag the dialog from one of the menu items. STEPS TO REPRODUCE 1. open Kalendar (not fullscreen) in an X11 session 2. go to settings -> configure kalendar -> calendar sources 3. click 'add new calendar source' and note the dialog is only half displayed as mentioned above OBSERVED RESULT calendar sources dialog half displayed EXPECTED RESULT calendar sources dialog displayed in full SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 35 x86_64 kernel: 5.15.7 (Koji) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I am running Kalendar via XWayland (e.g. `QT_QPA_PLATFORM=xcb kalendar` from the exec line in a copy of the .desktop file) I am running KDE frameworks from marcdeop/kf5 copr repo (KDE SIG copr repo) I have marcdeop/plasma repo enabled also (although plasma 5.23.3 is from distro packages) -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 446784] Calendar sources window only half displayed when Kalendar minimised or at lower resolutions
https://bugs.kde.org/show_bug.cgi?id=446784 --- Comment #1 from Ryan --- I have cleared the kalendar cache, it doesn't fix the problem. I have also tested in a freshly installed Fedora 35 vm using the kalendar rpm install (should be in stable packages now, although at the time it was from updates-testing) -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 421802] menu bar goes missing after using rdp for a while
https://bugs.kde.org/show_bug.cgi?id=421802 Ryan changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Ryan --- I believe this issue is resolved now, I haven't witnessed it in recent times. Also Fedora 32 is long past end of life. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Ryan changed: What|Removed |Added CC||r...@rschanz.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem tem
https://bugs.kde.org/show_bug.cgi?id=449021 Ryan changed: What|Removed |Added CC||r...@rschanz.org --- Comment #13 from Ryan --- I'd like to also mention my experience and give any info if needed. I also experience this bug on a fully updated Arch system as well. I'm also not running NVIDIA graphics and am running the latest beta of plasma from the kde-unstable repo and experience this issue a few times per day, where it isn't resolved until I run `plasmashell --replace` from KRunner. The entire system seems responsive, like the task switcher, KRunner, and the desktop, just the panel and its applets (except the application menu) freezes. Also a dual monitor setup, I don't think I've experienced this issue on my purely 1 screen laptop, though I don't use it often enough to really justify that claim. I'll keep an eye out for it, maybe leave it running for a while to see if it ever crops up. SOFTWARE/OS VERSIONS: Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-arch1-1 Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U Memory: 17.6 GiB of RAM Graphics Processor: AMD Radeon Vega 10 Graphics -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 438300] New: Spectacle crashes after closing
https://bugs.kde.org/show_bug.cgi?id=438300 Bug ID: 438300 Summary: Spectacle crashes after closing Product: Spectacle Version: 21.04.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: im_drac...@hotmail.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (21.04.0) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.9-200.fc33.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.0 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: - What I was doing when the application crashed: took a screenshot, copied it to clipboard, closed spectacle then it threw the crash report The crash can be reproduced every time. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x7f2ace2d2b65 in kImageAnnotator::FontPicker::~FontPicker() () from /lib64/libkImageAnnotator.so.0 #5 0x7f2ace296535 in kImageAnnotator::AnnotationItemSettings::~AnnotationItemSettings() () from /lib64/libkImageAnnotator.so.0 #6 0x7f2ace2968d2 in kImageAnnotator::AnnotationWidget::~AnnotationWidget() () from /lib64/libkImageAnnotator.so.0 #7 0x7f2ace28c3fb in kImageAnnotator::CoreView::~CoreView() () from /lib64/libkImageAnnotator.so.0 #8 0x7f2ace28eb7d in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /lib64/libkImageAnnotator.so.0 #9 0x7f2ace28ed6d in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /lib64/libkImageAnnotator.so.0 #10 0x7f2acc78f93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #11 0x7f2acd23b246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #12 0x564ba9354b41 in KSWidget::~KSWidget() () #13 0x7f2acc78f93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #14 0x7f2acd23b246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #15 0x564ba935b6d5 in SpectacleCore::~SpectacleCore() () #16 0x564ba9351a22 in main () [Inferior 1 (process 155177) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430057] New: Plasma crashes when moving widget to a second monitor
https://bugs.kde.org/show_bug.cgi?id=430057 Bug ID: 430057 Summary: Plasma crashes when moving widget to a second monitor Product: plasmashell Version: 5.20.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: r...@interoctiv.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.3) Qt Version: 5.15.2 Frameworks Version: 5.76.0 Operating System: Linux 5.9.10-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Entered edit mode on the desktop and dragged the timer widget from one monitor to another (secondary-external to primary-laptop or the opposite direction). - Unusual behavior I noticed: The widget stopped moving when the window's leading edge reached the border between monitors. The widget disappeared, Plasma crashed then restarted. - Custom settings Both are high-DPI monitors (4k). The laptop monitor has 200% scaling. The external monitor has 150% scaling. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1544] [New LWP 1708] [New LWP 1722] [New LWP 1723] [New LWP 1724] [New LWP 1725] [New LWP 1784] [New LWP 1790] [New LWP 1791] [New LWP 1793] [New LWP 1817] [New LWP 1835] [New LWP 1836] [New LWP 1837] [New LWP 2368] [New LWP 2370] [New LWP 2532] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f61377556b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 [Current thread is 1 (Thread 0x7f61360ef840 (LWP 1500))] Thread 18 (Thread 0x7f611e0a0640 (LWP 2532)): #0 0x7f61377556b2 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61385c2dcb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f613a30a177 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55f64d6474b8) at /usr/include/qt5/QtCore/qdeadlinetimer.h:68 #3 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55f64d647420) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:936 #4 0x7f613a30c609 in QSGRenderThread::run() (this=0x55f64d647420) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1053 #5 0x7f61385bce51 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f613774f3e9 in start_thread () at /lib64/libpthread.so.0 #7 0x7f613821a943 in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f60aab97640 (LWP 2370)): #0 0x7f61377556b2 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61385c2dcb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f613a30a177 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55f640921ab8) at /usr/include/qt5/QtCore/qdeadlinetimer.h:68 #3 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55f640921a20) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:936 #4 0x7f613a30c609 in QSGRenderThread::run() (this=0x55f640921a20) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1053 #5 0x7f61385bce51 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f613774f3e9 in start_thread () at /lib64/libpthread.so.0 #7 0x7f613821a943 in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f60ab4ef640 (LWP 2368)): #0 0x7f61377556b2 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61385c2dcb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f613a30a177 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55f63a0365e8) at /usr/include/qt5/QtCore/qdeadlinetimer.h:68 #3 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55f63a036550) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:936 #4 0x7f613a30c609 in QSGRenderThread::run() (this=0x55f63a036550) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1053 #5 0x7f61385bce51 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f613774f3e9 in start_thread () at /lib64/libpthread.so.0 #7 0x7f613821a943 in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f60d55fc640 (LWP 1837)): #0 0x7f61377556b2 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61385c2dcb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f613a30a177 in
[neon] [Bug 490862] Kate 24.05.2 doesn't run: 'libpcre.so.3: cannot open shared object file: No such file or directory'
https://bugs.kde.org/show_bug.cgi?id=490862 --- Comment #10 from Ryan --- (In reply to chris.m.geroux from comment #9) > (In reply to Scarlett Moore from comment #8) > > please test the latest in --candidate There is no change for my side. I get the same error message as before. ``` /snap/kate/181/usr/bin/kate: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory ``` ``` snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/candidate refresh-date: today at 20:46 CEST channels: latest/stable:24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 24.08.0 2024-09-05 (181) 2GB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-21 (178) 2GB classic installed: 24.08.0(181) 2GB classic ``` -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 490862] Kate 24.05.2 doesn't run: 'libpcre.so.3: cannot open shared object file: No such file or directory'
https://bugs.kde.org/show_bug.cgi?id=490862 --- Comment #11 from Ryan --- (In reply to Ryan from comment #10) > (In reply to chris.m.geroux from comment #9) > > (In reply to Scarlett Moore from comment #8) > > > please test the latest in --candidate > > There is no change for my side. I get the same error message as before. > ``` > /snap/kate/181/usr/bin/kate: error while loading shared libraries: > libpcre.so.3: cannot open shared object file: No such file or directory > ``` > ``` > snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR > tracking: latest/candidate > refresh-date: today at 20:46 CEST > channels: > latest/stable:24.05.2 2024-08-04 (177) 2GB classic > latest/candidate: 24.08.0 2024-09-05 (181) 2GB classic > latest/beta: ↑ > latest/edge: 24.05.2 2024-08-21 (178) 2GB classic > installed: 24.08.0(181) 2GB classic > ``` Thank you for all the hard work! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 491892] New: Snap gui does not appear after system update
https://bugs.kde.org/show_bug.cgi?id=491892 Bug ID: 491892 Summary: Snap gui does not appear after system update Classification: Applications Product: kate Version: 23.08.5 Platform: Snap OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: jryan.dani...@gmail.com Target Milestone: --- SUMMARY After a routine system update (sudo apt update; sudo apt upgrade), my kate snap no longer launches the gui. STEPS TO REPRODUCE 1. Start kate from the launcher or terminal. 2. Nothing happens. 3. OBSERVED RESULT No GUI interface is presented. No windows open. Launching kate from the terminal produces not GUI either nor any error message. System monitor shows that kate is running as expected. I can run kate on CLI to show help or version. I can use the CLI (and launcher) to start other kate sessions, none of which will produce any GUI. Tested with swaywm and with gnome wayland. **I now cannot used either the candidate nor stable branch of kate.** EXPECTED RESULT Some GUI should launch. SOFTWARE/OS VERSIONS snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/stable refresh-date: today at 10:37 CEST channels: latest/stable:24.05.2 2024-08-04 (177) 2GB classic latest/candidate: 23.08.4 2023-12-09 (171) 276MB classic latest/beta: ↑ latest/edge: 24.05.2 2024-08-01 (177) 2GB classic installed: 23.08.4(171) 276MB classic OS: Ubuntu 24.04 LTS x86_64 Host: OptiPlex 7050 Kernel: 6.8.0-40-generic Uptime: 27 mins Packages: 2408 (dpkg), 9 (flatpak), 84 (snap) Shell: bash 5.2.21 Resolution: 3840x2160 WM: sway Terminal: kitty CPU: Intel i5-7600 (4) @ 4.100GHz GPU: Intel HD Graphics 630 GPU: AMD ATI Radeon HD 8830M / R7 250 / R7 M465X Memory: 3762MiB / 31958MiB -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489801] New: All Links Open in Firefox even though it is not my default Browser
https://bugs.kde.org/show_bug.cgi?id=489801 Bug ID: 489801 Summary: All Links Open in Firefox even though it is not my default Browser Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rcavit...@gmail.com Target Milestone: --- SUMMARY All links, no matter what, now open in Firefox even though it is not my default browser. If I uninstall Firefox, links will not open at all. STEPS TO REPRODUCE 1. Open link (Discord, shared via KDE Connect, etc) 2. Observe that it opens in Firefox even though it's not the default browser. OBSERVED RESULT Links open in Firefox, or they do not open at all if Firefox is not installed. EXPECTED RESULT Links open in my actually set default browser. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 490058] New: org.freedesktop.secrets DBus API
https://bugs.kde.org/show_bug.cgi?id=490058 Bug ID: 490058 Summary: org.freedesktop.secrets DBus API Classification: Frameworks and Libraries Product: frameworks-kwallet Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: r...@interoctiv.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY KWallet is not accessible to [JabRef](https://www.jabref.org/) reference manager, a Java application that uses the secrets service via sweisend/secret-service and pure-java/kdewallet. See details and troubleshooting attempts in the following bug reports: * https://github.com/JabRef/jabref/issues/11296 * https://github.com/swiesend/secret-service/pull/43 * https://github.com/javakeyring/java-keyring/issues/98 STEPS TO REPRODUCE 1. Install JabRef reference manager 2. Launch from the terminal to see error messages 3. Click File > Preferences > Web search in JabRef OBSERVED RESULT The terminal shows an exception: credential store not supported Custom API Key in JabRef preferences under Web Search shows no content and options are disabled because the credential store is not supported. EXPECTED RESULT JabRef uses org.freedesktop.secrets, which is supposed to be supported by kwallet, so I expect JabRef to be able to access the wallet and store credentials. I checked that the secrets service is running and that I can add keys to it. I also authorized JabRef by editing ~/.config/kwalletrc. I also added a service file in ~/.local/share/dbus-1/services/org.freedesktop.secrets.service (and restarted the service / rebooted the system) ``` [D-BUS Service] 4 │ Name=org.freedesktop.secrets 5 │ Exec=/usr/bin/kwalletd6 ``` SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240704 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION * https://bugs.kde.org/show_bug.cgi?id=313216 * https://github.com/JabRef -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 490058] KWallet is not accessible by an application using via org.freedesktop.secrets.service
https://bugs.kde.org/show_bug.cgi?id=490058 Ryan changed: What|Removed |Added Summary|org.freedesktop.secrets |KWallet is not accessible |DBus API|by an application using via ||org.freedesktop.secrets.ser ||vice -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 489629] Add AsciiDoc MIME-type icons to Breeze
https://bugs.kde.org/show_bug.cgi?id=489629 --- Comment #7 from Ryan --- (In reply to Nate Graham from comment #6) > No need to open an Issue there, just do merge request. Thanks Nate. My account is working now, and I think I will try some greyscale icons before making the merge request. I discovered that I somewhat miss the contrast between Dolphin's blue folders and white plain text icons. Many of the text MIME-types have a coloured icon, and this is nice too, but plain-text and markdown have black-and-white or grey icons, which might suit AsciiDoc too. -- You are receiving this mail because: You are watching all bug changes.
