[okular] [Bug 410723] Freehand annotation jagged lines with stylus
https://bugs.kde.org/show_bug.cgi?id=410723 --- Comment #11 from Rene --- Could it be that somehow the path is created by both the xinput device and the input fed to X's core pointer? That could explain sets of close points? On Wed, 25 Sep 2019 at 01:10, wrote: > https://bugs.kde.org/show_bug.cgi?id=410723 > > --- Comment #10 from blackdovahb...@gmail.com --- > (In reply to Oliver Sander from comment #9) > > Created attachment 122832 [details] > > Plot of the points of the spiky path > > > > I extracted the points of the problematic path from the pdf document, and > > plotted them using gnuplot. This gets us one step closer to an > explanation: > > As can be seen from the attached picture, each point is actually a pair > of > > points, a small distance apart. Together with a MiterJoin line style this > > explains the jaggedness of the resulting path. > > > > [Currently I simply assume that MiterJoin line drawing is used, but I > didn't > > check. For a 'normal' set of points on a path you wouldn't see the > > difference.] > > > > So the remaining task is to find out where these double points come > from. My > > system (which is a bleeding edge Okular on Debian Buster) doesn't produce > > them. I am tempted to conjecture that the problem is somewhere in the > lower > > layers of the tablet input stack, and not in Okular itself. > > Thank you, Oliver. By the sounds of it, I do think you're correct about the > origin of the error. It would make sense why the path would appear jagged > and > spiky because of the pair of joints. I'm not well-versed in these things > and my > understanding of it is lacking. So take my opinion with a grain of salt. > > However, I don't believe that the error is caused by the tablet itself. My > drawing pad seems to work fine in other applications that are more geared > towards drawing/art (Rene stated that it works fine for him in GIMP). This > could happen because it uses a different method for tracking paths or could > lead to an inconclusive idea that it is a problem with Okular. > > I would also like to mention that my drawing pad is of the same brand as > Rene's > but is a different model. I don't know how relevant that information is. I > suppose it's possible that this is a bug that occurs with only Wacom > tablets. I > don't know how likely that would be. > > Drawing in Okular before I upgraded from Ubuntu 18.04 to Ubuntu 19.04, I > had no > issues. The error only came to be after upgrading my OS. This leaves me to > believe (though I may be incorrect) that this isn't an issue with the > drawing > tablets but something else. I would also like to reiterate that this only > occurred after upgrading my OS (the same thing happened in Rene's case). I > don't know why that is but I do think that it's quite strange and could > have > something to do with the bug. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412293] Image editor Tools sidebar width not restored
https://bugs.kde.org/show_bug.cgi?id=412293 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- I'm actually sure that there was no change compared to the 6.3.0. The sidebar strategy was always scaled down to a minimum size, but no scroll bars were visible. The idea is to provide maximum area for the image. I'll take a look at it this evening. Maik -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 410742] Externally-opened files no longer open in existing window
https://bugs.kde.org/show_bug.cgi?id=410742 Dominik Haumann changed: What|Removed |Added CC||zmo...@hotmail.com --- Comment #8 from Dominik Haumann --- *** Bug 412288 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412288] Kate ignores already running instance and opens document in a new window
https://bugs.kde.org/show_bug.cgi?id=412288 Dominik Haumann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE Latest Commit||https://cgit.kde.org/kate.g ||it/commit/?h=Applications/1 ||9.08&id=636af882e3c936411f5 ||6069585940901b39628d1 --- Comment #2 from Dominik Haumann --- *** This bug has been marked as a duplicate of bug 410742 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412288] Kate ignores already running instance and opens document in a new window
https://bugs.kde.org/show_bug.cgi?id=412288 --- Comment #1 from Dominik Haumann --- Following the discussion in https://www.reddit.com/r/kde/comments/d8fhdo/kate_from_the_command_line_no_longer_opens_in/ this should be fixed in some 19.08.x release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412276] no root access from normal user login using plasma 5.16.90
https://bugs.kde.org/show_bug.cgi?id=412276 --- Comment #4 from olignomi --- As of now, I run the previous described software/hardware with plasma 5.16.5. A normal user can use the dolphin super user mode requiering the root password. After entering the pw, dolphin super user mode opens. (recommended or not) Same for yast. After the upgrade to plasma 5.16.90, this procedure does not work anymore. The passwordbox opens again to ask for the correct pw. I rechecked, the pw is correct. When I return to plasma 5.16.5 everything is fine again. Maybe I'm wrong saying plasma is the problem! If so, could you reassign it e.g. to "dolphin"? At least, if that is the focus, an errormessage should advise not to use dolphin super user mode, instead of asking for the correct pw. tnx -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386620] Canvas framerate limiter might not be working as intended
https://bugs.kde.org/show_bug.cgi?id=386620 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Dmitry Kazakov --- I think I have fixed exactly this bug, when fixing bug 409460. Please check if the problem still persists in the nightly builds (I don't think it is available in 4.2 branch): https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ If the bug still present, please reopen this report :) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412259] Add ability to enter payee city and state
https://bugs.kde.org/show_bug.cgi?id=412259 --- Comment #13 from Thomas Baumgart --- Please make sure that the DB backend is working as well. The necessary columns are already present and maybe, you don't have to do anything besides testing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412286] Occational short slowdown/freeze while painting
https://bugs.kde.org/show_bug.cgi?id=412286 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #6 from Dmitry Kazakov --- Hi, acc4commissions! I have three questions :) 1) What CPU do you have? How many cores? And did you change the default setting in Preferences->Preformance->Advanced->CPU Limit? The limit should be set to maximum (that is the number of cores you have). 2) Do you have View->Instant Preview enabled? Does disabling it help? 3) What brush preset you use for the test? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396028] Imported Layer Styles Lose Properties
https://bugs.kde.org/show_bug.cgi?id=396028 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412202] THEMES AND ICONS NOT SHOWING
https://bugs.kde.org/show_bug.cgi?id=412202 --- Comment #8 from Cherkah --- Created attachment 122851 --> https://bugs.kde.org/attachment.cgi?id=122851&action=edit ActionToolBar.qml -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411001] Brushes will not appear
https://bugs.kde.org/show_bug.cgi?id=411001 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 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.
[plasmashell] [Bug 411302] freeBSD evolution after setting back compositor to Xrender,
https://bugs.kde.org/show_bug.cgi?id=411302 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408902] Zoom shortcut Ctrl+space+leftclick make krita crash when I turn to paint with the brush again
https://bugs.kde.org/show_bug.cgi?id=408902 --- Comment #16 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.
[kate] [Bug 405929] Spellchecker: dictionary language reset after each "replace"
https://bugs.kde.org/show_bug.cgi?id=405929 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411282] Spotify desktop client resumes playback after Skype call
https://bugs.kde.org/show_bug.cgi?id=411282 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411782] Brush strokes not working on any layers
https://bugs.kde.org/show_bug.cgi?id=411782 --- 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 411664] clicking on a certain brush preset crashes software
https://bugs.kde.org/show_bug.cgi?id=411664 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411659] Unknown error.
https://bugs.kde.org/show_bug.cgi?id=411659 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412286] Occational short slowdown/freeze while painting
https://bugs.kde.org/show_bug.cgi?id=412286 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 412304] New: Open with dialog with invalid supported files
https://bugs.kde.org/show_bug.cgi?id=412304 Bug ID: 412304 Summary: Open with dialog with invalid supported files Product: kdialog Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: m...@korniux.net Target Milestone: --- Created attachment 122850 --> https://bugs.kde.org/attachment.cgi?id=122850&action=edit Screenshot SUMMARY In "Open File" dialog from chromium-based browsers with specified accepted types in input[type=file] shows "Undefined" file extensions. STEPS TO REPRODUCE 1. Go to https://interactive-examples.mdn.mozilla.net/pages/tabbed/input-file.html in chromimum-based browser (gecko-based uses GTK) 2. Click on "Choose file" in "Output" 3. Open format filter OBSERVED RESULT "undefined, Image PNG, Image JPEG, undefined" EXPECTED RESULT "Image PNG, Image JPEG" SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 4.19.69-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15,6 GiB of RAM ADDITIONAL INFORMATION used -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412303] New: System Settings' Displays KCM mystifies newbies on moving monitors around
https://bugs.kde.org/show_bug.cgi?id=412303 Bug ID: 412303 Summary: System Settings' Displays KCM mystifies newbies on moving monitors around Product: systemsettings Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@callthecomputerdoctor.com Target Milestone: --- SUMMARY The System Settings' "Displays" module is not clear about what to do regarding dragging monitor positions around. OBSERVED RESULT When I try to explain to new KDE users that you can move monitors around in this settings page, they're a bit mystified by what I'm talking about. I actually have to show them. Because there's no feedback or prompt on the settings page that is actually possible that you can move a "monitor" by dragging it around. It's not a familiar interface to most people I train. Right now, the cursor shape is the standard arrow pointer when you mouse over the screen representation. There is no textual hint that the screens are movable in relative to each other. EXPECTED RESULT At least change the cursor to the four-directional-move cursor when mousing over the screen representation. This gives feedback that things are movable. Put a text string somewhere that says something to the effect, "Click and drag the monitors to represent the same actual layout as your setup". So people know that they can actually do that. Because this particular user interaction is novel throughout KDE. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412302] New: Suggestion: System Settings sidebar: Indent children category names from parent category headers
https://bugs.kde.org/show_bug.cgi?id=412302 Bug ID: 412302 Summary: Suggestion: System Settings sidebar: Indent children category names from parent category headers Product: systemsettings Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: k...@callthecomputerdoctor.com Target Milestone: --- SUMMARY In the System Settings’ sidebar of categories, the category header names do not appear to me to be visually distinct from their children and cause me to work harded to scan the separate categories' children. For example, the Appearance, Workspace, Personalization category header names have the same indent level as their children items, albeit with a slightly bolded face and no icon. Would it be more clear to have indented children items? SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410959] Full screen mode disappearing when invoking popup palette and color history
https://bugs.kde.org/show_bug.cgi?id=410959 vanyossi changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com Status|CONFIRMED |ASSIGNED CC||ghe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411352] [Wishlist] Improve performance of assisstant tools rendered on canvas.
https://bugs.kde.org/show_bug.cgi?id=411352 vanyossi changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ghe...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from vanyossi --- I don't get any slowdown following the steps provided or even after adding more than 10 vanishing points and panning at different zooming levels. Could you paste the text from "help > system information for bug reports"? Also check that you are not using OpenGL directly for display canvas acceleration but ANGLE. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 412271] Search field should return results for an emoji
https://bugs.kde.org/show_bug.cgi?id=412271 --- Comment #2 from Brennan Kinney --- ☝ 261D WHITE UP POINTING INDEX ✌ 270C VICTORY HAND These two and others behave a little differently. Paste the glyph into the search field, then backspace once(nothing is deleted), then space two times, now a result shows. Paste and add space and no effect. Unclear what causes that, perhaps it's due to UTF-8/UTF-16 differences(inbetween values you'd get for single latin character or an emoji, latin is 1 UTF-8 char, emoji seem to be around 4 UTF-8, and these glyphs are 3 UTF-8 but only 1 UTF-16). Perhaps there will be similar issues with other glyphs/emoji like ZWJ (Zero Width Joiner), which combine multiple emoji together to form a single one. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 412301] Modifying settings for touchpad using system settings have no effect on touchpad.
https://bugs.kde.org/show_bug.cgi?id=412301 Unlisted Person changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Unlisted Person --- I may have to retract this ticket. As I was getting ready to add diagnostics I did several suspend and resumes and now modifying the touchpad settings with the KDE system settings did affect mouse acceleration although the ID changes from 14 to 13. xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ SYNA307B:00 06CB:CD46 Touchpadid=14 [slave pointer (2)] ⎜ ↳ Wacom HID 48DD Pen stylus id=15 [slave pointer (2)] ⎜ ↳ Wacom HID 48DD Pen eraser id=18 [slave pointer (2)] ⎜ ↳ Wacom HID 48DD Finger id=22 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=19 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ HP HD Camera: HP HD Cameraid=11 [slave keyboard (3)] ↳ HP HD Camera: HP IR Cameraid=12 [slave keyboard (3)] ↳ Intel HID events id=16 [slave keyboard (3)] ↳ Intel HID 5 button array id=17 [slave keyboard (3)] ↳ HP Wireless hotkeys id=20 [slave keyboard (3)] ↳ HP WMI hotkeysid=21 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ HP Active Pen G2 Keyboard id=23 [slave keyboard (3)] $ xinput --list-props 14 | grep Accel libinput Accel Speed (369): 1.00 libinput Accel Speed Default (370): 0.00 (modify settings in KDE system settings) $ xinput --list-props 14 | grep Accel libinput Accel Speed (369): 0.888476 libinput Accel Speed Default (370): 0.00 Sorry - will close as "WORKSFORME" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411934] Krita Crash after changing Color Space to Grayscale
https://bugs.kde.org/show_bug.cgi?id=411934 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|RESOLVED --- Comment #4 from vanyossi --- With so little information it will be impossible to fix, im setting this to resolved waitingforinfo as you can open it again if the crash happens again. Here is a link to the information on how to generate a backtrace, the backtrace help us pinpoint the actions that took place to make krita crash. https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#dr-minw :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402329] The vector shape's repeat type of gradient is not saved.
https://bugs.kde.org/show_bug.cgi?id=402329 vanyossi changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/6fefdb7b48105a ||08edde8acd4b20c9a54d1fa53c Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from vanyossi --- Git commit 6fefdb7b48105a08edde8acd4b20c9a54d1fa53c by Ivan Yossi. Committed on 25/09/2019 at 03:04. Pushed by ivany into branch 'master'. Fix spread Mode not loading on svg parse Removed private QGradient::Spread usage and instead use private QGradient member. This copies correctly on qMap assign during svg parsing M +2-2libs/flake/svg/SvgGradientHelper.cpp M +0-1libs/flake/svg/SvgGradientHelper.h https://invent.kde.org/kde/krita/commit/6fefdb7b48105a08edde8acd4b20c9a54d1fa53c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412270] Keep active layer name when merging
https://bugs.kde.org/show_bug.cgi?id=412270 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #1 from vanyossi --- this probably needs discussion. you are merging the layer on top to the layer below so it is logical to keep the name of the layer below. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 412301] New: Modifying settings for touchpad using system settings have no effect on touchpad.
https://bugs.kde.org/show_bug.cgi?id=412301 Bug ID: 412301 Summary: Modifying settings for touchpad using system settings have no effect on touchpad. Product: Touchpad-KCM Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: atulbish...@gmail.com Reporter: kdem...@jeo.net Target Milestone: --- SUMMARY. Modifying settings for touchpad using KDE system settings have no effect on the touchpad. STEPS TO REPRODUCE 1. Start KDE system touchpad management window 2a. xinput --list-props 19 | grep Accel 2b. xinput --list-props 13 | grep Accel 3. Try to change things in GUI 4. Notice most things are greyed out, mouse seems unaffected on the acceleration. 5a. xinput --list-props 19 | grep Accel 5b. xinput --list-props 13 | grep Accel OBSERVED RESULT device 19 settings change, but touchpad behavior does not. EXPECTED RESULT Mouse sensitivity/acceleration changes. 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-29-generic OS Type: 64-bit Hardware: Laptop = HP Zbook X360 G5 ADDITIONAL INFORMATION There are TWO Touchpads listed when one runs "xinput --list --short" $ xinput --list --short ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=19 [slave pointer (2)] ⎜ ↳ SYNA307B:00 06CB:CD46 Touchpadid=13 [slave pointer (2)] ⎜ ↳ Wacom HID 48DD Pen stylus id=14 [slave pointer (2)] ⎜ ↳ Wacom HID 48DD Pen eraser id=15 [slave pointer (2)] ⎜ ↳ Wacom HID 48DD Finger id=22 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ HP HD Camera: HP HD Cameraid=11 [slave keyboard (3)] ↳ HP HD Camera: HP IR Cameraid=12 [slave keyboard (3)] ↳ Intel HID events id=16 [slave keyboard (3)] ↳ Intel HID 5 button array id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ HP Wireless hotkeys id=20 [slave keyboard (3)] ↳ HP WMI hotkeysid=21 [slave keyboard (3)] ↳ HP Active Pen G2 Keyboard id=23 [slave keyboard (3)] It appears that the touchpad modification system in KDE only changes id=19. But ID=13 is the one that affects the touchpad. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412300] Akonadi crashing after changing mail server dns name
https://bugs.kde.org/show_bug.cgi?id=412300 Aaron Williams changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Aaron Williams --- I restarted Kontact and am unable to reproduce this now. It successfully downloaded a couple hundred thousand emails. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412278] Assertion failure when trying to open a specific kra document
https://bugs.kde.org/show_bug.cgi?id=412278 vanyossi changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||ghe...@gmail.com --- Comment #1 from vanyossi --- On krita master f867486c5e835cd (macOS) I only got the assert once on opening but krita never crashed. I did try to reopen the file several times but the assert never showed again in the terminal. It is possible this bug is already fixed, or that maybe I need to paint in a certain way to trigger it as just waiting, or doing strokes on a new layer, does not cause the file to crash krita. Could you test if you can reproduce it in latest nightly krita? (Download krita next form the download page) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412300] Akonadi crashing after changing mail server dns name
https://bugs.kde.org/show_bug.cgi?id=412300 --- Comment #1 from Aaron Williams --- Created attachment 122849 --> https://bugs.kde.org/attachment.cgi?id=122849&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412300] New: Akonadi crashing after changing mail server dns name
https://bugs.kde.org/show_bug.cgi?id=412300 Bug ID: 412300 Summary: Akonadi crashing after changing mail server dns name Product: Akonadi Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: aar...@doofus.org Target Milestone: --- Application: akonadiserver (5.12.1) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 4.12.14-lp151.28.13-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: I changed the host name used for my mail server and the port number and now Akonadi keeps crashing while downloading email. The server is running Cyrus IMAP. The old host name used a non-standard port number but I doubt that has anything to do with this. I have hundreds of thousands of emails in the Inbox going back well over a decade. The crash can be reproduced sometimes. -- Backtrace (Reduced): #7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #8 0x7f33f5706741 in __GI_abort () at abort.c:79 #9 0x7f33f5d34e83 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 #10 0x7f33f5d3add8 in __cxxabiv1::__terminate (handler=) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:47 #11 0x7f33f5d3ae23 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:57 Possible duplicates by query: bug 412218, bug 411687, bug 411347, bug 411017, bug 409782. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412202] THEMES AND ICONS NOT SHOWING
https://bugs.kde.org/show_bug.cgi?id=412202 --- Comment #7 from Christoph Feck --- The 'qml' directory may not be a direct subdirectory of /usr/lib. On my system (openSUSE), it is /usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml If you cannot find it, let the system search it: cd /usr find | grep ActionToolBar.qml -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 411285] Tickets with Status/Resolution NEEDSINFO WAITINGFORINFO are automatically switched to RESOLVED WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=411285 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 411285] Tickets with Status/Resolution NEEDSINFO WAITINGFORINFO are automatically switched to RESOLVED WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=411285 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #6 from Nate Graham --- I'm sorry this isn't going how you expect. But it's the way the system is designed to work: if the requested information is not provided, the bug eventually gets closed as RESOLVED WORKSFORME. This is merely a short way of saying "the respondent never provided the requested information proving that it's an actionable issue, so we are closing the bug because we do not keep un-actionable bugs open." That's the way the system is designed to work. I don't see any actual problem here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412294] Crashed while copying files
https://bugs.kde.org/show_bug.cgi?id=412294 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- In the last weekend apparently the same occured on my Arch Linux. I did some file transfers from an internal hd to another internal hd (both formatted with ntfs file system) copying several big files. Plasma crashed (panel disappeared and wallpaper was replaced with a black background) 5 times at least, but weirdly "coredumpctl" command indicated no plasma crash and drkonqi icon never appeared in the systray. But the worst thing was: in some cases the whole X11 session crashed during the file transfer and my system went to login screen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412204] impossible to create and format partitions after an ext4 partition to be deleted
https://bugs.kde.org/show_bug.cgi?id=412204 --- Comment #9 from Patrick Silva --- Created attachment 122848 --> https://bugs.kde.org/attachment.cgi?id=122848&action=edit partition manager can not delete "unknown" partition I changed my partitioning scheme since I opened this report. Today I reverted such changes to try your patch and try to reproduce the problem reported here. I tried your patch, apparently it solved the problem after the step 2a, but partition formatting was still failling after the step 2b. And partition manager failed to delete the "unknown" partition created in the step 2b. I reinstalled kmpcore package from Arch repos and got the same results. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 411285] Tickets with Status/Resolution NEEDSINFO WAITINGFORINFO are automatically switched to RESOLVED WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=411285
Filipus Klutiero changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|INTENTIONAL |---
--- Comment #5 from Filipus Klutiero ---
(In reply to Nate Graham from comment #3)
> Yep, what you're describing is exactly the way it's supposed to work: if
> information is requested but not provided in a month, the bug gets closed.
As described in Summary and in the Description, the status gets set to RESOLVED
and the resolution to WORKSFORME, which is hopefully not how it's supposed to
work.
> We implemented this system to alleviate demands on human bug triagers and to
> provide clarity and finality for the thousands of bugs that had NEEDSINFO
> WAITINGFORINFO as the status.
Who are you ("we")? How would this system "alleviate demands" on bug triagers?
And what do you mean by "providing finality"?
> If you think this is a problem, please bring it up on the
> kde-commun...@kde.org mailing list, as Harals indicated.
I certainly think that's a problem; I wouldn't be reporting it otherwise.
Please avoid marking tickets as resolved until the problem reported was solved.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 412211] Night Color Always On using Auto or Location
https://bugs.kde.org/show_bug.cgi?id=412211 --- Comment #13 from Samantha --- To answer your questions: > If you click the "Get Location" button it shows the correct > longitute/latitude values in the input fields? Location Mode is grabbing the correct location, as expected. These coordinates are greyed out if switching over to Auto Mode, but they are still correct. If I manually define coordinates in the Location box (i.e. 49., -122.), click apply and then change the mode to automatic, the grayed out box is automatically switched to the correct coordinates. > What times does it show then in the greyed out times fields above with and > without the patch from Phabricator? Sunrise and Sunset times are correct for my locale, with or without the patch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412211] Night Color Always On using Auto or Location
https://bugs.kde.org/show_bug.cgi?id=412211 --- Comment #12 from Samantha --- Created attachment 122847 --> https://bugs.kde.org/attachment.cgi?id=122847&action=edit Automatic Mode Settings Patched or unpatched, looks the same -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412211] Night Color Always On using Auto or Location
https://bugs.kde.org/show_bug.cgi?id=412211 --- Comment #11 from Samantha --- Created attachment 122846 --> https://bugs.kde.org/attachment.cgi?id=122846&action=edit Location Mode Settings without Patch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412211] Night Color Always On using Auto or Location
https://bugs.kde.org/show_bug.cgi?id=412211 --- Comment #10 from Samantha --- Created attachment 122845 --> https://bugs.kde.org/attachment.cgi?id=122845&action=edit Location Mode Settings with Patch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411506] Kwin requires constant restart after weeks of uptime to refresh windows
https://bugs.kde.org/show_bug.cgi?id=411506 --- Comment #23 from Michael Butash --- Created attachment 122844 --> https://bugs.kde.org/attachment.cgi?id=122844&action=edit Output of qdbus kwin supportInfo post upgrade and current breaking Updated supportInfo post full system upgrade and still having a total failure of kde/kwin currently. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 411285] Tickets with Status/Resolution NEEDSINFO WAITINGFORINFO are automatically switched to RESOLVED WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=411285 --- Comment #4 from Filipus Klutiero --- (In reply to Harald Sitter from comment #2) > Well, this is a complaint about the state names, which needs to go to the > kde-commun...@kde.org mailing list. Musing this in a bug report seems > entirely pointless. This is not a complaint about state names, but a report of the defect described. If you think there is an underlying bug with state names or whatever, you are free to say so here or on a topical mailing list. > The current behavior is the result of earlier discussion > and consensus on aforementioned mailing list, so further discussion should > go there I would think. Issue trackers are the canonical place to discuss issues. If there was related discussion on that mailing list though, it would be useful to reference it here (and perhaps cross-reference with a mail to the list pointing here). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411506] Kwin requires constant restart after weeks of uptime to refresh windows
https://bugs.kde.org/show_bug.cgi?id=411506 --- Comment #22 from Michael Butash --- Interesting part I find is it does seem to be compositing, it's just not showing me anything but a black window. When I use an alt terminal to log in at shell, I see kwin_x11 --replace running, and qdbus supportInformation shows compositing up and running. Very odd behavior, something new. If I try to restart compositing with Ctrl-Alt F12, I get the console screen again just blinking, until I switch to F3 and back to F1, then I get the composited black screen again. Almost like there's nothing behind the compositor there to show. I don't know how this went from compositor instability to desktop no longer works, but it sure did. I haven't installed anything new in a while, but it was up to around ~50 days of uptime too. I will post an updated qdbus supportInfo as well post-upgrade and currently broken. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 412299] New: A ticket can have both resolution INTENTIONAL and status RESOLVED
https://bugs.kde.org/show_bug.cgi?id=412299 Bug ID: 412299 Summary: A ticket can have both resolution INTENTIONAL and status RESOLVED Product: bugs.kde.org Version: unspecified Platform: Other URL: https://bugs.kde.org/show_bug.cgi?id=411285 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: chea...@gmail.com CC: she...@kde.org Target Milestone: --- SUMMARY bugs.kde.org allows a given report to simultaneously have both its Status field set to RESOLVED and its Resolution field set to "INTENTIONAL": >INTENTIONAL >The problem described is a bug which will never be fixed. This actually occurs in practice, as can be seen in ticket #411285. STEPS TO REPRODUCE 1. Access a RESOLVED report such as #302642 2. Select the INTENTIONAL option in the second field in the Status line. 3. Activate the Save Changes button to the right. OBSERVED RESULT I did not verify that, but presumably, the above will suffice to get a "RESOLVED INTENTIONAL" ticket. EXPECTED RESULT Either the operation should be rejected, or - ideally - only compatible options should be shown. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412211] Night Color Always On using Auto or Location
https://bugs.kde.org/show_bug.cgi?id=412211 --- Comment #9 from Roman Gilg --- What exactly happens in "Location" mode? If you click the "Get Location" button it shows the correct longitute/latitude values in the input fields? In case it shows the values you expect at your location, what times does it show then in the greyed out times fields above with and without the patch from Phabricator? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410723] Freehand annotation jagged lines with stylus
https://bugs.kde.org/show_bug.cgi?id=410723 --- Comment #10 from blackdovahb...@gmail.com --- (In reply to Oliver Sander from comment #9) > Created attachment 122832 [details] > Plot of the points of the spiky path > > I extracted the points of the problematic path from the pdf document, and > plotted them using gnuplot. This gets us one step closer to an explanation: > As can be seen from the attached picture, each point is actually a pair of > points, a small distance apart. Together with a MiterJoin line style this > explains the jaggedness of the resulting path. > > [Currently I simply assume that MiterJoin line drawing is used, but I didn't > check. For a 'normal' set of points on a path you wouldn't see the > difference.] > > So the remaining task is to find out where these double points come from. My > system (which is a bleeding edge Okular on Debian Buster) doesn't produce > them. I am tempted to conjecture that the problem is somewhere in the lower > layers of the tablet input stack, and not in Okular itself. Thank you, Oliver. By the sounds of it, I do think you're correct about the origin of the error. It would make sense why the path would appear jagged and spiky because of the pair of joints. I'm not well-versed in these things and my understanding of it is lacking. So take my opinion with a grain of salt. However, I don't believe that the error is caused by the tablet itself. My drawing pad seems to work fine in other applications that are more geared towards drawing/art (Rene stated that it works fine for him in GIMP). This could happen because it uses a different method for tracking paths or could lead to an inconclusive idea that it is a problem with Okular. I would also like to mention that my drawing pad is of the same brand as Rene's but is a different model. I don't know how relevant that information is. I suppose it's possible that this is a bug that occurs with only Wacom tablets. I don't know how likely that would be. Drawing in Okular before I upgraded from Ubuntu 18.04 to Ubuntu 19.04, I had no issues. The error only came to be after upgrading my OS. This leaves me to believe (though I may be incorrect) that this isn't an issue with the drawing tablets but something else. I would also like to reiterate that this only occurred after upgrading my OS (the same thing happened in Rene's case). I don't know why that is but I do think that it's quite strange and could have something to do with the bug. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 412298] New: Kontact Flatpak Package does not run on Kubuntu 18.04 because of Akonadi
https://bugs.kde.org/show_bug.cgi?id=412298 Bug ID: 412298 Summary: Kontact Flatpak Package does not run on Kubuntu 18.04 because of Akonadi Product: kontact Version: unspecified Platform: Flatpak OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: zpari...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install Kontact Flatpak 19.04.1 stable package on Kubuntu 18.04 2. Start Akonadi if necessessary 3. Run Kontact Flatpak OBSERVED RESULT Messages say wrong QT version and Akonadi not functioning properly and will try again... EXPECTED RESULT Kontact Should start with Akonadi working properly SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.9 KDE Frameworks Version: 54.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Kernel: 4.18.0-25-generic -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 412297] New: Treat pass-by-reference as variable definition
https://bugs.kde.org/show_bug.cgi?id=412297 Bug ID: 412297 Summary: Treat pass-by-reference as variable definition Product: kdevelop Version: 5.4.1 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: silverunicorn2...@yandex.ru Target Milestone: --- In PHP, when I pass a non-existent variable by reference, it comes into existence. That’s used for output-only parameters. E.g. after a call to `mysqli_stmt::bind_result`, each of its arguments becomes a variable. But KDevelop doesn’t notice that, highlighting the variable as undefined (like those were never assigned to). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412294] New: Crashed while copying files
https://bugs.kde.org/show_bug.cgi?id=412294 Bug ID: 412294 Summary: Crashed while copying files Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: 7cat...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Copying 25Gb from my HDD to desktop Firefox with quite a few tabs discord desktop app - Custom settings of the application: Hugepages enabled (6Gb) Just some popular extensions installed -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7086143880 (LWP 930))] Thread 14 (Thread 0x7f7032e0a700 (LWP 5118)): #0 0x7f708a124415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f708ac52660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f708ac52752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f708ca36dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f708ca3705e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f708ac4c5b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f708a11e57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f708a8db0e3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f70425db700 (LWP 2876)): #0 0x7f708a124415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f708ac52660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f708ac52752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f708ca36dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f708ca3705e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f708ac4c5b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f708a11e57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f708a8db0e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f7040d9d700 (LWP 2582)): #0 0x7f708a124415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f708ac52660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f708ac52752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f708ca36dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f708ca3705e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f708ac4c5b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f708a11e57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f708a8db0e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f7041c3a700 (LWP 1440)): #0 0x7f708a124415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f708ac52660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f708ac52752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f708ca36dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f708ca3705e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f708ac4c5b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f708a11e57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f708a8db0e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f7065510700 (LWP 1200)): [KCrash Handler] #6 0x0018 in () #7 0x7f708cdc42f2 in () at /usr/lib/libKF5Plasma.so.5 #8 0x7f708cdc4489 in () at /usr/lib/libKF5Plasma.so.5 #9 0x7f708a81be70 in __run_exit_handlers () at /usr/lib/libc.so.6 #10 0x7f708a81bfae in () at /usr/lib/libc.so.6 #11 0x7f707cc1b1e0 in () at /usr/lib/dri/i965_dri.so #12 0x7f707dc4b3d3 in glPrimitiveBoundingBox () at /usr/lib/libGLX_mesa.so.0 #13 0x7f707ddc0759 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #14 0x7f708b1f5a72 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #15 0x7f708ca330ee in () at /usr/lib/libQt5Quick.so.5 #16 0x7f708ca36fc8 in () at /usr/lib/libQt5Quick.so.5 #17 0x7f708ac4c5b0 in () at /usr/lib/libQt5Core.so.5 #18 0x7f708a11e57f in start_thread () at /usr/lib/libpthread.so.0 #19 0x7f708a8db0e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f7065d1e700 (LWP 1188)): #0 0x7f708a8d0667 in poll () at /usr/lib/libc.so.6 #1 0x7f70890f9130 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f70890f9201 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f708ae72a1c in QEventDispatcherGlib::processEvents
[Akonadi] [Bug 412296] New: Akonadi DAV process crashed after starting EteSync
https://bugs.kde.org/show_bug.cgi?id=412296 Bug ID: 412296 Summary: Akonadi DAV process crashed after starting EteSync Product: Akonadi Version: 5.12.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_davgroupware_resource (5.12.1) Qt Version: 5.12.5 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-gentoo x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: 1. I have Akonadi set up to sync with EteSync via etesync-dav 2. etesync-dav was not running (but Akonadi was) 3. I started etesync-dav 4. Akonadi DAV process crashed $ etesync-dav --version EteSync DAV version: 0.11.0 Radicale version: 2.1.11 -- Backtrace: Application: EteSync (akonadi_davgroupware_resource), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2c561fe840 (LWP 2902))] Thread 5 (Thread 0x7f2c4dbb3700 (LWP 2971)): #0 0x7f2c5b9df3db in poll () from /lib64/libc.so.6 #1 0x7f2c59e0f11e in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f2c59e0f23f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f2c5c01822b in QEventDispatcherGlib::processEvents (this=0x7f2c44000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f2c5bfc1a7b in QEventLoop::exec (this=this@entry=0x7f2c4dbb2d60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2c5be217e1 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2c5be22891 in QThreadPrivate::start (arg=0x555a654ca800) at thread/qthread_unix.cpp:361 #7 0x7f2c5a8854ca in start_thread () from /lib64/libpthread.so.0 #8 0x7f2c5b9eb7cf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f2c4e3b4700 (LWP 2969)): #0 0x7f2c5b9df3db in poll () from /lib64/libc.so.6 #1 0x7f2c59e0f11e in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f2c59e0f23f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f2c5c01822b in QEventDispatcherGlib::processEvents (this=0x7f2c4b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f2c5bfc1a7b in QEventLoop::exec (this=this@entry=0x7f2c4e3b3d60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2c5be217e1 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2c5be22891 in QThreadPrivate::start (arg=0x555a654adab0) at thread/qthread_unix.cpp:361 #7 0x7f2c5a8854ca in start_thread () from /lib64/libpthread.so.0 #8 0x7f2c5b9eb7cf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f2c4ebb5700 (LWP 2965)): #0 0x7f2c5b9df3db in poll () from /lib64/libc.so.6 #1 0x7f2c59e0f11e in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f2c59e0f23f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f2c5c01822b in QEventDispatcherGlib::processEvents (this=0x7f2c48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f2c5bfc1a7b in QEventLoop::exec (this=this@entry=0x7f2c4ebb4d30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2c5be217e1 in QThread::exec (this=this@entry=0x7f2c5c9b4dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2c5c92ed06 in QDBusConnectionManager::run (this=0x7f2c5c9b4dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f2c5be22891 in QThreadPrivate::start (arg=0x7f2c5c9b4dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7f2c5a8854ca in start_thread () from /lib64/libpthread.so.0 #9 0x7f2c5b9eb7cf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f2c54f73700 (LWP 2936)): #0 0x7f2c5b9df3db in poll () from /lib64/libc.so.6 #1 0x7f2c5aae9d5f in ?? () from /lib64/libxcb.so.1 #2 0x7f2c5aaeba1a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f2c55ae7508 in QXcbEventQueue::run (this=0x555a654519c0) at qxcbeventqueue.cpp:228 #4 0x7f2c5be22891 in QThreadPrivate::start (arg=0x555a654519c0) at thread/qthread_unix.cpp:361 #5 0x7f2c5a8854ca in start_thread () from /lib64/libpthread.so.0 #6 0x7f2c5b9eb7cf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2c561fe840 (LWP 2902)): [KCrash Handler] #6 0x7f2c5daf6d2b in KDAV::EtagCache::setEtagInternal(QString const&, QString const&) () from /lib64/libKPimKDAV.so.5 #7 0x7f2c5daf6f03 in KDAV::EtagCach
[systemsettings] [Bug 412202] THEMES AND ICONS NOT SHOWING
https://bugs.kde.org/show_bug.cgi?id=412202 --- Comment #6 from Cherkah --- >Do you have a self built kirigami? Can I see your >/usr/lib/qml/org/kde/kirigami.2/ActionToolBar.qml >file this file like this is present on my system: ls /usr/lib/qml/org/kde/kirigami.2/ActionToolBar.qml none ls /usr/lib/qml/org/kde/ none /usr/lib/qml/org/ none /usr/lib/qml/ none -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411506] Kwin requires constant restart after weeks of uptime to refresh windows
https://bugs.kde.org/show_bug.cgi?id=411506 --- Comment #21 from Michael Butash --- So last night my desktop finally broke entirely, where after it woke up, all I got was a blank display. At this point I was left with no choice but to reboot it, and did so gracefully from an alt tty. A reboot would get me to sddm login, but once logging in, I get the framebuffer start same black display, but I could see the mouse moving as it would normally across the displays, just no apps. Restarting sddm and trying Mate or Cinnamon, I now get the black screen for anything beyond sddm. Installing and using GDM doesn't seem to work either, but not sure that isn't just a config thing having never used it before anyways. It's odd, I get no error from xorg logs, journalctl looks fine through launching sddm and into plasma, until it gets to kwin_x11 gives "qt.qpa.xcb: QXcbConnection: XCB error: 3 (Bad Window) 9 (Bad Drawable). All other log output for the session seems like apps are starting fine. I had this happen once before similarly, seems something I installed upgraded some core components, and an entirely pacman -Syu fixed it, so did so here, but still no change, same as before upgrade. Now I'm not even sure where to start with this to get a working desktop again now. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412202] THEMES AND ICONS NOT SHOWING
https://bugs.kde.org/show_bug.cgi?id=412202 --- Comment #5 from David Edmundson --- "file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml" "Error loading QML file.\n133: Type Kirigami.InlineMessage unavailable\n77: Type T.InlineMessage unavailable\n263: Type Kirigami.ActionToolBar unavailable\n175: Unexpected token `>'\n175: Unexpected token `>'\n" what. Do you have a self built kirigami? Can I see your /usr/lib/qml/org/kde/kirigami.2/ActionToolBar.qml file -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412295] New: Assert on font settings
https://bugs.kde.org/show_bug.cgi?id=412295 Bug ID: 412295 Summary: Assert on font settings Product: konsole Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: k...@davidedmundson.co.uk Target Milestone: --- Application: konsole (19.11.70) (Compiled from sources) Qt Version: 5.14.0 Frameworks Version: 5.63.0 Operating System: Linux 5.2.11-arch1-1-ARCH x86_64 Distribution: Arch Linux -- Information about the crash: I was playing around to choose the best font after it was somehow reset. Backtrace shows konsole clearly requesting something that's out of Qt's bounds. -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1417e2d880 (LWP 1379))] Thread 3 (Thread 0x7f140d96f700 (LWP 1381)): #0 0x7f14153e1667 in poll () from /usr/lib/libc.so.6 #1 0x7f141205aa80 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f141205ab51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f1415c2657c in QEventDispatcherGlib::processEvents (this=0x7f140b20, flags=...) at /home/david/projects/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1415b8c34b in QEventLoop::processEvents (this=0x7f140d96ecb0, flags=...) at /home/david/projects/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:138 #5 0x7f1415b8c685 in QEventLoop::exec (this=0x7f140d96ecb0, flags=...) at /home/david/projects/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:225 #6 0x7f1415922fca in QThread::exec (this=0x7f1417380dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/david/projects/qt5/qtbase/src/corelib/thread/qthread.cpp:536 #7 0x7f14172c5379 in QDBusConnectionManager::run (this=0x7f1417380dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/david/projects/qt5/qtbase/src/dbus/qdbusconnection.cpp:179 #8 0x7f1415925e87 in QThreadPrivate::start (arg=0x7f1417380dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/david/projects/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:342 #9 0x7f141504157f in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f14153ec0e3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f140f9d7700 (LWP 1380)): #0 0x7f14153e1667 in poll () from /usr/lib/libc.so.6 #1 0x7f14144c4630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f14144c62db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f14104101bc in QXcbEventQueue::run (this=0x564bf7702e30) at /home/david/projects/qt5/qtbase/src/plugins/platforms/xcb/qxcbeventqueue.cpp:228 #4 0x7f1415925e87 in QThreadPrivate::start (arg=0x564bf7702e30) at /home/david/projects/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:342 #5 0x7f141504157f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f14153ec0e3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1417e2d880 (LWP 1379)): [KCrash Handler] #6 0x7f141532a755 in raise () from /usr/lib/libc.so.6 #7 0x7f1415315851 in abort () from /usr/lib/libc.so.6 #8 0x7f141591ac5c in qt_message_fatal (context=..., message=...) at /home/david/projects/qt5/qtbase/src/corelib/global/qlogging.cpp:1894 #9 0x7f141591729a in QMessageLogger::fatal (this=0x7ffd96c84920, msg=0x7f1415ccbd50 "ASSERT failure in %s: \"%s\", file %s, line %d") at /home/david/projects/qt5/qtbase/src/corelib/global/qlogging.cpp:893 #10 0x7f141590dc13 in qt_assert_x (where=0x7f14166d6fe0 "QFont::setWeight", what=0x7f14166d6fc0 "Weight must be between 0 and 99", file=0x7f14166d6e38 "/home/david/projects/qt5/qtbase/src/gui/text/qfont.cpp", line=1097) at /home/david/projects/qt5/qtbase/src/corelib/global/qglobal.cpp:3310 #11 0x7f14162aa7df in QFont::setWeight (this=0x7ffd96c84a88, weight=113) at /home/david/projects/qt5/qtbase/src/gui/text/qfont.cpp:1097 #12 0x7f14188b71fb in Konsole::TerminalDisplay::drawCharacters (this=0x564bf792a510, painter=..., rect=..., text=..., style=0x564bf81e3160, invertCharacterColor=false) at /home/david/projects/kde5/src/kde/applications/konsole/src/TerminalDisplay.cpp:801 #13 0x7f14188b7708 in Konsole::TerminalDisplay::drawTextFragment (this=0x564bf792a510, painter=..., rect=..., text=..., style=0x564bf81e3160) at /home/david/projects/kde5/src/kde/applications/konsole/src/TerminalDisplay.cpp:864 #14 0x7f14188ba587 in Konsole::TerminalDisplay::drawContents (this=0x564bf792a510, paint=..., rect=...) at /home/david/projects/kde5/src/kde/applications/konsole/src/TerminalDisplay.cpp:1688 #15 0x7f14188b8e2b in Konsole::TerminalDisplay::paintEvent (this=0x564bf792a510, pe=0x7ffd96c855c0) at /home/david/projects/kde5/src/kde/applications/konso
[digikam] [Bug 412293] Image editor Tools sidebar width not restored
https://bugs.kde.org/show_bug.cgi?id=412293 --- Comment #2 from andrej.valen...@zoho.com --- Created attachment 122843 --> https://bugs.kde.org/attachment.cgi?id=122843&action=edit Sidebar after - 3 columns -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412293] Image editor Tools sidebar width not restored
https://bugs.kde.org/show_bug.cgi?id=412293 andrej.valen...@zoho.com changed: What|Removed |Added Attachment #122842|Tools sidebar after using |Tools sidebar before using description|tools - 3 columns |tools - 4 columns -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412293] Image editor Tools sidebar width not restored
https://bugs.kde.org/show_bug.cgi?id=412293 andrej.valen...@zoho.com changed: What|Removed |Added Attachment #122842|Tools sidebar before using |Tools sidebar after using description|tools |tools - 3 columns -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412293] Image editor Tools sidebar width not restored
https://bugs.kde.org/show_bug.cgi?id=412293 --- Comment #1 from andrej.valen...@zoho.com --- Created attachment 122842 --> https://bugs.kde.org/attachment.cgi?id=122842&action=edit Tools sidebar before using tools -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412293] New: Image editor Tools sidebar width not restored
https://bugs.kde.org/show_bug.cgi?id=412293 Bug ID: 412293 Summary: Image editor Tools sidebar width not restored Product: digikam Version: 6.4.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Usability-Ergonomy Assignee: digikam-bugs-n...@kde.org Reporter: andrej.valen...@zoho.com Target Milestone: --- SUMMARY After using any of the tools in Image Editor and confirming (OK) or canceling the changes the "Tools" sidebar becomes narrower - does not restore the size/width. STEPS TO REPRODUCE 1. Chose a photo and click Image Editor (or F4) - the Tools sidebar is 4 columns wide 2. Use any of the tools in the sidebar and click OK or Cancel 3. Back to the Image Editor base view - the Tools sidebar is 3 columns wide 4. Manually change the sidebar size to show 4 columns and repeat steps 1-2 - again the sidebar becomes only 3 columns wide. OBSERVED RESULT No matter what the size of the sidebar before using any of the tools is, after returning to the base Image Editor view the size is only 3 columns wide. This is annoying because after that the tools change position in the sidebar and I have to look for them in different places. I tried setting the size of the sidebar to even more columns (like 6 or 7) and still after using a tool the size is back to 3 columns. EXPECTED RESULT Would like the size of the sidebar to stay the same whenever I'm using the Image Editor. SOFTWARE/OS VERSIONS Windows: 10 digiKam version: digiKam-6.4.0-git-20190924T120716-Win64 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: KDE Frameworks 5.61.0 Qt Version: Qt 5.13.1 (built against 5.13.1 ADDITIONAL INFORMATION In the version 6.3 this does not happen and the sidebar always "comes back" with 4 columns width. And I don't know if it has anything to do whith this in the Settings I've got the "Restore the settings of the Image Editor tools" checked. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412204] impossible to create and format partitions after an ext4 partition to be deleted
https://bugs.kde.org/show_bug.cgi?id=412204 --- Comment #8 from Andrius Štikonas --- (In reply to Patrick Silva from comment #6) > (In reply to Andrius Štikonas from comment #5) > > (In reply to Patrick Silva from comment #3) > > > This problem is always reproducible here. > > > > > > If you give me detailed instructions, I can try your fix. > > > > By the way, how detailed instruction do you need? > > > > Basically in kpmcore dir apply patch with > > > > patch -p1 < patch_name.patch > > mkdir build > > cd build > > cmake .. -DCMAKE_INSTALL_PREFIX=/usr > > make > > sudo make install > > building was successful, but kpmcore can not be installed: > Compiling... succeeded (after 2 minutes, and 51 seconds) > Installing.. failed (after 0 seconds) > Unable to install kpmcore! > > > > <<< PACKAGES FAILED TO BUILD >>> > kpmcore - ~/kde/src/log/2019-09-24-01/kpmcore/install.log > :-( > > and when I run "patch -p1 < bug412204.patch" in kpmcore directory, I get a > "File to patch:" prompt. What about "git apply bug412204.patch" ? I don't use kdesrc-build, so I'm not the best person to advise on that. You can try asking somebody else. Alternatively, you can just copy libpmsfdiskbackendplugin.so from build tree to your install folder (on my distro it is /usr/lib64/qt5/plugins/libpmsfdiskbackendplugin.so) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412292] New: Hidden panel appears too quickly
https://bugs.kde.org/show_bug.cgi?id=412292 Bug ID: 412292 Summary: Hidden panel appears too quickly Product: plasmashell Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jplx...@gmail.com Target Milestone: 1.0 SUMMARY I've set my bottom panel so that it can be covered by windows. I don't want it to waste space when I'm using a maximized window. What then happens is that when I and try to access something at the bottom of the current window, I will accidentally hit the mouse pointer against the bottom of the screen. The panel appears, covers what I wanted to reach and takes a while to disappear again. It's probably just a second, but it feels like ages, which is very annoying when I quickly want to do something. I suggest a tiny delay, maybe with a setting, to prevent the panel from being displayed when the user just accidentally hits the bottom of the screen. STEPS TO REPRODUCE 1. Set panel to autohide/be covered by windows 2. Accidentally hit bottom of screen, immeadiately moving the mouse somewhere else. 3. Panel appears OBSERVED RESULT I accidentally make the panel appear when I didn't want to EXPECTED RESULT The panel only appears when I deliberately move the mouse to the bottom edge of the screen. This usually means it stays there for longer. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 384314] ledger sort option does not work properly
https://bugs.kde.org/show_bug.cgi?id=384314 --- Comment #3 from Ralf Habacker --- Git commit c0d3df01823db7fe0a6107a84fa7c3d3008a8d1d by Ralf Habacker. Committed on 24/09/2019 at 20:32. Pushed by habacker into branch '4.8'. Correct direction display of symbols in column sort dialog of ledger view M +2-2kmymoney/widgets/transactionsortoptionimpl.cpp https://commits.kde.org/kmymoney/c0d3df01823db7fe0a6107a84fa7c3d3008a8d1d -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371837] Dolphin General option "Executing scripts or desktop files" doesn't let you choose between "execute" and "open".
https://bugs.kde.org/show_bug.cgi?id=371837 Elvis Angelaccio changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Summary|Dolphin General option |Dolphin General option |"Executing scripts or |"Executing scripts or |desktop files" cannot be|desktop files" doesn't let |unchecked |you choose between ||"execute" and "open". --- Comment #11 from Elvis Angelaccio --- Reopening and updating the title. It is still not possible to choose between "execute" and "open". See also https://phabricator.kde.org/T9932 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411001] Brushes will not appear
https://bugs.kde.org/show_bug.cgi?id=411001 --- Comment #5 from zpodsch...@gmail.com --- [image: image.png] This is currently all the brushes I have. I tried making more brushes but I have no other variations other than the paint brush. Sorry again for the lateness, life just got in the way. On Wed, Sep 11, 2019 at 10:30 AM Scott Petrovic wrote: > https://bugs.kde.org/show_bug.cgi?id=411001 > > Scott Petrovic changed: > >What|Removed |Added > > > CC||scottpetro...@gmail.com > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #4 from Scott Petrovic --- > It appears your brushes are just filtered down, so you only see a few of > them. > Can you take a screenshot of what your Brush presets docker looks like that > only has the 3 brushes? > > Does setting the drop-down to "All" still only show 3 brushes? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412291] Mac: Opening Preferences zooms the main window to unusable state
https://bugs.kde.org/show_bug.cgi?id=412291 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED CC||caulier.gil...@gmail.com Component|general |Bundle-MacOS Platform|Other |MacPorts Packages Status|REPORTED|RESOLVED Version Fixed In||6.4.0 --- Comment #1 from caulier.gil...@gmail.com --- Already reported, and already fixed with next 6.4.0 release. Pre-PKG package can be tested here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 401013] kde-open/xdg-open does not handle symbols at start or end of schema URL
https://bugs.kde.org/show_bug.cgi?id=401013
Ahmad Samir changed:
What|Removed |Added
Version|5.44.0 |5.16.90
CC||a.samir...@gmail.com
Component|general |general
Assignee|fa...@kde.org |aleix...@kde.org
Status|REPORTED|CONFIRMED
Product|frameworks-kio |kde-cli-tools
Ever confirmed|0 |1
--- Comment #3 from Ahmad Samir ---
Looks like it's a bug in ClientApp::kde_open() [1]:
for "test://example" info.url is QUrl("test://example")
for "test://example--" info.url is QUrl("http://test//example--";)
[1] https://cgit.kde.org/kde-cli-tools.git/tree/kioclient/kioclient.cpp#n212
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 412291] New: Mac: Opening Preferences zooms the main window to unusable state
https://bugs.kde.org/show_bug.cgi?id=412291 Bug ID: 412291 Summary: Mac: Opening Preferences zooms the main window to unusable state Product: digikam Version: 6.3.0 Platform: Other OS: macOS Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gerald.bossertstumv...@gmail.com Target Milestone: --- Created attachment 122840 --> https://bugs.kde.org/attachment.cgi?id=122840&action=edit digikam main window behind the preferences/configure window with increased icons, symbols, text ... SUMMARY STEPS TO REPRODUCE 1. Start digikam App in macOS 2. Open "Preferences" under the digikam menu 3. The Preferences window appears (window title "Configure"). 4. Close the Preferences window OBSERVED RESULT With step "3" all content (icons, text, images, symbols ...) of the main window behind the Preferences window is increased. The GUI is unusable. Workaround: - Configure digikam as usual - Close Preferences - Quit digikam app - Start digikam app - Don't use Preferences EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: 10.14.6 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 409415] Freeze when opening edit dialog for second time
https://bugs.kde.org/show_bug.cgi?id=409415 Thomas Fischer changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #5 from Thomas Fischer --- (In reply to Tobias Schmalz from comment #4) > I still have no clue what went wrong on my > system earlier, but it seems that KBibTeX had nothing to do with it. So > sorry for bothering you and thank you for your support! m) > > PS: Great software btw, I really like using KBibTeX! Thanks for the feedback! :-) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410774] Cannot reply on second SMS
https://bugs.kde.org/show_bug.cgi?id=410774 Piotr Mierzwinski changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED --- Comment #11 from Piotr Mierzwinski --- Application from time to time crashes like I reported below. Recently it happened in case of last update (Android version). Android only notified about new version. I tried to send new messaged and afer send KDE application crashed. Another issue is split of longer messages. First part of message is collected in notifications (no possibility of reply), second (even one work) is present in second. Here I can reply, but I cannot see whole message, because is cut. It happens also that messages are duplicated in Notification. For example first part is placed twice. I hope new version will fix most issues current one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412202] THEMES AND ICONS NOT SHOWING
https://bugs.kde.org/show_bug.cgi?id=412202 --- Comment #4 from Cherkah --- all qml-module-qtquick-controls2 and libkf5kirigami2-5 qml-module-org-kde-kirigami2 are installed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412202] THEMES AND ICONS NOT SHOWING
https://bugs.kde.org/show_bug.cgi?id=412202
--- Comment #3 from Cherkah ---
results:
QCoreApplication::arguments: Please instantiate the QApplication object first
Icon theme "gnome" not found.
Icon theme "gnome" not found.
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet:
Theme.View instead
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet:
Theme.View instead
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet:
Theme.View instead
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet:
Theme.View instead
kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1",
"Impossible d'exécuter l'instruction", "no such column: rl.initiatingAgent")
kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1",
"Impossible d'exécuter l'instruction", "no such column: rl.initiatingAgent")
org.kde.kcoreaddons: Error loading plugin "kcm_lookandfeel" "La bibliothèque
partagée est introuvable."
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
"file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml"
"Error loading QML file.\n44: Type Kirigami.Action unavailable\n21: module
\"QtQuick.Controls\" version 2.5 is not installed\n"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:214:
TypeError: Cannot read property 'createObject' of null
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet:
Theme.View instead
org.kde.kcoreaddons: Error loading plugin "kcm_desktoptheme" "La bibliothèque
partagée est introuvable."
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
"file:///usr/share/kpackage/kcms/kcm_desktoptheme/contents/ui/main.qml"
"Error loading QML file.\n93: Type Kirigami.Action unavailable\n21: module
\"QtQuick.Controls\" version 2.5 is not installed\n"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:214:
TypeError: Cannot read property 'createObject' of null
org.kde.kcoreaddons: Error loading plugin "kcm_cursortheme" "La bibliothèque
partagée est introuvable."
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
"file:///usr/share/kpackage/kcms/kcm_cursortheme/contents/ui/main.qml"
"Error loading QML file.\n34: Type Delegate unavailable\n55: Type
Kirigami.Action unavailable\n21: module \"QtQuick.Controls\" version 2.5 is not
installed\n"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:214:
TypeError: Cannot read property 'createObject' of null
log_user_manager: 1000
org.kde.kcoreaddons: Error loading plugin "kcm_translations" "La bibliothèque
partagée est introuvable."
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
"file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml"
"Error loading QML file.\n133: Type Kirigami.InlineMessage unavailable\n77:
Type T.InlineMessage unavailable\n263: Type Kirigami.ActionToolBar
unavailable\n175: Unexpected token `>'\n175: Unexpected token `>'\n"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:214:
TypeError: Cannot read property 'createObject' of null
--
You are receiving this mail because:
You are watching all bug changes.
[rsibreak] [Bug 412289] Repeating Welcome Screen
https://bugs.kde.org/show_bug.cgi?id=412289 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Albert Astals Cid --- Which libkf5coreaddons version are you running? -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 411339] zanshin fails to run on neon
https://bugs.kde.org/show_bug.cgi?id=411339 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 412290] Gwenview hangs when loading if cifs share not connected
https://bugs.kde.org/show_bug.cgi?id=412290 --- Comment #1 from Eric Adams --- I forgot to add that the workaround for this is to simply unmount the network share if you are on a different network. Gwenview is fine after that. Obviously not a high severity issue but thought it was worth reporting all the same. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 412290] New: Gwenview hangs when loading if cifs share not connected
https://bugs.kde.org/show_bug.cgi?id=412290 Bug ID: 412290 Summary: Gwenview hangs when loading if cifs share not connected Product: gwenview Version: 19.04.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: esa1...@gmail.com Target Milestone: --- SUMMARY Gwenview will not open an image (local disk) when cifs network mounts are disconnected. I assume it is doing a directory scan of some kind for whatever reason and hangs while trying to access the share. STEPS TO REPRODUCE 1. Either manually mount or add a mount option to fstab to a network share using cifs. 2. Disconnect the network or use a different network where the share is not accessible 3. Open any image on your local disk or other accessible location. OBSERVED RESULT The main Gwenview window appears but nothing is shown and eventually Plasma asks if you'd like to close or wait. EXPECTED RESULT Gwenview doesn't care if a network location is inaccessible and is able to open images regardless. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.04 with backports ppa enabled. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-29-lowlatency OS Type: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 412289] New: Repeating Welcome Screen
https://bugs.kde.org/show_bug.cgi?id=412289 Bug ID: 412289 Summary: Repeating Welcome Screen Product: rsibreak Version: 0.12.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: ctkocm...@gmail.com Target Milestone: --- SUMMARY The initial RSI Break weclome screen pops up every time I log into the desktop session. I have already clicked the "do not show me this again" box on the message. STEPS TO REPRODUCE 1. Using XFCE, log into user account 2. Click the "do not show me this again" box 3. reboot or turn off and then turn on the computer OBSERVED RESULT RSI Break weclome screen is displayed EXPECTED RESULT The RSI "Welcome Screen" no longer pops up after logging into the desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux (available in About System) KDE Plasma Version: not using KDE Frameworks Version: libkf5coreaddons Qt Version: libkf5configcore5 (QT Framework only) ADDITIONAL INFORMATION Peppermint OS 10 (Ubuntu 18.04) LXDE/XFCE Desktop running rsibreak 4:0.2.8-2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412039] Auto mask is several kinds of horribly broken
https://bugs.kde.org/show_bug.cgi?id=412039 --- Comment #3 from Darxus --- I thought the appimage was supposed to contain all the needed updated libraries? If anybody else is finding themselves in a similar situation, I ended up using blender, which is also free / open source, but has a steep learning curve: https://blenderartists.org/t/how-do-i-use-a-single-motion-tracking-marker-to-obscure-a-section-of-the-image/1181115/4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412211] Night Color Always On using Auto or Location
https://bugs.kde.org/show_bug.cgi?id=412211 --- Comment #8 from Samantha --- Just an update for the kwin side of things: I have rebuilt kwin with the revisions to the diff requested by Roman and the behavior of Location mode has remained consistent across patches. Should a separate bug report be opened for kded? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376061] QtAv not available to play video (UPSTREAM problem)
https://bugs.kde.org/show_bug.cgi?id=376061 --- Comment #9 from Michal Kec (MiK) --- Created attachment 122839 --> https://bugs.kde.org/attachment.cgi?id=122839&action=edit Digikam 6.3.0 components information (In reply to Jonathan Riddell from comment #8) > Should be fixed in 6.3.0 in neon I can not confirm, unfortunately. (screenshot) I have both digiKam (6.3.0-0xneon+18.04+bionic+build30) and libqtav1 (1.12.0+ds-4build3) packages installed from KDE Neon repos. Do I need to install/setup anything else? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412288] New: Kate ignores already running instance and opens document in a new window
https://bugs.kde.org/show_bug.cgi?id=412288 Bug ID: 412288 Summary: Kate ignores already running instance and opens document in a new window Product: kate Version: 19.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: zmo...@hotmail.com Target Milestone: --- SUMMARY Previously: you click on file in file manager (f.e. in Dolphin), if Kate window exists in same virtual desktop as file manager then that file was opened in new tab of existing Kate window. Now: file is opened in a new Kate window. STEPS TO REPRODUCE 1. Open a file manager. 2. Click on file to open for editing. 3. Click on another file to open for editing. OBSERVED RESULT Result: two windows rather than one window with two tabs. EXPECTED RESULT Another file should be opened in a new tab. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-29-generic OS Type: 64-bit Processors: 16 × AMD Ryzen 7 1700X Eight-Core Processor Memory: 15,7 GiB -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412286] Occational short slowdown/freeze while painting
https://bugs.kde.org/show_bug.cgi?id=412286 --- Comment #4 from wolthera --- Yeah, I am seeing the FPS take a nosedive at 0.16 seconds, dropping to 17.5 fps from around 50-70 when drawing and 120 when hovering. So it might be opengl related. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412276] no root access from normal user login using plasma 5.16.90
https://bugs.kde.org/show_bug.cgi?id=412276 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from David Edmundson --- What makes you say that yast not starting is a plasma bug? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412286] Occational short slowdown/freeze while painting
https://bugs.kde.org/show_bug.cgi?id=412286 --- Comment #3 from acc4commissi...@gmail.com --- Created attachment 122838 --> https://bugs.kde.org/attachment.cgi?id=122838&action=edit (try to) record It also seems happen in 4.1.7, so I guess it's not new... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412282] Okular 1.8.1 icon in Windows Store is the old Okular icon instead of the Breeze (Plasma 5) icon
https://bugs.kde.org/show_bug.cgi?id=412282 --- Comment #5 from Pedro_Rosmaninho --- (In reply to Luigi Toscano from comment #2) > That's the corret Okular icon. See also: > https://okular.kde.org/ > > The Breeze icon theme provides a different icon, but that's not the official > Okular icon. I saw the Okular website. But since it seems to still be stuck in the 90's I assumed that the website was still not updated to current Plasma UI guidelines while Okular itself was already following it. Considering that Breeze is the official icon set of Plasma, and Okular also is a KDE app I thought that the Breeze icon was the app icon. Also, I'll disagree that the Breeze Okular icon is ugly. IMO it's the opposite. In the old Oxygen icon the glasses are just plain silly. The Breeze icon maintained the blue stripe of the Oxygen icon and added a red bookmark on top that gives it visual richness. A downside is that it's too dark, so in dark themes it will be hard to spot. But for consistency sake then use the same icon everywhere. Currently, the Breeze icon is used in the titlebar and inside Okular, while in Windows the used icon is the Oxygen icon. Since I am not using Plasma, Okular should show its icon inside of the app instead of the Breeze icon. Also, please give the Okular devs a shiny new icon please. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405854] softness not applied in wipe transition
https://bugs.kde.org/show_bug.cgi?id=405854 cuill...@laposte.net changed: What|Removed |Added CC|cuill...@laposte.net| -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405854] softness not applied in wipe transition
https://bugs.kde.org/show_bug.cgi?id=405854 cuill...@laposte.net changed: What|Removed |Added CC||cuill...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 406721] Dolphin prevents unmounting of a removable device for a while after canceling a file copy
https://bugs.kde.org/show_bug.cgi?id=406721 --- Comment #3 from Nate Graham --- Maybe we just need to display a better error message here so the user knows why the device is busy. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 391611] Spectacle keeps running in the background if clicked on image of the screenshot in the notification and not on "open" button
https://bugs.kde.org/show_bug.cgi?id=391611 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #9 from Nate Graham --- That's what I thought. Please open a new bug if you see additional issues. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 412268] Filepicker unusable when using fractional scaling
https://bugs.kde.org/show_bug.cgi?id=412268 Nate Graham changed: What|Removed |Added CC||n...@kde.org Component|general |general Assignee|dolphin-bugs-n...@kde.org |br...@frogmouth.net Summary|Filepicker unusable when|Filepicker unusable when |scaling enabled |using fractional scaling Product|dolphin |kdialog --- Comment #1 from Nate Graham --- This is KDialog, not actually the file dialog itself. The file dialog works just fine with fractional scaling, so KDialog must be doing something weird with it. -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 412287] New: KOrganizer (korgac), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=412287 Bug ID: 412287 Summary: KOrganizer (korgac), signal: Segmentation fault Product: korgac Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: imurz...@gmail.com Target Milestone: --- Application: korgac (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: Ubuntu 19.04 -- Information about the crash: KOrganizer (korgac), signal: Segmentation fault The crash can be reproduced every time. -- Backtrace: Application: Напоминания KOrganizer (korgac), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6046469a80 (LWP 10641))] Thread 5 (Thread 0x7f603e4ad700 (LWP 10670)): #0 0x7f604dbe9729 in __GI___poll (fds=0x7f6034004e30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f604b424bf6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f6034004e30, timeout=, context=0x7f6034000bf0) at ../../../glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f6034000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3922 #3 0x7f604b424d1c in g_main_context_iteration (context=0x7f6034000bf0, may_block=1) at ../../../glib/gmain.c:3988 #4 0x7f604e187063 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f604e1325bb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f604df7d2c6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f604df7e612 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f604bc74182 in start_thread (arg=) at pthread_create.c:486 #9 0x7f604dbf5b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f603ecae700 (LWP 10666)): #0 __GI___libc_read (nbytes=16, buf=0x7f603ecad900, fd=10) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=10, buf=buf@entry=0x7f603ecad900, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f604b46b410 in read (__nbytes=16, __buf=0x7f603ecad900, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #3 g_wakeup_acknowledge (wakeup=0x7f60380039a0) at ../../../glib/gwakeup.c:210 #4 0x7f604b4246cf in g_main_context_check (context=context@entry=0x7f603bf0, max_priority=2147483647, fds=fds@entry=0x7f6030004a30, n_fds=n_fds@entry=1) at ../../../glib/gmain.c:3705 #5 0x7f604b424ba0 in g_main_context_iterate (context=context@entry=0x7f603bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3924 #6 0x7f604b424d1c in g_main_context_iteration (context=0x7f603bf0, may_block=1) at ../../../glib/gmain.c:3988 #7 0x7f604e187063 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f604e1325bb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f604df7d2c6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f604df7e612 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f604bc74182 in start_thread (arg=) at pthread_create.c:486 #12 0x7f604dbf5b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f603febf700 (LWP 10658)): #0 __GI___libc_read (nbytes=16, buf=0x7f603febe8d0, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=buf@entry=0x7f603febe8d0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f604b46b410 in read (__nbytes=16, __buf=0x7f603febe8d0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #3 g_wakeup_acknowledge (wakeup=0x558357594eb0) at ../../../glib/gwakeup.c:210 #4 0x7f604b4246cf in g_main_context_check (context=context@entry=0x7f6038000bf0, max_priority=2147483647, fds=fds@entry=0x5583576296c0, n_fds=n_fds@entry=1) at ../../../glib/gmain.c:3705 #5 0x7f604b424ba0 in g_main_context_iterate (context=context@entry=0x7f6038000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3924 #6 0x7f604b424d1c in g_main_context_iteration (context=0x7f6038000bf0, may_block=1) at ../../../glib/gmain.c:3988 #7 0x7f604e187063 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f604e1325bb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f604df7d2c6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f604e3ff565 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x7f604df7e612
[plasmashell] [Bug 412276] no root access from normal user login using plasma 5.16.90
https://bugs.kde.org/show_bug.cgi?id=412276 olignomi changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #2 from olignomi --- OK, should not does not mean it is not allowed. It is and was always possible to open dolphin in super user mode. What about the other issue about the yast2 login, which requires a root pw for a normal user? The mentioned problem is, that in both cases the valid root pw is not accepted. In older plasma versions (e.g. 5.16.5) it works fine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412286] Occational short slowdown/freeze while painting
https://bugs.kde.org/show_bug.cgi?id=412286 wolthera changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO Severity|wishlist|normal --- Comment #2 from wolthera --- Also setting this to normal, even though it's gonna take much more info to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412286] Occational short slowdown/freeze while painting
https://bugs.kde.org/show_bug.cgi?id=412286 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- We'll need a bit more information than this. Did it happen before, is it new behaviour? Could you go to settings->configure Krita->performance->advanced and toggle 'Debug Logging of OpenGL framerate' as well as 'Debug logging of brush rendering speed', and then make a recording where you reproduce this issue? Maybe these two debug outputs can give some hard numbers to the problem... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412276] no root access from normal user login using plasma 5.16.90
https://bugs.kde.org/show_bug.cgi?id=412276 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Edmundson --- This is not supported. File managers should not be run as root. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412286] New: Occational short slowdown/freeze while painting
https://bugs.kde.org/show_bug.cgi?id=412286 Bug ID: 412286 Summary: Occational short slowdown/freeze while painting Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY git ddb3a87 Brush occationally (very shortly) freezes while painting. It's not a big problem but very annoying. The behavior feels like how it used to freeze on autosaving in old krita. STEPS TO REPRODUCE I'm not sure when it happens but 1 way to see the freeze is 1. Paint something (Bigger brush size would be easy to see what happens) 2. Undo it with ctrl+Z, and then paint something again. 3. Repeat 1~2. If you do the recursive process fast enough, it becomes obvious that there's a choppiness in brush moves. SOFTWARE/OS VERSIONS Windows: win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Krita Version: 4.3.0-prealpha (git ddb3a87) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 6.1.7601 Pretty Productname: Windows 7 SP 1 (6.1) Product Type: windows Product Version: 7sp1 Hardware Information GPU Acceleration: desktop Memory: 16351 Mb Number of Cores: 8 Swap Location: C:/Users/(-)/AppData/Local/Temp OpenGL Info Vendor: "ATI Technologies Inc." Renderer: "Radeon RX 560 Series" Version: "3.0.13558 Compatibility Profile Context 26.20.11015.5009" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: false == log == Supported renderers: QFlags(0x2|0x4|0x8) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 2 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 4 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) 2 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::bt2020PQColorSpace, profile QSurfaceFormat::CompatibilityProfile) 2 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) 4 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::bt2020PQColorSpace, profil
