[kwin] [Bug 429365] New: ctrl + alt + f-key results in kwin crash
https://bugs.kde.org/show_bug.cgi?id=429365 Bug ID: 429365 Summary: ctrl + alt + f-key results in kwin crash Product: kwin Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mikon55...@bcpfm.com Target Milestone: --- Created attachment 133471 --> https://bugs.kde.org/attachment.cgi?id=133471=edit crash.txt SUMMARY Ctrl + Alt + F-key results in a black screen and a Kwin error on returning to ctrl + alt + F1. Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-29-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 15,6 GiB of RAM Graphics Processor: GeForce GTX 680MX/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421461] plasmashell memory spike and lag when removing wallpapers from Desktop-Settings menu
https://bugs.kde.org/show_bug.cgi?id=421461 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- How are you removing all wallpapers at once? You can remove a folder in the sidebar for the slideshow plugin, and you can remove individual wallpapers from the image plugin one at a time, but I'm not aware of a way to remove many at once. Can you clarify? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418027] Default wallpaper always applied to newly-connected screens
https://bugs.kde.org/show_bug.cgi?id=418027 Nate Graham changed: What|Removed |Added Summary|Change default wallpager|Default wallpaper always |for *all* screen|applied to newly-connected ||screens Severity|wishlist|minor Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408633] thin vertical line when wallpaper is scaled and cropped
https://bugs.kde.org/show_bug.cgi?id=408633 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #8 from Nate Graham --- I'm not able to reproduce this issue with a POTD wallpaper in Plasma 5.20. Are you? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404623] Desktop is NOT unloading properly the SlideShow wallpaper plugin
https://bugs.kde.org/show_bug.cgi?id=404623 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Are you still experiencing this in Plasma 5.20? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429364] New: Dolphin does not display dollar sign ($) in some file names
https://bugs.kde.org/show_bug.cgi?id=429364 Bug ID: 429364 Summary: Dolphin does not display dollar sign ($) in some file names Product: dolphin Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: cont...@yannsalmon.fr CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I accidentally created a file with a dollar sign in it. Dolphin does not display that sign in the name. This could cause confusion, at least. STEPS TO REPRODUCE 1. With bash, run touch 'file.na'$'me' 2. Open Dolphin and display the containing folder OBSERVED RESULT File is displayed as file.name EXPECTED RESULT File should be displayed as file.na$me SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION When the name ends with $, it gets displayed (eg. touch 'filename'$). But adding an empty string after makes it disappear (eg. touch 'filename'$''). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428375] System monitor sensor widget details window is blank after upgrade to plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=428375 --- Comment #12 from Marcio Merlnoe --- Created attachment 133470 --> https://bugs.kde.org/attachment.cgi?id=133470=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 424901] "Force filesystem indexing" feature is disabled after Elisa to be restarted
https://bugs.kde.org/show_bug.cgi?id=424901 mohamadhosein changed: What|Removed |Added CC||mhebte...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 428647] Elisa's fast search doesn't follow softlinks
https://bugs.kde.org/show_bug.cgi?id=428647 mohamadhosein changed: What|Removed |Added CC||mhebte...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428375] System monitor sensor widget details window is blank after upgrade to plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=428375 --- Comment #11 from Marcio Merlnoe --- Created attachment 133469 --> https://bugs.kde.org/attachment.cgi?id=133469=edit plasmashell --replace 2>&1 | tee -a log.txt -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428085] "Often Used/Recent file" list doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=428085 Nate Graham changed: What|Removed |Added Version Fixed In||5.77 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 94311] Use Kde password Wallet for keeping Nickserv's "identify" password's
https://bugs.kde.org/show_bug.cgi?id=94311 Mariano changed: What|Removed |Added CC||mariano.mo...@protonmail.co ||m --- Comment #24 from Mariano --- This needs to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427010] Inconsistent context menu for Folder View containment
https://bugs.kde.org/show_bug.cgi?id=427010 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- I can't reproduce with Plasma 5.20.3 on Arch Linux. KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429363] New: Connections change while typing password
https://bugs.kde.org/show_bug.cgi?id=429363 Bug ID: 429363 Summary: Connections change while typing password Product: systemsettings Version: 5.20.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_networkmanagement Assignee: jgrul...@redhat.com Reporter: axel.br...@gmx.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 133468 --> https://bugs.kde.org/attachment.cgi?id=133468=edit Trying to enter a password at a certain network, and networks juggle around I want to connect to a new wireless network, in this case Bause-31. While typing the password the order of networks changes, but the input box does not change its position. So I continue typing the pw on a completely different network! While the order of networks continues changing, the situation as shown in the screenshot appears Expected result: password box remains at selected network while typing May be related to https://bugs.kde.org/show_bug.cgi?id=420887 Operating System: openSUSE Tumbleweed 2020 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429262] Import Python Plugins doesn't import all action files
https://bugs.kde.org/show_bug.cgi?id=429262 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/596 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 427859] Unable to build Syntax Highlighting Engine on windows 10 32 bit
https://bugs.kde.org/show_bug.cgi?id=427859 --- Comment #7 from Prajith --- hi Christoph, I was able to build for x64 bit and it is working fine. Please close the ticket. Very much thanks for responding. Regards, Prajith On Tue, Nov 10, 2020 at 5:02 AM Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=427859 > > --- Comment #6 from Christoph Feck --- > Please provide the output of the cmake, make, and compile steps. The > screenshot > you added only shows that the build failed. Also, please add text instead > of > images. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 390476] Muon rebuilds search index very often and inefficient
https://bugs.kde.org/show_bug.cgi?id=390476 mgol...@mitchgolden.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||mgol...@mitchgolden.com Status|REOPENED|NEEDSINFO --- Comment #4 from mgol...@mitchgolden.com --- Are people still seeing this? I do not observe this behavior on Kubuntu 20.10 with muon 5.8.0. Could it have been a packaging issue just on Neon? -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 400041] [wayland] Crashes when opening font files with kfontview
https://bugs.kde.org/show_bug.cgi?id=400041 Andrey changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429362] Please make qtwebengine dependency optional
https://bugs.kde.org/show_bug.cgi?id=429362 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.2.0 Component|general |Geolocation Resolution|--- |WORKSFORME CC||caulier.gil...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- You want mean QtWebKit, not QtWebEngine. The last one is the official web render supported by Qt team. It's a Qt wrapper for Chromium engine. QtWebKit is an old one, no more supported by Qt team. This is optional to switch from QtWebEngine to QtWebkit and vis versa, through a Cmake option: https://invent.kde.org/graphics/digikam/-/blob/master/core/CMakeLists.txt#L36 Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 428175] Discover process keeps on running even after the window is closed
https://bugs.kde.org/show_bug.cgi?id=428175 Nate Graham changed: What|Removed |Added URL||https://github.com/fwupd/fw ||upd/issues/2600 Status|REOPENED|RESOLVED Resolution|--- |UPSTREAM --- Comment #9 from Nate Graham --- So that got reverted, but the upstream issue was fixed, in the end! See https://github.com/fwupd/fwupd/issues/2600 FWIW I still think your change makes sense at least for the master branch. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 361286] muon authentication window close too quickly
https://bugs.kde.org/show_bug.cgi?id=361286 mgol...@mitchgolden.com changed: What|Removed |Added Resolution|--- |WORKSFORME CC||mgol...@mitchgolden.com Status|REPORTED|RESOLVED --- Comment #2 from mgol...@mitchgolden.com --- I am also unable to reproduce this. (I am on 5.8.0) If this is a problem on someone's machine, it seems likely to me that the issue is somewhere outside of muon anyway. Feel free to reopen this if you are still having the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427055] Desktop Grid with Present Windows Effect: display icons and/or window titles
https://bugs.kde.org/show_bug.cgi?id=427055 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 Andrey changed: What|Removed |Added CC||cont...@scrumplex.net --- Comment #23 from Andrey --- *** Bug 400041 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 400041] [wayland] Crashes when opening font files with kfontview
https://bugs.kde.org/show_bug.cgi?id=400041 Andrey changed: What|Removed |Added Assignee|unassigned-b...@kde.org |butir...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||butir...@gmail.com --- Comment #5 from Andrey --- I suppose it's Wayland specific? *** This bug has been marked as a duplicate of bug 401031 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 427311] Kolourpaint crashes when opening "More effects" window
https://bugs.kde.org/show_bug.cgi?id=427311 Nate Graham changed: What|Removed |Added Version Fixed In||5.21 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 427311] Kolourpaint crashes when opening "More effects" window
https://bugs.kde.org/show_bug.cgi?id=427311 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/breeze/commit/3be21543a7 ||5e747862f3a2a5f876d23e9f66f ||13a --- Comment #5 from Nate Graham --- Git commit 3be21543a75e747862f3a2a5f876d23e9f66f13a by Nate Graham, on behalf of David Edmundson. Committed on 19/11/2020 at 18:54. Pushed by ngraham into branch 'master'. Move dialog margin settings to polish event Paint events MUST not change the state of things. This is especially important within style code that is used in many apps that we do not control. Doing it in polish is better. It's still not ideal to adjust geometry in the style, but at least this is where we have a similar hook for QDockWidget so hopefully we know this pattern is acceptable. M +11 -3kstyle/breezestyle.cpp https://invent.kde.org/plasma/breeze/commit/3be21543a75e747862f3a2a5f876d23e9f66f13a -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 427078] No energy information on a desktop pc
https://bugs.kde.org/show_bug.cgi?id=427078 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429346] Rotating and cropping: Concentration of the cropping frame on the real image area.
https://bugs.kde.org/show_bug.cgi?id=429346 --- Comment #2 from Ferry <06f13.41...@mailbox.org> --- Thanks Maik, the rotation tool is much more powerful than I expected. My problem is now solved. Am 2020-11-19 um 19:27 schrieb Maik Qualmann: > https://bugs.kde.org/show_bug.cgi?id=429346 > > Maik Qualmann changed: > > What|Removed |Added > > CC||metzping...@gmail.com > > --- Comment #1 from Maik Qualmann --- > The tool to crop the aspect ratio does not consider pixel content, this is not > an bug. The rotation tool can automatically cut to the largest area. Then with > the aspect ratio tool crop to the maximum area - done. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429362] New: Please make qtwebengine dependency optional
https://bugs.kde.org/show_bug.cgi?id=429362 Bug ID: 429362 Summary: Please make qtwebengine dependency optional Product: digikam Version: 7.1.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- QtWebEngine often has critical security vulnerabilities and slow to fix them. Can Digikam do without (perhaps absent some features)? -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 403526] Can't change repository to https - security bug
https://bugs.kde.org/show_bug.cgi?id=403526 mgol...@mitchgolden.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||mgol...@mitchgolden.com --- Comment #1 from mgol...@mitchgolden.com --- I am running muon in Kubuntu 10.20, but I don't have the protocol (http) dropdown you are describing. This is odd, because the muon version is the same as the one you say you are using. $ muon --version muon 5.8.0 Can you please check to see if this is the version you actually have? Also - sources.list is sort of deprecated. You should be looking in sources.list.d -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427102] Shrinking Dolphin window after error causes places panel to become thinner
https://bugs.kde.org/show_bug.cgi?id=427102 Patrick Silva changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- I can reproduce with Dolphin 20.12 beta on Arch Linux. Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429361] New: Window state / session not remembered after reboot
https://bugs.kde.org/show_bug.cgi?id=429361 Bug ID: 429361 Summary: Window state / session not remembered after reboot Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manuelcha...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 1) Arrange applications in a layout 2) Expect that the layout will be there on next login 3) Do a REBOOT 4) Session / layout appears to not be remembered 5) Restores some previous layout *) To save / remember the layout it's currently required to LOGOUT. #) It should remember / save it on reboot too. Note: I reboot using 'sudo reboot' I'm on Plasma 5.17.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429346] Rotating and cropping: Concentration of the cropping frame on the real image area.
https://bugs.kde.org/show_bug.cgi?id=429346 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The tool to crop the aspect ratio does not consider pixel content, this is not an bug. The rotation tool can automatically cut to the largest area. Then with the aspect ratio tool crop to the maximum area - done. Maik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429276] folders is called F
https://bugs.kde.org/show_bug.cgi?id=429276 --- Comment #10 from Luigi Toscano --- Just for future reference: I've tested a few themes (Qt 5.15.1, qt5-style-plugin 5.0.0+git, Plasma 5.19.5) and I've found out that: The & is visible with MS Windows 9x, Fusion, cde and motif . It does work as expected on Breeze, Oxygen, QtCurve, plastique, gtk, cleanlooks, adwaita. I'm not sure whether MS Windows 9x is part of Qt or not, in that case the bug should be probably RESOLVED UPSTREAM, but the main point is that it's not on KDE side. Fusion being broken is a bit worrying, as it's shipped with Qt. Just for reference, if you are looking for a classing Windows look, you may try some modern themes (in terms of development) like https://github.com/grassmunk/Chicago95 (I haven't tested it) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416232] Stop using lighter text for columns in details view
https://bugs.kde.org/show_bug.cgi?id=416232 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Nate Graham --- Code-wise, this is trivially done by removing the line "painter->setPen(m_additionalInfoTextColor);" in kstandarditemlistwidget.cpp, which causes it to fall back to the default text color. However this has the effect of causing additional information text in icon view to also be drawn using the default font color rather than a lightened version of it. I haven't yet found a way to only make this change for the columns in list view. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429335] digikam 7.2.0-beta2 (18.11.2020) crashes after assigning name to unknown face
https://bugs.kde.org/show_bug.cgi?id=429335 --- Comment #4 from Maik Qualmann --- Git commit 7b74bbd030dfb7292461aa8ac3d80a59d4e2fb9b by Maik Qualmann. Committed on 19/11/2020 at 17:57. Pushed by mqualmann into branch 'master'. fix memory leak M +5-0core/utilities/facemanagement/workers/trainerworker.cpp https://invent.kde.org/graphics/digikam/commit/7b74bbd030dfb7292461aa8ac3d80a59d4e2fb9b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429335] digikam 7.2.0-beta2 (18.11.2020) crashes after assigning name to unknown face
https://bugs.kde.org/show_bug.cgi?id=429335 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.2.0 Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/22e497a ||d75f6808df2707472ecae72da60 ||e24710 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Maik Qualmann --- Git commit 22e497ad75f6808df2707472ecae72da60e24710 by Maik Qualmann. Committed on 19/11/2020 at 17:46. Pushed by mqualmann into branch 'master'. fix crash in the TrainerWorker FIXED-IN: 7.2.0 M +2-1NEWS M +4-3core/utilities/facemanagement/workers/trainerworker.cpp https://invent.kde.org/graphics/digikam/commit/22e497ad75f6808df2707472ecae72da60e24710 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428085] "Often Used/Recent file" list doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=428085 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kactivities-stats/co ||mmit/6faad8ed5f76510de06707 ||836d6406e7177086a3 --- Comment #7 from Ivan Čukić --- Git commit 6faad8ed5f76510de06707836d6406e7177086a3 by Ivan Čukić. Committed on 19/11/2020 at 17:39. Pushed by ivan into branch 'ivan/event-filtering-for-files-and-directories'. Add event filtering for files and directories The df52b1a3 revision introduced Type::files and Type::directories special resource type values for queries, but it omitted to support the same special values in the ResultWatcher. M +10 -1src/resultwatcher.cpp https://invent.kde.org/frameworks/kactivities-stats/commit/6faad8ed5f76510de06707836d6406e7177086a3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427744] Default application used to open file can change when a new app is installed
https://bugs.kde.org/show_bug.cgi?id=427744 --- Comment #9 from xtf --- Would ordered by date instead of alphanum solve the problem or appending newcomers to the explicit list? Other example: have not needed mkvbuilder before, .mkv files was assoc to vlc, installed mkvbuilder, .mkv was bound to mkvbuilder. This has just one assoc, a program with multiple capabilities would overthrow the last default program, if it is higher in alphanum. Don't be to attached to the provided examples. Every distro has this problem. Or is this even a FreeDesktop.org problem? -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 429360] Mouse pointer disappear
https://bugs.kde.org/show_bug.cgi?id=429360 --- Comment #1 from anthomas --- I have tried to change mouse pointer theme, but the problem still persist. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 429360] New: Mouse pointer disappear
https://bugs.kde.org/show_bug.cgi?id=429360 Bug ID: 429360 Summary: Mouse pointer disappear Product: Planet KDE Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: c...@walagran.com Reporter: antho...@fastwebnet.it Target Milestone: --- SUMMARY When there are too much windows opened the mouse pointer disappear. And is impossible to recovery without reboot. STEPS TO REPRODUCE 1. Happen switching from a windows to another. Is impossible to reproduce with precise steps, but happen frequently after some minutes of work. SOFTWARE/OS VERSIONS Linux/KDE Plasma: kubuntu 20.10 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.14.2 Qt Version: 5.14.2 I'm using kubuntu 20.10, but the problem is present in kubuntu 20.04 too. My system is a iMac late 2010, i3 cpu 540@ 3.07 GHz. GPU: AMD RV730. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416631] Multibyte characters inconvenience
https://bugs.kde.org/show_bug.cgi?id=416631 Martin changed: What|Removed |Added CC||spleefe...@gmail.com --- Comment #1 from Martin --- Created attachment 133466 --> https://bugs.kde.org/attachment.cgi?id=133466=edit konsole 20.08.3 Seems working for me with konsole 20.08.3 and Plasma 5.20.3, unless I am misunderstanding your issue -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 427232] Add openweathermap.org
https://bugs.kde.org/show_bug.cgi?id=427232 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 428430] Please add TheTVDB.com as a data source
https://bugs.kde.org/show_bug.cgi?id=428430 --- Comment #1 from Robby Stephenson --- TheTVDB is a subscription model, $12 a year or free to users who add content. I'll check into it. I was also alerted to TVMaze which may be another alternative -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429359] New: Scroll to switch Virtual Desktop not working (Kubuntu 20.10)
https://bugs.kde.org/show_bug.cgi?id=429359 Bug ID: 429359 Summary: Scroll to switch Virtual Desktop not working (Kubuntu 20.10) Product: plasmashell Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: kiwim...@runbox.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Configure Desktop > Mouse actions > Vertical scroll > Switch Desktop The mouse action does not work. Vertical scroll seems to not respond at all. I've tried setting other actions (e.g. switch window, open standard menu, etc) to Vertical scroll to try triggering it, without success. I've set the change desktop action to other mouse buttons (left), where it did open the virtual desktop "drop-down" list. It seems to me that Vertical Scroll is not registered as it was previously. This is on Kubuntu 20.10. Prior to doing a reinstall, I was running 20.04, where it worked "as it always have". To check if I was loosing my marbles, I verified this on my desktop, which is still running 20.04: scrolling worked as should. I also had my friend check his setups. He observed the same as me: PC running 20.04 had vertical scroll = change virtual desktop working as it should; however on the PC with a 20.10 install it didn't work. STEPS TO REPRODUCE 1. Install Kubuntu 20.10 (or likely the KDE/Plasma release shipped in it?) 2. Try to change virtual desktop via scrolling. 3. Observe *nothing* ;) OBSERVED RESULT - Scrolling to change virtual desktop not working as it should. EXPECTED RESULT - Scrolling with mouse wheel on desktop should change the virtual desktop. - This has been default behavious for as long as I can remember. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-29-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4870HQ CPU @ 2.50GHz Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon R9 ™ M370X ADDITIONAL INFORMATION - I have not done a deep dive in setting, to see if there's some new toggle somewhere that prevents this from working. I'm assuming a new toggle isn't the case, since the scrolling is still a Default > On setting when doing a fresh install. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427846] Kickoff - Two "Applications" Headers in History
https://bugs.kde.org/show_bug.cgi?id=427846 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427846] Kickoff - Two "Applications" Headers in History
https://bugs.kde.org/show_bug.cgi?id=427846 Nate Graham changed: What|Removed |Added Keywords|triaged | Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429088] "History" tab is broken after I uninstall a recently launched app
https://bugs.kde.org/show_bug.cgi?id=429088 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 427846 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427846] Kickoff - Two "Applications" Headers in History
https://bugs.kde.org/show_bug.cgi?id=427846 --- Comment #6 from Nate Graham --- *** Bug 429088 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 429331] smart properties and test results should be visible and notify the user
https://bugs.kde.org/show_bug.cgi?id=429331 --- Comment #4 from Luiz Angelo De Luca --- (In reply to Harald Sitter from comment #3) > KDE is a community. I'm sure we'll not report anything ;) > Plasma will, but unfortunately the userbase of Plasma is mch too varied > to report that kind of data. I'm still from the times where kde was a thing, not a community... Old habits die hard. > The problem with reporting the lines you mention is that 99% of people won't > know what they mean or what to do about them which is why we break the > entire affair down to a binary state of either everything is grand or > everything is not. Which has the disadvantage that potentially failing disks > slip under the radar if the overall status says ok even when it isn't. HDD dying process is a little more subtle than "run, I'm gonna explode!". A read error with a msg like "it might be a one time error like a power outage. However, if this error keeps reoccurring, it indicates that part of your data in your HDD is not readable anymore". This is something a user might understand. It could show previous tests or error messages to let the user decide if a new HDD is needed. > At the same time replicating what smartd already does and tracking report > trends to discern problems seems a bit useless given, well, smartd already > does just that ^^ It generates the error log. However, that error will never reach a gui-only user. That's what I'm suggesting: exposing "Hey, a read error happened!" to gui users. If smarttools guys does not have a good heuristic, it is not plasma-disk that will implement one. But plasma-disk could expose and "translate" some errors and let the user decide. > We could maybe have a tiny hint icon somewhere in kinfocenter that there > were problems in the report data so the user can look at it and/or choose to > err on the side of caution and replace the disk. If all last self-tests finished with an error, it should be something to report with a big red flashing icon. Not something subtle inside kinfocenter. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 411900] Tracking activity
https://bugs.kde.org/show_bug.cgi?id=411900 --- Comment #2 from Ivan Čukić --- This is something that kinda existed in Plasma 4.x (for Plasma Active) when kactivitymanagerd followed a 'let's add everything into it' kind of an application. KAMD grew too much to be maintainable, so the scope is now more focussed. I agree that this would be a great thing to have in Plasma, but not as a part of KAMD. A separate time tracking application / plasma applet / system tray applet that integrates with activities* would be quite easy to implement. If anyone is game, I could mentor the project. At least the activities integration part. * Plasma Vault was also in a sense a part of KAMD in Plasma Active days, and now it is a separate applet that integrates with activities. And, IMO, much better than what we had back then. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427744] Default application used to open file can change when a new app is installed
https://bugs.kde.org/show_bug.cgi?id=427744 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 428738] Scanning of image fails with Invalid argument
https://bugs.kde.org/show_bug.cgi?id=428738 --- Comment #1 from Mgns --- While performing some more testing, it seems that the error message only appears when I use scan resolutions above 300 DPI. For 300 DPI and below, the program is able to correctly obtain the image and let me save it to the disk. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 407316] [RFE] recentdocuments:/ ioslave does not work in open dialog using XDG portal in Firefox
https://bugs.kde.org/show_bug.cgi?id=407316 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #6 from Nate Graham --- I can't test anymore as my XDG portal dialog on openSUSE Tumbleweed has temporarily broken, but I'll take your word for it! -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 429358] New: Make QtWebEngine dependency optional
https://bugs.kde.org/show_bug.cgi?id=429358 Bug ID: 429358 Summary: Make QtWebEngine dependency optional Product: kdevplatform Version: 5.6.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: shell Assignee: kdevelop-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- KDevelop only uses QtWebEngine for its built-in documentation viewer. Since QtWebEngine often has unfixed security vulnerabilities (about a dozen at this moment), it would be nice to make it optional where practical to do so. I'd prefer to forego the built-in documentation entirely (rather than pull in QtWebEngine), but it's probably also possible to simply use XDG to open the docs in whatever external HTML viewer the user has? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428503] cannot reopen a kcm after go back to intro page
https://bugs.kde.org/show_bug.cgi?id=428503 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 427835 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427835] Clicking a KCM and clicking home button and then clicking back the same KCM is not working
https://bugs.kde.org/show_bug.cgi?id=427835 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Patrick Silva --- *** Bug 428503 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422682] "Show in Activities" item is missing in window menu
https://bugs.kde.org/show_bug.cgi?id=422682 --- Comment #4 from gudv...@gmail.com --- (In reply to robin from comment #3) > Does anyone maybe has a solution or a respective Arch bug regarding this? I > already searched but found nothing. In my case it was fixed after reboot, IIRC. But if yours is not showing consistently then it is probablt arch (or rather manjaro) issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427846] Kickoff - Two "Applications" Headers in History
https://bugs.kde.org/show_bug.cgi?id=427846 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #5 from Patrick Silva --- I can reproduce, see bug 429088 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429357] New: Only the default settings of the pen buttons are recognized
https://bugs.kde.org/show_bug.cgi?id=429357 Bug ID: 429357 Summary: Only the default settings of the pen buttons are recognized Product: krita Version: 4.4.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: todellahyvakalamie...@gmail.com Target Milestone: --- Created attachment 133465 --> https://bugs.kde.org/attachment.cgi?id=133465=edit Picture of the pro pen 3d default settings in the wacom software SUMMARY I'm using a Wacom Intuos Pro M tablet (PHT-660P). I have two pens: the standard pro pen 2, and a pro pen 3d. The pro pen 2 works as expected. The pro pen 3D is acting strange with Krita. The pen has a default button setting, which from top to bottom -> right click, double click, and tumble. In Krita, only when I'm working on the canvas, no matter how I set up these buttons, they only work by the default state, and it's only true for the topmost two buttons. The tumble button can be configured freely, and works. If I move the pen away from the canvas, for example, I bring up the pop-up pallette, the button settings are recognized. This makes this pen only usable with the default settings currently. This happened after updating Krita to 4.4.0.. Upgrading to 4.4.1. did not fix the problem. When presented the problem, I also upgraded my wacom driver, which also did not fix the problem. Made a fresh Krita reinstall, and even tried out the tablet along with a clean krita install on another computer. The end result is the same. STEPS TO REPRODUCE 1. Have Krita 4.4.1. installed, and have the tablet the two pens connected to it. Set the button on the pro pen 3d to different controls from default, which is easy to differentiate from them. 2. Working on the canvas, test out the topmost two buttons. They are right click (pop-up pallette), and double click (pan), in this order. 3. Move the pen away from the canvas, test buttons again. They work as set up in the wacom software. OBSERVED RESULT The topmost two pen buttons do not work apart from their default settings when the canvas is active. EXPECTED RESULT The buttons should behave the same even in the canvas. SOFTWARE/OS VERSIONS Windows: Windows 10 Home Edition x64 version ADDITIONAL INFORMATION - Tried to change the canvas from DX to OpenGL, and even software rendering. Made no difference. - Clean installed the wacom driver, also did not help. - The buttons work everywhere as they set up apart from the canvas. - The pro pen 2 works perfectly, as it should. - The same problem persist if I only attach my pro pen 3d to the tablet, and completely delete the pro pen 2 from the settings. - The wacom tester program shows no errors in the pen. Thank you in advance for trying to help with my problem! -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 429356] New: Please make qtwebengine dependency optional
https://bugs.kde.org/show_bug.cgi?id=429356 Bug ID: 429356 Summary: Please make qtwebengine dependency optional Product: skrooge Version: 2.23.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: luke-jr+kdeb...@utopios.org CC: steph...@mankowski.fr Target Milestone: --- QtWebEngine often has critical security vulnerabilities and slow to fix them. Can Skrooge do without (perhaps absent some features)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427851] GIMP internal screenshot tool broken by 5.20 release
https://bugs.kde.org/show_bug.cgi?id=427851 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424283] Change Battery to Brightness icon in tray notification area
https://bugs.kde.org/show_bug.cgi?id=424283 Nowshed H. Imran changed: What|Removed |Added CC||now.im@gmail.com --- Comment #5 from Nowshed H. Imran --- I would like to propose a solution. It is ok not separating the icons. However, as soon as the AC power is connected, the battery icon gets hidden in status and notification menu. So, if I need to change the brightness, I can't do it with a single tap. Solution: Battery icon is always visible in taskbar. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427924] GNU Octave Directory Browser Hangs
https://bugs.kde.org/show_bug.cgi?id=427924 Patrick Silva changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Patrick Silva --- Thank you Ian. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 429197] Pinch to zoom is broken. It moves the pdf away from the point where I'm zooming.
https://bugs.kde.org/show_bug.cgi?id=429197 --- Comment #7 from Nate Graham --- It does indeed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 --- Comment #22 from Patrick Silva --- kfontview crash was already reported, see bug 400041 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 --- Comment #21 from Andrey --- When I try to open .ttf font, it opens in a separate app named something like Font View which instantly closes, probably because of the same crash. Could someone confirm and point me if that has already been also reported? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 428125] local file installation broken because of only-trusted
https://bugs.kde.org/show_bug.cgi?id=428125 Patrick Silva changed: What|Removed |Added CC||felixbra...@gmail.com --- Comment #10 from Patrick Silva --- *** Bug 427898 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 427898] cannot install from unsinged repo [critical]
https://bugs.kde.org/show_bug.cgi?id=427898 Patrick Silva changed: What|Removed |Added Resolution|UPSTREAM|DUPLICATE CC||bugsefor...@gmx.com --- Comment #3 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 428125 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429292] Dolphin in FTP mode should auto replace remote files after editing
https://bugs.kde.org/show_bug.cgi?id=429292 --- Comment #8 from Nate Graham --- Woohoo! Magic indeed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429355] New: Black window in system settings
https://bugs.kde.org/show_bug.cgi?id=429355 Bug ID: 429355 Summary: Black window in system settings Product: systemsettings Version: 5.20.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: luca.erra...@gmail.com Target Milestone: --- Created attachment 133464 --> https://bugs.kde.org/attachment.cgi?id=133464=edit Users settings window SUMMARY Since the last update whenever I click on my user profile photo, I get redirected to the corresponding page in system settings, but a black page is shown instead (see attachment) STEPS TO REPRODUCE In my case 1. Open application launcher 2. Click on profile photo (as per modify user info) 3. Get redirected to Users system settings OBSERVED RESULT A black page is shown in the Users panel EXPECTED RESULT A page containing settings for Users management is shown SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.4.0-54-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-7500 CPU @ 3.40GHz Memory: 23.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429292] Dolphin in FTP mode should auto replace remote files after editing
https://bugs.kde.org/show_bug.cgi?id=429292 --- Comment #7 from Ozim --- (In reply to Nate Graham from comment #6) > Oh right, unstable has it already but user edition does not. :/ > > I guess you'll need to wait, or manually find and install the package, yeah. It's a kind of magic! Found repo here https://launchpad.net/~panfaust/+archive/ubuntu/kio-fuse installed package - and got it working!! Thanx a lot! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396064] Restore defaults button resets to the previous saved setting and not the actual default settings
https://bugs.kde.org/show_bug.cgi?id=396064 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- Note for a developer: see that there is also an option to reset configuration from Settings -> Reset Krita Configurations . I think it would be good to just rename this one as "Restore Previous"? (Reset Krita Configurations does something that might not be visible from the dialog, because it also resets the workspace etc.). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429292] Dolphin in FTP mode should auto replace remote files after editing
https://bugs.kde.org/show_bug.cgi?id=429292 --- Comment #6 from Nate Graham --- Oh right, unstable has it already but user edition does not. :/ I guess you'll need to wait, or manually find and install the package, yeah. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427924] GNU Octave Directory Browser Hangs
https://bugs.kde.org/show_bug.cgi?id=427924 --- Comment #5 from Ian Proudler --- Sorry about that I thought I had uploaded it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427924] GNU Octave Directory Browser Hangs
https://bugs.kde.org/show_bug.cgi?id=427924 --- Comment #4 from Ian Proudler --- Created attachment 133463 --> https://bugs.kde.org/attachment.cgi?id=133463=edit Screenshot of browser window -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 427404] PPC ISA 3.1 support is missing, part 6
https://bugs.kde.org/show_bug.cgi?id=427404 --- Comment #23 from Carl Love --- Next set of patches is in bugzilla 429352. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 427404] PPC ISA 3.1 support is missing, part 6
https://bugs.kde.org/show_bug.cgi?id=427404 --- Comment #22 from Carl Love --- Committed patch to fux the xscvhpdp assembly code issue. commit 025bdca23b2fca0dd68b6077426500237aee85c5 (origin/master, origin/HEAD) Author: Carl Love Date: Thu Nov 12 15:18:23 2020 -0600 PowerPC, fix for conv_f16_to_double xscvhpdp assembler code The previous commit: commit eb82a294573d15c1be663673d55b559a82ca29d3 Author: Julian Seward Date: Tue Nov 10 21:10:48 2020 +0100 Add a missing ifdef, whose absence caused build breakage on non-POWER targets. fixed the compile issue in conv_f16_to_double() where non-Power platforms do not support the power xscvhpdp assembly instructions. The instruction is supported by ISA 3.0 platforms. Older Power platforms still fail to compile with the assembly instruction. This patch fixes the if def for power systems that do not support ISA 3.0. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 429352] PPC ISA 3.1 support is missing, part 7
https://bugs.kde.org/show_bug.cgi?id=429352 --- Comment #3 from Carl Love --- Part 8 patches are in bugzilla 429354 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 429354] PPC ISA 3.1 support is missing, part 8
https://bugs.kde.org/show_bug.cgi?id=429354 --- Comment #1 from Carl Love --- Created attachment 133462 --> https://bugs.kde.org/attachment.cgi?id=133462=edit Test cases for VSX Mask Manipulation operations Add test case patch -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429292] Dolphin in FTP mode should auto replace remote files after editing
https://bugs.kde.org/show_bug.cgi?id=429292 --- Comment #5 from Ozim --- (In reply to Nate Graham from comment #4) > Aha! > > This bug is already fixed if you install kio-fuse, which exists to handle > exactly this case. I believe it is packaged in Neon. > > *** This bug has been marked as a duplicate of bug 75324 *** no, it's not the part of KDE Neonm is there a way to get at least deb package? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 429354] New: PPC ISA 3.1 support is missing, part 8
https://bugs.kde.org/show_bug.cgi?id=429354 Bug ID: 429354 Summary: PPC ISA 3.1 support is missing, part 8 Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- Created attachment 133461 --> https://bugs.kde.org/attachment.cgi?id=133461=edit Functional support for ISA 3.1, VSX Mask manipulation operations Patches for ISA 3.1 Power PC, part 8 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 429352] PPC ISA 3.1 support is missing, part 7
https://bugs.kde.org/show_bug.cgi?id=429352 --- Comment #2 from Carl Love --- This is the 7th bugzilla for the ISA 3.1 Power PC support. The bugzilla for part 6 is 427404. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429353] Lockscreen doesn't resize to full screen after rotation of screen
https://bugs.kde.org/show_bug.cgi?id=429353 --- Comment #1 from Bhushan Shah --- Created attachment 133460 --> https://bugs.kde.org/attachment.cgi?id=133460=edit broken lockscreen -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 429352] PPC ISA 3.1 support is missing, part 7
https://bugs.kde.org/show_bug.cgi?id=429352 --- Comment #1 from Carl Love --- Created attachment 133459 --> https://bugs.kde.org/attachment.cgi?id=133459=edit Test cases for new IOps The test cases -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429353] New: Lockscreen doesn't resize to full screen after rotation of screen
https://bugs.kde.org/show_bug.cgi?id=429353 Bug ID: 429353 Summary: Lockscreen doesn't resize to full screen after rotation of screen Product: kwin Version: git master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY This seems to happen on the phone, where rotating phone lockscreen doesn't properly resize. STEPS TO REPRODUCE 1. Start PlaMo session 2. Lock 3. Rotate phone OBSERVED RESULT You got broken UI EXPECTED RESULT Lockscreen resizes in any orientation -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 429352] New: PPC ISA 3.1 support is missing, part 7
https://bugs.kde.org/show_bug.cgi?id=429352 Bug ID: 429352 Summary: PPC ISA 3.1 support is missing, part 7 Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- Created attachment 133458 --> https://bugs.kde.org/attachment.cgi?id=133458=edit Functional support for ISA 3.1, New Iops Power PC missing ISA 3.1 support. Additional patches, part 7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406697] Cut & Paste layers is possible inside locked group
https://bugs.kde.org/show_bug.cgi?id=406697 --- Comment #14 from Tymond --- Git commit d25e08a3c6298f98850e1f22284f30536425eec1 by Agata Cacko. Committed on 19/11/2020 at 15:49. Pushed by tymond into branch 'krita/4.3'. Fix assert on New Layer From Visible on invisible active layer Before this commit, Krita would assert on New Layer from Visible when used on invisible layer. This commit fixes this. Explanation: Buckle up, it's going to be a ride :) In 2016 there was a problem that invisible layers would show up when they were merged, see bug 359707. https://bugs.kde.org/show_bug.cgi?id=359707 As a solution, "just remove the layers separately instead of merging" strategy was used. In 2018 it turned out that in case when putAfter (the layer Krita puts the merged result above of) is invisible, it gets removed, so then it's null and Krita tries to merge other layers in instead of putAfter, see bug 395903. https://bugs.kde.org/show_bug.cgi?id=395903 As a solution, if putAfter was invisible, one of the visible nodes-to-be-merged were assigned to putAfter to replace the original putAfter node, to make sure that when original putAfter is removed, some other layer is doing its job. (The fact that it's a soon-to-be-merged layer is not a problem). In 2020 it turned out that there is quite a lot of actions that are possible in locked groups. It required some more changes to the code. See bug 406697. https://bugs.kde.org/show_bug.cgi?id=406697 A solution included a change to the relevant code such that invisible putAfter would be unconditionally replaced with one of the nodes from the to-be-merged list, and then if putAfter had no parent, Krita would encounter an assert. Problem with this behaviour: In case of newLayerFromVisible(), mergedNodes list would only contain a root node (which has no parent). If the putAfter is invisible, then it's replaced with "one of" mergedNodes, which means the root node. Which means it's going to assert. However it's not always necessary to replace putAfter with one of the to-be-merged nodes. It's only needed when it's going to be removed. Hence moving the replacing into the if. Because root is not invisible, the list of invisible nodes will be empty and nothing will be replaced and nothing will be removed. NOTE: I also added a new condition: '&& cleanupNodes'. It's not stricly necessary to cover all usecases of mergeMultipleNodesImpl, because the only usecase where cleanupNodes is false is the newLayerFromVisible case (which will fail the first condition). However it makes it more future-proof since the only case those nodes needs to be removed is when cleanupNodes is true (otherwise removing nodes would be a dataloss bug). NOTE2: It's possible that putAfter replacement needs one more check (to see if it is in fact in the invisibleNodes list). I couldn't find a situation where it was needed, though, so I left it as it is. Related: bug 428683, bug 359707, bug 395903 (cherry picked from commit c1ab1ee97f196e73d8340918e2d9b7a79eafbbca) M +15 -8libs/image/kis_layer_utils.cpp https://invent.kde.org/graphics/krita/commit/d25e08a3c6298f98850e1f22284f30536425eec1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428683] New Layer From Visible not working properly in 4.4.0 onwards
https://bugs.kde.org/show_bug.cgi?id=428683 Tymond changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/c1ab1ee97 |hics/krita/commit/d25e08a3c |f196e73d8340918e2d9b7a79eaf |6298f98850e1f22284f30536425 |bbca|eec1 --- Comment #2 from Tymond --- Git commit d25e08a3c6298f98850e1f22284f30536425eec1 by Agata Cacko. Committed on 19/11/2020 at 15:49. Pushed by tymond into branch 'krita/4.3'. Fix assert on New Layer From Visible on invisible active layer Before this commit, Krita would assert on New Layer from Visible when used on invisible layer. This commit fixes this. Explanation: Buckle up, it's going to be a ride :) In 2016 there was a problem that invisible layers would show up when they were merged, see bug 359707. https://bugs.kde.org/show_bug.cgi?id=359707 As a solution, "just remove the layers separately instead of merging" strategy was used. In 2018 it turned out that in case when putAfter (the layer Krita puts the merged result above of) is invisible, it gets removed, so then it's null and Krita tries to merge other layers in instead of putAfter, see bug 395903. https://bugs.kde.org/show_bug.cgi?id=395903 As a solution, if putAfter was invisible, one of the visible nodes-to-be-merged were assigned to putAfter to replace the original putAfter node, to make sure that when original putAfter is removed, some other layer is doing its job. (The fact that it's a soon-to-be-merged layer is not a problem). In 2020 it turned out that there is quite a lot of actions that are possible in locked groups. It required some more changes to the code. See bug 406697. https://bugs.kde.org/show_bug.cgi?id=406697 A solution included a change to the relevant code such that invisible putAfter would be unconditionally replaced with one of the nodes from the to-be-merged list, and then if putAfter had no parent, Krita would encounter an assert. Problem with this behaviour: In case of newLayerFromVisible(), mergedNodes list would only contain a root node (which has no parent). If the putAfter is invisible, then it's replaced with "one of" mergedNodes, which means the root node. Which means it's going to assert. However it's not always necessary to replace putAfter with one of the to-be-merged nodes. It's only needed when it's going to be removed. Hence moving the replacing into the if. Because root is not invisible, the list of invisible nodes will be empty and nothing will be replaced and nothing will be removed. NOTE: I also added a new condition: '&& cleanupNodes'. It's not stricly necessary to cover all usecases of mergeMultipleNodesImpl, because the only usecase where cleanupNodes is false is the newLayerFromVisible case (which will fail the first condition). However it makes it more future-proof since the only case those nodes needs to be removed is when cleanupNodes is true (otherwise removing nodes would be a dataloss bug). NOTE2: It's possible that putAfter replacement needs one more check (to see if it is in fact in the invisibleNodes list). I couldn't find a situation where it was needed, though, so I left it as it is. Related: bug 359707, bug 395903, bug 406697 (cherry picked from commit c1ab1ee97f196e73d8340918e2d9b7a79eafbbca) M +15 -8libs/image/kis_layer_utils.cpp https://invent.kde.org/graphics/krita/commit/d25e08a3c6298f98850e1f22284f30536425eec1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395903] Krita merges layers it shouldn't
https://bugs.kde.org/show_bug.cgi?id=395903 --- Comment #5 from Tymond --- Git commit d25e08a3c6298f98850e1f22284f30536425eec1 by Agata Cacko. Committed on 19/11/2020 at 15:49. Pushed by tymond into branch 'krita/4.3'. Fix assert on New Layer From Visible on invisible active layer Before this commit, Krita would assert on New Layer from Visible when used on invisible layer. This commit fixes this. Explanation: Buckle up, it's going to be a ride :) In 2016 there was a problem that invisible layers would show up when they were merged, see bug 359707. https://bugs.kde.org/show_bug.cgi?id=359707 As a solution, "just remove the layers separately instead of merging" strategy was used. In 2018 it turned out that in case when putAfter (the layer Krita puts the merged result above of) is invisible, it gets removed, so then it's null and Krita tries to merge other layers in instead of putAfter, see bug 395903. https://bugs.kde.org/show_bug.cgi?id=395903 As a solution, if putAfter was invisible, one of the visible nodes-to-be-merged were assigned to putAfter to replace the original putAfter node, to make sure that when original putAfter is removed, some other layer is doing its job. (The fact that it's a soon-to-be-merged layer is not a problem). In 2020 it turned out that there is quite a lot of actions that are possible in locked groups. It required some more changes to the code. See bug 406697. https://bugs.kde.org/show_bug.cgi?id=406697 A solution included a change to the relevant code such that invisible putAfter would be unconditionally replaced with one of the nodes from the to-be-merged list, and then if putAfter had no parent, Krita would encounter an assert. Problem with this behaviour: In case of newLayerFromVisible(), mergedNodes list would only contain a root node (which has no parent). If the putAfter is invisible, then it's replaced with "one of" mergedNodes, which means the root node. Which means it's going to assert. However it's not always necessary to replace putAfter with one of the to-be-merged nodes. It's only needed when it's going to be removed. Hence moving the replacing into the if. Because root is not invisible, the list of invisible nodes will be empty and nothing will be replaced and nothing will be removed. NOTE: I also added a new condition: '&& cleanupNodes'. It's not stricly necessary to cover all usecases of mergeMultipleNodesImpl, because the only usecase where cleanupNodes is false is the newLayerFromVisible case (which will fail the first condition). However it makes it more future-proof since the only case those nodes needs to be removed is when cleanupNodes is true (otherwise removing nodes would be a dataloss bug). NOTE2: It's possible that putAfter replacement needs one more check (to see if it is in fact in the invisibleNodes list). I couldn't find a situation where it was needed, though, so I left it as it is. Related: bug 428683, bug 359707, bug 406697 (cherry picked from commit c1ab1ee97f196e73d8340918e2d9b7a79eafbbca) M +15 -8libs/image/kis_layer_utils.cpp https://invent.kde.org/graphics/krita/commit/d25e08a3c6298f98850e1f22284f30536425eec1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359707] Merging invisible layers unhides them
https://bugs.kde.org/show_bug.cgi?id=359707 --- Comment #5 from Tymond --- Git commit d25e08a3c6298f98850e1f22284f30536425eec1 by Agata Cacko. Committed on 19/11/2020 at 15:49. Pushed by tymond into branch 'krita/4.3'. Fix assert on New Layer From Visible on invisible active layer Before this commit, Krita would assert on New Layer from Visible when used on invisible layer. This commit fixes this. Explanation: Buckle up, it's going to be a ride :) In 2016 there was a problem that invisible layers would show up when they were merged, see bug 359707. https://bugs.kde.org/show_bug.cgi?id=359707 As a solution, "just remove the layers separately instead of merging" strategy was used. In 2018 it turned out that in case when putAfter (the layer Krita puts the merged result above of) is invisible, it gets removed, so then it's null and Krita tries to merge other layers in instead of putAfter, see bug 395903. https://bugs.kde.org/show_bug.cgi?id=395903 As a solution, if putAfter was invisible, one of the visible nodes-to-be-merged were assigned to putAfter to replace the original putAfter node, to make sure that when original putAfter is removed, some other layer is doing its job. (The fact that it's a soon-to-be-merged layer is not a problem). In 2020 it turned out that there is quite a lot of actions that are possible in locked groups. It required some more changes to the code. See bug 406697. https://bugs.kde.org/show_bug.cgi?id=406697 A solution included a change to the relevant code such that invisible putAfter would be unconditionally replaced with one of the nodes from the to-be-merged list, and then if putAfter had no parent, Krita would encounter an assert. Problem with this behaviour: In case of newLayerFromVisible(), mergedNodes list would only contain a root node (which has no parent). If the putAfter is invisible, then it's replaced with "one of" mergedNodes, which means the root node. Which means it's going to assert. However it's not always necessary to replace putAfter with one of the to-be-merged nodes. It's only needed when it's going to be removed. Hence moving the replacing into the if. Because root is not invisible, the list of invisible nodes will be empty and nothing will be replaced and nothing will be removed. NOTE: I also added a new condition: '&& cleanupNodes'. It's not stricly necessary to cover all usecases of mergeMultipleNodesImpl, because the only usecase where cleanupNodes is false is the newLayerFromVisible case (which will fail the first condition). However it makes it more future-proof since the only case those nodes needs to be removed is when cleanupNodes is true (otherwise removing nodes would be a dataloss bug). NOTE2: It's possible that putAfter replacement needs one more check (to see if it is in fact in the invisibleNodes list). I couldn't find a situation where it was needed, though, so I left it as it is. Related: bug 428683, bug 395903, bug 406697 (cherry picked from commit c1ab1ee97f196e73d8340918e2d9b7a79eafbbca) M +15 -8libs/image/kis_layer_utils.cpp https://invent.kde.org/graphics/krita/commit/d25e08a3c6298f98850e1f22284f30536425eec1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417983] Nothing happens when "Use" button of GHNS window is clicked
https://bugs.kde.org/show_bug.cgi?id=417983 --- Comment #4 from Alexander Lohnau --- Git commit 858dec4c07561e6c834686c3ff14ed624238cdcc by Alexander Lohnau. Committed on 19/11/2020 at 15:46. Pushed by alex into branch 'master'. Rework adoption API This reworks the existing adoption API which adds warnings/error messages to it. In order for the KCMs to react to the adoption event the `signalEntryEvent` signal was added. Also this fixes the buttons in the UI being clickable. M +1-1src/core/CMakeLists.txt M +115 -62 src/core/engine.cpp M +34 -0src/core/engine.h M +6-0src/core/entryinternal.h M +3-2src/core/errorcode.h M +1-1src/qtquick/qml/Page.qml M +1-1 src/qtquick/qml/private/entrygriddelegates/BigPreviewDelegate.qml M +1-1src/qtquick/qml/private/entrygriddelegates/ThumbDelegate.qml M +1-1src/qtquick/qml/private/entrygriddelegates/TileDelegate.qml M +1-4src/qtquick/quickitemsmodel.cpp M +2-4src/ui/itemsviewdelegate.cpp https://invent.kde.org/frameworks/knewstuff/commit/858dec4c07561e6c834686c3ff14ed624238cdcc -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429351] New: Copy and paste in editor is losing kerning property
https://bugs.kde.org/show_bug.cgi?id=429351 Bug ID: 429351 Summary: Copy and paste in editor is losing kerning property Product: krita Version: nightly build (please specify the git hash!) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: lucidsunli...@yandex.ru Target Milestone: --- SUMMARY Kerning property is not carried over, the copy will have kerning enabled regardless of previous setting and GUI toggle will show it disabled. STEPS TO REPRODUCE 1. Pick a font with kerning support (e.g. Noto Sans) 1. Create a "Placeholder Text" object 2. Disable kerning (via GUI toggle, or by saving the text and reopening the editor if on 4.4.1) 3. Select and copy "Placeholder Text" 4. Paste it on new line 5. Compare "Text" between two lines OBSERVED RESULT Pasted text have kerning enabled. EXPECTED RESULT Pasted text have kerning disabled. SOFTWARE/OS VERSIONS Linux: 5.9.8-arch1-1 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION Can be reproduced on 4.4.1, but requires some extra steps due to invalid kerning property handling and lack of GUI toggle, git hashes which fixes that and add the toggle: - on master: f837e086a5a4fbcff48b15e044e1684912fa2524 - on krita/4.3: 885641566f182ce316b068bb6d4b015cb0c2a55c GUI toggle not being active is caused by `QTextCharFormat::fontKerning()` in `SvgTextEditor::checkFormat()` reporting `false`, despite copy having kerning enabled. The copy seems to be using HTML under the hood, and `QTextDocument::toHtml()` doesn't convert kerning. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427924] GNU Octave Directory Browser Hangs
https://bugs.kde.org/show_bug.cgi?id=427924 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Patrick Silva --- Still no screenshot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427169] Brush freezes, disappears when opening color palette, gets stuck in "pan" mode
https://bugs.kde.org/show_bug.cgi?id=427169 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Component|Usability |tablet support -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427934] Virtual keyboard wrong position on login and lock screens
https://bugs.kde.org/show_bug.cgi?id=427934 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427939] On very short screens, Apply, Help, Defaults etc buttons on many pages become inaccessible
https://bugs.kde.org/show_bug.cgi?id=427939 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426777] Users KCM Avatars list no longer lists custom entries in /usr/share/user-manager/avatars
https://bugs.kde.org/show_bug.cgi?id=426777 Nate Graham changed: What|Removed |Added Summary|(5.20) Users KCM Avatars|Users KCM Avatars list no |list no longer lists custom |longer lists custom entries |entries in |in |/usr/share/user-manager/ava |/usr/share/user-manager/ava |tars|tars -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425036] Change done in Users kcm is applied despite the password dialog being canceled
https://bugs.kde.org/show_bug.cgi?id=425036 Nate Graham changed: What|Removed |Added Summary|Change done in Users kcm is |Change done in Users kcm is |applied despite the |applied despite the |password dialog is canceled |password dialog being ||canceled -- You are receiving this mail because: You are watching all bug changes.
