[plasmashell] [Bug 352476] Keyboard navigation in systray and the popup
https://bugs.kde.org/show_bug.cgi?id=352476 --- Comment #28 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1983 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453166] Opening and closing Panel widgets with keyboard shortcuts fails to return focus to the previously-focused window
https://bugs.kde.org/show_bug.cgi?id=453166 --- Comment #17 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1983 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457288] New: nvidia drivers crash
https://bugs.kde.org/show_bug.cgi?id=457288 Bug ID: 457288 Summary: nvidia drivers crash Product: systemsettings Version: 5.18.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: larionov.v...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.7) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.15.0-41-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: System crashes after installing nvidia drivers version 340.108. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2c40ed1080 (LWP 21875))] Thread 5 (Thread 0x7f2c2eaee700 (LWP 21881)): #0 0x7ffe085d7aed in clock_gettime () #1 0x7f2c47db00b5 in __GI___clock_gettime (clock_id=1, tp=0x7f2c2eaedab0) at ../sysdeps/unix/sysv/linux/clock_gettime.c:38 #2 0x7f2c48384d15 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2c483835ad in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2c48383b89 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2c483851a6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2c45dfa8ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f2c45dfb29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f2c45dfb4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f2c48385453 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2c4832c3ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2c48164785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2c474161a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f2c481659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2c469a1609 in start_thread (arg=) at pthread_create.c:477 #15 0x7f2c47df2133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f2c3d18f700 (LWP 21880)): #0 0x7f2c45df9262 in g_source_ref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2c45df9328 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2c45dfacbf in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2c45dfb312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2c45dfb4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2c48385453 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2c4832c3ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2c48164785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2c474161a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f2c481659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2c469a1609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f2c47df2133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2c3f0a1700 (LWP 21878)): #0 0x7ffe085d7aed in clock_gettime () #1 0x7f2c47db00b5 in __GI___clock_gettime (clock_id=1, tp=0x7f2c3f0a0aa0) at ../sysdeps/unix/sysv/linux/clock_gettime.c:38 #2 0x7f2c48384d15 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2c483835ad in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2c48383b89 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2c483851a6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2c45dfa8ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f2c45dfb29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f2c45dfb4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f2c48385453 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2c4832c3ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2c48164785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2c48607efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #13 0x7f2c481659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2c469a1609 in start_thread (arg=) at pthread_create.c:477 #15
[plasmashell] [Bug 456163] KWin error on resume from suspend after Lock screen error
https://bugs.kde.org/show_bug.cgi?id=456163 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 456132] Krunner fails and won't let you type
https://bugs.kde.org/show_bug.cgi?id=456132 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[krita] [Bug 456154] Krita crashes when pasting from Windows 11 Photo app
https://bugs.kde.org/show_bug.cgi?id=456154 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456747] attempting select application menu entry style crashes
https://bugs.kde.org/show_bug.cgi?id=456747 --- 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 450473] Transparent windows content on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=450473 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 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.
[frameworks-baloo] [Bug 455732] Fast native indexer did not see many of my "various artists" albums
https://bugs.kde.org/show_bug.cgi?id=455732 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 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.
[krunner] [Bug 456103] Excessive system journal messages from the Discord Messenger Client when launched from KRunner
https://bugs.kde.org/show_bug.cgi?id=456103 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[kwin] [Bug 455350] Regression in 5.25: present windows can't be deactivated for desktop grid
https://bugs.kde.org/show_bug.cgi?id=455350 --- Comment #14 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.
[Spectacle] [Bug 436218] Rectangular region grab under xwayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=436218 --- Comment #6 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.
[kalzium] [Bug 457191] Kalzium crashes after clicking the Molecular Editor button
https://bugs.kde.org/show_bug.cgi?id=457191 2wxsy5823...@opayq.com changed: What|Removed |Added Summary|Kalzium “分子编辑器”按钮在点击后崩溃|Kalzium crashes after ||clicking the Molecular ||Editor button -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 --- Comment #40 from Chris --- (In reply to Kai Uwe Broulik from comment #4) > That script isn't particularly efficient. > I like the idea of reducing the timeout for turning off the screen when it's > locked (and/or making that a separate option since you might not want it to > turn off at all while not locked), though. I added it to my todo list. > Thanks. What do you think of the script there https://bugs.kde.org/show_bug.cgi?id=348529#c33? It does not, on the face of it, rely on an infinite loop, and it works both with x11 and wayland. dbus-monitor --session "type='signal',interface='org.freedesktop.ScreenSaver'" | while read x; do case "$x" in *"boolean true"*) echo SCREEN_LOCKED; kwriteconfig5 --file powermanagementprofilesrc --group AC --group DPMSControl --key idleTime 60; qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus ;; *"boolean false"*) echo SCREEN_UNLOCKED; kwriteconfig5 --file powermanagementprofilesrc --group AC --group DPMSControl --key idleTime 600; qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus ;; esac done It is quick and dirty cut and paste but I think it works, and I don't see why not? As they say in https://bugs.kde.org/show_bug.cgi?id=348529#c39, it could help having something like that integrated in System-Settings, instead on relying on users hacks. It is annoying having 30W plus, of monitor LED, glowing unnecessarily. (https://www.thehomehacksdiy.com/how-much-power-watts-does-a-monitor-use/) Keep in mind that for most users, monitor power button is not an option because it scrambles up all the settings. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457272] Incorrect UI Element Padding under KDE with Breeze Theme at 1.5 scale
https://bugs.kde.org/show_bug.cgi?id=457272 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |7.7.0 CC||caulier.gil...@gmail.com Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456417] Translucency
https://bugs.kde.org/show_bug.cgi?id=456417 --- Comment #5 from audioprof2...@hotmail.com --- (In reply to Nate Graham from comment #1) > Sorry, I'm having a hard time understanding what you're requesting. Do you > think you could write in complete sentences? i will try... LOL™ better to explain with analogy... a window in a room, has a glass... sometimes, construction workers need to replace the broken glass, when moving the new glass through the street from the truck to the building, usually they paint a large X, so people can see the glass, and avoid a collision and break the New glass. unless they want to do a prank. similar happens with Mosquitoes, Flyes and Bees and birds, Forest insects are Not smart enough, brains are too small to know that a transparent object can exist, so they hit over and over with the glass when they are desperate to get out of the room, some insects are more calm, and stand on it, to analyze it, to understand, why there is an invisible force field. LOL™ but in some areas, insects become smarter, and learn in a few generations to sense the flow of the air current, to avoid collitions with invisible force fields- LOL™. Another example; The iconic Fruit Store, made from all glass, has a Giant Fruit logo on the glass and vertical lines. https://i.insider.com/5601b730dd08951e138b45f0 https://i.insider.com/560bb67cdd08950c628b457e A Glass is Not Transparent on the sides. Everything Transparent is Not Good. Unless you want to do a Prank. or you are an Alien from Another Planet. LOL™ or the Invisible Man. or very angry. https://www.youtube.com/watch?v=3dg960XGGSA https://www.youtube.com/watch?v=oLXDO5JR8-k https://www.youtube.com/watch?v=lW9rCmmHFgQ https://www.youtube.com/watch?v=mGLXbK2XWMY https://www.youtube.com/watch?v=djGBeMzMFEk https://www.youtube.com/watch?v=Oo0NJsr5m4I https://www.youtube.com/watch?v=lw8sIboEL6E https://www.youtube.com/watch?v=QtmRlNFtIuE https://www.businessinsider.com/apples-regent-street-store-overhaul-2015-9 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 393080] Crash in PodcastSettingsDialog::init
https://bugs.kde.org/show_bug.cgi?id=393080 --- Comment #10 from Lyall --- Created attachment 150991 --> https://bugs.kde.org/attachment.cgi?id=150991=edit Screen shots from start to crash Simple screen shots of parts of the Amarok UI up until crash. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 393080] Crash in PodcastSettingsDialog::init
https://bugs.kde.org/show_bug.cgi?id=393080 --- Comment #9 from Lyall --- Created attachment 150990 --> https://bugs.kde.org/attachment.cgi?id=150990=edit Debug output - amarok --debug, it's a text file, with colour escape codes, embedded Ran amarok at the command line amarok --debug > /tmp/amarok.log 2>&1 Log contains output from start to crash. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457287] c28dff79721d3805edcd413ef233216b3b3b0104 causes all instances of Kirigami.Page to lose vertical scrollbars with recent Qt
https://bugs.kde.org/show_bug.cgi?id=457287 Nate Graham changed: What|Removed |Added Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457287] New: c28dff79721d3805edcd413ef233216b3b3b0104 causes all instances of Kirigami.Page to lose vertical scrollbars with recent Qt
https://bugs.kde.org/show_bug.cgi?id=457287 Bug ID: 457287 Summary: c28dff79721d3805edcd413ef233216b3b3b0104 causes all instances of Kirigami.Page to lose vertical scrollbars with recent Qt Product: frameworks-kirigami Version: Master Platform: Other URL: https://bugreports.qt.io/browse/QTBUG-104983 OS: Linux Status: REPORTED Keywords: regression Severity: grave Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: n...@kde.org CC: notm...@gmail.com Target Milestone: Not decided With Qt 5.15.5, commit c28dff79721d3805edcd413ef233216b3b3b0104 in Kirigami triggers https://bugreports.qt.io/browse/QTBUG-104983 and all instances of Kirigami.Page lose their scrollbars. Everything is fine if that commit in Kirigami is reverted, or if commit 908aa77d16e00f2bccc0ddae0f8b61955c56a6a1 in Qt is reverted. But with both, Kirigami.Page instances lose their vertical scrollbars. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456417] Translucency
https://bugs.kde.org/show_bug.cgi?id=456417 --- Comment #4 from Nate Graham --- I can't triage this bug until I understand what the issue is, and I can't understand it right now. Can you please rephrase using complete sentences? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456417] Translucency
https://bugs.kde.org/show_bug.cgi?id=456417 --- Comment #3 from audioprof2...@hotmail.com --- Latest Kubuntu 22 LTS same issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457149] Plasma start with systemd breaks certain autostart file
https://bugs.kde.org/show_bug.cgi?id=457149 Weng Xuetian changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Weng Xuetian --- (In reply to David Edmundson from comment #2) > out of curiosity which .desktop file were you affected by? Was it > ibus-daemon? I don't use ibus. This https://github.com/fcitx/fcitx/blob/eb54e2b244e93d695c83c1f3bdbe6ee83155058a/data/fcitx-autostart.desktop.in#L12 It just contains the "X-GNOME-Autostart-Phase" due to some random reason. Maybe because I want it start after the panel is loaded in GNOME 2 times. I don't know if it does anything good, but it was just there and suddenly break by plasma updade. (Also I don't know why I remove this line in fcitx5 which make it unaffected luckily) So to me the situation as fcitx dev is not that bad, because mainstream distro (debian/ubuntu/fedora) does not use fcitx's own xdg autostart for input method. Right now the most affected distro is arch linux, so I just release a new version of old fcitx 4 in emergency simply avoid breakage by plasma. I'm actually reading the bug and they even find fcitx is affected? but no one wants to just open a bug to fcitx upstream? https://github.com/systemd/systemd/issues/18791#issuecomment-788922727 I have no idea about X-system-skip, not sure what's the semantics of it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433196] Make the icons of minimized applications, more pronounced
https://bugs.kde.org/show_bug.cgi?id=433196 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1068 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #33 from Felix Ernst --- (In reply to Mathias from comment #31) > I've been using 1) single-click and 2) split screens in 3) detailed list > view for ages, It seems like people with this combination are disrupted the most by the full row activation area. From what I have seen so far, most of the remaining strongly negative feedback to this change is from people in this user group. The problem is mostly about switching the active view. Before the full row highlight change, switching the active view by mouse was done by clicking not-directly-on-an-item which also cleared the selection. Now one can only switch the active view by either clicking the resizable padding on the sides or by drawing a small selection rectangle to the right of a file name. I agree that this requires a bit more effort. However it is debatable if it is unreasonable to expect users to click the side padding area and to resize it if clicking it seems to require too much effort. I wonder if there is another way in which we could make switching the active view easy that wouldn't get tripped up by the full row highlight. I guess not even the setting to switch the active view by using the "tab" key would be a complete solution because it also requires users to get used to it and isn't a great default for blind users. It would be best of course if we could find a solution that doesn't require any user to change a setting at all. Consuming the first click on an inactive view just to activate it but not to activate clicked items/rows might also potentially be unintuitive. Double-click users don't seem to mind this though. Ideas welcome. Having a setting to turn off full row highlight just because we can't figure out how to make switching the active pane comfortable would be a bit paneful. I am not really considering the unselecting of items as a big issue anymore because users unselect way less than they activate items so the usability benefit of having larger click areas for activation more than evens out the drawback of unselecting requiring more effort. This is true to me even if I take the initial learning curve into account. > and I use the navigation buttons (up and back) Clicking "Up" can be replaced by clicking the enclosing folder in the location bar but I guess opensuse has the "Up" button by default for a reason. It would be better if users didn't need to change their ways too much. I always click the "Back" button on my mouse to go "Back" without having to change the active view first. But not everyone does this or has such mouse side buttons so changing the active view first is necessary for many users. > or the mouse controls a lot to navigate through my folder structure. Not quite sure what you mean. Mouse controls work without changing the active view first so this shouldn't have become any more difficult. Actually it should be easier because the click target for opening a folder has increased. @Satyam: Not sure if you are aware, but most of the issues you have pointed out in comment #25 have already been addressed. Cutting and pasting has been fixed to work pretty much as before. The bug about tooltips is tracked separately and can be fixed separately of this bug report. Please don't compare KDE to Microsoft and Apple as long as the regressions happen because we are fixing popular bugs. Sensationalism doesn't help here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457272] Incorrect UI Element Padding under KDE with Breeze Theme at 1.5 scale
https://bugs.kde.org/show_bug.cgi?id=457272 --- Comment #8 from Freddie Witherden --- (In reply to Maik Qualmann from comment #7) > Created attachment 150985 [details] > padding.png > > Here is a screenshot, at 1.5 scaling, comparing Edit and View. Tested with > native digiKam-8.0.0 on openSUSE Tumbleweed. Absolutely identical. What > digiKam version are you using, on which system? Version 7.5.0 with KDE Frameworks 5.96.0 and Qt 5.15.5 and the xcb windowing system. All packages from Gentoo portage. (I am still waiting for my distro to bump to 7.7.0 as per https://bugs.gentoo.org/861341). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435439] Yakuake crashed while manually resizing drop-down window.
https://bugs.kde.org/show_bug.cgi?id=435439 --- Comment #4 from Chris THompson --- Created attachment 150989 --> https://bugs.kde.org/attachment.cgi?id=150989=edit New crash information added by DrKonqi yakuake (22.04.1) using Qt 5.15.5 Yakuake crashes whenever I attempted to resize the Yakuake window. Reason for needing to resize the window is because after a recent update to Fedora KDE spin, the Yakuake Application is starting in what appears to be an almost minimized state. -- Backtrace (Reduced): #4 0x55a7fae9f7e6 in TitleBar::mouseMoveEvent(QMouseEvent*) () #5 0x7fd7e786d828 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #6 0x7fd7e782ad22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #7 0x7fd7e7833392 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #8 0x7fd7e6d6d228 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435439] Yakuake crashed while manually resizing drop-down window.
https://bugs.kde.org/show_bug.cgi?id=435439 Chris THompson changed: What|Removed |Added CC||ch...@tech101.us -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456716] Okular crash when editing PDF
https://bugs.kde.org/show_bug.cgi?id=456716 Albert Astals Cid changed: What|Removed |Added Resolution|--- |UPSTREAM CC||aa...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Albert Astals Cid --- Tell the opensuse folks to update poppler. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456999] Email developer triggers unexpected close
https://bugs.kde.org/show_bug.cgi?id=456999 --- Comment #6 from Claudio Cambra --- (In reply to onedesignllc from comment #5) > Thank you, > > I am quite new to this so I am not aware on how to provide crash data. > The issue is also in the discover app when you click to mail the > contributors it may be better to make it just a text than a button. When the crash popup appears, there should be an option titled "Developer information". You can copy the contents of the text and provide them here -- that is a backtrace. The fact that this happens in Discover too leads me to believe this is a common issue, perhaps in Kirigami. Still, to confirm, we would need a backtrace or some other source of information (such as the output of running Kalendar in the terminal). > please kindly let me know how I can get access to the mailing list you > have a great software here and I am in the testing version. The most popular mailing lists can be found here: https://kde.org/support/mailinglists/ A full list can be found here: https://mail.kde.org/mailman/listinfo Hope this helps. - Claudio -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457234] crash when closing signed file
https://bugs.kde.org/show_bug.cgi?id=457234 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- You may want to figure out who wrote that e-dowod-pkcs11-64.so end tell them. I don't think there's much we can do here. I guess I would be silly in hoping the Polish goverment released that as free software? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 457286] New: Krusader sometimes crasehes when copying files
https://bugs.kde.org/show_bug.cgi?id=457286 Bug ID: 457286 Summary: Krusader sometimes crasehes when copying files Product: krusader Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: globalun...@disroot.org CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.2 "Peace of Mind") Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.11-1-default x86_64 Windowing System: Wayland Distribution: openSUSE Tumbleweed DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: Sometimes when you copy files from one oane to another, Krusader crashes In this case i was copying files from my /home folder (BTRFS) to my BTRFS pattition on my 64 GB Flash drive ORIGINAL BUG REPORT: https://bugs.kde.org/show_bug.cgi?id=448647#add_comment The crash can be reproduced sometimes. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault [KCrash Handler] #4 QAbstractScrollArea::viewport() const (this=0x0) at widgets/qabstractscrollarea.cpp:556 #5 0x561930912577 in KrViewItem::redraw() (this=0x5619332c2e70) at /usr/src/debug/krusader-2.7.2-2.1.x86_64/krusader/Panel/PanelView/krviewitem.cpp:144 #6 0x5619308e0b55 in KrPreviewJob::slotGotPreview(KFileItem const&, QPixmap const&) (this=0x561932f97fa0, item=, preview=) at /usr/src/debug/krusader-2.7.2-2.1.x86_64/krusader/Panel/krpreviewjob.cpp:89 #7 0x5619308cddcc in KrPreviewJob::slotFailed(KFileItem const&) (item=..., this=0x561932f97fa0) at /usr/src/debug/krusader-2.7.2-2.1.x86_64/krusader/Panel/krpreviewjob.cpp:77 #8 KrPreviewJob::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x561932f97fa0, _c=, _id=, _a=) at /usr/src/debug/krusader-2.7.2-2.1.x86_64/build/krusader/Panel/Panel_autogen/EWIEGA46WW/moc_krpreviewjob.cpp:91 #9 0x7fed66540e9c in doActivate(QObject*, int, void**) (sender=0x5619336ce440, signal_index=26, argv=0x7ffedcf8b650) at kernel/qobject.cpp:3898 #10 0x7fed6653a22f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fed67ff6980 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffedcf8b650) at kernel/qobject.cpp:3946 #11 0x7fed67f58b25 in KIO::PreviewJob::failed(KFileItem const&) (this=, _t1=) at /usr/src/debug/kio-5.96.0-1.1.x86_64/build/src/widgets/KF5KIOWidgets_autogen/include/moc_previewjob.cpp:205 #12 0x7fed67f53b63 in KIO::PreviewJobPrivate::determineNextFile() (this=0x561933700a00) at /usr/src/debug/kio-5.96.0-1.1.x86_64/src/widgets/previewjob.cpp:537 #13 0x7fed66540e6f in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffedcf8b7a0, r=0x5619336ce440, this=0x5619337fbd90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate(QObject*, int, void**) (sender=0x5619335da4d0, signal_index=6, argv=0x7ffedcf8b7a0) at kernel/qobject.cpp:3886 #15 0x7fed6653a22f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5619335da4d0, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffedcf8b7a0) at kernel/qobject.cpp:3946 #16 0x7fed6787b615 in KJob::result(KJob*, KJob::QPrivateSignal) (this=this@entry=0x5619335da4d0, _t1=, _t1@entry=0x5619335da4d0, _t2=...) at /usr/src/debug/kcoreaddons-5.96.0-1.1.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #17 0x7fed6787f7cb in KJob::finishJob(bool) (this=0x5619335da4d0, emitResult=) at /usr/src/debug/kcoreaddons-5.96.0-1.1.x86_64/src/lib/jobs/kjob.cpp:98 #18 0x7fed66540e6f in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffedcf8b8c0, r=0x5619335da4d0, this=0x5619336f0c90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x561931fc1be0, signal_index=5, argv=0x7ffedcf8b8c0) at kernel/qobject.cpp:3886 #20 0x7fed6653a22f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x561931fc1be0, m=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffedcf8b8c0) at kernel/qobject.cpp:3946 #21 0x7fed67b20f16 in KIO::SlaveInterface::error(int, QString const&) (this=this@entry=0x561931fc1be0, _t1=, _t2=...) at /usr/src/debug/kio-5.96.0-1.1.x86_64/build/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:452 #22 0x7fed67b25cf8 in KIO::SlaveInterface::dispatch(int, QByteArray const&) (this=0x561931fc1be0, _cmd=102, rawdata=...) at /usr/src/debug/kio-5.96.0-1.1.x86_64/src/core/slaveinterface.cpp:181 #23 0x7fed67b20dc6 in KIO::SlaveInterface::dispatch() (this=0x561931fc1be0) at /usr/src/debug/kio-5.96.0-1.1.x86_64/src/core/slaveinterface.cpp:78 #24 0x7fed67b23369 in
[plasmashell] [Bug 453242] kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade
https://bugs.kde.org/show_bug.cgi?id=453242 --- Comment #14 from Kamil Dudka --- The problem reported in comment #0 was actually caused by bug #457285. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423864] Updated "Confirm Logout" setting not applied on logout until next login session
https://bugs.kde.org/show_bug.cgi?id=423864 --- Comment #7 from Kamil Dudka --- (In reply to Kamil Dudka from comment #4) > After updating my Gentoo box to 5.20, the Log Out and Shut Down buttons in > plasma stopped working. They just cause plasma shell to crash. After > reverting the change mentioned in comment #2, the buttons work again. This was actually caused by bug #457285. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 457285] KConfigWatcher::config() returns nullptr when built without DBUS support
https://bugs.kde.org/show_bug.cgi?id=457285 --- Comment #1 from Kamil Dudka --- Created attachment 150988 --> https://bugs.kde.org/attachment.cgi?id=150988=edit [PATCH] KConfigWatcher: initialize d->m_config in constructor -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 457285] New: KConfigWatcher::config() returns nullptr when built without DBUS support
https://bugs.kde.org/show_bug.cgi?id=457285 Bug ID: 457285 Summary: KConfigWatcher::config() returns nullptr when built without DBUS support Product: frameworks-kconfig Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: kdu...@redhat.com CC: kdelibs-b...@kde.org Target Milestone: --- As additional KDE applications started to use KConfigWatcher, they started to crash on my laptop running Gentoo Linux. I was trying to patch them one by one to prevent the crashes. Then I realized that kconfig was built without dbus support on my system. After rebuilding kconfig with -DKCONFIG_USE_DBUS, the crashes went away. I looked into the source code of KConfigWatcher and discovered that its constructor initializes d->m_config only if KCONFIG_USE_DBUS is defined: https://github.com/KDE/kconfig/blob/491f5464/src/core/kconfigwatcher.cpp#L47 Consequently KConfigWatcher::config() may return nullptr, which triggers null dereference at caller's side, where a non-null value is expected. STEPS TO REPRODUCE 1. build kconfig without dbus support OBSERVED RESULT Applications like plasma or kwin start to crash. EXPECTED RESULT No crashes. SOFTWARE/OS VERSIONS Linux: 5.15.52-gentoo-x86_64 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Previously reported with backtraces at: bug #423864 comment #4 bug #453242 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
https://bugs.kde.org/show_bug.cgi?id=452967 --- Comment #7 from Kevin Kofler --- Can this bugfix be backported to the upcoming 5.25.4 bugfix release? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421021] [Wayland] Sometimes, the behaviour of Alt+Tab is reversed temporally
https://bugs.kde.org/show_bug.cgi?id=421021 magib...@hotmail.com changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- Version|5.18.4 |5.25.3 --- Comment #4 from magib...@hotmail.com --- I used the Wayland session again after a very long time and experienced this issue again in Plasma 5.25.3. Therefore, I'm reopening this issue. I'm sorry that I cannot provide steps to reproduce this issue reliably, since it just happens all of a suden. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376865] In-progress or half-finished animations included when capturing a screenshot without using the global keyboard shortcut or a delay
https://bugs.kde.org/show_bug.cgi?id=376865 Yuriy Vidineev changed: What|Removed |Added CC||adeptsm...@gmail.com --- Comment #16 from Yuriy Vidineev --- Same issue here. KDE Neon 5.25 User Edition KDE 5.25.3 KDE Framework 5.96 Qt 5.15.5 Linux 5.15 running X11 on Intel UHD graphics -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #32 from Satyam --- This update abandons the way dolphin has worked for the entirety of it's existence. It's not true to make a change to a fundamental way something has functioned for many years and say that's fixing a bug. This is not a bug fix, it's a reduction of function. KDE introduced me to single click in 3.5. Turns out there's a major efficiency with it. Now you're abandoning my years of use in favor of an idea that it's a more correct way. For years KDE has offered the most efficient work flow. For the first time ever I'm finding myself being disrupted the way I'm used to by Microsoft and Apple. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 457284] New: Lock screen shows black on Nvidia hardware
https://bugs.kde.org/show_bug.cgi?id=457284 Bug ID: 457284 Summary: Lock screen shows black on Nvidia hardware Product: kscreenlocker Version: 5.25.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eeickme...@ubuntu.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Lock screen shows black on Nvidia hardware. We did not see the same result on intel hardware with the same setup. STEPS TO REPRODUCE 1. Instal KDE 5.25.2 and 22.04 Jammy Jellyfish on a kubuntu focus system and reboot 2. Close the lid of the laptop and wait ~5 seconds for it to go to sleep 3. Open the lid and the lock screen should show up with a black background OBSERVED RESULT Lock screen has a black background because no background is selected EXPECTED RESULT Lock screen should should have a background selected SOFTWARE/OS VERSIONSLinux/KDE Plasma: Kubuntu 22.04 / 5.25.2 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Occured on nvidia hardware, did not occur on intel hardware. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457283] New: Broken desktop-panel visibility toggling when opening/closing the desktop grid
https://bugs.kde.org/show_bug.cgi?id=457283 Bug ID: 457283 Summary: Broken desktop-panel visibility toggling when opening/closing the desktop grid Product: kwin Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: bastimeyer...@gmail.com Target Milestone: --- Created attachment 150987 --> https://bugs.kde.org/attachment.cgi?id=150987=edit broken panel visibility during desktopgrid animation SUMMARY Since bug 451590 got fixed now (WindowHeap animation stuttering), it's become more obvious that there's an issue with desktop panels when opening and closing the desktop-grid. 1. Panels set to auto-hide are incorrectly fading in while closing the grid and they disappear instantly when the animation finishes (this can only be observed when no window is maximized). This is the bigger issue of the two, as it makes the closing animation appear glitchy. 2. Panels which are are always visible don't fade out while opening the desktop grid. Compared to when closing the grid, the panels correctly fade in. This is just a minor inconsistency issue. STEPS TO REPRODUCE Set the global animation scaling factor to a slow value to properly see the issue. 1.1. Have a panel added to the desktop and set to auto-hide 1.2. Open desktop grid and close it again on a desktop where no window is maximized 1.3. Watch the panel incorrectly fade in when closing the grid, even though it's supposed to stay hidden, and then watch it disappear instantly when the animation finishes 2.1. Have a panel added to the desktop and set to always-visible 2.2. Open desktop grid and close it again on a desktop where no window is maximized 2.3. Watch the panel disappear immediately when opening the grid, and watch it correctly fade in when closing the grid SOFTWARE/OS VERSIONS kwin built from latest commit on the Plasma/5.25 branch (9d7b7ad08102) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 333115] Add tool to fix dust area from lens
https://bugs.kde.org/show_bug.cgi?id=333115 caulier.gil...@gmail.com changed: What|Removed |Added Status|REOPENED|RESOLVED Version Fixed In||7.8.0 Resolution|--- |FIXED --- Comment #7 from caulier.gil...@gmail.com --- GmicQt digiKam plugin has inpainting functions. Please look my screenshot : https://i.imgur.com/qPvdRoS.png No need to write a new plugin for that... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #31 from Mathias --- Another usage scenario that cries for making the old behaviour at least available as an option again: I've been using 1) single-click and 2) split screens in 3) detailed list view for ages, and I use the navigation buttons (up and back) or the mouse controls a lot to navigate through my folder structure. And for doing that I need to change focus between the two split lists a lot. And I switch between the two lists by clicking in empty areas - the biggest ones are usually those after the filenames. The small empty column at the start is - too small. So please make it an option if you don't like to revert to the old behaviour. Until this change Dolphin was such a great file manager. (Switch to double-click is not an option, than I could have stayed with Windows 25 years ago ;)) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457282] New: KDE Plasma crashes when changing the Desktop Layout
https://bugs.kde.org/show_bug.cgi?id=457282 Bug ID: 457282 Summary: KDE Plasma crashes when changing the Desktop Layout Product: plasmashell Version: 5.25.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.3) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.17.5-76051705-generic x86_64 Windowing System: X11 Distribution: Feren OS DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: Every time the Desktop Layout is changed, KDE Plasma crashes twice. It only started happening in 5.25. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [New LWP 24946] [New LWP 24949] [New LWP 24991] [New LWP 25043] [New LWP 25044] [New LWP 25046] [New LWP 25047] [New LWP 25048] [New LWP 25049] [New LWP 25050] [New LWP 25051] [New LWP 25052] [New LWP 25053] [New LWP 25054] [New LWP 25055] [New LWP 25056] [New LWP 25057] [New LWP 25058] [New LWP 25059] [New LWP 25060] [New LWP 25061] [New LWP 25062] [New LWP 25311] [New LWP 25359] [New LWP 25365] [New LWP 25366] [New LWP 25504] [New LWP 25505] [New LWP 25506] [New LWP 25507] [New LWP 25508] [New LWP 25509] [New LWP 25510] [New LWP 25511] [New LWP 25512] [New LWP 25513] [New LWP 25514] [New LWP 25515] [New LWP 25516] [New LWP 25517] [New LWP 25518] [New LWP 25519] [New LWP 25520] [New LWP 25521] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7c0038f99f in poll () from /lib/x86_64-linux-gnu/libc.so.6 __preamble__ [Current thread is 1 (Thread 0x7f7bfc4ba9c0 (LWP 24933))] Thread 45 (Thread 0x7f7b18bf9700 (LWP 25521)): #0 0x7f7c000b9376 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c007255fb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7c023bf2f4 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f7c023bf769 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f7c0071f553 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 44 (Thread 0x7f7b193fa700 (LWP 25520)): #0 0x7f7c000b9376 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7bea4385eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7f7bea4381eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 43 (Thread 0x7f7b19bfb700 (LWP 25519)): #0 0x7f7c000b97d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c00725588 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7c00722aa1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7c0071f553 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 42 (Thread 0x7f7b1a3fc700 (LWP 25518)): #0 0x7f7c000b97d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c00725588 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7c00722aa1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7c0071f553 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 41 (Thread 0x7f7b1abfd700 (LWP 25517)): #0 0x7f7c000b97d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c00725588 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7c00722aa1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7c0071f553 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 40 (Thread 0x7f7b517fa700 (LWP 25516)): #0 0x7f7c000b97d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c00725588 in QWaitCondition::wait(QMutex*,
[krita] [Bug 457193] 5.1.0-beta2 is crashing on startup
https://bugs.kde.org/show_bug.cgi?id=457193 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from tomtomtomreportin...@gmail.com --- 5.1.0-beta1 had an issue where saving brushes would make those brushes unreadable in other versions. If you saved any brushes during beta 1, try using https://krita-artists.org/t/brush-fixer-for-brushes-created-in-krita-5-1-beta-1/44075 to fix such brushes or move the affected brushes elsewhere. Does this resolve your issue? -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Martino Fontana changed: What|Removed |Added CC||tinozzo...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450268] Magic Lamp / Slide effects duration speed should always be controlled by global option
https://bugs.kde.org/show_bug.cgi?id=450268 --- Comment #16 from bastimeyer...@gmail.com --- > No, because it's not a duration. It's this "springiness" constant. Okay, but you have to acknowledge that with the addition of the "springmotion" logic in 00ae7d38939e3e0c3414009f49d1dabb3a6345bd, sliding between desktops and switching activities has become painfully slow, especially the last end of the animation, which is a usability nightmare. Compared to other animations controlled by the global animation scaling factor, the slide animation is about twice as long, which is really bad. The constants either need to be adjusted accordingly, so that the overall animation time matches the one of the previous implementation, or the user should be given a chance to customize them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451590] Stutter on right-most screen of multi-screen setup when opening WindowHeap-based effects
https://bugs.kde.org/show_bug.cgi?id=451590 --- Comment #30 from bastimeyer...@gmail.com --- I've applied 63bf8112006acb37504c5d0b0cc850a74d3eb1da to Plasma/5.25 and it seems to have indeed fixed the stuttering. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456458] Cursor keeps disappearing! Disappears when moving from desktop to the taskbar. Changes from a normal 'arrow' to a 'hand' or some other icon. This started with the previous
https://bugs.kde.org/show_bug.cgi?id=456458 --- Comment #3 from cheryle --- 7.29/2022 Cursor disappearing is getting worse!! When changing applications the computer locks up! Nothing helps, other than rebooting. Production has dropped to 50%. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 457281] New: See-through / transparent window
https://bugs.kde.org/show_bug.cgi?id=457281 Bug ID: 457281 Summary: See-through / transparent window Product: kdenlive Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: k...@03j.de Target Milestone: --- Created attachment 150986 --> https://bugs.kde.org/attachment.cgi?id=150986=edit Result, the white parts you see is my desktop wallpaper SUMMARY See-through window on a fresh install of kdenlive. STEPS TO REPRODUCE 1. Install kdenlive 22.04.3 from the arch linux extra packages 2. Open kdenlive OBSERVED RESULT See your background image in some parts of the program. This result **doesn't** appear when i tell sway to fullscreen this window EXPECTED RESULT See a black/gray background but not my Sway Background SOFTWARE/OS VERSIONS Archlinux: Kernel 5.18.14-zen1-1-zen Sway: version 1.7 ADDITIONAL INFORMATION I'm using sway and set my background image via the sway config. I also use Krita on my archlinux sway installation and the bug doesn't appear in krita. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455507] Overview effect search box almost always causes hard system lockup
https://bugs.kde.org/show_bug.cgi?id=455507 --- Comment #12 from indecisiveautoma...@gmail.com --- Thanks for the help, sorry we didn't get anywhere but I appreciate all of your time regardless! I don't think any of my drives are faulty though I will investigate and check, I do have a nearly 7 year old storage HDD in my PC but KRunner doesn't crash my system when I activate and search with it using Alt+Space, it's only in the Overview effect that it crashes. Also, even if that drive isn't mounted, the Overview effect still crashes my system. My other 4 drives are all SSDs and all only a few years old, I run games off them without any problems so I don't think they're faulty either. But it's a bit strange that my system only crashes with the Overview effect search box. If there's any "preferred" way of diagnosing drives/getting drive health info to post for additional debugging, I'm happy to post that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455507] Overview effect search box almost always causes hard system lockup
https://bugs.kde.org/show_bug.cgi?id=455507 Niklas Stephanblome changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #11 from Niklas Stephanblome --- If your disk isn't faulty (hardware-wise, use any disk utility to check that) then I'm out of ideas. I'll leave this up to someone with more experience. For anyone trying to troubleshoot this, this issue is that KWin_Wayland crashes with SIGSEGV (=Signal 11) right after having started KRunner provider for baloo file indexer. The relevant lines from the journal are: Jul 29 17:42:58 endeavour dbus-daemon[826]: [sessionuid=1000 pid=826] Activating via systemd: service name='org.kde.runners.baloo' unit='plasma-baloorunner.service' requested by ':1.6' (uid=1000 pid=852 comm="/usr/bin/kwin_wayland --wayland-fd 7 --socket wayl") Jul 29 17:42:58 endeavour systemd[811]: Starting KRunner provider for baloo file indexer... Jul 29 17:42:58 endeavour dbus-daemon[826]: [session uid=1000 pid=826] Successfully activated service 'org.kde.runners.baloo' Jul 29 17:42:58 endeavour systemd[811]: Started KRunner provider for baloo file indexer. Jul 29 17:43:01 endeavour audit[852]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 pid=852 comm="GlobalQueue[22]" exe="/usr/bin/kwin_wayland" sig=11 res=1 Jul 29 17:43:01 endeavour kernel: traps: GlobalQueue[22][2373] general protection fault ip:7f46bcef7346 sp:7f45ecff8770 error:0 in libQt5Core.so.5.15.5[7f46bcc9f000+2c8000] Jul 29 17:43:01 endeavour kernel: audit: type=1701 audit(1659112981.368:102): auid=1000 uid=1000 gid=1000 ses=3 pid=852 comm="GlobalQueue[22]" exe="/usr/bin/kwin_wayland" sig=11 res=1 Jul 29 17:43:01 endeavour systemd[1]: Created slice Slice /system/systemd-coredump. Jul 29 17:43:01 endeavour audit: BPF prog-id=25 op=LOAD Jul 29 17:43:01 endeavour audit: BPF prog-id=26 op=LOAD Jul 29 17:43:01 endeavour audit: BPF prog-id=27 op=LOAD Jul 29 17:43:01 endeavour kernel: audit: type=1334 audit(1659112981.381:103): prog-id=25 op=LOAD Jul 29 17:43:01 endeavour kernel: audit: type=1334 audit(1659112981.381:104): prog-id=26 op=LOAD Jul 29 17:43:01 endeavour kernel: audit: type=1334 audit(1659112981.381:105): prog-id=27 op=LOAD Jul 29 17:43:01 endeavour audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-2397-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 29 17:43:01 endeavour systemd[1]: Started Process Core Dump (PID 2397/UID 0). Jul 29 17:43:01 endeavour kernel: audit: type=1130 audit(1659112981.382:106): pid=1 uid=0 auid=4294 [ This is the last line of the journal ] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453628] While Overview is open, touching the screen edge with an auto-hidden panel on it and closing Overview causes the panel to appear and stay open
https://bugs.kde.org/show_bug.cgi?id=453628 Nate Graham changed: What|Removed |Added Summary|Hovering over a panel with |While Overview is open, |auto-hide causes the panel |touching the screen edge |to stay open without hiding |with an auto-hidden panel |whilst overview is active |on it and closing Overview ||causes the panel to appear ||and stay open Status|REOPENED|CONFIRMED --- Comment #7 from Nate Graham --- Can reproduce that. Looks like that is the original bug and I just misunderstood it, sorry. I guess we should block the panel's screen edge activation while Overview is open. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457271] Baloo indexes files it shouldn't index
https://bugs.kde.org/show_bug.cgi?id=457271 --- Comment #5 from JanLukas --- (In reply to Nate Graham from comment #4) > Ok. Do you seen the same error anymore when you disable, purge and enable > baloo using balooctrl? It looks like it's gone, but I will try to replicate the bug again tomorrow when I have some time -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457271] Baloo indexes files it shouldn't index
https://bugs.kde.org/show_bug.cgi?id=457271 --- Comment #4 from Nate Graham --- Ok. Do you seen the same error anymore when you disable, purge and enable baloo using balooctrl? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455507] Overview effect search box almost always causes hard system lockup
https://bugs.kde.org/show_bug.cgi?id=455507 --- Comment #10 from indecisiveautoma...@gmail.com --- The system still locked up even after disabling file search. At first, the Overview effect closed and I was able to use my system for a few seconds, and then it locked up again. I tried this a few more times and each time was the same: The Overview effect closed and I could use my PC for a few seconds. I tested to see if it was some specific action that caused the lockup afterwards but even if I don't touch anything the system locks up after a few seconds. I have seconds enabled in my digital clock on my panel so when that freezes it gives a good indication of when its frozen, and it takes about 2-4 seconds. I wanted to make note and reiterate something: I got a warning when I unchecked this, saying it will disable file search in KRunner too. I can search for files just fine without any lockups from KRunner, which I just briefly mentioned in the opening part of this issue. I search for files with with KRunner every so often and I haven't had any issues with it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457272] Incorrect UI Element Padding under KDE with Breeze Theme at 1.5 scale
https://bugs.kde.org/show_bug.cgi?id=457272 --- Comment #7 from Maik Qualmann --- Created attachment 150985 --> https://bugs.kde.org/attachment.cgi?id=150985=edit padding.png Here is a screenshot, at 1.5 scaling, comparing Edit and View. Tested with native digiKam-8.0.0 on openSUSE Tumbleweed. Absolutely identical. What digiKam version are you using, on which system? Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
https://bugs.kde.org/show_bug.cgi?id=452967 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457280] Screen edges unusable since 5.25 - accessibility
https://bugs.kde.org/show_bug.cgi?id=457280 Just Anig changed: What|Removed |Added CC||ultragandalf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457280] New: Screen edges unusable since 5.25 - accessibility
https://bugs.kde.org/show_bug.cgi?id=457280 Bug ID: 457280 Summary: Screen edges unusable since 5.25 - accessibility Product: kwin Version: 5.25.3 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: ultragandalf...@gmail.com Target Milestone: --- SUMMARY *** Hello, I suffer from Essential tremor. My hand is trembling slightly (involuntarily). In 5.25, something subtly changed about how the screen edge is triggered - since then, I cannot use the desktop grid effect anymore. Instead of triggering the overview, it triggers it, and then when my mouse cursor moves slightly, seemingly immediately registers the screen edge trigger again, reverting the overview effect. Sometimes multiple times, leading to a flickering between desktop grid and regular desktop. This was not the case previously; It would be great if you could restore the behaviour from 5.24, where this problem was not present for me. *** SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 451726] KNS content displays ugly unclickable URL in its "Distributed by" metadata field
https://bugs.kde.org/show_bug.cgi?id=451726 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434713] Nothing happens when I press the keyboard shortcut of Keyboard Layout applet by the first time
https://bugs.kde.org/show_bug.cgi?id=434713 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455507] Overview effect search box almost always causes hard system lockup
https://bugs.kde.org/show_bug.cgi?id=455507 --- Comment #9 from Niklas Stephanblome --- If you go to System Settings > Search > File Search > uncheck "enable file search", then does Overview still crash the system? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457272] Incorrect UI Element Padding under KDE with Breeze Theme at 1.5 scale
https://bugs.kde.org/show_bug.cgi?id=457272 --- Comment #6 from Freddie Witherden --- (In reply to Maik Qualmann from comment #5) > Just to avoid any misunderstanding, are you talking about the border padding > or the item margin (left, top, right, bottom)? The overall widget padding. Consider the menu bar. Counting the pixels in Krita between the right hand side of the "t" in "Edit" and the left hand side of the "V" in view we get 31px. But in digiKam it is 20. Now lets look at tab height. In Krita our tabs are 45px high, whilst in digiKam they are 36px. Things get more fun if we look at the base-line distance: 10px in digiKam and 15px in Krita. Curiously, these ratios are, give or take a pixel, those of my high-DPI scale factor (1.5x). -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 454878] Images being shown in full res in Compact mode
https://bugs.kde.org/show_bug.cgi?id=454878 James Graham changed: What|Removed |Added CC||james.h.graham@protonmail.c ||om Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from James Graham --- Can confirm this is due to the fact that the limiting factor on image size is the width of the bubble, which is still technically there in compact mode just invisible and set to maximise to the available width in the lisView. This means that if the listView is wide a large image will be able to grow to full size taking up a lot of space. This could pretty easily be solved by putting a maximum size on the image we just have to pick what we think looks good. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 457278] Discover crashes every time when closing the window after applying updates
https://bugs.kde.org/show_bug.cgi?id=457278 Nate Graham changed: What|Removed |Added Version Fixed In||5.25.4 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457235] Laptop screen gets resized to after hot-plugging external monitor
https://bugs.kde.org/show_bug.cgi?id=457235 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- > the laptop display is resized to its top left quarter and garbled up Can you take a screenshot of what the laptop display shows when this happens? I'd like to make sure I understand what exactly you mean, as there are unfortunately quite a lot of things that can go wrong here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457055] Isolate layer doesn't work well
https://bugs.kde.org/show_bug.cgi?id=457055 --- Comment #3 from Dannel Gutiérrez --- (In reply to Dmitry Kazakov from comment #2) > Yes, these are two dirrefent shortcuts. Shift+click on the visibility icon > hides the layers in a tricky way (it is **not** an isolated mode), and > alt+click on the layer name enables isolated mode on that layer. Oh I see, I thought both were ways to isolate layer, well then Shift + Click is broken because it doesn't work right =( A suggestion, if you could make the shortcut to isolate layer only work with the visibility icon please, since it honestly confuses many users, I discovered this thanks to another user who tried it by chance, but if he hadn't Commented on this, the truth is, I don't think I discovered it by myself and the most possible thing is that I would have thought that it was broken. The latter is just a suggestion, nothing more to make it more friendly to new users. Thank you so much for answering =) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457255] deselect/disappear after restart
https://bugs.kde.org/show_bug.cgi?id=457255 David Chmelik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Chmelik --- The problem was thinking F11 might maximize Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 456905] NeoChat generating duplicate newlines
https://bugs.kde.org/show_bug.cgi?id=456905 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/neochat/-/merge_requests/492 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446468] Selected folder icon becomes white in selected list items
https://bugs.kde.org/show_bug.cgi?id=446468 Nate Graham changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #20 from Nate Graham --- *** Bug 457197 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457197] Compact and Details View: Selected folder icon becomes black using Breeze and white using Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=457197 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- It's Bug 446468 *** This bug has been marked as a duplicate of bug 446468 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457222] edit mode toolbar appears when editing a plasma panel
https://bugs.kde.org/show_bug.cgi?id=457222 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457222] edit mode toolbar appears when editing a plasma panel
https://bugs.kde.org/show_bug.cgi?id=457222 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This is the intended design, and it was done to make sure that the global edit mode is always the global edit mode, and not a panel-specific UI that slightly differs from other edit modes. We wanted to make sure this mode was discoverable and consistent. So I don't expect this to change, sorry. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 457279] In Kexi, allow deactivation of "snap to grid" feature in form design mode.
https://bugs.kde.org/show_bug.cgi?id=457279 Jarosław Staniek changed: What|Removed |Added Status|REPORTED|CONFIRMED URL||https://forum.kde.org/viewt ||opic.php?f=221=175584 Ever confirmed|0 |1 CC||stan...@kde.org --- Comment #1 from Jarosław Staniek --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 457279] New: In Kexi, allow deactivation of "snap to grid" feature in form design mode.
https://bugs.kde.org/show_bug.cgi?id=457279 Bug ID: 457279 Summary: In Kexi, allow deactivation of "snap to grid" feature in form design mode. Product: KEXI Version: 3.2.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Forms Assignee: kexi-b...@kde.org Reporter: wa...@ukulele.com CC: a...@piggz.co.uk, in...@fables.co.za 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. Open Kexi 2. Go into form design mode 3. When moving object on page, everything will get snapped to grid. OBSERVED RESULT In Form Design mode, snap to grid is the default and I'm unable to deactivate it. I would like the option of deactivating it. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (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.
[digikam] [Bug 457272] Incorrect UI Element Padding under KDE with Breeze Theme at 1.5 scale
https://bugs.kde.org/show_bug.cgi?id=457272 --- Comment #5 from Maik Qualmann --- Just to avoid any misunderstanding, are you talking about the border padding or the item margin (left, top, right, bottom)? Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457271] Baloo indexes files it shouldn't index
https://bugs.kde.org/show_bug.cgi?id=457271 --- Comment #3 from JanLukas --- 1. Disabling indexing, purging and re-enabling it fixed the problem 2. [Basic Settings] Indexing-Enabled=true [General] dbVersion=2 exclude filters=*~,*.part,*.o,*.la,*.lo,*.loT,*.moc,moc_*.cpp,qrc_*.cpp,ui_*.h,cmake_install.cmake,CMakeCache.txt,CTestTestfile.cmake,libtool,config.status,confdefs.h,autom4te,conftest,confstat,Makefile.am,*.gcode,*.csproj,*.m4,*.rej,*.gmo,*.pc,*.omf,*.aux,*.tmp,*.po,*.vm*,*.nvram,*.rcore,*.swap,lzo,litmain.sh,*.orig,.histfile.*,.xsession-errors*,*.map,*.so,*.a,*.db,*.qrc,*.ini,*.init,*.img,*.vdi,*.vbox*,vbox.log,*.qcow2,*.vmdk,*.vhd,*.vhdx,*.sql,*.sql.gz,*.ytdl,*.class,*.pyc,*.pyo,*.elc,*.qmlc,*.jsc,*.fastq,*.fq,*.gb,*.fasta,*.fna,*.gbff,*.faa,po,CVS,.svn,.git,_darcs,.bzr,.hg,CMakeFiles,CMakeTmp,CMakeTmpQmake,.moc,.obj,.pch,.uic,.npm,.yarn,.yarn-cache,__pycache__,node_modules,node_packages,nbproject,core-dumps,lost+found exclude filters version=6 exclude folders[$e]=$HOME/ index hidden folders=true -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457223] Scrollable lists in OverlaySheet have unnecessary horizontal scrollbar which blocks the last item
https://bugs.kde.org/show_bug.cgi?id=457223 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kirigami/commit/5728 ||e56dc37a8a05d6bc91227cea3cb ||375fe8445 Status|CONFIRMED |RESOLVED Version Fixed In||5.97 --- Comment #3 from Nate Graham --- Git commit 5728e56dc37a8a05d6bc91227cea3cb375fe8445 by Nate Graham. Committed on 29/07/2022 at 18:13. Pushed by ngraham into branch 'master'. OverlaySheet: add workaround for Qt horizontal scrollview bug https://bugreports.qt.io/browse/QTBUG-83890 doesn't seem like it's going to be fixed anytime soon, so let's add the traditional workaround for it. Until it's fixed, all instances of QQC2.ScrollView that aren't intended to be horizontally scrollable need this workaround. FIXED-IN: 5.97 M +3-0src/controls/templates/OverlaySheet.qml https://invent.kde.org/frameworks/kirigami/commit/5728e56dc37a8a05d6bc91227cea3cb375fe8445 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457223] Scrollable lists in OverlaySheet have unnecessary horizontal scrollbar which blocks the last item
https://bugs.kde.org/show_bug.cgi?id=457223 Nate Graham changed: What|Removed |Added Summary|Digital Clock's "Add More |Scrollable lists in |Timezones" dialog has a |OverlaySheet have |unnecessary horizontal |unnecessary horizontal |scrollbar which blocks the |scrollbar which blocks the |item underneath |last item Assignee|plasma-b...@kde.org |kdelibs-b...@kde.org CC||n...@kde.org, ||notm...@gmail.com Version|5.25.3 |5.96.0 Ever confirmed|0 |1 Product|plasmashell |frameworks-kirigami Status|REPORTED|CONFIRMED Component|Digital Clock |general --- Comment #2 from Nate Graham --- Caused by https://bugreports.qt.io/browse/QTBUG-83890, which is frustratingly still open after all these years. I'll add the traditional workaround for it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 455180] Plasma applet show as if connected to many wifi networks
https://bugs.kde.org/show_bug.cgi?id=455180 Nate Graham changed: What|Removed |Added CC||fclh...@yahoo.com --- Comment #1 from Nate Graham --- *** Bug 457211 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 457211] Network connections shows multiple false WiFi connecting states after user switch
https://bugs.kde.org/show_bug.cgi?id=457211 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 455180 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455507] Overview effect search box almost always causes hard system lockup
https://bugs.kde.org/show_bug.cgi?id=455507 --- Comment #8 from indecisiveautoma...@gmail.com --- Present Windows didn't cause any crash, and I was unable to run that command. It said "File Indexer already running". I'm not sure which process for baloo (if any) are safe to close, or if there is a proper command to stop and restart the file indexer. -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 457038] "It is better to fail in originality than to succeed in imitation."
https://bugs.kde.org/show_bug.cgi?id=457038 Ömer Fadıl USTA changed: What|Removed |Added Status|REPORTED|RESOLVED CC|nicolas.fe...@gmx.de, | |plasma-b...@kde.org | Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 457211] Network connections shows multiple false WiFi connecting states after user switch
https://bugs.kde.org/show_bug.cgi?id=457211 Nate Graham changed: What|Removed |Added Component|general |applet CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457272] Incorrect UI Element Padding under KDE with Breeze Theme at 1.5 scale
https://bugs.kde.org/show_bug.cgi?id=457272 --- Comment #4 from Maik Qualmann --- Look at the Kate session selection between the search input and the list view the same distance as in digiKam, in Kate itself again a 0 padding. As I said, it is our intention. I used to play in digiKam with a 0 padding a long time ago, but I didn't like it because the sidebar elements are closer to the thumbnails and previews. That looked "more confusing". Maybe we could reduce the top and bottom padding, I could test that again. Basically we use the padding recommended by Qt. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 457219] ki18n fail to build from source while QT5 is installed
https://bugs.kde.org/show_bug.cgi?id=457219 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- This is an issue with your local setup. Please ask for help in the #kde-devel chatroom on Matrix. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 457220] kdoctools fail to build
https://bugs.kde.org/show_bug.cgi?id=457220 Nate Graham changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #9 from Nate Graham --- > /home/elias/kde/build/kdoctools/bin/meinproc5: symbol lookup error: > /home/elias/kde/build/kdoctools/bin/meinproc5: undefined symbol: > _ZN18KCompressionDeviceC1ERK7QString This is an issue with your local setup. Please ask for help in the #kde-devel chatroom on Matrix. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 457221] Fails to open my project
https://bugs.kde.org/show_bug.cgi?id=457221 Ömer Fadıl USTA changed: What|Removed |Added Product|Spam|kdenlive Component|Spam|Effects & Transitions CC||omeru...@gmail.com Assignee|n...@kde.org|vpi...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457242] Option to add a fullscreen button to the titlebar
https://bugs.kde.org/show_bug.cgi?id=457242 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 CC||n...@kde.org Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456873] Unable to use activities since Plasma 5.25.0
https://bugs.kde.org/show_bug.cgi?id=456873 Nate Graham changed: What|Removed |Added CC||noah.slyker...@gmail.com --- Comment #8 from Nate Graham --- *** Bug 457253 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457253] Pinning apps on specific activity doesn't work
https://bugs.kde.org/show_bug.cgi?id=457253 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 456873 *** -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 457236] Dutch translation of "Adaptive" in plasma_shell_org.kde.plasma.desktop.pot isn't ideal
https://bugs.kde.org/show_bug.cgi?id=457236 Nate Graham changed: What|Removed |Added Component|general |nl Summary|Adaptive in |Dutch translation of |plasma_shell_org.kde.plasma |"Adaptive" in |.desktop.pot appears to |plasma_shell_org.kde.plasma |behave as Automatic |.desktop.pot isn't ideal Ever confirmed|0 |1 Version|5.25.3 |unspecified Target Milestone|1.0 |--- Status|REPORTED|CONFIRMED CC||n...@kde.org Assignee|plasma-b...@kde.org |kde-i18n...@kde.org Product|plasmashell |i18n --- Comment #3 from Nate Graham --- I agree that the English text is accurate enough here. Moving to i18n. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 457259] New bug reports product selection is hard to navigate
https://bugs.kde.org/show_bug.cgi?id=457259 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- See Bug 340420 and Bug 238608. Arbitrarily marking this as a duplicate of Bug 340420 since I can't mark one bug as a duplicate of two. *** This bug has been marked as a duplicate of bug 340420 *** -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340420] Make it easier to find components for common products
https://bugs.kde.org/show_bug.cgi?id=340420 Nate Graham changed: What|Removed |Added CC||serkon...@pm.me --- Comment #13 from Nate Graham --- *** Bug 457259 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457265] Improvement: configuring the digital clock in the panel should be done in the same way as for "spectacle"
https://bugs.kde.org/show_bug.cgi?id=457265 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC||n...@kde.org --- Comment #1 from Nate Graham --- This is already implemented: go to Date Format > Custom and then you can make it use whatever date string you want. The time string is not configurable this way because it would be too insane and impossible for us to control the layout in code regarding what goes where for all the different form factors the clock can take. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451590] Stutter on right-most screen of multi-screen setup when opening WindowHeap-based effects
https://bugs.kde.org/show_bug.cgi?id=451590 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #29 from Nate Graham --- Awesome, let's call it fixed! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] Old behavior of klipper: When only mouse-selected text gets into the history.
https://bugs.kde.org/show_bug.cgi?id=457266 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Can you clarify what exactly the old behavior was, and what you can't do anymore? Is there no setting to re-enable the behavior you aren't able to use? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451590] Stutter on right-most screen of multi-screen setup when opening WindowHeap-based effects
https://bugs.kde.org/show_bug.cgi?id=451590 --- Comment #28 from Eric Edlund --- The stutter is gone on master for me (wooo hooo) 10th gen intel i7 integrated graphics -- You are receiving this mail because: You are watching all bug changes.
