[kdenlive] [Bug 407079] geometry of composite and transform efefct is taken from another MPG clip.
https://bugs.kde.org/show_bug.cgi?id=407079 --- Comment #3 from Davy Bartoloni --- Created attachment 119846 --> https://bugs.kde.org/attachment.cgi?id=119846=edit Screengrab, projects and files. here the 2 files (1 video with custom size, 1920x450) and a squared image (perfect square).. and the composite and trasform resize is presenting the geometry of the MP4 on the sqaure image. (red borders are different from real image borders) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407228] New: Crash while using move tool with a large layer
https://bugs.kde.org/show_bug.cgi?id=407228 Bug ID: 407228 Summary: Crash while using move tool with a large layer Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY git 0bb8b52 Crashed moving a 7k x 9k layer with move tool (with keyboard) I think the perpormance in general with large canvas is kinda slow in krita. Not that I'm not able to do my job, but it would be nice to see it improve in the future. STEPS TO REPRODUCE 1. Fill a 7k x 9k layer with something. 2. Select move tool 3. Press any of up, down, left, right keys. 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 Error occurred on Sunday, May 5, 2019 at 14:23:51. krita.exe caused an Access Violation at location 07FEBE855540 in module kritadefaulttools.dll Reading from location . AddrPC Params 07FEBE855540 0022C090 1CD88320 0246A140 kritadefaulttools.dll!0x25540 KisToolMove::moveDiscrete+0x20 07FEC44675DD 20D18D30 001F 20D18D30 Qt5Core.dll!0x2275dd QMetaObject::activate+0x90d 07FEC26F3E0E 0022C090 07FEC4445689 1CD88320 Qt5Widgets.dll!0x3e0e QAction::activate+0xfe 07FEC26F48CB 0022FBB0 0001 Qt5Widgets.dll!0x48cb QAction::event+0x1b 07FEC26F7BDC 77383128 0050 Qt5Widgets.dll!0x7bdc QApplicationPrivate::notify_helper+0x9c 07FEC26FEC63 0001 07FEC426215F Qt5Widgets.dll!0xec63 QApplication::notify+0x3b3 07FEC14C35C6 20FE5148 0001 2CB6B810 libkritaui.dll!0x2c35c6 KisApplication::notify+0x16 07FEC443BF08 3F7AF4A0 00020001 0001 Qt5Core.dll!0x1fbf08 QCoreApplication::sendEvent+0x1a8 07FEC3C87659 0246A230 1CD88320 0112 Qt5Gui.dll!0x67659 QShortcutMap::dispatchEvent+0xe9 07FEC3C87872 0100 089FE4E8 089FE4C0 Qt5Gui.dll!0x67872 QShortcutMap::tryShortcut+0x1b2 07FEC3C35C10 2CAF1780 0238D670 0001 Qt5Gui.dll!0x15c10 QWindowSystemInterface::handleShortcutEvent+0x170 07FEC3C53775 07FEC4441F53 0001 Qt5Gui.dll!0x33775 QGuiApplicationPrivate::processKeyEvent+0x95 07FEC3C58445 024AE520 023A0450 000D034E Qt5Gui.dll!0x38445 QGuiApplicationPrivate::processWindowSystemEvent+0xe5 07FEC3C303FC 773D6AF8 000D034E 0401 Qt5Gui.dll!0x103fc QWindowSystemInterface::sendWindowSystemEvents+0x44c 07FEC449689A 0038 0022C608 Qt5Core.dll!0x25689a QEventDispatcherWin32Private::sendTimerEvent+0x60a 77179BBD 0022C720 07FEC44963C0 USER32.dll!0x19bbd UserCallWinProcCheckWow+0x1ad 771798C2 0022C720 0022C720 07FEC44963C0 USER32.dll!0x198c2 DispatchMessageWorker+0x3b5 07FEC4495D4B 023A0450 0024 02468B20 Qt5Core.dll!0x255d4b QEventDispatcherWin32::processEvents+0x5db 6A8FB7D5 0080 0014 2820 qwindows.dll!0x7b7d5 qt_plugin_instance+0x2e15 07FEC443A14F 07FEEE3FCE60 07FEC2D9CA70 0022FB70 Qt5Core.dll!0x1fa14f QEventLoop::exec+0x13f 07FEC4443417 0022FC00 0022FBB0 0008 Qt5Core.dll!0x203417 QCoreApplication::exec+0x77 000140006EE3 0001 023A01B0 000140FC3978 krita.exe!0x6ee3 main+0x2143 0001400013C7 krita.exe!0x13c7 __tmainCRTStartup+0x247 0001400014CB krita.exe!0x14cb WinMainCRTStartup+0x1b 7727556D kernel32.dll!0x1556d BaseThreadInitThunk+0xd 773D385D ntdll.dll!0x5385d RtlUserThreadStart+0x1d 00014000-000140FD3000 krita.exe 7738-7751F000 ntdll.dll 6.1.7601.24417 07FEEC99-07FEEC9A2000 aswhook.dll 19.4.4318.0 7726-7737F000 kernel32.dll 6.1.7601.24417 07FEFD1B-07FEFD21A000 KERNELBASE.dll6.1.7601.24417 07FEEE3E-07FEEE41F000 libkritaglobal.dll 07FEEE4B-07FEEE4BE000 libkritaversion.dll 6144-6145A000 libgcc_s_seh-1.dll 07FEFEDF-07FEFEE8F000 msvcrt.dll
[kdenlive] [Bug 407079] geometry of composite and transform efefct is taken from another MPG clip.
https://bugs.kde.org/show_bug.cgi?id=407079 --- Comment #2 from Davy Bartoloni --- (In reply to emohr from comment #1) > By opening your Kdenlive file it leads to a crash on Windows and to the > comma/point issue under Linux. > > Added to issue: https://invent.kde.org/kde/kdenlive/issues/78. > > I assume your other issue could be the same root cause: > https://bugs.kde.org/show_bug.cgi?id=405924 on latest sources also happens to me. (i can't open the geometry example created just few days ago)... i will provide an updated one. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407077] Composite and transform parameters (and also geometry) are taken from other clip.
https://bugs.kde.org/show_bug.cgi?id=407077 --- Comment #9 from Davy Bartoloni --- (In reply to emohr from comment #7) > Created attachment 119820 [details] > Fade on video clip > > @JBM: I changed the comma to point in the language settings and I could load > the Kdenlive file. > > @Davy: I think you are confused that the effect “composite and transform” > between V1 and A1 apply to the clip on V1. Correct? i'm confused about effects applied on tracks that have no effects, and switching the V1 to Background, the fading is working in another way (inverted?) but now seems fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407077] Composite and transform parameters (and also geometry) are taken from other clip.
https://bugs.kde.org/show_bug.cgi?id=407077 --- Comment #8 from Davy Bartoloni --- (In reply to Jean-Baptiste Mardelle from comment #6) > Your attached project file, works correctly for me now. > Please provide another sample project and describe what is wrong if you > think this issue is not solved. @emohr, the crash is probably related to the > Windows locale issue that prevents opening a project that was created with a > different locale. If you change your locale to use a comma instead of a dot, > you might be able to open the project i can confirm that now the project works as expected, fixed for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406863] Wacom Cintiq Pro32 stops tracking stylus when lifted and returned to canvas space
https://bugs.kde.org/show_bug.cgi?id=406863 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403942] crash by right click
https://bugs.kde.org/show_bug.cgi?id=403942 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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.
[Touchpad-KCM] [Bug 368156] No touchpad found
https://bugs.kde.org/show_bug.cgi?id=368156 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[krita] [Bug 401759] Animation does not render properly when I change the end frame
https://bugs.kde.org/show_bug.cgi?id=401759 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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 403265] [HUION] Shortcuts not working with Python Scripts with 1060 Plus (8192)
https://bugs.kde.org/show_bug.cgi?id=403265 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[plasmashell] [Bug 370258] No option to bring forward multiple windows of the same program
https://bugs.kde.org/show_bug.cgi?id=370258 --- Comment #21 from Aaron Wolf --- (In reply to Lukas Ba. from comment #20) > (In reply to David Edmundson from comment #19) > > > I can't imagine bringing multiple windows forward at once being a good > > solution to anything. If I have a maximised dolphin and 2 smaller ones lower > > in the stack I have no way to access the ones lower in the stack. > > I imagine this: Multiple windows of the same application are split > side-by-side, and bringing them to front shows all of them. The windows are > not overlapping or stacked thereafter, because they were side-by-side before > they were minimized. It's not just minimization. Maybe there are multiple windows being used all visible at once by one program, and then a second (maybe even full-screen) program is opened or brought forward. Now, there's no way to easily go *back* to see the multiple windows of the original program other than minimizing or pushing to the back the particular blocking windows. I want a way to have a multi-window program open, then move to another program, and then go back to the first by choosing the first (rather than thinking about which program(s) to hide). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370258] No option to bring forward multiple windows of the same program
https://bugs.kde.org/show_bug.cgi?id=370258 --- Comment #20 from Lukas Ba. --- (In reply to David Edmundson from comment #19) > I can't imagine bringing multiple windows forward at once being a good > solution to anything. If I have a maximised dolphin and 2 smaller ones lower > in the stack I have no way to access the ones lower in the stack. I imagine this: Multiple windows of the same application are split side-by-side, and bringing them to front shows all of them. The windows are not overlapping or stacked thereafter, because they were side-by-side before they were minimized. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406863] Wacom Cintiq Pro32 stops tracking stylus when lifted and returned to canvas space
https://bugs.kde.org/show_bug.cgi?id=406863 --- Comment #2 from Brian --- Yay! The nightly build works just as expected (and the way 4.1.7 works with my other Wacom devices). Looking forward towards being able to use it. Is there a rough ETA for when 4.2 stable may be coming? Thanks! -- 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 --- Comment #24 from Peter Eszlari --- (In reply to Luca Carlon from comment #22) > Hello, I'm also affected by this issue. It is so severe that the system was > hardly usable. I just noticed one thing: I suspect the issue appears for me > only when drm is enabled with nvidia-drm.modeset=1. By default this was not > set in Kubuntu 18.10 and 19.04 (may explain why Peter Eszlari could not > reproduce?). Unfortunately drm is the only way I found to prevent horizontal > tearing. > No idea if this info is already known or of any help to you. I can't reproduce this bug with nvidia-drm.modeset=1 either. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404771] Panning of canvas cant be set to Shift+Alt+LMB.
https://bugs.kde.org/show_bug.cgi?id=404771 Jasper changed: What|Removed |Added Resolution|--- |NOT A BUG CC||firebea...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #1 from Jasper --- The shortcut Shift + Alt + Left is already in use in the Default Krita Profile. The shortcut is used in the Alternate Invocation section to set the action mode of the current tool to Secondary Mode. If you want to use the Shift + Alt + Left combination for another action you need to make sure that the key/mouse combination is only used once. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 406145] Kaffeine hangs with latest libdvbv5-1.16.5
https://bugs.kde.org/show_bug.cgi?id=406145 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #15 from Mauro Carvalho Chehab --- (In reply to Mauro Carvalho Chehab from comment #14) > (In reply to Ali Molaei from comment #13) > > Same problem on Arch Linux with kaffeine 2.0.16 and 2.0.17 with > > libv4l-1.16.5 > > > > kaffiene works with libv4l 1.16.3 > > The fix for it was already at upstream at libv4l. A new version of it > (1.16.6) will very likely be released this weekend. v4l-utils-1.16.6 was released today with the needed fix. So, I'm closing this bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 407227] New: Mint 19.1 on 64bit laptop .... kde-spectacle white-screens, requiring rebooting
https://bugs.kde.org/show_bug.cgi?id=407227 Bug ID: 407227 Summary: Mint 19.1 on 64bit laptop kde-spectacle white-screens, requiring rebooting Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: douglas.fort...@swissvault.io Target Milestone: --- SUMMARY kde-spectacle (a screen snapshot program) white-screens, requiring rebooting STEPS TO REPRODUCE 1. Linux Mint 19.1 64bit on Acer Aspire V5 laptop 8GB memory 2. Install kde-spectacle (replacement for ksnapshot) via synaptic 3. Screen capture of rectangular zone (and maybe any screen capture) OBSERVED RESULT White screen, halting system EXPECTED RESULT A screen image capture SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linut Mint Linux version 4.15.0-48-generic (buildd@lgw01-amd64-036) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 ADDITIONAL INFORMATION Please bring back ksnapshot into synaptic menu which worked just fine. PS: If someone is submitting a bug, why make them create an account, you probably lose 90% of the bug reporting because people are in a hurry and don't have time to create new accounts! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196 --- Comment #3 from Sebastian Krzyszkowiak --- Since 15-16 ms timeouts suggest that it's likely some rendering loop, let me add that I use Intel Mesa drivers on Arch and llvmpipe in the VM, if that makes any difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196 --- Comment #2 from Sebastian Krzyszkowiak --- Created attachment 119845 --> https://bugs.kde.org/attachment.cgi?id=119845=edit strace A freshly booted Neon ISO in a virtual machine. The same thing I observed locally on my Arch with stable Plasma. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Color picker of GIMP 2.10 doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Summary|Colour Picker of GIMP |Color picker of GIMP 2.10 |doesn't work with OpenGL|doesn't work with OpenGL |compositor backend |compositor backend -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Flags||X11+, Usability+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 --- Comment #1 from Evgen --- > OBSERVED RESULT > GIMP picks color under mouse > > EXPECTED RESULT > GIMP picks some color (black/blue) from Plasma theme Sorry, EXPECTED/OBSERVED must be vice versa. Unfortunately I'm unable to edit initial message. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Keywords||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] New: Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Bug ID: 407226 Summary: Colour Picker of GIMP doesn't work with OpenGL compositor backend Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scene-opengl Assignee: kwin-bugs-n...@kde.org Reporter: alts...@gmail.com Target Milestone: --- SUMMARY When kwin_x11 uses OpenGL 2/3 compositor backends, GIMP 2.10 can't get right color with built-in color picker. STEPS TO REPRODUCE 1. Make sure you have compositing enabled with OpenGL backend 2. Install gimp 2.10.8+ (on Neon you can use ppa:otto-kesselgulasch/gimp) 3. Try to pick color OBSERVED RESULT GIMP picks color under mouse EXPECTED RESULT GIMP picks some color (black/blue) from Plasma theme SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION GIMP 2.8.12 from repos is not affected. Flatpak version also works fine (didn't test Snap). After you switch backend to Xrender or "block compositing" from "Special Settings", color picker works properly. I tried it also on Kubuntu (Plasma 5.12.x) with this PPA. Debian 10 (Plasma 5.14.5) & Mageia 7 (Plasma 5.15.4) have GIMP 2.10 in the official repos and there problem is also reproducible. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402760] Source browse mode activated when saving the document with shortcut
https://bugs.kde.org/show_bug.cgi?id=402760 --- Comment #6 from RJVB --- I didn't say you changed the "save" shortcut, I pointed out that it is difficult to use that or any other shortcut without side-effect if the Ctrl key on it self is used as a shortcut too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407216] Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor
https://bugs.kde.org/show_bug.cgi?id=407216 --- Comment #7 from Danfox Davies --- Attempting to backtrace with GDB by attaching it to the process ID of kwin_x11 caused the GUI to instantly hang/freeze altogether on its TTY. I was still able to switch to another TTY. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 407225] New: Startup
https://bugs.kde.org/show_bug.cgi?id=407225
Bug ID: 407225
Summary: Startup
Product: rkward
Version: unspecified
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: rkward-de...@kde.org
Reporter: gregoryhell...@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:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
---Problem description---
Please fill in the missing bits *in English*.
I encountered the error message quoted below. Additionally, I saw the following
symptoms:
###Please fill in (if applicable)###
What - in detail - did you do directly before you encountered this problem?
###Please fill in###
When you try to repeat the above, does the problem occur again (no, sometimes,
always)?
###Please fill in###
If applicable: When doing the same thing in an R session outside of RKWard, do
you see the same problem?
###Please fill in###
Do you have any further information that might help us to track this problem
down? In particular, if applicable, can you provide sample data and sample R
code to reproduce this problem?
###Please fill in###
RKWard is available in many different packagings, and sometimes problems are
specific to one method of installation. How did you install RKWard (which
file(s) did you download)?
###Please fill in###
---Error Message---
Message code: r_engine_has_died
Error during handshake with backend process. Expected token '', received token
'{415f8340-8a7b-4f3a-9c49-1aab83797f30}'
The R backend will be shut down immediately. This means, you can not use any
more functions that rely on it. I.e. you can do hardly anything at all, not
even save the workspace (but if you're lucky, R already did that). What you can
do, however, is save any open command-files, the output, or copy data out of
open data editors. Quit RKWard after that. Sorry!
---Session Info---
RKWard version: 0.7.0b
KDE Frameworks version (runtime): 5.43.0
KDE Frameworks version (compile time): 5.43.0
Qt version (runtime): 5.9.4
Windows runtime version (refer to QSysInfo documentation to translate code into
human readable form): 0x90
Local config directory: C:/Users/Greg's Desktop/AppData/Local
RKWard storage directory: C:/Users/Greg's Desktop/.rkward/
Backend version (as known to the frontend):
Debug message file (this may contain relevant diagnostic output in case of
trouble):
C:/Users/Greg's Desktop/AppData/Local/Temp/rkward.frontend
- backend not available or rk.sessionInfo() canceled -
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-browser-integration] [Bug 398073] Browser interaction working improperly with Google Play Music
https://bugs.kde.org/show_bug.cgi?id=398073 James Lee changed: What|Removed |Added CC||ja...@james.tl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407216] Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor
https://bugs.kde.org/show_bug.cgi?id=407216 --- Comment #6 from Danfox Davies --- System spec: Intel Core i7 8-core, 24GB RAM, NVidia GeForce GTX 1060, plenty of disk space Regarding it being kwin crashing: my bad. I will see about how to get a kwin backtrace later. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407224] ColorSpace wrong option with P3 screens
https://bugs.kde.org/show_bug.cgi?id=407224 wolthera changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||griffinval...@gmail.com Ever confirmed|0 |1 --- Comment #1 from wolthera --- Mangatengu's issue was... Images made in Krita look desaturated outside of Krita. Her display is DCI-P3 as all modern mac books, but configuring it as such was difficult because the 'use system monitor profile' actually worked against it, making Krita think it was sRGB. So what needs to be done is... 1. Figure out whether this option does anything at all on Mac, or is it only there for colord linux integration? 2. Is it having similar problems on windows? 3. Should we then hide it? Or should we clarify it? I think this is definitely a usability speed bump. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407224] New: ColorSpace wrong option with P3 screens
https://bugs.kde.org/show_bug.cgi?id=407224 Bug ID: 407224 Summary: ColorSpace wrong option with P3 screens Product: krita Version: 4.1.7 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- As discussed with Wolthera, the following option may need to be hidden on new macbooks: Color Management > Display > Use system monitor profile. After switching all the color space options to display P3 and seeing no change, I just unchecked this box and the oversaturation is gone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384470] Crash in QSGBatchRenderer::Renderer::renderBatches
https://bugs.kde.org/show_bug.cgi?id=384470 David Edmundson changed: What|Removed |Added CC||supercockga...@gmail.com --- Comment #15 from David Edmundson --- *** Bug 406137 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406137] Crash after changing visiblity of an Entrie on the systemstray
https://bugs.kde.org/show_bug.cgi?id=406137 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 384470 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370258] No option to bring forward multiple windows of the same program
https://bugs.kde.org/show_bug.cgi?id=370258 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #19 from David Edmundson --- The duplicated bugs aren't quite the same. Two are saying clicking should cycle toplevels. Generally it's wy more productive when bug reports state the problem and not propose solutions. Something this and all the duplicates do :/ I can't imagine bringing multiple windows forward at once being a good solution to anything. If I have a maximised dolphin and 2 smaller ones lower in the stack I have no way to access the ones lower in the stack. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- Not here. A bunch from the rendering every few seconds. Nothing special. Can you paste a small snippet of your "sudo strace -f -p `pidof plasmashell`" output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407216] Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor
https://bugs.kde.org/show_bug.cgi?id=407216 --- Comment #4 from Danfox Davies --- $ journalctl -f | grep --line-buffered kde May 04 20:08:52 The-Pot-of-Gold dbus-daemon[1619]: [session uid=1000 pid=1619] Activating service name='org.kde.Spectacle' requested by ':1.219' (uid=1000 pid=12144 comm="/usr/lib/x86_64-linux-gnu/qt4/bin/qdbus org.kde.Sp" label="kernel") May 04 20:08:52 The-Pot-of-Gold dbus-daemon[1619]: [session uid=1000 pid=1619] Successfully activated service 'org.kde.Spectacle' May 04 20:09:38 The-Pot-of-Gold org.kde.Spectacle[1619]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1528, resource id: 30343069, major code: 14 (GetGeometry), minor code: 0 This was the log while reproducing the crash with the Firefox window stretched across a monitor to the right. The bug is confirmed not to occur when Firefox is only on one monitor. Info from the Nvidia X Server Settings app Linux x86_64 Nividia proprietary driver 390.116 X.org 11.0 / 1.19.6 (11906000) 'Screens': 1 (but there are two full HD monitors) NV-Control 1.29 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407216] Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor
https://bugs.kde.org/show_bug.cgi?id=407216 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from David Edmundson --- >Plasmashell crashes, such that window borders are gone and windows do not >become active by being clicked on That'll be kwin crashing, not plasmashell A crash needs a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406703] VSync setting does not work after reboot
https://bugs.kde.org/show_bug.cgi?id=406703 --- Comment #2 from Andrei Rybak --- > Also, out of curiosity, why do you want full screen repaints? :-) Because without this setting, the windows tearing hurts my eyes. > Please post output of `qdbus org.kde.KWin /KWin supportInformation` before > and after applying the workaround. I'll try to get this next time I reboot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407223] New: On resize parts of Application Launcher are transparent
https://bugs.kde.org/show_bug.cgi?id=407223 Bug ID: 407223 Summary: On resize parts of Application Launcher are transparent Product: kwin Version: 5.12.7 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rybak@gmail.com Target Milestone: --- Created attachment 119844 --> https://bugs.kde.org/attachment.cgi?id=119844=edit Application Launcher opacity glitch on resize demonstration SUMMARY STEPS TO REPRODUCE 1. Add "Application Launcher" widget 2. Open "Application Launcher" panel (by clicking or via shortcut) 3. Resize it via Alt+RMB to be bigger OBSERVED RESULT Some parts of the newly resized window stay transparent. EXPECTED RESULT Widget's window has the same overall opacity. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Alt+RMB method of window resizing is not advertized enough. Found out about it just before I was going to report a duplicate of ticket https://bugs.kde.org/show_bug.cgi?id=399668 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406964] Latte dock constantly resizing when nearly out of space
https://bugs.kde.org/show_bug.cgi?id=406964 --- Comment #16 from sdfjsfjaei-h...@yahoo.de --- (In reply to Michail Vourlakos from comment #15) > In upcoming commit you will be able to choose the behavior from: > > > Auto, auto scrolling and scroll wheel does not influence scrolling > Single Axis, scrolling Tasks only with horizontal scrolling for horizontal > dock, vertical scrolling only with vertical dock > Both Axes, current behavior with no auto scrolling Nice! I'm really looking forward to that. =) -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 406268] telepathy-accounts-signon does not seem to have a build system to use
https://bugs.kde.org/show_bug.cgi?id=406268 --- Comment #3 from Michael Pyne --- Git commit 6385f5e429dd11393b48690a33d67a66edeacfd2 by Michael Pyne. Committed on 04/05/2019 at 20:15. Pushed by mpyne into branch 'master'. Add support for Meson build system. New/updated config file options: * 'configure-flags', reused as the way to pass cmdline options to the meson setup command. * 'ninja-options', a new option to pass cmdline options to the `ninja` command. Note that ninja is mandated by Meson as the underlying build tool. Tested with https://github.com/plibither8/2048.cpp Fixes #27, reviewed in !8. Test suite passes and I continue to be able to build 2048.cpp. I've also validated that ninja-options is passed to ninja when building 2048.cpp, though this was a manual verification. M +1-0CMakeLists.txt M +43 -2doc/index.docbook M +1-0modules/ksb/Application.pm M +2-1modules/ksb/BuildSystem.pm A +71 -0modules/ksb/BuildSystem/Meson.pm M +8-0modules/ksb/Module.pm M +3-2vim/syntax/kdesrc-buildrc.vim https://invent.kde.org/kde/kdesrc-build/commit/6385f5e429dd11393b48690a33d67a66edeacfd2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407219] No menu with global menu enabled
https://bugs.kde.org/show_bug.cgi?id=407219 Boudewijn Rempt changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|NOT A BUG |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407219] No menu with global menu enabled
https://bugs.kde.org/show_bug.cgi?id=407219 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Boudewijn Rempt --- If you are not a developer, you should not change metadata on a bug report. You do not have the knowledge to do so; please do not do it again. I will not look at this bug report again. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 394073] Changing the volume using the scrollwheel does not work correctly.
https://bugs.kde.org/show_bug.cgi?id=394073 --- Comment #3 from Mauro Carvalho Chehab --- (In reply to romeoK from comment #0) > Changing the volume with the scrollwheel of the mouse does not work when > pointer is inside the media window. > > You can make the scrollwheel only work like doing so: > > Go into fullscreen mode. The top menu is hidden. Now hover the mouse into > the top menu and then very carefully hover back into the media window, but > dont let the top menu dissapear. Now hover up again into the top menu, and > voila, the scrollwheel works perfectly (as long as you don't leave the > boundaries of the top menu) > > Would be nice if the scrollwheel works everywhere inside the application. I was not able to reproduce the behaviour you're describing above, but the new code should probably have fixed any misbehaviours. You should notice that the mouse wheel is context sensitive: it only change volume if inside the streaming window. If you place it on the top of a slide bar, it should be changing it; if you place inside the lateral menu, it will scroll the items there. Could you please check with the upstream code if the reported issue was gone? -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 394073] Changing the volume using the scrollwheel does not work correctly.
https://bugs.kde.org/show_bug.cgi?id=394073 --- Comment #2 from Mauro Carvalho Chehab --- (In reply to romeoK from comment #1) > Please note, that when timeshift is active, the scrollwheel is used to jump > forward/backward in the stream. This should be disabled, or it might > conflict with the volume change. Timeshift behavior was fixed on those commits: https://cgit.kde.org/kaffeine.git/commit/?id=b4e3d1c20445ca0af21a589392d5a310a42f6745 https://cgit.kde.org/kaffeine.git/commit/?id=6c7b2f361ab199a6e2bb7c60bfe9fb320c318c41 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 405277] [feature request] Configure mouse wheel action
https://bugs.kde.org/show_bug.cgi?id=405277 --- Comment #1 from Mauro Carvalho Chehab --- (In reply to higuita from comment #0) > right now the mouse scroll wheel controls the volume, i would prefer to > switch to channel switch, but right now we can't control the mouse wheel > action > > So please allow customization of the mouse wheel action Actually, the mouse scroll wheel is context-sensitive. Its action depends on where the mouse position is: - inside the channel list menu, it scrolls the channels; - on the top of the volume bar, it changes volume; - at the reproduction window, it changes the volume [1]; - at the position bar, it changes the position while playing videos [1]. [1] There was a bug there. Just fixed. It should be possible to add support for it to switch the channel, but it is not too trivial, as the media widget code is the same for both DVB and video play. Also, I'm not so sure where to add an option for such kind of configuration. If you want, feel free to submit us patches for such feature. Otherwise, I'll keep this bug opened as a reminder. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407154] Issue rendering PAL input
https://bugs.kde.org/show_bug.cgi?id=407154 emohr changed: What|Removed |Added Flags||timeline_corruption+ CC||fritzib...@gmx.net --- Comment #1 from emohr --- Please try with the current Kdenlive AppImage version 19.04.0 https://files.kde.org/kdenlive/release/ Or the Kdenlive_Nightly_Appimage https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ Environment settings: set processing threads to 1. Multithreading is not possible at the moment. Render -> tick “parallel processing” -> tick “more options” -> on the right side set threads to “0”. This is the fastest render setting. If you have problem with the rendered video untick “parallel processing”. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407219] No menu with global menu enabled
https://bugs.kde.org/show_bug.cgi?id=407219 beojan changed: What|Removed |Added Target Milestone|1.0 |--- Component|general |General Assignee|k...@davidedmundson.co.uk|krita-bugs-n...@kde.org Product|plasmashell |krita Version|5.15.4 |git master -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407219] No menu with global menu enabled
https://bugs.kde.org/show_bug.cgi?id=407219 --- Comment #2 from beojan --- I don't know why the bug exists, but it's definitely a bug in Krita because other Qt or KDE applications don't exhibit it. It's a major bug because there is no menu bar *at all*. If it were simply a case of displaying an in-window menubar, it would be a minor bug, but with no menu bar *at all*, Krita's functionality is severely limited. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407219] No menu with global menu enabled
https://bugs.kde.org/show_bug.cgi?id=407219 --- Comment #3 from beojan --- By the way, the menus work fine in Krita 4.1.8, so this is a regression. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407188] Title Clip Show background does not overlay brackgroud
https://bugs.kde.org/show_bug.cgi?id=407188 emohr changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Flags||Brainstorm+ CC||fritzib...@gmx.net --- Comment #1 from emohr --- Thanks for reporting. Tick/untick 3 times “show background” then you should see the background. Please confirm. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407204] Dissolve effect fades black.
https://bugs.kde.org/show_bug.cgi?id=407204 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||Translation_missing+ Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from emohr --- 17.12.3 is outdated. Could you try either with the 18.12.1b or the 19.04.0 AppImage version? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407011] kdenlive 18.12.3 MP4/VOB rendering looses lip sync after adding 2nd audio track
https://bugs.kde.org/show_bug.cgi?id=407011 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||Brainstorm+ --- Comment #2 from emohr --- We have still sync issues which we not really understand (3-4 frames). 19.04: The fade problem should be fixed now (today). Could you try with the nightly build tomorrow: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ . -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407193] Cursor stops working after setting render threads higher than one
https://bugs.kde.org/show_bug.cgi?id=407193 emohr changed: What|Removed |Added Flags||Translation_missing+ Resolution|--- |WAITINGFORINFO CC||fritzib...@gmx.net Status|REPORTED|NEEDSINFO --- Comment #1 from emohr --- Environment settings: set processing threads to 1. Multithreading is not possible at the moment. Render -> tick “parallel processing” -> tick “more options” -> on the right side set threads to “0”. This is the fastest render setting. If you have problem with the rendered video untick “parallel processing”. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402760] Source browse mode activated when saving the document with shortcut
https://bugs.kde.org/show_bug.cgi?id=402760 --- Comment #5 from Simone Gaiarin --- I haven't understood your point. I have not set Ctrl as a shortcut for save. I am using the default shortcuts. I compiled KDevelop from source (tag 5.3.2), and when executed it does not have this problem. Only the version installed through the package manager has it. Any idea how can I further debug this? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 338184] RFE: enable specifying custom headers
https://bugs.kde.org/show_bug.cgi?id=338184 John Scott changed: What|Removed |Added Summary|RFE: allow me specify the |RFE: enable specifying |in-reply-to/references |custom headers |headers explicitly | CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 407222] New: Ability to use clang for windows
https://bugs.kde.org/show_bug.cgi?id=407222 Bug ID: 407222 Summary: Ability to use clang for windows Product: Craft Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Core Assignee: vonr...@kde.org Reporter: jtam...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- SUMMARY The clang free compiler is available for windows as prebuilt-binaries in: http://releases.llvm.org/download.html And it uses much less disk space than any (free to test) Visual Studio. Craft can only use (from the setup): Welcome to the Craft setup wizard! Select compiler [0] Mingw-w64, [1] Microsoft Visual Studio 2017, [2] Microsoft Visual Studio 2019 (Experimental) (Default is Microsoft Visual Studio 2017): -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 407153] Kaffeine 2.0.17 fails to build with libvlc 2.2.6
https://bugs.kde.org/show_bug.cgi?id=407153
Mauro Carvalho Chehab changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kaf |https://commits.kde.org/kaf
|feine/402cbee5e675cf795b619 |feine/2644cbf02ed39bb6b194b
|b834f92aac086972afc |c6b7935b069b5769364
--- Comment #17 from Mauro Carvalho Chehab ---
Git commit 2644cbf02ed39bb6b194bc6b7935b069b5769364 by Mauro Carvalho Chehab.
Committed on 04/05/2019 at 12:35.
Pushed by mauroc into branch 'master'.
vlc: with vlc 2.x, use vlcMedia for libvlc_MediaMetaChanged event
As reported by Wolfgang, the libVlc 2.x fix applied at
402cbee5e675 ("vlc: fix support for vlc 2.x") still have issues,
causing some troubles at least on audio CDs.
The root cause seems to be that, on vlc 2.x, the event
libvlc_MediaMetaChanged should be registered against the
vlcMedia instance, instead of vlcMediaPlayer instance.
Document that inside the code, as this is not obvious.
While the old way is still supported on vlc 3.x, I opted to
keep the code inside #ifs, as some day we'll drop support for
vlc 2.x, making the code simpler.
Also, since this event is registered aganst a vlcMedia object
and behaves different than when applied against a vlcMediaPlayer
object, I'm also using a different name there, in order to avoid
confusion.
Signed-off-by: Mauro Carvalho Chehab
M +16 -4src/backend-vlc/vlcmediawidget.cpp
https://commits.kde.org/kaffeine/2644cbf02ed39bb6b194bc6b7935b069b5769364
--
You are receiving this mail because:
You are watching all bug changes.
[kaffeine] [Bug 407153] Kaffeine 2.0.17 fails to build with libvlc 2.2.6
https://bugs.kde.org/show_bug.cgi?id=407153 --- Comment #16 from Wolfgang Bauer --- (In reply to Mauro Carvalho Chehab from comment #15) > Could you please check if the enclosed patch address the issues? Yes, it indeed seems to be fine now. The playback (still) works, the mentioned error message is gone, AudioCD track changes are now announced again in Kaffeine's window. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404597] Jumpy, unpredictable zoom behavior right after canvas rotation
https://bugs.kde.org/show_bug.cgi?id=404597 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/0a552f7b729bcb ||417553ab7304a2dde6e45e9b4a Resolution|--- |FIXED --- Comment #11 from Dmitry Kazakov --- Git commit 0a552f7b729bcb417553ab7304a2dde6e45e9b4a by Dmitry Kazakov. Committed on 04/05/2019 at 17:13. Pushed by dkazakov into branch 'master'. Fix canvas jumping when zooming after canvas rotation One should avoid cycling signals carefully. The bug has been caused by commit: e7cd6d6ff4dd629f72525bd9e1cbf5d37becd965 M +3-0plugins/dockers/overview/overviewdocker_dock.cpp https://invent.kde.org/kde/krita/commit/0a552f7b729bcb417553ab7304a2dde6e45e9b4a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407219] No menu with global menu enabled
https://bugs.kde.org/show_bug.cgi?id=407219 Boudewijn Rempt changed: What|Removed |Added Component|General |general Assignee|krita-bugs-n...@kde.org |k...@davidedmundson.co.uk CC||b...@valdyas.org, ||plasma-b...@kde.org Version|git master |5.15.4 Product|krita |plasmashell Severity|major |minor Target Milestone|--- |1.0 --- Comment #1 from Boudewijn Rempt --- I'm sorry, but why do you thing this is a bug in Krita? We're using a plain old QMenu menu, like all other KDE applications. Also, this isn't a major bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403576] Cannot edit transparency masks as greyscale images when using pixel brush with wash mode.
https://bugs.kde.org/show_bug.cgi?id=403576 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/0ed30208c97a83 ||74b8c2b0b04f8d51b9b119d83b Status|ASSIGNED|RESOLVED --- Comment #10 from Dmitry Kazakov --- Git commit 0ed30208c97a8374b8c2b0b04f8d51b9b119d83b by Dmitry Kazakov. Committed on 04/05/2019 at 16:53. Pushed by dkazakov into branch 'master'. Implement a projection store for masks (for indirect painting) We have implemented correct painting on masks, but we have never implemented a projection for them. Indeed, for normal rendering process they don't need it. But when a mask is selected in isolated mode, it still needs a projection, so that the use could see the result of the painting. M +1-0libs/image/CMakeLists.txt M +8-9libs/image/KisRecycleProjectionsJob.cpp M +4-3libs/image/KisRecycleProjectionsJob.h A +283 -0libs/image/KisSafeNodeProjectionStore.cpp [License: GPL (v2+)] A +109 -0libs/image/KisSafeNodeProjectionStore.h [License: GPL (v2+)] M +14 -5libs/image/kis_base_node.cpp M +2-1libs/image/kis_base_node.h M +16 -122 libs/image/kis_layer.cc M +0-12 libs/image/kis_layer.h M +26 -12 libs/image/kis_mask.cc M +20 -2libs/image/kis_node.cpp M +4-1libs/image/kis_node.h M +5-0sdk/tests/testing_nodes.h https://invent.kde.org/kde/krita/commit/0ed30208c97a8374b8c2b0b04f8d51b9b119d83b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407221] New: Random KWin hang on VirtualDesktop RefCount
https://bugs.kde.org/show_bug.cgi?id=407221
Bug ID: 407221
Summary: Random KWin hang on VirtualDesktop RefCount
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: subd...@gmail.com
Target Milestone: ---
I have KWin hangs rather often in the last few weeks. KWin just does not react
anymore, but does not segfault. Last backtrace in frozen state gives me this:
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7feebac30932 in QtPrivate::RefCount::ref (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:54
54 inline bool ref() Q_DECL_NOTHROW {
(gdb) bt
#0 0x7feebac30932 in QtPrivate::RefCount::ref() (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:54
#1 0x7feebac4df03 in
QVector::QVector(QVector const&)
(this=0x7ffec8307cd0, v=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:359
#2 0x7feebaefc980 in KWin::Options::glPlatformInterface() const
(this=0x7ffec8307cd0) at
/home/roman/dev/kde/build/kde/workspace/kwin/kwin_autogen/EWIEGA46WW/../../../../../../src/kde/workspace/kwin/options.h:600
#3 0x7feebac3292e in KWin::Toplevel::isOnAllDesktops() const
(this=0x556355875d00) at
/home/roman/dev/kde/src/kde/workspace/kwin/toplevel.h:837
#4 0x7feebac32a5f in KWin::Toplevel::isOnDesktop(int) const
(this=0x556355875d00, d=1) at
/home/roman/dev/kde/src/kde/workspace/kwin/toplevel.h:853
#5 0x7feebacfdb16 in KWin::Placement::placeAtRandom(KWin::AbstractClient*,
QRect const&, KWin::Placement::Policy) (this=0xd0bc2af7f5e1fc00,
c=0x556355ecd240, area=...) at
/home/roman/dev/kde/src/kde/workspace/kwin/placement.cpp:165
#6 0x7feebacfde09 in KWin::Placement::placeSmart(KWin::AbstractClient*,
QRect const&, KWin::Placement::Policy) (this=0x556355ecd5f0, c=0x5563569da950,
area=...) at /home/roman/dev/kde/src/kde/workspace/kwin/placement.cpp:234
#7 0x7feebacfd561 in KWin::Placement::place(KWin::AbstractClient*, QRect&,
KWin::Placement::Policy, KWin::Placement::Policy) (this=0x556355ecd5f0,
c=0x5563569da950, area=..., policy=KWin::Placement::Smart,
nextPlacement=KWin::Placement::Unknown)
at /home/roman/dev/kde/src/kde/workspace/kwin/placement.cpp:94
#8 0x7feebacfd3a6 in KWin::Placement::place(KWin::AbstractClient*, QRect&)
(this=0x556355ecd5f0, c=0x5563569da950, area=...) at
/home/roman/dev/kde/src/kde/workspace/kwin/placement.cpp:74
#9 0x7feebae4d549 in KWin::ShellClient::doMinimize() (this=0x556355af22c0)
at /home/roman/dev/kde/src/kde/workspace/kwin/shell_client.cpp:1775
#10 0x7feebae46aed in KWin::ShellClient::init() (this=0x5563569da950) at
/home/roman/dev/kde/src/kde/workspace/kwin/shell_client.cpp:369
#11 0x7feebae59aa6 in
QTypedArrayData::iterator::operator+(int)
const (this=0x7ffec8308080, j=0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:160
#12 0x7feebae58da9 in
QVector::reallocData(int, int,
QFlags) (this=0x7feeb849dc60, asize=21859,
aalloc=1435093824, options=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h
#13 0x7feebae57c00 in
QtPrivate::SequentialContainerConverterHelper::registerConverter(int) () at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:1543
#14 0x7ffec8308120 in ()
#15 0x in ()
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 407220] New: SDDM (Breeze theme) crashes when clicking the "Different User" button.
https://bugs.kde.org/show_bug.cgi?id=407220 Bug ID: 407220 Summary: SDDM (Breeze theme) crashes when clicking the "Different User" button. Product: Breeze Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: QtQuickControls Assignee: k...@davidedmundson.co.uk Reporter: jako...@gmx.at Target Milestone: --- Created attachment 119843 --> https://bugs.kde.org/attachment.cgi?id=119843=edit journalctl output SUMMARY When pressing the "Different User" button SDDM crashes and needs to be restartet. STEPS TO REPRODUCE 1. Configure SDDM to use the Breeze theme 2. Click on the "Different User" Button. OBSERVED RESULT The screen goes to black except for the still working mouse cursor. EXPECTED RESULT Being able to select a different user to log in. SOFTWARE/OS VERSIONS Linux: Arch linux (available in About System) KDE Plasma Version: 5.15.4-1 KDE Frameworks Version: Qt Version: 5.12.3-2 SDDN Version: 0.18.1-1 ADDITIONAL INFORMATION Already posted at SDDM github page but was refered to post again here as it is a fault of the breeze theme and not SDDM itself https://github.com/sddm/sddm/issues/1162#event-2319107226 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396675] Could not save - Failed to save the annotations for layer ...
https://bugs.kde.org/show_bug.cgi?id=396675 --- Comment #10 from ocumo --- _ Argumentum ad hominem "A fallacious argumentative strategy whereby genuine discussion of the topic at hand is avoided by instead attacking the character, motive, or other attribute of the person making the argument, (...), rather than attacking the substance of the argument itself." (source: wikipedia). Q.E.D. None of what you say challenges the substance of the argument itself. Your intention is solely to offend and punish me because don't like the overwhelming argumentation I presented. According to you, my "offense" seems to be verbosity. But instead of addressing that as a criticism negative or constructively, you opt to demonstrate irrational hatred and distorted reality. In your own words, which unfortunately disprove and discredit yourself: "how you messed up your system" ...which is a lie, without any substance and disproved largely, as you have several times demonstrated it with your own words. It only intends to hurt me, as a person: "That guy messed up his system. What a ..." It is not substantiated in any reasoning that leads unequivocally to that. Or: can you explain, why is that a logical conclusion? Ergo: Ad hominem. "I am closing all reports that you made that are still open." ...just to "hurt me", not because they were fixed. So "let's punish him by hurting our project and the users!". Brilliant strategy. I will wait until you realize you are not "hurting" me. You are hurting your project, your users and your own image and reputation as leader of a relevant project for a big community. Not me. I am still waiting: don't you see it yet? I have time. What about now? Ergo: Ad hominem. The problem does exist, not in "my system". It is a bug affecting your product and your users, like it or not. Users less technically savvy and less resourceful than myself. Forget about me as a person. I am not relevant to you. Let alone the multiple experiments and evidence that can be read by everybody. Just tell them to read your words in your comment here: https://bugs.kde.org/show_bug.cgi?id=392251#c24 . Among many others. But you are trying to deflect from that. By insult. By diminishing me as an incompetent user that "messes up his system", although you have said the exact opposite many times. Deflection does works well as a strategy, but only with non intelligent, ignorant people, as any politician will tell you. But you have revealed your true position, although without justification or honest reasoning: "This is not my bug, it's somebody else's, I won't fix it." Good for you. Bad for krita. Not being right, makes you explode, so: Ad hominem. "Let's insult this guy to scare others that might come like him in the future". Bad news. You don't get to dictate what I do, what I say or where I say it. Anything. That is not how the real world works. bugs.kde.org is not your private property, neither the Internet. Equally grotesque would be me ordering you to refrain from insulting me personally and to stop believing you can give me orders or instructions, or order you to refrain from using fallacies to "argument" against concrete, objective technical issues. I would be delusional if I would think that would work. I will keep demonstrating that I am verbose with very good reasons, if and whenever I want, and you can keep demonstrating what you have demonstrated so concise but eloquently (thanks for that, really). If you would step down of such arrogant position for a little while you might find that there might be others reading your "argumentation" and find it a bit dictatorial and too obviously conveniently deviating the conversation from technically demonstrated issues. But is that how you solve issues in life? Insulting those who disagree with you or that you have offended and bullied previously? I have no idea what makes you think you command masses, but whatever it is, Well, with ignorant, low intelligence audience, fallacy, manipulation and bullying do work like a charm, I give you that. Those eventually end up following and obeying. With intelligent, highly educated people, doesn't work. So, no, I won't "obey your commands" or be intimidated by lies, attempt of bullying, threats and personal insult. Ad hominem. Shame on you. Is your next move to elevate the insulting to major cursing or lies to deflect the substance of the issue? Really you need help, at various levels. An apology wouldn't hurt you and could give better results, improving a little bit the shot you gave on your own foot and in krita project today. A person like that, who doesn't accept any criticism and uses bullying, fallacy, and personal attack as means of terminating a technical disagreement, is seriously incapable of normal, intelligent interaction with highly educated, intelligent audience. Q.E.D. _ -- You are receiving this mail because: You are watching all bug
[ark] [Bug 407007] Slow performance on opening zip file
https://bugs.kde.org/show_bug.cgi?id=407007 Elvis Angelaccio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #5 from Elvis Angelaccio --- You're welcome ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407219] New: No menu with global menu enabled
https://bugs.kde.org/show_bug.cgi?id=407219 Bug ID: 407219 Summary: No menu with global menu enabled Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: beo...@gmail.com Target Milestone: --- SUMMARY No menus are shown when a global menu plasmoid is added STEPS TO REPRODUCE 1. Add a global menu plasmoid to a Plasma panel 2. Open Krita OBSERVED RESULT No menubar in the plasmoid, no menubar in Krita EXPECTED RESULT A menubar would be displayed in the plasmoid SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.0 (available in About System) KDE Plasma Version: 5.15 KDE Frameworks Version: 5.57 Qt Version: 5.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 407007] Slow performance on opening zip file
https://bugs.kde.org/show_bug.cgi?id=407007 --- Comment #4 from Mattia --- The libzip plugin doesn't get created in Fedora RPMS because the .spec file misses libzip-devel as BuildRequires. By using the libzip plugin the performance greatly improves, so I've reported to Fedora Bugzilla a request to enable it: https://bugzilla.redhat.com/show_bug.cgi?id=1706358 I think you can close this bug here. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 406587] Autodrop stops in freecell
https://bugs.kde.org/show_bug.cgi?id=406587 Jim Sanderson changed: What|Removed |Added CC||jssalesm...@gmail.com --- Comment #9 from Jim Sanderson --- Ubuntu 19.04 (Disco Dingo) shows this behavior, also. Autodrop works correctly in other games, only Freecell seems to be affected. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407218] New: Add support for the copy_file_range syscall
https://bugs.kde.org/show_bug.cgi?id=407218 Bug ID: 407218 Summary: Add support for the copy_file_range syscall Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: ahajk...@redhat.com Target Milestone: --- Created attachment 119842 --> https://bugs.kde.org/attachment.cgi?id=119842=edit patch valgrind currently does not support copy_file_range syscall. My patch adds the support for the various architectures. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407217] Toggle Change Colors button does not toggle
https://bugs.kde.org/show_bug.cgi?id=407217 --- Comment #1 from Squeaky Pancakes --- Created attachment 119841 --> https://bugs.kde.org/attachment.cgi?id=119841=edit Toggle Change Colors button pressed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407217] New: Toggle Change Colors button does not toggle
https://bugs.kde.org/show_bug.cgi?id=407217 Bug ID: 407217 Summary: Toggle Change Colors button does not toggle Product: okular Version: 1.7.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: squeakypanca...@disroot.org Target Milestone: --- Created attachment 119840 --> https://bugs.kde.org/attachment.cgi?id=119840=edit Toggle Change Colors not pressed SUMMARY When pressing the Toggle Change Colors button it doesn't toggle on in the toolbar. STEPS TO REPRODUCE 1. Open a document 2. Add Toggle Change Colors button to toolbar 3. Click Toggle Change Colors button OBSERVED RESULT Button looks untoggled EXPECTED RESULT Button should look like it is toggled SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 394075] Mousepointer does not hide in fullscreen mode after movement.
https://bugs.kde.org/show_bug.cgi?id=394075 --- Comment #2 from Mauro Carvalho Chehab --- (In reply to romeoK from comment #1) > Since day 1 of using Kaffeine, i have this warning under > settings/diagnostic, not sure if it's related. > > [Warning ] QObject::connect: No such slot DvbTab::hideCursor() This is unrelated, and the warning was already removed on upstream version. (In reply to romeoK from comment #0) > When in fullscreen mode, the mousepointer does hide, but only until you move > it. From then it does not hide anymore. This applies to fullscreen mode only > (afair). Could you please check if this still occurs on Kaffeine 2.0.17? There were several fixes related to minimal and full screen modes since 2.0.15. Here, mousepointer is hiding fine on all modes. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 388713] Cannot set schedule through midnight
https://bugs.kde.org/show_bug.cgi?id=388713 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Mauro Carvalho Chehab --- As I was not able to reproduce this bug, I'm closing it. If you can still reproduce it on Kaffeine 2.0.17, feel free to re-open with additional details. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 393650] On scheduled recording, user can inadvertently initiate a second recording on the same channel.
https://bugs.kde.org/show_bug.cgi?id=393650 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #2 from Mauro Carvalho Chehab --- As this is the expected behavior, I'm closing this BZ. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 398949] Clean PMT for descrambled recorded programms
https://bugs.kde.org/show_bug.cgi?id=398949 Mauro Carvalho Chehab changed: What|Removed |Added Attachment #115160|0 |1 is obsolete|| --- Comment #1 from Mauro Carvalho Chehab --- Created attachment 119839 --> https://bugs.kde.org/attachment.cgi?id=119839=edit Clean PMT for descrambled recorded programms if CAM is enabled Please check if this patch works. It should be doing the same thing as yours, except that it will only strip CAM descriptors when there is a CI hardware. Unfortunately, I'm unable to test it locally, as I don't have any CI module here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407216] Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor
https://bugs.kde.org/show_bug.cgi?id=407216 --- Comment #3 from Danfox Davies --- May affect the result: there was a taskbar across the middle of the window because of where it was positioned. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407216] Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor
https://bugs.kde.org/show_bug.cgi?id=407216 --- Comment #2 from Danfox Davies --- Correction to Steps To Reproduce: step 3.5: click 'Take a new screenshot'. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407216] Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor
https://bugs.kde.org/show_bug.cgi?id=407216 --- Comment #1 from Danfox Davies --- Correction to observed result: background windows /can/ be accessed by first closing the windows in front of them, IF those windows have their own close-options in their menus. But that's obviously beside the point of the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407216] New: Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor
https://bugs.kde.org/show_bug.cgi?id=407216 Bug ID: 407216 Summary: Plasmashell crashes when screenshot taken in Spectacle of active window larger than 1 monitor Product: plasmashell Version: 5.12.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: dan...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Plasmashell crashes when a screenshot is taken in Spectacle when Spectacle is set to take a screenshot of the active window and that window is larger than 1 monitor on a multi-monitor NVidia proprietary-driver Ubuntu 18.04 + KDE system. https://bugs.kde.org/show_bug.cgi?id=406339 is similar but not the same (they report their bug in Neon Packages and not Ubuntu, also they have a different method of taking the screenshots). STEPS TO REPRODUCE 1. Stretch a Mozilla Firefox window across two screens (one above the other), leaving it as the active window. 2. Press Print Screen to bring up Spectacle. 3. Set Spectacle to take a screenshot of the active window. 4. Left click on the active window with your mouse. OBSERVED RESULT Plasmashell crashes, such that window borders are gone and windows do not become active by being clicked on. Windows can also no longer be moved around, maximised, minimised or restored. Music continues to play if it is on at the time, but one cannot access any window which was in the background or minimised or on a different workspace. Using kquitapp5 plasmashell && kstart5 plasmashell produces a new instance of plasmashell except all the previous windows are listed on the taskbar but refuse to restore or maximise, they are therefore still inaccessible. A reboot is the only way to get them back. EXPECTED RESULT A screenshot would be taken of the active window and Plasmashell would continue operating as normal. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Tried upgrading the Linux kernel from 4.20 to 5.0.12, same problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405574] Autosave doesn't work for new files, saving fails with 'Access Denied' message
https://bugs.kde.org/show_bug.cgi?id=405574 --- Comment #2 from fdbk --- Oh, thanks. Yep, suspected it was something like this, due to my %temp% location, but I thought it'd be okay because it looked like it would have write permissions, at least from the looks of Security tab in properties of c:\temp\ - Full control for Everyone, SYSTEM, Administrators and Users, and even though there were no permissions set for my user profile specifically, it's reasonable to assume that I and programs I run under that user would have those permissions inherited from permissions for all Users. Even when I set permissions specifically for my user profile, autosaving would fail. It's good to know that there will be more options for autosave location. Thank you. On Mon, Mar 18, 2019 at 4:46 PM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=405574 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > CC||b...@valdyas.org > Resolution|--- |NOT A BUG > > --- Comment #1 from Boudewijn Rempt --- > Usually, the temp folder on windows is located in > "C:/Users//AppData/Local/Temp", apparently you configured your > windows to > so it's c:\Temp, and at the same time didn't give yourself permission to > write > there. > > That's not a bug in Krita, though we could add logic to check if the temp > location is writable, and if it isn't try somewhere else, but that's a lot > of > working around a misconfiguration. > > Apart from that. there's nothing we can do, though in 4.2.0 you can also > choose > to select your c:\Users\\ as the default location fo unsaved file > autosaves. > > I've considered making it possible to configure the path where unnamed > autosave > files would be saved to, like it's possible to configure the path for swap > files (also by default the temp dir), but that would give a lot of > headaches > when it comes to user support. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406348] dolphin produces a bug instead of browsing kdeconnect device
https://bugs.kde.org/show_bug.cgi?id=406348 --- Comment #2 from Sylvain --- I am copying a few music albums and it seems to work flawlessly, at least for this time. KDEConnect 1.12.6 on mobile KDEConnect 1.3.3 on desktop The latest version of the desktop app does not feature in the LTS Kubuntu's repositories, if there's an error again I'll update to the latest version and see. I've also been willing to try FreeBSD, with Plasma, and just received today « Absolute FreeBSD 3rd edition » published last year. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407213] Using Tab to switch focus does not cycle correctly
https://bugs.kde.org/show_bug.cgi?id=407213 Julian Schraner changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||m...@xyquadrat.ch Ever confirmed|0 |1 --- Comment #1 from Julian Schraner --- Can confirm with Dolphin 19.04. This is rather weird, as Qt should default to cycle tab focus (https://doc.qt.io/qt-5/focus.html). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400979] Device Preference "Test" button ignores selected device, only plays to default
https://bugs.kde.org/show_bug.cgi?id=400979 --- Comment #2 from Jonathan Marten --- Have investigated and found a possible solution. See https://phabricator.kde.org/D21015 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 407153] Kaffeine 2.0.17 fails to build with libvlc 2.2.6
https://bugs.kde.org/show_bug.cgi?id=407153 --- Comment #15 from Mauro Carvalho Chehab --- (In reply to Wolfgang Bauer from comment #13) > (In reply to Mauro Carvalho Chehab from comment #12) > > Git commit 402cbee5e675cf795b619b834f92aac086972afc by Mauro Carvalho > > Chehab. > > Committed on 03/05/2019 at 12:11. > > Pushed by mauroc into branch 'master'. > > > > vlc: fix support for vlc 2.x > > It seems that change was not fully correct. > > Playback works now, but I still get this error message: > This object event manager doesn't know about 'MediaMetaChanged' > events04-05-19 10:05:54.006 [Warning ] kaffeine.mediawidget: Cannot attach > event handler 0 > > (only problem I noticed is that AudioCD track changes are not notified to > the user anymore, there could be more though) > > I note that the 2.0.16 code in makePlay() called > libvlc_media_event_manager(vlcMedia) to get the eventManager, while the code > in the constructor calls libvlc_media_player_event_manager(vlcMediaPlayer). > And it seems the latter doesn't know about libvlc_MediaMetaChanged in vlc > 2.x, which I assume is also the reason that playback didn't work at all in > the first place... Gah, that looks a very confusing code at 2.x... Both vlcMedia and vlcMediaPlayer uses the same events enum and shares the same event handler, but it seems they actually have a different set of events, instead of sharing a common event list! Could you please check if the enclosed patch address the issues? I ended by adding a longer comment trying to explain the issue. That should help to keep this code working if we need to do other changes there. Also, in a matter of fact, we could simply remove the #if, as the code should also work fine on 3.x, but I opted to keep them, as this would make easier if some day we decide to remove support for 2.x. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 407153] Kaffeine 2.0.17 fails to build with libvlc 2.2.6
https://bugs.kde.org/show_bug.cgi?id=407153 --- Comment #14 from Mauro Carvalho Chehab --- Created attachment 119837 --> https://bugs.kde.org/attachment.cgi?id=119837=edit Further changes to address issues with vlc 2.x -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407215] New: First level of sidebar view does not allow for keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=407215 Bug ID: 407215 Summary: First level of sidebar view does not allow for keyboard navigation Product: systemsettings Version: 5.15.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY There is currently no way to effectively navigate through the first level of sidebar view of System Settings using Tab, Shift+Tab, Ctrl+Tab, Enter, or direction keys. At most, pressing Tab once will remove focus from search bar, and Tab a few more times will cycle through the Frequently Used section with no possibility of input whatsoever aside from cycling with Tab and Shift+Tab. Ctrl+f does not bring focus back to the search field. This occurs on tree view and icon view as well. There's no indication whatsoever that Ctrl+m will bring out the Configure window under the hamburger menu, even when pressing Alt. This occurs in all view modes. This is confusing since the second and third levels of System Settings allow for keyboard navigation. This leads to two situations: *A keyboard-centric user, confronted with the first level of System Settings, sees the inability to navigate through it without the mouse, and thus thinks the rest of System Settings does not allow for keyboard navigation; or *A keyboard-centric user that accidentally finds out the second and third levels of System Settings are keyboard-navigable might expect the first level to be as well, and be frustrated with the inability to do so. It's worth mentioning that both tree view and icon view allow for basic keyboard navigation. SOFTWARE/OS VERSIONS 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-13-generic -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407160] Unexpected hiding and offsetting behaviour of active selection after performing a move action on layer with move tool
https://bugs.kde.org/show_bug.cgi?id=407160 Boudewijn Rempt changed: What|Removed |Added Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407186] kwin crash with browser open or program open
https://bugs.kde.org/show_bug.cgi?id=407186 Vlad Zagorodniy changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Vlad Zagorodniy --- crash happens in the video driver -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405693] PNG Brush tips are suddenly being recognized as GBR format instead of masks
https://bugs.kde.org/show_bug.cgi?id=405693 --- Comment #7 from Boudewijn Rempt --- Git commit eef2caf3807a8eb3a4e0ad928e7d966e1a397cf4 by Boudewijn Rempt. Committed on 04/05/2019 at 12:08. Pushed by rempt into branch 'master'. Convert the brushtip image to grayscale if it's a mask M +2-1libs/brush/kis_png_brush.cpp https://invent.kde.org/kde/krita/commit/eef2caf3807a8eb3a4e0ad928e7d966e1a397cf4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407214] New: Pressing Enter or Ctrl+Tab after typing on the filter or search fields is not very intuitive
https://bugs.kde.org/show_bug.cgi?id=407214 Bug ID: 407214 Summary: Pressing Enter or Ctrl+Tab after typing on the filter or search fields is not very intuitive Product: dolphin Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: herzensch...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY When using filter or search, there's no indicator that Enter is necessary to switch focus to the directory view, unlike with browsers, krunner, kickoff and okular. Unlike these, however, the ability to navigate through typed text in the search and filter fields seems to be desirable, considering the powerful nature of Dolphin search. Ctrl+Tab also works, but is actually more inexpected. It's typically used for switching tabs on browsers, and Dolphin itself uses it for switching tabs created with Ctrl+T. Shift+Tab eventually transfers focus to the directory view, but it requires too many presses, 3. Tab is typically expected to switch focus to other elements in typical keyboard-centered workflows, but is currently afflicted by https://bugs.kde.org/show_bug.cgi?id=407213 SUGGESTION When filter or search is highlighted, aside from Enter and Ctrl+Tab, add Tab as a key that immediately transfers focus to directory view. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407213] New: Using Tab to switch focus does not cycle correctly
https://bugs.kde.org/show_bug.cgi?id=407213 Bug ID: 407213 Summary: Using Tab to switch focus does not cycle correctly Product: dolphin Version: 18.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: herzensch...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Pressing Tab when directory view is focused transfers focus to the zoom scrollbar. Pressing Tab then goes to the Places panel and stops cycling. However: Pressing Shift+Tab when in directory view transfers focus to localization bar, wherein each of its 3 elements can be focused. Pressing Shift+Tab 3 times more transfers focus to the Places panel. Pressing Shift+Tab does not get stuck and will resume cycling, the next focus transfers being the zoom scrollbar and the directory view, continuing endlessly. STEPS TO REPRODUCE 1. Open Dolphin 2. Press Tab 2 times in order to get to Places panel. 3. Press Tab 1 time to see it does not cycle. OBSERVED RESULT Cycling through window elements in Dolphin stops after the Places panel using Tab. Cycling through window elements in Dolphin continues after the Places panel using Shift+Tab. EXPECTED RESULT Cycling through window elements in Dolphin continues after the Places panel using Tab. Cycling through window elements in Dolphin continues after the Places panel using Shift+Tab. SOFTWARE/OS VERSIONS 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-13-generic -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 205260] add full screen view
https://bugs.kde.org/show_bug.cgi?id=205260 Christian Krippendorf changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||22fe2a67bee7b67570d04d21f11 ||7eb61e3d9413f Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 407036] Akregator close tab crash
https://bugs.kde.org/show_bug.cgi?id=407036 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Wolfgang Bauer --- *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Wolfgang Bauer changed: What|Removed |Added CC||jdhayes.li...@gmail.com --- Comment #46 from Wolfgang Bauer --- *** Bug 407036 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 407190] Akregator crasht every time
https://bugs.kde.org/show_bug.cgi?id=407190 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Wolfgang Bauer --- Probably a duplicate of bug# *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Wolfgang Bauer changed: What|Removed |Added CC||c...@hetnet.nl --- Comment #45 from Wolfgang Bauer --- *** Bug 407190 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 407174] korganizer crashes on boot
https://bugs.kde.org/show_bug.cgi?id=407174 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Wolfgang Bauer --- Fixed in akonadi-calendar 19.04, a backport of the fix has been pushed to Leap 15.1 as well, so it should be fixed in the next snapshot. *** This bug has been marked as a duplicate of bug 406411 *** -- You are receiving this mail because: You are watching all bug changes.
