[okular] [Bug 359932] Okular is very slow at opening some EPUB's
https://bugs.kde.org/show_bug.cgi?id=359932 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #22 from Norbert Preining --- I can confirm the same behavior on Debian/unstable with Plasma 5.22.2, Okular 21.04.2, all native (no flatpak or other systems). I tried other viewers (mupdf, calibre ebook, atril) all of which worked without hiccup and much faster. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359932] Okular is very slow at opening some EPUB's
https://bugs.kde.org/show_bug.cgi?id=359932 tidux changed: What|Removed |Added Platform|Archlinux Packages |Flatpak Version|0.24.0 |21.04.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359932] Okular is very slow at opening some EPUB's
https://bugs.kde.org/show_bug.cgi?id=359932 tidux changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||j...@dorsal.tk --- Comment #21 from tidux --- I am running Fedora Kinoite Rawhide amd64 (immutable-base distribution) currently on Plasma 5.22. I have installed Okular 21.04.2 from Flatpak. My system is a Ryzen 2500U with 16GB RAM and /home on btrfs on a SATA 6Gbps SSD. Under default performance settings, Okular uses 100% of a single CPU core for approximately five seconds while opening the file, and then another four seconds per individual page turn. This is the single worst performance I have ever seen of any epub renderer on any system. I attempted to trade memory usage for performance by disabling "Enable transparency effects" and setting "Memory usage" to "Greedy" in the Performance tab of the "Configure Okular" menu. The file took over ten seconds to open, a process which was still pegging a single CPU core. Page load time was decreased by 25% to three seconds, and pages that had already been rendered once opened near instantly. This suggests a pair of bugs: 1. The parser takes far too long to load an epub file or a portion of it into memory. 2. The renderer is extremely slow, and should probably be replaced with QtWebKit or QtWebEngine. The entire point of basing EPUB on HTML is that performant generation/parsing/rendering libraries are universal on every system capable of making a modern TLS connection to obtain such files. We should use one. To reproduce, simply open the following public domain EPUB file in Okular: https://gutenberg.org/ebooks/10 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438886] Godot MIME icon doesn't appear to be working
https://bugs.kde.org/show_bug.cgi?id=438886 Michael Alexsander changed: What|Removed |Added CC||michaelalexsander@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 437475] Update cannot be seen
https://bugs.kde.org/show_bug.cgi?id=437475 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437522] Spactacle Crash
https://bugs.kde.org/show_bug.cgi?id=437522 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438196] Random Crashing
https://bugs.kde.org/show_bug.cgi?id=438196 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438437] Latte Dock crashing
https://bugs.kde.org/show_bug.cgi?id=438437 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438427] Crash while adding a widget.
https://bugs.kde.org/show_bug.cgi?id=438427 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] Latte Dock Crashes at Login
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 438104] dolphin - Segmentation fault randomly when open
https://bugs.kde.org/show_bug.cgi?id=438104 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438360] Plasma panel appears completely transparent with many translucent themes since 5.22 update.
https://bugs.kde.org/show_bug.cgi?id=438360 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 437903] Latte Dock crashed unexpected
https://bugs.kde.org/show_bug.cgi?id=437903 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439106] Low pointer polling rates cause inconsistent frame 'timings' in functions tied to pointer movement.
https://bugs.kde.org/show_bug.cgi?id=439106 --- Comment #2 from Ralek Kolemios --- Created attachment 139652 --> https://bugs.kde.org/attachment.cgi?id=139652=edit Proposed fix Text taken from https://krita-artists.org/t/what-makes-kritas-canvas-operations-feel-so-wrong/25377/20?u=ralek My concept for how to fix this. Of course I don't understand the inner working of QT or Krita, I'm just an artist, so this is going off of theoretical data and my desire to help. In the background, asynchronously, a pointer pseudoposition function is constantly receiving inputs from the actual pointer. It keeps the last 2 (or more if you’re a math major) of these positions and timings in-memory for later reference. At any point in time that an action requires an ‘up to date’ and ‘consistent’ but not necessarily extremely accurate pointer position, such as for panning, zooming, rotating, etc, instead of grabbing the current pointer position, it calls the pointerPseudoposition function. This function grabs the current microtime, and extrapolates a ‘current’ pointer position given the previous 2 mouse positions and microtime. I’d imagine the math would look something like: x1 = last known x position x2 = last x position before x1 y1 = last known y position y2 = last y position before y1 time1 = time int in microseconds of last known pointer input time2 = time int in microseconds of previously known pointer input before time1 currentTime = the microseconds of when the function is called newX = x1 + ( (currentTime - time1) / (time1 - time2) * (x1 - x2)) newY = y1 + ( (currentTime - time1) / (time1 - time2) * (y1 - y2)) This will output an X and Y position of the ‘mouse’ which should slot into whatever function the current pan/rotate/zoom function uses when it calls for the mouse position. This will cause slightly weird behavior if the pointer changes directions instantaneously, but for natural movements such as tablet pens, this could be a lifesaver. Perhaps it could be a toggle-able feature called ‘polling rate compensation’. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439138] New: Some Flatpak applications are not showing in application launcher
https://bugs.kde.org/show_bug.cgi?id=439138 Bug ID: 439138 Summary: Some Flatpak applications are not showing in application launcher Product: plasmashell Version: 5.22.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: kfsbgd4o4...@opayq.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Some of my installed Flatpak applications are not showing in the KDE launcher, but they are showing in the GNOME launcher. The applications are Photos (org.gnome.Photos) and Extensions (org.gnome.Extensions). Other Flatpak applications like GNOME gedit, Firefox, Telegram and VLC can show in the KDE launcher properly. STEPS TO REPRODUCE 1. Install Photos or Extensions from flatpak 2. They are not showing in KDE launcher 3. After reboot they are still not showing OBSERVED RESULT Applications are not showing in KDE launcher EXPECTED RESULT Applications are showing in KDE launcher SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Uninstalling and reinstalling the applications does not resolve the problem. Rebooting does not resolve the problem. echo $XDG_DATA_DIRS gives: /home/van/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share Affected desktop files: /var/lib/flatpak/exports/share/applications/org.gnome.Extensions.desktop [Desktop Entry] Type=Application Name[be]=Пашырэнні Name[bn_IN]=এক্সটেনশনগুলি Name[ca]=Extensions Name[cs]=Rozšíření Name[da]=Udvidelser Name[de]=Erweiterungen Name[el]=Επεκτάσεις Name[en_GB]=Extensions Name[eo]=Etendaĵoj Name[es]=Extensiones Name[eu]=Hedapenak Name[fa]=افزونهها Name[fi]=Laajennukset Name[fr]=Extensions Name[fur]=Estensions Name[gl]=Extensións Name[he]=הרחבות Name[hr]=Proširenja Name[hu]=Kiterjesztések Name[id]=Ekstensi Name[it]=Estensioni Name[ja]=拡張機能 Name[kab]=Isiɣzaf Name[kk]=Кеңейтулер Name[ko]=확장 Name[lt]=Plėtiniai Name[lv]=Paplašinājumi Name[mjw]=Extensions Name[nb]=Utvidelser Name[nl]=Uitbreidingen Name[os]=Уӕлӕмхасӕнтӕ Name[pa]=ਇਕਸਟੈਨਸ਼ਨ Name[pl]=Rozszerzenia Name[pt]=Extensões Name[pt_BR]=Extensões Name[ro]=Extensii Name[ru]=Расширения Name[sk]=Rozšírenia Name[sl]=Razširitve lupine Name[sr]=Проширења Name[sv]=Tillägg Name[tr]=Uzantılar Name[uk]=Розширення Name[zh_CN]=扩展 Name[zh_TW]=擴充套件 Name=Extensions Icon=org.gnome.Extensions Comment[af]=Stel GNOME Shell-uitbreidings op Comment[an]=Configurar as extensions de GNOME Shell Comment[ar]=اضبط امتدادات صدفة جنوم Comment[as]=GNOME শ্বেল সম্প্ৰসাৰনসমূহ সংৰূপণ কৰক Comment[be]=Наладзіць пашырэнні абалонкі GNOME Comment[bg]=Настройки на разширенията на обвивката Comment[bn_IN]=GNOME সেল এক্সটেনশন কনফিগার করুন Comment[bs]=Podesi GNOME Shell proširenja Comment[ca]=Configureu les extensions del GNOME Shell Comment[ca@valencia]=Configureu les extensions del GNOME Shell Comment[ckb]=ڕێکخستنی زیادکراوەکانی گنۆم شێڵ Comment[cs]=Nastavit rozšíření pro GNOME Shell Comment[da]=Konfigurér GNOME Shell-udvidelser Comment[de]=GNOME-Shell-Erweiterungen einrichten Comment[el]=Ρύθμιση επεκτάσεων του GNOME Shell Comment[en_GB]=Configure GNOME Shell Extensions Comment[eo]=Agordi GNOME-ŝelajn kromprogramojn Comment[es]=Configurar las extensiones de GNOME Shell Comment[et]=GNOME Shelli laienduste seadistamine Comment[eu]=Konfiguratu GNOME Shell-eko gehigarriak Comment[fa]=پیکربندی افزونههای پوستهٔ گنوم Comment[fi]=Hallitse Gnome Shell -laajennuksia Comment[fr]=Configurer les extensions Shell de GNOME Comment[fur]=Configure lis estensions di GNOME Shell Comment[ga]=Cumraigh Eisínteachtaí GNOME Shell Comment[gd]=Rèitich leudachain Slige GNOME Comment[gl]=Configure as extensións de GNOME Shell Comment[gu]=GNOME Shell ઍક્સટેન્શનને રૂપરેખાંકિત કરો Comment[he]=הגדרת הרחבות GNOME Shell Comment[hi]=गनोम शेल एक्सटेंशन विन्यस्त करें Comment[hr]=Podesi proširenja GNOME ljuske Comment[hu]=GNOME Shell kiterjesztések beállítása Comment[ia]=Configurar le extensiones GNOME Shell Comment[id]=Konfigurasi Ekstensi GNOME Shell Comment[is]=Stilla GNOME Shell Extension skeljarviðbætur Comment[it]=Configura le estensioni di GNOME Shell Comment[ja]=GNOME Shell 拡張機能の設定を行います Comment[kk]=GNOME Shell кеңейтулерін баптау Comment[km]=កំណត់រចនាសម្ព័ន្ធផ្នែកបន្ថែមរបស់ GNOME សែល Comment[kn]=GNOME ಶೆಲ್ ಎಕ್ಸಟೆನ್ಶನ್ಸ್ ಅನ್ನು ಸಂರಚಿಸಿ Comment[ko]=그놈 셸 확장을 설정합니다 Comment[ky]=GNOME Shell кеңейтмелерин ырастоо Comment[lt]=Konfigūruoti GNOME Shell plėtinius Comment[lv]=Konfigurēt GNOME Shell paplašinājumus Comment[ml]=ഗ്നോം ഷെല് എക്സ്റ്റെന്ഷനുകള് ക്രമീകരിയ്ക്കുക Comment[mr]=GNOME शेल एक्सटेंशन्स् संरचीत करा Comment[ms]=Konfigur Sambungan-Sambungan Shell GNOME Comment[nb]=Sett opp
[plasma-systemmonitor] [Bug 439123] Shift+Delete for sending SIGKILL does not work
https://bugs.kde.org/show_bug.cgi?id=439123 Felipe Kinoshita changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-systemmonitor/com ||mit/b7d26345f8a43c9297bc466 ||01d4f5f1fdf80a9dc Resolution|--- |FIXED --- Comment #3 from Felipe Kinoshita --- Git commit b7d26345f8a43c9297bc46601d4f5f1fdf80a9dc by Felipe Kinoshita. Committed on 25/06/2021 at 03:59. Pushed by fhek into branch 'master'. Kill process when pressing Shift+Delete This commit makes possible to kill a process when pressing Shift+Delete on the applications/process table. M +3-0src/faces/applicationstable/contents/ui/FullRepresentation.qml M +3-0src/faces/processtable/contents/ui/FullRepresentation.qml https://invent.kde.org/plasma/plasma-systemmonitor/commit/b7d26345f8a43c9297bc46601d4f5f1fdf80a9dc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #18 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/947 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439137] New: GTK4 child windows/dialogs positioned incorrectly on KWin X11
https://bugs.kde.org/show_bug.cgi?id=439137 Bug ID: 439137 Summary: GTK4 child windows/dialogs positioned incorrectly on KWin X11 Product: kwin Version: 5.22.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: nyanpas...@tuta.io Target Milestone: --- Not sure if this is a GTK4 bug or a WM bug. For more information, see my GTK4 bug report at https://gitlab.gnome.org/GNOME/gtk/-/issues/4070. SUMMARY When GTK4 applications spawn child windows or dialogs, they randomly appear at the top-left corner of the screen instead of on top of their parent. STEPS TO REPRODUCE 0. Install KDE Plasma on X11, and GTK4. 1. Launch KDE Plasma X11. 2. Run gtk4-demo. Scroll down to "Dialogs" and press "Run" in the title bar. 3. Push "Message Dialog" or "Interactive Dialog". OBSERVED RESULT On KDE Plasma X11, with gtk4-demo, the "Dialogs" window has a 45%-ish chance of appearing at the top-left corner of the screen, a 45%-ish chance of appearing where there's empty room on the desktop, and a 10%-ish chance of appearing on top of the parent window. The "Message Dialog" (with title bar) and "Interactive Dialog" it creates have a 50%-ish chance of appearing at the top left corner of the screen, instead of on the window. If you `killall kwin_x11` before opening the windows/dialogs, they will always appear in the top-left of the screen. If you follow the same steps with gtk3-demo, the "Dialogs and Message Boxes" window always appears where there is room on-screen (otherwise on the top-left corner), and the Message/Interactive Dialogs always appear on top of their parent windows. With kwin_x11 killed, all windows and dialogs appear in the top-left corner of the screen. EXPECTED RESULT I expect GTK4 windows to not be positioned nondeterministically on KWin (which could be a KWin bug, or something more complex), and not be placed in the top-left corner of the screen. Ideally GTK4 windows would behave like GTK3 windows. Does GTK4 think it's the responsibility of the GUI toolkit or WM to position windows? I'm guessing both GTK3 and GTK4 do not communicate window positions to X, but instead supplies instructions to the WM, and GTK4 does so differently, and they're either wrong or misinterpreted by non-GNOME WMs. (I've heard on the gtk-rs Matrix that GTK4 doesn't compute window positions itself, and I observed that gtk3-demos's "Dialogs and Message Boxes" window is placed on the parent in XFCE, but in empty space on KDE.) And there are even bigger behavioral differences on GTK4. I didn't take the time to test gtk3/4-demo's behavior on GNOME or any DE's Wayland, but I did test gtk3/4-widget-factory's behavior. (See https://gitlab.gnome.org/GNOME/gtk/-/issues/4070#additional-information.) Window positioning is much more consistent on Wayland. I suspect that's because the WM, not the toolkit, manages window positioning, so GTK4 has no room to screw positions up. But I don't know why GTK on X11 has inconsistent windowing behavior, since I think it delegates positioning to the WM like Wayland does. (I think so because it spawns windows at (0, 0) without a WM running.) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.12-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2 GTK: 4.2.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #17 from Felipe Kinoshita --- If you want any help you can call me at @fhek789:kde.org on matrix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439136] version 4.4.5 is damaged and won't open on MacOS
https://bugs.kde.org/show_bug.cgi?id=439136 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #1 from vanyossi --- If this happens after you open the DMG file it is a problem on macOS 10.13: High Sierra is very old and the verification process fails on it. We no longer have a High Sierra system to identify what changed when we moved our build process to the an M1 mac, but since then High Sierra validation fails. You can delete the online validation by removing the "com.apple.quarantine" flag from krita.app after installing it. This will allow krita to open on your system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #16 from Sebastian E. --- (In reply to Felipe Kinoshita from comment #15) > Sure, also why you don't make this change, seems like you have been studying > this code a lot recently, just create a merge request and I can take a loot > at it. I've already read parts of the "Get involved" guide, and successfully installed kdesrc-build and built/run Dolphin. But I still need to figure out more stuff, like setting up CLion, code style, git-pulling the latest changes, properly run it on my existing system, testing, Gitlab account, how to make a merge request, etc... If I've had enough time, I would have done it myself. But yeah, I'll probably contribute in the future. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438767] Animation curves - Value not taken in account immediately
https://bugs.kde.org/show_bug.cgi?id=438767 Emmet O'Neill changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/ba8c627c1 ||45397e815cd8aa15d9d928aa78a ||3474 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Emmet O'Neill --- Git commit ba8c627c145397e815cd8aa15d9d928aa78a3474 by Emmet O'Neill. Committed on 25/06/2021 at 01:56. Pushed by emmetoneill into branch 'master'. Transform mask now properly updates when active keyframe's value changes. M +4-2libs/image/kis_node.cpp https://invent.kde.org/graphics/krita/commit/ba8c627c145397e815cd8aa15d9d928aa78a3474 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #15 from Felipe Kinoshita --- Sure, also why you don't make this change, seems like you have been studying this code a lot recently, just create a merge request and I can take a loot at it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439106] Low pointer polling rates cause inconsistent frame 'timings' in functions tied to pointer movement.
https://bugs.kde.org/show_bug.cgi?id=439106 Ralek Kolemios changed: What|Removed |Added CC||i...@ralek.art --- Comment #1 from Ralek Kolemios --- Created attachment 139651 --> https://bugs.kde.org/attachment.cgi?id=139651=edit polling rate comparison A graphic describing why I believe this issue happens. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439136] New: version 4.4.5 is damaged and won't open on MacOS
https://bugs.kde.org/show_bug.cgi?id=439136 Bug ID: 439136 Summary: version 4.4.5 is damaged and won't open on MacOS Product: krita Version: 4.4.5 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: monica.fo...@gmail.com Target Milestone: --- SUMMARY Using Mac OSX 10.13.6. I downloaded the Krita .dmg, followed the installation steps, and when I tried to open the program for the first time, there was a loading bar that said it was "verifying" the program. Then I get the error " "Krita" is damaged and can't be opened. You should move it to the Trash." I deleted and re-downloaded the .dmg a few times and this happened every time. STEPS TO REPRODUCE 1. Download Mac version of Krita 4.4.5 2. Run installer 3. Open app OBSERVED RESULT App won't open and can't be used EXPECTED RESULT App would open and could be used SOFTWARE/OS VERSIONS Windows: macOS: 10.13.6 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277
--- Comment #14 from Sebastian E. ---
@Felipe Kinoshita
Could you please revert or fix your commit that broke it?
https://invent.kde.org/plasma/plasma-workspace/-/commit/6befb657dd9fd811160e0369913d769cfff7f02d
Your commit reintroduced a change that has been reverted before:
https://invent.kde.org/plasma/plasma-workspace/-/commit/885c4abe7b5343caa7407c4b441b2cfcd78828c3
Fixing that warning along with the change did not really help, it just crashes
differently.
Alternatively replace
if (screen == nullptr) {
return;
}
with
if (screen == nullptr) screen = QGuiApplication::screens()[0]
Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 439135] color management completely non-functional under Wayland, works under X
https://bugs.kde.org/show_bug.cgi?id=439135 --- Comment #1 from amspacey --- Also, this is kind of a nit that I didn't want to make a whole separate bug report for, but would you consider adding a manual override for the manufacturer name of my monitor? You're relying on the PNP ID list, which on my distro is provided by the hwids package. For some insane inscrutable reason, the name of the company that made my monitor is literally "DO NOT USE - AUO" according to the UEFI PNP ID registry: https://uefi.org/PNP_ID_List?search=AUO I realize it's kind of ugly, but a two line fix, something like if (pnpid == "AUO") return "AU Optronics"; would fix this issue for me a probably a lot of users. It's ugly to see "DO NOT USE - AUO" as the name of the screen in colord-kde. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439135] New: color management completely non-functional under Wayland, works under X
https://bugs.kde.org/show_bug.cgi?id=439135 Bug ID: 439135 Summary: color management completely non-functional under Wayland, works under X Product: kwin Version: 5.22.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: jogir...@zetmail.com Target Milestone: --- SUMMARY A discussion with a KDE contributor on Reddit revealed that color management is apparently supposed to be working as of 5.22 under the KWin Wayland compositor. It mostly works for me in Gnome, but doesn't work at all in KDE. STEPS TO REPRODUCE 1. Start a Wayland session (startplasma-wayland) 2. Observe whether color corrections previously applied under X are applied 3. Open settings and go to color corrections 4. Try to apply the ICC profile for the screen 5. Try to use colormgr to manually import / apply an ICC profile OBSERVED RESULT No color corrections can be applied under KWin. None of the profiles shown under X show up under Wayland, probably because the device ID is different. Trying to import any profile (including profiles that were *not* installed under X) gives the error "color profile is already installed". Trying to import a profile with colormgr hangs for a few seconds and then returns "the profile was not added in time". I *can* apply certain test profiles built into colord to the screen, oddly enough. E.g. there's a profile called Bluish.icc that changes the white point of the screen to make it much bluer, for testing purposes. I can apply this profile with colord-kde and it does in fact make my screen much bluer. I was able to delete this profile with colormgr, and after doing that I can't import it again (I get the errors described above). So it's possible this issue is just with *importing* profiles. Under Gnome, the monitor is correctly detected (although once again without any profiles because of a differing device ID) and I can import and apply my profiles, which works as expected. The calibration curves are correctly loaded in the VCGT under Gnome. Some applications that were previously color managed under KWin + X are *not* correctly color managed under Gnome. Although the white balance has been corrected due to the system-wide colord settings, sRGB images are much too saturated. These applications include Firefox and eog (eye of gnome). Most applications that allow manually setting a profile (versus relying on the application communicating with colord) work correctly, e.g. GIMP. EXPECTED RESULT Color management should work as expected. colord-kde should correctly detect my screen and allow me to apply profiles, and colord should load the calibration curves into the VCGT when I do so. Also, because the Wayland protocol for communicating color management information between applications and the compositor is not yet finalized or merged (https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14), applications running on a color managed KDE + Wayland system are expected to do their own color management at this time. Firefox (running under xwayland for me) should be able to request the active color profile from colord, and send correctly mapped colors for my screen to the compositor. Same with eog and so on. SOFTWARE/OS VERSIONS Linux: Arch Linux / kernel 5.12.12 / x86_64 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Graphics: Mesa DRI Intel HD Graphics 3000 Please let me know if there's more information I can provide. I'm able to test stuff and provide additional debugging information as needed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439122] Make the size of the taskbar thumbnail proportional to the size of the source window
https://bugs.kde.org/show_bug.cgi?id=439122 Felipe Kinoshita changed: What|Removed |Added CC||kinof...@gmail.com --- Comment #1 from Felipe Kinoshita --- That would be quite nice IMO. Off course we would need a max size so the thumbnails don't grow infinitely. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439133] Report bug menu dissapears on hover
https://bugs.kde.org/show_bug.cgi?id=439133 Felipe Kinoshita changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||kinof...@gmail.com --- Comment #1 from Felipe Kinoshita --- That's not the case on more recent versions, the "Report bug..." action in on the about page now. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 439111] [Feature Request] Add option to disable auto playback of the last open file
https://bugs.kde.org/show_bug.cgi?id=439111 Felipe Kinoshita changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||kinof...@gmail.com --- Comment #1 from Felipe Kinoshita --- *** This bug has been marked as a duplicate of bug 436887 *** -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 436887] Add a setting to disable opening of last viewed video on startup
https://bugs.kde.org/show_bug.cgi?id=436887 Felipe Kinoshita changed: What|Removed |Added CC||dron1...@gmail.com --- Comment #1 from Felipe Kinoshita --- *** Bug 439111 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439123] Shift+Delete for sending SIGKILL does not work
https://bugs.kde.org/show_bug.cgi?id=439123 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-systemmonitor/-/merge_requests/149 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u
https://bugs.kde.org/show_bug.cgi?id=439132 magnus.gros...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u
https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #1 from magnus.gros...@gmail.com --- Sorry my bad, this is a bug from the Telegram side. They forgot to put the MimeType line into the local desktop file (but did not forget to put it into the systemwide desktop file). I will close this now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439134] New: Texture bound too early
https://bugs.kde.org/show_bug.cgi?id=439134 Bug ID: 439134 Summary: Texture bound too early Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: aleix...@kde.org Target Milestone: --- Opening a bug so not to forget. #0 0x7f1044ec2d22 in raise () at /usr/lib/libc.so.6 #1 0x7f1044eac90e in abort () at /usr/lib/libc.so.6 #2 0x7f10457ecbb1 in qt_message_fatal (message=..., context=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #3 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffdfcda19b8, msg=msg@entry=0x7f1045aed000 "ASSERT: \"%s\" in file %s, line %d") at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:893 #4 0x7f10457ebfe2 in qt_assert(char const*, char const*, int) (assertion=, file=, line=) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qglobal.cpp:3358 #5 0x7f10486868c4 in KWin::GLTexture::bind() (this=0x559d17f6fab0) at /home/apol/devel/frameworks/kwin/src/libkwineffects/kwingltexture.cpp:422 #6 0x7f104868605e in KWin::GLTexture::GLTexture(QImage const&, unsigned int) (this=0x559d17f6fab0, image=..., target=3553) at /home/apol/devel/frameworks/kwin/src/libkwineffects/kwingltexture.cpp:86 #7 0x7f103dc1d9aa in KWin::SceneOpenGL2::paintCursor(QRegion const&)::$_7::operator()() const (this=0x559d18556a30) at /home/apol/devel/frameworks/kwin/src/plugins/scenes/opengl/scene_opengl.cpp:307 #8 0x7f103dc28386 in QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::SceneOpenGL2::paintCursor(QRegion const&)::$_7>::call(KWin::SceneOpenGL2::paintCursor(QRegion const&)::$_7&, void**) (f=..., arg=0x7ffdfcda1e70) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:146 #9 0x7f103dc28351 in QtPrivate::Functor::call, void>(KWin::SceneOpenGL2::paintCursor(QRegion const&)::$_7&, void*, void**) (f=..., arg=0x7ffdfcda1e70) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:256 #10 0x7f103dc282f1 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x559d18556a20, r=0x559d16952a50, a=0x7ffdfcda1e70, ret=0x0) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:443 #11 0x7f1045a42133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffdfcda1e70, r=0x559d16952a50, this=0x559d18556a20) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate(QObject*, int, void**) (sender=0x559d1654ed90, signal_index=3, argv=0x7ffdfcda1e70) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #13 0x7f104899bd70 in KWin::Cursors::currentCursorChanged(KWin::Cursor*) (this=0x559d1654ed90, _t1=0x559d165c2950) at src/kwin_autogen/EWIEGA46WW/moc_cursor.cpp:385 #14 0x7f1048a2e569 in KWin::Cursors::emitCurrentCursorChanged() (this=0x559d1654ed90) at /home/apol/devel/frameworks/kwin/src/cursor.cpp:81 #15 0x7f1048a3a048 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KWin::Cursors::*)()>::call(void (KWin::Cursors::*)(), KWin::Cursors*, void**) (f=(void (KWin::Cursors::*)(KWin::Cursors * const)) 0x7f1048a2e550 , o=0x559d1654ed90, arg=0x7ffdfcda2060) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:152 #16 0x7f1048a39fad in QtPrivate::FunctionPointer::call, void>(void (KWin::Cursors::*)(), KWin::Cursors*, void**) (f=(void (KWin::Cursors::*)(KWin::Cursors * const)) 0x7f1048a2e550 , o=0x559d1654ed90, arg=0x7ffdfcda2060) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:185 #17 0x7f1048a39ef2 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x559d165c1990, r=0x559d1654ed90, a=0x7ffdfcda2060, ret=0x0) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:418 #18 0x7f1045a42133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffdfcda2060, r=0x559d1654ed90, this=0x559d165c1990) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x559d165c2950, signal_index=5, argv=0x7ffdfcda2060) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #20 0x7f104899b845 in KWin::Cursor::cursorChanged() (this=0x559d165c2950) at src/kwin_autogen/EWIEGA46WW/moc_cursor.cpp:217 #21 0x7f1048a2efed in KWin::Cursor::updateCursor(QImage const&, QPoint const&) (this=0x559d165c2950, image=..., hotspot=...) at /home/apol/devel/frameworks/kwin/src/cursor.cpp:180 #22 0x7f1048b68087 in KWin::PointerInputRedirection::init()::$_0::operator()() const (this=0x559d1723e330) at /home/apol/devel/frameworks/kwin/src/pointer_input.cpp:120 #23
[systemsettings] [Bug 439095] This configuration module just doesn't work on my notebook
https://bugs.kde.org/show_bug.cgi?id=439095 Felipe Kinoshita changed: What|Removed |Added CC||kinof...@gmail.com --- Comment #1 from Felipe Kinoshita --- Is it not available or you can turn it on and off but it doesn't take effect? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439083] Discover crashes when changing Release Upgrade setting
https://bugs.kde.org/show_bug.cgi?id=439083 Jose changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439133] Report bug menu dissapears on hover
https://bugs.kde.org/show_bug.cgi?id=439133 Jose changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439133] New: Report bug menu dissapears on hover
https://bugs.kde.org/show_bug.cgi?id=439133 Bug ID: 439133 Summary: Report bug menu dissapears on hover Product: Discover Version: 5.14.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: jluisgar...@mailbox.org CC: aleix...@kde.org Target Milestone: --- Created attachment 139650 --> https://bugs.kde.org/attachment.cgi?id=139650=edit screenshot_with_2_scenarios SUMMARY Report bug menu dissapears on hover STEPS TO REPRODUCE 1. Open Discover tool (Software Center) 2. Click on Settings 3. Try to report a bug by clicking on the 3 dots of the top right corner. 4. Hover on "About Discover" and move down to "Report Bug" OBSERVED RESULT "Report Bug" option dissapears. (See screenshot with 2 scenarios) EXPECTED RESULT "Report Bug" option should not dissapear on hover. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 10.10 (new installation) (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION *** If you follow a different path "Report Bug" option does NOT dissapear. (See screenshot with 2 scenarios) ** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439104] Chrome apps are not opened in an isolated app window but in a chrome session instead
https://bugs.kde.org/show_bug.cgi?id=439104 --- Comment #3 from Felipe Kinoshita --- Created attachment 139649 --> https://bugs.kde.org/attachment.cgi?id=139649=edit youtube shortcut -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439104] Chrome apps are not opened in an isolated app window but in a chrome session instead
https://bugs.kde.org/show_bug.cgi?id=439104 Felipe Kinoshita changed: What|Removed |Added CC||kinof...@gmail.com --- Comment #2 from Felipe Kinoshita --- Cannot reproduce, works fine for me. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436005] Kde neon Not installed on Btrfs
https://bugs.kde.org/show_bug.cgi?id=436005 --- Comment #9 from gr...@kde.org --- Right now there's **no** layout, and installation fails. Merging a specific layout means that that is "the layout" and then installation will succeed, but you're stuck with the subvolumes chosen in that specific layout. Soon, Calamares will have a fallback / default layout that it will use even if there's no layout -- so you'll get "the layout" from Calamares. People get shirty if "the layout" is wrong -- as in, argumentative whether /var/db should be a subvolume or not -- so having any layout at all is bad news for distro's, who are going to take the heat for it. (PRs for a btrfs-layout-designing tool in a Calamares module are welcome) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439132] New: kioexec is used, even if the application enables its own network transparency with %u
https://bugs.kde.org/show_bug.cgi?id=439132
Bug ID: 439132
Summary: kioexec is used, even if the application enables its
own network transparency with %u
Product: frameworks-kio
Version: 5.83.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kio-bugs-n...@kde.org
Reporter: magnus.gros...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. Download telegram-desktop
2. Register telegram-desktop's desktop file, by opening the Settings and
blindly typing the cheat code "registertg" (no input field focused)
3. Close Telegram Desktop
4. Run xdg-open 'tg://resolve?domain=durov'
OBSERVED RESULT
kio-exec terminates with error "unknown protocol tg://"
EXPECTED RESULT
Telegram Desktop starts with https://t.me/durov opened as chat
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
Deleting the local desktop file
~/.local/share/applications/userapp-Telegram-Desktop-HUPUW0.desktop solves the
problem.
HOWEVER, replacing the content of that same file with the content of the
system-wide /usr/share/applications/telegramdesktop.desktop does NOT solve the
problem.
So it must be a bug in the way that KDE parses local desktop files. kioexec
should not be used at all to download the url, it should just pass the argument
to Telegram.
Original issue at the telegram repo:
https://github.com/telegramdesktop/tdesktop/issues/16478
Output of the above xdg-open command:
command= "/usr/bin/telegram-desktop -workdir ~/.local/share/TelegramDesktop/ --
%u" args= ("/usr/bin/telegram-desktop -workdir ~/.local/share/TelegramDesktop/
-- %u", "tg://resolve?domain=durov")
kf.kio.core: Protocol Class of url QUrl("tg://resolve?domain=durov") , isn't
':local', cancelling job.
Copying QUrl("tg://resolve?domain=durov") to
QUrl("file:///~/.cache/kioexec/krun/7009_0/unnamed")
kf.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes
Protokoll „tg“.\n"
If I am not mistaken, the above command and args string seem to have parsed the
parameters incorrectly?
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 439049] Can't configure APT source
https://bugs.kde.org/show_bug.cgi?id=439049 techxga...@outlook.com changed: What|Removed |Added Platform|Other |Neon Packages --- Comment #1 from techxga...@outlook.com --- I forgot to change the platform to specifically Neon. On Kubuntu, I still can. Operating System: Kubuntu 21.04 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-22-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439131] New: Detached brush editor does not respect brush changes done via the Python API
https://bugs.kde.org/show_bug.cgi?id=439131 Bug ID: 439131 Summary: Detached brush editor does not respect brush changes done via the Python API Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- SUMMARY I found this because I have a plugin that sets the brush size, but was able to reproduce with the Scripter plugin. STEPS TO REPRODUCE 1. Open Scripter plugin, paste: win = Krita.instance().activeWindow() view = win.activeView() view.setBrushSize(5) 2. Open brush editor (in detached mode). 3. Run script. OBSERVED RESULT Note that the brush size changes in the toolbar but not the brush editor. Changing anything in the brush editor causes the size to reset to what the brush editor thinks it is. This also happens with opacity (setPaintingOpacity) and I'm guessing anything else that can be set via the API. EXPECTED RESULT Changes are "applied" everywhere. SOFTWARE/OS VERSIONS Windows 10 Krita Nightly 4407898 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111
--- Comment #50 from Alexandr Paliy ---
Sorry for double-posting, I'll add some info.
When I say "icon is missing", ofc I mean that normally it would be shown (for
example, now I have like 70% of battery, and in tray settings it is set to be
always shown - but it is not, and it's also missing from "expanded" tray ("show
hidden icons")).
I've tried to set "Always show all entries" in systray's properties - I can see
everything except for battery :)
I don't know if that's still actual, but:
> David Edmundson 2020-06-29 14:40:55 UTC
> Can I see the output of:
> qdbus org.freedesktop.DBus /org/freedesktop/DBus
> org.freedesktop.DBus.ListNames
Here it is:
https://gist.github.com/alexandrpaliy/06012b961bdb463ec3f488260ddba469
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Alexandr Paliy changed: What|Removed |Added CC||alexandrpa...@gmail.com --- Comment #49 from Alexandr Paliy --- Operating System: Gentoo Linux KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.10.45-gentoo (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Happens to me too, but it's not consistently gone. Sometimes icon is present, sometimes it's not. I did not make any "deep" tests, but it feels like icon is missing after system went to sleep and woke up. After reboot icon [usually] is present again. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1
https://bugs.kde.org/show_bug.cgi?id=381819 Konrad Rzepecki changed: What|Removed |Added CC||hanni...@astral.lodz.pl --- Comment #26 from Konrad Rzepecki --- I'm also hit by this bug. And I can confirm that patch added by Ștefan Talpalaru works for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 438675] Last horizontal disk size indicator is rendered on first entry of Places
https://bugs.kde.org/show_bug.cgi?id=438675 --- Comment #4 from Chris Holland --- The solution is to follow kio's filepicker code properly. I wrote the dolphin code simpler since I thought I'd squirreled out all the edge cases of it being recycled. Seems like I can't do that though. https://invent.kde.org/frameworks/kio/-/blob/master/src/filewidgets/kfileplacesview.cpp#L121 https://invent.kde.org/frameworks/kio/-/blob/master/src/filewidgets/kfileplacesview.cpp#L235 mutable QMap m_freeSpaceInfo; -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 415954] kservice fails to build from source
https://bugs.kde.org/show_bug.cgi?id=415954 Hari changed: What|Removed |Added CC||hariashok2...@gmail.com --- Comment #1 from Hari --- Created attachment 139648 --> https://bugs.kde.org/attachment.cgi?id=139648=edit H -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438444] plasma-framework master fails to compile with cmake v3.20.2
https://bugs.kde.org/show_bug.cgi?id=438444 Andreas Cord-Landwehr changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/plasma-framework/com ||mit/8953e77ec26b90da0e79e3c ||f3ecb727034768d58 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #8 from Andreas Cord-Landwehr --- Git commit 8953e77ec26b90da0e79e3cf3ecb727034768d58 by Andreas Cord-Landwehr. Committed on 24/06/2021 at 20:11. Pushed by cordlandwehr into branch 'master'. Add compatibility code when GLVND is not available CMake's FindOpenGL internally handles EGL only correctly when GLVND is available. This might not the case on embedded systems and actually it is not necessary when EGL::EGL is found. M +14 -1CMakeLists.txt M +3-1src/declarativeimports/core/CMakeLists.txt https://invent.kde.org/frameworks/plasma-framework/commit/8953e77ec26b90da0e79e3cf3ecb727034768d58 -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 366581] messageviewer does not wrap long JSONs with no spaces
https://bugs.kde.org/show_bug.cgi?id=366581 --- Comment #4 from Hari --- Created attachment 139647 --> https://bugs.kde.org/attachment.cgi?id=139647=edit /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 438675] Last horizontal disk size indicator is rendered on first entry of Places
https://bugs.kde.org/show_bug.cgi?id=438675
nttkde changed:
What|Removed |Added
CC||watisthis...@outlook.com
--- Comment #3 from nttkde ---
I took a quick look into this couple of months ago, and as far as I understand
it is indeed related to recycling of the placesitemlistwidget objects (which
happens only when part of the places panel is hidden - the scrollbar is there).
Take this with a grain of salt but hopefully it's at least somewhat
readable/helpful. (Zren has mostly seen this already.)
The capacity bar state (m_freeSpaceInfo & m_drawCapacityBar) is stored inside
placesitemlistwidgets and when the widget gets "recycled" into an other index
it still carries the old data with it. ResetCapacityBar() is not called during
recycling.
Other widget parameters are normally reset from
kitemlistview::updateWidgetProperties()
(or initializeItemListWidget) when recycle/reuse happens in
kitemlistview::doLayout().
(doLayout->createWidget->create->popRecycleableWidget and doLayout()
reusableitems [line 1761])
The setData() call in updateCapacityBar() resets widgets' other data but of
course doesn't affect the m_freeSpaceInfo/m_drawCapacityBar since those are
stored in the widget object.
((IIRC for testing purposes, if you create a method in *itemlistwidget classes
that gets called from updateWidgetProperties(), and overload it in
placesitemlistwidget so that it calls resetCapacityBar(), it should fix the
bug.))
First paint will use the wrong data but the next repaint after
updateCapacityBar makes the bar go away
except...
The more annoying aspect is that I can reproduce it on the disk devices too,
and when it appears on an unmounted device the bar won't go away at all in a
following repaint since then url.isEmpty() in placesitemlistwidget.cpp:60 just
returns without recalculating the bar.
('url' is stored in the "model" data externally, and becomes empty for an
unmounted device. 'udi' above exists for unmounted devices too).
Scrolling may make it go away if a different widget gets recycled on its place.
Thus moving the updateCapacityBar() call to the beginning of paint() won't fix
the bug for the disk device items.
If MVC model is to be followed, the placesitemlistwidget (kind of part of the
"view" here, isn't it?) has some tasks that should maybe be rather divided into
the model or controller.
If m_freeSpaceInfo and m_drawCapacityBar could be read and updated from data()
or something similar (from the model that doesn't get recycled) as eg. the url
is read, that would solve the problems,
but currently there doesn't seem to be a way to access the model directly from
the placesitemlistwidget.
PlacesItemListWidget can only read data() and it's copied from the model to the
widget every time it's recycled/reused in the
updateWidgetProperties()->setData().
--
You are receiving this mail because:
You are watching all bug changes.
[gwenview] [Bug 439130] New: Gwenview crashes on generating thumb previews of tiff files
https://bugs.kde.org/show_bug.cgi?id=439130 Bug ID: 439130 Summary: Gwenview crashes on generating thumb previews of tiff files Product: gwenview Version: 20.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: admfu...@gmail.com Target Milestone: --- Application: gwenview (20.04.2) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.78-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.2 -- Information about the crash: - What I was doing when the application crashed: waiting for thumbnails previews to generate Tiffs are from scanned images made with Xsane. High resolution, typicaly 2400 dpi 16 bit greyscale. 75 to 150 Mb sized files unable to install backtrace code at this time to give more details. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 0x7f4f4ac3e420 in raise () from /lib64/libc.so.6 #5 0x7f4f4ac3fa01 in abort () from /lib64/libc.so.6 #6 0x7f4f4ac81877 in __libc_message () from /lib64/libc.so.6 #7 0x7f4f4ac88093 in malloc_printerr () from /lib64/libc.so.6 #8 0x7f4f4c6a9a0d in QImageData::~QImageData (this=0x5617b1ad5190, __in_chrg=) at image/qimage.cpp:169 #9 0x7f4f4c6a9a77 in QImage::~QImage (this=0x7f4f1c638ad0, __in_chrg=) at image/qimage.cpp:1015 #10 0x7f4f4fadf0da in ?? () from /usr/lib64/libgwenviewlib.so.5 #11 0x7f4f4fadfb66 in ?? () from /usr/lib64/libgwenviewlib.so.5 #12 0x7f4f4b4730b2 in QThreadPrivate::start (arg=0x5617b11599d0) at thread/qthread_unix.cpp:361 #13 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #14 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f4f1ffac700 (LWP 3930) "gwenview:shlo1"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f4f207ad700 (LWP 3929) "gwenview:shlo0"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f4f20fae700 (LWP 3928) "gwenview:sh2"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f4f217af700 (LWP 3927) "gwenview:sh1"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f4f21fb0700 (LWP 3926) "gwenview:sh0"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f4f227b1700 (LWP 3925) "gwenvie:disk$3"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f4f22fb2700 (LWP 3924) "gwenvie:disk$2"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f4f237b3700 (LWP 3923) "gwenvie:disk$1"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f4f23fb4700 (LWP 3922) "gwenvie:disk$0"): #1 0x7f4f2ac4ae9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f4f2ac4aa87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f4f447354f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f4ad00ecf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f4f248fc700 (LWP 3921) "gwenview:cs0"): #1
[kdepim] [Bug 366581] messageviewer does not wrap long JSONs with no spaces
https://bugs.kde.org/show_bug.cgi?id=366581 --- Comment #3 from Hari --- Created attachment 139646 --> https://bugs.kde.org/attachment.cgi?id=139646=edit Life -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437570] KDiff3 3-way merge injects newlines and strips trailing newlines
https://bugs.kde.org/show_bug.cgi?id=437570 --- Comment #10 from michael --- Git commit 4ee5627d28d65e095ce2149f80e6fdc7c6d5047d by Michael Reeves. Committed on 24/06/2021 at 20:07. Pushed by mreeves into branch '1.9'. Fix EOL handling in SourceData::FileData::preprocess This resolves the striping of the trailing EOLs. M +26 -6src/SourceData.cpp M +2-0src/diff.cpp https://invent.kde.org/sdk/kdiff3/commit/4ee5627d28d65e095ce2149f80e6fdc7c6d5047d -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437570] KDiff3 3-way merge injects newlines and strips trailing newlines
https://bugs.kde.org/show_bug.cgi?id=437570 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/commit/cb1801979c87a |kdiff3/commit/17b02147d5e9d |36e2b0d38f8c1d5780b95cf7d60 |14a518dd4c5c9b63ef330e1c539 --- Comment #9 from michael --- Git commit 17b02147d5e9d14a518dd4c5c9b63ef330e1c539 by Michael Reeves, on behalf of Adriaan de Groot. Committed on 24/06/2021 at 20:08. Pushed by mreeves into branch '1.9'. Do not put line feed between removed lines If a line is removed in a merge, then there should be no line feed before it -- that will come from a subsequent **non**-deleted line. This avoids double-newlines when a line is removed. (cherry picked from commit 942325c58a922b0297861ad3c2b1832248b1bf14) FIXED-IN:1.9.3 (cherry picked from commit cb1801979c87a36e2b0d38f8c1d5780b95cf7d60) M +4-1src/mergeresultwindow.cpp https://invent.kde.org/sdk/kdiff3/commit/17b02147d5e9d14a518dd4c5c9b63ef330e1c539 -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 366581] messageviewer does not wrap long JSONs with no spaces
https://bugs.kde.org/show_bug.cgi?id=366581 Hari changed: What|Removed |Added CC||hariashok2...@gmail.com --- Comment #2 from Hari --- Created attachment 139645 --> https://bugs.kde.org/attachment.cgi?id=139645=edit Life -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 388807] Choose icon dialog: distant of widgets is too high when dialog is wide
https://bugs.kde.org/show_bug.cgi?id=388807 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kiconthemes/-/merge_requests/34 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 438536] Using right click on a Desktop icon will show the context menu on the other monitor
https://bugs.kde.org/show_bug.cgi?id=438536 --- Comment #3 from fuo...@gmail.com --- Relevant upstream issue for X11 https://bugreports.qt.io/browse/QTBUG-94778 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437570] KDiff3 3-way merge injects newlines and strips trailing newlines
https://bugs.kde.org/show_bug.cgi?id=437570 --- Comment #8 from michael --- Git commit f8cec3c7b954bc182f80c113c914baee90195b0b by Michael Reeves. Committed on 24/06/2021 at 19:46. Pushed by mreeves into branch 'master'. Fix EOL handling in SourceData::FileData::preprocess This resolves the striping of the trailing EOLs. M +42 -12 src/SourceData.cpp M +2-2src/SourceData.h M +67 -12 src/autotests/DiffTest.cpp M +2-0src/diff.cpp https://invent.kde.org/sdk/kdiff3/commit/f8cec3c7b954bc182f80c113c914baee90195b0b -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437570] KDiff3 3-way merge injects newlines and strips trailing newlines
https://bugs.kde.org/show_bug.cgi?id=437570 michael changed: What|Removed |Added Version Fixed In||1.9.3 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/commit/cb1801979c87a ||36e2b0d38f8c1d5780b95cf7d60 --- Comment #7 from michael --- Git commit cb1801979c87a36e2b0d38f8c1d5780b95cf7d60 by Michael Reeves, on behalf of Adriaan de Groot. Committed on 24/06/2021 at 19:47. Pushed by mreeves into branch 'master'. Do not put line feed between removed lines If a line is removed in a merge, then there should be no line feed before it -- that will come from a subsequent **non**-deleted line. This avoids double-newlines when a line is removed. (cherry picked from commit 942325c58a922b0297861ad3c2b1832248b1bf14) FIXED-IN:1.9.3 M +4-1src/mergeresultwindow.cpp https://invent.kde.org/sdk/kdiff3/commit/cb1801979c87a36e2b0d38f8c1d5780b95cf7d60 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 439129] New: Add the ability to uninstall the emoji selector
https://bugs.kde.org/show_bug.cgi?id=439129 Bug ID: 439129 Summary: Add the ability to uninstall the emoji selector Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: popov...@ukr.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Currently I can easily uninstall the emoji selector on openSUSE Tumbleweed, but I cannot do the same on KDE neon. It would be great to make this app a separate package so that it can be uninstalled. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 User Edition KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 439129] Add the ability to uninstall the emoji selector
https://bugs.kde.org/show_bug.cgi?id=439129 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438871] 3.15:unhandled instruction bytes: 0xF3 0x49 0xF 0x6F 0x9C 0x24 0x60 0x2 0x0 0x0
https://bugs.kde.org/show_bug.cgi?id=438871 Simon Sobisch changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #6 from Simon Sobisch --- (In reply to Tom Hughes from comment #5) > Created attachment 139502 [details] > Patch to ignore REX.W for MOVDQU > > Try this patch and see if it helps... Yes, brought me directly to the next one: vx amd64->IR: unhandled instruction bytes: 0xF3 0x49 0xF 0x7F 0x4B 0xE0 0xF3 0x49 0xF 0x7F vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=1 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=1 Following the lead with the patch I've did the same for the 0x7F case /* F3 0F 7F = MOVDQU -- move from G (xmm) to E (mem or xmm). */ allowing a size of either 4 or 8 - now the application can be run with valgrind. Thank you very much - I hope those two patches are well enough to get into the next release. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439128] Can't name brush after a deleted brush.
https://bugs.kde.org/show_bug.cgi?id=439128 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO Keywords||release_blocker CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Deleted resources are only marked as deleted so they disappear from the user's view. You can still check them out on Resource Manager. There should be a method to delete all "backup files" aka deleted resources and old versions of resources, but there isn't one yet. Assuming we don't want to change the overall design, what do you think should happen in that case? Would it be fine if the resource name was "ResourceName" and the actual file name was "ResourceName (1).kpp" to keep it different from "ResourceName.kpp" which is still there? Or removing/replacing the old resource would be fine? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430049] session memory leak
https://bugs.kde.org/show_bug.cgi?id=430049 Waqar Ahmed changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG CC||waqar@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439128] New: Can't name brush after a deleted brush.
https://bugs.kde.org/show_bug.cgi?id=439128 Bug ID: 439128 Summary: Can't name brush after a deleted brush. Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Create new brush, name it something, for example "1". Save it. 2. Delete it. 3. Try to save a new brush with the same name "1". OBSERVED RESULT Nothing happens, brush does not appear in any lists. In the log docker I see: Resource "paintoppresets" "1.kpp" already exists in ... Could not add resource "1.kpp" to the storage "" Failed to add resource "1" It seems the preset is not really deleted from my resources, only marked as deleted. Deleting it manually does not help because the database still thinks it's deleted. EXPECTED RESULT I can name a brush after a deleted brush. I wouldn't really expect the preset to be kept around in my resources folder either... SOFTWARE/OS VERSIONS Windows 10 Krita Nightly 4407898 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439127] New: Crash when switching to smudge brush engine with rgba tip in lightness map mode
https://bugs.kde.org/show_bug.cgi?id=439127 Bug ID: 439127 Summary: Crash when switching to smudge brush engine with rgba tip in lightness map mode Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- Created attachment 139644 --> https://bugs.kde.org/attachment.cgi?id=139644=edit crash log STEPS TO REPRODUCE 1. Create smudge brush, set tip to an rgba tip, set brush mode to lightness map. 2. Create a new brush in another engine (e.g. pixel) 3. Try to create smudge brush again. SOFTWARE/OS VERSIONS Windows 10 Krita Nightly 4407898 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439126] New: Cursor on desktop and some other Plasma elements differs from the one chosen in settings.
https://bugs.kde.org/show_bug.cgi?id=439126 Bug ID: 439126 Summary: Cursor on desktop and some other Plasma elements differs from the one chosen in settings. Product: plasmashell Version: 5.21.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: alydar...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139643 --> https://bugs.kde.org/attachment.cgi?id=139643=edit Unthemed Cursor on Desktop SUMMARY Cursor on desktop and some other Plasma elements differs from the one chosen in settings. STEPS TO REPRODUCE 1. Choose custom cursor 2. Put cursor on desktop (it differs, sometimes defaults to "KDE Classic" scheme 3. Put cursor on panel or an application and it matches the chosen cursor in settings. OBSERVED RESULT An old or different cursor theme appears on some parts of the desktop and parts of the Plasma workspace but *does* appear on applications and the panels. EXPECTED RESULT Cursor theme should be coherent across all elements of the Plasma workspace and open applications. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Some some parts of the desktop do show the applied cursor theme while other parts show the wrong theme. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439118] Left-click on Latte Tasks shows no windows previews when all effects are disabled
https://bugs.kde.org/show_bug.cgi?id=439118 --- Comment #2 from borivoje petrovic --- It seems that I have found it. It is in latte tasks that there wasn't the option of clicking of different mouse keys. I am closing the issue. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439125] New: Opening file on Windows starts in %SYSTEM_ROOT% (system32) instead of user home
https://bugs.kde.org/show_bug.cgi?id=439125 Bug ID: 439125 Summary: Opening file on Windows starts in %SYSTEM_ROOT% (system32) instead of user home Product: kate Version: 20.12.2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: jm.ouwerk...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install Kate app via MS App store 2. Launch Kate 3. Attempt to Open a file from UI OBSERVED RESULT The Open file dialog starts in C:\Windows\System32 (%SYSTEM_ROOT%) EXPECTED RESULT I would expect it to start in my user home directory. SOFTWARE/OS VERSIONS Windows: Edition Windows 10 Enterprise Version 20H2 Installed on17/03/2021 OS build19042.1052 Experience Windows Feature Experience Pack 120.2212.2020.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439124] New: Konsole - tabs to space conversion
https://bugs.kde.org/show_bug.cgi?id=439124 Bug ID: 439124 Summary: Konsole - tabs to space conversion Product: konsole Version: 21.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: matthew.lev...@gmail.com Target Milestone: --- SUMMARY Hello. I noticed that the output on Konsole terminal is different from the output on the file. Example: du test/* 4 test/aaa-file.txt 4 test/bbb-file.txt 4 test/ccc-file.txt Between "4" and "test/aaa-file.txt" there are 7 spaces. So I copy that output from Konsole, I'll get 7 spaces in between. On the other hand, if I run the following command du test/* > ~/Desktop/output.txt, I'll get tabs instead, on the output.txt file. 4 test/aaa-file.txt (<<< tab in between) 4 test/bbb-file.txt (<<< tab in between) 4 test/ccc-file.txt (<<< tab in between) That makes total difference in terms of CTRL-C + CTRL-V results. You can copy and paste from Konsole terminal into other softwares and the results are much better. Where can I disable this "tab to spaces" conversion on KDE Konsole? I really-really-really appreciate your help. Thank you so much. SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.11-300.fc34.x86_64 OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439123] Shift+Delete for sending SIGKILL does not work
https://bugs.kde.org/show_bug.cgi?id=439123 --- Comment #1 from Jan Keith Darunday --- Created attachment 139642 --> https://bugs.kde.org/attachment.cgi?id=139642=edit Screenshot showing what happens when you shift+delete in th old system monitor -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439123] New: Shift+Delete for sending SIGKILL does not work
https://bugs.kde.org/show_bug.cgi?id=439123 Bug ID: 439123 Summary: Shift+Delete for sending SIGKILL does not work Product: plasma-systemmonitor Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: jkcdarun...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY In the original system monitor, selecting a process and pressing shift+delete (instead of just delete) shows a window confirming the killing of the process (not just SIGTERM). In the new system monitor, the support for sending SIGTERM for delete was recently added but the support for shift+delete for sending SIGKILL wasn't causing a feature regression between the old and new system monitor. STEPS TO REPRODUCE 1. Go to plasma-systemmonitor 2. Go to processes 3. Select a process 4. Press delete (works) and then ok 5. Press shift+delete (does nothing) OBSERVED RESULT Pressing delete and accepting the popup sends SIGTERM Pressing shift+delete does nothing EXPECTED RESULT Pressing shift+delete should show a force kill popup saying that it will "immediately and forcibly kill" the process in bold then send a SIGKILL when accepted SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.12-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Attached screenshot shows pressing delete and shift+delete in the old system monitor. Both Delete and Shift+Delete also work for KSysguard -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 423100] Konsole does not render Hindi properly
https://bugs.kde.org/show_bug.cgi?id=423100 --- Comment #7 from Rishabh --- Ninjalj, it seems like the issue was fixed, not sure which version. regarding the issue with Virama in zsh there is a simple solution, refer this https://unix.stackexchange.com/questions/598440/zsh-indic-fonts-support-rendering-issue-which-is-working-fine-on-bash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427972] Display of (Qt)Virtual Keyboard doesn't work properly under Wayland session.
https://bugs.kde.org/show_bug.cgi?id=427972 Jonathan Riddell changed: What|Removed |Added CC||j...@jriddell.org --- Comment #26 from Jonathan Riddell --- I've updated Maliit in neon now to 2.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439122] Make the size of the taskbar thumbnail proportional to the size of the source window
https://bugs.kde.org/show_bug.cgi?id=439122 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439122] New: Make the size of the taskbar thumbnail proportional to the size of the source window
https://bugs.kde.org/show_bug.cgi?id=439122 Bug ID: 439122 Summary: Make the size of the taskbar thumbnail proportional to the size of the source window Product: plasmashell Version: 5.22.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: popov...@ukr.net CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139641 --> https://bugs.kde.org/attachment.cgi?id=139641=edit Current taskbar thumbnail SUMMARY Currently the size of the taskbar thumbnail is fixed and doesn't depend on the size of the source window and for windows with non-standard sizes contains a lot of empty space on the wider sides. It would be great to make the size of the taskbar thumbnail proportional to the size of the source window. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210621 KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439121] New: Info Zenter showed chrash even though no crash happened
https://bugs.kde.org/show_bug.cgi?id=439121 Bug ID: 439121 Summary: Info Zenter showed chrash even though no crash happened Product: systemsettings Version: 5.22.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: michael.thorwa...@gmx.net Target Milestone: --- Application: systemsettings5 (5.22.2) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.3.18-59.5-preempt x86_64 Windowing System: X11 Drkonqi Version: 5.22.2 Distribution: "openSUSE Leap 15.3" -- Information about the crash: - What I was doing when the application crashed: I am using the KDE in German therefore I guess it is "info center" what I used was Infozentrum. I was looking for my system and I informed myself about the usb devices. After that I closed the application by clicking on the "x" (top right corner of the window). - Unusual behavior I noticed: KDE reported that a crash had happened, but there was not crash that I could observe. I repeated it four times, and always the same behaviour. The crash can be reproduced every time. -- Backtrace: Application: Info Center (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 QScopedPointer >::operator-> (this=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #5 qGetPtrHelper > > (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1135 #6 QShortcutMap::d_func (this=) at kernel/qshortcutmap_p.h:73 #7 QShortcutMap::removeShortcut (this=this@entry=0xc8, id=-36, owner=owner@entry=0x55d91db14160, key=...) at kernel/qshortcutmap.cpp:185 #8 0x7f64d115b22e in QQuickShortcut::ungrabShortcut (this=this@entry=0x55d91db14160, shortcut=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-lp153.4.1.x86_64/src/quick/util/qquickshortcut.cpp:413 #9 0x7f64d115c259 in QQuickShortcut::ungrabShortcut (shortcut=..., this=0x55d91db14160) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-lp153.4.1.x86_64/src/quick/util/qquickshortcut.cpp:141 #10 QQuickShortcut::~QQuickShortcut (this=0x55d91db14160, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-lp153.4.1.x86_64/src/quick/util/qquickshortcut.cpp:141 #11 0x7f64d13a57f3 in QQmlPrivate::QQmlElement::~QQmlElement (this=0x55d91db14160, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-lp153.4.1.x86_64/include/QtQml/../../src/qml/qml/qqmlprivate.h:144 #12 QQmlPrivate::QQmlElement::~QQmlElement (this=0x55d91db14160, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-lp153.4.1.x86_64/include/QtQml/../../src/qml/qml/qqmlprivate.h:144 #13 0x7f64d39974eb in QObjectPrivate::deleteChildren (this=0x55d91db9ae80) at kernel/qobject.cpp:2104 #14 0x7f64d39a1e9e in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1082 #15 0x7f64d1239dad in QQuickItem::~QQuickItem (this=0x55d91db9adc0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-lp153.4.1.x86_64/src/quick/items/qquickitem.cpp:2304 #16 0x7f643e7379bd in QQuickButton::~QQuickButton (this=0x55d91db9adc0, __in_chrg=) at ../../../include/QtQuickTemplates2/5.15.2/QtQuickTemplates2/private/../../../../../src/quicktemplates2/qquickbutton_p.h:57 #17 QQuickToolButton::~QQuickToolButton (this=0x55d91db9adc0, __in_chrg=) at ../../../include/QtQuickTemplates2/5.15.2/QtQuickTemplates2/private/../../../../../src/quicktemplates2/qquicktoolbutton_p.h:55 #18 QQmlPrivate::QQmlElement::~QQmlElement (this=0x55d91db9adc0, __in_chrg=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #19 QQmlPrivate::QQmlElement::~QQmlElement (this=0x55d91db9adc0, __in_chrg=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #20 0x7f644cda1bd0 in ToolBarLayoutDelegate::~ToolBarLayoutDelegate (this=0x55d91dbbb7d0, __in_chrg=) at /usr/src/debug/kirigami2-5.83.0-lp153.146.1.x86_64/src/toolbarlayoutdelegate.cpp:82 #21 0x7f644cda1c09 in ToolBarLayoutDelegate::~ToolBarLayoutDelegate (this=0x55d91dbbb7d0, __in_chrg=) at /usr/src/debug/kirigami2-5.83.0-lp153.146.1.x86_64/src/toolbarlayoutdelegate.cpp:88 #22 0x7f644cd9e503 in std::default_delete::operator() (this=, __ptr=) at /usr/include/c++/7/bits/unique_ptr.h:78 #23 std::unique_ptr >::~unique_ptr (this=, __in_chrg=) at /usr/include/c++/7/bits/unique_ptr.h:263 #24 std::pair > >::~pair (this=, __in_chrg=) at /usr/include/c++/7/bits/stl_pair.h:208 #25 __gnu_cxx::new_allocator > > >::destroy > > > (this=, __p=) at /usr/include/c++/7/ext/new_allocator.h:140 #26 std::allocator_traits > > > >::destroy > > > (__a=..., __p=) at /usr/include/c++/7/bits/alloc_traits.h:487 #27 std::__detail::_Hashtable_alloc > >, false> > >::_M_deallocate_node (__n=0x55d91dbb2b80, this=) at /usr/include/c++/7/bits/hashtable_policy.h:2084 #28 0x7f644cda10f0 in std::__detail::_Hashtable_alloc > >, false> > >::_M_deallocate_nodes (this=,
[plasmashell] [Bug 439120] The transition between system tray applets when being hovered over by mouse doesn't look good.
https://bugs.kde.org/show_bug.cgi?id=439120 --- Comment #1 from kdeneon...@gmail.com --- Created attachment 139640 --> https://bugs.kde.org/attachment.cgi?id=139640=edit The video showing aforementioned issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439120] New: The transition between system tray applets when being hovered over by mouse doesn't look good.
https://bugs.kde.org/show_bug.cgi?id=439120 Bug ID: 439120 Summary: The transition between system tray applets when being hovered over by mouse doesn't look good. Product: plasmashell Version: 5.22.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kdeneon...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Flags: version_5_applied+, Wayland-, X11+, VisualDesign+ SUMMARY Hovering over the mouse between different applets of system tray produces inconsistent and visually ugly transition. STEPS TO REPRODUCE 1. Place the cursor on any system tray applet. 2. Take the cursor to another applet. 3. Repeat this quickly. OBSERVED RESULT The transition is does not produce consistent result. EXPECTED RESULT The transition should be consistent. Probably a fade in or fade out effect should be rendered. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION It seems less bad when there is a window instead of desktop. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437153] filenamesearch crashes in KCoreDirLister
https://bugs.kde.org/show_bug.cgi?id=437153 --- Comment #9 from Filip Fila --- (In reply to postix from comment #8) > (In reply to Filip Fila from comment #7) > > I'm using Frameworks 5.83 and I still get "The process for the filename > > search protocol died unexpectedly" error when trying to search in Dolphin. > > Do you have a complete stacktrace? For me it's fixed on openSUSE TW, > Frameworks 5.83. This is Manjaro so I don't have debug symbols. I'm running 5.83.0 with Baloo completely disabled. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 437742] maliit-keyboard has broken dependencies
https://bugs.kde.org/show_bug.cgi?id=437742 Jonathan Riddell changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jonathan Riddell --- package updated now -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437153] filenamesearch crashes in KCoreDirLister
https://bugs.kde.org/show_bug.cgi?id=437153 --- Comment #8 from postix --- (In reply to Filip Fila from comment #7) > I'm using Frameworks 5.83 and I still get "The process for the filename > search protocol died unexpectedly" error when trying to search in Dolphin. Do you have a complete stacktrace? For me it's fixed on openSUSE TW, Frameworks 5.83. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437153] filenamesearch crashes in KCoreDirLister
https://bugs.kde.org/show_bug.cgi?id=437153 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #7 from Filip Fila --- I'm using Frameworks 5.83 and I still get "The process for the filename search protocol died unexpectedly" error when trying to search in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303331] kwin shows too small previews/thumbnails
https://bugs.kde.org/show_bug.cgi?id=303331 popov895 changed: What|Removed |Added CC||popov...@ukr.net --- Comment #19 from popov895 --- (In reply to Alexander Mentyu from comment #18) > Is this still reproducible? No. Can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 --- Comment #21 from Patrick Silva --- Arch Linux provides KDE Qt including the patch for qt5-wayland that supposedly fixes this crash. https://invent.kde.org/qt/qt/qtwayland/-/merge_requests/9 However, System Settings is still crashing when I apply certain changes. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 439119] New: Domain users and groups are not recognized (??? displayed)
https://bugs.kde.org/show_bug.cgi?id=439119 Bug ID: 439119 Summary: Domain users and groups are not recognized (??? displayed) Product: krusader Version: Git Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: ismelh...@ksat.cz CC: krusader-bugs-n...@kde.org Target Milestone: --- After joining domain (samba ad) using sssd the domain users and groups are not recognized and are displayed as "???" both in list view and in properties pop-up. Local users and groups are displayed correctly. ls, exa, mc, dolphin, ... displays domain users names and groups names correctly. Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 sssd.conf: ldap_id_mapping = False, id_provider = ad domain groups id = 25xx and domain users id = 65xxx -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438232] Krita's F1 link (Menu>Help>Krita Handbook) always points to English documentation URL under any locale
https://bugs.kde.org/show_bug.cgi?id=438232 Alvin Wong changed: What|Removed |Added CC||scottpetro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439118] Left-click on Latte Tasks shows no windows previews when all effects are disabled
https://bugs.kde.org/show_bug.cgi?id=439118 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Michail Vourlakos --- Use latte git version, Tasks advanced page, left click, preview windows -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 --- Comment #20 from David Edmundson --- Obviously if some-one has this crash and has explicitly verified that they have the Qt patch above cherry-picked, please do comment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 David Edmundson changed: What|Removed |Added CC||mathsping...@163.com --- Comment #19 from David Edmundson --- *** Bug 439067 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439067] System Settings Crash after Apply Window Decorations config
https://bugs.kde.org/show_bug.cgi?id=439067 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 437455 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439115] System Settings crashed while browsing around and resetting pages to defaults
https://bugs.kde.org/show_bug.cgi?id=439115 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 437455 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 David Edmundson changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #18 from David Edmundson --- *** Bug 439115 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439117] Crash in QShortcutMap::hasShortcutForKeySequence
https://bugs.kde.org/show_bug.cgi?id=439117 David Edmundson changed: What|Removed |Added Summary|Mayhem so no wonder... |Crash in ||QShortcutMap::hasShortcutFo ||rKeySequence CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439118] New: Left-click on Latte Tasks shows no windows previews when all effects are disabled
https://bugs.kde.org/show_bug.cgi?id=439118 Bug ID: 439118 Summary: Left-click on Latte Tasks shows no windows previews when all effects are disabled Product: lattedock Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: boriv...@gmail.com Target Milestone: --- SUMMARY The only thing that does not work as I would like is showing windows previews when multiple instances of an application are opened, when there is no desktop effects present (like present windows, or similar) STEPS TO REPRODUCE 1. Add latte Tasks on a panel 2. Pin one application to the launcher and open two instances (usually with middle click) 3. try to click on that icon with two instances open to show the windows previews (in order to change the active instance 4. nothing happens OBSERVED RESULT there are no windows previews when there are multiple instances open EXPECTED RESULT show windows previews in order to be able to change the active instance SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437648] Appmenu/tooltips off position when secondary monitor is configured in left-Wayland
https://bugs.kde.org/show_bug.cgi?id=437648 fuo...@gmail.com changed: What|Removed |Added CC||fuo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
