[yakuake] [Bug 379163] Save Session
https://bugs.kde.org/show_bug.cgi?id=379163 Eike Hein changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eike Hein --- *** This bug has been marked as a duplicate of bug 149522 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 149522] Save and restore sessions
https://bugs.kde.org/show_bug.cgi?id=149522 Eike Hein changed: What|Removed |Added CC||ferchoj.alapa+b...@gmail.co ||m --- Comment #24 from Eike Hein --- *** Bug 379163 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 364098] In split pane view konsole should respect focus follows mouse but doesn't
https://bugs.kde.org/show_bug.cgi?id=364098 --- Comment #5 from davidblunkett --- I simply fail to see your objection to this. Policy "click to focus" clearly flies in the face of user preferences. Respecting the window manager setting is trivial to implement and you could even consider and option: - click to focus - window manager choice - focus follows mouse And in answer to your question - I cannot think of a single multipane application that doesn't behave this way, I think konsole is uniquely uncooperative. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Severity|major |wishlist --- Comment #1 from Boudewijn Rempt --- Someone who is familiar with wayland should do that. I'm not using gnome or wayland myself at this point. Not that libinput has problems anyway -- it causes irregular lines. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368350] folder full text search doesn't work : folder status always 'still not indexed'
https://bugs.kde.org/show_bug.cgi?id=368350 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #6 from Laurent Montel --- We fixed a lot of bug about it in 5.5.0. Could you test it please ? Regards -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 149522] Save and restore sessions
https://bugs.kde.org/show_bug.cgi?id=149522 --- Comment #25 from Jasem Mutlaq --- and I'm still using DBus to restore saved tabs. However, in recent Plasma you get warning that using DBus for this is "unsafe". I am still forced to use DBus though since there is no option yet to restore previous tabs. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 149522] Save and restore sessions
https://bugs.kde.org/show_bug.cgi?id=149522 Ciro Santilli changed: What|Removed |Added CC||ciro.santi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 379116] Failure when updating kate
https://bugs.kde.org/show_bug.cgi?id=379116 Harald Sitter changed: What|Removed |Added Latest Commit||https://commits.kde.org/ki1 ||8n/7bce4e8128365de13682b400 ||e4acf5b393e94ab9 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Harald Sitter --- Git commit 7bce4e8128365de13682b400e4acf5b393e94ab9 by Harald Sitter. Committed on 25/04/2017 at 08:30. Pushed by sitter into branch 'master'. fix basename handling of po files Summary: get_filename_component(... ... NAME_WE) gets the name without the *longest* extension. in case of 'org.kde.plasma.kittens.po' that would leave us with 'org' as name. Use a regular expression to grab the basename without the short extension (e.g. 'org.kde.plasma.kittens') to prevent broken file names. add a test to assert that this works in the future Reviewers: apol, ilic Reviewed By: apol Subscribers: #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D5557 M +13 -0autotests/CMakeLists.txt A +6-0autotests/ki18n_install/CMakeLists.txt A +20 -0 autotests/ki18n_install/po/de/plasma_applet_org.kde.plasma.katesessions.po A +5-0autotests/ki18n_install/test.cmake M +6-1cmake/build-pofiles.cmake https://commits.kde.org/ki18n/7bce4e8128365de13682b400e4acf5b393e94ab9 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 379116] Failure when updating kate
https://bugs.kde.org/show_bug.cgi?id=379116 --- Comment #7 from Harald Sitter --- builds retried, the situation should pretty much auto-resolve. do note that you will likely encounter the problem again when that happens simply force an overwrite. None of the debs are correct so it doesn't matter which one you force. Once all affected packages were updated once it'll be fixed for good. sudo dpkg --install --force-overwrite /var/cache/apt/archives/foo.deb $ ./jenkins_retry.rb -b '^xenial_(unstable|stable)_[^_]+_(marble|kate|kscreen|plasma-workspace|kdeplasma-addons|plasma-desktop)+$' I, [2017-04-25T10:37:58.453217 #12931] INFO -- retry: /^xenial_(unstable|stable)_[^_]+_(marble|kate|kscreen|plasma-workspace|kdeplasma-addons|plasma-desktop)+$/ I, [2017-04-25T10:37:59.153385 #12931] INFO -- retry: Setting system into maintenance mode. I, [2017-04-25T10:38:00.292468 #12931] INFO -- retry: xenial_stable_plasma_kscreen | status - success | queued - false I, [2017-04-25T10:38:00.494518 #12931] INFO -- retry: xenial_unstable_plasma_kscreen | status - success | queued - false I, [2017-04-25T10:38:00.570096 #12931] INFO -- retry: xenial_stable_plasma_plasma-desktop | status - unstable | queued - false I, [2017-04-25T10:38:00.582361 #12931] INFO -- retry: xenial_unstable_applications_kate | status - success | queued - false I, [2017-04-25T10:38:00.605418 #12931] INFO -- retry: xenial_unstable_plasma_plasma-desktop | status - failure | queued - false W, [2017-04-25T10:38:00.886758 #12931] WARN -- retry: xenial_unstable_plasma_kscreen --> build W, [2017-04-25T10:38:01.039269 #12931] WARN -- retry: xenial_stable_plasma_plasma-desktop --> build W, [2017-04-25T10:38:01.063465 #12931] WARN -- retry: xenial_unstable_applications_kate --> build I, [2017-04-25T10:38:01.077934 #12931] INFO -- retry: xenial_unstable_plasma_kdeplasma-addons | status - failure | queued - false I, [2017-04-25T10:38:01.456546 #12931] INFO -- retry: xenial_stable_applications_kate | status - success | queued - false I, [2017-04-25T10:38:01.552402 #12931] INFO -- retry: xenial_stable_applications_marble | status - failure | queued - false W, [2017-04-25T10:38:01.870864 #12931] WARN -- retry: xenial_unstable_plasma_kdeplasma-addons --> build W, [2017-04-25T10:38:02.191068 #12931] WARN -- retry: xenial_stable_applications_kate --> build W, [2017-04-25T10:38:02.299011 #12931] WARN -- retry: xenial_stable_applications_marble --> build I, [2017-04-25T10:38:05.609966 #12931] INFO -- retry: xenial_stable_plasma_plasma-workspace | status - unstable | queued - false I, [2017-04-25T10:38:05.628753 #12931] INFO -- retry: xenial_unstable_plasma_plasma-workspace | status - unstable | queued - false I, [2017-04-25T10:38:05.702539 #12931] INFO -- retry: xenial_unstable_applications_marble | status - failure | queued - false I, [2017-04-25T10:38:05.724345 #12931] INFO -- retry: xenial_stable_plasma_kdeplasma-addons | status - unstable | queued - false W, [2017-04-25T10:38:06.173275 #12931] WARN -- retry: xenial_unstable_plasma_plasma-desktop --> build W, [2017-04-25T10:38:06.257982 #12931] WARN -- retry: xenial_stable_plasma_kscreen --> build W, [2017-04-25T10:38:06.427483 #12931] WARN -- retry: xenial_unstable_plasma_plasma-workspace --> build W, [2017-04-25T10:38:06.582744 #12931] WARN -- retry: xenial_unstable_applications_marble --> build W, [2017-04-25T10:38:06.719650 #12931] WARN -- retry: xenial_stable_plasma_kdeplasma-addons --> build W, [2017-04-25T10:38:11.484999 #12931] WARN -- retry: xenial_stable_plasma_plasma-workspace --> build -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 379184] New: Endless loop for authentication
https://bugs.kde.org/show_bug.cgi?id=379184 Bug ID: 379184 Summary: Endless loop for authentication Product: kio-gdrive Version: 1.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: s.sut...@gmx.de Target Milestone: --- Google ask me for username & password, than for permission to allow. I give all permissions... then, the login-screen of google appear again. This is an endless loop. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379114] (Git master only) Segfault when opening a document containing a file layer
https://bugs.kde.org/show_bug.cgi?id=379114 Boudewijn Rempt changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/3c37f43d9a4f2dc82fa67dea ||a22fa7b71c61a718 --- Comment #2 from Boudewijn Rempt --- Git commit 3c37f43d9a4f2dc82fa67deaa22fa7b71c61a718 by Boudewijn Rempt. Committed on 25/04/2017 at 09:10. Pushed by rempt into branch 'master'. We cannot load images outside the GUI thread because of all the qobjects that can be created. Besides, the spinning bar dialog is the wrong approach to feedback, especially if the statusbar progressbar is still present, but Krita should be giving progress feedback in the statusbar. M +0-5libs/ui/KisImportExportManager.cpp https://commits.kde.org/krita/3c37f43d9a4f2dc82fa67deaa22fa7b71c61a718 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378846] If canvas is zoomed out, brushes get very slow
https://bugs.kde.org/show_bug.cgi?id=378846 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #3 from Boudewijn Rempt --- Which opengl driver are you using? Looks like it has problems updating the projection. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379185] New: file sort order by name is wrong in dolphin/kate file open dialog/etc
https://bugs.kde.org/show_bug.cgi?id=379185 Bug ID: 379185 Summary: file sort order by name is wrong in dolphin/kate file open dialog/etc Product: dolphin Version: 17.03.80 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: vkr...@yahoo.com Target Milestone: --- Created attachment 105179 --> https://bugs.kde.org/attachment.cgi?id=105179&action=edit Screenshot illustrating the problem. openSUSE 42.2, $ rpm -q dolphin kate plasma5-workspace-libs dolphin-17.03.80-81.16.x86_64 kate-17.04.0-4.3.x86_64 plasma5-workspace-libs-5.9.4-306.2.x86_64 mkdir /tmp/dir cd /tmp/dir touch a1 a11 a112 a2 a211 a22 a221 a223 a3 a33 a331 Then compare the order of files in the output of "ls -alF" with the order of files in Dolphin or Kate's Open dialog when sorting by name. Clearly, the latter applications are not doing the expected thing. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 376620] breeze-dark: badly readable gray on gray text in plasma widgets
https://bugs.kde.org/show_bug.cgi?id=376620 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379186] New: Crashing on new file dialog
https://bugs.kde.org/show_bug.cgi?id=379186 Bug ID: 379186 Summary: Crashing on new file dialog Product: krita Version: 3.1.3-beta Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bug.repor...@web.de Target Milestone: --- Krita 3.1.3beta crashes on new file dialog (2048x2048px/300pp). Hit "Create" will crash Krita instantly repeatedly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 350148] plasmashell wants "metadata.desktop" files in slideshow sub-directories for some reason and isn't too shy to mention it 3 times per image
https://bugs.kde.org/show_bug.cgi?id=350148 Nick Cross changed: What|Removed |Added CC||k...@goots.org -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379075] 'Sort Ascending' and 'Sort Descending' Buttons do not seem to work.
https://bugs.kde.org/show_bug.cgi?id=379075 Jarosław Staniek changed: What|Removed |Added Target Milestone|--- |3.0.2 -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379075] Sorting by current field not working in forms
https://bugs.kde.org/show_bug.cgi?id=379075 Jarosław Staniek changed: What|Removed |Added Assignee|kexi-b...@kde.org |stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379075] 'Sort Ascending' and 'Sort Descending' Buttons do not seem to work.
https://bugs.kde.org/show_bug.cgi?id=379075 Jarosław Staniek changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |ASSIGNED --- Comment #2 from Jarosław Staniek --- Confirmed then. Sorting is performed but the currently focused field is not properly detected so different sorting field is used, at least sometimes. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379075] Sorting by current field not working in forms
https://bugs.kde.org/show_bug.cgi?id=379075 Jarosław Staniek changed: What|Removed |Added Summary|'Sort Ascending' and 'Sort |Sorting by current field |Descending' Buttons do not |not working in forms |seem to work. | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376723] Non-selectable strings in layer blending modes
https://bugs.kde.org/show_bug.cgi?id=376723 Alexey changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID |--- --- Comment #2 from Alexey --- (In reply to wolthera from comment #1) > That's because the new layers are grayscale layers, you need to toggle > 'output to color not grayscale' if you want all the blending modes to work. O'key... but all blending modes works correct if we simple reselect layer (no change a color space!). And layers color space is rgb, not grayscale. :) So, it's works but not works right after separation. So — it's a bug, not a feature. Minor bug but may be misleading. P.S. I apologize for my awkward English, this is not my primary language -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379080] Changing Fields Types
https://bugs.kde.org/show_bug.cgi?id=379080 --- Comment #2 from Ian Whitfield --- Created attachment 105180 --> https://bugs.kde.org/attachment.cgi?id=105180&action=edit Incorrect Field Type -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379080] Changing Fields Types
https://bugs.kde.org/show_bug.cgi?id=379080 --- Comment #3 from Ian Whitfield --- Created attachment 105181 --> https://bugs.kde.org/attachment.cgi?id=105181&action=edit Error Message after Change -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376723] Non-selectable strings in layer blending modes
https://bugs.kde.org/show_bug.cgi?id=376723 Alexey changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376723] Non-selectable strings in layer blending modes
https://bugs.kde.org/show_bug.cgi?id=376723 Alexey changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 379160] baloo-widgets .po files not extracted
https://bugs.kde.org/show_bug.cgi?id=379160 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Harald Sitter --- As I understand it that was fixed in the metadata -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379080] Changing Fields Types
https://bugs.kde.org/show_bug.cgi?id=379080 --- Comment #4 from Jarosław Staniek --- OK, so the "Error Message after Change" is rather warning about action that can't be undone. You've changed the field type, saved. What happened? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376723] Non-selectable strings in layer blending modes
https://bugs.kde.org/show_bug.cgi?id=376723 --- Comment #3 from Alexey --- Created attachment 105182 --> https://bugs.kde.org/attachment.cgi?id=105182&action=edit moving layers and reselect layers Yep! I be not correct, it's grayscale color space... but: — Do you think this works correctly? ;) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 379187] New: PHP class generation from code fails
https://bugs.kde.org/show_bug.cgi?id=379187 Bug ID: 379187 Summary: PHP class generation from code fails Product: umbrello Version: 2.21.3 (KDE Applications 16.12.3) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: clemens.j...@floh.de Target Milestone: --- Created attachment 105183 --> https://bugs.kde.org/attachment.cgi?id=105183&action=edit Example of PHP file from which generating an UML class fails. Hi, I am using the latest Umbrello version 2.22.0 on Archlinux. I'm trying to generate an UML class from PHP code (PHP5 compatible) but it fails with various errors in the log complaining about the code syntax. The only thing I will get is a "file"-entity in the components view but there should be a "class"-entity in the logical view I think. Generating UML classes from java source works as expected. I'll attach you an example of the failing file so you can try yourself. Best whishes Clemens -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 377272] Multiple monitors with different resoltuion UI auto scaling
https://bugs.kde.org/show_bug.cgi?id=377272 Lukasz changed: What|Removed |Added CC||dolo...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 375467] Cantor hangs at "Initializing Session" when choosing Sage backend
https://bugs.kde.org/show_bug.cgi?id=375467 hackitfor...@gmail.com changed: What|Removed |Added CC||hackitfor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 377195] Cantor hangs at "Initializing session" when choosing R backend
https://bugs.kde.org/show_bug.cgi?id=377195 hackitfor...@gmail.com changed: What|Removed |Added CC||hackitfor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 379188] New: Cantor can't initialize session for multiple backends
https://bugs.kde.org/show_bug.cgi?id=379188 Bug ID: 379188 Summary: Cantor can't initialize session for multiple backends Product: cantor Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fil...@kde.org Reporter: hackitfor...@gmail.com CC: alexanderrie...@gmail.com Target Milestone: --- Using the 17.04 version cantor. Way to reproduce: 1. In arch linux, install cantor, sagemath, maxima, r. 2. Start cantor, choose any one of the sage, maxima, or r sessions. 3. Initializing takes forever. 4. When clicking cancel while initializing, the corresponding help menus (Show Sage Help, Show Maxima Help, Show R help) appear normally and usable. The session, however, is blank, without cursor etc. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379151] Konsole header text overlaps command text
https://bugs.kde.org/show_bug.cgi?id=379151 --- Comment #4 from SeederKun --- (In reply to Kurt Hindenburg from comment #3) > well I hope Noto Sans is not the default - it is not a fixed width font (so > of course it has issues) - try noto mono hmmm...I'm not so sure if it's noto sans all tho it's noto font but dunno if its sans or mono I will check that and reply back Thank you -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379080] Changing Fields Types
https://bugs.kde.org/show_bug.cgi?id=379080 --- Comment #5 from Ian Whitfield --- Don't know!!! I'm scared of losing my Database and don't want to have to do all that work again!! I could try on the other DB as I have it on two different machines OK - Just tried it. I changed a Field to a different Type and selected 'Save' and got the Error Message as reported. I selected 'OK' and Kexi "crashed" I re-opened Kexi and looked at the Table and ALL THE DATA HAS GONE!! IMHO this has to be changed/modified or something! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379151] Konsole header text overlaps command text
https://bugs.kde.org/show_bug.cgi?id=379151 --- Comment #5 from SeederKun --- (In reply to SeederKun from comment #4) > (In reply to Kurt Hindenburg from comment #3) > > well I hope Noto Sans is not the default - it is not a fixed width font (so > > of course it has issues) - try noto mono > > hmmm...I'm not so sure if it's noto sans all tho it's noto font but dunno if > its sans or mono > I will check that and reply back > > Thank you ok after checking...it's noto sans like I said before so do I have to change it to noto mono will try and give a feedback Thanks again -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379080] Changing Fields Types
https://bugs.kde.org/show_bug.cgi?id=379080 --- Comment #6 from Jarosław Staniek --- > I'm scared of losing my Database and don't want to have to do all > that work again!! Whenever you need to test such things, just copy your kexi file to a new name and play with the copy... And backup your work regularly. > I selected 'OK' and Kexi "crashed" Kexi version? We need to know if this was fixed recently. Please note this https://forum.kde.org/viewtopic.php?f=220&t=138821#p375259 > I re-opened Kexi and looked at the Table and ALL THE DATA > HAS GONE!! IMHO this has to be changed/modified or something! Yes, this is in development: https://bugs.kde.org/show_bug.cgi?id=125253 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379151] Konsole header text overlaps command text
https://bugs.kde.org/show_bug.cgi?id=379151 --- Comment #6 from SeederKun --- (In reply to SeederKun from comment #5) > (In reply to SeederKun from comment #4) > > (In reply to Kurt Hindenburg from comment #3) > > > well I hope Noto Sans is not the default - it is not a fixed width font > > > (so > > > of course it has issues) - try noto mono > > > > hmmm...I'm not so sure if it's noto sans all tho it's noto font but dunno if > > its sans or mono > > I will check that and reply back > > > > Thank you > > ok after checking...it's noto sans like I said before > so do I have to change it to noto mono > > will try and give a feedback > > Thanks again ok so basically the fixed width was dejavu sans I think I changed that by mistake lol I made it to noto mono and everything is fine now in konsole Thank you very much!!! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378877] Brush offset/scaling on canvas
https://bugs.kde.org/show_bug.cgi?id=378877 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Severity|critical|normal Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- I'm sorry, but that really isn't a bug in Krita. It works fine on my test helix... You're using the latest driver as far as I can see. You could try to make a tablet log to see whether Krita is getting weird coordinates from the tablet driver, for instance because of display scaling. It could also be a problem with the wacom configuration or settings. The canvas listens to tablet events from the wintab driver; the rest of the gui gets synthetic mouse events from Windows, so it's not so strange that you see different behaviour. Also, you don't mention which version of Krita you're using? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376723] Non-selectable strings in layer blending modes
https://bugs.kde.org/show_bug.cgi?id=376723 Nicholas LaPointe changed: What|Removed |Added Resolution|--- |DUPLICATE CC||nicholaslapoin...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #4 from Nicholas LaPointe --- In the second video you posted, it looks like applying "Separate image" leads to the same bug I noticed a few months ago. I'll mark this report as a duplicate. *** This bug has been marked as a duplicate of bug 374386 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374386] Invalid composite op/color space combinations are reachable
https://bugs.kde.org/show_bug.cgi?id=374386 Nicholas LaPointe changed: What|Removed |Added CC||o-di...@ya.ru --- Comment #3 from Nicholas LaPointe --- *** Bug 376723 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379080] Changing Fields Types
https://bugs.kde.org/show_bug.cgi?id=379080 --- Comment #7 from Ian Whitfield --- I mentioned earlier - I'm running 3.1 Alpha AppImage 0324. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 378437] lost functionality
https://bugs.kde.org/show_bug.cgi?id=378437 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- In kmail or kaddressbook ? I don't understand what step do you use for reproducing bugs. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379189] New: Delete does not work for multiselection
https://bugs.kde.org/show_bug.cgi?id=379189 Bug ID: 379189 Summary: Delete does not work for multiselection Product: kmail2 Version: 5.4.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: b...@mrvanes.com Target Milestone: --- Since upgrade to Kmail 5.4.3 I'm unable to Delete mails when multiple mails are selected. Mind that I don't mean "Move to Trash". I'm talking about "Delete" (skip trash) which has default shortcut shift-del attached to it. When I select one mail I can shift-delete it. When I select two or more mails, this fails. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368350] folder full text search doesn't work : folder status always 'still not indexed'
https://bugs.kde.org/show_bug.cgi?id=368350 --- Comment #7 from Jens --- (In reply to Laurent Montel from comment #6) > We fixed a lot of bug about it in 5.5.0. > Could you test it please ? > Regards KDE 5.5.0 or KMAIL 5.5.0? i use KDE-Plasma 5.9.4 and KDE-Framework 5.31.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378134] Crash on exit after pressing 'no' in save warning dialog box.
https://bugs.kde.org/show_bug.cgi?id=378134 Boudewijn Rempt changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/77540d4be574b5b38b265c7c ||c22a2e574f1bab5f Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Boudewijn Rempt --- Git commit 77540d4be574b5b38b265c7cc22a2e574f1bab5f by Boudewijn Rempt. Committed on 25/04/2017 at 11:46. Pushed by rempt into branch 'master'. Timing issues on closing krita can lead to the display renderer being gone before the palette docker is closed, which is why we put the pointer in a QPointer. M +1-1libs/ui/KisPaletteModel.cpp https://commits.kde.org/krita/77540d4be574b5b38b265c7cc22a2e574f1bab5f -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 375296] unable to use kdeconnect-cli to send an sms
https://bugs.kde.org/show_bug.cgi?id=375296 Laurent Montel changed: What|Removed |Added Latest Commit||https://commits.kde.org/ako ||nadi-contacts/44f16b485ee9a ||d207888d18b5db7320c2c7d72dc Status|UNCONFIRMED |RESOLVED Version Fixed In||5.5.1 Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- Git commit 44f16b485ee9ad207888d18b5db7320c2c7d72dc by Montel Laurent. Committed on 25/04/2017 at 11:53. Pushed by mlaurent into branch 'Applications/17.04'. Fix Bug 375296 - unable to use kdeconnect-cli to send an sms FIXED-IN: 5.5.1 I can't test it but we need to quote text and number M +3-3src/actions/sendsmsaction.cpp https://commits.kde.org/akonadi-contacts/44f16b485ee9ad207888d18b5db7320c2c7d72dc -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 370804] address book properties menu does not work
https://bugs.kde.org/show_bug.cgi?id=370804 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Laurent Montel --- Do you still have this problem ? (in new version ?) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379189] Delete does not work for multiselection
https://bugs.kde.org/show_bug.cgi?id=379189 --- Comment #1 from Martin van Es --- I've tested a little further and now notice that the mail list looses focus when (multi)selecting mails (it seems focus moves to the mail window, but I'm not sure). If I'm able to craftily refocus the maillist (while keeping the multiselection) I can shift-del the mails. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378741] Crash on creating new or opening file.
https://bugs.kde.org/show_bug.cgi?id=378741 wolthera changed: What|Removed |Added CC||bug.repor...@web.de --- Comment #4 from wolthera --- *** Bug 379186 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379186] Crashing on new file dialog
https://bugs.kde.org/show_bug.cgi?id=379186 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from wolthera --- *** This bug has been marked as a duplicate of bug 378741 *** -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 375296] unable to use kdeconnect-cli to send an sms
https://bugs.kde.org/show_bug.cgi?id=375296 --- Comment #2 from Philippe ROUBACH --- thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378821] Handbook
https://bugs.kde.org/show_bug.cgi?id=378821 wolthera changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- We don't support 2.9 anymore, I'm afraid. We're in the process of attempting to update steam to 3.0. In the meantime, the docs are up on docs.krita.org. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379190] New: Strikeout/underline not available in font dialogs
https://bugs.kde.org/show_bug.cgi?id=379190 Bug ID: 379190 Summary: Strikeout/underline not available in font dialogs Product: kexi Version: 3.1 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Reports and Printouts Assignee: kexi-b...@kde.org Reporter: stan...@kde.org CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- Strikeout/underline are not available in font dialogs. If we use KDE Plasma Desktop (XDG_CURRENT_DESKTOP=KDE env. variable) or a desktop with advanced font dialog, strikeout/underline font attributes are available. Otherwise, e.g. when XDG_CURRENT_DESKTOP=XFCE there's no way to set the attributes in Kexi for reports. Forms are also affected and any future use. Scope: Windows not affected. macOS: to be checked. Temporary workaround: try to set XDG_CURRENT_DESKTOP=KDE before running Kexi. Final solution: use the QFontDialog::DontUseNativeDialog flag to QFontDialog::getFont. Implementation note: fix in kexi and kproperty. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378207] New key-frame with content is swapped with new empty key-frame
https://bugs.kde.org/show_bug.cgi?id=378207 wolthera changed: What|Removed |Added Resolution|--- |INVALID CC||griffinval...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from wolthera --- While this does indeed happen, it is not a bug per se. The new keyframe will always add an empty frame at any given spot. You should be using copy keyframe for this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378426] Empty gray Kate screen
https://bugs.kde.org/show_bug.cgi?id=378426 --- Comment #6 from David RG --- Yeah, I just upgraded twice to 17.04. Now it won't even load, which I guess is a separate bug... Trace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa100b7a900 (LWP 24073))] Thread 3 (Thread 0x7fa0d277d700 (LWP 24076)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa0d699652b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fa0d6996257 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fa0f7da06da in start_thread (arg=0x7fa0d277d700) at pthread_create.c:456 #4 0x7fa0fb32c17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fa0eb554700 (LWP 24074)): #0 0x7fa0fb32018d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa0f5c6f576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa0f5c6f68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa0fbf4cf2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa0fbef688a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa0fbd23fe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa0fc35f5c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fa0fbd28c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa0f7da06da in start_thread (arg=0x7fa0eb554700) at pthread_create.c:456 #9 0x7fa0fb32c17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fa100b7a900 (LWP 24073)): [KCrash Handler] #6 0x7fa0fd4ba810 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x5569c21f03c4 in ?? () #8 0x5569c21f08a2 in ?? () #9 0x5569c21f2250 in ?? () #10 0x5569c21e30e7 in ?? () #11 0x5569c21cdab2 in ?? () #12 0x5569c22039d5 in ?? () #13 0x5569c22049db in ?? () #14 0x5569c2204e66 in ?? () #15 0x5569c220552c in ?? () #16 0x5569c21d053c in ?? () #17 0x5569c21d08f5 in ?? () #18 0x5569c21c9008 in ?? () #19 0x7fa0fb2443f1 in __libc_start_main (main=0x5569c21c6fd0, argc=1, argv=0x7ffecc1147d8, init=, fini=, rtld_fini=, stack_end=0x7ffecc1147c8) at ../csu/libc-start.c:291 #20 0x5569c21cac6a in _start () -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379190] Strikeout/underline not available in font dialogs
https://bugs.kde.org/show_bug.cgi?id=379190 Jarosław Staniek changed: What|Removed |Added Assignee|kexi-b...@kde.org |stan...@kde.org Ever confirmed|0 |1 Target Milestone|--- |3.0.2 Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379191] New: PlasmaShell disapeared and reappeared after few seconds - only once
https://bugs.kde.org/show_bug.cgi?id=379191 Bug ID: 379191 Summary: PlasmaShell disapeared and reappeared after few seconds - only once Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde_...@dlk.pl CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.8-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: just plainly switching to next song by shortcut, but i don't think thats related, it was first crash, -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f780cefe800 (LWP 1322))] Thread 27 (Thread 0x7f76f1896700 (LWP 30011)): #0 0x7f78013f2e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f78013acc99 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f78013ad6cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7f78013ad8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f7806eee06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f7806e9789a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7806cb9a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f7806cbe6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f7805b732e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f78065d154f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f36d75f7700 (LWP 8962)): #0 0x7f78065c767d in poll () at /usr/lib/libc.so.6 #1 0x7f77fb1bbee1 in () at /usr/lib/libpulse.so.0 #2 0x7f77fb1ad6f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f77fb1add8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f77fb1ade40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f77fb1bbe29 in () at /usr/lib/libpulse.so.0 #6 0x7f77fab4bfe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7f7805b732e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f78065d154f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7f76f0a77700 (LWP 8961)): #0 0x7f7806eed4ed in () at /usr/lib/libQt5Core.so.5 #1 0x7f78013acc8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f78013ad6cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7f78013ad8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f7806eee06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f7806e9789a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7806cb9a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f7809df1025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f7806cbe6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7805b732e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f78065d154f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f76f27fc700 (LWP 4670)): #0 0x7f7805b79756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7806cbf58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f77545d61d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f77545da9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f77545daa32 in
[krita] [Bug 378741] Crash on creating new or opening file.
https://bugs.kde.org/show_bug.cgi?id=378741 --- Comment #5 from Hank --- Sorry for the duplicate. I tried my best to search the bug tracker list with no result. At least I´m glad I´m not alone. FWIW: I´m still on macOS Yosemite. Cheers -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379192] New: KRun freezes the ui for a 1-2 secs in some cases
https://bugs.kde.org/show_bug.cgi?id=379192 Bug ID: 379192 Summary: KRun freezes the ui for a 1-2 secs in some cases Product: plasmashell Version: 5.9.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mvourla...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 105184 --> https://bugs.kde.org/attachment.cgi?id=105184&action=edit kate desktop file Trying to execute some specific launchers (this is not happening with all launchers) freezes for a sec the plasma ui. This was discovered first with Latte and I tried to follow the codepath. Latte is using a bouncing animation when a launcher is clicked and at the same time triggers from libtaskmanager the activation of that app. (libtaskamanager is using KRun for this). There are launchers that freeze all the ui totally for 1-2 secs in the above case (in Tumbleweed, kwrite and kate launchers) I initially tried to add the app launching code that was using KRun inside a separate thread. I was hoping that this would be enough but didnt improve anything. Following this issue more, from other users and developers it was noticed that the same ui freeze is happening also for the plasmashell panels when the specific launchers are triggered I attach also the desktop files -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379192] KRun freezes the ui for a 1-2 secs in some cases
https://bugs.kde.org/show_bug.cgi?id=379192 --- Comment #1 from Michail Vourlakos --- Created attachment 105185 --> https://bugs.kde.org/attachment.cgi?id=105185&action=edit kwrite desktop file -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379151] Konsole header text overlaps command text
https://bugs.kde.org/show_bug.cgi?id=379151 Kurt Hindenburg changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376405] Saturation value in HSV adjustment isn't restored
https://bugs.kde.org/show_bug.cgi?id=376405 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #3 from Boudewijn Rempt --- Thanks for the patch! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376405] Saturation value in HSV adjustment isn't restored
https://bugs.kde.org/show_bug.cgi?id=376405 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Latest Commit||https://commits.kde.org/kri ||ta/581b87f6469894f6c7ee1d2f ||19bbf34883b869be Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Boudewijn Rempt --- Thanks for the patch! --- Comment #4 from Boudewijn Rempt --- Git commit 581b87f6469894f6c7ee1d2f19bbf34883b869be by Boudewijn Rempt. Committed on 25/04/2017 at 12:38. Pushed by rempt into branch 'master'. This fixes loading a hsv adjustment from a filter layer and editing them. M +5-2plugins/filters/colorsfilters/wdg_hsv_adjustment.ui https://commits.kde.org/krita/581b87f6469894f6c7ee1d2f19bbf34883b869be -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368363] OpenGL canvas remains blank with some driver/gpu combinations on Windows
https://bugs.kde.org/show_bug.cgi?id=368363 --- Comment #7 from Boudewijn Rempt --- Krita only uses the nvidia driver if you explicitly start it with that driver, using right-click on the executable, select display driver. At least, it's that way on my dual gpu device. Your intel driver is indeed the outdated one with the know bug. Current is 15.something: https://downloadcenter.intel.com/product/81500/Intel-HD-Graphics-3000 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360415] amd64 instructions ADCX and ADOX are not implemented in VEX
https://bugs.kde.org/show_bug.cgi?id=360415 Jeffrey Walton changed: What|Removed |Added CC||noloa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376085] shift-drag doesn't correctly resize the quick brush
https://bugs.kde.org/show_bug.cgi?id=376085 Boudewijn Rempt changed: What|Removed |Added Summary|In latest git master, the |shift-drag doesn't |brush doesn't get resized |correctly resize the quick |beyond 1k size with shift |brush |drag| --- Comment #7 from Boudewijn Rempt --- Yeah, the hickup is normal: it's because at that point the masks are generated for the larger sizes. Those masks are going to take a serious amount of memory, by the way. But weird that the bug happens with specifically the quick brush engine. I guess that one doesn't implement brush resizing correctly. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 379164] kdepim-runtime translations missing
https://bugs.kde.org/show_bug.cgi?id=379164 Harald Sitter changed: What|Removed |Added Latest Commit||https://commits.kde.org/rel ||easeme/fbb33d15f0792086b281 ||eafb099c4964f5755209 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- Git commit fbb33d15f0792086b281eafb099c4964f5755209 by Harald Sitter. Committed on 25/04/2017 at 11:06. Pushed by sitter into branch 'master'. make sure modules that are projects get i18n_paths constructed properly We unconditionally dropped the last part of a path to get the i18n_path, not paying attention to us potentially dropping the last part thus rendering the path empty. Instead only drop the last part iff it isn't the only part in the array. M +4-1lib/releaseme/project.rb M +20 -0test/data/kde_projects.xml M +10 -0test/test_project.rb https://commits.kde.org/releaseme/fbb33d15f0792086b281eafb099c4964f5755209 -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 379161] kdegraphics/libs translations not found
https://bugs.kde.org/show_bug.cgi?id=379161
Harald Sitter changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/rel
||easeme/309af97921a89423941b
||5d6a5cefaed4e534c1cb
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Harald Sitter ---
Git commit 309af97921a89423941b5d6a5cefaed4e534c1cb by Harald Sitter.
Committed on 25/04/2017 at 12:42.
Pushed by sitter into branch 'master'.
reduce drop limit after removing a leading kde/ part
The general assumption is that path.split.pop.join('-') will be the
i18n_path. e.g. playground/utils becomes playground-utils and
playground/utils/libs becomes also playground-utils. To that end we drop
parts until we have <= 2 to join. This was going wrong with nested projects
inside kde/* projects as we drop the first kde/ part.
So kde/kdegraphics/libs would be [kde,kdegraphics,libs] then we drop the
kde to get [kdegraphics,libs] and now no longer drop parts treating it
like playground, when really it shouldn't be as effectively our
requirements are different. Technically we want [kde,kdegraphics,libs] to
be popped until only 2 are left, we can't do that because dropping kde
is sort of a pre condition, otherwise we'll have to do some mind bending
to prevent empty paths etc.
M +49 -14 lib/releaseme/project.rb
M +48 -0test/data/kde_projects.xml
M +11 -1test/test_project.rb
https://commits.kde.org/releaseme/309af97921a89423941b5d6a5cefaed4e534c1cb
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 369349] Low framerate when drawing with the stabilizer
https://bugs.kde.org/show_bug.cgi?id=369349 --- Comment #21 from Boudewijn Rempt --- Which version are you using? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 353474] Hidden icon 'Path editing' for 'Vector Selection'
https://bugs.kde.org/show_bug.cgi?id=353474 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Boudewijn Rempt --- Yes, this is done in master. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360415] amd64 instructions ADCX and ADOX are not implemented in VEX
https://bugs.kde.org/show_bug.cgi?id=360415
--- Comment #4 from Jeffrey Walton ---
I'm working from the SVN sources, and the issue still exists. It appears
something is amiss with the patch.
The program was built with Clang on a Skylake machine. Its not in the big
integer part of the library. Clang is using it for regular math.
**
Here's what GDB shows:
Breakpoint 2, ECP::EncodedPointSize (this=0x7fffb3f8,
compressed=0x0) at ./ecp.h:75
75 {return 1 +
(compressed?1:2)*GetField().MaxElementByteLength();}
(gdb) disass
Dump of assembler code for function ECP::EncodedPointSize(bool) const:
=> 0x00594750 <+0>: push %rbx
0x00594751 <+1>: xor%eax,%eax
0x00594753 <+3>: cmp$0x1,%sil
0x00594757 <+7>: mov$0x1,%ebx
0x0059475c <+12>:adcx %eax,%ebx
0x00594761 <+17>:callq 0x475eb0
0x00594766 <+22>:mov%rax,%rdi
0x00594769 <+25>:callq 0x521020
0x0059476e <+30>:imul %ebx,%eax
0x00594771 <+33>:add$0x1,%eax
0x00594774 <+36>:pop%rbx
0x00594775 <+37>:retq
End of assembler dump.
**
Here's what Valgrind shows:
valgrind ./cryptest.exe v
...
HMQV validation suite running...
vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x38 0xF6 0xD8 0xE8 0x4A
0x17 0xEE 0xFF
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F38
vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
==12079== valgrind: Unrecognised instruction at address 0x59475c.
==12079==at 0x59475C: ECP::EncodedPointSize(bool) const (ecp.h:75)
==12079==by 0x591A3B: ECP::DecodePoint(ECPPoint&, BufferedTransformation&,
unsigned long) const (ecp.cpp:107)
==12079==by 0x5917DD: ECP::DecodePoint(ECPPoint&, unsigned char const*,
unsigned long) const (ecp.cpp:69)
==12079==by 0x591D66: ECP::BERDecodePoint(BufferedTransformation&) const
(ecp.cpp:151)
==12079==by 0x54E3EA:
DL_GroupParameters_EC::BERDecode(BufferedTransformation&)
(eccrypto.cpp:534)
==12079==by 0x4AAF77: Test::ValidateHMQV() (validat2.cpp:392)
==12079==by 0x48201A: Test::ValidateAll(bool) (validat1.cpp:162)
==12079==by 0x4369B6: Validate(int, bool, char const*) (test.cpp:916)
==12079==by 0x432FE4: main (test.cpp:406)
==12079== Your program just tried to execute an instruction that Valgrind
==12079== did not recognise. There are two possible reasons for this.
==12079== 1. Your program has a bug and erroneously jumped to a non-code
==12079==location. If you are running Memcheck and you just saw a
==12079==warning about a bad jump, it's probably your program's fault.
==12079== 2. The instruction is legitimate but Valgrind doesn't handle it,
==12079==i.e. it's Valgrind's fault. If you think this is the case or
==12079==you are not sure, please let us know and we'll try to fix it.
==12079== Either way, Valgrind will now raise a SIGILL signal which will
==12079== probably kill your program.
==12079==
==12079== Process terminating with default action of signal 4 (SIGILL)
==12079== Illegal opcode at address 0x59475C
==12079==at 0x59475C: ECP::EncodedPointSize(bool) const (ecp.h:75)
==12079==by 0x591A3B: ECP::DecodePoint(ECPPoint&, BufferedTransformation&,
unsigned long) const (ecp.cpp:107)
==12079==by 0x5917DD: ECP::DecodePoint(ECPPoint&, unsigned char const*,
unsigned long) const (ecp.cpp:69)
==12079==by 0x591D66: ECP::BERDecodePoint(BufferedTransformation&) const
(ecp.cpp:151)
==12079==by 0x54E3EA:
DL_GroupParameters_EC::BERDecode(BufferedTransformation&)
(eccrypto.cpp:534)
==12079==by 0x4AAF77: Test::ValidateHMQV() (validat2.cpp:392)
==12079==by 0x48201A: Test::ValidateAll(bool) (validat1.cpp:162)
==12079==by 0x4369B6: Validate(int, bool, char const*) (test.cpp:916)
==12079==by 0x432FE4: main (test.cpp:406)
==12079==
==12079== HEAP SUMMARY:
==12079== in use at exit: 69,547 bytes in 538 blocks
==12079== total heap usage: 210,211 allocs, 209,673 frees, 67,196,780 bytes
allocated
==12079==
==12079== LEAK SUMMARY:
==12079==definitely lost: 0 bytes in 0 blocks
==12079==indirectly lost: 0 bytes in 0 blocks
==12079== possibly lost: 0 bytes in 0 blocks
==12079==still reachable: 69,547 bytes in 538 blocks
==12079== suppressed: 0 bytes in 0 blocks
==12079== Rerun with --leak-check=full to see details of leaked memory
==12079==
==12079== For counts of detected and suppressed errors, rerun with: -v
==12079== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction (core dumped)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 370722] Krita crashes when choosing OK in the configuration window
https://bugs.kde.org/show_bug.cgi?id=370722 --- Comment #7 from Boudewijn Rempt --- And does it also happen if you run krita explicitly on the nvidia gpu? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369349] Low framerate when drawing with the stabilizer
https://bugs.kde.org/show_bug.cgi?id=369349 --- Comment #22 from Mat --- The lastest nightly build -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378942] Add a brush size docker
https://bugs.kde.org/show_bug.cgi?id=378942 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Boudewijn Rempt --- Well, if it's just having a bunch of diameter icons, then adding setBrushSize(int) to the Canvas api should be enough to make it possible to implement a docker like this. I wouldn't package the script with Krita by default, though, put it on share.kde.org. It can be handy for people who come from sai, but for others it's likely just clutter. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379193] New: DDoSing discover/featured-5.9.json ocs/providers.xml
https://bugs.kde.org/show_bug.cgi?id=379193 Bug ID: 379193 Summary: DDoSing discover/featured-5.9.json ocs/providers.xml Product: Discover Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: j...@jriddell.org Target Milestone: --- okay, Discover has a severe DOS bug then I see a pattern repeating over and over where the url /ocs/providers.xml is absolutely slammed very hard and I mean like 20 requests in a single second hard at the same time that IP also hits that discover featured url https://autoconfig.kde.org/discover/featured-5.9.json is what is looks for yep, thats the vhost that gets hammered (it hits download.kde.org/ocs/providers.xml first though) is there any reason why it would want to fetch 20 or so copies of the OCS providers.xml file? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379193] DDoSing discover/featured-5.9.json ocs/providers.xml
https://bugs.kde.org/show_bug.cgi?id=379193 Jonathan Riddell changed: What|Removed |Added CC||bcooks...@kde.org, ||j...@jriddell.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"
https://bugs.kde.org/show_bug.cgi?id=362856 Giuseppe Ghibò changed: What|Removed |Added CC||gh...@mageia.org --- Comment #27 from Giuseppe Ghibò --- I'm using the DPI forced to 282 but I get this problems too when using QT_AUTO_SCREEN_SCALE_FACTOR=1 which I use as default; forcing QT_AUTO_SCREEN_SCALE_FACTOR=0 before calling okular of course doesn't cause the loss of resolution but in that case fonts menus and especially widgets (scroll bars) aren't scaled properly. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 379194] New: Ambiguous Shortcuts - gwenview Cut and Remove -> Shift+Del
https://bugs.kde.org/show_bug.cgi?id=379194 Bug ID: 379194 Summary: Ambiguous Shortcuts - gwenview Cut and Remove -> Shift+Del Product: gwenview Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: gurge...@gmail.com CC: myr...@kde.org Target Milestone: --- Created attachment 105186 --> https://bugs.kde.org/attachment.cgi?id=105186&action=edit the warning, in portuguese First use of Opensuse 42.3. When I tried to open an image, the warning displays the message about ambiguous shrtcuts (in Portuguese. Cf. attachment). Cut and Remove have the same shortcut in Gwenview. The program runs normally. The solution is simply modify the Cut shortcut key to Ctrl+X, for example, in Settings -> Configure Shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 379194] Ambiguous Shortcuts - gwenview Cut and Remove -> Shift+Del
https://bugs.kde.org/show_bug.cgi?id=379194 Fernando Gurgel changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 379195] New: Konversation can't handle IDN urls
https://bugs.kde.org/show_bug.cgi?id=379195 Bug ID: 379195 Summary: Konversation can't handle IDN urls Product: konversation Version: 1.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: bugs5.kde@sjau.ch Target Milestone: --- Well, I just read an article about IDN urls and how they are used for phishing. One of the examples given was https://www.xn--80ak6aa92e.com/ (not apple) which shows in some browsers as apple.com. Anway, when I paste that url in Konversation and click on it to open it, an error message pops up: Malformed URL Invalid hostname (contains invalid characters); source was "https://www..com/";; scheme = "https", host = "", path = "/" The URL is correct but it seems Konversation can't handle IDN urls properly. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379196] New: Dolphin does not appear on the screen
https://bugs.kde.org/show_bug.cgi?id=379196 Bug ID: 379196 Summary: Dolphin does not appear on the screen Product: dolphin Version: 16.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: germano.massu...@gmail.com Target Milestone: --- I am trying to use dolphin 16.12.3 but it does not appear on the screen, so you get only a process running in background. I don't know at the moment if the bug is reproducible, since it is the first time I experience it, and I am using such Dolphin version since many days. Plasma 5.9.4 $ gdb dolphin 8514 GNU gdb (GDB) Fedora 7.12.1-47.fc25 Type "apropos word" to search for commands related to "word"... Reading symbols from dolphin...Reading symbols from /usr/lib/debug/usr/bin/dolphin.debug...done. done. Attaching to program: /usr/bin/dolphin, process 8514 [New LWP 8515] [New LWP 8516] [New LWP 8517] [New LWP 8518] [New LWP 8519] [New LWP 8520] [New LWP 8521] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fcb64f4c81d in nanosleep () at ../sysdeps/unix/syscall-template.S:84 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) (gdb) continue Continuing. (After 5 minutes) ^C Thread 1 "dolphin" received signal SIGINT, Interrupt. 0x7fcb64f4c81d in nanosleep () at ../sysdeps/unix/syscall-template.S:84 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) (gdb) bt #0 0x7fcb64f4c81d in nanosleep () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcb65c2bb8d in qt_nanosleep(timespec) (amount=...) at tools/qelapsedtimer_unix.cpp:193 #2 0x7fcb65b93dc8 in QThread::msleep(unsigned long) (msecs=msecs@entry=50) at thread/qthread_unix.cpp:506 #3 0x7fcb676e2cd8 in KDirWatchPrivate::useFAM(KDirWatchPrivate::Entry*) (this=this@entry=0x56251d9918d0, e=e@entry=0x56251d8a84e0) at /usr/src/debug/kcoreaddons-5.33.0/src/lib/io/kdirwatch.cpp:696 #4 0x7fcb676e306a in KDirWatchPrivate::addWatch(KDirWatchPrivate::Entry*) (this=this@entry=0x56251d9918d0, e=e@entry=0x56251d8a84e0) at /usr/src/debug/kcoreaddons-5.33.0/src/lib/io/kdirwatch.cpp:979 #5 0x7fcb676e3c33 in KDirWatchPrivate::addEntry(KDirWatch*, QString const&, KDirWatchPrivate::Entry*, bool, QFlags) (this=0x56251d9918d0, instance=instance@entry=0x56251d89f770, _path=..., sub_entry=, sub_entry@entry=0x0, isDir=isDir@entry=false, watchModes=..., watchModes@entry=...) at /usr/src/debug/kcoreaddons-5.33.0/src/lib/io/kdirwatch.cpp:936 #6 0x7fcb676e5e13 in KDirWatch::addFile(QString const&) (this=this@entry=0x56251d89f770, _path=...) at /usr/src/debug/kcoreaddons-5.33.0/src/lib/io/kdirwatch.cpp:1891 #7 0x7fcb69d91dbd in KBookmarkManager::KBookmarkManager(QString const&) (this=0x56251d89ce60, bookmarksFile=...) at /usr/src/debug/kbookmarks-5.33.0/src/kbookmarkmanager.cpp:293 #8 0x7fcb69d921e8 in KBookmarkManager::managerForExternalFile(QString const&) (bookmarksFile=...) at /usr/src/debug/kbookmarks-5.33.0/src/kbookmarkmanager.cpp:226 #9 0x7fcb6bc0cbc5 in KFilePlacesModel::KFilePlacesModel(QObject*) (this=0x56251d803a10, parent=) at /usr/src/debug/kio-5.33.0/src/filewidgets/kfileplacesmodel.cpp:93 #10 0x7fcb6c5fc1c6 in DolphinViewContainer::DolphinViewContainer(QUrl const&, QWidget*) (this=0x56251d88d800, url=..., parent=) at /usr/src/debug/dolphin-16.12.3/src/dolphinviewcontainer.cpp:72 #11 0x7fcb6c603d5c in DolphinTabPage::createViewContainer(QUrl const&) const (this=this@entry=0x56251d8870d0, url=...) at /usr/src/debug/dolphin-16.12.3/src/dolphintabpage.cpp:340 #12 0x7fcb6c603f93 in DolphinTabPage::DolphinTabPage(QUrl const&, QUrl const&, QWidget*) (this=0x56251d8870d0, primaryUrl=..., secondaryUrl=..., parent= to continue, or q to quit--- d out>) at /usr/src/debug/dolphin-16.12.3/src/dolphintabpage.cpp:42 #13 0x7fcb6c605a95 in DolphinTabWidget::openNewTab(QUrl const&, QUrl const&) (this=this@entry=0x56251d4a4960, primaryUrl=..., secondaryUrl=...) at /usr/src/debug/dolphin-16.12.3/src/dolphintabwidget.cpp:143 #14 0x7fcb6c605f26 in DolphinTabWidget::openDirectories(QList const&, bool) (this=0x56251d4a4960, dirs=..., splitView=false) at /usr/src/debug/dolphin-16.12.3/src/dolphintabwidget.cpp:169 #15 0x7fcb6c5efb7c in DolphinMainWindow::openDirectories(QList const&, bool) (this=, dirs=..., splitView=) at /usr/src/debug/dolphin-16.12.3/src/dolphinmainwindow.cpp:177 #16 0x7fcb6c60a41d in kdemain(int, char**) (argc=, argv=) at /usr/src/debug/dolphin-16.12.3/src/main.cpp:136 #17 0x7fcb64ea0401 in __libc_start_main (main= 0x56251bd09b10 , argc=1, argv=0x7fff2ea2a4e8, init=, fini=, rtld_fini=, stack_end=0x7fff2ea2a4d8) at ../csu/libc-start.c:289 #18 0x56251bd09b4a in _start () (gdb) -- You are receivin
[plasmashell] [Bug 379197] New: [Wayland] Close session leads to black screen
https://bugs.kde.org/show_bug.cgi?id=379197 Bug ID: 379197 Summary: [Wayland] Close session leads to black screen Product: plasmashell Version: 5.9.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: germano.massu...@gmail.com Target Milestone: 1.0 Exiting from Plasma session leads to black screen. User is not even able to switch to tty session. Intel video driver: i915 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378741] Crash on creating new or opening file.
https://bugs.kde.org/show_bug.cgi?id=378741 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Boudewijn Rempt --- Please try https://download.kde.org/unstable/krita/3.1.3-rc.1/krita-3.1.3-rc.1.dmg, it shouldn't contain the broken plugin. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369349] Low framerate when drawing with the stabilizer
https://bugs.kde.org/show_bug.cgi?id=369349 --- Comment #23 from Boudewijn Rempt --- Hm, that was broken for some time... But not that long. Have you tried to temporarily move your kritarc so you can test with a clean config? There are also setings subtelities that interact with your current zoom level and so on, but I haven't got the deep knowledge about that, I only heard about that in a video made by david revoy. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379198] New: PIM events plugin: remove passed events
https://bugs.kde.org/show_bug.cgi?id=379198 Bug ID: 379198 Summary: PIM events plugin: remove passed events Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: flo.hen...@gmail.com Target Milestone: 1.0 It would be nice if the PIM events plugin in the digital clock automatically hides events that are passed, for example I have an event from 8-10 in the morning and another one at 4 in the afternoon. If I open the digital clock at 11am only the 4pm event is show because the first event passed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379196] Dolphin does not appear on the screen
https://bugs.kde.org/show_bug.cgi?id=379196 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu --- Comment #1 from Rex Dieter --- I appears to be waiting on #3 0x7fcb676e2cd8 in KDirWatchPrivate::useFAM There's a long-standing issue where gamin will sometimes hang, if you have any current gamin processes, try killing them, and see if that helps. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 378945] Export of selected alarms fails
https://bugs.kde.org/show_bug.cgi?id=378945 --- Comment #2 from rusconi --- Greetings Jarvie, thank you for your reply. In fact, after thinking a bit about it, I reasoned that the most simple thing to backup is simply the calendar.ics file that contains all the active alarms. So, forget about my enquiry/suggestion. Filippo -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379199] New: "Recently used color" is not influenced by fill function
https://bugs.kde.org/show_bug.cgi?id=379199 Bug ID: 379199 Summary: "Recently used color" is not influenced by fill function Product: krita Version: 3.1.3-beta Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: color selectors Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- when using a stroke a new color gets added to "recently used colors" in the advanced color selector and the popup, but this isnt the case if you use the fill function (in the menu or via shorctut.) the fill tool does do this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379196] Dolphin does not appear on the screen
https://bugs.kde.org/show_bug.cgi?id=379196 --- Comment #2 from Germano Massullo --- https://bugzilla.gnome.org/show_bug.cgi?id=777997#c4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378780] Select All paints layer black
https://bugs.kde.org/show_bug.cgi?id=378780 Khalil changed: What|Removed |Added CC||khalil12...@mail.ru --- Comment #10 from Khalil --- Здравствуйте! Не могли бы вы подробнее описать проблему? Постарайтесь дать как можно больше информации, пожалуйста. По миниатюре слоя видно, что он не закрашен. Исчезает ли черный цвет при выполнении каких-либо действий? Не могли бы вы записать видео? Оно бы очень помогло. Исчезает ли проблема при обновлении Intel Graphics Driver? https://downloadcenter.intel.com Если проблема не будет решена, попробуйте отключить OpenGL >нашёл Простите, что именно вы нашли? Выключение OpenGL: Настройки => Настроить Krita => Монитор => OpenGL По поводу функционала и мелких проблем можете обращатся в IRC чат (Freenode => #krita), но там только английский. На русском можете обратится в https://vk.com/ilovefreeart, но это не официальное сообщество. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376954] overwrite mode crash
https://bugs.kde.org/show_bug.cgi?id=376954 legocef...@yahoo.fr changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from legocef...@yahoo.fr --- Good! Yesterday, I upgraded to kdenlive 17.04 and now, there is no crash when doing this operation. Thank by considering my bug repport. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379196] Dolphin does not appear on the screen
https://bugs.kde.org/show_bug.cgi?id=379196 Rex Dieter changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #3 from Rex Dieter --- marking closed->upstream (hang in a dependent service/library) -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 370522] kaddressbook: Progress window misbehaves on consecutive vCard imports
https://bugs.kde.org/show_bug.cgi?id=370522 Laurent Montel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||mon...@kde.org Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Laurent Montel --- it works fine here. Could you test with last version please ? -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 379200] New: Kleopatra crashes the whole system when trying to sign/encrypt the file.
https://bugs.kde.org/show_bug.cgi?id=379200 Bug ID: 379200 Summary: Kleopatra crashes the whole system when trying to sign/encrypt the file. Product: kleopatra Version: 2.2.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: raghavendra_...@rcomext.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- We are able to launch Kleopatra, but it crashes the whole system (in this case it's a Windows Virtual Environment) We have run process explorer to identify at what point it crashes and it was identified that as soon the Kleopatra tries to execute PinEntry.exe the whole virtual session freezes. With this we are unable to run any debugging or procmon tools to see what is happening. Could I request you to look into this please? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379201] New: Onion skins sometimes dont update immediatly on triggering the function
https://bugs.kde.org/show_bug.cgi?id=379201 Bug ID: 379201 Summary: Onion skins sometimes dont update immediatly on triggering the function Product: krita Version: 3.1.3-beta Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- when activating onion skins ,often i have to toggle between 2 frames to trigger the update of the canvas. This obviously should not happen this way, the onion skins need to update immediatly on activation/deactivation to avoid losing time and effort. The file i'm working now is 2880x1620 and has 50 to 60-ish frames with multiple layers (8 or so) it also happens if i make the canvas size smaller. It's 30MB in size. 8 bit depth. I have 64 GB of ram and an nvidia gtx980 during the typing of this bug, the bug stopped happening,maybe due to refreshing with isolate layer mode? or because I undid a resize? or Maybe it dumped my history? I dont know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379202] New: Plasma mostly crashes when I' m closing the Freepascal Application Lazarus
https://bugs.kde.org/show_bug.cgi?id=379202 Bug ID: 379202 Summary: Plasma mostly crashes when I' m closing the Freepascal Application Lazarus Product: plasmashell Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jtr...@freenet.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.6) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.57-18.3-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I closed the Freepascal Application Lazarus Best Regards JTryIt The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb3c7034900 (LWP 1822))] Thread 10 (Thread 0x7fb2f1f55700 (LWP 10161)): #0 0x7fb3c053e49d in poll () at /lib64/libc.so.6 #1 0x7fb3b61a30a1 in () at /usr/lib64/libpulse.so.0 #2 0x7fb3b619476c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7fb3b6194dde in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7fb3b6194e90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7fb3b61a3006 in () at /usr/lib64/libpulse.so.0 #6 0x7fb3b5b3a408 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #7 0x7fb3bfd47744 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb3c0546d3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fb2f1512700 (LWP 10160)): #0 0x7fb3c053e49d in poll () at /lib64/libc.so.6 #1 0x7fb3bcc05314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb3bcc0542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb3c0e4b32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb3c0df8fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb3c0c33f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb3c3f409c8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fb3c0c389e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb3bfd47744 in start_thread () at /lib64/libpthread.so.0 #9 0x7fb3c0546d3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fb303223700 (LWP 2278)): #0 0x7fb3bcc467b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb3bcc04969 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb3bcc05230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb3bcc0542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb3c0e4b32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb3c0df8fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb3c0c33f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fb30464b8f7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #8 0x7fb3c0c389e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb3bfd47744 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb3c0546d3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fb30ed55700 (LWP 2208)): #0 0x7fb3c6e8ab0e in _dl_update_slotinfo () at /lib64/ld-linux-x86-64.so.2 #1 0x7fb3c6e7a115 in update_get_addr () at /lib64/ld-linux-x86-64.so.2 #2 0x7fb3c0c37a06 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fb3c0e4b23a in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb3bcc0495d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #5 0x7fb3bcc05230 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7fb3bcc0542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #7 0x7fb3c0e4b32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fb3c0df8fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7fb3c0c33f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #10 0x7fb3c4ac3632 in () at /usr/lib64/libQt5Quick.so.5 #11 0x7fb3c0c389e9 in () at /usr/lib64/libQt5Core.so.5 #12 0x7fb3bfd47744 in start_thread () at /lib64/libpthread.so.0 #13 0x7fb3c0546d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fb39d6cf700 (LWP 1976)): #0 0x7fb3bfd4c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb3c671293b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fb3c6712969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fb3bfd47744 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb3c0546d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb39f3ff700 (LWP 1955)): #0 0x7fb3bcc467b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb3bcc04
[plasmashell] [Bug 379203] New: Plasma crash when removing panel
https://bugs.kde.org/show_bug.cgi?id=379203 Bug ID: 379203 Summary: Plasma crash when removing panel Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kendos.ken...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Closing the notification "panel removed" after deleting the bottom panel after I created and configured my top panel. - Unusual behavior I noticed: The panel removed notification appeared twice on the bottom (previous system tray) and top of the screen (new system tray). -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff77505f800 (LWP 3255))] Thread 15 (Thread 0x7ff67effd700 (LWP 14968)): #0 0x7ff76dcb3756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff76edf958b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7ff6bc55e1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7ff6bc5629d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7ff6bc560249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7ff76edf86d8 in () at /usr/lib/libQt5Core.so.5 #23 0x7ff76dcad2e7 in start_thread () at /usr/lib/libpthread.so.0 #24 0x7ff76e70b54f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7ff67f7fe700 (LWP 14967)): #0 0x7ff76dcb3756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff76edf958b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7ff6bc55e1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7ff6bc5629d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7ff6bc562a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7ff6bc55d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7ff6bc560249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x0
[krita] [Bug 379201] Onion skins sometimes dont update immediatly on triggering the function
https://bugs.kde.org/show_bug.cgi?id=379201 wolthera changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||griffinval...@gmail.com Ever confirmed|0 |1 --- Comment #1 from wolthera --- I have the same thing happening with an 8bit file at 2000x5000 with 16frames. I also have a similar issue where the canvas won't update properly when I toggle layer visibility on some layers. While it does say it is updating, it doesn't do much, and I have to switch frames to actually have it show anything. -- You are receiving this mail because: You are watching all bug changes.
