[kdenlive] [Bug 426983] Exporting with libx264rgb results in strange colors
https://bugs.kde.org/show_bug.cgi?id=426983 --- Comment #2 from the_guy_with_h...@hotmail.com --- (In reply to emohr from comment #1) > In the render dialog -> disable "parallel processing" and try again. Just tried this, but had no luck :( -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426109] No saving projets sessions
https://bugs.kde.org/show_bug.cgi?id=426109 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425910] tiltablle symetry
https://bugs.kde.org/show_bug.cgi?id=425910 Manga Tengu changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #6 from Manga Tengu --- Yes ! Closing ! Thank you ! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405922] Very frequent akonadi crash in QLocale::dayName
https://bugs.kde.org/show_bug.cgi?id=405922 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374514] Crash on akonadictl stop
https://bugs.kde.org/show_bug.cgi?id=374514 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426475] okular document archive can't be opened even when saved with .okular ending
https://bugs.kde.org/show_bug.cgi?id=426475 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425710] Render Artefacts appear when using STROKE layer style with text tool
https://bugs.kde.org/show_bug.cgi?id=425710 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423631] can't save project
https://bugs.kde.org/show_bug.cgi?id=423631 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425910] tiltablle symetry
https://bugs.kde.org/show_bug.cgi?id=425910 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 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 are watching all bug changes.
[kmymoney] [Bug 427051] The saving of a database to MySQL fails
https://bugs.kde.org/show_bug.cgi?id=427051 --- Comment #5 from Stanimir Boychev --- (In reply to Eleazar from comment #4) > This is not limited to windows. I reported this issue using Linux (Kubuntu + > MySql). > > https://bugs.kde.org/show_bug.cgi?id=398410 It seems different - I don't observe crash and dump. Just a normal exception is thrown, which results in an error message box. KMyMoney continues to work after it. Just nothing is saved to the DB. Also I use the latest stable build for win x64 of KMyMoney 5.1. The other bug refers to version 5.0. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427059] New: Kdevelop Crash at starting
https://bugs.kde.org/show_bug.cgi?id=427059 Bug ID: 427059 Summary: Kdevelop Crash at starting Product: kdevelop Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: ganeshredco...@gmail.com Target Milestone: --- Created attachment 131977 --> https://bugs.kde.org/attachment.cgi?id=131977=edit Crash Report Kdevelop Crash at starting -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 427046] In plasma-wayland the background image gets black and white when entering the desktop.Only when I click anywhere on the desktop the color returns.
https://bugs.kde.org/show_bug.cgi?id=427046 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 399021 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399021] [Wayland] "Desaturate unresponsive applications..." effect remains even when the window is no longer frozen
https://bugs.kde.org/show_bug.cgi?id=399021 Patrick Silva changed: What|Removed |Added CC||alexjp.lene...@gmail.com --- Comment #14 from Patrick Silva --- *** Bug 427046 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #9 from caulier.gil...@gmail.com --- If it do not crash in ImageMagick, it must not crash in digiKam PNG plugin. Both use libpng, so the behavior must be the same. Thanks to share the PNG file, this will help to investigate. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #8 from Brad Templeton --- The upload is now complete at http://www.templetons.com/etc/big4.png if you really want to test on the actual file. Note that while catching exceptions in the plugin is a good idea to avoid segfault of all of digikam, I have a suspicion it takes some time to fault, and you would not want to have it try and fail repeatedly. Which means that after such a failure, you might want to produce a fake "failed" thumbnail so it doesn't try again until you do a rescan. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #7 from Brad Templeton --- BTW, display doesn't crash, just displays a full sized gray window but it does show a little thumbnail of it. If you want to work with it and have the bandwidth, it will be uploaded to http://www.templetons.com/etc/big4.png Upload should complete in 4 minutes, rsync says, but that varies so let me update when it's there. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #6 from Brad Templeton --- Correct. It is a near-gigapixel panorama. I have hundreds of these and most don't cause a problem, though I usually have them as tiff or when they fit, jpg If it is too large for digikam, that is understandable. Display does not handle it. I don't know how I made the png, possibly in gimp or convert from a tiff. Of course, digikam must not seg fault on it, however, and should just treat it as a file it can't handle displaying what it can. However, as I said this file is a decade old, and has been in my digikam archives all that time, and never caused it to seg fault. Looking at other large files it is not doing a good thumbnail, but as I say, I can understand if it is too large for that. (I would like to still be able to move such images around, add captions etc. if needed.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #5 from caulier.gil...@gmail.com --- The crash is located in libpng at end. It pass in thumbnail engine, and in DImg plugin to load PNG file, and finaly libpng. This is can be due of digiKam DImg plugin to handle memory with libpng, or the way to catch exceptions from libpng. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #4 from caulier.gil...@gmail.com --- Thanks for the feedback. It's a huge image. How did you generate this file ? Panorama ? It's a landscape ? It's a astro photo ? Can you open the file in ImageMagik "display" command line tool ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #3 from Brad Templeton --- Let me add I do have a very fast internet connection, so if you really want the gigabyte file, I can make it available for you -- I just figured you might want to look for something obvious at the designated point in the backtrace before asking for that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #2 from Brad Templeton --- Image: big4.png Format: PNG (Portable Network Graphics) Mime type: image/png Class: DirectClass Geometry: 49494x15588+0+0 Units: Undefined Colorspace: sRGB Type: TrueColor Base type: Undefined Endianess: Undefined Depth: 8-bit Channel depth: red: 8-bit green: 8-bit blue: 8-bit Channel statistics: Pixels: 771512472 Red: min: 0 (0) max: 255 (1) mean: 97.7906 (0.383493) standard deviation: 51.0469 (0.200184) kurtosis: -1.15167 skewness: 0.224519 entropy: 0.925188 Green: min: 0 (0) max: 255 (1) mean: 133.99 (0.525452) standard deviation: 56.1589 (0.220231) kurtosis: -1.34467 skewness: -0.312729 entropy: 0.907559 Blue: min: 0 (0) max: 255 (1) mean: 162.729 (0.638155) standard deviation: 63.0851 (0.247392) kurtosis: -1.10013 skewness: -0.440393 entropy: 0.909048 Image statistics: Overall: min: 0 (0) max: 255 (1) mean: 131.503 (0.5157) standard deviation: 56.7636 (0.222602) kurtosis: -1.20481 skewness: -0.014954 entropy: 0.913932 Rendering intent: Perceptual Gamma: 0.454545 Chromaticity: red primary: (0.64,0.33) green primary: (0.3,0.6) blue primary: (0.15,0.06) white point: (0.3127,0.329) Background color: white Border color: srgb(223,223,223) Matte color: grey74 Transparent color: black Interlace: None Intensity: Undefined Compose: Over Page geometry: 49494x15588+0+0 Dispose: Undefined Iterations: 0 Compression: Zip Orientation: Undefined Properties: date:create: 2020-09-27T18:24:45-07:00 date:modify: 2010-06-02T15:39:54-07:00 png:IHDR.bit-depth-orig: 8 png:IHDR.bit_depth: 8 png:IHDR.color-type-orig: 2 png:IHDR.color_type: 2 (Truecolor) png:IHDR.interlace_method: 0 (Not interlaced) png:IHDR.width,height: 49494, 15588 png:sRGB: intent=0 (Perceptual Intent) signature: 030a41cc6a75a15071b9c4be6019c8405e0a8c2492b592f553381b8a8c87b2a2 Artifacts: filename: big4.png verbose: true Tainted: False Filesize: 1.00509GiB Number pixels: 771.512M Pixels per second: 52.1998MB User time: 13.340u Elapsed time: 0:15.780 Version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 --- Comment #1 from caulier.gil...@gmail.com --- Can you give us the ouput of ImageMagick tool "identify" with this PNG file. The command line is "idenify -v _foo_.png" Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 caulier.gil...@gmail.com changed: What|Removed |Added Component|Thumbs-Image|Plugin-FilesIO-PNG CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427058] New: When window size is small, accessing minimized toolbar items from 'arrow' menu is problematic
https://bugs.kde.org/show_bug.cgi?id=427058 Bug ID: 427058 Summary: When window size is small, accessing minimized toolbar items from 'arrow' menu is problematic Product: dolphin Version: 20.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: maximts...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 131976 --> https://bugs.kde.org/attachment.cgi?id=131976=edit Small screen record to illustrate described issue. SUMMARY Accessing hidden toolbar items is problematic, because pop-up disappears before any item is selected - I think it happens because of a bug that items below pop-up recognize the cursor hover, and pop-up loses focus. STEPS TO REPRODUCE 1. Dolphin's window size is minimized, toolbar items located on the right side get hidden under arrow button. 2. Clicking on arrow button reveals pop-up panel, containing row with all hidden items. 3. Trying to click any item located on the left side of pop-up panel OBSERVED RESULT Pop-up immediately disappears when any interface interactive element in Dolphin gets hovered by cursor (even if item is located beneath the pop-up or very close to it). EXPECTED RESULT Pop-up should disappears only after mouse click - inside or outside the panel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Neon: 5.19 Plasma: 5.19.5 KDE Frameworks: 5.74.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 427057] New: vex amd64->IR: unhandled instruction bytes: 0xC4 0xC2 0x7D 0x13 0x4 0x54 0xC4 0xE3 0x7D 0x19
https://bugs.kde.org/show_bug.cgi?id=427057 Bug ID: 427057 Summary: vex amd64->IR: unhandled instruction bytes: 0xC4 0xC2 0x7D 0x13 0x4 0x54 0xC4 0xE3 0x7D 0x19 Product: valgrind Version: 3.13.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: goffinet.franc...@gmail.com Target Milestone: --- SUMMARY vex error in Opencv 3.4.7 (inside contrib modules), the lib has been manually compiled. valgind is from Ubuntu packages on Ubuntu 18.04 (bionic) OBSERVED RESULT vex amd64->IR: unhandled instruction bytes: 0xC4 0xC2 0x7D 0x13 0x4 0x54 0xC4 0xE3 0x7D 0x19 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=1 vex amd64->IR: VEX=1 VEX.L=1 VEX.n=0x0 ESC=0F38 vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==30103== valgrind: Unrecognised instruction at address 0x8ea2988. ==30103==at 0x8EA2988: cv::opt_AVX2::cvt16f32f(unsigned char const*, unsigned long, unsigned char const*, unsigned long, unsigned char*, unsigned long, cv::Size_, void*) (in /usr/local/lib/libopencv_core.so.3.4.7) ==30103==by 0x8C3082D: cv::convertFp16(cv::_InputArray const&, cv::_OutputArray const&) (in /usr/local/lib/libopencv_core.so.3.4.7) ==30103==by 0x9F4FA0D: cv::dnn::experimental_dnn_34_v13::(anonymous namespace)::CaffeImporter::populateNet(cv::dnn::experimental_dnn_34_v13::Net) (in /usr/local/lib/libopencv_dnn.so.3.4.7) ==30103==by 0x9F5222D: cv::dnn::experimental_dnn_34_v13::readNetFromCaffe(cv::String const&, cv::String const&) (in /usr/local/lib/libopencv_dnn.so.3.4.7) [... personal stack trace removed ...] ==30103== Your program just tried to execute an instruction that Valgrind ==30103== did not recognise. There are two possible reasons for this. ==30103== 1. Your program has a bug and erroneously jumped to a non-code ==30103==location. If you are running Memcheck and you just saw a ==30103==warning about a bad jump, it's probably your program's fault. ==30103== 2. The instruction is legitimate but Valgrind doesn't handle it, ==30103==i.e. it's Valgrind's fault. If you think this is the case or ==30103==you are not sure, please let us know and we'll try to fix it. ==30103== Either way, Valgrind will now raise a SIGILL signal which will ==30103== probably kill your program. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425724] non-white animated text is the wrong color
https://bugs.kde.org/show_bug.cgi?id=425724 --- Comment #7 from Todd Lewis --- Further information. I have been using the "SD/DVD Widescreen">>"DV/DVD Widescreen NTSC" profile because my current application doesn't require higher resolution. However, this is an interlaced profile, which can be really annoying for titles even when it's working as designed. Besides, my current projects will never be viewed on an interlaced display. So as an experiment I copied /usr/share/mlt/profiles/svcd_ntsc_wide to a new file /usr/share/mlt/profiles/svcd_ntsc_wide_p and changed it thus: < progressive=0 -- > progressive=1 leaving everything else the same. When previewing or rendering the problematic titles with this new otherwise identical but progressive profile, all of the strance color issues go away. (Plus it's no longer interlaced, so I'm happy.) I'm beginning to think this is strictly a problem with mlt rather than kdenlive. Does kdenlive use mlt to create the previews of titles? If so, either there's something about how kdenlive interacts with mlt for interlace -- at least with respect to titles -- or mlt has a bug all its own. I don't know enough about kdenlive's internals to make a guess though, and I'm not aware of any wrong color issues with interlace profiles outside of non-white text in titles. For my purposes, I can use the progressive profile (renders work fine on youtube, btw), but that won't help if somebody actually needs interlace. Thanks for your efforts. Great program. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427056] New: Digikam seg faults building thumbnail from gigabyte PNG
https://bugs.kde.org/show_bug.cgi?id=427056 Bug ID: 427056 Summary: Digikam seg faults building thumbnail from gigabyte PNG Product: digikam Version: 7.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-Image Assignee: digikam-bugs-n...@kde.org Reporter: kde...@em.4brad.com Target Milestone: --- Created attachment 131975 --> https://bugs.kde.org/attachment.cgi?id=131975=edit The output of digikam and gdb on seg fault SUMMARY For the past several weeks, digikam has been segfaulting about 10 seconds after I start it, even when I change what folder is under view. It appears to be rebuilding thumbnails. To see if I could fix it, I ran in the 7.2 beta appimage and the fault still occurs. STEPS TO REPRODUCE 1. Run digikam (in my photo albums, alas) 2. Wait 10 seconds 3. OBSERVED RESULT Seg fault. It seems to fault building a thumbnail for a very large PNG. This file has been present for a decade in many versions of digikam.However, when I move that file out of my archives it no longer faults so that is the cause. Of course, I don't really want to give you a gigabyte file, but will if it is the only way to diagnose. EXPECTED RESULT Not seg fault SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427055] New: Desktop Grid with Present Windows Effect: display icons and/or window titles
https://bugs.kde.org/show_bug.cgi?id=427055 Bug ID: 427055 Summary: Desktop Grid with Present Windows Effect: display icons and/or window titles Product: kwin Version: 5.19.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: groszdaniel...@gmail.com Target Milestone: --- This effect should have the option of displaying window icons and/or titles, as in the regular Present Windows effect, either taking the settings of the Present Windows effect or having its own configuration options. Note: it does take the layout option from the Present Windows effect (related bugs, fixed: Bug 214722 and Bug 374329). SOFTWARE/OS VERSIONS openSUSE Tumbleweed 20200925 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426254] Window sizes are not remembered on Wayland
https://bugs.kde.org/show_bug.cgi?id=426254 --- Comment #6 from alexjp.lene...@gmail.com --- Think of brasero and perhaps some other Gtk Apps.They still refuse to get resized,despite the fixing of this bug recently. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425873] Task Switcher All Windows Reverse Shortcut Does Not Get Applied
https://bugs.kde.org/show_bug.cgi?id=425873 Grósz Dániel changed: What|Removed |Added CC||groszdaniel...@gmail.com --- Comment #2 from Grósz Dániel --- Here the Apply button always remains greyed out when changing task switcher shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398410] KMyMoney crashes when trying to save entries back to DB Backend
https://bugs.kde.org/show_bug.cgi?id=398410 --- Comment #47 from Eleazar --- Updated to the latest version of Kubuntu and tested again. Problem still present. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427051] The saving of a database to MySQL fails
https://bugs.kde.org/show_bug.cgi?id=427051 Eleazar changed: What|Removed |Added CC||eaglex...@gmail.com --- Comment #4 from Eleazar --- This is not limited to windows. I reported this issue using Linux (Kubuntu + MySql). https://bugs.kde.org/show_bug.cgi?id=398410 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427054] New: Commission in other than base currency show incorrect amount
https://bugs.kde.org/show_bug.cgi?id=427054 Bug ID: 427054 Summary: Commission in other than base currency show incorrect amount Product: kmymoney Version: 5.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: tokes.be...@gmail.com Target Milestone: --- SUMMARY I paid commission in USD when bought some US stocks. My base currency and the currency of the investment account is HUF. In the reports (Transactions by Accounts and Transactions by Categories) the commission showing incorrect amounts (e.g. 711927.31 HUF for $7.99 -> 89102.2916 HUF/USD). When checking Commission category e.g. in Income and Expenses This Year report or by double clicking it in the Categories view to open in Ledger view, the correct amount shown (2389.90 HUF for $7.99 -> 299.1113 HUF/USD). Correct amount can be calculated in Transactions by Accounts report too: total amount in the "[Split Transaction]" line and the total price paid in "Transfer to: Investments: Investment account: Stock" are correct so commission can be calculated, though showing the wrong amount. STEPS TO REPRODUCE 1. Book the investment transaction 2. Fill the correct amount or exchange rate in the popup window 3. Check Transactions... reports OBSERVED RESULT Amount of commission in base currency is wrong in Transactions reports of Reports view, correct in Income and Expenses and Cash flow reports of Reports view and also correct in Categories view (Ledger view). EXPECTED RESULT Reports show the same amount as one can see in Categories. SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I use the last stable build of KMYMoney for Windows 5.1-763. Other transactions are calculated correctly in the reports too, like spending in EUR and HRK during vacations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426072] kwin_wayland crashes when I hover over task manager after dragging an entry from it to kickoff
https://bugs.kde.org/show_bug.cgi?id=426072 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #2 from Leszek Lesner --- Similiar crash when dragging a file ontop the taskswitcher and then pressing ALT+Tab to switch as it does not do automatic raising of windows that are associated with the windiw list you drag the file onto. Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 0x in () #6 0x7fd9ba7ad0b9 in DeclarativeMimeData::DeclarativeMimeData(QMimeData const*) (this=0x55ed13745840, copy=0x55ed0a37de80) at /home/leszek/kde/src/kdeclarative/src/qmlcontrols/draganddrop/DeclarativeMimeData.cpp:39 #7 0x7fd9ba7ac4cb in DeclarativeDragDropEvent::mimeData() (this=0x7ffd73381480) at /home/leszek/kde/src/kdeclarative/src/qmlcontrols/draganddrop/DeclarativeDragDropEvent.cpp:52 #8 0x7fd9ba7a2a79 in DeclarativeDragDropEvent::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x7ffd73381480, _c=QMetaObject::ReadProperty, _id=4, _a=0x7ffd7337f550) at /home/leszek/kde/build/kdeclarative/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:121 #9 0x7fd9d0c182a9 in QQmlPropertyData::readProperty(QObject*, void*) const (property=0x7ffd7337f530, target=, this=0x55ed224798f8) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../../../../src/Qt5/qtdeclarative/src/qml/qml/qqmlpropertydata_p.h:357 #10 0x7fd9d0c182a9 in loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0x55ed00cbfa10, object=0x7ffd73381480, property=...) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:138 #11 0x7fd9d0c37344 in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) (frame=0x7ffd7337f740, engine=0x55ed00cbfa10, code=0x7fd9ac5794a2 ":\004:\005\030\b\022<\030\v\246\006\b\001\v\030\b\006b\bL\005\246\a\006") at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:638 #12 0x7fd9d0c3c657 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (frame=frame@entry=0x7ffd7337f740, engine=engine@entry=0x55ed00cbfa10) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:463 #13 0x7fd9d0bcf412 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) (this=this@entry=0x55ed04b939e0, thisObject=, argv=argv@entry=0x7fd9c81db508, argc=, context=) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/jsruntime/qv4function.cpp:69 #14 0x7fd9d0d556a7 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) (this=this@entry=0x55ed04b94ec0, callData=callData@entry=0x7fd9c81db4d8, isUndefined=isUndefined@entry=0x0) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../../../../src/Qt5/qtdeclarative/src/qml/jsruntime/qv4value_p.h:343 #15 0x7fd9d0d00217 in QQmlBoundSignalExpression::evaluate(void**) (this=, a=0x7ffd73381450) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../../../../src/Qt5/qtdeclarative/src/qml/jsruntime/qv4jscall_p.h:95 #16 0x7fd9d0d0162b in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) (e=0x55ed04b93900, a=0x7ffd73381450) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../../../../src/Qt5/qtdeclarative/src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69 #17 0x7fd9d0d357b3 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=a@entry=0x7ffd73381450) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/qml/qqmlnotifier.cpp:104 #18 0x7fd9d0ce253c in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) (object=0x55ed04b93c10, index=, a=0x7ffd73381450) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/qml/qqmlengine.cpp:834 #19 0x7fd9cefd104f in doActivate(QObject*, int, void**) (sender=0x55ed04b93c10, signal_index=30, argv=0x7ffd73381450) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject_p.h:110 #20 0x7fd9ba7a3343 in DeclarativeDropArea::dragEnter(DeclarativeDragDropEvent*) (this=0x55ed04b93c10, _t1=0x7ffd73381480) at /home/leszek/kde/build/kdeclarative/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDropArea.cpp:268 #21 0x7fd9ba7ac89f in DeclarativeDropArea::dragEnterEvent(QDragEnterEvent*) (this=0x55ed04b93c10, event=0x7ffd73381800) at /home/leszek/kde/src/kdeclarative/src/qmlcontrols/draganddrop/DeclarativeDropArea.cpp:46 #22 0x7fd9d13697e8 in QQuickItem::event(QEvent*) (this=0x55ed04b93c10, ev=0x7ffd73381800) at /home/leszek/kde/src/Qt5/qtdeclarative/src/quick/items/qquickitem.cpp:8128 #23 0x7fd9cfeb311e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55ed008e8e20, receiver=receiver@entry=0x55ed04b93c10,
[kwin] [Bug 426072] kwin_wayland crashes when I hover over task manager after dragging an entry from it to kickoff
https://bugs.kde.org/show_bug.cgi?id=426072 Leszek Lesner changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427053] Plasma crash after removing laggy widget 'panon'
https://bugs.kde.org/show_bug.cgi?id=427053 --- Comment #1 from burritobazooka+...@gmail.com --- (oh, and: panon was only configured to use one 'monitor' device - lag was worse when having it mix together all speaker sources) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427053] New: Plasma crash after removing laggy widget 'panon'
https://bugs.kde.org/show_bug.cgi?id=427053 Bug ID: 427053 Summary: Plasma crash after removing laggy widget 'panon' Product: plasmashell Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: burritobazooka+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-10-amd64 x86_64 Distribution: SolydXK -- Information about the crash: - What I was doing when the application crashed: I removed the 'panon' third-party plasmoid from the panel because its audio buffer was lagging behind what I was hearing. I then clicked on the Weather Widget and after about 4 seconds, plasma crashed and restarted (the Weather Widget behaved as expected before that) - Unusual behavior I noticed: panon audio buffer was lagging behind what I was hearing (although today is the first time I've tried this addon) - Custom settings of the application: panon is: https://store.kde.org/p/1326546 - I used the widest frequency range at about 25fps weather widget is: https://store.kde.org/p/998917 I have three screens and both of these were on my third screen. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f545e098840 (LWP 27809))] Thread 16 (Thread 0x7f53f972d700 (LWP 28141)): #0 0x7f5463097494 in __GI___libc_read (nbytes=10, buf=0x7f53f972cb9e, fd=63) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f5463097494 in __GI___libc_read (fd=63, buf=0x7f53f972cb9e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f545f084f61 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #3 0x7f5460dfc57e in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5460dfcfe0 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f5460dfd0a0 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f5460e0b079 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f545f0b4468 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #8 0x7f54622d0fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7f54630a64cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f5415373700 (LWP 27843)): #0 0x7f54622d700c in futex_wait_cancelable (private=0, expected=0, futex_word=0x563a99d9fabc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f54622d700c in __pthread_cond_wait_common (abstime=0x0, mutex=0x563a99d9fa68, cond=0x563a99d9fa90) at pthread_cond_wait.c:502 #2 0x7f54622d700c in __pthread_cond_wait (cond=0x563a99d9fa90, mutex=0x563a99d9fa68) at pthread_cond_wait.c:655 #3 0x7f5454f5fb23 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f5454f5f877 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f54622d0fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7f54630a64cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f5417821700 (LWP 27836)): #0 0x7f546309b819 in __GI___poll (fds=0x7f5410264d70, nfds=1, timeout=89434) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5461190136 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f546119025c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f54635ad743 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f546355b15b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f54633aae76 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5464f60476 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f54633b4a67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f54622d0fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7f54630a64cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f5425149700 (LWP 27825)): #0 0x7f54611d9e84 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f546118faa0 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f54611900e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f546119025c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f54635ad743 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f546355b15b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6
[plasmashell] [Bug 426496] Multiple monitor assignment is wrong after update to Qt 5.15.1
https://bugs.kde.org/show_bug.cgi?id=426496 --- Comment #49 from David Rubio --- (In reply to Daniel Baumgartner from comment #48) > It's fixed with Qt 5.15.1-2.1 (opensuse tumbleweed 20200925) > > changelog: > - Revert commit to fix screen geometry on startup (boo#1176750, QTBUG-86604): > * 0001-Revert-Emit-QScreen-availableG-g-eometryChanged-on-l.patch I compiled my own qt5-base with the patch on the Qt bug tracker, and it works now. I don't know if they will release a new version over this though. I'm guessing not. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 402459] All clips in timeline start with the first image of a Slideshow
https://bugs.kde.org/show_bug.cgi?id=402459 Phuoc changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Phuoc --- Verified on v20.0.8, resolved. There was only a minor (not reproducible) issue. When I first time expanded the clip in step 6 the clip vanished from the timeline. After undo, I couldn't reproduce that. -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 427052] New: The "wait" command cause cpu overheat
https://bugs.kde.org/show_bug.cgi?id=427052
Bug ID: 427052
Summary: The "wait" command cause cpu overheat
Product: kturtle
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: c...@kde.nl
Reporter: hugues.larr...@laas.fr
Target Milestone: ---
SUMMARY
The "wait" command cause cpu overheat !
STEPS TO REPRODUCE
Running the following code :
reset
wait 10
OBSERVED RESULT
On an i7-8665U, CPU run at full speed (4.20GHz turbo boost) for 10 seconds
EXPECTED RESULT
CPU stay cool (~700MHz)
SOFTWARE/OS VERSIONS
kturtle 19.12.3 / Ubuntu 20.04 / Mate desktop
kturtle 18.04.1 / Debian buster / Mate desktop
kturtle 18.04.1 (backported) / Debian stretch amd64 / Mate desktop
kturtle 18.04.1 (backported) / Debian stretch i386 / Mate desktop
kturtle 16.08.3 / Debian stretch i386 / Mate desktop
ADDITIONAL INFORMATION
I have solved the problem for myself using the following workaround:
+++ kturtle-19.12.3/src/interpreter/executer.cpp
@@ -26,14 +26,13 @@
#include
#include
-#include // for wait
+#include // for usleep
#include
#include
#include
#include
void Executer::initialize(TreeNode* tree, ErrorList* _errorList)
{
rootNode = tree;
@@ -631,7 +630,9 @@ void Executer::executeWait(TreeNode* nod
if (!checkParameterQuantity(node, 1, 2+Token::Wait*100+90)) return;
if (!checkParameterType(node, Value::Number, 2+Token::Wait*100+91)
) return;
waiting = true;
-
QTimer::singleShot(static_cast(1000*node->child(0)->value()->number()),
this, ::stopWaiting);
+ usleep(static_cast(100*node->child(0)->value()->number()));
+ waiting = false;
+ return;
}
void Executer::executeAssert(TreeNode* node) {
// //qDebug() << "called";
so I don't know if it is a bug from kturtle or from QT, I don't really
understanding c++...
Happy Hacking.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 426923] EOS R5 CR3 Missing exif data with current master branch code
https://bugs.kde.org/show_bug.cgi?id=426923 --- Comment #11 from K D Murray --- Looks like broken CR3 from EOS R5/R6 is a known issue for libraw, with fixes in the pipeline. It appears the author of the new CR3 decoder is keeping it private for now, but will be in the next released version of libraw (I hope). https://github.com/LibRaw/LibRaw/issues/317#issuecomment-671383514 https://github.com/LibRaw/LibRaw/issues/317#issuecomment-674831840 Cheers, Kevin -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427051] The saving of a database to MySQL fails
https://bugs.kde.org/show_bug.cgi?id=427051 --- Comment #3 from Stanimir Boychev --- (In reply to Stanimir Boychev from comment #2) > MySQL versions are > > Server: 5.1.73 > Client: 5.6.17 (libmysql.dll) I've also tried with Client v5.1.73 - with the same result. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427051] The saving of a database to MySQL fails
https://bugs.kde.org/show_bug.cgi?id=427051 --- Comment #2 from Stanimir Boychev --- MySQL versions are Server: 5.1.73 Client: 5.6.17 (libmysql.dll) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427051] The saving of a database to MySQL fails
https://bugs.kde.org/show_bug.cgi?id=427051 --- Comment #1 from Stanimir Boychev --- Created attachment 131974 --> https://bugs.kde.org/attachment.cgi?id=131974=edit Snapshot from the created DB These are the tables that are created. Only kmmFileInfo has some data in it - one line with version=12 and fixLevel=5 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427051] The saving of a database to MySQL fails
https://bugs.kde.org/show_bug.cgi?id=427051 Stanimir Boychev changed: What|Removed |Added CC||sboyc...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427051] New: The saving of a database to MySQL fails
https://bugs.kde.org/show_bug.cgi?id=427051 Bug ID: 427051 Summary: The saving of a database to MySQL fails Product: kmymoney Version: 5.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: database Assignee: kmymoney-de...@kde.org Reporter: sboyc...@hotmail.com Target Milestone: --- SUMMARY The saving of a database to MySQL fails STEPS TO REPRODUCE 1. Install KMyMoney on Windows. Add libmysql.dll to kmymoney/bin otherwise MySQL saving does not work 2. Try to save a database to SQL/MYSQL. Use "Save As...", select "SQL", select Database Type MySQL 3. specify the database name, host name, username and password 4. Click "OK" OBSERVED RESULT The DB is created, tables also are created, but then: The following error message is shown: Cannot save to current database: Error in function unsigned long __cdecl MyMoneyStorageSqlPrivate::highestNumberFromIdString(class QString,class QString,int) : starting commit unit Driver = QMYSQL, Host = nas542, User = sboychev, Database = KMyMoney Driver Error: Database Error No -1: Text: Error type 0 Executed: Query error No -1: Driver not loaded Driver not loaded Error type 1 C:\_\9b0777e7\kmymoney\kmymoney\plugins\sql\mymoneystoragesql.cpp:359 EXPECTED RESULT Saved DB in MySQL SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 426466] doxygen latex formulas are highlighted differently in single-line and multi-line comment blocks (C/C++)
https://bugs.kde.org/show_bug.cgi?id=426466 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/72 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418050] KDE Plasma crash on systray click
https://bugs.kde.org/show_bug.cgi?id=418050 Lars Segelken changed: What|Removed |Added CC||lars...@northernraven.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420196] A KCM is re-loaded when its entry in a subcategory list/column is clicked
https://bugs.kde.org/show_bug.cgi?id=420196 --- Comment #5 from David Edmundson --- *** Bug 419336 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419336] System Settings prompts to save/discard changes when I click on the name of the current KCM
https://bugs.kde.org/show_bug.cgi?id=419336 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 420196 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427050] The classes toolview does not work--no classes displayed
https://bugs.kde.org/show_bug.cgi?id=427050 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Francis Herne --- I can't reproduce this with 5.6-git on Arch, the Classes toolview is working fine. Do you have an example of a specific project this doesn't work with? (also, can you please set the 'Version' field?) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418303] Font in sidebar is not antialiased until a second layer sidebar is opened on Wayland
https://bugs.kde.org/show_bug.cgi?id=418303 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #9 from David Edmundson --- Please reopen if you see this after you have QtWayland with 18ab3edaf2a4cdd1e9df6e166cf51a69a9785ecd (I think that's Qt 5.15.2?) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427050] New: The classes toolview does not work--no classes displayed
https://bugs.kde.org/show_bug.cgi?id=427050 Bug ID: 427050 Summary: The classes toolview does not work--no classes displayed Product: kdevelop Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: kdbase-kde...@yahoo.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open an existing project with C++ classes. 2. Click on Classes toolview button. 3. Select All projects classes or the current project classes OBSERVED RESULT The list of classes is empty. EXPECTED RESULT Show class hierarchy, with all classes, members, etc. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION This has been going on for several months. I am currently on Fedora, but it's the same on Arch Linux and Debian sid. The class parser works fine. If I hover over a variable, it shows all the information about the variable, such as where it's declared and defined. I can go to these locations, see where the variable is used, etc. These features are more important, for me at least, than the Classes toolview, but the toolview is also nice. It appears that no one else has reported this, but I cannot find any error in my configuration. It worked well until a few months ago. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 252338] KSysguard does not refresh Swap details on "Memory and Swap History" graph; but does so on the status bar
https://bugs.kde.org/show_bug.cgi?id=252338 ad...@pegasis.site changed: What|Removed |Added CC||ad...@pegasis.site -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427049] New: tablet stylus conflict when i click on the two hotkey button
https://bugs.kde.org/show_bug.cgi?id=427049 Bug ID: 427049 Summary: tablet stylus conflict when i click on the two hotkey button Product: krita Version: 4.4.0-beta1 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: crople...@gmail.com Target Milestone: --- SUMMARY i have a one by wacom tablet (CTL-472). i have a conflict when i click on the two hotkey of the stylus. the upper button (stylus) is configured to be the barspace button and always when I click on it, first it appears the pop-up palette but when i click a seconde time the real hotkey works. and the lower hotkey has the same problem. on the krita 4.3 version it was working well STEPS TO REPRODUCE 1. click on stylus hotkey 2. 3. OBSERVED RESULT pop-up palette appears EXPECTED RESULT the button configured for (Barspace) SOFTWARE/OS VERSIONS Windows: Windows 10 (x86_64) 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.
[systemsettings] [Bug 427048] New: Keyboard navigation tab not available
https://bugs.kde.org/show_bug.cgi?id=427048 Bug ID: 427048 Summary: Keyboard navigation tab not available Product: systemsettings Version: 5.15.4 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: yoho...@gmail.com Target Milestone: --- SUMMARY Although described in the manual (https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/mouse/index.html), there is no such tab as "keyboard navigation" on my system and I'm unable to disable this option that I've specified on my old system which didn't have a mouse (now I have one). STEPS TO REPRODUCE 1. Open systemsettings 2. Go to "mouse" OBSERVED RESULT No the tab is not present... EXPECTED RESULT It should be, or there should be a way to enable/disable keyboard navigation SOFTWARE/OS VERSIONS Linux Mageia 7.1 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417219] Daemonized Dolphin inappropriately triggers session restoration
https://bugs.kde.org/show_bug.cgi?id=417219 --- Comment #23 from Attila --- I think I have got it, but first let me just mention something. In your case Dolphin was autostarted because of "~/.config/autostart/dolphin.desktop". You had that file for an unknown reason and the behaviour was intended and OK. In my case the behaviour was unintended and really annoying plus a bad user experience. It has turned out that there is a file in "/etc/xdg/autostart/org.kde.dolphin.desktop" which is provided by the RPM "dolphin". This file contains a line "Exec=dolphin --daemon". I have deleted the file and Dolphin doesn't come up. Tt wasn't a big deal to me as a user to investigate a little further. Somehow I have to inform the Fedora packagers to remove the file "org.kde.dolphin.desktop", but I don't know how. Any idea? -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 421348] "Cannot write File" in Live Preview with source included from subdirectories
https://bugs.kde.org/show_bug.cgi?id=421348 --- Comment #3 from rreignier --- After looking in the source code to see if this subdirectories creation can be added, it is already there actually. See here: https://invent.kde.org/office/kile/-/blob/d4917b16ded388b4ecd9979feb78def389ec7e52/src/livepreview.cpp#L77 But the files need to be opened as part of a Kile Project and even the images must be part of the project. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416237] Window showing preview of gtk3 theme has no window decoration on Wayland
https://bugs.kde.org/show_bug.cgi?id=416237 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #3 from David Edmundson --- >There is no button to preview gtk theme on Plasma 5.20 beta. The button will show/hide itself depending on whether it finds the executable: "gtk_preview". I don't know where that is meant to come from. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427041] Geolocation information not being saved to the metadata
https://bugs.kde.org/show_bug.cgi?id=427041 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||7.2.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424230] Plasma Widget installed from KDE Store is not listed in system tray settings until Plasma is restarted
https://bugs.kde.org/show_bug.cgi?id=424230 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/297 -- You are receiving this mail because: You are watching all bug changes.
[KDb] [Bug 427047] New: In plasma-wayland, global menu: Only one menu of an app can be opened on the panel.After that, the other Menus cannot be opened.
https://bugs.kde.org/show_bug.cgi?id=427047 Bug ID: 427047 Summary: In plasma-wayland,global menu: Only one menu of an app can be opened on the panel.After that,the other Menus cannot be opened. Product: KDb Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: stan...@kde.org Reporter: alexjp.lene...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version:5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 427040] run several assumptions with multiple colors
https://bugs.kde.org/show_bug.cgi?id=427040 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 Dotan Cohen changed: What|Removed |Added CC||kde-2011...@dotancohen.com --- Comment #13 from Dotan Cohen --- I can confirm the issue in Kubutu 2020.04. I don't know which KDE version this is, for some reason it is missing from the About KDE dialogues. Specifically keyboard shortcuts are not being saved. For instance, I removed the setting for Alt-F1 because the Jetbrains IDEs use this shortcut, but every time I log in I have to remove it again. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 427046] New: In plasma-wayland the background image gets black and white when entering the desktop.Only when I click anywhere on the desktop the color returns.
https://bugs.kde.org/show_bug.cgi?id=427046 Bug ID: 427046 Summary: In plasma-wayland the background image gets black and white when entering the desktop.Only when I click anywhere on the desktop the color returns. Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: alexjp.lene...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version:5.74.0 Qt Version:5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 426219] Add a way to disable installing udev rule
https://bugs.kde.org/show_bug.cgi?id=426219 --- Comment #5 from Michael Pyne --- Git commit 2317c3a32e5aee1e926bd912275fd2149757f69a by Michael Pyne. Committed on 27/09/2020 at 19:15. Pushed by mpyne into branch 'master'. setup: Make include-dependencies optional, show module groups not chosen. My hope is to make it easier for new users to understand how to add module groups if they are desired later, since there has previously been no generated note or warning in the generated kdesrc-buildrc if the user chose no major groups. In this case we had a user who, even though they didn't select any module groups, still had kdesrc-build trying to build bluez-qt due to include-dependencies being set to 'true' (the default). However bluez-qt needs a CMake option to be passed to build with kdesrc-build; this option isn't set unless the kf5-frameworks-build-include file is read in. That fix will happen in a separate commit, this should hopefully make it easier to read through the generated kdesrc-buildrc in any case. M +74 -39 kdesrc-build-setup https://invent.kde.org/sdk/kdesrc-build/commit/2317c3a32e5aee1e926bd912275fd2149757f69a -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 426219] Add a way to disable installing udev rule
https://bugs.kde.org/show_bug.cgi?id=426219 --- Comment #6 from Michael Pyne --- Git commit ed1545b71654c7e9dc3f3ca65e0c29ef1f6d92c5 by Michael Pyne. Committed on 27/09/2020 at 19:52. Pushed by mpyne into branch 'master'. setup: Break out common 'options' blocks for kdesrc-build-setup to always use. This change should address the immediate breakage that a user had when using kdesrc-build-setup, choosing no major module groups, and then using kdesrc-build to eventually build bluez-qt. In that case, bluez-qt had an 'options' block in kf5-frameworks-build-include to address the error he'd experienced, however since kdesrc-build-setup didn't generate a include to that file, the options weren't picked up either. kdesrc-build later found the module via include-dependencies and built it anyways. To fix this, break out "always-set" options into a dedicated file (kf5-common-options-build-include) and include that from kdesrc-build-setup-generated files always. I moved these from kf5-frameworks-build-include so I added an include from that file back to kf5-common-options-build-include for backwards compatibility for existing users. This relies on duplicate options blocks continuing to work (similar to C++'s One Definition Rule) so I've documented that in the code for now. M +1-0CMakeLists.txt M +10 -5kdesrc-build-setup A +19 -0kf5-common-options-build-include M +4-15 kf5-frameworks-build-include M +2-0kf5-qt5-build-include M +2-0kf5-workspace-build-include M +5-0modules/ksb/Application.pm M +6-1modules/ksb/FirstRun.pm https://invent.kde.org/sdk/kdesrc-build/commit/ed1545b71654c7e9dc3f3ca65e0c29ef1f6d92c5 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 421348] "Cannot write File" in Live Preview with source included from subdirectories
https://bugs.kde.org/show_bug.cgi?id=421348 rreignier changed: What|Removed |Added CC||r...@robopec.com --- Comment #2 from rreignier --- I have hit the same issue using subdirectories. It might not be too hard to create the subdirectories in the output like. A bit like the Bash script in this answer: https://tex.stackexchange.com/a/477506 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 427045] In plasma-wayland resizing the mouse cursor in system settings-mouse cursor doesn't work whatever cursor theme you choose.
https://bugs.kde.org/show_bug.cgi?id=427045 alexjp.lene...@gmail.com changed: What|Removed |Added Summary|In plasma-wayland resizing |In plasma-wayland resizing |the mouse cursor in system |the mouse cursor in system |settings-mouse cursor |settings-mouse cursor |doesn't work whatever |doesn't work whatever |cursor theme you choose.ose |cursor theme you choose. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 427045] New: In plasma-wayland resizing the mouse cursor in system settings-mouse cursor doesn't work whatever cursor theme you choose.ose
https://bugs.kde.org/show_bug.cgi?id=427045 Bug ID: 427045 Summary: In plasma-wayland resizing the mouse cursor in system settings-mouse cursor doesn't work whatever cursor theme you choose.ose Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: alexjp.lene...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version:5.19.5 KDE Frameworks Version:5.74.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422552] Auto-detect appropriate scale factor for the easy cases (e.g. 4k screen) on X11
https://bugs.kde.org/show_bug.cgi?id=422552 m...@al404.spb.ru changed: What|Removed |Added CC||m...@al404.spb.ru --- Comment #5 from m...@al404.spb.ru --- Hi I'm interested in this fix, also. I have thinkpad x1 yoga (1st gen) with 2560x1440 resolution, and wayland can't work with this resolution =( -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 427044] icon setting fails
https://bugs.kde.org/show_bug.cgi?id=427044 Amnon changed: What|Removed |Added CC||amye...@gmail.com --- Comment #1 from Amnon --- Created attachment 131972 --> https://bugs.kde.org/attachment.cgi?id=131972=edit pictures -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 427044] New: icon setting fails
https://bugs.kde.org/show_bug.cgi?id=427044 Bug ID: 427044 Summary: icon setting fails Product: kile Version: 2.9.93 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: amye...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. try to change icon for "pdflatex" 2. press ok 3. icon does not change OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427030] Move Taskmanager background highlight bar to the opposite side
https://bugs.kde.org/show_bug.cgi?id=427030 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #17 from Nate Graham --- > Other arguments include that there might be good other reasons why the > opposite style is used that extensively and that "Plasma" itself uses this > opposite style for the highlight of list (?) items - see the attachment. If we don't know the reason, then we'd be blindly copying them on the assumption that they're right and we're wrong. Without concrete evidence that it is actually better, "everyone else is doing it" isn't a valid reason. (In reply to Claudius Ellsel from comment #16) > The main argument was that users are probably accustomed to the opposite > style, yes. Got it. So this would be the "user familiarity" argument. While there is an inherent Jakob's Law argument that consistency with what people are familiar with is good, this only goes so far; it cannot be taken to its logical conclusion that even minor aesthetic choices must be copied, or else we will be drawn to copy 100% of Windows or Android or whatever just because it's probably what everyone else is familiar with. This makes us a cheap and inferior copy and there is no reason not to simply use the original instead. See also https://community.kde.org/Get_Involved/Design/Lessons_Learned#Copying_Apple I don't think this very minor aesthetic thing is worth changing. If you disagree and prefer the opposite style where the indicator bar is far from the content area rather than close to it, you're welcome to create a Plasma theme that does so. That's why we have theming: so that people who don't agree with the default aesthetic choices can self-satisfy. Who knows, maybe it will be so popular that lots of people will start using it and distros will ship it by default and we'll be encouraged to accept the change. Stranger things have happened. :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427041] Geolocation information not being saved to the metadata
https://bugs.kde.org/show_bug.cgi?id=427041 MarcP changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from MarcP --- Arg, I'm so sorry! It must have been that. It wasn't my usual computer, so I must have forgotten to enable that option again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427041] Geolocation information not being saved to the metadata
https://bugs.kde.org/show_bug.cgi?id=427041 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Hi Marc, we didn't already have the topic? ((:-)) There is a new setting in the metadata settings to enable writing of geolocation information. By default like all other write settings, deactivated. Geolocation information is now also synchronized when it is written later. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413071] [Wayland] Kmail crashes when resized or maximized
https://bugs.kde.org/show_bug.cgi?id=413071 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #2 from Lukas --- The issue is stll happening on Wayland. Running kmail (or kontact) with QT_QPA_PLATFORM=xcb works but it is a little disappointing that ther ehasn't been any progress on this in years. KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427042] Save Incremental Version/Backup does not work
https://bugs.kde.org/show_bug.cgi?id=427042 Boudewijn Rempt changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |sharafzaz...@gmail.com Ever confirmed|0 |1 CC||b...@valdyas.org Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427043] New: Usage log and system information cannot be saved to a file
https://bugs.kde.org/show_bug.cgi?id=427043 Bug ID: 427043 Summary: Usage log and system information cannot be saved to a file Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY In 5.0.0 39f51c6, usage log and system information for bug reports cannot be saved. STEPS TO REPRODUCE 1. Open Help -> Show system information for bug reports, or Show Krita Log for bug reports 2. Click 'Save to file' 3. Select a directory to save to OBSERVED RESULT The operation fails silently. There is a file in the target directory with size of 0B. EXPECTED RESULT The log file is saved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427042] New: Save Incremental Version/Backup does not work
https://bugs.kde.org/show_bug.cgi?id=427042 Bug ID: 427042 Summary: Save Incremental Version/Backup does not work Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY In 5.0.0 39f51c6, if you try to save with 'Save Incremental Version' or 'Save Incremental Backup', the operation does not save and produces an error. It fails both for local storage and Google Drive. A normal document produces a different error than an autosave file open on startup after a crash. STEPS TO REPRODUCE 1. Open a document 2. Make some changes 3. Save with 'File' -> 'Save Incremental Version' or 'Save Incremental Backup' OBSERVED RESULT The document is not saved. Saving a normal document says: "Cannot open file for writing. An unspecified error occured.". Saving an autosave produces either a popup with "Couldn't save incremental version. Alternative names exhausted, try manually saving with a higher number." (for incremental version), or an error in the status bar: "Error during saving: / cannot be written to. Please save under a different name." (incremental backup). EXPECTED RESULT The document is saved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425250] Computer freezes Randomly
https://bugs.kde.org/show_bug.cgi?id=425250 --- Comment #4 from Alexander Potashev --- I've seen similar GPU hangups with i915 video driver when playing StarCraft2, kernel messages contained this: Aug 30 17:39:52 glue kernel: i915 :00:02.0: Resetting rcs0 for preemption time out Aug 30 17:39:52 glue kernel: i915 :00:02.0: SC2.exe[55786] context reset due to GPU hang Aug 30 17:39:52 glue kernel: i915 :00:02.0: GPU HANG: ecode 9:1:84df7cfc, in SC2.exe [55786] Please check kernel log for similar messages (use dmesg or look in /var/log/messages). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419746] Firefox Developer Edition icon is incorrectly set to the one of Firefox Release
https://bugs.kde.org/show_bug.cgi?id=419746 ariasuni changed: What|Removed |Added Version|5.19.4 |5.19.5 --- Comment #6 from ariasuni --- I still have this problem, it doesn’t always happen but often. Right now I tested changing the task switcher and I still have the same problem. I tried the preview of the task switcher in System Settings (Window Management → Task Switcher) and there it displays the right icon. I tried rebooting my computer and launching Firefox Developer Edition right after entering my session, and the icon is wrong… Note that I have both Firefox Release and Firefox Developer Edition installed and that I use default (breeze) icons. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425011] ext_qt for Android does not build
https://bugs.kde.org/show_bug.cgi?id=425011 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Anna Medonosova --- ext_qt from master builds correctly now, thanks to Sharaf Zaman. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427041] New: Geolocation information not being saved to the metadata
https://bugs.kde.org/show_bug.cgi?id=427041 Bug ID: 427041 Summary: Geolocation information not being saved to the metadata Product: digikam Version: 7.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Geolocation Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY The metadata is not saved to the image (unlike regular keywords, that are saved just fine). I have experienced this issue every now and then, but I don't know what might be causing it. STEPS TO REPRODUCE 1. Go to the Geolocation tool 2. Drop the picture on the map 3. Click apply OBSERVED RESULT Changes are applied immediately (faster than usual), and the geolocation icon appears on top of the picture in thumbnail view. However, if you refresh the metadata, that geolocation has not been written. EXPECTED RESULT Geolocation information actually being written to the picture. SOFTWARE/OS VERSIONS This is happening in Ubuntu 18.04.5 LTS with Gnome. I have tried it right now with digikam 7.1 (stable, appimage) and the digikam-7.2.0-beta1-20200920T074549-x86-64.appimage, with the same result. ADDITIONAL INFORMATION Running digikam in debug mode does not show any errors when trying to save the metadata. I made sure the picture is writable by the user than runs digikam (and made sure I can write other kind of metadata without any issue). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427041] Geolocation information not being saved to the metadata
https://bugs.kde.org/show_bug.cgi?id=427041 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 426219] Add a way to disable installing udev rule
https://bugs.kde.org/show_bug.cgi?id=426219 Juraj changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #4 from Juraj --- The problem was caused bu not selectiong "frameworks" in kdesrc-build-setup TUI. This caused it to not include the configuration file into ~.kdesrc-buildrc file. This paired with option "include-dependencies" which pulled the frameworks which I did not wish to build (that is why I did not check them in TUI) but were still built and such created this error. There could be a little warning ar a whole page with yes/no to include dependencies with explanation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425250] Computer freezes Randomly
https://bugs.kde.org/show_bug.cgi?id=425250 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from David Edmundson --- marking as needsinfo as per comment -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 421296] WiFi disconnecting and reconnecting randomly
https://bugs.kde.org/show_bug.cgi?id=421296 David Edmundson changed: What|Removed |Added Severity|critical|normal CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 426915] Krunner Not Rendering Properly
https://bugs.kde.org/show_bug.cgi?id=426915 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from David Edmundson --- ok, lets hope it was fixed by something else, but please reopen if it comes back -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 426219] Add a way to disable installing udev rule
https://bugs.kde.org/show_bug.cgi?id=426219 --- Comment #3 from Juraj --- I installed it from Archlinux AUR: https://aur.archlinux.org/packages/kdesrc-build-git/ I used kdesrc-build-setup and went through the graphical guide to set it up. I only had problem that it was unable to find module dir which was solved by setting PERLLIB env var to the installation directory. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 426219] Add a way to disable installing udev rule
https://bugs.kde.org/show_bug.cgi?id=426219 --- Comment #2 from Michael Pyne --- As of commit cbf96256, the suggested CMake option is already passed to bluez-qt. Someone else has reported this as a bug on IRC. Could I ask how kdesrc-build was installed (cloned from git or distribution packages) and how the kdesrc-build configuration was generated (kdesrc-build-setup, modification of the sample configuration, kdesrc-build --initial-setup, something else)? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 426986] Kscreenlocker not setting picture of the day as background
https://bugs.kde.org/show_bug.cgi?id=426986 --- Comment #8 from Domenico Panella --- ok. thanks :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425910] tiltablle symetry
https://bugs.kde.org/show_bug.cgi?id=425910 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #4 from Tymond --- Can this report be closed then? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427030] Move Taskmanager background highlight bar to the opposite side
https://bugs.kde.org/show_bug.cgi?id=427030 Claudius Ellsel changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #16 from Claudius Ellsel --- (In reply to Nate Graham from comment #15) > So in essence, you suspect that other platforms are doing it differently for > good reasons, even if you don't know what those reasons are, and that > accordingly, users are accustomed to the opposite style, rather than ours. > > Is that accurate? The main argument was that users are probably accustomed to the opposite style, yes. Other arguments include that there might be good other reasons why the opposite style is used that extensively and that "Plasma" itself uses this opposite style for the highlight of list (?) items - see the attachment. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 426986] Kscreenlocker not setting picture of the day as background
https://bugs.kde.org/show_bug.cgi?id=426986 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.20 Status|NEEDSINFO |RESOLVED --- Comment #7 from Nate Graham --- Yep! Phew. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 427040] New: run several assumptions with multiple colors
https://bugs.kde.org/show_bug.cgi?id=427040 Bug ID: 427040 Summary: run several assumptions with multiple colors Product: ksudoku Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: thierry.rouil...@laposte.net CC: kde-games-b...@kde.org Target Milestone: --- I would like to make devilish difficulty games with several assumptions. But you would have to use different colors. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427039] New: Stylus offset in Krita (bug in xf86-input-wacom)
https://bugs.kde.org/show_bug.cgi?id=427039 Bug ID: 427039 Summary: Stylus offset in Krita (bug in xf86-input-wacom) Product: krita Version: 4.3.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: poke1...@gmx.de Target Milestone: --- SUMMARY Hi guys, just wondering if you are aware of: https://github.com/linuxwacom/xf86-input-wacom/issues/93 This is *not* a Krita bug, but I'm wondering if Krita's flatpak distro should set / mention `QT_XCB_TABLET_LEGACY_COORDINATES=1` as this fixed the issue. STEPS TO REPRODUCE 1. Use Krita 4.3.0 via flatpak on current Manjaro / Gnome Desktop 2. Use external USB Wacom tablet stylus to click user interface 3. Offset in clicks on UI OBSERVED RESULT Clicks with Stylus are offset so that Krita is basically unusable via Stylus. Strangely, the offset does not occur when drawing inside the canvas. Anyway, it's a xf86-input-wacom bug (see above). EXPECTED RESULT Correct offsets. SOFTWARE/OS VERSIONS macOS: Manjaro/ gnome ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 424471] Sections of Kate settings are barely readable
https://bugs.kde.org/show_bug.cgi?id=424471 --- Comment #5 from Christoph Cullmann --- We are working on redoing the config dialog: https://invent.kde.org/utilities/kate/-/merge_requests/105 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 427038] New: Audio manager sound checker
https://bugs.kde.org/show_bug.cgi?id=427038 Bug ID: 427038 Summary: Audio manager sound checker Product: plasma-pa Version: 5.4.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: prote...@hotmail.it CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The audio manager sound checker is the applet in the system manager used to test the audio of each speaker. When the Subwoofer speaker is tested user can hear a kind of indistinct noise from that speaker. However using this command from terminal speaker-test -Dplug:surround51 -c6 -twav the user can hear the typical sound voice indicating the speaker works rightly telling: "Subwoofer". Is it possible to add a voice-sound also to the manager sound checker via Subwoofer button telling: Subwoofer replacing the indistinct noise? thanks STEPS TO REPRODUCE 1. open system manager 2. to access the audio manager 3. test the subwoofer speaker 4. open terminal 5. run speaker-test -Dplug:surround51 -c6 -twav 6. hear the voice when subwoofer is invoked. OBSERVED RESULT indistinct noise from subwoofer speaker EXPECTED RESULT voice from subwoofer telling "subwoofer" SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-48-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427030] Move Taskmanager background highlight bar to the opposite side
https://bugs.kde.org/show_bug.cgi?id=427030 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #15 from Nate Graham --- So in essence, you suspect that other platforms are doing it differently for good reasons, even if you don't know what those reasons are, and that accordingly, users are accustomed to the opposite style, rather than ours. Is that accurate? -- You are receiving this mail because: You are watching all bug changes.
