[plasmashell] [Bug 408049] Touch activation on touchscreen for Folder View items almost never works (does work for Desktop view and for Folder View with touchpad )
https://bugs.kde.org/show_bug.cgi?id=408049 Marian Klein changed: What|Removed |Added Summary|Touch activation for Folder |Touch activation on |View items almost never |touchscreen for Folder View |works (does work for|items almost never works |Desktop view) |(does work for Desktop view ||and for Folder View with ||touchpad ) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408052] Auto precision does not seem to update on brush size Change
https://bugs.kde.org/show_bug.cgi?id=408052 vanyossi changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408052] New: Auto precision does not seem to update on brush size Change
https://bugs.kde.org/show_bug.cgi?id=408052 Bug ID: 408052 Summary: Auto precision does not seem to update on brush size Change Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: ghe...@gmail.com Target Milestone: --- While fixing a bug I noticed the only place autoprecision is calculated is when checking the Auto precision checkbox. Resizing the brush in any way does not update precision automagically. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408049] Touch activation for Folder View items almost never works (does work for Desktop view)
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #14 from Marian Klein --- Ok I will look at it. For touchscreen users , current workaround is to switch to Desktop View temporarily when they drag new icons to Desktop. After they are finished with adding new icons they can switch immediately back to Folder View and they still can open those new icons always by single tap irrespective of System Settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408049] Touch activation for Folder View items almost never works (does work for Desktop view)
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #13 from Nate Graham --- My bad, the source file you want to look at is actually https://cgit.kde.org/plasma-desktop.git/tree/containments/desktop/package/contents/ui/FolderView.qml -- 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 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407057] I cant move my cursor using my tablet in a rectangular box on the left side of the screen it just skips over it.
https://bugs.kde.org/show_bug.cgi?id=407057 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.
[BalooWidgets] [Bug 406930] Baloo crashes on startup
https://bugs.kde.org/show_bug.cgi?id=406930 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.
[cantor] [Bug 402176] Cantor crashes when trying to execute cell with SageMath backend
https://bugs.kde.org/show_bug.cgi?id=402176 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408049] Touch activation for Folder View items almost never works (does work for Desktop view)
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #12 from Nate Graham --- Absolutely! Please feel free to. Check out https://cgit.kde.org/plasma-desktop.git/tree/desktoppackage/contents/views/Desktop.qml Side note: I know I probably came off as a bit of a jerk in your last few bug reports, and for that I apologize. When I was new to KDE, I filed a lot of similar bug reports asking for Plasma to support workarounds for issues that didn't seem like they were getting fixed fast enough. But eventually I learned that doing this is not a sustainable way to develop software, because over time it causes your codebase to become so messy and fragile that fixing issues correctly becomes practically impossible. So it's important that we not shoot ourselves in the foot by fixing things the wrong way that makes it harder to fix them in the right way later. We absolutely welcome efforts to fix bugs in the right way, though! If you haven't set up a development environment yet, check out https://community.kde.org/Get_Involved/development -- 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 #9 from Nate Graham --- (In reply to Marian Klein from comment #8) > OK, > > if you don't want to honour "force font dpi" setting > what about not to change the height of plasma panel at all when the screen > resolution changes? That would be enough for me. > > Is this an acceptable fix? If we implemented your suggestion, after reducing the screen resolution but keeping the panel height constant in millimeters by reducing the number of pixels of height, then the clock's date display would become smaller and blurrier, and a panel that was previously tall enough to have two rows of System Tray icons would be reduced in height enough to bump it down to only one row. These are all behaviors that would cause other people to file bug reports. The correct solution is to fix the bug so that you don't feel the need to work around it by changing the screen resolution or using the Force Fonts DPI setting, not put in a workaround that would cause other issues for other people. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408049] Touch activation for Folder View items almost never works (does work for Desktop view)
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #11 from Marian Klein --- Thanks Nate. Now if you don't mind me helping kde/plasma, you can point me to the relevant source files so I can start looking into it to help kde to fix it fast. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408051] New: With touch, always activate items on single-click
https://bugs.kde.org/show_bug.cgi?id=408051 Bug ID: 408051 Summary: With touch, always activate items on single-click Product: plasmashell Version: 5.15.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 When using a touchscreen, the concept of the double-click does not make sense. When the user is using the systemwide double-click setting, this should be ignored when trying to activate Folder View items with a touchscreen, and they should always be activated with a single touch. Alternatively, if it's deemed critically important to respect the single-click/double-click setting even with touch input, a double-tap should not require that the cursor click the same spot; tapping twice *anywhere* on the item should be sufficient to trigger the double-tap to activate the item. -- 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 #8 from Marian Klein --- OK, if you don't want to honour "force font dpi" setting what about not to change the height of plasma panel at all when the screen resolution changes? That would be enough for me. Is this an acceptable fix? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408049] Touch activation for Folder View items almost never works (does work for Desktop view)
https://bugs.kde.org/show_bug.cgi?id=408049 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Assignee|k...@davidedmundson.co.uk|h...@kde.org Component|general |Folder Summary|Tapping/click on any|Touch activation for Folder |application on plasma |View items almost never |desktop on touch screen |works (does work for |almost never works in |Desktop view) |Folder View in Configure| |Desktop/Wallpaper setting | |(usable for Desktop view). | Resolution|WAITINGFORINFO |--- CC||n...@kde.org Status|NEEDSINFO |CONFIRMED --- Comment #10 from Nate Graham --- No, because that would prevent people from moving files and folders to the desktop, and would be especially unwelcome for people who don't have a touchscreen device. The solution is to fix the bug, not to work around it by changing the defaults and breaking someone else. Anyway, I can confirm the bug. Touch in Folder View does not seem to work reliably. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works in Folder View in Configure Desktop/Wallpaper setting (usable for Desktop view).
https://bugs.kde.org/show_bug.cgi?id=408049 Marian Klein changed: What|Removed |Added Target Milestone|--- |1.0 Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk Component|general |general Version|unspecified |5.15.90 Product|kde |plasmashell CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works in Folder View in Configure Desktop/Wallpaper setting (usable for Desktop view).
https://bugs.kde.org/show_bug.cgi?id=408049 Marian Klein changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=407951 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 Marian Klein changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408049 --- Comment #12 from Marian Klein --- See bug #408049 https://bugs.kde.org/show_bug.cgi?id=408049 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works in Folder View in Configure Desktop/Wallpaper setting (usable for Desktop view).
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #9 from Marian Klein --- Would you consider changing the default in /usr/share/plasma/shells/org.kde.plasma.desktop/contents/defaults from [Desktop] Containment=org.kde.plasma.folder ToolBox=org.kde.desktoptoolbox RuntimePlatform=Desktop to [Desktop] Containment=org.kde.desktopcontainment ToolBox=org.kde.desktoptoolbox RuntimePlatform=Desktop Basically reverting commit https://github.com/KDE/plasma-desktop/commit/151bfb728ce8eed923f8e32ae39e345441af2f7b#diff-6366258246a7ce4ad842884ba6d6e247 until touchscreen clicks are properly fixed in Folder View. In Folder view the only way how I can launch an application by employing a touchscreen is this: I can position pointer with the mouse or touchpad on the icon (hovering) followed by a tapping either single click or double click (depending on setting in "System settings/Desktop behaviour/Workspace/click behaviour") on the icon on the touchscreen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 --- Comment #11 from Nate Graham --- (In reply to Marian Klein from comment #9) > Hi Nate. > > I am happy you have the same laptop as me, so you could test quickly. > I think the title is very specific. > How to reproduce. > > 1.) Example drag a "dolphin icon from menu/launcher" to a plasma desktop. > 2.) double click or single click on dolphin Yep, I can confirm that this is broken with Folder view, but it does work with Desktop view. Please file a new bug report on Plasmashell | Folder describing this (and only this) issue. If you have any other touch-related issues, please file additional bugs for them. Thanks! -- 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 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #7 from Nate Graham --- Plasma core developers say it's not recommended. I understand that it is very frustrating to have your bugs closed with no satisfactory resolution since from your perspective it's still broken. However it's important to understand how bug reporting systems work. It may help to read https://community.kde.org/Get_Involved/Bug_Reporting#Understand_what_the_resolution_statuses_mean For this particular bug, the situation is a bit complex for both technical and political reasons. We are not going to make Plasma respond to the Force Fonts DPI control because it's not supposed to do that. I'm totally with you that this control should probably not even exist, but that's another matter. The correct solution for your problem is to make Plasma respond properly to the official scaling setting. This already works on Wayland, but does not work on X; see bug 356446 for more details. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #34 from caulier.gil...@gmail.com --- Maik, It was a false compilation error in fact. The PKG build script use a git cache to speed up and of course the build directory compiled with older XCode from digiKam core was not cleaned. All compile fine now, but CLang generate one million of warnings. This must be fixed ain all case. Updated 6.2.0 pre release PKG will be online in few minutes : https://files.kde.org/digikam/ Gilles Caulier -- 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 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 408050] New: Cannot open any files (QTemporaryFile::exists() returns false)
https://bugs.kde.org/show_bug.cgi?id=408050 Bug ID: 408050 Summary: Cannot open any files (QTemporaryFile::exists() returns false) Product: umbrello Version: 2.27.2 (KDE Applications 18.12.2) Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: kgame...@hotmail.com Target Milestone: --- Created attachment 120367 --> https://bugs.kde.org/attachment.cgi?id=120367=edit Sample xmi file to show problem - but happens with any file. SUMMARY Cannot open any files. Files can be saved. STEPS TO REPRODUCE 1. Open umbrello 2. Open file OBSERVED RESULT Error dialog shows up: The file does not exist EXPECTED RESULT File should open SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Release 29; Umbrello: 2.27.2 / Fedora package: umbrello-18.12.2-1.fc29.src.rpm (available in About System): KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Error dialog is thrown in line 517 of umldoc.cpp as tmpfile.exists() (in line 512) returns false I can use gdb to manually jump from 512 to 537 and am able to open files. To reproduce... 1. Install debuginfo files for umbrello (and qt5-core) 2. Break at *0x5565b37b (break *0x5565b37b) 3. Jump past if block (j *0x5565b396) For some reason tmpfile::exists() suddenly reports false in line 512. file.exists() reports true in the same line! I reported the bug to redhat/fedora (https://bugzilla.redhat.com/show_bug.cgi?id=1711446) - but they requested that it be filed here also/instead. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works in Folder View in Configure Desktop/Wallpaper setting (usable for Desktop view).
https://bugs.kde.org/show_bug.cgi?id=408049 Marian Klein changed: What|Removed |Added Summary|Tapping/click on any|Tapping/click on any |application on plasma |application on plasma |desktop on touch screen |desktop on touch screen |almost never works. |almost never works in ||Folder View in Configure ||Desktop/Wallpaper setting ||(usable for Desktop view). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #8 from Marian Klein --- Under the "Desktop view" a)The icons dragged onto desktop are stored ~/.local/share/plasma_icons/ b) Icons from ~/.local/share/plasma_icons/ are only displayed on desktop c) Icons get activated/launched always by single click not respecting "system settings/Desktop behaviour/click behaviour" d) Touchscreen works for launching an app by single tapping. Under the "Folder view" a) Dragged icons are stored into ~/Desktop b) Icons from both ~/.local/share/plasma_icons/ and ~/Desktop are displayed on Desktop. c) Only icons from ~/.local/share/plasma_icons/ work with touchscreen (single click) Icons in ~/Desktop are not possible to launch with touchscreen d) this is the default out-of-box setting in "Configure desktop" preventing to place new icons into -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #7 from Marian Klein --- Thanks,I learned something new. This is a mess. So there are two types of icons? Those dragged to desktop with Folder view and those with desktop view? What is the rationale for having those two views and what should be a difference between those two views? This is not user friendly at all. Out of the box setting for KDE/neon/kubuntu should be such that launching an app with tapping/clicking on touchscreen works out-of-the-box reliably and consistently in both views as is the case for mouse/touchpad. Touchscreen now works with one of those (the other one from what was a default option, I lost track of what was original default setting ), but it does not respect single/double click setting in system settings. It always open with single click. why? Launching an app with mouse/touchpad works in both views, but touchscreen with one of those only. Why? This needs to be consistent and reliable. What is the reason for not having consistent behaviour? Also I noticed when I dragged the dolphin icon in one of those view I got huge icon, but this is probably related to my "force font dpi=288" option. I have a hidpi laptop and setting 3840x2160 monitor? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #25 from Brian --- Created attachment 120366 --> https://bugs.kde.org/attachment.cgi?id=120366=edit Logfile which includes period when the focus issue occured. Not sure if this has any related errors to the focus bug, however there was some other issues during the time that i was testing, and i did encounter the focus bug with Minecraft, Steam, And Firefox. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #6 from Christoph Feck --- "Configure Desktop" is in the desktop's right-click menu. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #5 from Marian Klein --- Thank you for you reply. I cannot see "Configure Desktop > Wallpaper" in system settings. Can you correct yourself or be more specific where it is? I use out of the box setting for neon and for kubuntu 19.04 I use either kubuntu or breze theme. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #4 from Marian Klein --- Thank you for you reply. I cannot see "Configure Desktop > Wallpaper" in system settings. Can you correct yourself or be more specific where it is? I use out of the box setting for neon and for kubuntu 19.04 I use either kubuntu or breze theme. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Christoph Feck --- Click handling on the desktop depends on which desktop layout you are using (folder view or a regular desktop). Please check Configure Desktop > Wallpaper. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 Marian Klein changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #2 from Marian Klein --- opening the same app on the touchscreen works via the menu/launcher/dashboard with single click. It is just when the icon is on the desktop it does not work. I noticed sometimes it does for me, but most of the time it DOES not. It is very unreliable. I believe it is something to do with the focus, the icon gets when mouse is hovered over the icon, but the focus/hover is not received when you use touchscreen. Hence the click action and app activation is not working. Can someone with touchscreen to reproduce and confirm this problem? Also once confirmed can someone re-assign it to the correct team? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 408045] "Bit edit" checkboxes have uneven borders when desktop scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=408045 Christoph Feck changed: What|Removed |Added Status|REPORTED|CONFIRMED Keywords||junior-jobs Ever confirmed|0 |1 --- Comment #2 from Christoph Feck --- Enabling antialiasing in BitButton::paintEvent() should give better rendering with fractional scaling. https://cgit.kde.org/kcalc.git/tree/kcalc_bitset.cpp#n42 https://doc.qt.io/qt-5/qpainter.html#rendering-quality -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 --- Comment #1 from Marian Klein --- To be clear the 4) point you click/tap on touchscreen. 4.) Depending on your settings in "System settings/Desktop behaviour/Workspace/" a)Single click to open files and folders b)Double click to open files and folders/single click select either try to double click or single click on the dropped icon on desktop by using touch screen. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408049] New: Tapping/click on any application on plasma desktop on touch screen almost never works.
https://bugs.kde.org/show_bug.cgi?id=408049 Bug ID: 408049 Summary: Tapping/click on any application on plasma desktop on touch screen almost never works. Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mkleins...@gmail.com Target Milestone: --- SUMMARY Opening/launching an app does not work with touchscreen. STEPS TO REPRODUCE 1. Get a laptop/convertible with a touchscreen. (I have HP spectre x360 convertible) 2.) install neon-developer-20190514-0001.iso (or alternativally install into virtual box) 3.) After booting the system pick an application from the menu. and drag it onto desktop. (I am picking a dolphin app from menu/launcher/dashboard.) You can choose any app. Problem does not depend on the app. I drag a dolphin icon from menu/launcher/dashboard to a plasma desktop. 4.) Depending on your settings in "System settings/Desktop behaviour/Workspace/" a)Single click to open files and folders b)Double click to open files and folders/single click select either try to double click or single click on the dropped icon on desktop. OBSERVED RESULT Dolphin Does not open. EXPECTED RESULT Dolphin should open. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 Kernel Version: 5.0.0-15-lowlatency OS Type: 64-bit Processor: 1 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 3.9 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 --- Comment #10 from Marian Klein --- Can you advise what is the best component in plasma to assign this? This is not a specific app. This is actual plasma desktop thing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 --- Comment #9 from Marian Klein --- Hi Nate. I am happy you have the same laptop as me, so you could test quickly. I think the title is very specific. How to reproduce. 1.) Example drag a "dolphin icon from menu/launcher" to a plasma desktop. 2.) double click or single click on dolphin Just because something is a big area to work, it is a bug. It is a bug, because for gnome it works. Reopen it and keep this bug open. -- 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 Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #6 from Marian Klein --- Who said it is not recommended? Why the "force font DPI" is in the system then? Remove it then. Even if something is not recommended as you said and system allows it and system misbehave when it is used then it is still bug. I am not happy you keep closing the valid bugs for me. Do you want to keep your bug list short? I am reporting the problem from the user perspective as it is the status now, not from ideal design perspective far in the future. So do a temporary fix now and then you revisit later. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407554] Crashed when creating a text after autosaving on a document has a selection somewhere
https://bugs.kde.org/show_bug.cgi?id=407554 --- Comment #9 from acc4commissi...@gmail.com --- It seems that you don't have to autosave the document... Make a selection > Save or Autosave > Stay or Deselect (Either ways it crashes) > Create a text > Crash And it doesn't seem to affect the other documents in current krita instance. The problem happens only in the document that the selection-save action has been done in. -- 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 #6 from Sergio --- On 28/05/19 23:51, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=407998 > > --- Comment #5 from Nate Graham --- >> I find it strange that they do not do so for KDE Applications > I suspect that it's partially a resourcing issue and partially because > there's much less urgency compared to a web browser, which is the #1 attack > vector on most computers. I also tend to see it as a resourcing issue. But KDE Applications also happen to include a browser (konqueror) and an email client (kmail). >> Still, if a distro makes the choice of staying with an outdated version that >> is not updated upstream, that should mean providing some sort of downstream >> support. > That's not really how it works. If distros choose to package old versions of > our software, that doesn't (and shouldn't) create any kind of obligation on > our > part to provide patches. I know that there is no "obligation" from distros. I have not expressed myself correctly, sorry. What I meant is that if some user can find low risk patches for the unsupported version they ship (as I was trying to do), they should at least consider applying it downstream. For instance (with some resistance because of the SRU) they did when it was impossible to duplex. > The IMO correct way to resolve this situation--if it > needs resolving--would be to alter the KDE apps release model to have LTS > releases like Plasma has. Then distros that insist on shipping old stuff can > lock themselves into the LTS version of our apps and receive a steady stream > of > bugfixes, just like they do with Plasma. > Then again, this wouldn't help you since the scaling chooser was a new > feature, > not a bugfix--so you'd need a newer major version anyway. > The scaling chooser is a new feature, but avoiding scaling something that should obviously not be scaled (and so avoiding the waste of a lot of ink and paper) looks more like a bugfix. So there is a chance that an LTS policy could still help! In any case, right now, I am working around the issue using okular as a viewer and FoxitReader for Linux to print. Hope I'll not have to do it until Ubuntu 19.10! ;-) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408048] New: Selection by words is sticky in Midnight Commander
https://bugs.kde.org/show_bug.cgi?id=408048 Bug ID: 408048 Summary: Selection by words is sticky in Midnight Commander Product: konsole Version: 18.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: andy...@mail.ru Target Milestone: --- SUMMARY Somewhere between Konsole 18.04.3 in Kubuntu 18.10 and 18.12.3 in Kubuntu 19.04, selecting text with mouse in Midnight Commander running in Konsole or Yakuake became sticky. This is super annoying. STEPS TO REPRODUCE 1. Start Konsole, run "mc". 2. In Midnight Commander, open a text file and start typing. 3. Select a piece of text by pressing Shift, Left mouse button and moving the mouse. Notice that selection is adjusted by character, you can start and end selection in the middle of a word. 4. Select a word in the text by pressing Shift and double-clicking Left mouse button on the word. The whole word is selected. 5. Try again to select a piece of text, like in step 3. OBSERVED RESULT In step 5, moving the mouse selects text by words, not by characters. You can try starting the selection multiple times, every time it will select text by words. It is not possible to restore the original behavior of selection by characters, except by Left clicking somewhere in the text. EXPECTED RESULT 1. Shift + Left click should always start selection by character. 2. Shift + Double left click should always start selection by words. The two rules should be true no matter what kind of selection had been done before. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Walter Lapchynski changed: What|Removed |Added CC||w...@ubuntu.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #85 from Lastique --- Created attachment 120365 --> https://bugs.kde.org/attachment.cgi?id=120365=edit Konsole with Midnight Commander correct For reference, this is how it should look. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #84 from Lastique --- Created attachment 120364 --> https://bugs.kde.org/attachment.cgi?id=120364=edit Konsole with Midnight Commander garbled In my case, --notransparency helps with raw console output, but running e.g. Midnight Commander shows somewhat garbled output with some rows and columns around characters undrawn. See the attached screenshot, it is with scaling factor 1.7. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408047] New: Rendering scripts
https://bugs.kde.org/show_bug.cgi?id=408047 Bug ID: 408047 Summary: Rendering scripts Product: kdenlive Version: 19.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: promike1...@gmail.com Target Milestone: --- SUMMARY This is the case when I can't tell if this is a bug or a feature. It didn't use to be like this and I can't use it the way I'd like to. STEPS TO REPRODUCE I generated scripts because I have more flexibility in the terminal. I could schedule them and decide what to do after that. If I click on the 'Generate Script' button, it asks for the name of this rendering. I also see the pending renderings in the 'Scripts' tab but I don't get a shell script (something.sh) EXPECTED RESULT Either asks for the location of the script or place it automatically to a sane location. (the former is more reasonable) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Have a nice day :) -- 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 #49 from Guilherme Almeida --- (In reply to Erik Kurzinger from comment #48) > (In reply to Guilherme Almeida from comment #47) > > (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 confirm that, Luca. Using PRIME on Manjaro 18.0.4, I changed > > /etc/modprobe.d/nvidia-drm.conf, setting like this options nvidia_drm > > modeset=0 and the the frezze has stoped. I haven't noticed tearing so far, > > but if happens I will edit this reply. > > Note that the reason this resolves the issue is that is disables PRIME > synchronization entirely (see > https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime- > synchronization/ for details). So tearing would be expected, since this is > how the NVIDIA driver is made aware of each vblank by the Intel driver. > > Only disabling vsync for the QtQuick pop-ups would definitely be a > preferable solution, I think. Yeah, I've noticed... Is strange that this problem affects users from differents ways? I mean... One user reported (https://forum.manjaro.org/t/kde-plasma-freeze-when-i-use-screen-edges-kwin-hang-regression/88897/31?u=fvguilherme) that simple install kwin-lowlatency from AUR instead of kwin has solved the problem. and yes, I've noticed a little horizontal tearing. I choose keep the freeze. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408041] Brush freezes when attempting to paint.
https://bugs.kde.org/show_bug.cgi?id=408041 tus...@vista.aero changed: What|Removed |Added CC||tus...@vista.aero --- Comment #3 from tus...@vista.aero --- Does this happen only when you are using then pen, or the mouse as well? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 407407] No way to un-bind an existing shortcut when being notified of a conflict
https://bugs.kde.org/show_bug.cgi?id=407407 Nate Graham changed: What|Removed |Added Summary|No way to suppress Shortcut |No way to un-bind an |is a design flow ...|existing shortcut when ||being notified of a ||conflict -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 407407] No way to suppress Shortcut is a design flow ...
https://bugs.kde.org/show_bug.cgi?id=407407 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- I don't have or use VSCode; could you describe how they handle it, or better yet, add a screenshot? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407409] Discover lists Snap packages without icon in search results
https://bugs.kde.org/show_bug.cgi?id=407409 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 CC||n...@kde.org Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- LOL I see the opposite problem: the list entry has an icon, but the app page doesn't! -- 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 #5 from Nate Graham --- > I find it strange that they do not do so for KDE Applications I suspect that it's partially a resourcing issue and partially because there's much less urgency compared to a web browser, which is the #1 attack vector on most computers. > Still, if a distro makes the choice of staying with an outdated version that > is not updated upstream, that should mean providing some sort of downstream > support. That's not really how it works. If distros choose to package old versions of our software, that doesn't (and shouldn't) create any kind of obligation on our part to provide patches. The IMO correct way to resolve this situation--if it needs resolving--would be to alter the KDE apps release model to have LTS releases like Plasma has. Then distros that insist on shipping old stuff can lock themselves into the LTS version of our apps and receive a steady stream of bugfixes, just like they do with Plasma. Then again, this wouldn't help you since the scaling chooser was a new feature, not a bugfix--so you'd need a newer major version anyway. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407410] After you check a Snap permission and cancel the password dialog to apply it, Discover shows such permission as checked until you leave the app description page and reopen it
https://bugs.kde.org/show_bug.cgi?id=407410 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- 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 #4 from Sergio --- I was expecting something like that. There is a lot of other software that has a similar development model and for them in many notable cases distros make the choice of "following the most recent stable" even if they are LTS or anyway non-rolling releases. A typical case is "firefox". I find it strange that they do not do so for KDE Applications. And I find it even weirder that Ubuntu does it (somehow) with its KDE PPAs for plasma and framework, but does not do it for applications. Still, if a distro makes the choice of staying with an outdated version that is not updated upstream, that should mean providing some sort of downstream support. This is why I was asking if you expect my issue to be fixable with a simple patch downstream. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407423] Add a Show/Hide feature to the notification "Packages to remove"
https://bugs.kde.org/show_bug.cgi?id=407423 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org --- Comment #1 from Nate Graham --- A few releases ago, the pop-up only did show packages to remove, which resulted in extremely scary situations like this: The following packages will be removed: * Plasma-desktop By displaying the added packages, we made it instead say: The following packages will be removed: * Plasma-desktop The following packages will be added: * Plasma-desktop-whatever ...Which made it easy to see that nothing was actually being removed, it's just that a package was basing renamed or something. However I can see how this causes a UX regression when the a replacement or removal transaction also includes a lot of added packages. Sort of a tricky problem. Like you suggest, maybe we could make it say: The following packages will be added: * package1 * package2 * package3 * package3 * package5 [Show full list] -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 408045] "Bit edit" checkboxes have uneven borders when desktop scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=408045 --- Comment #1 from Lastique --- Created attachment 120363 --> https://bugs.kde.org/attachment.cgi?id=120363=edit KCalc with uneven Bit Edit checkbox borders -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408046] New: Stem audio export won't work
https://bugs.kde.org/show_bug.cgi?id=408046 Bug ID: 408046 Summary: Stem audio export won't work Product: kdenlive Version: 19.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: promike1...@gmail.com Target Milestone: --- SUMMARY Stem audio export seems to be broken. STEPS TO REPRODUCE Try exporting audio stems. You'll end up having a single audio file. OBSERVED RESULT Kdenlive renders a single mixed-down stereo audio file. (Basically this checkbox is not doing anything right now) EXPECTED RESULT Kdenlive should render separate audio tracks SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Thank you for your hard work. I do enjoy using the latest release! Keep up the good work -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 408045] New: "Bit edit" checkboxes have uneven borders when desktop scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=408045 Bug ID: 408045 Summary: "Bit edit" checkboxes have uneven borders when desktop scaling is enabled Product: kcalc Version: 18.12 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: andy...@mail.ru Target Milestone: --- SUMMARY When desktop scaling is enabled, "Bit edit" checkboxes have uneven border widths. See attached screenshot. STEPS TO REPRODUCE 1. Go to KDE System Settings -> Display and Monitor -> Scale Display. 2. Select scale factor greater than 1.0. I used 1.7. 3. Reboot. 4. Launch KCalc. Make sure it is in Numerical System Mode and Show Bit Edit is enabled. OBSERVED RESULT Bit edit checkboxes have borders of uneven width, as if scaled using nearest neighbour filter. EXPECTED RESULT The checkboxes should be drawn according to the scaling factor, not scaled post-drawing. This would result in a more uniform look of the checkboxes. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 KCalc: 18.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407889] Shift-clicking in folder view with list view mode stops working properly after a restart
https://bugs.kde.org/show_bug.cgi?id=407889 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407886] Hovering over or selecting items inside a folder view in list view mode with the cursor is very unreliable
https://bugs.kde.org/show_bug.cgi?id=407886 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407888] Items remain with a different "strong" highlight color after drag-and-dropping them
https://bugs.kde.org/show_bug.cgi?id=407888 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- 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 #48 from Erik Kurzinger --- (In reply to Guilherme Almeida from comment #47) > (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 confirm that, Luca. Using PRIME on Manjaro 18.0.4, I changed > /etc/modprobe.d/nvidia-drm.conf, setting like this options nvidia_drm > modeset=0 and the the frezze has stoped. I haven't noticed tearing so far, > but if happens I will edit this reply. Note that the reason this resolves the issue is that is disables PRIME synchronization entirely (see https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime-synchronization/ for details). So tearing would be expected, since this is how the NVIDIA driver is made aware of each vblank by the Intel driver. Only disabling vsync for the QtQuick pop-ups would definitely be a preferable solution, I think. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 Nate Graham changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #8 from Nate Graham --- There are definitely real bugs here. I have exactly the same hardware as you (HP Spectre x360 convertible) so I'm quite aware of how much work needs to be done. However this bug report is not actionable because it does not track one specific issue that can be resolved. "Make everything work with touch" is too broad. Please file individual bugs for the apps and plasma components where you find that touch support out-of-the box is lacking. Thanks! -- 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 Nate Graham changed: What|Removed |Added Resolution|--- |NOT A BUG CC||n...@kde.org Status|REPORTED|RESOLVED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=356446 --- Comment #5 from Nate Graham --- > Modern HiDpi laptops/tablets/convertibles need to set higher value in force > fonts DPI in systems setting. Actually that's not the recommend way to achieve high DPI scaling. You should be using the Screen scaling system in System Settings > Display & Monitor > Scale Display. If you are unable or willing to use this because of outstanding bugs, those should be filed rather than resorting to the use of the Force Fonts DPI control. The bug that tracks Plasma not working with it on X11 is Bug 356446 (it works fine on Wayland). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham 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.
[yakuake] [Bug 388217] Yakuake height incorrect if desktop scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=388217 --- Comment #6 from Lastique --- While that works as a workaround, it keeps Yakuake UI elements unscaled. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #33 from Maik Qualmann --- I will try the days CLANG. If I understand correctly, there is a problem with the debug macros, but why? Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407881] new notifications system does not work with Snap package of Discord
https://bugs.kde.org/show_bug.cgi?id=407881 Kai Uwe Broulik changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #6 from Kai Uwe Broulik --- Thank you very much! From the output I can tell that it asks us to replace an existing notification with ID 1767 with a new one. Testing suggests that when replacing a non-existing notification we end up not displaying anything. The notification spec isn't clear about how to deal with that situation but given it describes it as "An optional ID of an existing notification that this notification is intended to replace." and the fact that it previously worked, I'll adjust our system to just add a new notification in this case. This is still an application bug imho as I have never seen any application do that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408043] Krita 4.2.0 crashes on closing
https://bugs.kde.org/show_bug.cgi?id=408043 --- Comment #4 from Heiko Becker --- Doesn't seem so, it only throws some python error at me: [cut away similar messages] NOT COOL: Duplicated action name from xml data: "execute_script_9" NOT COOL: Duplicated action name from xml data: "execute_script_10" NOT COOL: Duplicated action name from xml data: "krita_filter_threshold" krita.lib.widgets: The file could not be parsed. QObject::startTimer: Timers cannot have negative intervals /tmp/.mount_krita-IILTfz/usr/lib/krita-python-libs/krita added to PYTHONPATH Exception ignored in: Traceback (most recent call last): File "/tmp/.mount_krita-IILTfz/usr/lib/python3.5/threading.py", line 1283, in _shutdown assert tlock.locked() SystemError: returned a result with an error set -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408044] No icon for Paste Reference Image From System Clipboard
https://bugs.kde.org/show_bug.cgi?id=408044 --- Comment #2 from Dmitry Utkin --- MR: https://invent.kde.org/kde/krita/merge_requests/34 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #32 from caulier.gil...@gmail.com --- This is the CLang version from XCode : bash-3.2$ clang --version Apple LLVM version 10.0.1 (clang-1001.0.46.4) Target: x86_64-apple-darwin18.6.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin bash-3.2$ Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #31 from caulier.gil...@gmail.com --- yes, but i's not enough : /opt/digikam/libexec/qt5/lib/QtWidgets.framework/Headers/qabstractitemview.h:349:10: note: overridden virtual function is here bool eventFilter(QObject *object, QEvent *event) override; ^ In file included from /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.cpp:23: /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.h:70:42: warning: 'dragDropHandler' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] virtual AbstractItemDragDropHandler* dragDropHandler() const; ^ /Users/gilles/dktemp/digikam-master/core/libs/widgets/common/dragdropimplementations.h:119:42: note: overridden virtual function is here virtual AbstractItemDragDropHandler* dragDropHandler() const = 0; ^ In file included from /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.cpp:23: /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.h:71:25: warning: 'mapIndexForDragDrop' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] virtual QModelIndex mapIndexForDragDrop(const QModelIndex& index) const; ^ /Users/gilles/dktemp/digikam-master/core/libs/widgets/common/dragdropimplementations.h:125:25: note: overridden virtual function is here virtual QModelIndex mapIndexForDragDrop(const QModelIndex& index) const = 0; ^ In file included from /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.cpp:23: /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.h:72:25: warning: 'pixmapForDrag' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] virtual QPixmap pixmapForDrag(const QList& indexes) const; ^ /Users/gilles/dktemp/digikam-master/core/libs/widgets/common/dragdropimplementations.h:130:25: note: overridden virtual function is here virtual QPixmap pixmapForDrag(const QList& indexes) const = 0; ^ In file included from /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.cpp:23: /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.h:73:18: warning: 'wheelEvent' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] virtual void wheelEvent(QWheelEvent* event); ^ /opt/digikam/libexec/qt5/lib/QtWidgets.framework/Headers/qabstractscrollarea.h:120:10: note: overridden virtual function is here void wheelEvent(QWheelEvent *) override; ^ In file included from /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.cpp:23: /Users/gilles/dktemp/digikam-master/core/app/views/tableview/tableview_treeview.h:75:18: warning: 'hasHiddenGroupedImages' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] virtual bool hasHiddenGroupedImages(const ItemInfo& info) const; ^ /Users/gilles/dktemp/digikam-master/core/app/items/utils/groupingviewimplementation.h:48:19: note: overridden virtual function is here virtual bool hasHiddenGroupedImages(const ItemInfo&) const ^ [ 59%] Automatic MOC for target Editor_ShearTool_Plugin [ 59%] Built target Editor_ShearTool_Plugin_autogen [ 59%] Building CXX object core/app/CMakeFiles/digikamgui_src.dir/views/tableview/tableview_column_geo.cpp.o 6 warnings generated. [ 59%] Building CXX object core/app/CMakeFiles/digikamgui_src.dir/views/tableview/tableview_column_digikam.cpp.o [ 59%] Automatic MOC for target showfoto [ 59%] Built target showfoto_autogen Scanning dependencies of target digikamdatabase [ 59%] Building CXX object core/libs/database/CMakeFiles/digikamdatabase.dir/digikamdatabase_autogen/mocs_compilation.cpp.o 5 warnings generated. [ 59%] Linking CXX shared library libdigikamdatabase.dylib Undefined symbols for architecture x86_64: "DIGIKAM_DBJOB_LOG()", referenced from: Digikam::SearchesJob::run() in dbjob.cpp.o "DIGIKAM_COREDB_LOG()", referenced from: Digikam::CoreDbPrivilegesChecker::checkPriv(Digikam::CoreDbBackend&, QString const&) in coredbchecker.cpp.o Digikam::CoreDbCopyManager::copyTable(Digikam::CoreDbBackend&, QString const&, Digikam::CoreDbBackend&, QString const&) in coredbcopymanager.cpp.o Digikam::CoreDbSchemaUpdater::update() in coredbschemaupdater.cpp.o Digikam::CoreDbSchemaUpdater::startUpdates() in coredbschemaupdater.cpp.o Digikam::CoreDbSchemaUpdater::makeUpdates() in coredbschemaupdater.cpp.o Digikam::CoreDbSchemaUpdater::endWrapSchemaUpdateStep(bool, QString const&) in coredbschemaupdater.cpp.o
[elisa] [Bug 407945] "Files" view shows misaligned folder names
https://bugs.kde.org/show_bug.cgi?id=407945 --- Comment #2 from Nate Graham --- Here's a patch: https://phabricator.kde.org/D21469 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408043] Krita 4.2.0 crashes on closing
https://bugs.kde.org/show_bug.cgi?id=408043 Boudewijn Rempt changed: What|Removed |Added Platform|Other |Exherbo Packages --- Comment #3 from Boudewijn Rempt --- Okay, fixed the platform. Does the appimage also crash for you? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408043] Krita 4.2.0 crashes on closing
https://bugs.kde.org/show_bug.cgi?id=408043 --- Comment #2 from Heiko Becker --- (In reply to Boudewijn Rempt from comment #1) > Which linux distribution and which version of Qt is this? Exherbo Linux and as mentioned above Qt 5.12.3. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408041] Brush freezes when attempting to paint.
https://bugs.kde.org/show_bug.cgi?id=408041 Boudewijn Rempt changed: What|Removed |Added Platform|Windows CE |MS Windows Status|REPORTED|NEEDSINFO CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO OS|Windows CE |MS Windows --- Comment #2 from Boudewijn Rempt --- please also try with 4.2.0, which we're going to release tomorrow (but you can already get it at https://download.kde.org/stable/krita/4.2.0/). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408043] Krita 4.2.0 crashes on closing
https://bugs.kde.org/show_bug.cgi?id=408043 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Which linux distribution and which version of Qt is this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408044] No icon for Paste Reference Image From System Clipboard
https://bugs.kde.org/show_bug.cgi?id=408044 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Sure. Create a merge request. that would be great -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408044] New: No icon for Paste Reference Image From System Clipboard
https://bugs.kde.org/show_bug.cgi?id=408044 Bug ID: 408044 Summary: No icon for Paste Reference Image From System Clipboard Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: loen...@gmail.com Target Milestone: --- Created attachment 120362 --> https://bugs.kde.org/attachment.cgi?id=120362=edit Screenshot with button with no icon I was testing a new feature "Paste Reference Image From System Clipboard" introduced in commit 00d3e6d939f05b28fd85eaa574ba94dd1f818c21 . It works perfectly, in exception the "paste" button has no icon and therefore looks absent (but still clickable if you have image in clipboard). It's reproducible in version krita-4.3.0-prealpha-755c59f-x86_64.appimage STEPS TO REPRODUCE 1. Copy an image to clipboard 2. Activate "References image tool" 3. Look on the Tool Options dock OBSERVED RESULT There is no button to paste, but it you hover the pointer between "Add Reference Image" and "Load Reference Images Set", a hint "Paste Reference Image >From System Clipboard" will appear and the empty button is clickable. EXPECTED RESULT There should be a button with "paste" icon. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 18.04 ADDITIONAL INFORMATION I have fixed it in my fork, may I create a merge request? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408043] New: Krita 4.2.0 crashes on closing
https://bugs.kde.org/show_bug.cgi?id=408043 Bug ID: 408043 Summary: Krita 4.2.0 crashes on closing Product: krita Version: 4.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: heire...@exherbo.org Target Milestone: --- STEPS TO REPRODUCE 1. Open krita 2. Close it again OBSERVED RESULT drkonqi informs about a crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 Backtrace: Application: krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/x86_64-pc-linux-gnu/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9b0b418ec0 (LWP 17363))] Thread 3 (Thread 0x7f9ab5ffb700 (LWP 17436)): #0 0x7f9b0fa62256 in __libc_disable_asynccancel () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6 #1 0x7f9b0fa4a14b in poll () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6 #2 0x7f9b0d5c8c8e in g_main_context_poll (priority=, n_fds=1, fds=0x7f9ad80025e0, timeout=, context=0x7f9ad80058a0) at ../glib-2.60.3/glib/gmain.c:4228 #3 g_main_context_iterate (context=context@entry=0x7f9ad80058a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.60.3/glib/gmain.c:3922 #4 0x7f9b0d5c8daf in g_main_context_iteration (context=0x7f9ad80058a0, may_block=may_block@entry=1) at ../glib-2.60.3/glib/gmain.c:3988 #5 0x7f9b0ffe709b in QEventDispatcherGlib::processEvents (this=0x7f9ad8018050, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f9b0ff8f6fb in QEventLoop::exec (this=this@entry=0x7f9ab5ffad80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f9b0fdd6201 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f9b0fdd7242 in QThreadPrivate::start (arg=0x557a25822e80) at thread/qthread_unix.cpp:364 #9 0x7f9b0def363f in start_thread () from /usr/x86_64-pc-linux-gnu/lib/libpthread.so.0 #10 0x7f9b0fa54d63 in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6 Thread 2 (Thread 0x7f9b03fff700 (LWP 17365)): #0 0x7f9b0fdd765c in QMutex::lock (this=this@entry=0x557a1aa67370) at /usr/x86_64-pc-linux-gnu/include/c++/9.1.0/bits/atomic_base.h:769 #1 0x7f9b0ffe6f8e in QMutexLocker::QMutexLocker (m=0x557a1aa67370, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:206 #2 QThreadData::canWaitLocked (this=0x557a1aa67340) at ../../include/QtCore/5.13.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:269 #3 postEventSourcePrepare (s=0x7f9afc004b80, timeout=timeout@entry=0x7f9b03ffeb84) at kernel/qeventdispatcher_glib.cpp:260 #4 0x7f9b0d5c827e in g_main_context_prepare (context=context@entry=0x7f9afc000bf0, priority=priority@entry=0x7f9b03ffec08) at ../glib-2.60.3/glib/gmain.c:3499 #5 0x7f9b0d5c8bbe in g_main_context_iterate (context=context@entry=0x7f9afc000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.60.3/glib/gmain.c:3907 #6 0x7f9b0d5c8daf in g_main_context_iteration (context=0x7f9afc000bf0, may_block=may_block@entry=1) at ../glib-2.60.3/glib/gmain.c:3988 #7 0x7f9b0ffe709b in QEventDispatcherGlib::processEvents (this=0x7f9afc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f9b0ff8f6fb in QEventLoop::exec (this=this@entry=0x7f9b03ffed40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #9 0x7f9b0fdd6201 in QThread::exec (this=this@entry=0x7f9b0dfa1dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #10 0x7f9b0df22347 in QDBusConnectionManager::run (this=0x7f9b0dfa1dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #11 0x7f9b0fdd7242 in QThreadPrivate::start (arg=0x7f9b0dfa1dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:364 #12 0x7f9b0def363f in start_thread () from /usr/x86_64-pc-linux-gnu/lib/libpthread.so.0 #13 0x7f9b0fa54d63 in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6 Thread 1 (Thread 0x7f9b0b418ec0 (LWP 17363)): [KCrash Handler] #6 QThreadStorageData::get (this=0x0) at thread/qthreadstorage.cpp:122 #7 0x7f9b0fe87e27 in QThreadStorage::hasLocalData (this=) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:141 #8 qtPcreCallback () at tools/qregularexpression.cpp:1094 #9 0x7f9b0d6f9aec in pcre2_jit_match_16 () from /usr/x86_64-pc-linux-gnu/lib/libpcre2-16.so.0 #10 0x7f9b0d6fd7c7 in pcre2_match_16 () from /usr/x86_64-pc-linux-gnu/lib/libpcre2-16.so.0 #11 0x7f9b0fe87fb8 in safe_pcre2_match_16 (code=0x557a23a10740, subject=0x557a2350c318, length=30, startOffset=0,
[kdeconnect] [Bug 400922] KDE connect spams notifications when receiving SMS
https://bugs.kde.org/show_bug.cgi?id=400922 --- Comment #7 from jw...@fastmail.fm --- I mentioned the PC reboot to confirm that the problem seems to stem from the Android side. However I cannot confirm that a restart of the app resets the popup counter. When I go into settings and click and confirm to "force stop" for KDE Connect, the app continues to run. Android 8.0.0, KDE Connect 1.12.6. On Tue, 28 May 2019, at 14:44, Derek Atkins wrote: > https://bugs.kde.org/show_bug.cgi?id=400922 > > --- Comment #6 from Derek Atkins --- > (In reply to jwala from comment #5) > > Running on PC with Arch using Xfce 4.12. Each incident seems to add 4 extra > > pop-ups, now at ~32 alerts per SMS. Do not see way to dismiss alerts beyond > > clicking on each one. Reboots of PC have not changed accumulation amounts. > > Like I said in comment #4, if you force-kill the KDE App on your Android phone > and then restart it, it should reset the counter again. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 408009] Expose rdrand and f16c even on avx if host cpu supports them
https://bugs.kde.org/show_bug.cgi?id=408009
Mark Wielaard changed:
What|Removed |Added
CC||ahajk...@redhat.com
Status|ASSIGNED|RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Mark Wielaard ---
commit 791fe5ecf909d573bcbf353b677b9404f9da0ed4
Author: Mark Wielaard
Date: Mon May 27 22:19:27 2019 +0200
Expose rdrand and f16c through cpuid also if the host only has avx.
The amd64 CPUID dirtyhelpers are mostly static since they emulate some
existing CPU "family". The avx2 ("i7-4910MQ") CPUID variant however
can "dynamicly" enable rdrand and/or f16c if the host supports them.
Do the same for the avx_and_cx16 ("i5-2300") CPUID variant.
https://bugs.kde.org/show_bug.cgi?id=408009
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 402242] Automatic tab unload
https://bugs.kde.org/show_bug.cgi?id=402242 Juraj changed: What|Removed |Added CC||sgd.or...@gmail.com --- Comment #1 from Juraj --- Hello, I put together a simple prototype (Python extension) https://www.pling.com/p/1307514/ To report an issue with it please use GitHub: https://github.com/SGOrava/Unloader -- 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 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Nate Graham --- Those versions are not maintained or even developed upstream. KDE apps have a fairly short and frequent release schedule: three major versions a year, and each major version's bugfix branch is no longer maintained after the release of the next one. It's not really ideal for LTS distros. :/ For those, you're better off using the Snap or Flatpak versions of apps if you find yourself in need of newer versions. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 --- Comment #2 from Marcos Dione --- Try here: http://dionecanali.hd.free.fr/~mdione/000x004-hillshade.tif -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408041] Brush freezes when attempting to paint.
https://bugs.kde.org/show_bug.cgi?id=408041 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Can you try to turn off OpenGL in the settings and see if the issue goes away? Sometimes old Intel graphics cards can have that issue. Maybe that is the culprit? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407340] PPC64, does not support the vlogefp, vexptefp instructions
https://bugs.kde.org/show_bug.cgi?id=407340 Carl Love changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407340] PPC64, does not support the vlogefp, vexptefp instructions
https://bugs.kde.org/show_bug.cgi?id=407340 Carl Love changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Carl Love --- VEX and test case patches committed. commit 31b3a755a93daaacbb993ffd80fb0780cc76464d Author: Carl Love Date: Tue May 28 14:03:59 2019 -0500 PPC64, Update testcases for vlogefp, vexptefp instructions https://bugs.kde.org/show_bug.cgi?id=407340 commit 3a345d9f8e8e98ee74f2c66f69ab51220cd18d47 Author: Carl Love Date: Tue May 28 14:07:04 2019 -0500 PPC64, Add support for vlogefp, vexptefp instructions Add Iop_Exp2_32Fx4 to VEX/pub/libvex_ir.h to support the 2^x instruction. Enable the existing test support for the two instructions in none/tests/ppc64/subnormal_test.c and none/tests/ppc64/jm-insns.c. https://bugs.kde.org/show_bug.cgi?id=407340 Closing bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393630] System tray icons not clickable and collapsible when an entry's visibility is changed to hidden
https://bugs.kde.org/show_bug.cgi?id=393630 --- Comment #41 from Christoph Feck --- > This bug is still present on Kubuntu LTS. Is it normal? Yes. This bug has been fixed since Plasma 5.15.1, and Kubuntu 18.04 uses Plasma 5.12. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400922] KDE connect spams notifications when receiving SMS
https://bugs.kde.org/show_bug.cgi?id=400922 --- Comment #6 from Derek Atkins --- (In reply to jwala from comment #5) > Running on PC with Arch using Xfce 4.12. Each incident seems to add 4 extra > pop-ups, now at ~32 alerts per SMS. Do not see way to dismiss alerts beyond > clicking on each one. Reboots of PC have not changed accumulation amounts. Like I said in comment #4, if you force-kill the KDE App on your Android phone and then restart it, it should reset the counter again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #30 from Maik Qualmann --- Ok, I see now that the process was already 62% and the unknown compiler option has only been treated as a warning. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407995] Crash when playing cut video with AutoTrack effect
https://bugs.kde.org/show_bug.cgi?id=407995 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #2 from Rafael Linux User --- I'm sorry, that is, Autotrack :( -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400922] KDE connect spams notifications when receiving SMS
https://bugs.kde.org/show_bug.cgi?id=400922 jw...@fastmail.fm changed: What|Removed |Added Platform|openSUSE RPMs |Archlinux Packages CC||jw...@fastmail.fm --- Comment #5 from jw...@fastmail.fm --- Running on PC with Arch using Xfce 4.12. Each incident seems to add 4 extra pop-ups, now at ~32 alerts per SMS. Do not see way to dismiss alerts beyond clicking on each one. Reboots of PC have not changed accumulation amounts. -- 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 #2 from Sergio --- Cannot believe I posted all the versions of Qt, plasma, KDE framework and I forgot the version of okular! Sorry about that. It is 1.4.3, rather dated. Looks like ubuntu provides up to date plasma and framework via its KDE backports PPA, but does not provide fresh applications. Also kubuntu disco is still at 1.6.3. So the question becomes: are the 1.4 and 1.6 series maintained upstream or downstream only? Is the newer scale mode chooser backportable by distribution? Alternatively would it be possible to at least disable the scaling in okular 1.4.x or 1.6.x when the PDF page size fits in the paper size (ignoring the printer margins) with a simple single patch that downstream can apply? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #29 from Maik Qualmann --- https://invent.kde.org/kde/digikam/commit/c061131ee1aecad1f935f87eed267430136ae056 Maik -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408042] New: Calendar cannot be fetched from server because the login credentials string is too long
https://bugs.kde.org/show_bug.cgi?id=408042
Bug ID: 408042
Summary: Calendar cannot be fetched from server because the
login credentials string is too long
Product: Akonadi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: danielinberli...@gmail.com
Target Milestone: ---
Created attachment 120361
--> https://bugs.kde.org/attachment.cgi?id=120361=edit
Text file with error message
The calendar entries cannot be fetched from server because the login
credentials string is too long. I can see all calendars in KOrganizer, but the
calendar display filed remains empty.
Reason seems to be that the domain name of the server is very long.
It is a Horde server.
The client system running Akonadi is an OpenSUSE Leap 15.1.
All other calendars from this horde system can be displayed without problems
(domain name much shorter).
Reason seems to be a database table, column remoteId is to short, see the
following error message (for data protection reasons I have replaced some
letters by x letters, but I did not change the number of letters):
2019-05-25T23:59:16.891848+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error while handling command FetchItems on
connection akonadi_davgroupware_resource_3 (0x55628b8621c0)
2019-05-25T23:59:16.895902+02:00 loa1 akonadiserver[3907]: message repeated 3
times: [ org.kde.pim.akonadiserver: Error while handling command FetchItems on
connection akonadi_davgroupware_resource_3 (0x55628b8621c0)]
2019-05-25T23:59:19.334931+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: DATABASE ERROR:
2019-05-25T23:59:19.335251+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error code: "1406"
2019-05-25T23:59:19.335417+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: DB error: "Data too long for column 'remoteId' at
row 1"
2019-05-25T23:59:19.335599+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error text: "Data too long for column 'remoteId'
at row 1 QMYSQL3: Der Befehl konnte nicht ausgeführt werden"
2019-05-25T23:59:19.335735+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(int, 0))(":1",
QVariant(QString,
"https://www.x.de/h/rpc.php/calendars/xx.xxx...@x-xxx-xxx.de/calendar~OV5Iqp6YmUNuhCyok2UpkJN/Ham4UixcxFU3Ft6PRqFr9X2.ics#04008200E00074C5B7101A82E00890B6EB6A4B4BD4011000544F59A1A0F4D341A8CF12EB09461AE62018-10-25T13:00:00+00:00;))(":2",
QVariant(QString, "\"065c4f8744e0ae5a4e2d3ea03efe3b88\""))(":3",
QVariant(QString, ""))(":4", QVariant(qlonglong, 85))(":5", QVariant(qlonglong,
3))(":6", QVariant(QDateTime, QDateTime(2019-05-25 21:59:19.334 UTC
Qt::TimeSpec(UTC(":7", QVariant(QDateTime, QDateTime(2019-05-25
21:59:19.334 UTC Qt::TimeSpec(UTC(":8", QVariant(bool, false))(":9",
QVariant(qlonglong, 0)))
2019-05-25T23:59:19.335874+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Query: "INSERT INTO PimItemTable (rev, remoteId,
remoteRevision, gid, collectionId, mimeTypeId, datetime, atime, dirty, size)
VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9)"
2019-05-25T23:59:19.336000+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error during insertion into table "PimItemTable"
"Data too long for column 'remoteId' at row 1 QMYSQL3: Der Befehl konnte nicht
ausgeführt werden"
2019-05-25T23:59:19.336129+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error while handling command CreateItem on
connection akonadi_davgroupware_resource_3 (0x55628b8621c0)
2019-05-25T23:59:19.336255+02:00 loa1 akonadi_davgroupware_resource[6897]:
org.kde.pim.akonadicore: Creating/updating items from the akonadi database
failed: "Failed to append item"
2019-05-25T23:59:19.339166+02:00 loa1 akonadi_davgroupware_resource[6897]:
org.kde.pim.akonadicore: Error during ItemSync: "Failed to append item"
I would be very thankfull if you could have a look at this.
Regards,
Daniel
--
You are receiving this mail because:
You are watching all bug changes.
[kdesvn] [Bug 401529] kdesvn commit message window should use plain-text, occasionally sends truncated commit message to svnclient
https://bugs.kde.org/show_bug.cgi?id=401529 Christian Ehrlicher changed: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||svn/d95fadbb28a19e467dad118 ||5722fc688f1c966b6 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Christian Ehrlicher --- Git commit d95fadbb28a19e467dad1185722fc688f1c966b6 by Christian Ehrlicher. Committed on 28/05/2019 at 18:59. Pushed by chehrlic into branch 'master'. Don't accept richtext in commit message dialog M +5-9src/ksvnwidgets/commitmessage.ui M +11 -7src/svnfrontend/editpropsdlg.ui https://commits.kde.org/kdesvn/d95fadbb28a19e467dad1185722fc688f1c966b6 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407995] Crash when playing cut video with AutoTrack effect
https://bugs.kde.org/show_bug.cgi?id=407995 emohr changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Flags||timeline_corruption+ Status|REPORTED|NEEDSINFO CC||fritzib...@gmx.net --- Comment #1 from emohr --- Do you mean AutoMask? I have tried with AppImage 19.04.1c and AutoMask as you descript. No crash -- You are receiving this mail because: You are watching all bug changes.
