[krita] [Bug 408093] No option for anti-aliasing in selection tool options
https://bugs.kde.org/show_bug.cgi?id=408093 --- Comment #2 from Maurice Campobasso --- Sorry, my bad! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 --- Comment #5 from y...@jacky.wtf --- (In reply to Filzmaier Josef from comment #4) > I've tested rssguard which provides this functionality. I'm wondering if it > would be possible to re-use its code in Akregator, as i generally would > prefer using akregator for this. > > I've found the code in > https://github.com/martinrotter/rssguard/tree/master/src/services/owncloud > > Any akregator/c++/qt developer here who could estimate how much effort it > would be to re-use the code in akregator? I think i would be willing to try > and implement it if it is not extremely time-consuming... > > I'm not an expert in C++ and Qt but i know it somewhat and would like to get > better at it. I'm used to C and java. I've begun gaining more interest on working on low hanging fruit in KDE. This looks like it could be up my alley. I'll report back with progress when I do! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 y...@jacky.wtf changed: What|Removed |Added CC||y...@jacky.wtf -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408092] Quickly undoing and redoing using tablet express keys de/activates Soft Proofing.
https://bugs.kde.org/show_bug.cgi?id=408092 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Please check whether your express keys don't also send the shortcut for toggling soft proofing; this does sound more like a configuration issue than a bug in Krita. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398700] ZWO ASI120MC-S camera crashes KStars
https://bugs.kde.org/show_bug.cgi?id=398700 Jean-Claude changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Jean-Claude --- A number of dysfunctions are linked to this ASI120MC-S camera running on macOS and ZWO admitted it : https://astronomy-imaging-camera.com/product/asi120mc-color : “Full resolution function of the ASI120 requires full 480mbs USB communication! Mac OSX may not compatible well. Neither Windows though virtual machine. Windows though Bootcamp is recommended. Or use our ASI120S USB3.0 Cameras which runs well under Mac OSX.” https://astronomy-imaging-camera.com/software-drivers : “– Our ASI120MM/MC camera is not compatible very well with Mac OSX. – USB3.0 cameras is recommended for Mac users and fully compatible with USB2.0 host. This THREAD may help you if you want to try our ASI120MM/MC cameras on Mac OSX.” Since I discarded this camera and replaced it by a ZWO ASI174MM everything is working perfectly -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408088] No visual feedback on clicking reload file layer and unfolding hierarchy instead
https://bugs.kde.org/show_bug.cgi?id=408088 vanyossi changed: What|Removed |Added Severity|normal |minor Status|REPORTED|NEEDSINFO CC||ghe...@gmail.com Resolution|--- |NOT A BUG --- Comment #1 from vanyossi --- The file layers reload automatically if the linked file changes, there is no need to reload them. The icon seems to be there to indicate the automatic reload, or maybe sometime in the past you had to reload manually. boud: Should we change the icon? or remove it entirely? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408093] No option for anti-aliasing in selection tool options
https://bugs.kde.org/show_bug.cgi?id=408093 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||b...@valdyas.org Status|REPORTED|RESOLVED --- Comment #1 from Boudewijn Rempt --- In Krita 4.2, selections are by default vector shapes. The anti-aliasing checkbox is only relevant for raster selections and will appear if you switch the selection type. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 395783] Solver process crashed
https://bugs.kde.org/show_bug.cgi?id=395783 --- Comment #3 from Jean-Claude --- (In reply to Stanley Fertig from comment #1) > I am having PRECISELY the same issue. Solver works on my iMac but same > process crashed error message on my MacBook Air. > > J-C, did you ever get an answer or otherwise resolve this issue? Hi Stan, No more problem. I'm using Kstars 3.2.2 as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408089] Entire program window is either white or mirrors web browser display
https://bugs.kde.org/show_bug.cgi?id=408089 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #3 from vanyossi --- This bug is very similiar in nature to 407693, same windows 10, 64bit. can't mark as duplicated yet as the issue is not a consistent transparent window. could you check if turning off aero fixes the problem for you? this id recommended in the comment here https://bugs.kde.org/show_bug.cgi?id=407693#c1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408093] New: No option for anti-aliasing in selection tool options
https://bugs.kde.org/show_bug.cgi?id=408093 Bug ID: 408093 Summary: No option for anti-aliasing in selection tool options Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: cybermotron...@rocketmail.com Target Milestone: --- The checkbox to allow/disallow anti-aliasing of selections is missing in the tool options for all selection tools. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408087] File layers using .kra files saved in 4.1.7 doesn't show up when opening in 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408087 vanyossi changed: What|Removed |Added Ever confirmed|0 |1 CC||ghe...@gmail.com Status|REPORTED|CONFIRMED --- Comment #2 from vanyossi --- This is so weird on macOS. 4.1.7 can't create .kra file Layers, but if I make a kra file layer in 4.2.0 it will show as an empty layer. The wird thing: Saving the file in 4.2 and opening it in 4.1.7 the KRA file layer shows correctly. Seems to be a regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408069] The transformation tool covers the whole layer but not the frame content
https://bugs.kde.org/show_bug.cgi?id=408069 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 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.
[krita] [Bug 404996] Undoing HSV adjustment causes layers to stop functioning
https://bugs.kde.org/show_bug.cgi?id=404996 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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.
[kwin] [Bug 407538] kwin crashes
https://bugs.kde.org/show_bug.cgi?id=407538 --- 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.
[kdenlive] [Bug 407469] Problems with rendering Previews and with GLSL/Movit
https://bugs.kde.org/show_bug.cgi?id=407469 --- Comment #6 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.
[plasmashell] [Bug 407555] Starting X-Server with 2nd monitor throws panel menus half way up the screen.
https://bugs.kde.org/show_bug.cgi?id=407555 --- 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.
[kwin] [Bug 407075] crash wen switching apps on different desktops (texstudio)
https://bugs.kde.org/show_bug.cgi?id=407075 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[krita] [Bug 404707] When scaling mode is Nearest Neighbour, I can't preview animation
https://bugs.kde.org/show_bug.cgi?id=404707 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[plasmashell] [Bug 406835] Plasma 5.15.4 crash
https://bugs.kde.org/show_bug.cgi?id=406835 --- Comment #6 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 408092] New: Quickly undoing and redoing using tablet express keys de/activates Soft Proofing.
https://bugs.kde.org/show_bug.cgi?id=408092 Bug ID: 408092 Summary: Quickly undoing and redoing using tablet express keys de/activates Soft Proofing. Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: cumberbun...@yahoo.com Target Milestone: --- SUMMARY Quickly undoing and redoing using tablet express keys de/activates Soft Proofing. STEPS TO REPRODUCE 1. Designate two express keys to "undo" and "redo" functions. 2. Quickly undo, then redo. OBSERVED RESULT First express key activates desired function, then Soft Proofing turns on/off. EXPECTED RESULT Undo/Redo activate in the desired order. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Redo and Undo functions can be used in either order to achieve a similar result. Result has been found using a Wacom "Intuos Draw" Tablet. Also noted that the Keyboard Shortcuts for the same functions do not yield the same effect. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407693] Transparent Interface
https://bugs.kde.org/show_bug.cgi?id=407693 wolthera changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from wolthera --- Ah, thank you for the info! Now we'll have to see if we can find hardware to reproduce on, or whether we can pin down what causes this. There might be some more questions coming up. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 327480] Artificial sharp edges when using Color: Mix Fuzzy in Wash Mode
https://bugs.kde.org/show_bug.cgi?id=327480 --- Comment #6 from vanyossi --- Some updates as im close to fixing this: This can be exagerated by picking a light colored foreground color and a dark colored background color. It only happens in autoBrush The artifacts are triggered on a strong change in Mix Strenght, which makes fuzzy dab the perfect mode to trigger it. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408090] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408090 Mauro Carvalho Chehab changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Mauro Carvalho Chehab --- *** This bug has been marked as a duplicate of bug 408004 *** -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #4 from Mauro Carvalho Chehab --- *** Bug 408090 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408090] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408090 Bug 408090 depends on bug 408004, which changed state. Bug 408004 Summary: No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek" https://bugs.kde.org/show_bug.cgi?id=408004 What|Removed |Added Status|CLOSED |REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 Mauro Carvalho Chehab changed: What|Removed |Added Ever confirmed|0 |1 Status|CLOSED |REOPENED Resolution|FIXED |--- --- Comment #3 from Mauro Carvalho Chehab --- (In reply to awf_ul from comment #2) > Nope; it appears to not be fixed. If the tuner or screenbuffer is opened, > tuned, initialized by another app it appears to work. Otherwise, just a > blank screen. Why did you open #408090? I can't see the difference from this one... What's really weird here is to complain about mjpeg... This sounds completely bogus, as it doesn't sound right to receive mjpeg streams with ATSC. In order to be able to debug it, I need ~60 seconds with a full record of the channel you're having problems, in order to use a RF generator and test it locally. It can be captured using dvbv5-zap: https://linuxtv.org/wiki/index.php/Dvbv5-zap#Recording_the_full_MPEG_stream_on_a_transponder Even 60 seconds of record will produce a big file. So, you'll likely need to use Google Driver or something similar and e-mail me a link for download. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369723] __builtin_longjmp not supported in clang/llvm on Android arm64 target
https://bugs.kde.org/show_bug.cgi?id=369723 Benoit Jacob changed: What|Removed |Added CC||benoitja...@google.com --- Comment #7 from Benoit Jacob --- Created attachment 120388 --> https://bugs.kde.org/attachment.cgi?id=120388&action=edit Implement VG_MINIMAL_SETJMP in inline assembly on Android/arm64 Here is another patch written from scratch / from first principles, separate from the bionic code that was discussed earlier here. It is available under the current licensing terms of the valgrind file it modifies. Comments should explain the details / why I think it's correct, but let me know if I missed something. I did take very literally the comment at the top of this file saying that it was enough to save only integer registers, so this patch does only that (the patch that had been considered earlier in this bug was also saving floating-point registers). I've also noticed that VG_MINIMAL_LONGJMP was hardcoding the value 1 for the second parameter, so this patch hardcodes that. So I really think this implementation is minimal. Together with the patch on bug 339861, this allows building Valgrind on Android NDK r19c, arm64 (clang toolchain). I've tested this manually on some testcases, this does seem to work as intended. The choice of inline assembly to implement this directly in the header was partly because it allowed to keep everything local (the definition of the jmpbuf struct and the two functions, setjmp and longjmp, that it's private to), partly because that saved me the hassle of touching the buildsystem and partly because I'm just more familiar with inline assembly. Let me know if you require an out-of-line implementation in a .S file but then please advise on the path of that file and give some pointers to integrate that in the build system (conditionally compiling that file on android/arm64). Technically, this code should be correct on arm64 regardless of OS(android) but there were just enough scary notes about some registers' special roles depending on the OS in section 5.1.1. of the Aaarch PCS document (link in comment in the patch) that I thought it safer to keep this restricted to android for now, which is all I've tested. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339861] Remove Elf32_Nhdr definition for Android
https://bugs.kde.org/show_bug.cgi?id=339861 Benoit Jacob changed: What|Removed |Added Attachment #120387|0 |1 is patch|| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339861] Remove Elf32_Nhdr definition for Android
https://bugs.kde.org/show_bug.cgi?id=339861 Benoit Jacob changed: What|Removed |Added CC||benoitja...@google.com --- Comment #8 from Benoit Jacob --- Created attachment 120387 --> https://bugs.kde.org/attachment.cgi?id=120387&action=edit Variant: only disable this on __clang__ Here is another patch that preserves the existing behavior unless __clang__ is defined. Building with clang only became the default in NDK r13, in late 2016. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 408091] Missing pkey syscalls
https://bugs.kde.org/show_bug.cgi?id=408091 --- Comment #1 from Mark Wielaard --- Created attachment 120386 --> https://bugs.kde.org/attachment.cgi?id=120386&action=edit linux x86 and amd64 memory protection key syscalls -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 408091] Missing pkey syscalls
https://bugs.kde.org/show_bug.cgi?id=408091 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 408091] New: Missing pkey syscalls
https://bugs.kde.org/show_bug.cgi?id=408091 Bug ID: 408091 Summary: Missing pkey syscalls Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: m...@klomp.org Target Milestone: --- Since linux 4.9 there are a couple of syscalls to handle memory protection keys. Valgrind doesn't support memory protection keys and the RDPKRU/WRPKRU instructions to update the new PKRU register. But the syscalls have some use without that support. First pkey_alloc () can be used to check whether memory protection keys are usage: pkey_alloc() is always safe to call regardless of whether or not the operating system supports protection keys. It can be used in lieu of any other mechanism for detecting pkey support and will simply fail with the error ENOSPC if the operating system has no pkey support. Secondly pkey_mprotect can be used even without a real pkey: If the key allocation fails due to lack of support for memory protection keys, the pkey_mprotect call can usually be skipped. In this case, the region will not be protected by default. It is also possible to call pkey_mprotect with a key value of -1, in which case it will behave in the same way as mprotect. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407693] Transparent Interface
https://bugs.kde.org/show_bug.cgi?id=407693 --- Comment #2 from Rafael --- As requested, here is the log from Krita 4.2.0. I turned off the "transparency effect" in Windows 10 theme color, but unfortunately doesn't works. SESSION: 29 May 2019 21:08:02 -0300. Executing C:\Program Files\Krita (x64)\bin\krita.exe WARNING: This file contains information about your system and the images you have been working with. If you have problems with Krita, the Krita developers might ask you to share this file with them. The information in this file is not shared automatically with the Krita developers in any way. You can disable logging to this file in Krita's Configure Krita Dialog. Please review the contents of this file before sharing this file with anyone. Krita Version: 4.2.0 Languages: en_US, en_US Hidpi: false Qt Version (compiled): 5.12.2 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17763 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Hardware Information GPU Acceleration: desktop Memory: 8147 Mb Number of Cores: 4 Swap Location: C:/Users/rafah/AppData/Local/Temp 29 May 2019 21:08:19 -0300: Importing application/x-krita to application/x-krita. Location: D:/rafah/Documents/HRK/Tattoo/T O M I E.kra. Real location: D:/rafah/Documents/HRK/Tattoo/T O M I E.kra. Batchmode: 0 29 May 2019 21:08:21 -0300: Enabled stabilizer. 29 May 2019 21:08:21 -0300: Enabled stabilizer. 29 May 2019 21:08:21 -0300: Enabled stabilizer. 29 May 2019 21:08:21 -0300: Enabled stabilizer. 29 May 2019 21:08:21 -0300: Enabled stabilizer. 29 May 2019 21:08:21 -0300: Enabled stabilizer. 29 May 2019 21:08:45 -0300: Saving Document D:/rafah/Documents/HRK/Tattoo/T O M I E.kra as D:/rafah/Documents/HRK/Tattoo/T O M I E.kra (mime: application/x-krita). 3508 * 4960 pixels, 24 layers. 101 frames, 24 framerate. Export configuration: No configuration 29 May 2019 21:08:45 -0300: Converting from application/x-krita to application/x-krita. Location: D:/rafah/Documents/HRK/Tattoo/T O M I E.kra. Real location: D:/rafah/Documents/HRK/Tattoo/T O M I E.kra. Batchmode: 0. Configuration: none 29 May 2019 21:08:47 -0300: Completed saving D:/rafah/Documents/HRK/Tattoo/T O M I E.kra (mime: application/x-krita). Result: OK 29 May 2019 21:08:50 -0300: Closing. OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 760/PCIe/SSE2" Version: "4.6.0 NVIDIA 430.64" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: false == log == Supported renderers: QFlags(0x2|0x4) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGLES * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::bt2020PQColo
[krita] [Bug 408087] File layers using .kra files saved in 4.1.7 doesn't show up when opening in 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408087 --- Comment #1 from katearche...@yandex.ru --- For me it's a quite severe bug since my workflow is tightly coupled with file layer functionality and because of it I cannot use new krita at all. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408090] New: No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408090 Bug ID: 408090 Summary: No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek" Product: kaffeine Version: 2.0.17 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mchehab+sams...@kernel.org Reporter: awf...@charter.net CC: mchehab+sams...@kernel.org Depends on: 408004 Target Milestone: --- +++ This bug was initially created as a clone of Bug #408004 +++ ADDITIONAL INFORMATION ATSC TV tuner appears to work, Channels show lock and good SNR on known good station. gets [7fe81001d3e0] mjpeg demux error: cannot peek STEPS TO REPRODUCE 1. Start Kaffeine using known scan tables from Fedora 29 which was functional 2. Select Digital TV; says Playing in upper left corner, station info and time display, but no display. 3. OBSERVED RESULT Black screen, randomly *does* start to function but very rarely. edit: it appears if tuner is initialized, opened, and tuned by other application, kaffeine does seem to work properly after that. 27-05-19 13:13:42.059 [Info] kaffeine.dvb: Using built-in dvb device manager 27-05-19 13:13:42.315 [Info] kaffeine.dev: Found dvb device P1131713317de7352: Nextwave NXT200X VSB/QAM frontend 27-05-19 13:13:42.524 [Warning ] kf5.kio.core: "Could not enter folder tags:/." [7fe81001d3e0] mjpeg demux error: cannot peek [7fe82901dbe0] mjpeg demux error: cannot peek [7fe82901df50] mjpeg demux error: cannot peek [7fe82901e1b0] mjpeg demux error: cannot peek [7fe82901e1b0] mjpeg demux error: cannot peek [7fe82901e1b0] mjpeg demux error: cannot peek EXPECTED RESULT Ran well in Fedora 29. Online updated to Fedora 30. Other video player like VLC works with tuner and plays ATSC channel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Up to date Fedora 30, x86_64. ADDITIONAL INFORMATION 58930.143142] radeon_dp_aux_transfer_native: 32 callbacks suppressed In DMesg: [131517.358412] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 5400...86000 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=408004 [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek" -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 awf_ul changed: What|Removed |Added Blocks||408090 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=408090 [Bug 408090] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek" -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #2 from awf_ul --- Nope; it appears to not be fixed. If the tuner or screenbuffer is opened, tuned, initialized by another app it appears to work. Otherwise, just a blank screen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408089] Entire program window is either white or mirrors web browser display
https://bugs.kde.org/show_bug.cgi?id=408089 --- Comment #2 from Elijah Taylor --- Created attachment 120385 --> https://bugs.kde.org/attachment.cgi?id=120385&action=edit An example of Krita while completely white -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408089] Entire program window is either white or mirrors web browser display
https://bugs.kde.org/show_bug.cgi?id=408089 --- Comment #1 from Elijah Taylor --- Created attachment 120384 --> https://bugs.kde.org/attachment.cgi?id=120384&action=edit Another example of Krita mirroring other windows Turns out this issue isn't actually limited to just web browsers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408089] New: Entire program window is either white or mirrors web browser display
https://bugs.kde.org/show_bug.cgi?id=408089 Bug ID: 408089 Summary: Entire program window is either white or mirrors web browser display Product: krita Version: 4.2.0 Platform: Other OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: elijahitay...@artlover.com Target Milestone: --- Created attachment 120383 --> https://bugs.kde.org/attachment.cgi?id=120383&action=edit One example of Krita mirroring the Brave web browser SUMMARY When I start the new 4.2.0 version of Krita for Windows 10 64x, the entire display is completely white. Often times, when I open Krita while either the Microsoft Edge or Brave web browsers are open even if they're minimized, Krita shows whatever was being shown in either browser at the moment I opened Krita. This has never once happened in any previous version of Krita that I ran on Windows 10. I've tried restarting my computer and even reinstalling Krita 4.2.0, but it makes no difference. STEPS TO REPRODUCE 1. For white screen, start Krita without any other windows open or maximized 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 Pro 64x macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I'm running Windows 10 Pro 10.0.15063 x64 with Intel Core i7-3770k 3.50 GHz, Nvidia GTX 750 Ti graphics processor (Nvidia driver version 417.71), and just one display monitor with 1080p resolution. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408088] New: No visual feedback on clicking reload file layer and unfolding hierarchy instead
https://bugs.kde.org/show_bug.cgi?id=408088 Bug ID: 408088 Summary: No visual feedback on clicking reload file layer and unfolding hierarchy instead Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: katearche...@yandex.ru Target Milestone: --- SUMMARY There is a button on a file layer in a docker with circular arrows presumably meaning that the file layer should be reloaded from disk but clicking on in results in nothing. STEPS TO REPRODUCE 1. Click on the button with circular arrows situated on a file layer row in layers docker OBSERVED RESULT Nothing happens or if there are masks applied to a layer all of the layer hierarchy unfolds. EXPECTED RESULT Some visual feedback that Krita is trying to reload the file and totally not the unfolding of masks attached to a layer instead. SOFTWARE/OS VERSIONS Happens in Krita 4.1.7 and 4.2.0 noth on ubuntu18.04 and win10. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408087] File layers using .kra files saved in 4.1.7 doesn't show up when opening in 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408087 katearche...@yandex.ru changed: What|Removed |Added Version|unspecified |4.2.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408087] New: File layers using .kra files saved in 4.1.7 doesn't show up when opening in 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408087 Bug ID: 408087 Summary: File layers using .kra files saved in 4.1.7 doesn't show up when opening in 4.2.0 Product: krita Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: katearche...@yandex.ru Target Milestone: --- Created attachment 120382 --> https://bugs.kde.org/attachment.cgi?id=120382&action=edit an example of incorrect behavior of file layers in 4.2.0 SUMMARY When trying to open .kra files containing file layers referencing another .kra files 4.2.0 opens them with blank images instead of supposed-to-be-there-images-from-a-file-layer. Opening files with .png file layers on the other hand works fine. STEPS TO REPRODUCE Fork 1: 1. Download the attachment with files saved in 4.1.7. 2. Open the file named test_file_layer_with_layer_kra_417.kra in 4.2.0 Fork 2. 1. Create a new file in 4.1.7 2. Make a new file layer referencing .kra file and save the file. 3. Open the previously saved file in 4.2.0. OBSERVED RESULT There should be a blank image instead of the file layer and on big(dimension wise) images(both file layer's and an image itself) canvas starts to lag. However clicking on folder icon on a file layer opening the file layer it is referencing. Opening the same file in 4.1.7 on the other hand working totally fine. EXPECTED RESULT Files should opened as before. Doing the same steps with .png files results in expected behavior: files in 4.17 and 4.2.0 looks the same and file layers are displayed correctly. I've included .png example in the same attachment for demonstrating the case. This is happening on both windows 10(64bit) and ubuntu 18.04 64bit-appimage version of 4.2.0. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408080] kdeconnectd.exe stops responding to TCP requests after 20 minutes
https://bugs.kde.org/show_bug.cgi?id=408080 Simon changed: What|Removed |Added Component|messaging-application |common Platform|Windows CE |MS Windows Assignee|si...@ergotech.com |piyushaggarwal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408046] Stem audio export won't work
https://bugs.kde.org/show_bug.cgi?id=408046 --- Comment #2 from promike1...@gmail.com --- Maybe, it was my fault not to mention that I'd been using this feature for years. I can't go back now to check it, because of some dependencies, but I'm quite sure this feature was working with kdenlive version 18.12.3 I just updated my system but I've neither installed nor removed any 'plug-ins'. I didn't upgrade it between the two dates but this must have gone wrong somewhere around here. As a workaround, I manually muted the other tracks and exported them individually, which is really not convenient. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408047] Rendering scripts
https://bugs.kde.org/show_bug.cgi?id=408047 --- Comment #2 from promike1...@gmail.com --- Yes, sure, let's change this bug report into a wishlist. In fact I've had a scripts folder in Documents for a long time which has nothing to do with kdenlive and I don't want to mix up my stuff there. I don't get it. Kdenlive used to ask the destination folder! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407288] Kate doesn't bring existing session into foreground
https://bugs.kde.org/show_bug.cgi?id=407288 --- Comment #14 from Dominik Haumann --- There is another addition proposed here: https://phabricator.kde.org/D21485 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 John A changed: What|Removed |Added CC||drjohnny...@gmail.com --- Comment #50 from John A --- I can confirm that the regression appears in Kubuntu 19.04 with kwin 5.15.90, an NVIDIA Optimus setup (NVIDIA is selected as the primary GPU), OpenGL 3.1 used as the rendering backend and options nvidia_drm modeset=1 set(to enable PRIME Synchronization and eliminate horizontal screen tearing). KWin hangs when using active screen edges (Present Windows), Alt-tabbing and sometimes when maximizing or moving a window. Switching the rendering backend to XRender resolves the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407812] KDE Connect doesn't unset wallpaper upon media player exit on desktop
https://bugs.kde.org/show_bug.cgi?id=407812 Nicolas Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||kdeconnect-android/commit/e ||52f418dad3dd8bb34763fc8f8c1 ||bd680d489be8 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Nicolas Fella --- Git commit e52f418dad3dd8bb34763fc8f8c1bd680d489be8 by Nicolas Fella, on behalf of Matthijs Tijink. Committed on 29/05/2019 at 20:55. Pushed by nicolasfella into branch 'master'. Properly close the media session when closing the media notification M +4-1 src/org/kde/kdeconnect/Plugins/MprisPlugin/MprisMediaSession.java https://invent.kde.org/kde/kdeconnect-android/commit/e52f418dad3dd8bb34763fc8f8c1bd680d489be8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408086] New: Can't change layer visibility, lock/unlock, etc. with tablet pen
https://bugs.kde.org/show_bug.cgi?id=408086 Bug ID: 408086 Summary: Can't change layer visibility, lock/unlock, etc. with tablet pen Product: krita Version: 4.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: aut...@autumnlansing.com Target Milestone: --- SUMMARY I just tried the newly-released 4.2.0 and discovered that I can no longer change the visibilty of layers, or lock/unlock them, etc. using my tablet pen. I'm an Intuos4 user. When touching the pen to the icons, they quickly blink off and then back on again. Holding the pen on the icons for several seconds does not have any different effect. The mouse works normally. STEPS TO REPRODUCE 1. Using an Intuos4 pen, tap the layer visibilty icon. OBSERVED RESULT Icon blinks off and then on again. Layer does not change visibility. EXPECTED RESULT Layer should change visibility and icon should reflect that. I've had to go back to 4.1.7 until this is fixed, as I'm constantly fiddling with layers, and it's too disruptive to switch back and forth between pen and mouse. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408085] New: The way to order the effects is very bad
https://bugs.kde.org/show_bug.cgi?id=408085 Bug ID: 408085 Summary: The way to order the effects is very bad Product: kdenlive Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: rafamar.mm...@gmail.com Target Milestone: --- SUMMARY The way to order the effects is very bad, in the previous versions it was much more intuitive and better, easier to work, more professional. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365372] HSY' square color selector does not display the correct square content for a given hue
https://bugs.kde.org/show_bug.cgi?id=365372 --- Comment #2 from to...@gmx.at --- Created attachment 120381 --> https://bugs.kde.org/attachment.cgi?id=120381&action=edit shifting hue of advanced color selector The exact same problem persists in Krita 4.2.0 I added a quick video that shows the resulting problem of shifting hues when picking up and slightly modifying a color. In the video, all the resulting colors should be more or less the exact same color. Steps: 1. Choose a color and paint a stroke 2. Pick up the color from the painted stroke 3. Notice the sudden Jump of hue in the advanced color selector 4. Tweaking the color slightly (e.g. clicking in the same spot at the value slider) updates the current brush color 5. Paint a stroke with the new color again and notice the wrong hue This works for most of the advanced color selectors (round and square) as long as they are in HSY' mode. The new artistic color selector does not seem to be affected by this bug. I do however prefer the countinous selectability of the advanced selector (currenty not possible with all dimensions of the artistic one) and would love to see this bug adressed some day as well. HSY is a great model for picking color for paintings, but so far I always fall back to HSI because of this bug. OS: Antergos/Arch Linux Krita Version: 4.2.0 (blank default profile) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365372] HSY' square color selector does not display the correct square content for a given hue
https://bugs.kde.org/show_bug.cgi?id=365372 to...@gmx.at changed: What|Removed |Added CC||to...@gmx.at -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408084] New: Position and Zoom does not work
https://bugs.kde.org/show_bug.cgi?id=408084 Bug ID: 408084 Summary: Position and Zoom does not work Product: kdenlive Version: 19.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: cont...@tiotrom.com Target Milestone: --- SUMMARY: The Position and Zoom effect, once applied, it will transform a video or photo into a dark canvas. Basically, does not work. STEPS TO REPRODUCE 1. Add video/photo to timeline 2. Add Position and Zoom effect 3. Add a few keyframes to the effect OBSERVED RESULT The video/photo become black (black canvas) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408083] New: The first keyframe of the effects can not be moved
https://bugs.kde.org/show_bug.cgi?id=408083 Bug ID: 408083 Summary: The first keyframe of the effects can not be moved Product: kdenlive Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: rafamar.mm...@gmail.com Target Milestone: --- SUMMARY The first keyframe of the effects can not be moved, this was very useful for inverting animations, but now it is impossible to move the first keyframe. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 19.04 (available in About System) Operating System: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-15-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 15.8 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 408082] New: krarc stopped working with rpm
https://bugs.kde.org/show_bug.cgi?id=408082 Bug ID: 408082 Summary: krarc stopped working with rpm Product: krusader Version: 2.7.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: krarc Assignee: krusader-bugs-n...@kde.org Reporter: dutchk...@txoriaskea.org CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY Ever since I use Krusader I can browse into rpm archives by just clicking on them, just like any other archive. Now I get a 'the folder xxx.rpm doesn't exist' STEPS TO REPRODUCE 1. Double click on rpm package 2. 3. OBSERVED RESULT Error that folder doesn't exist EXPECTED RESULT Should open as a folder, a browsable archive SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Opensuse tumbleweed x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408081] New: The track compositing does not work as it should
https://bugs.kde.org/show_bug.cgi?id=408081 Bug ID: 408081 Summary: The track compositing does not work as it should Product: kdenlive Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: rafamar.mm...@gmail.com Target Milestone: --- Created attachment 120380 --> https://bugs.kde.org/attachment.cgi?id=120380&action=edit simple composition of a possible background for texts with four layers (the idea is to be animated) SUMMARY When you change from high quality mode to none and you add the transition from composite or composite and transform to the tracks they are not shown properly or in the order in which they are placed from top to bottom, then if you select the high quality mode again only the track that is below is shown ... this in 18.04 and earlier worked perfectly. STEPS TO REPRODUCE I attach a file and this way I save the unnecessary explanations after explaining it in the summary 1. 2. 3. OBSERVED RESULT wrong EXPECTED RESULT that works as it should, or how it worked in previous versions. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 19.04 (available in About System) Operating System: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-15-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 15.8 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #70 from Stanley Fertig --- Created attachment 120379 --> https://bugs.kde.org/attachment.cgi?id=120379&action=edit Log file from solver crashing on my Air -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 Stanley Fertig changed: What|Removed |Added CC||stanl...@nyc.rr.com --- Comment #69 from Stanley Fertig --- I am today (5/29/19) getting the same plate solver "process crashed" message on my macBook Air running Mojave. Because the solver was working on my iMac but not my Air, I completely erased the HD on my Air, re-installed Mojave, re-installed kStars, including GSC and the Astrometry index files (copied from my iMac, where they work), and then ran it. It still crashes. I did this before installing anything funky. Happy to share log file... -stan in Brooklyn -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408057] Areas transformed with the transform tool disappear
https://bugs.kde.org/show_bug.cgi?id=408057 --- Comment #5 from alienzombini...@gmail.com --- (In reply to alienzombininja from comment #3) > (In reply to Gremriel from comment #1) > > Tested this on Windows10 with both OpenGL and Angle, and I cannot reproduce > > this. > > I tried again and it seems that it happens only when I use the tablet's > stylus to do the transformation. When I use the mouse (all setup still the > same) everything behaves as expected. I tested again with the stylus and mouse, and it occurs with the mouse too. The bug occurs too if the tablet is turned off. I tried several combinations of rescaling and rotation but couldn't find any pattern, it seems to happen randomly -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 395783] Solver process crashed
https://bugs.kde.org/show_bug.cgi?id=395783 Stanley Fertig changed: What|Removed |Added Assignee|mutla...@ikarustech.com |stanl...@nyc.rr.com --- Comment #2 from Stanley Fertig --- Created attachment 120378 --> https://bugs.kde.org/attachment.cgi?id=120378&action=edit Log file with error from my Air using kStars v3.2.2 -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 406662] console log warning on closing main configuration page
https://bugs.kde.org/show_bug.cgi?id=406662 Jazeix Johnny changed: What|Removed |Added Latest Commit|https://commits.kde.org/gco |https://commits.kde.org/gco |mpris/d333aeecb537e713a58e8 |mpris/83b25d8f5fc93d9db048f |3720a32b219a46384d2 |8b3045ebe0b68995ff4 --- Comment #2 from Jazeix Johnny --- Git commit 83b25d8f5fc93d9db048f8b3045ebe0b68995ff4 by Johnny Jazeix, on behalf of Timothée Giet. Committed on 29/05/2019 at 19:18. Pushed by jjazeix into branch 'multiple_dataset'. menu, fix warning when closing configuration page M +3-2src/core/DialogActivityConfig.qml https://commits.kde.org/gcompris/83b25d8f5fc93d9db048f8b3045ebe0b68995ff4 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 395783] Solver process crashed
https://bugs.kde.org/show_bug.cgi?id=395783 Stanley Fertig changed: What|Removed |Added CC||stanl...@nyc.rr.com --- Comment #1 from Stanley Fertig --- I am having PRECISELY the same issue. Solver works on my iMac but same process crashed error message on my MacBook Air. J-C, did you ever get an answer or otherwise resolve this issue? Thanks, stan in Brooklyn (In reply to Jean-Claude from comment #0) > I'm a bit at a loss because I recently get the following error when I try to > solve : > "Solver failed. Try again > Error starting solver: Process crashed" > I get this error only on laptop and not on the desktop although I'm using > exactly the same KStars configuration on both machines (I copied in fact the > whole disk of the desktop to the laptop) > The Astrometry folders are identical. > I'm using the simulators. > What is the origin of this problem ? > Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 --- Comment #9 from Marian Klein --- When "scale display=1" and "force font dpi" is unchecked then Menu and desktop icons are of a good size ,but dolphin and fonts in menu on left size in system settings look too tiny. So I am confused now why neon does not treat kde fonts consistently. "display scale=3" fixes the problem with fonts in dolphin and menu on left in system settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055
--- Comment #8 from Marian Klein ---
My native screen dpi is 330 as I explained in the bug report, but I only try up
to 92*3 dpi for symmetry with "scale display".
Originally I was setting either ("force font dpi=288" a and "scale
display=1")
or (unchecked "force font dpi" and "scale display=3")
And yes the effect for non-maximized window was there in both cases and panel
in maximized window and full screen looked correct/big enough.
After you prompted me I tried
(unchecked "force font dpi" and "scale display") and panel in maximized window
and
menu and desktop fonts look big with readable size. The effect with smaller
panel in non-maximized window is still there too.
I am confused regarding font in menu and desktop, maybe guest OS gets correct
DPI via VirtualBox from host OS without
me messing with scale display and force font dpi. I don't remember how it was
when I installed neon first.
I noticed only sddm login screen had too tiny font (But this is another
unrelated bug).c
Probably I will try to install neon from scratch to notice initial state.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 408046] Stem audio export won't work
https://bugs.kde.org/show_bug.cgi?id=408046 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Severity|normal |wishlist Flags||Brainstorm+ --- Comment #1 from emohr --- I assume you would be able to export via stem-audio-export each audio track in a separate wave file like descripted here: https://forum.kde.org/viewtopic.php?f=271&t=130071. Correct? I made a short test and this is not working in Kdenlive as some “plug-in” are missing. I found some info about stem here: https://www.gizmodo.com.au/2015/12/everything-you-need-to-know-about-the-new-stem-audio-file-format/. Seems an open file format. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408080] New: kdeconnectd.exe stops responding to TCP requests after 20 minutes
https://bugs.kde.org/show_bug.cgi?id=408080 Bug ID: 408080 Summary: kdeconnectd.exe stops responding to TCP requests after 20 minutes Product: kdeconnect Version: 1.10 Platform: Windows CE OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: x0a.c...@gmail.com Target Milestone: --- SUMMARY This is a long-time bug I've experienced on Windows (at least 6 months). STEPS TO REPRODUCE 1. Run `cmd /k "cd C:\Program Files\KDE Connect\bin & kdeconnectd.exe"` (opens kdeconnectd with persistent command line) 2. Run `nc localhost 1716` (on linux subsystem if you don't have netcat). 3. kdeconnectd.exe should print to stderr: "kdeconnect.core: LanLinkProvider newConnection\n". 4. Wait approximately 20-30 minutes, try netcat again. OBSERVED RESULT kdeconnectd.exe will initially work as intended. All connections to port 1716 will be logged to the console. kdeconnect-indicator.exe will show a list of paired devices, all functions work. After about 20 minutes, kdeconnectd stops replying to network commands. Connections to :1716 will still be accepted, but will no longer be logged to the console. No inquiries from kdeconnect-indicator will be answered. And the client on Android will show "The paired device is not reachable". kdeconnectd.exe must be killed and restarted. It fails so predictably that I have a script that monitors kdeconnectd.exe's stderr, tries a TCP connection to 1716 every 10 mins, and kills and restarts it if "LanLinkProvider newConnection" isn't written after 1 second. EXPECTED RESULT Should work as expected all year long. SOFTWARE/OS VERSIONS Windows: 10.0.17763 Build 17763 ADDITIONAL INFORMATION I'm on a wired connection. The only feature I use (occasionally) is remote input. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 408079] New: Fetching feeds causes duplicated items
https://bugs.kde.org/show_bug.cgi?id=408079 Bug ID: 408079 Summary: Fetching feeds causes duplicated items Product: akregator Version: GIT (master) Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-b...@kde.org Reporter: danielrosc...@phoenitydawn.de Target Milestone: --- When fetching a feed multiple times akregator duplicates existing items when the content of a fetched item differs from the content of the same item already available locally. I'm suffering from this bug now since 10+ years and would like to see it finally gone. Here is my theory why it happens: Instead of using the guid only to compare two items for equality, Akregator builds a hash over title, description, content, link and author (https://github.com/KDE/akregator/blob/0d588dcbfb9cc93dec5b6bcbf3b01336ca1d09ce/src/feed/feed.cpp#L581-L585 and https://github.com/KDE/akregator/blob/0d588dcbfb9cc93dec5b6bcbf3b01336ca1d09ce/src/article.cpp#L189) and checks that as well, unless the guid started with "hash:". I believe this is not according to the specification, which states: > guid stands for globally unique identifier. It's a string that uniquely > identifies the item. > When present, an aggregator may choose to use this string to determine if an > item is new. > > http://some.server.com/weblogItem3207 > > There are no rules for the syntax of a guid. Aggregators must view them as a > string. It's up to > the source of the feed to establish the uniqueness of the string. http://www.rssboard.org/rss-specification#ltguidgtSubelementOfLtitemgt The current behavior produces duplicate items when authors fix typos in their posts or when software inserts random bits in the data (e.g. in Javascript included in the markup (Podlove Publisher is known for that (https://github.com/podlove/podlove-publisher/blob/192a2710b6ad3d0f5eff67f4daacb5d6dac6ab4a/lib/modules/subscribe_button/button.php#L88))). The latter case is particularly annoying as it produces a new item every single time akregator fetches the feed. I'd be happy to provide additional information if necessary. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #7 from Nate Graham --- Does this happen if you *don't* set the Force Fonts DPI to some high value? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405724] multi-screen to single screen slideshow memory leak
https://bugs.kde.org/show_bug.cgi?id=405724 rtver...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #10 from rtver...@gmail.com --- I am now on Qt 5.12.3 and plasmashell is no longer over-indulging in memory, so likely this was in Qt. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 --- Comment #12 from Marian Klein --- see bug 408055 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408047] Rendering scripts
https://bugs.kde.org/show_bug.cgi?id=408047 emohr changed: What|Removed |Added Flags||timeline_corruption+ Resolution|--- |WAITINGFORINFO CC||fritzib...@gmx.net Status|REPORTED|NEEDSINFO --- Comment #1 from emohr --- The scripts are stored: Linux: /home/username/Documents/scripts/ Windows: C:/Users/username/Documents/scripts. We can change the bug to wishlist if you think we should be able to choose the folder where a script should be stored. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 --- Comment #6 from Marian Klein --- See bug 408055 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 Marian Klein changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408055 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 Marian Klein changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408003 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 357171] Create new symlink dialog shows directories but not files
https://bugs.kde.org/show_bug.cgi?id=357171 Nate Graham changed: What|Removed |Added CC||skeleton1...@hotmail.it --- Comment #13 from Nate Graham --- *** Bug 408077 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408077] unable to create links to files or folders
https://bugs.kde.org/show_bug.cgi?id=408077 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- Just fixed recently! *** This bug has been marked as a duplicate of bug 357171 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 --- Comment #5 from Marian Klein --- Note that maximized (first picture in attachment) and non-maximized (second picture) windows are very close in size. And yet panel height logic sets very different automated/default panel heights. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 408078] New: KDevelop crash on macOS
https://bugs.kde.org/show_bug.cgi?id=408078 Bug ID: 408078 Summary: KDevelop crash on macOS Product: kdevelop Version: 5.3.2 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: critical Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: ka...@karhm.com Target Milestone: --- SUMMARY KDevelop crash on macOS 10.14.4 (18E226) Mojave. I get the following log when i launch KDevelop from terminal qrc:/qml/main.qml:21:1: module "QtQuick" is not installed welcomepage errors: (qrc:/qml/main.qml:21:1: module "QtQuick" is not installed) kdevplatform.shell: Can't load plugin "kdevqthelp" because a factory to load the plugin could not be obtained: "Cannot load library /Applications/kdevelop.app/Contents/PlugIns/kdevplatform/31/kdevqthelp.so: (dlopen(/Applications/kdevelop.app/Contents/PlugIns/kdevplatform/31/kdevqthelp.so, 133): Library not loaded: @rpath/QtHelp.framework/Versions/5/QtHelp\n Referenced from: /Applications/kdevelop.app/Contents/PlugIns/kdevplatform/31/kdevqthelp.so\n Reason: image not found)" Segmentation fault: 11 STEPS TO REPRODUCE 1. Go to https://www.kdevelop.org/download 2. Download KDevelop (64bit) DMG 3. Open the downloaded DMG file 4. Move 'KDevelop.app' to '/Applications' folder 5. Open KDevelop.app OBSERVED RESULT This issue is happening to me since 4 months and i was never be able to open KDevelop on macOS EXPECTED RESULT SOFTWARE/OS VERSIONS macOS: 10.14.4 (18E226) Mojave ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408077] unable to create links to files or folders
https://bugs.kde.org/show_bug.cgi?id=408077 --- Comment #1 from Skeleton221 --- Operating System: Antergos Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 Kernel Version: 5.1.5-arch1-2-ARCH OS Type: 64-bit Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor Memory: 7,6 GiB STEPS TO REPRODUCE 1. Right Mouse click on the desktop 2. Create a new basic Link to file or directory OBSERVED RESULT it shows only the folders and not the files EXPECTED RESULT should show files and folders ADDITIONAL INFORMATION opening dolphin or plasmashell in the terminal shows no error -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 --- Comment #4 from Marian Klein --- Created attachment 120377 --> https://bugs.kde.org/attachment.cgi?id=120377&action=edit After some resizing of VirtualBox window with guest OS/neon, the guest OS panel reverts back to small height. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 --- Comment #3 from Marian Klein --- Created attachment 120376 --> https://bugs.kde.org/attachment.cgi?id=120376&action=edit Non-maximized guest os virtualbox window, guest OS panel manually set taller for readability -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407497] Crash on scrolling project bin and other.
https://bugs.kde.org/show_bug.cgi?id=407497 emohr changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Flags|timeline_corruption+|Brainstorm+ Severity|normal |wishlist Status|NEEDSINFO |REPORTED --- Comment #5 from emohr --- Thank you for your feedback. For number 1: I opened issue: https://invent.kde.org/kde/kdenlive/issues/210 For number 3: issue: https://invent.kde.org/kde/kdenlive/issues/165 is opened already. I change the bug to wishlist. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 --- Comment #2 from Marian Klein --- Created attachment 120375 --> https://bugs.kde.org/attachment.cgi?id=120375&action=edit Not maximized window panel goes too tiny by default. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407529] NVIDIA display issues on wake from suspend
https://bugs.kde.org/show_bug.cgi?id=407529 Honghao Li changed: What|Removed |Added CC|i...@rasphino.cn | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407529] NVIDIA display issues on wake from suspend
https://bugs.kde.org/show_bug.cgi?id=407529 Honghao Li changed: What|Removed |Added CC||i...@rasphino.cn -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 --- Comment #1 from Marian Klein --- Created attachment 120374 --> https://bugs.kde.org/attachment.cgi?id=120374&action=edit Neon guest OS in virtual box maximized window panel height is good. Neon guest OS in virtual box maximized window panel height looks good by default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408077] unable to create links to files or folders
https://bugs.kde.org/show_bug.cgi?id=408077 Skeleton221 changed: What|Removed |Added Summary|OS:Antergos |unable to create links to ||files or folders -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408077] OS:Antergos
https://bugs.kde.org/show_bug.cgi?id=408077 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408077] New: OS:Antergos
https://bugs.kde.org/show_bug.cgi?id=408077 Bug ID: 408077 Summary: OS:Antergos Product: plasmashell Version: 5.15.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: skeleton1...@hotmail.it CC: plasma-b...@kde.org Target Milestone: 1.0 Flags: Wayland-, X11-, Backport-, Brainstorm-, corner_case-, Translation_missing-, Usability+, VisualDesign- 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: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407646] Onion skin docker minimum fixed width too wide
https://bugs.kde.org/show_bug.cgi?id=407646 --- Comment #3 from WOAS --- Bug(?) also present in Win10 x64 version -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407646] Onion skin docker minimum fixed width too wide
https://bugs.kde.org/show_bug.cgi?id=407646 WOAS changed: What|Removed |Added CC||korotkih...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407693] Transparent Interface
https://bugs.kde.org/show_bug.cgi?id=407693 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from wolthera --- A similar situation was noted for Windows 7 here, but there turning off aero fixed it: https://www.deviantart.com/comments/1/799531875/4737939621 No idea what windows 10 might have that could trigger similar behaviour. Rafael, if you could, can you try to find information on what kind of graphics card/driver you have? There should be some opengl/angle info in the help->system information for bugreports that would be useful for instance. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407998] Okular scales down pages when printing
https://bugs.kde.org/show_bug.cgi?id=407998 --- Comment #8 from Nate Graham --- Darn. That would be a good bug to file against Neon | Snaps. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408057] Areas transformed with the transform tool disappear
https://bugs.kde.org/show_bug.cgi?id=408057 --- Comment #4 from Gremriel --- I sometimes have the selection content disappear for a second, and some weird lines dancing around inside the selection. I will update my drivers to see if that helps. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407998] Okular scales down pages when printing
https://bugs.kde.org/show_bug.cgi?id=407998 --- Comment #7 from Sergio --- Wanted to give 1.7.x a try and tried installing the snap. That does not work, though. t.qpa.xcb: could not connect to display :0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aborted (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408076] New: [Surface Pro 2017] Eraser on stylus doesn't switch to eraser brush
https://bugs.kde.org/show_bug.cgi?id=408076 Bug ID: 408076 Summary: [Surface Pro 2017] Eraser on stylus doesn't switch to eraser brush Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: cybermotron...@rocketmail.com Target Milestone: --- When using the eraser on the stylus, it doesn't change to the eraser tool/brush. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 --- Comment #11 from Nate Graham --- There's so much discussion here that I'm having a hard time identifying what the issue really is. Can you attach a screen recording that depicts it happening? That would be very helpful. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408075] New: Okular flips pages if history is exhausted while using the back / forward keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=408075 Bug ID: 408075 Summary: Okular flips pages if history is exhausted while using the back / forward keyboard shortcuts Product: okular Version: 1.7.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY Okular binds the alt+shift+left/right shortcuts to the 'back' and 'forward' items by default. If the history is exhausted (i.e. we navigate back/forward till there are no more locations left), okular starts moving to the next/previous page, acting as if we have pressed just the left/right arrow key. STEPS TO REPRODUCE 1. Open a PDF in Okular. 2. Add the back and forward buttons to the toolbar (this is just to illustrate the issue) 3. Note that the 'forward' button is greyed out. 4. Press Alt+Shift+Right (forward). 5. Note that Okular moves forward one page. 6. Now scroll up and down to populate the history. 7. Press Alt+Shift+Left until the history of previous locations is exhausted. At this point, the 'back' button will be greyed out and unclickable. 8. Press Alt+Shift+Left 8. Note that this causes Okular to move one page back (as if we had just pressed the left arrow key) OBSERVED RESULT Okular flips pages when there is nowhere to go to in the history. EXPECTED RESULT Okular should do nothing if history is exhausted (i.e. after steps 8 and 4). SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION This is reproducible only if the shortcut contains an arrow key. If we bind something like ctrl+9 to 'forward', Okular shows the expected behaviour. Prima facie, it looks like Okular doesn't correctly handle the keypresses corresponding to a shortcut if the shortcut corresponds to an action that cannot be performed (like going 'forward' when we are at the most recently veiwed location). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408069] The transformation tool covers the whole layer but not the frame content
https://bugs.kde.org/show_bug.cgi?id=408069 --- Comment #3 from stepan --- Oh, i gust found out that it happens when onion skin is turned on. If it is off , the transform tool works as usual. -- You are receiving this mail because: You are watching all bug changes.
