[krita] [Bug 450290] New: I cannot zoom the canvas with mouse wheel. I tried different settings but without any luck.
- 10 Jan 2022 15:19:07 +0100. Executing /Applications/krita.app/Contents/MacOS/krita Krita Version: 5.0.0, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 2208 -- -- -- -- -- -- -- -- 10 Jan 2022 15:19:07 +0100: Style: fusion. Available styles: macintosh, Windows, Fusion 10 Jan 2022 15:19:08 +0100: Database is up to date. Version: 0.0.15, created by Krita 5.0.0, at Wed Dec 29 16:30:07 2021 10 Jan 2022 15:19:14 +0100: Created image "Unnamed", 2480 * 3508 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 10 Jan 2022 15:44:33 +0100: CLOSING SESSION SESSION: 10 Jan 2022 15:45:00 +0100. Executing /Applications/krita.app/Contents/MacOS/krita Krita Version: 5.0.2, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 2355 -- -- -- -- -- -- -- -- 10 Jan 2022 15:45:00 +0100: Style: fusion. Available styles: macintosh, Windows, Fusion 10 Jan 2022 15:45:01 +0100: Database is up to date. Version: 0.0.15, created by Krita 5.0.0, at Wed Dec 29 16:30:07 2021 10 Jan 2022 15:45:16 +0100: Created image "Unnamed", 3508 * 2480 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 10 Jan 2022 15:48:05 +0100: CLOSING SESSION SESSION: 10 Jan 2022 15:48:36 +0100. Executing /Applications/krita.app/Contents/MacOS/krita Krita Version: 5.0.2, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 2383 -- -- -- -- -- -- -- -- 10 Jan 2022 15:48:36 +0100: Style: fusion. Available styles: macintosh, Windows, Fusion 10 Jan 2022 15:48:37 +0100: Database is up to date. Version: 0.0.15, created by Krita 5.0.0, at Wed Dec 29 16:30:07 2021 10 Jan 2022 15:48:42 +0100: Created image "Unnamed", 3508 * 2480 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 10 Jan 2022 15:49:41 +0100: CLOSING SESSION SESSION: 20 Jan 2022 09:51:09 +0100. Executing /Applications/krita.app/Contents/MacOS/krita Krita Version: 5.0.2, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 1515 -- -- -- -- -- -- -- -- 20 Jan 2022 09:51:09 +0100: Style: fusion. Available styles: macintosh, Windows, Fusion 20 Jan 2022 09:51:10 +0100: Database is up to date. Version: 0.0.15, created by Krita 5.0.0, at Wed Dec 29 16:30:07 2021 20 Jan 2022 09:51:22 +0100: Importing image/png to application/x-krita. Location: /Users/jakub/Desktop/opengraph-blog.png. Real location: /Users/jakub/Desktop/opengraph-blog.png. Batchmode: 0 20 Jan 2022 09:51:22 +0100: Loaded image from image/png. Size: 1012 * 506 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 20 Jan 2022 09:58:23 +0100: Autosaving: /Users/jakub/Desktop/opengraph-blog.png-autosave.kra 20 Jan 2022 09:58:23 +0100: Converting from application/x-krita to application/x-krita. Location: /Users/jakub/Desktop/opengraph-blog.png-autosave.kra. Real location: /Users/jakub/Desktop/opengraph-blog.png-autosave.kra. Batchmode: 0. Configuration: none 20 Jan 2022 09:58:23 +0100: Completed saving /Users/jakub/Desktop/opengraph-blog.png-autosave.kra (mime: application/x-krita). Result: OK. Warning: . Size: 86286 20 Jan 2022 10:07:08 +0100: SAFE ASSERT (krita): "changeList.memento == memento" in file /Users/Packaging/KritaBuild/krita/libs/image/tiles3/kis_memento_manager.cc, line 273 20 Jan 2022 10:07:11 +0100: SAFE ASSERT (krita): "changeList.memento == memento" in file /Users/Packaging/KritaBuild/krita/libs/image/tiles3/kis_memento_manager.cc, line 273 20 Jan 2022 10:09:20 +0100: Removing autosave file: /Users/jakub/Desktop/opengraph-blog.png-autosave.kra 20 Jan 2022 10:09:20 +0100: CLOSING SESSION SESSION: 20 Jan 2022 10:11:31 +0100. Executing /Applications/krita.app/Contents/MacOS/krita Krita Version: 5.0.2, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 2436 -- -- -- -- -- -- -- -- 20 Jan 2022 10:11:31 +0100: Style: fusion. Available styles: macintosh, Windows, Fusion 20 Jan 2022 10:11:32 +0100: Database is up to date. Version: 0.0.15, created by Krita 5.0.0, at Wed Dec 29 16:30:07 2021 20 Jan 2022 10:13:28 +0100: Created image "Unnamed", 256 * 256 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 20 Jan 2022 10:15:21 +0100: Importing image/png to application/x-krita. Location: /Users/jakub/Desktop/Screenshot 2022-01-20 at 10.13.50.png. Real location: /Users/jakub/Desktop/Screenshot 2022-01-20 at 10.13.50.png. Batchmode: 0 20 Jan 2022 10:15:21 +0100: Loaded image from image/png. Size: 1048 * 1046 pixels, 1.99989 dpi. Color model: 8-bit
[Craft] [Bug 455223] New: Can't run Skrooge because of KF5DBusAddons.dll
https://bugs.kde.org/show_bug.cgi?id=455223 Bug ID: 455223 Summary: Can't run Skrooge because of KF5DBusAddons.dll Product: Craft Version: master Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Blueprints Assignee: vonr...@kde.org Reporter: jnizniow...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- SUMMARY I can't run skrooge crafted with the latest Craft version. STEPS TO REPRODUCE 1. craft skrooge 2. Execute \CraftRoot\build\extragear\skrooge\work\build\bin\skrooge.exe OBSERVED RESULT A system error "The code execution cannot proceed because KF5DBusAddons.dll was not found. Reinstalling the program may fix this problem" EXPECTED RESULT Running skrooge smoothly SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION I updated Craft, Skrooge, and kdbusaddons, with no errors. I even can find the "missing" library, so I followed some guide adivisng to use "regsvr32 /u [pathname]" command - but that gave me another error: "The module [pathname] was loaded but the entry point DllUnregisterServer was not found. Make sure that [pathname] is a valid DLL or OCX file and try again." -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 455223] Can't run Skrooge because of KF5DBusAddons.dll
https://bugs.kde.org/show_bug.cgi?id=455223 Jakub changed: What|Removed |Added CC||jnizniow...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476791] Qt apps running as root are transparent (and so Installation window is transparent)
https://bugs.kde.org/show_bug.cgi?id=476791 --- Comment #8 from Jakub --- I was not able to reproduce it on non-Virtualbox setup, so it might be a Virtualbox thing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482760] New: Global shortcuts not working with NumPad
https://bugs.kde.org/show_bug.cgi?id=482760 Bug ID: 482760 Summary: Global shortcuts not working with NumPad Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jaburek.ja...@gmail.com Target Milestone: --- SUMMARY After updating to Plasma 6.0.1, global shortcuts containing numbers stopped working when pressing the numbers on the numpad. Example: I have configured Switch to desktop with Meta+, now the shortcut works only when I press Meta+Shift+"+" (my keyboard layout is Czech, and to type 1 without the numpad, I have to press Shift and the key above letter Q). STEPS TO REPRODUCE 1. Configure a Switch to Desktop 1 shortcut using Meta+1. 2. Apply changes. 3. Be on another desktop than 1, and press Meta and 1 on the numpad. OBSERVED RESULT Nothing happens. EXPECTED RESULT Plasma should switch to Desktop 1. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with kernel 6.7.8-zen1-1-zen (64-bit) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Graphics Platform: Wayland ADDITIONAL INFORMATION System settings correctly accepts input from the numpad. I can set shortcut Meta+1 by pressing 1 on the numpad, but after saving the shortcut, Plasma will not recognize it, unless I use the key above the letter part and hold Shift at the same time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483257] New: Floating panel dodges Firefox window way too early
https://bugs.kde.org/show_bug.cgi?id=483257 Bug ID: 483257 Summary: Floating panel dodges Firefox window way too early Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: h...@kopanko.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 166964 --> https://bugs.kde.org/attachment.cgi?id=166964&action=edit A screen recording SUMMARY Firefox window makes the panel hide too early, when it not near it. STEPS TO REPRODUCE 1. Set panel to dodge windows 2. Open Firefox window 3. Move it close to the panel OBSERVED RESULT Panel dodges the window when it is far away. EXPECTED RESULT Like with other windows, it should hide only when Firefox is near. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A34 System Version: 1.0 ADDITIONAL INFORMATION Attached is a screen recording of this behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483257] On X11, floating panel dodges CSD-using Firefox window way too early
https://bugs.kde.org/show_bug.cgi?id=483257 --- Comment #3 from Jakub --- (In reply to Nate Graham from comment #2) > Possibly it's the CSD headerbar? Cannot reproduce the issue with Firefox in > CSD mode, though--at least on Wayland. Possibly an X11-only bug. > > Can you reproduce it on X11, Niccolò? When I ran Firefox with GTK_CSD=0 the problem disappeared. I don't think this solves the issue, but it does narrow it down. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481085] Battery widget in panel doesn't save "show percent" setting
https://bugs.kde.org/show_bug.cgi?id=481085 Jakub changed: What|Removed |Added CC||jjaruszew...@outlook.com --- Comment #10 from Jakub --- Can still reproduce on Plasma 6.0.5 on two different laptops. Now one has this setting permanently disabled (it was a relatively fresh plasma 6 install). And one has this setting permanently enabled (I enabled it back in Plasma 5). Either way changes to this setting does not save the changes to the config file :c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483932] Plasmashell segfaults in libfreetype.so.6 when adding plasmoid with custom font
https://bugs.kde.org/show_bug.cgi?id=483932 Jakub changed: What|Removed |Added Version|6.0.2 |6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483468] New: Dragging is broken for chromium/all electron based apps when running in native Wayland
https://bugs.kde.org/show_bug.cgi?id=483468 Bug ID: 483468 Summary: Dragging is broken for chromium/all electron based apps when running in native Wayland Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jjaruszew...@outlook.com Target Milestone: --- Created attachment 167112 --> https://bugs.kde.org/attachment.cgi?id=167112&action=edit Rearranging bookmarks plasma 5 vs 6 SUMMARY Rearranging bookmarks etc. does not work when running in native Wayland. *This is a regression from Plasma 5* Also happens if i try to rearrange files in obsidian (drag file to a folder) or try to change servers order on Vesktop (Discord) STEPS TO REPRODUCE 1. Open any chromium app in native Wayland 2. Try to rearrange any element with apps 3. See it does not work OBSERVED RESULT Bookmarks do not rearrange EXPECTED RESULT Bookmarks etc. rearrange correctly SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-12650H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop N7601ZM_N7601ZM System Version: 1.0 ADDITIONAL INFORMATION An attachment video was taken on 2 different PCs since I didn't want to downgrade on this one, but drad&drop was working on this PC too with Plasma 5. I have 250% fractional scaling and one monitor only. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483468] Dragging is broken for chromium/all electron based apps when running in native Wayland
https://bugs.kde.org/show_bug.cgi?id=483468 Jakub changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jakub --- I updated to 6.0.2 today and it's working again! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483593] New: ConfigOverlay.qml:288: TypeError: Cannot read property 'applet' of null when adding a widget
https://bugs.kde.org/show_bug.cgi?id=483593 Bug ID: 483593 Summary: ConfigOverlay.qml:288: TypeError: Cannot read property 'applet' of null when adding a widget Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jjaruszew...@outlook.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY This does not happen always, but it's easiest to reproduce while adding an applet from "Plasma 6 clocks" category in store. Happened to me with KDE ModernClock (https://store.kde.org/p/2135653) (but happens with others too). It's 90% reproducible, but if you happen to successfully place the widget, error does not happen again. My guess is that ConfigOverlay.qml:288 does not check for existence of `currentApplet` (like in bug https://bugs.kde.org/show_bug.cgi?id=335268 but different line number) STEPS TO REPRODUCE 1. Add KDE Moder Clock to your desktop OBSERVED RESULT Plasma crashes 9/10 times :/ EXPECTED RESULT Plasma does not crash :) SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-12650H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop N7601ZM_N7601ZM System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 477574] Skanlite crashesh on startup
https://bugs.kde.org/show_bug.cgi?id=477574 Jakub changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Jakub --- No longer crashing on released plasma 6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477579] Plasma does not close Chromium broswers running under Xwayland on logout
https://bugs.kde.org/show_bug.cgi?id=477579 Jakub changed: What|Removed |Added Summary|Plasma only tries to close |Plasma does not close |native Wayland windows and |Chromium broswers running |not Xwayland ones causing |under Xwayland on logout |data loss | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477579] Plasma does not close Chromium broswers running under Xwayland on logout
https://bugs.kde.org/show_bug.cgi?id=477579 --- Comment #4 from Jakub --- Yes, it's only chroium browsers running Xwayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483593] ConfigOverlay.qml:288: TypeError: Cannot read property 'applet' of null when adding a widget
https://bugs.kde.org/show_bug.cgi?id=483593 --- Comment #1 from Jakub --- This is line 289 in current master, which is exactly: https://invent.kde.org/plasma/plasma-desktop/-/blob/84900edcea17bb2070606f3a1520f57aff1d1476/containments/panel/contents/ui/ConfigOverlay.qml#L289 I believe the solution would be the same as in: https://invent.kde.org/plasma/plasma-desktop/-/blob/84900edcea17bb2070606f3a1520f57aff1d1476/containments/panel/contents/ui/ConfigOverlay.qml#L310 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483593] ConfigOverlay.qml:288: TypeError: Cannot read property 'applet' of null when adding a widget
https://bugs.kde.org/show_bug.cgi?id=483593 --- Comment #3 from Jakub --- (In reply to Niccolò Venerandi from comment #2) > I'll do a MR with your suggestion as that should certainly hide the error, > but it really shouldn't be crashing! I did some investigating and you're right, this error is not the reason of the crash! Actually plasma segfaults in libfreetype.so.6.20.1 when adding a plasmoid using custom font (and bug appears in "Plasma 6 clocks" since they often use custom fonts). I will create a separate bug report for that and link it here -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483932] New: Plasmashell segfaults in libfreetype.so.6 when adding plasmoid with custom font
https://bugs.kde.org/show_bug.cgi?id=483932 Bug ID: 483932 Summary: Plasmashell segfaults in libfreetype.so.6 when adding plasmoid with custom font Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jjaruszew...@outlook.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY This is reproducible 9/10 times. If plasmoid is placed successfully, error does not occur again (after restart etc.). If plasmoid is placed on the panel, then plasma goes into crashloop. STEPS TO REPRODUCE 1. Add plasmoid with custom font (for example: https://store.kde.org/p/2135653/, but the bug happens with the others too) 2. Plasmashell crashes OBSERVED RESULT Plasmashell crashes EXPECTED RESULT Plasmoid is placed successfully, at worst case error message is displayed STACK TRACE: Message: Process 1415 (plasmashell) of user 1000 dumped core. Stack trace of thread 1415: #0 0x77f2a0e20ef1 FT_Get_PS_Font_Info (libfreetype.so.6 + 0x90ef1) #1 0x77f2a2f3e600 _ZN13QFontEngineFT4initEN11QFontEngine6FaceIdEbNS0_11GlyphFormatEP13QFreetypeFace (libQt6Gui.so.6 + 0x53e600) #2 0x77f2a2f3ed1f _ZN13QFontEngineFT4initEN11QFontEngine6FaceIdEbNS0_11GlyphFormatERK10QByteArray (libQt6Gui.so.6 + 0x53ed1f) #3 0x77f2a2f4bf89 _ZN19QFontconfigDatabase10fontEngineERK8QFontDefPv (libQt6Gui.so.6 + 0x54bf89) #4 0x77f2a2d9a97b _ZN20QFontDatabasePrivate16loadSingleEngineEiRK8QFontDefP12QtFontFamilyP13QtFontFoundryP11QtFontStyleP10QtFontSize (libQt6Gui.so.6 + 0x39a97b) #5 0x77f2a2d9abb9 _ZN20QFontDatabasePrivate10loadEngineEiRK8QFontDefP12QtFontFamilyP13QtFontFoundryP11QtFontStyleP10QtFontSize (libQt6Gui.so.6 + 0x39abb9) #6 0x77f2a2da6ba7 _ZN20QFontDatabasePrivate8findFontERK8QFontDefib (libQt6Gui.so.6 + 0x3a6ba7) #7 0x77f2a2da7726 _ZN20QFontDatabasePrivate4loadEPK12QFontPrivatei (libQt6Gui.so.6 + 0x3a7726) #8 0x77f2a3058d1a n/a (libQt6Gui.so.6 + 0x658d1a) #9 0x77f2a2d848a5 _ZNK9QFontInfo6familyEv (libQt6Gui.so.6 + 0x3848a5) #10 0x77f2a3be3131 _ZN10QQuickText12updatePolishEv (libQt6Quick.so.6 + 0x1e3131) #11 0x77f2a3c29cca _ZN19QQuickWindowPrivate11polishItemsEv (libQt6Quick.so.6 + 0x229cca) #12 0x77f2a3dc6175 n/a (libQt6Quick.so.6 + 0x3c6175) #13 0x77f2a3c34779 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x234779) #14 0x77f2a42f438b _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xf438b) #15 0x77f2a2539818 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x139818) #16 0x77f2a2bb45d0 _ZN15QPlatformWindow20deliverUpdateRequestEv (libQt6Gui.so.6 + 0x1b45d0) #17 0x77f2a257c2c7 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x17c2c7) #18 0x77f2a42f438b _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xf438b) #19 0x77f2a2539818 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x139818) #20 0x77f2a2539b9b _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x139b9b) #21 0x77f2a27758a4 n/a (libQt6Core.so.6 + 0x3758a4) #22 0x77f2a1072f69 n/a (libglib-2.0.so.0 + 0x59f69) #23 0x77f2a10d13a7 n/a (libglib-2.0.so.0 + 0xb83a7) #24 0x77f2a1071162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #25 0x77f2a27739c4 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3739c4) #26 0x77f2a2543d6e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x143d6e) #27 0x77f2a253c2b8 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x13c2b8) #28 0x5fa55edf8476 n/a (plasmashell + 0x27476) #29 0x77f2a1e43cd0 n/a (libc.so.6 + 0x29cd0) #30 0x77f2a1e43d8a __libc_start_main (libc.so.6 + 0x29d8a) #31 0x5fa55edf8c65 n/a (plasmashell + 0x27c65) Stack trace of thread 1602: #0 0x77f2a1f190bf __poll (libc.so.6 + 0xff0bf) #1 0x77f2a10d12f6 n/a (libglib-2.0.so.0 + 0xb82f6) #2 0x77f2a1071162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x77f2a27739c4 _ZN20QEventDispatcherG
[plasmashell] [Bug 483593] ConfigOverlay.qml:288: TypeError: Cannot read property 'applet' of null when adding a widget
https://bugs.kde.org/show_bug.cgi?id=483593 --- Comment #4 from Jakub --- Filed a related bug report at: https://bugs.kde.org/show_bug.cgi?id=483932 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477579] Plasma does not close Chromium broswers running under Xwayland on logout
https://bugs.kde.org/show_bug.cgi?id=477579 --- Comment #6 from Jakub --- I am still able to reproduce this on newest Neon Unstable with all updates installed (19.03.2024), although this time it's on VM since I'm no longer using KDE Neon on my machine (but still Plasma 6 ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142
Jakub changed:
What|Removed |Added
CC||jjaruszew...@outlook.com
--- Comment #33 from Jakub ---
As stated in Chromium issue:
> There seems to have been some recent change in Kwin which has caused it to no
> longer send wl_data_source.{dnd_finished,cancelled} after
> wl_data_source.dnd_drop_performed in these cases described in the repro
> steps. My understanding is that it's a kwin bug, though Chromium should
> minimally protect against this kind of compositor misbehavior and bugs
> instead of the taking assumptions and stop responding to input events (due to
> the dnd nested message loop to be kept running indefinitely).
So maybe this is the kwin bug? Reproducible for me
--
You are receiving this mail because:
You are watching all bug changes.
[Craft] [Bug 452519] New: sqlcipher cannot be installed
https://bugs.kde.org/show_bug.cgi?id=452519 Bug ID: 452519 Summary: sqlcipher cannot be installed Product: Craft Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Blueprints Assignee: vonr...@kde.org Reporter: jnizniow...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. craft sqlcipher (or any app dependent on sqlcipher) OBSERVED RESULT The package isn't installed, there's an output instead: C:/CraftRoot/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -ltclstub8.6 collect2.exe: error: ld returned 1 exit status make: *** [Makefile:613: libtclsqlite3.la] Error 1 ←[33mAction: compile for libs/sqlcipher:3.4.2-6 FAILED←[0m *** Craft all failed: libs/sqlcipher after 3 minutes 15 seconds *** ←[31mfatal error: package libs/sqlcipher all failed←[0m Craft stopped with out completing ['libs/sqlcipher'] EXPECTED RESULT sqlcipher installed SOFTWARE/OS VERSIONS Windows: Windows10 ADDITIONAL INFORMATION As you can see, I'm using minGW (VS compiler didn't work for me) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 227625] Rectangle Tool -> Tool Options -> Fill With -> Gradient
https://bugs.kde.org/show_bug.cgi?id=227625 jakub changed: What|Removed |Added CC||kubajuchn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Jakub changed: What|Removed |Added CC|jakubmadej.pl+...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Plasma Wayland session (kwin_wayland) random crashes (segfault)
https://bugs.kde.org/show_bug.cgi?id=475629 Jakub changed: What|Removed |Added CC||jaburek.ja...@gmail.com --- Comment #3 from Jakub --- I have also started to experience random kwin_wayland crashes. So far they have only happened when interacting with the system, such as clicking on a button or moving the mouse, not when the computer is idle. I don’t think there’s a particular application that’s causing the crash. Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4720HQ CPU @ 2.60GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Backtrace: Thread 11 (Thread 0x7fc3eb7fe6c0 (LWP 21124)): #0 0x7fc44d8a74ae in () at /usr/lib/libc.so.6 #1 0x7fc44d8a9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fc4356d1b5c in () at /usr/lib/dri/crocus_dri.so #3 0x7fc43571ca0c in () at /usr/lib/dri/crocus_dri.so #4 0x7fc44d8aa9eb in () at /usr/lib/libc.so.6 #5 0x7fc44d92e7cc in () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fc41cdfe6c0 (LWP 16762)): #0 0x7fc44d8a74ae in () at /usr/lib/libc.so.6 #1 0x7fc44d8a9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fc4356d1b5c in () at /usr/lib/dri/crocus_dri.so #3 0x7fc43571ca0c in () at /usr/lib/dri/crocus_dri.so #4 0x7fc44d8aa9eb in () at /usr/lib/libc.so.6 #5 0x7fc44d92e7cc in () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fc41d5ff6c0 (LWP 16224)): #0 0x7fc44d8a74ae in () at /usr/lib/libc.so.6 #1 0x7fc44d8a9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fc4356d1b5c in () at /usr/lib/dri/crocus_dri.so #3 0x7fc43571ca0c in () at /usr/lib/dri/crocus_dri.so #4 0x7fc44d8aa9eb in () at /usr/lib/libc.so.6 #5 0x7fc44d92e7cc in () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fc42c8bd6c0 (LWP 16198)): #0 0x7fc44d920f6f in poll () at /usr/lib/libc.so.6 #1 0x7fc44c16c276 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc44c10c162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc44e8eaf7c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc44e89ae74 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc44e6f74f6 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc44e6f371a in () at /usr/lib/libQt5Core.so.5 #7 0x7fc44d8aa9eb in () at /usr/lib/libc.so.6 #8 0x7fc44d92e7cc in () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fc3ea7fc6c0 (LWP 17678)): #0 0x7fc44d8a74ae in () at /usr/lib/libc.so.6 #1 0x7fc44d8a9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fc4356d1b5c in () at /usr/lib/dri/crocus_dri.so #3 0x7fc43571ca0c in () at /usr/lib/dri/crocus_dri.so #4 0x7fc44d8aa9eb in () at /usr/lib/libc.so.6 #5 0x7fc44d92e7cc in () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fc400f656c0 (LWP 16486)): #0 0x7fc44d920f6f in poll () at /usr/lib/libc.so.6 #1 0x7fc44c16c276 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc44c10c162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc44e8eaf7c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc44e89ae74 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc44e6f74f6 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc44f6c59b0 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fc44e6f371a in () at /usr/lib/libQt5Core.so.5 #8 0x7fc44d8aa9eb in () at /usr/lib/libc.so.6 #9 0x7fc44d92e7cc in () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fc406c0 (LWP 16226)): #0 0x7fc44d920f6f in poll () at /usr/lib/libc.so.6 #1 0x7fc44c16c276 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc44c10c162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc44e8eaf7c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc44e89ae74 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc44e6f74f6 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc44f6c59b0 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fc44e6f371a in () at /usr/lib/libQt5Core.so.5 #8 0x7fc44d8aa9eb in () at /usr/lib/libc.so.6 #9 0x7fc44d92e7cc in () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fc4487ff6c0 (LWP 16184)): #0 0x7fc44d920f6f in poll () at /usr/lib/libc.so.6 #1 0x7fc44c16c276 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc44c10c162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc44e8eaf7c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc44e89ae74 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5
[kwin] [Bug 475629] Plasma Wayland session (kwin_wayland) random crashes (segfault)
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #6 from Jakub --- I had three crashes just today. I will downgrade Qt5 packages to version 5.15.10 and see if the crashes keep happening. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Plasma Wayland session (kwin_wayland) random crashes (segfault)
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #8 from Jakub --- I do have Bismuth (https://github.com/Bismuth-Forge/bismuth) installed and enabled. However if I remember correctly, no crash was during opening/closing a window or any other kind of window manipulation that would engage Bismuth. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #13 from Jakub --- Unfortunately Polonium does not support layouts that I use with Bismuth, and Bismuth still works fine for me even with the latest version of KWin. Yesterday I downgraded Qt5 packages to version 5.15.10, and didn’t experience any crash so far either. Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.10 List of qt5-* package versions: qt5-base 5.15.10+kde+r165-1 qt5-declarative 5.15.10+kde+r31-1 qt5-graphicaleffects 5.15.10-1 qt5-imageformats 5.15.11+kde+r12-1 qt5-location 5.15.10+kde+r5-1 qt5-multimedia 5.15.10+kde+r3-1 qt5-networkauth 5.15.10-1 qt5-quickcontrols 5.15.10-1 qt5-quickcontrols2 5.15.10+kde+r6-1 qt5-script 5.15.15-2 qt5-sensors 5.15.10-1 qt5-speech 5.15.10+kde+r1-1 qt5-svg 5.15.10+kde+r8-1 qt5-tools 5.15.10+kde+r3-2 qt5-translations 5.15.10-1 qt5-wayland 5.15.10+kde+r62-1 qt5-webchannel 5.15.10+kde+r3-1 qt5-webengine 5.15.15-2 qt5-webview 5.15.10-1 qt5-x11extras 5.15.10-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #16 from Jakub --- Update: After four days with the latest Plasma packages but Qt5 packages downgraded to version 5.15.10, I have not experienced a single KWin crash even with Bismuth active, in contrast to 2-3 crashes per day with Qt5 version 5.15.11. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476791] Qt apps running as root are transparent (and so Installation window is transparent)
https://bugs.kde.org/show_bug.cgi?id=476791 Jakub changed: What|Removed |Added Ever confirmed|0 |1 Summary|Installation window is |Qt apps running as root are |transparent |transparent (and so ||Installation window is ||transparent) CC||jjaruszew...@outlook.com Status|REPORTED|CONFIRMED --- Comment #3 from Jakub --- Can confirm on VirtualBox with 3D acceleration enabled. Also, this occurs to Qt6 apps running as root (for example Okular) on Wayland. Calamares running as normal user is not transparent (but it's no longer possible to install). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477573] New: Plasma always prevents logout (in any form) saying that there are apps preventing it even when no apps are running
https://bugs.kde.org/show_bug.cgi?id=477573 Bug ID: 477573 Summary: Plasma always prevents logout (in any form) saying that there are apps preventing it even when no apps are running Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: jjaruszew...@outlook.com Target Milestone: 1.0 Created attachment 163507 --> https://bugs.kde.org/attachment.cgi?id=163507&action=edit Logout confirmation with empty app list SUMMARY: Plasma always says that there are apps preventing logout even if there are none (no application windows is running and presented list of applications which prevent logout is empty) Related to: https://bugs.kde.org/show_bug.cgi?id=461176 Essentialy logout/shutdown/restart button does nothing and requires confirmation. STEPS TO REPRODUCE 1. Do not have any apps opened 2. Click on logout/shutdown/restart and confirm 3. Nothing happens for ~10 seconds 4. Popup appears saying that there are apps which prevent plasma from closing OBSERVED RESULT Plasma does not log out EXPECTED RESULT Plasma does log out if no application is preventing it SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon Unstable 20231126-1118 KDE Plasma Version: 5.81.80 (git master from neon unstable) KDE Frameworks Version: 5.245.0 (git master from neon unstable) Qt Version: 6.6.0 ADDITIONAL INFORMATION Running on real hardware, not VM. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 477574] New: Skanlite crashesh on startup
https://bugs.kde.org/show_bug.cgi?id=477574 Bug ID: 477574 Summary: Skanlite crashesh on startup Classification: Applications Product: Skanlite Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: jjaruszew...@outlook.com Target Milestone: --- Application: skanlite (24.01.80) Qt Version: 6.6.0 Frameworks Version: 5.245.0 Operating System: Linux 6.2.0-37-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.81.80 [CoredumpBackend] -- Information about the crash: Skanlite immediately crashesh on startup The crash can be reproduced every time. -- Backtrace: Application: Skanlite (skanlite), signal: Segmentation fault PID: 9163 (skanlite) UID: 1000 (jjaruszewski) GID: 1000 (jjaruszewski) Signal: 11 (SEGV) Timestamp: Sun 2023-11-26 18:02:40 CET (51s ago) Command Line: /usr/bin/skanlite Executable: /usr/bin/skanlite Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.skanlite-a7fa84018e184b99a677ca164a2db474.scope Unit: user@1000.service User Unit: app-org.kde.skanlite-a7fa84018e184b99a677ca164a2db474.scope Slice: user-1000.slice Owner UID: 1000 (jjaruszewski) Boot ID: 14a40efcf39a4c09bb81c2c25ce10cb3 Machine ID: 555d2e1c62ea410fb90ce441e165cc0e Hostname: KJ-VIVOBOOK-S Storage: /var/lib/systemd/coredump/core.skanlite.1000.14a40efcf39a4c09bb81c2c25ce10cb3.9163.170101816000.zst (present) Disk Size: 2.5M Message: Process 9163 (skanlite) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: aa5961f67fdb1ddb51def426e5bd6ca19fe33f10 Found module libKF5Style.so.5 with build-id: 2b92dd0444710ee4b8965972064ddf1e2c7a25f7 Found module libKF5Kirigami2.so.5 with build-id: d78fd3983d3db561a1107595f679efd768ec7413 Found module breeze5.so with build-id: 4015fec34229663d7f2c36e35afb355284fee393 Found module libpciaccess.so.0 with build-id: 4c93da952f83c1d085d4bdead692db544c79b004 Found module libtinfo.so.6 with build-id: e22ba7829a55a0dec2201a0b6dac7ba236118561 Found module libedit.so.2 with build-id: 9fcc3490de1a1f4919b1f6e398c99c7fa25f6863 Found module libdrm_intel.so.1 with build-id: 6b6329ad8a54ece1de4227b973970ebe471596c0 Found module libdrm_nouveau.so.2 with build-id: dfcb23b6631971a8c166f36bcb360e3839709a19 Found module libdrm_amdgpu.so.1 with build-id: 9b1da9a94f6ac68aed5fbcdd6f821efe2feeef28 Found module libelf.so.1 with build-id: 0eaf2d056fb292c3da2d99fa16c13d0ec798f121 Found module libdrm_radeon.so.1 with build-id: a071d941cf0318887e8965574d85c68e9f9ae7cd Found module libsensors.so.5 with build-id: 0d5803327d5e32a301844fb819fd3c762f8e69f6 Found module libLLVM-15.so.1 with build-id: 5d46c4221e9c32a1695da30bd95956dd9ce00984 Found module radeonsi_dri.so with build-id: d04a40e4062a8d444ff6f23d4fe768215b2e32c7 Found module libxshmfence.so.1 with build-id: f08296172ec7b676e1b371afc936e36add17366d Found module libxcb-sync.so.1 with build-id: 657d8516621c4042b4b221ce1b3525f92467ef7e Found module libxcb-present.so.0 with build-id: a4f415af56b06f1f38d5a0339dd9828ff136b115 Found module libxcb-dri3.so.0 with build-id: b6aa69fda711358025ae4dd29fa597866d29b8c5 Found module libwayland-server.so.0 with build-id: 973784b08700f99c40a702bb84da23ee78506225 Found module libdrm.so.2 with build-id: aa04a7263412a52fcfb9b97aa9d8518446ad01fc Found module libxcb-xfixes.so.0 with build-id: d6f264cc06fb6c92b5ced2c8f373cf5a5bda0e09 Found module libxcb-randr.so.0 with build-id: 7af27bf3e608d5c06645ad4086788afe8a8447e7 Found module libxcb-dri2.so.0 with build-id: dc5a2c2b0c9080fff87ea241e7298a7ac2f838e3 Found module libX11-xcb.so.1 with build-id: 70f2a36d79c623f42fd70fa7ffb06d8877c74f16 Found module libglapi.so.0 with build-id: a0ccfe27e38672edb3d602648e22711af960a154 Found module libgbm.so.1 with build-id: ea71017c17a466d7487e7c49bd1e548d094922f3 Found module libEGL_mesa.so.0 with build-id: fc1b63774e1077067c206cadb31412e44162ec9e Found module libwayland-egl.so.1 with build-id: 5e405bc68eeaab993b8d7a62c8d2b3f973b22953 Found module libqt-plugin-wayland-egl.so with build-id: a80d90540824e932d67d72ca8106f503cd79cee1 Found module libogg.so.0 with build-id: 842412496daf280ca5491dfb6581df5a378b72f0
[plasmashell] [Bug 477573] Plasma always prevents logout (in any form) saying that there are apps preventing it even when no apps are running
https://bugs.kde.org/show_bug.cgi?id=477573 --- Comment #1 from Jakub --- Note that this only happens where no app windows are present. If there is at least one window and kwin/plasma manages to close it, it will log out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477578] New: Spacing around floating panels (Kickoff/plasmoids) is not consistent
https://bugs.kde.org/show_bug.cgi?id=477578 Bug ID: 477578 Summary: Spacing around floating panels (Kickoff/plasmoids) is not consistent Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jjaruszew...@outlook.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 163511 --> https://bugs.kde.org/attachment.cgi?id=163511&action=edit Kickoff with improper spacing SUMMARY After a fresh login, floating panels which are on the edge of The Panel (such as Kickoff is on the left by default) are aligned to the edge of the screen. However after The Panel defloats and floats again (either by disabling and re-enabling floating or maximizing a window) floating panels are no longer aligned to the edge of the screen (and have proper spacing). Note that for users with Panel set to "dodge windows/windows go below/auto hide" issue won't go away by itself since panel won't defloat automatically. STEPS TO REPRODUCE 1. Have a floating panel set to whole width of the screen (default) and Kickoff/System tray at the edges (default) 2. Login into plasma and do not open any apps 3. Kickoff/floating plasmoids are misaligned 4. Defloat and re-float the panel 5. Now Kickoff/plasmoids have proper spacing OBSERVED RESULT Floating kickoff/plasmoids do not have proper spacing after a fresh login EXPECTED RESULT Floating kickoff/plasmoids have proper spacing after a fresh login SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop X521IA_M533IA System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477573] Plasma always prevents logout (in any form) saying that there are apps preventing it even when no apps are running
https://bugs.kde.org/show_bug.cgi?id=477573 --- Comment #3 from Jakub --- Additional thing: Kwin/Plasma only tries to close native wayland windows, but not Xwayland windows, so Xwayland app does not count as "open" in this case. I will create a separate bug report for this though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477579] New: Plasma only tries to close native Wayland windows and not Xwayland ones causing data loss
https://bugs.kde.org/show_bug.cgi?id=477579 Bug ID: 477579 Summary: Plasma only tries to close native Wayland windows and not Xwayland ones causing data loss Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: jjaruszew...@outlook.com Target Milestone: 1.0 SUMMARY Related to: https://bugs.kde.org/show_bug.cgi?id=461176 When logging out of plasma it will try to close native Wayland windows only, but not Xwayland ones. STEPS TO REPRODUCE Probably easiest to reproduce with Chromium based browser which will prompt for confirmation when multiple tabs are open. 1. Have an app which a - can run on both native wayland and xwayland, b - will prompt you for confirmation when closing it 2. Log out/shutdown/restart - xwayland app does not prompt you (and won't be listed in apps that prevented logging out if any) 3. Switch app to native wayland 4. Log out/shutdown/restart - app now prompts before closing OBSERVED RESULT Xwayland apps are not prompting for unsaved work EXPECTED RESULT Xwayland apps are prompting for unsaved work SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop X521IA_M533IA System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461176] Applications don't prompt to save unsaved work when logging out on Wayland, causing data loss
https://bugs.kde.org/show_bug.cgi?id=461176 Jakub changed: What|Removed |Added CC||jjaruszew...@outlook.com --- Comment #9 from Jakub --- Now plasma closes native Wayland apps, but still does not close Xwayland apps. Created separate bug report for that: https://bugs.kde.org/show_bug.cgi?id=477579 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477573] Plasma always prevents logout (in any form) saying that there are apps preventing it even when no apps are running
https://bugs.kde.org/show_bug.cgi?id=477573 Jakub changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477579 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477579] Plasma only tries to close native Wayland windows and not Xwayland ones causing data loss
https://bugs.kde.org/show_bug.cgi?id=477579 Jakub changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477573, ||https://bugs.kde.org/show_b ||ug.cgi?id=461176 CC||jjaruszew...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461176] Applications don't prompt to save unsaved work when logging out on Wayland, causing data loss
https://bugs.kde.org/show_bug.cgi?id=461176 Jakub changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477579 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477579] Plasma only tries to close native Wayland windows and not Xwayland ones causing data loss
https://bugs.kde.org/show_bug.cgi?id=477579 --- Comment #2 from Jakub --- (In reply to Nate Graham from comment #1) > ksmserver is supposed to close XWayland windows. Is this a recent > regression, or has that never worked for you? It's a fresh install of KDE Neon Unstable. I did some more testing comparing Plasma 6 and Plasma 5. Behavior of Plasma 5 is consistent - always closes all XWayland apps and Wayland apps are killed Bahavior of Plasma 6 is not - I've noticed this issue with Chromium based browser (Brave) running on Xwalyand - if the browser (xwayland) is the only running window it's not closed at all (regression from Plasma 5) - if there is at least one more native window (so for example browser (xwayland) window + kde settings (wayland) window), then all windows will close on logout, but the browser will not prompt before closing (and it should while having mutiple tabs) - but the issue is not present for every Xwayland app. For example OnlyOffice Desktop Editions (which is still on xwayland) will always close correctly AND ask for a confirmation if there is unsaved work If the browser is running on native Wayland it will properly close and ask for confirmation before closing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477625] New: Weird icon placement of apps that do not have window in Dekstop Overview
https://bugs.kde.org/show_bug.cgi?id=477625 Bug ID: 477625 Summary: Weird icon placement of apps that do not have window in Dekstop Overview Classification: Plasma Product: kwin Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: jjaruszew...@outlook.com Target Milestone: --- Created attachment 163543 --> https://bugs.kde.org/attachment.cgi?id=163543&action=edit Dekstop Overview with Wayland to X11 Video Bridge icon SUMMARY Noticed with Wayland to X11 Video Bridge enabled (default on KDE Neon). On the new desktop overview, icon of the Wayland to X11 Video Bridge is weirdly placed, but it should not even be there, since it does not have visible window (and not on the taskbar) STEPS TO REPRODUCE Note: Sometimes icon can be offscreen, so it may be useful to open mutilpe apps/add more virtual desktop 1. Have Wayland to X11 Video Bridge (check in system tray) 2. Have a couple windows open 3. Open (new) Desktop Overview Effect 4. See weirdly placed icon OBSERVED RESULT There is an icon of weirdly placed Wayland to X11 Video Bridge EXPECTED RESULT There is no icon at all SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop X521IA_M533IA System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477625] Weird icon placement of apps that do not have window in Dekstop Overview
https://bugs.kde.org/show_bug.cgi?id=477625 Jakub changed: What|Removed |Added CC||jjaruszew...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477625] Weird icon placement of apps that do not have window in Dekstop Overview
https://bugs.kde.org/show_bug.cgi?id=477625 Jakub changed: What|Removed |Added Attachment #163543|0 |1 is obsolete|| --- Comment #3 from Jakub --- Created attachment 163582 --> https://bugs.kde.org/attachment.cgi?id=163582&action=edit Wayland to X11 Video Bridge in Desktop Overview but not the Task Switcher -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477625] Weird icon placement of apps that do not have window in Dekstop Overview
https://bugs.kde.org/show_bug.cgi?id=477625 Jakub changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED --- Comment #4 from Jakub --- (In reply to David Redondo from comment #2) > > *** This bug has been marked as a duplicate of bug 477025 *** Can still reproduce. I do not have Wayland to X11 Video Bridge in the task switcher, but I do have it in the Dekstop Overview. This is no a duplicate of https://bugs.kde.org/show_bug.cgi?id=477025 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 471001] Cursors/pointers are huge in Firefox with system scaling greater than 200%
https://bugs.kde.org/show_bug.cgi?id=471001 Jakub changed: What|Removed |Added CC||jjaruszew...@outlook.com --- Comment #1 from Jakub --- Can confirm with Manjaro + Plasma 5.27.5 running Wayland with cursor size set to 24, 4k screen and 225% scaling. This does not happen only for Firefox, but for any app using GTK. Any scaling factor <= 200% works fine (even fractional scaling) but crossing 200% mark makes the cursor huge on GTK apps. (For example, 195% scaling is fine, 205% is not) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 471001] Cursors/pointers are huge in Firefox with system scaling greater than 200%
https://bugs.kde.org/show_bug.cgi?id=471001 Jakub changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Jakub --- *** This bug has been marked as a duplicate of bug 459161 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459161] Inconsistent cursor size on Wayland
https://bugs.kde.org/show_bug.cgi?id=459161 Jakub changed: What|Removed |Added CC||k...@paulmcauley.com --- Comment #8 from Jakub --- *** Bug 471001 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429211] Digital clock/whole panel sometimes stops updating until there is user interaction with Plasma
https://bugs.kde.org/show_bug.cgi?id=429211 Jakub changed: What|Removed |Added CC||jaburek.ja...@gmail.com --- Comment #13 from Jakub --- I started to experience a similar issue since a few days ago. The whole taskbar freezes after about an hour after starting the desktop session. No hover effects are displayed, the clock is frozen, opening new applications doesn’t show them in the taskbar and switching workspaces is not reflected on the taskbar. However, I can still click on the taskbar to open the application launcher, switch workspace, open calendar, etc. and it works. But unlike the original report, it does not unfreeze the taskbar, the only solution is to kquitapp5 plasmashell. SYSTEM INFORMATION: Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429211] [X11] Digital clock/whole panel sometimes stops updating until there is user interaction with Plasma
https://bugs.kde.org/show_bug.cgi?id=429211 Jakub changed: What|Removed |Added CC|jaburek.ja...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489851] New: Kwin crashes wehn dragging an app from Kickoff to desktop
https://bugs.kde.org/show_bug.cgi?id=489851 Bug ID: 489851 Summary: Kwin crashes wehn dragging an app from Kickoff to desktop Classification: Plasma Product: kwin Version: 6.1.2 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Wayland drag-and-drop for window content Assignee: kwin-bugs-n...@kde.org Reporter: jjaruszew...@outlook.com Target Milestone: --- SUMMARY: Kwin crashes when dragging a valid application from kickoff to desktop STEPS TO REPRODUCE 1. Drag any application from Kickoff to desktop OBSERVED RESULT EXPECTED RESULT Kwin Crashes SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-12650H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop N7601ZM_N7601ZM System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489851] Kwin crashes when dragging an app from Kickoff to desktop
https://bugs.kde.org/show_bug.cgi?id=489851 Jakub changed: What|Removed |Added Summary|Kwin crashes wehn dragging |Kwin crashes when dragging |an app from Kickoff to |an app from Kickoff to |desktop |desktop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489851] Kwin crashes when dragging an app from Kickoff to desktop
https://bugs.kde.org/show_bug.cgi?id=489851 --- Comment #1 from Jakub --- Created attachment 171446 --> https://bugs.kde.org/attachment.cgi?id=171446&action=edit Video of kwin crashing -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 466190] Audio notification sounds level initial default is 0%
https://bugs.kde.org/show_bug.cgi?id=466190 Jakub changed: What|Removed |Added CC||jjaruszew...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483932] Plasmashell segfaults in libfreetype.so.6 when adding plasmoid with custom font
https://bugs.kde.org/show_bug.cgi?id=483932 Jakub changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Jakub --- (In reply to Akseli Lahtinen from comment #1) > Hi, can you install debug symbols and send another backtrace? > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Backtraces > > You can also upload the backtrace files, see the "Add an attachment" link on > the site I tried to do it now, but I cannot reproduce it anymore, so I guess it works -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489811] Plasma shell crashes when dragging an application from application launcher to desktop on Wayland
https://bugs.kde.org/show_bug.cgi?id=489811 --- Comment #5 from Jakub --- (In reply to Akseli Lahtinen from comment #4) > I am unable to reproduce this, but I fixed similar-ish bug recently. See: > 484674 Yep, but here it crashes for valid desktop files too -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490456] New: Seo Content Lab Inżynieria treści agencja seo content lab Semantyczne Pozycjonowanie Stron Semantyczne SEO
https://bugs.kde.org/show_bug.cgi?id=490456 Bug ID: 490456 Summary: Seo Content Lab Inżynieria treści agencja seo content lab Semantyczne Pozycjonowanie Stron Semantyczne SEO Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: marta.szewc...@seocontentlab.pl Target Milestone: --- Seo Content Lab to agencja specjalizująca się w Inżynierii Treści i semantycznym SEO, która pomaga firmom osiągnąć lepsze pozycjonowanie w wynikach wyszukiwania. Dzięki głębokiemu zrozumieniu algorytmów wyszukiwarek, nasza firma opracowuje strategie content marketingu dostosowane do indywidualnych potrzeb każdego klienta. Specjalizujemy się w: Inżynieria Treści Strategie Contentowe Semantyczne Mapy Treści Mapy Topical Authority Budowa Autorytetu Strony Audyty Stron, Audyty Treści oraz Audyty Zaufania E.E.A.T. Ratowanie Stron i Blogów oraz Konsultowanie ich działań Szkoleniach SEO i Contentowe Semantyczne SEO Oferujemy szeroki zakres usług, w tym: Audyty zaufania E.E.A.T.: Analiza i optymalizacja czynników wpływających na wiarygodność i autorytet Twojej strony. Planowanie Treści - zaawansowane strategie contentowe Mapy semantyczne: Tworzenie szczegółowych map semantycznych, które wspierają strukturyzację treści zgodnie z zasadami semantycznego SEO. Optymalizacja treści: Dostosowywanie istniejących treści do wymogów SEO oraz tworzenie nowych, wartościowych tekstów. Strategie pozycjonowania: Opracowywanie skutecznych strategii mających na celu poprawę widoczności Twojej strony w wyszukiwarkach. Szkolenia SEO i Copywritingowe: Oferujemy szkolenia online dla twórców treści i właścicieli stron internetowych. Nasza agencja skupia się na dostarczaniu rozwiązań, które nie tylko zwiększają ruch na stronie, ale także przyczyniają się do budowania trwałej wartości dla marki online. Więcej informacji znajdziesz na naszej stronie: seocontentlab.pl -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490456] Seo Content Lab Inżynieria treści agencja seo content lab Semantyczne Pozycjonowanie Stron Semantyczne SEO
https://bugs.kde.org/show_bug.cgi?id=490456 Jakub changed: What|Removed |Added URL||https://seocontentlab.pl -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490456] Seo Content Lab Inżynieria treści agencja seo content lab Semantyczne Pozycjonowanie Stron Semantyczne SEO
https://bugs.kde.org/show_bug.cgi?id=490456 --- Comment #1 from Jakub --- Seo Content Lab to Agencja SEO i Marketingowa, w której skupiamy się na Inżynierii Treści i tym, jak treści mogą pomóc w rozwoju biznesu. Wszystkie działania zarówno naszych usług jak i szkoleń mają na celu zwiększenie ruchu i sprzedaży na Twojej Stronie Internetowej, a także wzmocnienie jej Autorytetu. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 356000] File removal that was performed by git rm cannot be committed from IDE
https://bugs.kde.org/show_bug.cgi?id=356000 Jakub changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Jakub --- works in 5.7.211203 (21.12.3) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Jakub changed: What|Removed |Added CC||kubek...@o2.pl --- Comment #12 from Jakub --- It would save a lot of time spent on redoing panels on external displays. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410883] New: Application not working at all.
https://bugs.kde.org/show_bug.cgi?id=410883 Bug ID: 410883 Summary: Application not working at all. Product: kdeconnect Version: unspecified Platform: Windows CE OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: ja...@kopanko.com Target Milestone: --- SUMMARY I downloaded kdeconnect-kde-master-108-windows-msvc2017_64-cl.exe artifact from KDE binary factory. When I try to run kdeconnect-indicator.exe the process is started and is visible in the process explorer, however no tray icon is shown and my phone says there are no available devices (can't connect by IP either). When I manually start kdeconnectd.exe manually my PC shows up in mobile application, however every pairing request times out. SOFTWARE/OS VERSIONS Windows: Version 10.0.17134 Compilation 17134 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422220] New: Layout issue when display scaling is set to 150%
https://bugs.kde.org/show_bug.cgi?id=40 Bug ID: 40 Summary: Layout issue when display scaling is set to 150% Product: yakuake Version: 3.0.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: jakubmadej.pl+...@gmail.com Target Milestone: --- Created attachment 128900 --> https://bugs.kde.org/attachment.cgi?id=128900&action=edit Screenshot 1 Strange horizontal line is rendered if my display uses scaling (150% in my case). This does not happen if I don't use scaling. STEPS TO REPRODUCE 1. Turn on display scaling 150% 2. Turn on drop down console 3. Press enter few times OBSERVED RESULT Horizontal line (transparency 0%) show up (every 2nd line) EXPECTED RESULT There is no change in background transparency SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422220] Layout issue when display scaling is set to 150%
https://bugs.kde.org/show_bug.cgi?id=40 --- Comment #1 from Jakub --- Created attachment 128901 --> https://bugs.kde.org/attachment.cgi?id=128901&action=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422220] Layout issue when display scaling is set to 150%
https://bugs.kde.org/show_bug.cgi?id=40 --- Comment #2 from Jakub --- Display resolution is 2560x1440 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418996] New: Dark Telegram icon on dark Breeze theme
https://bugs.kde.org/show_bug.cgi?id=418996 Bug ID: 418996 Summary: Dark Telegram icon on dark Breeze theme Product: Breeze Version: 5.18.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: jakubmadej.pl+...@gmail.com CC: kain...@gmail.com Target Milestone: --- SUMMARY Dark icon in system tray on Breeze Dark theme in KDE Plasma STEPS TO REPRODUCE 1. Open Telegram Desktop OBSERVED RESULT A dark icon appears in the system tray EXPECTED RESULT The icon should be light in the system tray SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux (available in About System) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418996] Dark Telegram icon on dark Breeze theme
https://bugs.kde.org/show_bug.cgi?id=418996 --- Comment #1 from Jakub --- Created attachment 126877 --> https://bugs.kde.org/attachment.cgi?id=126877&action=edit Screenshot Telegram icon hard to see -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419452] New: Okular does not display some Unicode characters
https://bugs.kde.org/show_bug.cgi?id=419452 Bug ID: 419452 Summary: Okular does not display some Unicode characters Product: okular Version: 1.9.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: jakubmadej.pl+...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open a PDF containing Unicode Character “ż” (U+017C) in Okular OBSERVED RESULT Okular can't display such character, there is blank space where the character is supposed to be displayed. EXPECTED RESULT All characters are displayed correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Other viewer, like Evince (or Chrome built in viewer) do not have this problem and all characters are displayed correctly. I've also analyzed used fonts (File->Properties->Fonts) with Plasma font viewer and all those fonts contain needed characters. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419452] Okular does not display some Unicode characters
https://bugs.kde.org/show_bug.cgi?id=419452 --- Comment #3 from Jakub --- Created attachment 127137 --> https://bugs.kde.org/attachment.cgi?id=127137&action=edit Example PDF Look for "WYPOSAŻENIE (2015.03-2015.07)" (middle of 1st page) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419452] Okular does not display some Unicode characters
https://bugs.kde.org/show_bug.cgi?id=419452 --- Comment #4 from Jakub --- Created attachment 127138 --> https://bugs.kde.org/attachment.cgi?id=127138&action=edit Screenshot from Okular This screenshot shows how Okular is displaying PDFs -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419452] Okular does not display some Unicode characters
https://bugs.kde.org/show_bug.cgi?id=419452 --- Comment #6 from Jakub --- Created attachment 127141 --> https://bugs.kde.org/attachment.cgi?id=127141&action=edit Okular properties -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419452] Okular does not display some Unicode characters
https://bugs.kde.org/show_bug.cgi?id=419452 --- Comment #7 from Jakub --- I have https://aur.archlinux.org/packages/ttf-ms-fonts/ installed, but I'm not sure if Okular is picking anything from that package (see attached "properties" screenshot). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419452] Okular does not display some Unicode characters
https://bugs.kde.org/show_bug.cgi?id=419452 --- Comment #9 from Jakub --- I have liberation fonts already installed (ttf-liberation-2.1.0-1) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419452] Okular does not display some Unicode characters
https://bugs.kde.org/show_bug.cgi?id=419452 Jakub changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #11 from Jakub --- I've installed ttf-vista-fonts package (containing Calibri) but it didn't help. Anyway - why would I need additional fonts while Evince is displaying everything just fine? -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 397061] New: Skrooge 2.14 crashes when I try to open transactions
https://bugs.kde.org/show_bug.cgi?id=397061 Bug ID: 397061 Summary: Skrooge 2.14 crashes when I try to open transactions Product: skrooge Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: fiilo...@gmail.com CC: steph...@mankowski.fr Target Milestone: --- It happens always when I try to open the transactions view for all accounts. I am able to open transactions from a specific account (e.g., via Accounts view) but any time I try to click "Transactions" or choose "All accounts" from transactions view menu, it crashes immediately. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 391690] New: Skrooge requires sqlcipher, but not found
https://bugs.kde.org/show_bug.cgi?id=391690 Bug ID: 391690 Summary: Skrooge requires sqlcipher, but not found Product: Craft Version: unspecified Platform: Windows CE OS: Windows CE Status: UNCONFIRMED Severity: normal Priority: NOR Component: Blueprints Assignee: vonr...@kde.org Reporter: fiilo...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- I try to install Skrooge on Windows 10. Craft warned that it needs some packages, but up until now I could find them and install separately, e.g. pkg-config, kdesignerplugin. Now it demands sqlcipher but it isn't available and I don't know how to add it manually (or it's possible at all). Reproducible: Always Steps to Reproduce: 1. craft skrooge Results: [...] -- Found PkgConfig: C:/CraftRoot/dev-utils/bin/pkg-config.exe (found version "0.28") -- Checking for module 'sqlcipher' -- Package sqlcipher was not found in the pkg-config search path. Perhaps you should add the directory containing `sqlcipher.pc' to the PKG_CONFIG_PATH environment variable Package 'sqlcipher', required by 'world', not found CMake Error at C:/CraftRoot/dev-utils/cmake/share/cmake-3.10/Modules/FindPkgConfig.cmake:415 (message): A required package was not found Call Stack (most recent call first): C:/CraftRoot/dev-utils/cmake/share/cmake-3.10/Modules/FindPkgConfig.cmake:593 (_pkg_check_modules_internal) CMakeLists.txt:90 (PKG_CHECK_MODULES) [...] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Jakub changed: What|Removed |Added CC|jakub...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447845] Under Wayland, XWayland web apps have incorrect icon
https://bugs.kde.org/show_bug.cgi?id=447845 Jakub changed: What|Removed |Added CC||jakub.kr...@email.cz --- Comment #15 from Jakub --- This issue just started happening for me again a few days ago (after applying updates). Fedora 41 & KDE Plasma 6.3. I first hit the issue some time last year (I think?) when I finally switched from X11 to Wayland. At that time I was able to resolve it by setting the #ozone-platform-hint to "Auto". Now it started again, and the #ozone-platform-hint setting doesn't help anymore. I double checked it was still set to "Auto", also tried changing it to "Wayland", but no joy. Whenever I start any Chromium app, it briefly shows its own icon in the tray before it changes to the default chromium icon a second later. It stays separate from the main Chromium icon initially until it gets grouped with it eventually (e.g. as soon as I launch any other app via a pinned icon). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it
https://bugs.kde.org/show_bug.cgi?id=364915 Jakub Gocoł changed: What|Removed |Added CC||jakub.go...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372280] New: Automatically generated virtual methods always use C++11 'override' keyword
https://bugs.kde.org/show_bug.cgi?id=372280 Bug ID: 372280 Summary: Automatically generated virtual methods always use C++11 'override' keyword Product: kdevelop Version: 5.0.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: sja...@gmail.com Target Milestone: --- In 5.x version, generating method declaration using ctrl+space ALWAYS adds 'override' at the end. I don't use c++11 mode, so this does not compile. In the projects settings, in "language support" I have C++03 selected. This is NOT C++03! Also, when generating declarations/definitions like that, new kdevelop ALWAYS adds full namespaces - including inside the class declaration, or in the implementation file even when "using namespace" is used. Both of these are incredibly annoying! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372552] New: More than one target in Build Sequence doesn't build anything
https://bugs.kde.org/show_bug.cgi?id=372552 Bug ID: 372552 Summary: More than one target in Build Sequence doesn't build anything Product: kdevelop Version: 5.0.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Build tools: CMake Assignee: kdevelop-bugs-n...@kde.org Reporter: sja...@gmail.com Target Milestone: --- Build sequence seems to be broken. When I add a single target (TargetA) to it and press F8, it builds that target. When I add another one (TargetB) and press F8, all I get in the message window is: project/path/build> make -j4 TargetB ** Killed process ** And it doesn't even try to build TargetA before. As soon as I remove either target from the list (doesn't matter which one), it starts to build the remaining target again. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372552] More than one target in Build Sequence doesn't build anything
https://bugs.kde.org/show_bug.cgi?id=372552 Jakub Schmidtke changed: What|Removed |Added CC||sja...@gmail.com --- Comment #4 from Jakub Schmidtke --- But I'm pretty sure it worked fine in kdevelop 4.7.3 and below... Each target would get built, in order, until something failed or all were finished. As a side question, 'F4' key used to jump to the next search result, build problem, etc. Now it only works when I do a global search (Ctrl-Alt-F). When I run a build and something fails, F4 doesn't do anything. Is it expected, am I doing something wrong, or is it a bug (and I should open a separate one)? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 362664] Switching screen in middle of password typing
https://bugs.kde.org/show_bug.cgi?id=362664 Jakub Gocoł changed: What|Removed |Added CC||jakub.go...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372963] plasmashell does not handle changes of the primary screen
https://bugs.kde.org/show_bug.cgi?id=372963 Jakub Gocoł changed: What|Removed |Added CC||jakub.go...@gmail.com --- Comment #11 from Jakub Gocoł --- I think this patch https://phabricator.kde.org/D3519 will fix your problem. I hope it will be merged soon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372963] plasmashell does not handle changes of the primary screen
https://bugs.kde.org/show_bug.cgi?id=372963 --- Comment #13 from Jakub Gocoł --- Try to reproduce and then describe simple scenarios in as few steps as possible. Because you described so many scenarios, I don't understand what exactly works and what doesn't work. 1. In first message, in point 1, you described scenario with change of primary screen. Did my patch resolved that issue for you? 2. Can you provide exact steps to crash plasma? I don't understand what exactly do you do. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403791] Replace all passivenotification messages with InlineMessages
https://bugs.kde.org/show_bug.cgi?id=403791 Jakub Narolewski changed: What|Removed |Added CC||izow...@gmail.com --- Comment #10 from Jakub Narolewski --- Is this up for grabs? Looking at: https://tinyurl.com/plasma-15-minute-bugs this is first on the list, assigned to ad...@leinir.dk but the work here seems stale with one commit from mid 2019 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] New: Periodic black screens on main monitor after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 Bug ID: 465712 Summary: Periodic black screens on main monitor after upgrade to 5.27 Classification: Plasma Product: kwin Version: 5.27.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: izow...@gmail.com Target Milestone: --- SUMMARY I have just upgraded my openSUSE installation and I hit a weird issue. I'm getting periodic black screen flashes at random'ish intervals and sometimes when interacting with Plasma elements. It happens only on my main screen - secondary seems to be fine. I do not see any errors in journalctl nor in dmesg that could be connected to it. STEPS TO REPRODUCE 1. Log in to the Plasma Desktop 2. Patiently observe the main monitor or click some stuff OBSERVED RESULT Main monitor flashes black. EXPECTED RESULT Main monitor works properly. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230213 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B78 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 Jakub Narolewski changed: What|Removed |Added Summary|Periodic black screens on |Periodic black screens on |main monitor after upgrade |main monitor with 144Hz |to 5.27 |refresh rate after upgrade ||to 5.27 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #1 from Jakub Narolewski --- It seemed to stop when I switched my main screen to the 60Hz - the same refresh rate as my secondary screen - it was set to the 144Hz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #2 from Jakub Narolewski --- Happens also inside the Wayland session. I can confirm that the monitor itself works fine under Windows 11 with refresh rate set to 144Hz. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #3 from Jakub Narolewski --- I observe no flashes when I switch off my secondary display and switch main one to the 144Hz - so it works fine in single monitor mode. What is interesting the flashes are there even on the SDDM screen, as soon as I boot my system. SDDM seems to force some higher refresh rate by default. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 Jakub Narolewski changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Jakub Narolewski --- (In reply to David Edmundson from comment #4) > - Was this definitely a non-issue on older Plasma? > Yes. I was using 5.26 for very long time without issues. > - Does this happen if you run a different (non-compositor) window manager. > Can you run "openbox --replace" and see if goes away. That will show if the > issue might be lower in the stack. > Will check this soon. > - Can you run "kscreen-doctor --monitor" and rerproduce some flickering, to > check if we're reconfiguring the monitor constantly > Is --monitor a valid flag for kscreen-doctor? I get `Unknown option 'monitor'` and --help is not listing it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #6 from Jakub Narolewski --- (In reply to David Edmundson from comment #4) > - Can you run "kscreen-doctor --monitor" and rerproduce some flickering, to > check if we're reconfiguring the monitor constantly To be also perfectly clear as how it looks like as I think that "flickering" undersells it a bit :P https://streamable.com/onjidu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 Jakub Narolewski changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #7 from Jakub Narolewski --- (In reply to David Edmundson from comment #4) > - Can you run "kscreen-doctor --monitor" and rerproduce some flickering, to > check if we're reconfiguring the monitor constantly I guess it should be "kscreen-console monitor". No, when this occurs no new stuff is printed by it. But! The flash occurs every single time I launch and close kscreen-console in terminal when monitor is set to 144Hz - will attach a link do video soon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444953] Dolphin cannot move file to trash if filename is too long: Clearer inline error message
https://bugs.kde.org/show_bug.cgi?id=444953 Jakub Kuczys changed: What|Removed |Added CC||m...@jacken.men --- Comment #1 from Jakub Kuczys --- I would like to suggest that this should be treated as a bug rather than a wishlist request. The FreeDesktop.org Trash specification explicitly doesn't require that the filename of the file in the Trash folder stays the same as info about the original name should instead be conveyed by the `Path` field in the `.trashinfo` file. This is how, for example, trash-cli behaves - it truncates the filename if it's too long (and adds a suffix if necessary though that's probably already handled by Dolphin since it's needed when a file with the same name gets deleted multiple times). [1] https://github.com/andreafrancia/trash-cli/blob/402999357ce32c0dfc945bcc161c020355950eb6/trashcli/put/info_dir.py#L19-L59 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #8 from Jakub Narolewski --- Using snapper I have booted a snapshot from before the upgrade. Now I'm at: Operating System: openSUSE Tumbleweed 20230209 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B78 System Version: 1.0 And the problem went away. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #9 from Jakub Narolewski --- (In reply to David Edmundson from comment #4) > - Does this happen if you run a different (non-compositor) window manager. > Can you run "openbox --replace" and see if goes away. That will show if the > issue might be lower in the stack. It also happens with openbox. This video shows behavior of kscreen-console for 60 and 144Hz. You can see the same flashes every time the kscreen-console is launched or closed while monitor is set to 144Hz: https://streamable.com/p0tzlx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #10 from Jakub Narolewski --- kscreen-console is using libkscreen to slurp the screen config from the system and I see quite a bit of changes there lately: https://invent.kde.org/plasma/libkscreen/-/commits/v5.27.0 I wonder if the way forward would be to bisect it and check if something there influences it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #13 from Jakub Narolewski --- (In reply to Liam Dawe from comment #12) > I just upgraded Fedora 37, and I am seeing this exact issue. Driving me > insane. > > This is on Plasma 5.26.5 so it's not just on 5.27 that this happens. > > I can confirm disabling my 60Hz monitor and sticking to my 180Hz monitor > solves it, but obviously that's not an actual fix. F37 is now on KDE Frameworks 5.103.0? I think that libkscreen / kscreen are packaged in it and in my case, apart from plasma 5.26.5 -> 5.27.0, frameworks were updated to 5.103 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712
--- Comment #16 from Jakub Narolewski ---
This is somehow connected to the VRR / Adaptive-Sync / G-Sync. The problem went
away when I disabled Adaptive-Sync in the OSD of my main monitor. For the
record, it identifies as: Electronics-LG ULTRAGEAR-107NTZN7V189
I also see, that kscreen-console reports:
{
"enabled": true,
"id": "c5319b8612a23fdfa95b46e53bc99d79",
"metadata": {
"fullname": "xrandr-LG Electronics-LG ULTRAGEAR-107NTZN7V189",
"name": "DP-2"
},
"mode": {
"refresh": 143.97325134277344,
"size": {
"height": 1440,
"width": 2560
}
},
"overscan": 0,
"pos": {
"x": 0,
"y": 0
},
"priority": 1,
"rgbrange": 0,
"rotation": 1,
"scale": 1,
"vrrpolicy": 2
}
with vrrpolicy set to 2 - which if I understand it - means "Automatic". Is
there some way to force it to 0?
--
You are receiving this mail because:
You are watching all bug changes.
