[plasmashell] [Bug 445236] All Qt5 applications have their font sizes way bigger than they are supposed to be in an X11 session in Plasma 5.23.3-1. This affects all components and I am not sure what c
https://bugs.kde.org/show_bug.cgi?id=445236 Antonio Rojas changed: What|Removed |Added CC||nishith.kha...@gmail.com --- Comment #3 from Antonio Rojas --- *** Bug 445252 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445252] Some elements have scaled up when updating from 5.23.2 to 5.23.3
https://bugs.kde.org/show_bug.cgi?id=445252 Antonio Rojas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 445236 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445252] Some elements have scaled up when updating from 5.23.2 to 5.23.3
https://bugs.kde.org/show_bug.cgi?id=445252 --- Comment #2 from Nishith Khanna --- Created attachment 143397 --> https://bugs.kde.org/attachment.cgi?id=143397=edit Dolphin which looks normal and not scaled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445252] Some elements have scaled up when updating from 5.23.2 to 5.23.3
https://bugs.kde.org/show_bug.cgi?id=445252 --- Comment #1 from Nishith Khanna --- Created attachment 143396 --> https://bugs.kde.org/attachment.cgi?id=143396=edit My display settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445252] Some elements have scaled up when updating from 5.23.2 to 5.23.3
https://bugs.kde.org/show_bug.cgi?id=445252 Nishith Khanna changed: What|Removed |Added Component|Edit Mode toolbar |Application Launcher ||(Kickoff) Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk CC||mikel5...@gmail.com, ||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445252] New: Some elements have scaled up when updating from 5.23.2 to 5.23.3
https://bugs.kde.org/show_bug.cgi?id=445252 Bug ID: 445252 Summary: Some elements have scaled up when updating from 5.23.2 to 5.23.3 Product: plasmashell Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Edit Mode toolbar Assignee: plasma-b...@kde.org Reporter: nishith.kha...@gmail.com CC: n...@kde.org Target Milestone: 1.0 Created attachment 143395 --> https://bugs.kde.org/attachment.cgi?id=143395=edit Screenshot of kicker I don't know it is very hard to explain but some elements on my desktop like edit mode toolbar, kicker and login logout screen have become very big. And to make it more strange rest of the stuff is fine like Firefox and Dolphin. This started happening when I got an upgrade from 5.23.2 to 5.23.3. I rebooted twice but it didn't fix the issue. Some info regarding my setup I have dual monitor setup. 1. Laptop Screen (disabled) 2. Monitor connected via HDMI Monitor is the only enabled screen. I enabled laptop screen and it had the same issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445251] New: Every since upgrading to 5.23, wobbly windows, alt-tab preview, clicking on grouped icons to show them all, (and other stuff) crash and stop working
https://bugs.kde.org/show_bug.cgi?id=445251 Bug ID: 445251 Summary: Every since upgrading to 5.23, wobbly windows, alt-tab preview, clicking on grouped icons to show them all, (and other stuff) crash and stop working Product: plasmashell Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: eliyahushap...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 143394 --> https://bugs.kde.org/attachment.cgi?id=143394=edit coredump without symbols (I understand that arch does not have a debug version) SUMMARY Wobbly windows is a great feature that makes it so the windows wobble when being moved. I didn't upgrade my system for a few months (so I guess I had 5.22) and recently upgraded to 5.23. Unfortunately ever since then wobbly windows, alt-tab preview, clicking on grouped icons to show them all stop working. There are other annoyances such as pixels randomly turning off when they are showing a moving GUI (move my mouse over the right click menu, press enter on the shell moving the line of text up one row). However, I cannot reproduce that as easily so I guess I shouldn't open bug reports for them STEPS TO REPRODUCE 0. Assume that you have wobbly windows selected already 1. System Settings -> Display and Monitor -> Compositor -> Enable compositor on startup 2. Enjoy wobbly windows (and alt-tab and grouping visual stuff) 3. Press alt tab a few times (I must have a few windows opened and covering each other) 4. Crash 5. No wobbly windows (and alt-tab and grouping visual stuff) OBSERVED RESULT Windows move in a boring Microsoft way EXPECTED RESULT Cool wobbles when the windows move SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.16-arch1-1 KDE Plasma Version: 5.23 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This is easily reproducible. I can make a video of it or other stuff if needed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445250] New: Resize Dialog: Focus should be on pixel dimensions 'Width' field by default
https://bugs.kde.org/show_bug.cgi?id=445250 Bug ID: 445250 Summary: Resize Dialog: Focus should be on pixel dimensions 'Width' field by default Product: krita Version: 4.4.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: jantho...@janthomae.de Target Milestone: --- SUMMARY When you try to resize an image using 'Image' -> 'Scale Image To New Size' by default the focus is on the OK button. This means to enter the new size you either need to click the 'Width' field with the mouse or need to press TAB key three times to select the 'Width' field. When resizing images with this dialog in the overwhelming majority of cases you will want to change the pixel size so it would be nice if the 'Width' field would have focus by default. This would work a lot nicer with a keyboard-focused workflow: Press Ctrl+Alt+I, enter the new dimension, press Enter -> Done. STEPS TO REPRODUCE 1. Open any image. 2. In the menu select 'Image' -> 'Scale Image To New Size' or press Ctrl+Alt+I 3. Resize dialog opens. OBSERVED RESULT The 'OK' button has focus by default. EXPECTED RESULT The 'Width' field in the 'Pixel Dimension' section has focus by default. SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366063] Window switcher does not start with specific key combination
https://bugs.kde.org/show_bug.cgi?id=366063 kde@grau.net changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445249] New: Akonadi crash after unplugging Thunderbolt dock with attached monitor on Wayland
https://bugs.kde.org/show_bug.cgi?id=445249
Bug ID: 445249
Summary: Akonadi crash after unplugging Thunderbolt dock with
attached monitor on Wayland
Product: Akonadi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: philipp.reichm...@gmail.com
Target Milestone: ---
Application: akonadiserver (5.18.3 (21.08.3))
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Unplugged my Thunderbolt dock, which has a monitor attached via DisplayPort, in
order to fix an issue where the monitor would not go to the resolution I
selected in System Settings.
- Unusual behavior I noticed:
The Wayland session was behaving strangely prior to unplugging.
The monitor is capable of 3840x2160 resolution and has supported this
resolution in KWin Wayland in the past. I can see and select this resolution in
System Settings.
Since this morning (with no user changes to my KDE configuration or packages),
the monitor comes up with 2560x1440. I can set it to 3840x2160 in System
Settings. However, when I apply the settings, the monitor will go to 2560x1440
anyway (as confirmed by the monitor's HUD), and when I enter System Settings
again, I see it again at 2560x1440.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 std::default_delete::operator() (__ptr=0x111,
this=) at /usr/include/c++/11/bits/unique_ptr.h:79
#7 std::unique_ptr >::~unique_ptr
(this=, this=) at
/usr/include/c++/11/bits/unique_ptr.h:361
#8 __gnu_cxx::new_allocator >
>::destroy > > (__p=,
this=) at /usr/include/c++/11/ext/new_allocator.h:168
#9
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at /usr/include/c++/11/bits/alloc_traits.h:531
#10 std::vector >,
std::allocator > > >::_M_erase
(__position=std::unique_ptr = {get() = {}}, this=) at /usr/include/c++/11/bits/vector.tcc:177
#11 std::vector >,
std::allocator > > >::erase
(__position=std::unique_ptr = {get() = {}}, this=) at /usr/include/c++/11/bits/stl_vector.h:1431
#12 Akonadi::Server::AkonadiServer::connectionDisconnected (this=) at
/usr/src/debug/akonadi-server-21.08.3-1.1.x86_64/src/server/akonadi.cpp:234
#13 0x7fd6f95f8fee in QObject::event (this=0x7ffe83590c90,
e=0x7fd6a4005970) at kernel/qobject.cpp:1314
#14 0x7fd6f95cc9cf in doNotify (event=0x7fd6a4005970,
receiver=0x7ffe83590c90) at kernel/qcoreapplication.cpp:1154
#15 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1140
#16 QCoreApplication::notifyInternal2 (receiver=0x7ffe83590c90,
event=0x7fd6a4005970) at kernel/qcoreapplication.cpp:1064
#17 0x7fd6f95cfa47 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55eb0afff980) at
kernel/qcoreapplication.cpp:1821
#18 0x7fd6f9624853 in postEventSourceDispatch (s=s@entry=0x55eb0b03da30) at
kernel/qeventdispatcher_glib.cpp:277
#19 0x7fd6f7852d4f in g_main_dispatch (context=0x55eb0b03d4d0) at
../glib/gmain.c:3381
#20 g_main_context_dispatch (context=0x55eb0b03d4d0) at ../glib/gmain.c:4099
#21 0x7fd6f78530d8 in g_main_context_iterate
(context=context@entry=0x55eb0b03d4d0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#22 0x7fd6f785318f in g_main_context_iteration (context=0x55eb0b03d4d0,
may_block=1) at ../glib/gmain.c:4240
#23 0x7fd6f9623ed4 in QEventDispatcherGlib::processEvents
(this=0x55eb0b03cbf0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x7fd6f95cb3fb in QEventLoop::exec (this=this@entry=0x7ffe83590ad0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#25 0x7fd6f95d36e0 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#26 0x55eb08ff7559 in AkApplicationBase::exec (this=0x7ffe83590c60) at
/usr/src/debug/akonadi-server-21.08.3-1.1.x86_64/src/shared/akapplication.cpp:107
#27 main (argc=, argv=) at
/usr/src/debug/akonadi-server-21.08.3-1.1.x86_64/src/server/main.cpp:65
[Inferior 1 (process 3075) detached]
The reporter indicates this bug may be a duplicate of or related to bug 442147.
Possible duplicates by query: bug 444916, bug 444909, bug 444534, bug 46,
bug 21.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 445241] My zoom feature isn't working properly.
https://bugs.kde.org/show_bug.cgi?id=445241 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Halla Rempt --- Sorry, but it's impossible to do anything with a report like this. Please read https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html to learn how to report bugs, or go to a user forum to ask for help: https://krita-artists.org. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole
https://bugs.kde.org/show_bug.cgi?id=378152 Jiri Slaby changed: What|Removed |Added Version|19.04.2 |21.08.2 CC||jirisl...@gmail.com --- Comment #3 from Jiri Slaby --- Still happens. For me on openSUSE with 21.08.2. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 444167] Not asking for openvpn private key password
https://bugs.kde.org/show_bug.cgi?id=444167 Jan Grulich changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Jan Grulich --- *** This bug has been marked as a duplicate of bug 444882 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 444882] Unable to connect to OpenVPN server with passphrase secured .p12 certificate
https://bugs.kde.org/show_bug.cgi?id=444882 Jan Grulich changed: What|Removed |Added CC||i...@markus-pister.de --- Comment #7 from Jan Grulich --- *** Bug 444167 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 444167] Not asking for openvpn private key password
https://bugs.kde.org/show_bug.cgi?id=444167 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #4 from Jan Grulich --- Hi, this should be (hopefully) fixed in Plasma 5.23.3 with https://invent.kde.org/plasma/plasma-nm/-/commit/48fad4ac77520d673414ef957e6dedc4d151eb73. Can you verify? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 445248] Using kirigami_package_breeze_icons on Windows results in failed INSTALL due to symlink to duplicate icons
https://bugs.kde.org/show_bug.cgi?id=445248 Javier O. Cordero Pérez (Cuperino) changed: What|Removed |Added Summary|Using |Using |kirigami_package_breeze_ico |kirigami_package_breeze_ico |ns on Windows results in|ns on Windows results in |failed INSTALL due to |failed INSTALL due to |symlink to duplicates |symlink to duplicate icons -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 445248] New: Using kirigami_package_breeze_icons on Windows results in failed INSTALL due to symlink to duplicates
https://bugs.kde.org/show_bug.cgi?id=445248 Bug ID: 445248 Summary: Using kirigami_package_breeze_icons on Windows results in failed INSTALL due to symlink to duplicates Product: frameworks-kirigami Version: 5.83.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: javiercorderope...@gmail.com Target Milestone: Not decided SUMMARY Using the `kirigami_package_breeze_icons` CMake instruction on Windows results in INSTALL failing due to some icons being found duplicate by CMake while reading symlink. Some of the conflicting icons include: > go-next-symbolic, go-previous-symbolic, format-fill-color Not listing some icons as part of `kirigami_package_breeze_icons`, such as the "format-fill-color" icon, will result in the conflict going away. Nevertheless, other icons, such as go-next-symbolic, create the conflict even if they are not listed to be imported. This results in an inability to use `kirigami_package_breeze_icons` on Windows. `kirigami_package_breeze_icons` continues to work fine for the macOS and Android platforms. STEPS TO REPRODUCE 1. Create a Kirigami project 2. Add `kirigami_package_breeze_icons` call to the `CMakeLists.txt` file where resources are added. 3. Build and install the project on Windows. (I'm using Craft to build the project on Windows. There, updating the package is enough to trigger the error because it occurs during CMake's install phase.) OBSERVED RESULT CMake fails to complete INSTALL due to being unable to read symlink because some icons were duplicated. Some of the duplicate icons are not listed by `kirigami_package_breeze_icons` thus making the conflict apparently impossible to avoid. >CMake Error at build/cmake_install.cmake:153 (file): > file INSTALL cannot read symlink > > "C:/CraftRoot/build/_/e31ae30d/build/breeze-icons/src/breeze-icons/icons/actions/22/format-fill-color.svg" > to duplicate at > > "C:/CraftRoot/build/entity/project/image-RelWithDebInfo-main/CraftRoot/qml/org/kde/kirigami.2/icons/format-fill-color.svg": > File exists. >Call Stack (most recent call first): > cmake_install.cmake:37 (include) EXPECTED RESULT Windows build completes INSTALL and shows appropriate icons when ran. SOFTWARE/OS VERSIONS Windows: Windows 10 KDE Frameworks Version: 5.83 - 5.87 Qt Version: 5.15 kde patched ADDITIONAL INFORMATION Here are the links to the Craft repository and project I'm attempting to build with `kirigami_package_breeze_icons`: https://github.com/Cuperino/craft-blueprints-qprompt https://github.com/Cuperino/QPrompt -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 445239] Scrolling changes contents of dropdowns etc. even when it shouldn't
https://bugs.kde.org/show_bug.cgi?id=445239 Thomas Surrel changed: What|Removed |Added CC||thomas.sur...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445247] New: Plasmashell crashes when unmounting a mounted USB.
https://bugs.kde.org/show_bug.cgi?id=445247 Bug ID: 445247 Summary: Plasmashell crashes when unmounting a mounted USB. Product: plasmashell Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Disks & Devices Assignee: plasma-b...@kde.org Reporter: samping...@gmail.com Target Milestone: 1.0 SUMMARY Plasmashell crashes when I unmount a USB by using "Safely Remove" option from System Tray applet. STEPS TO REPRODUCE 1. Insert a USB and mount it. 2. Unmount the mounted USB by clicking on "Safely Remove" option in System Tray applet. 3. See the plasmashell crash and restart itself. OBSERVED RESULT When I unmount a mounted USB, the systray applet shows that the USB has been safely removed and then crashes and replaces itself. Plasmashell doesnt crash after unmounting the USB sometimes, so by doing it repeatedly, this issue would appear. EXPECTED RESULT Unmounting a USB shouldn't result in a plasmashell crash. SOFTWARE/OS VERSIONS OS, Kernel: Arch Linux (all up-to-date), linux-tkg-pds-5.15.0-214 & linux-zen-5.14 (changing kernel doesn't make any difference) KDE Plasma: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION GPU: NVIDIA GeForce GTX 1060 6GB Driver: NVIDIA Proprietary Driver 495.44 Here is a video of this issue:- https://youtu.be/WfIZxLBrRLE -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444365] KDE 5.23.1 - KLIPPER - Actions truncate contents of clipboard
https://bugs.kde.org/show_bug.cgi?id=444365 --- Comment #1 from kurtsjunk...@outlook.com --- I wonder if this is an unintentional by product of the following fix: https://invent.kde.org/plasma/plasma-workspace/-/commit/f9669af2cfa6afdf6567ded5159c45ea8ab6c947 To fix bug https://bugs.kde.org/show_bug.cgi?id=431673 -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 445139] Skanpage coredump
https://bugs.kde.org/show_bug.cgi?id=445139 --- Comment #6 from Kåre Särs --- Thanks for the trace... Strange that Skanlite works, but Skanpage crashes The backtrace shows that the actual crash is in the net backend in sane... The reason why it crashes is still a bit unclear... Could you install also the debug symbols for libsane (libsane-dbg) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445246] New: Feature Request: Please add mobile hotspot support in windows 10
https://bugs.kde.org/show_bug.cgi?id=445246 Bug ID: 445246 Summary: Feature Request: Please add mobile hotspot support in windows 10 Product: kdeconnect Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: avichal1...@icloud.com Target Milestone: --- SUMMARY Feature Request: Please add mobile hotspot support in windows 10 STEPS TO REPRODUCE 1. Pair android device and windows 10 via kdeconnect 2. Turn on mobile hotspot in android. 3. Try to pair it via hotspot but it doesn't work OBSERVED RESULT It gets disconnected and no more devices show on adroid and Windows. It tells me to connect to wifi on android. Connecting with hotspot ip doesn't work either EXPECTED RESULT It should work perfectly fine just like it does with wifi because they are technically on the same network SOFTWARE/OS VERSIONS Windows: Edition Windows 10 Pro Version 21H1 Installed on16-02-2021 OS build19043.1288 Experience Windows Feature Experience Pack 120.2212.3920.0 ADDITIONAL INFORMATION Please add this feature. Your app will grow considerably in popularity. I downloaded it from the ms store and there were at least 10-30 comments there asking for this feature as well. i myself rated it a 3.5/5 on the microsoft store just because of lack of hotspot functionality. I will rate it a 5/5 if this feature gets added. If it loks like an issue just for me, please provide me with further guidance on how to enable this functionality if it already exists. Thanks! any response is greatly appreciated! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445105] Some shortcuts doesn't work when using Arabic keyboard layout.
https://bugs.kde.org/show_bug.cgi?id=445105 --- Comment #2 from Wissam --- (In reply to Nate Graham from comment #1) > If the issue affects non-KDE apps on X11, then it isn't a KDE bug, as no KDE > code is involved in handling keyboard events there. It could be in xkb or > another layer of the input stack. I'd suggest starting in XKB. But it works just fine in other desktop enviroments on the same laptop ( I have had this problem on multiple laptops and multiple distros as I said) and it affects kde apps like kate too. just to be sure, I just tried it in linux mint cinnamon edition and it works just fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445245] New: Plasma shell very laggy and glitchy in Wayland
https://bugs.kde.org/show_bug.cgi?id=445245 Bug ID: 445245 Summary: Plasma shell very laggy and glitchy in Wayland Product: plasmashell Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: generic-performance Assignee: plasma-b...@kde.org Reporter: d...@rhoatech.com Target Milestone: 1.0 SUMMARY Under Wayland Plasma Shell is extremely laggy, despite applications feel rather snappy. There are a number of graphical issues as well such as firefox disappearing and reappearing. STEPS TO REPRODUCE 1. Run Plasma shell in Wayland 2. Attempt to open the launcher 3. OBSERVED RESULT Takes anywhere from 10-30 seconds to show the menu EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 ADDITIONAL INFORMATION egl-wayland 1:1.1.9+2+gdaab854-1 kdeplasma-addons 5.23.3-1 kscreen 5.23.3-1 kscreenlocker 5.23.3-1 kwayland 5.87.0-1 kwayland-integration 5.23.3-1 kwayland-server 5.23.3-1 lib32-nvidia-utils 495.44-1 lib32-wayland 1.19.0-2 libkscreen 5.23.3-1 nvidia-dkms 495.44-3 nvidia-settings 495.44-1 nvidia-utils 495.44-3 plasma-browser-integration 5.23.3-1 plasma-desktop 5.23.3-1 plasma-disks 5.23.3-1 plasma-firewall 5.23.3-1 plasma-framework 5.87.0-1 plasma-integration 5.23.3-1 plasma-nm 5.23.3-1 plasma-pa 5.23.3-1 plasma-sdk 5.23.3-1 plasma-systemmonitor 5.23.3-1 plasma-thunderbolt 5.23.3-1 plasma-vault 5.23.3-1 plasma-wayland-session 5.23.3-1 plasma-workspace 5.23.3-1 plasma-workspace-wallpapers 5.23.3-1 qt5-wayland 5.15.2+kde+r36-1 wayland 1.19.0-2 wayland-protocols 1.23-1 wayland-utils 1.0.0-2 xorg-xwayland 21.1.3-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441367] Add an onboarding/"what's new?" app/widget/view/thing
https://bugs.kde.org/show_bug.cgi?id=441367 johnathan changed: What|Removed |Added CC||testing1237...@yahoo.com --- Comment #2 from johnathan --- i would add my inputs. Linus Sebastian from LTT on YouTube did the switch to Linux videos and yesterday they released the first video in the series. It was simply embarrassing. pop os failed spectacularly, mint had live image monitor issues and it reminded me of high school project that the kid didn't put a lot of thought in and the kid was still proud of showing it off, stumbling along the way. I have been using neon since 5.12 full time, so i know these things "should not happen" but since they did to a novice like Linus and Luke, maybe we need to look at how we can improve new comers. The on-boarding experience is a good thing. I would like to add, with ideas from the video to show people how to do basic stuff, like install packages. Pop os failed because of Pop os fault. doesn't matter. the user was let down. How about we inform the user about various install formats, like flatpak and snap and deb and how they are different. Small texts, just pointers. I did not understand why Linus had to use a software to find if all devices were set up, why doesn't the software at "on-boarding" time do that check and say "there are drivers missing for this device. should i check to see if there is a driver?" and install it also at the same time? How about we put the "whats new in Kde" blog posts in this on-boarding experience ? using the package manager is supposed to "prevent" users from bricking their setups generally. oh, would it be possible to more "humanize" error screens? we do say "you are about to take this step. the following will be removed", can we improve by saying "proceed with caution. doing this might brick your system" instead of a wall of text? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366063] Window switcher does not start with specific key combination
https://bugs.kde.org/show_bug.cgi?id=366063 --- Comment #6 from Mikiya Okuno --- Hi Martin, The problem appears to be solved in my version. I'm using 5.22, but the problem does not happen. BTW, I have not faced the problem for long time, because I switched my physical keyboard to ErgoDox, which can change the keyboard layout using its firmware ;) Kind regards, Mikiya -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425553] Konsole crashes on tab/window closing.
https://bugs.kde.org/show_bug.cgi?id=425553 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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.
[Discover] [Bug 444417] Discovery is slow during update
https://bugs.kde.org/show_bug.cgi?id=17 --- 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 444433] Latte crashes while using Zoom application.
https://bugs.kde.org/show_bug.cgi?id=33 --- 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.
[kwin] [Bug 444298] Unable to set 240 Hz
https://bugs.kde.org/show_bug.cgi?id=444298 --- Comment #12 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.
[kwin] [Bug 445244] Add option to allow fixed window focus when using a stylus
https://bugs.kde.org/show_bug.cgi?id=445244 qydwhotm...@gmail.com changed: What|Removed |Added Depends on||432104 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=432104 [Bug 432104] stylus/pen input does not work on window decorations -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432104] stylus/pen input does not work on window decorations
https://bugs.kde.org/show_bug.cgi?id=432104 qydwhotm...@gmail.com changed: What|Removed |Added Blocks||445244 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=445244 [Bug 445244] Add option to allow fixed window focus when using a stylus -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445224] kcm_formats doesn't show the short date format preview
https://bugs.kde.org/show_bug.cgi?id=445224 --- Comment #6 from Ahmad Samir --- Created attachment 143393 --> https://bugs.kde.org/attachment.cgi?id=143393=edit kcm_formats-2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445243] "Click raises active window" has no effect in wayland session
https://bugs.kde.org/show_bug.cgi?id=445243 qydwhotm...@gmail.com changed: What|Removed |Added Blocks||445244 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=445244 [Bug 445244] Add option to allow fixed window focus when using a stylus -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445244] New: Add option to allow fixed window focus when using a stylus
https://bugs.kde.org/show_bug.cgi?id=445244 Bug ID: 445244 Summary: Add option to allow fixed window focus when using a stylus Product: kwin Version: git master Platform: openSUSE RPMs URL: https://invent.kde.org/plasma/kwin/-/merge_requests/16 27 OS: Linux Status: REPORTED Keywords: usability Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: qydwhotm...@gmail.com Depends on: 445243 Target Milestone: --- Sometimes an artist may not want accidentally change the window focus when they are drawing. It would be better if there is an option to disable window activation policy (Click to focus...) for stylus. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=445243 [Bug 445243] "Click raises active window" has no effect in wayland session -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444917] Make "updates available" notifications more informative
https://bugs.kde.org/show_bug.cgi?id=444917 --- Comment #2 from Nagy Tibor --- But it tells me that some things have changed and pending updates have started amassing in the background. After the introduction of offline updates I started being guilty of not immediately updating when I only have a small number of outdated packages, postponing things a bit because restarting my machine every day just for updating three random packages is a hassle [1]. I may not be the only user that offline updates had this kind of detrimental effect on. And I cannot turn off offline updates because live updates have caused me severe Plasma and Dolphin breakages in the past. Showing a bit more detail in the notification popups would help nudging me to not forget updating. Currently these notification popups and the tray icon are devoid of any kind information, triggering banner blindness in users like me. [1] Why?: Partially broken login screen on multi-monitor setup with different resolutions, broken session restore in several of my apps (Bug 439243 and friends), etc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445243] "Click raises active window" has no effect in wayland session
https://bugs.kde.org/show_bug.cgi?id=445243 qydwhotm...@gmail.com changed: What|Removed |Added Version|git master |5.23.2 Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445243] New: "Click raises active window" has no effect in wayland session
https://bugs.kde.org/show_bug.cgi?id=445243 Bug ID: 445243 Summary: "Click raises active window" has no effect in wayland session Product: kwin Version: git master Platform: Other URL: https://invent.kde.org/plasma/kwin/-/merge_requests/16 27 OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: qydwhotm...@gmail.com Target Milestone: --- Because KWin installs WindowActionInputFilter in wayland session. But the filter ignores the option. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 444883] Autocomplete / suggestion is very slow and insert random result once I hit ENTER
https://bugs.kde.org/show_bug.cgi?id=444883 --- Comment #19 from Waqar Ahmed --- I have been thinking about this for a while and might have a solution. We are limited by LSP(s), and also because how we are doing things(in Kate). One major problem on Kate's side is that we start completing after one character is typed. The LSP server, once it gets the 'm', is smart enough (or dumb) to not send everything that matches. Hence we run out of possible matches quickly once filtering happens on typing more chars. The quick solution is to honor the "Minimum length to complete (default 3)" setting by default. Starting completions on the first char is imo not a good idea in itself. Plus we need to revert the hack that I put in earlier. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401479] Feature request: add animations that follow the fingers when performing touchpad gestures
https://bugs.kde.org/show_bug.cgi?id=401479 poperi...@mailbox.org changed: What|Removed |Added CC||poperi...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416570] Option for "sticky edges" in multi-screen configuration.
https://bugs.kde.org/show_bug.cgi?id=416570 reso_magna <123123213ewr...@yopmail.com> changed: What|Removed |Added CC||123123213ewr...@yopmail.com --- Comment #7 from reso_magna <123123213ewr...@yopmail.com> --- Has there been any update on this feature? I think it would be highly useful now that multi monitor setups are becoming more widespread and it doesn't seem to be something too hard to implement. (In reply to Akshay Naik from comment #6) > This might be the better solution. Top-only(pre-defined) or user-defined > regions of pressure. I think user-defined regions of pressure should be the way to go. Sure, pressure on the upper right and lower right edges of the screen are usually useful to hit the usual locations of the "Show Desktop" button and the button to close a window easily without moving the cursor to the second monitor, but you should also consider the scrollbars. It's really annoying and time consuming to have to carefully point the cursor at the (usually) narrow scrollbars of many applications, such as web browsers. If a user doesn't like this feature, maybe a toggle to turn it off could be implemented as well. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 441908] Using The ":only" Command In Vim Edit Mode With Only One Window Opened Causes Crash
https://bugs.kde.org/show_bug.cgi?id=441908 Nicolás Alvarez changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/-/commit/173a ||ae37f98c3112cae5e9b3777239b ||981caeb8a --- Comment #4 from Nicolás Alvarez --- This has been fixed in https://invent.kde.org/kdevelop/kdevelop/-/commit/173aae37f98c3112cae5e9b3777239b981caeb8a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444516] Crash while painting
https://bugs.kde.org/show_bug.cgi?id=444516 --- Comment #14 from David REVOY --- Created attachment 143392 --> https://bugs.kde.org/attachment.cgi?id=143392=edit Another crash while painting (backtrace+disassemble+info register) Here is another crash report while painting (I was just filling with brush shapes, same task since hours). This time I caught succesfully the disassemble + info register (in attachement). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445223] Dragging icons in task manager stops working after a few drags
https://bugs.kde.org/show_bug.cgi?id=445223 --- Comment #4 from zocsfxljsgpmiua...@protonmail.com --- Created attachment 143391 --> https://bugs.kde.org/attachment.cgi?id=143391=edit Dragging icons in the Task Manager stops working -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445223] Dragging icons in task manager stops working after a few drags
https://bugs.kde.org/show_bug.cgi?id=445223 zocsfxljsgpmiua...@protonmail.com changed: What|Removed |Added CC||zocsfxljsgpmiuaanz@protonma ||il.com --- Comment #3 from zocsfxljsgpmiua...@protonmail.com --- I can reproduce the bug. I will attach a video showing it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444800] Discover crashes with error ASSERT: "m_responsePending != pending"
https://bugs.kde.org/show_bug.cgi?id=444800 Aleix Pol changed: What|Removed |Added Status|REOPENED|RESOLVED Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/commit/a42c064c |ma/discover/commit/f676c7f3 |ba3e427d599cf5e046881ac4d68 |a3ab0d8b8cbd24af10c3029a1b6 |02c8d |20e01 Resolution|--- |FIXED --- Comment #8 from Aleix Pol --- Git commit f676c7f3a3ab0d8b8cbd24af10c3029a1b620e01 by Aleix Pol. Committed on 10/11/2021 at 02:33. Pushed by apol into branch 'master'. kns: Prevent calling setResponsePending(false) when we didn't issue M +3-1libdiscover/backends/KNSBackend/KNSBackend.cpp https://invent.kde.org/plasma/discover/commit/f676c7f3a3ab0d8b8cbd24af10c3029a1b620e01 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445228] Discover flatpak "System Updates" section disappears after doing a non-Update All
https://bugs.kde.org/show_bug.cgi?id=445228 --- Comment #1 from Aleix Pol --- I cannot reproduce. Can you confirm you can reproduce this when running "plasma-discover --backends flatpak"? Or does flatpak and packagekit need to be on for the issue to happen? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445226] Replace "this will remove some packages" dialog with a check for the transaction removing system-critical packages like plasma-workspace or kwin
https://bugs.kde.org/show_bug.cgi?id=445226 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/202 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445055] UserActionsMenu has a ghost in 3D
https://bugs.kde.org/show_bug.cgi?id=445055 --- Comment #6 from xupeidong --- OK,thanks a lot,I will have a try. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444837] Crash ~10s after opening
https://bugs.kde.org/show_bug.cgi?id=444837 Aleix Pol changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED --- Comment #7 from Aleix Pol --- Would you be able to build the Plasma/5.23 branch? I think I included a fix there today (614450b3ee9175fb16f068af505fb59ed27e6697). Or otherwise maybe wait until 5.23.4 gets released (yes, I'm sorry about that). Otherwise, you'll be getting a 5.23.3 update soon, if you could provide a backtrace from it, that could also help. Note that if you're unable to open discover because it crashes, you can use "plasma-discover --backends packagekit" that won't load the faulty backend. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 443920] Fade Transition leaving after burn
https://bugs.kde.org/show_bug.cgi?id=443920 --- Comment #4 from Jim --- Resolved by deleting fade out and adding back in. Seem like existing projects will need Fade Out reload. This is not a fix just a work around. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444839] Allow Discover to skip checking for updates on filtered Flatpak packages
https://bugs.kde.org/show_bug.cgi?id=444839 --- Comment #4 from Aleix Pol --- I understand it can be annoying, I'm not sure what's a good way to decide that an app is being annoying though. In fact, maybe a good way forward here would be to go tell the developers to only release new versions when they have something to show. We can check when the applications deploy dir changed last, which I understand it would tell us when we last changed (flatpak_installed_ref_get_deploy_dir), but still how do we know it's a pointless update? It could well be that 2h after releasing, firefox did a patch update because they found a security bug and you surely would want the updates there. I'd suggest to either: - contact the packagers. - install the stable branch of the apps that annoy you. - enable unattended updates. We could improve a bit the behaviour on unattended updates, if you decide to go that route we can sure have a discussion, as you might still be getting some notifications. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445184] Rust v0 symbol demangling is broken
https://bugs.kde.org/show_bug.cgi?id=445184 Nick Nethercote changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445235] Java/Ada/D demangling is probably broken
https://bugs.kde.org/show_bug.cgi?id=445235 Bug 445235 depends on bug 445184, which changed state. Bug 445184 Summary: Rust v0 symbol demangling is broken https://bugs.kde.org/show_bug.cgi?id=445184 What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445184] Rust v0 symbol demangling is broken
https://bugs.kde.org/show_bug.cgi?id=445184 --- Comment #4 from Nick Nethercote --- I filed #445235 for Java/Ada/D. Pushed as: commit 4831385c6706b377851284adc4c4545fff4c6564 (HEAD -> master, origin/master, origin/HEAD) Author: Nicholas Nethercote Date: Tue Nov 9 12:30:07 2021 +1100 Fix Rust v0 demangling. It's currently broken due to a silly test that prevents the v0 demangling code from even running. The commit also adds a test, to avoid such problems in the future. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444954] Discover flatpak "Check for Updates" either doesn't work or else is too fast for the user to notice that it worked
https://bugs.kde.org/show_bug.cgi?id=444954 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/discover/commit/375aae3b ||2975bf2115b5eb55b116d5a7363 ||27e80 Status|CONFIRMED |RESOLVED --- Comment #3 from Aleix Pol --- Git commit 375aae3b2975bf2115b5eb55b116d5a736327e80 by Aleix Pol. Committed on 10/11/2021 at 01:25. Pushed by apol into branch 'master'. flatpak: Also fetch metadata when checking for updates M +34 -19 libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp M +1-0libdiscover/backends/FlatpakBackend/FlatpakBackend.h https://invent.kde.org/plasma/discover/commit/375aae3b2975bf2115b5eb55b116d5a736327e80 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445052] Crash when launching discover
https://bugs.kde.org/show_bug.cgi?id=445052 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||a42c064c Resolution|--- |DUPLICATE --- Comment #1 from Aleix Pol --- This was fixed as of a42c064c. *** This bug has been marked as a duplicate of bug 444800 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444800] Discover crashes with error ASSERT: "m_responsePending != pending"
https://bugs.kde.org/show_bug.cgi?id=444800 Aleix Pol changed: What|Removed |Added CC||isma...@gmail.com --- Comment #7 from Aleix Pol --- *** Bug 445052 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445241] New: My zoom feature isn't working properly.
https://bugs.kde.org/show_bug.cgi?id=445241 Bug ID: 445241 Summary: My zoom feature isn't working properly. Product: krita Version: 4.4.8 Platform: Microsoft Windows OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: ialsolikeminecraft...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE I don't know how to produce this bug, it just happened randomly. OBSERVED RESULT My zoom feature isn't working properly, my mouse won't zoom in, and when I use the magnifying glass tool, it zooms in, but then it zooms out when I try to do anything. SOFTWARE/OS VERSIONS Windows: 7 macOS: none Linux/KDE Plasma: none (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I hope I did this correctly. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 443324] Spacer Tool hangs the app if used with grouped clips
https://bugs.kde.org/show_bug.cgi?id=443324 biblio...@gmail.com changed: What|Removed |Added Version|21.08.2 |21.08.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445240] Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue
https://bugs.kde.org/show_bug.cgi?id=445240 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445240] New: Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue
https://bugs.kde.org/show_bug.cgi?id=445240 Bug ID: 445240 Summary: Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue Product: kwin Version: 5.23.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: lexlex...@gmail.com Target Milestone: --- Created attachment 143390 --> https://bugs.kde.org/attachment.cgi?id=143390=edit wayland session log ***Please understand that this issue report is about logging only, not the failure to start the session.*** STEPS TO REPRODUCE 1. Have the issue where the session named "Plasma (Wayland)" fails to start from SDDM, in such a way that trying to start it from the SDDM login menu navigates to a black screen, stays there for a few seconds, then navigates back to the SDDM login menu. 2. Verify that the contents of your ~/.local/share/sddm/wayland-session.log file are the following, or any with "cannot open display:" with nothing following that text, like so: --- (kwin_wayland:1939): Gtk-WARNING **: 16:11:52.831: cannot open display: (kwin_wayland:1944): Gtk-WARNING **: 16:11:52.903: cannot open display: (kwin_wayland:1945): Gtk-WARNING **: 16:11:52.975: cannot open display: (kwin_wayland:1946): Gtk-WARNING **: 16:11:53.036: cannot open display: (kwin_wayland:1948): Gtk-WARNING **: 16:11:53.094: cannot open display: (kwin_wayland:1949): Gtk-WARNING **: 16:11:53.151: cannot open display: (kwin_wayland:1951): Gtk-WARNING **: 16:11:53.206: cannot open display: (kwin_wayland:1952): Gtk-WARNING **: 16:11:53.262: cannot open display: (kwin_wayland:1953): Gtk-WARNING **: 16:11:53.318: cannot open display: (kwin_wayland:1954): Gtk-WARNING **: 16:11:53.373: cannot open display: (kwin_wayland:1955): Gtk-WARNING **: 16:11:53.428: cannot open display: startplasmacompositor: Shutting down... startplasmacompositor: Done. --- 3. Spend as much time as it takes to search online for a way to work around the issue. OBSERVED BEHAVIOR The log entries here that are like "Gtk-WARNING **: 16:11:52.831: cannot open display: " with nothing after them are not informative enough to figure out what the problem is, and there's no error message explaining why the session could not start, from either kwin_wayland or startplasmacompositor. The log file itself is attached to this ticket. EXPECTED BEHAVIOR Session log entries for sessions which fail to start are expected to explain clearly what is causing them to fail to start. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Linux 5.15 KDE Plasma Version: KDE Plasma 5.23.3 KDE Frameworks Version: 5.23.3 Qt Version: 5.15.2 and 6.2.1 ADDITIONAL INFORMATION Remember, this issue report is not about the failure to start. That can be tackled in another ticket. This is about the log entries on session start failure not being useful enough to determine the cause of the session start failure. They should always say exactly what's wrong, and improving the logging to the point where it says exactly what's wrong if the session fails to start is the only goal of this ticket. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443959] [feature] - add a dodge full-screen option to dock visibility options
https://bugs.kde.org/show_bug.cgi?id=443959 --- Comment #6 from Miguel Guthridge --- (In reply to Michail Vourlakos from comment #5) > it is a good workaround though, no idea when such feature request will be > implemented. And hence the feature request :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444917] Make "updates available" notifications more informative
https://bugs.kde.org/show_bug.cgi?id=444917 --- Comment #1 from Aleix Pol --- How would a more populated notification improve your experience? It doesn't even tell you all the things that changed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445224] kcm_formats doesn't show the short date format preview
https://bugs.kde.org/show_bug.cgi?id=445224 --- Comment #5 from Nate Graham --- Oh. Can you post a screenshot of the issue in the new KCM? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445032] valgrind/memcheck crash with SIGSEGV when SIGVTALRM timer used and libthr.so associated
https://bugs.kde.org/show_bug.cgi?id=445032 --- Comment #12 from Nick Briggs --- I've rebuilt based on the latest git version, and concur that the SIGSEGV is fixed. Now it just offers up a continuous stream of "sigreturn eflags..." % grep memcheck-x86 /tmp/out | sort | uniq -c 93 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x20 77 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x24 46 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200010 4 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200011 31 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200014 43 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200044 4 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200055 224 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200080 12 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200081 240 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200084 52 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200085 20 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200090 12 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200091 20 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200094 82 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200095 70 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200801 128 pid 68162 (memcheck-x86-freebs): sigreturn eflags = 0x200805 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 445239] Scrolling changes contents of dropdowns etc. even when it shouldn't
https://bugs.kde.org/show_bug.cgi?id=445239 natalie_clar...@yahoo.de changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 445239] New: Scrolling changes contents of dropdowns etc. even when it shouldn't
https://bugs.kde.org/show_bug.cgi?id=445239 Bug ID: 445239 Summary: Scrolling changes contents of dropdowns etc. even when it shouldn't Product: Breeze Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Mouse wheel scrolling changes contents of dropdowns, sliders, spinboxes and the like even when it shouldn't, e.g. when scrolling the surrounding window. STEPS TO REPRODUCE 1. Open some settings window with elements that accept input by mouse wheel. 2. Scroll the window with the cursor in a position where later down a settings element will accidentally get under the mouse cursor. OBSERVED RESULT The contents of the settings element unwantedly change. EXPECTED RESULT The scrolling doesn't change the settings, only scrolls the window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Settings change on scrolling is very easily triggered by accident, especially when scrolling the surrounding window. This leads to unwanted changes, often without noticing, which can be very annoying (see e.g. https://www.reddit.com/r/kde/comments/9xgw29/disable_scrolling_as_dropdown_context/, https://www.reddit.com/r/kde/comments/bn0ri1/disable_scrolling_into_dropdowns_and_spinners/, https://www.reddit.com/r/kde/comments/9cbema/mouse_wheel_changes_sliders_and_drop_down_menus/, https://forum.kde.org/viewtopic.php?f=17=111261). There should be an option to globally disable this feature, or at least some way of making sure it isn't triggered by accident, e.g. by accepting mouse wheel input only after the element has been clicked. -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 445139] Skanpage coredump
https://bugs.kde.org/show_bug.cgi?id=445139 --- Comment #5 from idimitro --- Created attachment 143389 --> https://bugs.kde.org/attachment.cgi?id=143389=edit debug_traces Hi, here is the backtrace with debug symbols. I reproduced the issue on Neon machine on the same network with the same printer. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 445238] New: after changing swap amount `Memory and Swap History` legend shows old value
https://bugs.kde.org/show_bug.cgi?id=445238 Bug ID: 445238 Summary: after changing swap amount `Memory and Swap History` legend shows old value Product: ksysguard Version: 5.21.5 Platform: Debian unstable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: 236...@edu.p.lodz.pl CC: plasma-b...@kde.org Target Milestone: --- Created attachment 143388 --> https://bugs.kde.org/attachment.cgi?id=143388=edit minor ui malfunction SUMMARY as in title STEPS TO REPRODUCE 1. launch ksysguard $ ksysguard & # navigate to "System Load" tab 2. add more swap # cd /tmp # dd if=/dev/zero bs=1M count=1K of=more_swap # chmod 600 more_swap # mkswap more_swap # swapon more_swap 3. observe OBSERVED RESULT after changing swap amount `Memory and Swap History` graph legend shows old value while display on bottom updates to new one. EXPECTED RESULT it changing to new maximum SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: n/a, Linux/Gnome (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: no idea ADDITIONAL INFORMATION newly created graphs use current value -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444033] System Tray disappears when there are no visible entries
https://bugs.kde.org/show_bug.cgi?id=444033 --- Comment #4 from natalie_clar...@yahoo.de --- While removing and readding the system tray widget didn't help, setting up the whole panel anew did, so the problem has resolved itself for me. (Don't know if the issue should remain open anyway in case you still want to look into what triggers this bug.) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445237] crash when opening a automounted cifs location
https://bugs.kde.org/show_bug.cgi?id=445237 --- Comment #1 from Vladi --- Created attachment 143387 --> https://bugs.kde.org/attachment.cgi?id=143387=edit remote section -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445237] New: crash when opening a automounted cifs location
https://bugs.kde.org/show_bug.cgi?id=445237 Bug ID: 445237 Summary: crash when opening a automounted cifs location Product: dolphin Version: 21.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: vl...@aresgate.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 143386 --> https://bugs.kde.org/attachment.cgi?id=143386=edit path SUMMARY I have a automounted cifs location set up on my local machine to point to my samba server: /mnt/cifs/das on my local machine when i open dolphin and then double click on the path bar and enter the path manually if the path is not already mounted dolphin resets the path back to the parent cifs mount ie: I enter /mnt/cifs/das/example1, dolphin will reset path to /mnt/cifs/das sometimes at random dolphin crashes when loading file list for the mount point as well. STEPS TO REPRODUCE 1. open dolphin 2. navigate to a cifs mount 3. OBSERVED RESULT random crash EXPECTED RESULT file list SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.22.5 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2-r10 ADDITIONAL INFORMATION Portage 3.0.28 (python 3.9.7-final-0, default/linux/amd64/17.1/desktop/plasma, gcc-11.2.0, glibc-2.33-r7, 5.14.15 x86_64) = System uname: Linux-5.14.15-x86_64-AMD_Ryzen_7_3700X_8-Core_Processor-with-glibc2.33 KiB Mem:16320004 total, 8893948 free KiB Swap: 16382972 total, 16382972 free Timestamp of repository gentoo: Mon, 08 Nov 2021 22:21:34 + sh bash 5.1_p8 ld GNU ld (Gentoo 2.37_p1 p0) 2.37 distcc 3.4 x86_64-pc-linux-gnu [enabled] ccache version 4.4.2 [disabled] app-shells/bash: 5.1_p8::gentoo dev-java/java-config: 2.3.1::gentoo dev-lang/perl:5.34.0-r3::gentoo dev-lang/python: 3.9.7_p1::gentoo dev-lang/rust:1.53.0::gentoo dev-util/ccache: 4.4.2::gentoo dev-util/cmake: 3.20.5::gentoo sys-apps/baselayout: 2.7::gentoo sys-apps/openrc: 0.44.7::gentoo sys-apps/sandbox: 2.25::gentoo sys-devel/autoconf: 2.13-r1::gentoo, 2.71-r1::gentoo sys-devel/automake: 1.16.4::gentoo sys-devel/binutils: 2.37_p1::gentoo sys-devel/gcc:11.2.0::gentoo sys-devel/gcc-config: 2.4::gentoo sys-devel/libtool:2.4.6-r6::gentoo sys-devel/make: 4.3::gentoo sys-kernel/linux-headers: 5.10::gentoo (virtual/os-headers) sys-libs/glibc: 2.33-r7::gentoo Repositories: ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="*" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=znver2 -O3 -fgraphite-identity -floop-nest-optimize -fdevirtualize-at-ltrans -fipa-pta -fno-semantic-interposition -flto=auto -fuse-linker-plugin -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-march=znver2 -O3 -fgraphite-identity -floop-nest-optimize -fdevirtualize-at-ltrans -fipa-pta -fno-semantic-interposition -flto=auto -fuse-linker-plugin -pipe" DISTDIR="/usr/portage/distfiles" ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distcc distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://distfiles.gentoo.org; LANG="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" LINGUAS="en bg" MAKEOPTS="-j17 -l9" PKGDIR="/var/cache/binpkgs" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git" PORTAGE_TMPDIR="/var/cache/gentoo" USE="X a52 aac aalib acl acpi activities adns aio alsa amd64 asf bash-completion bluetooth branding btrfs bzip2 cairo caps cdda cdr chroot cli crypt cryptsetup cups curl custom-cflags custom-optimization dav1d dbus declarative device-mapper dri dts dv dvd dvdr egl elogind emboss encode exif faac faad ffmpeg flac fortran gbm gdbm gif glamor gles gles2 glib gold gpg
[plasmashell] [Bug 445223] Dragging icons in task manager stops working after a few drags
https://bugs.kde.org/show_bug.cgi?id=445223 --- Comment #2 from yiz...@kulodgei.com --- (In reply to Nate Graham from comment #1) > Those errors are unrelated. Cannot reproduce. :/ Maybe my steps were incorrect the first time. I had it happen just now from a reboot with various methods but the below one worked every time. Please try again: Perhaps it is tied to the amount of programs pinned? I have about 17 programs pinned in the task manager. 1) I took the 3rd last one and dragged it to the end. 2) Then again grabbed third last one to the end. 3) one more time did the same. After this the issue occurs where you can "pick up" the icon (it actually stays in the task manager but you get a mini version) however you cannot actually do anything with it but let go. This happens to all of the icons regardless if they moved before or not. Other cases, I simply did a cold boot and just dragged various programs here and there and then it stops working. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 444883] Autocomplete / suggestion is very slow and insert random result once I hit ENTER
https://bugs.kde.org/show_bug.cgi?id=444883 --- Comment #18 from Sven Brauch --- Ah. I didn't understand that either, but trusted the people who had used it with the LSP stuff to have a valid reason for this behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445236] All Qt5 applications have their font sizes way bigger than they are supposed to be in an X11 session in Plasma 5.23.3-1. This affects all components and I am not sure what c
https://bugs.kde.org/show_bug.cgi?id=445236 --- Comment #2 from Nicolas Fella --- A workaround is to set "Force font DPI" to 96 in the font settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445136] Crashes in KCMKWinDecoration::borderSizeIndexToString() while setting theme
https://bugs.kde.org/show_bug.cgi?id=445136 --- Comment #3 from Michael --- No, I did not; it was early on in the installation. I've since had other frustrations with Aisleriot Solitaire and have uninstalled and gone back to my previous Distro, with which I was happy using; your Distro piqued my interest and I may come back to if after it has matured more - it's a great idea! One of my other frustrations was in trying to figure out how exactly to uninstall an application. It's now academic. I'm just a 69 year old wannabe curmudgeon who knows more Windows than Linux. Thanks for your time Michael On Tue, Nov 9, 2021 at 3:25 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=445136 > > Nate Graham changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #2 from Nate Graham --- > I am digging into this, but I'm unable to reproduce the crash by > downloading > and applying the "Willow Dark" window decoration theme. Did you do anything > else before it crashed? Like change the border size, perhaps? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445236] All Qt5 applications have their font sizes way bigger than they are supposed to be in an X11 session in Plasma 5.23.3-1. This affects all components and I am not sure what c
https://bugs.kde.org/show_bug.cgi?id=445236 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- This is caused by a change in X11, see https://gitlab.freedesktop.org/xorg/xserver/-/issues/1241#note_1149546 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 445187] Elisa fails to build music library for flac files
https://bugs.kde.org/show_bug.cgi?id=445187 Rob Collins changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Rob Collins --- I tracked down the cause of this - an apparently corrupt baloo file indexer database, To fix the problem I did the following in a terminal: 1. balooctl purge 2. balooctl disable 3, rm -rf ~/.local/share/baloo 4. balooctl enable 5. balooctl resume You can check baloo's progress by typing balooctl status periodically and you can see "Files waiting for content indexing: __" tells you how many files left to index. When that entry goes to zero you know baloo is finished for now. If everything has worked properly the entry "Files failed to index:__" should say "0". I fired up Elisa again after all that an presto - all my albums are now neatly appearing as a library. As a side note you can check if your music files have been baloo-indexed properly by going into Dolphin and opening a folder with music files, right clicking , and adding in (eg) "album" or "artist" columns. If those columns are still empty and you know there are metatags inside them, then you know you've still got a problem with baloo indexing, and therefore Elisa won't work. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 444883] Autocomplete / suggestion is very slow and insert random result once I hit ENTER
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #17 from Milian Wolff ---
I was more talking about this part from waqar's earlier comment:
{quote}
The reason for the slowness is likely because very recently, a change was made
in ktexteditor that allows requerying the underlying completion source for
completions. The reason for requerying is to get more relevant completions
based on the newly typed characters, so for e.g you type
mov
You get a list of completions as a result. You type 'movIt' and you get new and
more relevant completions. It's also important to note that the requerying
doesn't happen for every typed character although I very much wanted to do that
but it had two issues
- the completion pop up blinked every time you typed a char (very annoying)
- it made kdevelop's completion too slow to the point that it was unbearable
So, the model is requeried but not for every character.
{/quote}
I don't understand why that should be done on the model level, instead of on
the filter level afterwards - typing `mov` once should give you all results
already. then typing `movIt` would only reduce the result set?
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 445210] Plasma hangs all but mouse moves and some beep - no keyboard response
https://bugs.kde.org/show_bug.cgi?id=445210 --- Comment #2 from Andrey --- + is handled by X11 and not Plasma, so it seems like lower-level problem indeed. That beeps might be symptom of some buffer overflow, e.g with keyboard events. XKB doesn't handle physical devices so should be indifferent. I might also be useful to look into X11 logs, I'm not sure journalctl grabs ones.. I see crashes in your log, can you also try the session with new user? What's on Wayland? Does the problem arose after some upgrade, meaning it's a regression? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445224] kcm_formats doesn't show the short date format preview
https://bugs.kde.org/show_bug.cgi?id=445224 Ahmad Samir changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #4 from Ahmad Samir --- I have the new KCM, which doesn't have the date format I mentioned in the description; I posted a screenshot of the old one that has it, the current KCM doesn't -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445236] New: All Qt5 applications have their font sizes way bigger than they are supposed to be in an X11 session in Plasma 5.23.3-1. This affects all components and I am not sure w
https://bugs.kde.org/show_bug.cgi?id=445236 Bug ID: 445236 Summary: All Qt5 applications have their font sizes way bigger than they are supposed to be in an X11 session in Plasma 5.23.3-1. This affects all components and I am not sure what category to use. Product: plasmashell Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: anhollander...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Flags: X11+, Usability+ Created attachment 143384 --> https://bugs.kde.org/attachment.cgi?id=143384=edit The expected font size is used by Bleachbit, a GTK3 app. Qalculate! Qt5 and Dolphin do not use the correct font size. The only thing that does is the clock. SUMMARY After updating to Plasma 5.23.3-1 from the Arch Linux repos, in an X11 session, all Qt5 applications' fonts are way bigger than they are supposed to be. This also applies to all plasmashell components, as well as KWin window titles. Absolutely none of this is reproducible in a Plasma Wayland session. STEPS TO REPRODUCE 1. Update KDE Plasma to 5.23.3-1 on Arch Linux 2. Reboot OBSERVED RESULT Observe SDDM's font sizes are way bigger than they were before updating. After logging in to an X11 session, all fonts in plasmashell, the KDE apps, and other Qt5 apps are way bigger than they were before updating. All GTK apps, as well as the clock widget, look totally fine. EXPECTED RESULT No changes after updating except for the intended minor tweaks and bug fixes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.23.3-1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-arch1-1 Graphics Platform: X11 ADDITIONAL INFORMATION I have reproduced this bug on two separate machines. Neither are using NVIDIA GPUs. The second one is running a completely stock KDE, except for changing the theme to Breeze Dark and upping the font sizes by 1pt. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445095] Touchpad Applet is missing
https://bugs.kde.org/show_bug.cgi?id=445095 --- Comment #2 from Nate Graham --- In retrospect, I think you're right and deleting the applet was a mistake. What I probably should have done is made it a read-only applet capable of showing status and nothing more, like the Caps Lock and Microphone applets. I stand by the decision to not let it disable the touchpad on click, because this provided a way for someone with no mouse to brick their system. I will work on adding it back in read-only form. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445235] New: Java/Ada/D demangling is probably broken
https://bugs.kde.org/show_bug.cgi?id=445235 Bug ID: 445235 Summary: Java/Ada/D demangling is probably broken Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: n.netherc...@gmail.com CC: jsew...@acm.org, m...@klomp.org, philippe.waroqui...@skynet.be Depends on: 445184 Target Milestone: --- +++ This bug was initially created as a clone of Bug #445184 +++ Valgrind has code to demangle symbols for: C++, Rust, Java, Ada, and D. But the Java/Ada/D demangling is probably broken because the code is unreachable. `VG_(demangle)` has an initial test that requires that the first two chars be "_Z" or "_R", which excludes a bunch of cases. Also, the code in `ML_(cplus_demangle)` that calls the demanglers for Java/Ada/D is a bit different to that for C++ and Rust (in the way the `*_DEMANGLING` constants are used), which may also be a problem. >From a quick look at the code, I think the following is true. - C++ symbols usually start with "_Z", but "_GLOBAL_" is also possible, which won't work. - Rust symbols start with "_Z" or "_R". - Java symbols are a subset of C++ symbols, so should be ok, modulo possible "_GLOBAL_" cases, and possible AUTO_DEMANGLING problems. - D symbols start with "_D", and so will be broken. - Ada symbols can start with "_ada_", or with a lower-case letter, and so will be broken. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=445184 [Bug 445184] Rust v0 symbol demangling is broken -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445184] Rust v0 symbol demangling is broken
https://bugs.kde.org/show_bug.cgi?id=445184 Nick Nethercote changed: What|Removed |Added Blocks||445235 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=445235 [Bug 445235] Java/Ada/D demangling is probably broken -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445184] Rust v0 symbol demangling is broken
https://bugs.kde.org/show_bug.cgi?id=445184 --- Comment #3 from Nick Nethercote --- > What about the Java Ada/gnat and D demangling defined in ML_(cplus_demangle)? > We seem to miss demangling them too because they (probably) don't start with > _Z or _R and aren't guarded by AUTO_DEMANGLING. > Has that also always been broken? Did we simple not notice because nobody > uses valgrind with those languages? >From a quick look at the code, I think the following is true. - C++ symbols usually start with "_Z", but "_GLOBAL_" is also possible, which won't work. - Java symbols are a subset of C++ symbols, so should be ok, modulo possible "_GLOBAL_" cases, and possible AUTO_DEMANGLING problems. - D symbols start with "_D", and so will be broken. - Ada symbols can start with "_ada_", or with a lower-case letter, and so will be broken. I found the AUTO_DEMANGLING stuff a bit confusing, but you are right that the code for Rust and C++ looks a bit different to the code for Java/Ada/D, in that respect. I suspect that you are also right about Java/Ada/D demangling being broken but nobody noticing due to low levels of usage. Fixing the Java/Ada/D problems is outside the scope of this bug, and I'm not familiar enough with those languages to fix and test things anyway. Here's what I'll do: I'll file a new bug pointing out the problems, update my commit to include a comment in `VG_(demangle)` that points to the bug, and then push. That way the Rust problems will be fixed, and the Java/Ada/D problems at least will be documented. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444979] Green dot in title bar, that only seems to show up when Firefox is open
https://bugs.kde.org/show_bug.cgi?id=444979 --- Comment #2 from poperi...@mailbox.org --- (In reply to Nate Graham from comment #1) > That sounds odd. Can you attach a screenshot of the window that shows the > weird little green dot? The thing is, it doesn't show up in screenshots, which would usually mean it's a hardware issue, right? But that doesn't explain how it disappears and reappears depending on so many software variables. It also doesn't show up in the completely black boot screen. I have some pictures of it though. When in a Firefox tab: https://forum.endeavouros.com/uploads/default/original/3X/3/1/315507341a50d24bea148cdc850bc361a4f6ad70.jpeg) Disappears when I open a new tab: https://forum.endeavouros.com/uploads/default/original/3X/b/0/b085bcda789b26a98e6803b955447ee62dafad36.jpeg Isn't there in Dolphin: https://forum.endeavouros.com/uploads/default/original/3X/e/c/ec01208ab345cf3bf8eb515d98317babd745a0ae.jpeg -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445032] valgrind/memcheck crash with SIGSEGV when SIGVTALRM timer used and libthr.so associated
https://bugs.kde.org/show_bug.cgi?id=445032 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445032] valgrind/memcheck crash with SIGSEGV when SIGVTALRM timer used and libthr.so associated
https://bugs.kde.org/show_bug.cgi?id=445032 --- Comment #11 from Paul Floyd --- Fixed with commit 4b8eddfde14291e288a7017edce5c7225e1533d6 Author: Paul Floyd Date: Tue Nov 9 23:11:15 2021 +0100 However I do now get similar kernel messages to those mentioned in the linked github issue. That's another problem though. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445234] New: function "crop video/pic": option "use project resolution" not set per default
https://bugs.kde.org/show_bug.cgi?id=445234 Bug ID: 445234 Summary: function "crop video/pic": option "use project resolution" not set per default Product: kdenlive Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: egerl...@aiai.de Target Milestone: --- SUMMARY function "crop video/pic": option "use project resolution" can't be set as default in settings. I often forget it, then video is damaged. Then I have to correct video, and loose much time. STEPS TO REPRODUCE 1. function "crop video/pic" 2. option "use project resolution" is not set. 3. I have to set it again and again OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: 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.
[kdeconnect] [Bug 429173] [Wayland] Keyboard input is not available from Android to KDE neon
https://bugs.kde.org/show_bug.cgi?id=429173 --- Comment #4 from Nicolas Fella --- right, sorry -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443101] No option to enter letters from KDE Connect android app
https://bugs.kde.org/show_bug.cgi?id=443101 Nicolas Fella changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||nicolas.fe...@gmx.de Status|REPORTED|NEEDSINFO --- Comment #2 from Nicolas Fella --- Are you using Wayland? Keyboard input is not implemented there -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429173] [Wayland] Keyboard input is not available from Android to KDE neon
https://bugs.kde.org/show_bug.cgi?id=429173 Prajna Sariputra changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #3 from Prajna Sariputra --- That other bug is talking about clipboard support, this is talking about keyboard input from the "Remote input" section in the app, the button is missing if the PC side is on Wayland. As of now I have version 1.17.0 on the Android side and Plasma 5.23.2 + KDE Connect 21.08.3 on the PC side, and this feature is still missing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445210] Plasma hangs all but mouse moves and some beep - no keyboard response
https://bugs.kde.org/show_bug.cgi?id=445210 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||butir...@gmail.com, ||n...@kde.org --- Comment #1 from Nate Graham --- I very much doubt this could be caused by any KDE code, especially on X11 where input handling is done by the X server rather than anything under KDE's control. XKB, maybe? Andrey, any ideas? Maybe this is related to the recent X11 release which caused various regressions. Did you happen up receive and apply an X11 update in tumbleweed recently? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443831] Improve UI: Replace hamburger menu with menu items directly
https://bugs.kde.org/show_bug.cgi?id=443831 --- Comment #1 from Nicolas Fella --- At some point we deliberately changed it to this, but I agree that it's not ideal -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445233] New: function "extract pic (to project)" makes pic from video proxy
https://bugs.kde.org/show_bug.cgi?id=445233 Bug ID: 445233 Summary: function "extract pic (to project)" makes pic from video proxy Product: kdenlive Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: egerl...@aiai.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. function "extract pic (to project)" 2. view result: pic is blurred , beacuse made from proxy 3. OBSERVED RESULT blurred EXPECTED RESULT not blurred, done from original video SOFTWARE/OS VERSIONS Windows: macOS: 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.
[kdeconnect] [Bug 443831] Improve UI: Replace hamburger menu with menu items directly
https://bugs.kde.org/show_bug.cgi?id=443831 Nicolas Fella changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||nicolas.fe...@gmx.de Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445205] Using the systray icons menu messes up the input methods
https://bugs.kde.org/show_bug.cgi?id=445205 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- Fixed in the Plasma 5.23.3 update that was just released today :) *** This bug has been marked as a duplicate of bug 444385 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events
https://bugs.kde.org/show_bug.cgi?id=444385 Nate Graham changed: What|Removed |Added CC||a...@laxu.de --- Comment #23 from Nate Graham --- *** Bug 445205 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
