[krita] [Bug 455420] New: This isn't exactly a bug, but could you please allow us to use the FFmpeg source code to export our animations please? Since I am a tablet user, I can't download FFmpeg, only
https://bugs.kde.org/show_bug.cgi?id=455420 Bug ID: 455420 Summary: This isn't exactly a bug, but could you please allow us to use the FFmpeg source code to export our animations please? Since I am a tablet user, I can't download FFmpeg, only the source code. Krita always tells me to download FFmpeg instead. Product: krita Version: 5.0.6 Platform: Android OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: renosk...@gmail.com Target Milestone: --- Created attachment 149808 --> https://bugs.kde.org/attachment.cgi?id=149808&action=edit Krita telling me it's preffered to download FFmpeg instead of using the source code. 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. Files 2. Render animation/video 3. FFmpeg source code OBSERVED RESULT FFmpeg source codes are not aloud. EXPECTED RESULT Source codes are aloud and I get to live happily with my animation. 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 455420] This isn't exactly a bug, but could you please allow us to use the FFmpeg source code to export our animations please? Since I am a tablet user, I can't download FFmpeg, only the
https://bugs.kde.org/show_bug.cgi?id=455420 --- Comment #2 from Owen --- Oh, that's alright then,I'll try to find a solution while you guys are at it. Thank you for listening to us,and do me a favour? Please tell me once you've fixed this. Thank you very much, enjoy the rest of your day/night. On Thu, 16 Jun 2022, 18:27 wolthera, wrote: > https://bugs.kde.org/show_bug.cgi?id=455420 > > wolthera changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > CC||griffinval...@gmail.com > Resolution|--- |LATER > > --- Comment #1 from wolthera --- > Hi, this is not allowed because you need to compile source code before it > can > be used by anything. The reason FFMpeg doesn't work on android is because > there's no version of FFMpeg for android. > > We're investigating what we can do to allow animation export on android, > but > there's no estimates for that (5.2 will allow animated webp and jpegxl > export, > but those won't get audio, we're still searching for an audio solution). We > will never be able to allow you to use the source code of ffmpeg on it's > own to > export animation, as that itself is technically impossible. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455931] New: When I try to form the sketch of the selected area, I go to the mesh form, of course, but for some reason most of the time when I try to control it, instead it rotates (this
https://bugs.kde.org/show_bug.cgi?id=455931 Bug ID: 455931 Summary: When I try to form the sketch of the selected area, I go to the mesh form, of course, but for some reason most of the time when I try to control it, instead it rotates (this happens to all the tool actions, apart from cage). Product: krita Version: 5.0.6 Platform: Android OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: renosk...@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. Make a selection area 2. Go to mesh form 3. Mesh the selected areas form to your will OBSERVED RESULT Instead, it rotates EXPECTED RESULT I can mesh it SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I'm a tablet user, if it concerns you. Thank you for your time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455931] When I try to form the sketch of the selected area, I go to the mesh form, of course, but for some reason most of the time when I try to control it, instead it rotates (this happe
https://bugs.kde.org/show_bug.cgi?id=455931 --- Comment #2 from Owen --- Yes,it does, but unfortunately the same thing happens when I use a stylus pen. It only rarely does as I desire. Also,I admire you putting in the effort to solve my problems,thank you very much. :) On Mon, 27 Jun 2022, 05:48 vanyossi, wrote: > https://bugs.kde.org/show_bug.cgi?id=455931 > > vanyossi changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > CC||ghe...@gmail.com > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from vanyossi --- > The user interface works as expected on desktop application using a mouse, > I > see you are using Android, does this happen when you use your fingers to > interact with the transform mesh? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455931] When I try to form the sketch of the selected area, I go to the mesh form, of course, but for some reason most of the time when I try to control it, instead it rotates (this happe
https://bugs.kde.org/show_bug.cgi?id=455931 --- Comment #4 from Owen --- Thank you so much for your time :D On Tue, 28 Jun 2022, 07:36 Bug Janitor Service, wrote: > https://bugs.kde.org/show_bug.cgi?id=455931 > > Bug Janitor Service changed: > >What|Removed |Added > > > Status|NEEDSINFO |REPORTED > Resolution|WAITINGFORINFO |--- > > --- Comment #3 from Bug Janitor Service --- > Thanks for your comment! > > Automatically switching the status of this bug to REPORTED so that the KDE > team > knows that the bug is ready to get confirmed. > > In the future you may also do this yourself when providing needed > information. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455931] When I try to form the sketch of the selected area, I go to the mesh form, of course, but for some reason most of the time when I try to control it, instead it rotates (this happe
https://bugs.kde.org/show_bug.cgi?id=455931 --- Comment #6 from Owen --- I can try to screenrecord it,tho I'm not sure how,I can try. I'll maybe be able to send it within the next hour or two. Thank you for your patience. On Tue, 28 Jun 2022, 11:24 sh_zam, wrote: > https://bugs.kde.org/show_bug.cgi?id=455931 > > --- Comment #5 from sh_zam --- > Hello! Can you please share the screen recording of this? As I can't > reproduce > this on my tablet. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455931] When I try to form the sketch of the selected area, I go to the mesh form, of course, but for some reason most of the time when I try to control it, instead it rotates (this happe
https://bugs.kde.org/show_bug.cgi?id=455931 --- Comment #7 from Owen --- I am very sorry,I have found the problem, I simply wasn't putting enough pressure on the screen. I am so so sorry for wasting your time. I found it out when I was recording my screen to send it to you. I'm am very sorry, I hope a misunderstanding like this won't happen again. Again,I am incredibly sorry. On Tue, 28 Jun 2022, 11:26 OwensDysphoria, wrote: > I can try to screenrecord it,tho I'm not sure how,I can try. I'll maybe be > able to send it within the next hour or two. Thank you for your patience. > > On Tue, 28 Jun 2022, 11:24 sh_zam, wrote: > >> https://bugs.kde.org/show_bug.cgi?id=455931 >> >> --- Comment #5 from sh_zam --- >> Hello! Can you please share the screen recording of this? As I can't >> reproduce >> this on my tablet. >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457700] New: Krita disables my pen
https://bugs.kde.org/show_bug.cgi?id=457700 Bug ID: 457700 Summary: Krita disables my pen Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: owenkit...@gmail.com Target Milestone: --- SUMMARY After about 30 minutes my renaisser pen will stop working and requires me to restart my laptop for it to work again. STEPS TO REPRODUCE 1. Use renaisser pen for about 30 min to an 1 hr OBSERVED RESULT Pen is completely disabled EXPECTED RESULT Pen should continue to work SOFTWARE/OS VERSIONS Windows: Yes ADDITIONAL INFORMATION I got a new renaisser pen not long after this issue and it still persisted, so I don't believe it is the pen malfunctioning The pen does not disable if I am not using krita. This issue did not happen for a couple months when I first got krita. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491153] New: When using two monitors, maximized XWayland applications do not reach the top of the screen for clicking
https://bugs.kde.org/show_bug.cgi?id=491153 Bug ID: 491153 Summary: When using two monitors, maximized XWayland applications do not reach the top of the screen for clicking Classification: Plasma Product: kwin Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: xwayland Assignee: kwin-bugs-n...@kde.org Reporter: o...@thegoulds.org Target Milestone: --- Created attachment 172200 --> https://bugs.kde.org/attachment.cgi?id=172200&action=edit Video of the issue SUMMARY Some applications cannot be clicked at the very top of the screen when maximized and using two monitors. STEPS TO REPRODUCE 1. Plug in a second monitor 2. Maximize an XWayland application on the primary monitor (in the video example, I use PrusaSlicer) 3. Click on the very top of the screen OBSERVED RESULT Clicking on the very top of the maximized app will instead click on what is behind it, like the desktop or another app. As well, the close, maximize, and minimize buttons do not reach to the top pixel when they normally do. EXPECTED RESULT Maximized applications should reach the top edge of the screen (which they do visually, just not for user interaction) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Not sure if it happens on all resolutions. For me, my primary monitor (on which the issue occurs) is 2560x1600 and the secondary monitor (on which the issue does not occur) is 1920x1080. The issue also does not occur if the second monitor is disconnected. See video for a demonstration of the issue. This issue is weirdly specific so I imagine there may be some issue replicating it - let me know if there's any more information I can provide to help. I have done some experimentation and narrowed it down to only apps running through XWayland that do this - all other apps I tested worked fine and I didn't find any XWayland apps that did not have this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491153] When using two monitors, maximized XWayland applications do not reach the top of the screen for clicking
https://bugs.kde.org/show_bug.cgi?id=491153 --- Comment #2 from Owen --- (In reply to fanzhuyifan from comment #1) > What is the output of `kscreen-doctor -o`? Are you using fractional scaling? Yeah, the main monitor is on 150% scale. Here's the output: Output: 1 eDP-2 enabled connected priority 1 Panel Modes: 0:2560x1600@165*! 1:2560x1600@60 2:1920x1200@165 3:1920x1080@165 4:1600x1200@165 5:1680x1050@165 6:1280x1024@165 7:1440x900@165 8:1280x800@165 9:1280x720@165 10:1024x768@165 11:800x600@165 12:640x480@165 13:1600x1200@60 14:1280x1024@60 15:1024x768@60 16:2560x1600@60 17:1920x1200@60 18:1280x800@60 19:2560x1440@60 20:1920x1080@60 21:1600x900@60 22:1368x768@60 23:1280x720@60 Geometry: 1920,7 1707x1067 Scale: 1.5 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB Output: 2 DP-5 enabled connected priority 2 DisplayPort Modes: 0:1920x1080@60*! 1:1920x1080@60 2:1920x1080@60 3:1920x1080@30 4:1920x1080@30 5:1920x1080@24 6:1920x1080@24 7:1600x1200@60 8:1680x1050@60 9:1400x1050@60 10:1280x1024@60 11:1440x900@60 12:1360x768@60 13:1280x800@60 14:1280x720@60 15:1280x720@60 16:1280x720@60 17:1024x768@75 18:1024x768@70 19:1024x768@60 20:800x600@75 21:800x600@72 22:800x600@60 23:800x600@56 24:720x480@60 25:720x480@60 26:720x480@60 27:720x480@60 28:720x480@60 29:640x480@75 30:640x480@73 31:640x480@60 32:640x480@60 33:640x480@60 34:720x400@70 35:1280x1024@60 36:1024x768@60 37:1280x800@60 38:1920x1080@60 39:1600x900@60 40:1368x768@60 41:1280x720@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491153] When using two monitors, maximized XWayland applications do not reach the top of the screen for clicking
https://bugs.kde.org/show_bug.cgi?id=491153 --- Comment #3 from Owen --- Just found out that the issue does not occur if the main monitor is at 160% scale. I also just discovered another issue, #459373 (https://bugs.kde.org/show_bug.cgi?id=459373) that seems to be similar, but it was on the bottom edge, was visual as well (there is no gap visually with this issue), and is marked as fixed. Possibly still related though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491153] When using two monitors, maximized XWayland applications do not reach the top of the screen for clicking
https://bugs.kde.org/show_bug.cgi?id=491153 --- Comment #5 from Owen --- (In reply to fanzhuyifan from comment #4) > Marking as duplicate of 459373. Feel free to reopen if the issue persists on > git master or the upcoming 6.2 release. > > *** This bug has been marked as a duplicate of bug 459373 *** didn't notice that the fix was in an upcoming release. I'm not sure if it's the exact same issue, since that one is also visual, but I'll wait for 6.2.0 and reopen then if it doesn't fix the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 Owen changed: What|Removed |Added CC||o...@ozone.id.au -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #107 from Owen --- (In reply to Bob Wya from comment #99) > (In reply to Nayr438 from comment #98) > > It was supposed to just be a default behavior starting with Qt5.13 to play > > it safe. At least to my understanding, but I could be wrong here. > > Setting: > > [QtQuickRendererSettings] > GraphicsResetNotifications=true > > locks my Plasma 5 Desktop, after a hibernate operation. > Tested on Gentoo with Plasma 5.15.90.1 and Qt 5.12.3 ... > > I get graphical corruption (desktop icons, System Settings. primarily) - > without the above setting. This is when resuming from hibernate - but not > consistently _every_ time. > > I'm using a Nvidia Geforce GTX 970M and Nvidia driver 418.52.10 ... Same problem here, on KDE Neon 5.16, Qt version 5.12.3 After resume from suspend no login screen appears, only the desktop background, I can restart plasma and kwin and it doesn't help, I have to reboot to get the desktop back. This is the same with the additional kwin_x11rc setting or without. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #109 from Owen --- (In reply to David Edmundson from comment #108) > >This is the same with the additional kwin_x11rc setting or without. > > Unsurprising. Change plasmashellrc or kdeglobals. Thanks for your efforts David. Yes I have done exactly as the post I quoted, added to ~/.config/kdeglobals [QtQuickRendererSettings] GraphicsResetNotifications=true I only mentioned kwin_x11rc as Comment 78 suggests ALSO setting the same flag to false in this file is necessary as well, either way makes no difference, having the kdeglobals setting is what causes the lock out after resume. Removing it fixes that problem but back to corrupt icon text. I'll try plasmashellrc instead in case that makes any difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382115] Rendering artifacts on desktop Icon Text after resume from suspend.
https://bugs.kde.org/show_bug.cgi?id=382115 Owen changed: What|Removed |Added CC||o...@ozone.id.au --- Comment #3 from Owen --- Also having this issue See this question on stackexchange: https://unix.stackexchange.com/questions/372710/kde5-after-resume-from-suspend-i-have-corrupted-labels-under-icons/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382115] Rendering artifacts on desktop Icon Text after resume from suspend.
https://bugs.kde.org/show_bug.cgi?id=382115 --- Comment #5 from Owen --- (In reply to Christoph Feck from comment #4) > According to comment #2, this needs fixing in Qt for its OpenGL usage in > QtQuick, similar to the fix in KWin for its OpenGL usage in the compositor. > > Please report this issue directly to Qt developers via > https://bugreports.qt.io/ > > The change in Qt should look similar to https://phabricator.kde.org/D6344 OK, thanks, seems they are aware https://bugreports.qt.io/browse/QTBUG-56610?jql=text%20~%20%22nvidia%22 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469555] 7c91c4bad9ee709eebfdf9d5b3997fa00ca7cd13 causes cursor to not snap back to center in Minecraft
https://bugs.kde.org/show_bug.cgi?id=469555 Owen changed: What|Removed |Added CC||o...@thegoulds.org --- Comment #15 from Owen --- Status of this says fixed but I am still having this issue in some games. For games on wine/proton, seems to depend if the game is set to fullscreen or borderless windowed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419179] Create password protected hotspot instead of one without security
https://bugs.kde.org/show_bug.cgi?id=419179 Bug 419179 depends on bug 449265, which changed state. Bug 449265 Summary: Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm https://bugs.kde.org/show_bug.cgi?id=449265 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 Owen changed: What|Removed |Added CC||o...@thegoulds.org Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #24 from Owen --- Still having this issue in Plasma 6.4.1. Provided workaround script fixed it, so I'm fairly certain it is the same issue. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 491310] New: LabPlot Legend Not Displaying Correctly
https://bugs.kde.org/show_bug.cgi?id=491310 Bug ID: 491310 Summary: LabPlot Legend Not Displaying Correctly Classification: Applications Product: LabPlot2 Version: 2.11.1 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: owenwang2...@icloud.com Target Milestone: --- Created attachment 172309 --> https://bugs.kde.org/attachment.cgi?id=172309&action=edit Plot with incorrect legend SUMMARY LabPlot legend has weird artifacts. STEPS TO REPRODUCE 1. Plot a table 2. Set curve symbol 3. Add a legend OBSERVED RESULT See attachment. EXPECTED RESULT The legend should generate correctly without the weird artifacts shown in the attached image. SOFTWARE/OS VERSIONS Release build 2.11.1 Jul 16 2024, 03:41:55 System: macOS 14.5 KDE Frameworks: Version 5.115.0 Qt Version: 5.15.13 (built against 5.15.12) ADDITIONAL INFORMATION Locale: English,United States (Decimal point '.', Group separator ',' Number settings: Decimal point '.', Group separator ',', Exponential 'e', Zero digit '0', Percent '%', Positive/Negative sign '+'/'-' (Updated on restart) Architecture: arm64-little_endian-lp64 Kernel: darwin 23.5.0 C++ Compiler: AppleClang 15.0.0.15000309 C++ Compiler Flags: -fno-operator-names -fno-exceptions -Wno-gnu-zero-variadic-macro-arguments -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self -Wvla -Wdate-time -D_GNU_SOURCE -Wall -Wextra -Wundef -Wpointer-arith -Wunreachable-code -Wunused -Wdeprecated-declarations -fno-omit-frame-pointer -fstack-protector -fexceptions -std=c++17 -O2 -Wcast-align -Wswitch-enum -fvisibility=default -pedantic -Wzero-as-null-pointer-constant -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 491310] LabPlot Legend Not Displaying Correctly
https://bugs.kde.org/show_bug.cgi?id=491310 --- Comment #1 from Owen Wang --- Just tested version 2.11.1 on Manjaro and the artifact is not appearing. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 491310] LabPlot Legend Not Displaying Correctly
https://bugs.kde.org/show_bug.cgi?id=491310 --- Comment #2 from Owen Wang --- (In reply to Owen Wang from comment #1) > Just tested version 2.11.1 on Manjaro and the artifact is not appearing. Just reproduced it on Manjaro as well. It happens whenever the symbol border width is not 0 pt. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 491310] LabPlot Legend Not Displaying Correctly
https://bugs.kde.org/show_bug.cgi?id=491310 --- Comment #5 from Owen Wang --- (In reply to Alexander Semke from comment #4) > (In reply to Owen Wang from comment #2) > > (In reply to Owen Wang from comment #1) > > > Just tested version 2.11.1 on Manjaro and the artifact is not appearing. > > > > Just reproduced it on Manjaro as well. It happens whenever the symbol border > > width is not 0 pt. > > Thank you reported this issue. I fixed it now and the fix will be included > in the next release. If this issues is urgent for you, consider using our > development version (nightly builds produced for multiple systems every day). Great, thanks for the prompt response! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406349] Android runtime linker ignores DF_1_INTERPOSE in vgpreload_core-*
https://bugs.kde.org/show_bug.cgi?id=406349 Owen wo changed: What|Removed |Added CC||wuwei...@huawei.com --- Comment #3 from Owen wo --- These Text "linker: Warning: "/system_Q_EA3/lib64/valgrind/vgpreload_core-arm64-linux.so" has unsupported flags DT_FLAGS_1=0x421 (ignoring unsupported flags)" has been existed for several version from valgrind 3.12 and android 7 . and these version are all worked (valgrind can detect the memory leak). But only android Q is failed. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 401913] New: Add support for Rust 2018 edition projects.
https://bugs.kde.org/show_bug.cgi?id=401913 Bug ID: 401913 Summary: Add support for Rust 2018 edition projects. Product: rust-qt-binding-generator Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@vandenoever.info Reporter: onel...@gmail.com Target Milestone: --- SUMMARY Currently, use statements in the generated modules are not compatible with Rust 2018 edition. I worked up a patch for this as a pull request (which was... closed immediately). The pull request I prepared earlier: https://github.com/KDE/rust-qt-binding-generator/pull/1 and the associated patch: https://patch-diff.githubusercontent.com/raw/KDE/rust-qt-binding-generator/pull/1.patch STEPS TO REPRODUCE 1. create a new cargo project based on the template 2. update your toolchain to >= 1.31 3. add `edition = "2018"` to the package section of your Cargo.toml 4. run `cargo build` OBSERVED RESULT Build fails since generated code tries to import crate-local modules as if they are top level crates. EXPECTED RESULT Build completes successfully. ADDITIONAL INFORMATION Just as an aside, I'm wondering if there isn't another way to handle questions, comments, feedback, or patches for this project. Feels a little heavy to report in this fashion just to get some discussion going, but I understand if this is just the way it has to be. Cheers, Owen -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 401913] Add support for Rust 2018 edition projects.
https://bugs.kde.org/show_bug.cgi?id=401913 --- Comment #1 from Owen Nelson --- Sorry, I'm catching up trying to navigate the KDE process. I signed up at identity.kde.org and got a diff up on phabricator now: https://phabricator.kde.org/D17447 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454439] New: Could not rename partial file smb://file.part
https://bugs.kde.org/show_bug.cgi?id=454439 Bug ID: 454439 Summary: Could not rename partial file smb://file.part Product: dolphin Version: 21.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: o...@quantumleapchicago.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Kubuntu 22.04 fresh install (minimum install, fully updated) 2. Connect to a Windows 2012 Server Share via smb://10.0.0.151 in Dolphin 3. Open any file for editing in any editor (Kate, Sublime, LibreWriter), make changes, and save. OBSERVED RESULT With Sublime, get "input/output error"; it can't merge the .part into the file With Kate, get "Could not rename partial file smb://10.0.0.151/shared/file.part" EXPECTED RESULT In previous Kubuntu versions (18.04 through 22.10), got prompted to send the file; and then prompted to overwrite the file. Upon answering yes, it works. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: Plasma 5.24.4, KDE Frameworks Version: KDE Frameworks 5.92, Qt Version: 5.15.3 Kernel: 5.15.0-33 ADDITIONAL INFORMATION * I have reproduced this on baremetal and VMs * I have seen other users report this bug in various distros, recently (2021-2022) all "resolved worksforme" or similar, but nothing specifically for Kubuntu * I have checked and have smbclient installed, as well as cifs-utils and nfs-common, as well as kio-fuse. * I notice in older versions (22.10) that when I have Terminal open in these Dolphin SMB locations, it does not show the directory; I'm still in my home / default directory. In 22.04, now it shows me a virtual path of kio-fuse directory. I wonder if that's the critical change? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 454439] Could not rename partial file smb://file.part
https://bugs.kde.org/show_bug.cgi?id=454439 --- Comment #3 from Christopher "Owen" Owens --- This is now working for me with Kate; not sure what changed. However, neither Sublime nor LibreOffice Write work, they still show I/O errors on saving the file. This is no longer a critical bug for me; as such no further debugging / followup will be provided. Feel free to reproduce or close as needed. Thank you for your help in this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 Owen changed: What|Removed |Added CC||wall.o...@gmail.com --- Comment #39 from Owen --- So I had this "bug" and screwed around with the mouse settings a bit to fix it. I'm guessing that dragging starts after you hold for the "drag start time" OR move the pointer the "drag start distance" while holding. So, I wondered, how come it thinks it's dragging when I'm not holding for the drag start time or moving it the drag start distance? Then I saw "pointer threshold" was 4px - the same value as "drag start distance". I'm not sure exactly how KDE handles these values, but it seems to be subtracting "pointer threshold" from "drag start distance" As in, if both are 4px you only need to move the pointer 0px to trigger drag starting. I just decreased pointer threshold to 2px by resetting to defaults, and have had no problem since. What I'm not sure of is how pointer threshold got set to 4px in the first place - I know I didn't do it. My guess is that some installs, for some reason, are setting this value to the same or greater value as "drag start distance", even though the default is lower. Why would a new install not be set to defaults? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 --- Comment #41 from Owen --- My point is just that in my case the problem wasn't that something lowered the doubleclick interval or DnD timeout below the defaults.. it was that something raised the "pointer threshold" above the default distance. -- You are receiving this mail because: You are watching all bug changes.
