[kontact] [Bug 453330] Scroll down with mousepad not working in mail and news text view component
https://bugs.kde.org/show_bug.cgi?id=453330 Martin Tlustos changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Martin Tlustos --- Works again. Closing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454373] New: dolphin: "Create New" context menu entry disabled after performing a search
https://bugs.kde.org/show_bug.cgi?id=454373
Bug ID: 454373
Summary: dolphin: "Create New" context menu entry disabled
after performing a search
Product: dolphin
Version: 22.04.1
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: search
Assignee: dolphin-bugs-n...@kde.org
Reporter: serkon...@pm.me
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When performing a search for files or folders the context menu entry "Create
new" is disabled.
This affects all tabs open at the moment of search.
The error cannot be resolved by restarting, thus it's somewhat persistent.
WORKAROUNDS
- open a new tab
- go back and forth in any tab already open
STEPS TO REPRODUCE
1. Press 'ctrl-f' and enter any search term
2. Start the search with 'enter'
3. Open the context menu via right click in any folder
4. Notice the disabled entry 'Create new' ('F10' shortcut also not working
anywhere)
OBSERVED RESULT
Cannot create new files.
EXPECTED RESULT
Creating new files working fine in all tabs except the search results.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 5.17.9-arch.1
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94
Qt Version: 5.15.4
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 443500] White icon for dark windows theme
https://bugs.kde.org/show_bug.cgi?id=443500 1justinpe...@gmail.com changed: What|Removed |Added CC||1justinpe...@gmail.com --- Comment #1 from 1justinpe...@gmail.com --- Created attachment 149195 --> https://bugs.kde.org/attachment.cgi?id=149195=edit This is what the taskbar icon looks like now -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 454355] Chennai Escorts
https://bugs.kde.org/show_bug.cgi?id=454355 Bacteria changed: What|Removed |Added Version|5.20.0 |unspecified Component|Birthdays Resource |Spam Assignee|kdepim-b...@kde.org |n...@kde.org Product|Akonadi |Spam -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454365] Overview touchpad gesture not working correctly.
https://bugs.kde.org/show_bug.cgi?id=454365 Bacteria changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dev.bacterios...@aleeas.com Resolution|--- |NOT A BUG --- Comment #1 from Bacteria --- What you are seeing by swiping 4 fingers down is "Present Windows effect" which is different from "Overview effect". For overview effect the gesture is 4 finger pinch. You would want to set 4 finger swipe down as overview but configuration of gestures isn't coming in 5.25. Hopefully it should land in 5.26. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454175] Panel popups' transparency status is reversed when a window is maximized
https://bugs.kde.org/show_bug.cgi?id=454175 Bacteria changed: What|Removed |Added CC||31...@tuta.io --- Comment #7 from Bacteria --- *** Bug 454371 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454371] Plasmoid adaptive transoarency behaviour inconsistent
https://bugs.kde.org/show_bug.cgi?id=454371 Bacteria changed: What|Removed |Added CC||dev.bacterios...@aleeas.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Bacteria --- *** This bug has been marked as a duplicate of bug 454175 *** -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 454372] Proposal: switch to the cherry-pick backwards workflow
https://bugs.kde.org/show_bug.cgi?id=454372 --- Comment #1 from tr...@yandex.com --- +1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452919] Thumbnails not showing for any files (documents, images, videos)
https://bugs.kde.org/show_bug.cgi?id=452919 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|DUPLICATE |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.
[kwin] [Bug 447680] Crash in DrmPipeline::applyPendingChangesLegacy()
https://bugs.kde.org/show_bug.cgi?id=447680 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #12 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.
[plasmashell] [Bug 452976] Plasma crash report but nothing wrong
https://bugs.kde.org/show_bug.cgi?id=452976 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452959] Date & Time component not reading format from Formats component
https://bugs.kde.org/show_bug.cgi?id=452959 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.
[Elisa] [Bug 454372] Proposal: switch to the cherry-pick backwards workflow
https://bugs.kde.org/show_bug.cgi?id=454372 Nate Graham changed: What|Removed |Added CC||hanyo...@protonmail.com, ||kosse...@kde.org, ||mon...@kde.org, ||tr...@yandex.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 454372] New: Proposal: switch to the cherry-pick backwards workflow
https://bugs.kde.org/show_bug.cgi?id=454372 Bug ID: 454372 Summary: Proposal: switch to the cherry-pick backwards workflow Product: Elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: task Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: n...@kde.org Target Milestone: --- Historically, Elisa has used a workflow whereby merge requests/commits are landed on either the master branch or the stable branch, and if the target was the stable branch because it was a bugfix, that branch is merged forward into master. A few years ago, Plasma moved to a different workflow whereby all merge requests/commits are landed on the master branch, and cherry-picked backwards into the stable branch as needed. Having used both approaches for a few years, I find that overall the cherry-pick workflow seems to reduce friction: 1. No more asking the submitter to change the target branch of their MR if it's a bugfix 2. No more manual merging, which means no more annoying merge conflicts in the `CMakeLists.txt` file after every branching event 3. You can cherry-pick right form the GitLab web UI, which is nice and fast and you don't have to leave the website after merging using the website I'd like to formally propose that we adopt it in Elisa. Matthieu Gallien is Elisa's formal maintainer, but he has not been active recently so I'm also CCing the top five contributors by number of lines added over the past year according to GitHub (https://github.com/KDE/gwenview/graphs/contributors?from=2021-05-24=2022-05-24=c, which has better tools for visualizing this compared to GitLab): Me, Tranter Madi, Han Young, Friedrich Kossebau, and Laurent Montel. What say ye? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441297] kwin_wayland crashed in KWin::EglGbmBackend::removeOutput() when I tried to run Opera browser natively on Wayland
https://bugs.kde.org/show_bug.cgi?id=441297 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.
[plasmashell] [Bug 433073] Pinned applications immediately terminate upon launch if launched from pinned icon.
https://bugs.kde.org/show_bug.cgi?id=433073 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[plasma-pa] [Bug 453583] Waydroid Audio Not Recognized
https://bugs.kde.org/show_bug.cgi?id=453583 --- Comment #9 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.
[kde] [Bug 453486] The mouse scroll wheel randomly stops working
https://bugs.kde.org/show_bug.cgi?id=453486 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453400] shortcuts are not saved
https://bugs.kde.org/show_bug.cgi?id=453400 --- 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 453425] [wayland] latte does not show on startup
https://bugs.kde.org/show_bug.cgi?id=453425 --- Comment #7 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.
[amarok] [Bug 452319] Configure Podcasts crashes amarok
https://bugs.kde.org/show_bug.cgi?id=452319 --- 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 452062] Xwayland app doesn't launch in Wayland KDE 5.24.5
https://bugs.kde.org/show_bug.cgi?id=452062 --- Comment #25 from McCak --- I am surprised this is actually a XWayland bug instead of KWIN itself.. because other DE with Wayland Functionality seems fine.. Anyway thank you for giving some info.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391956] Maximized windows too small when scaling is applied on X11
https://bugs.kde.org/show_bug.cgi?id=391956
--- Comment #25 from Jin Liu ---
I did some debugging on https://bugs.kde.org/show_bug.cgi?id=445741, which
might be relevant here. But I don't know much about kwin, so it's only wild
guesses:
In X11, kwin seems to force window size to be rounded to the "resize increment"
in WM_SIZE_HINTS, in various places.
The code is in X11Window::constrainClientSize:
https://invent.kde.org/plasma/kwin/-/blob/68f6734d5cf758004c3328777dbf66fe9113b4d6/src/x11window.cpp#L3551
>int width_inc = m_geometryHints.resizeIncrements().width();
>int height_inc = m_geometryHints.resizeIncrements().height();
>int basew_inc = m_geometryHints.baseSize().width();
>int baseh_inc = m_geometryHints.baseSize().height();
>if (!m_geometryHints.hasBaseSize()) {
>basew_inc = m_geometryHints.minSize().width();
>baseh_inc = m_geometryHints.minSize().height();
>}
>w = int((w - basew_inc) / width_inc) * width_inc + basew_inc;
>h = int((h - baseh_inc) / height_inc) * height_inc + baseh_inc;
In my laptop, the screen size is 3200x2000, KDE's global scaling set to 250%.
Then all KDE apps have "resize increment"=3 in WM_SIZE_HINTS, where all Gnome
apps seem to have "resize increment"=2, and other apps (e.g. vscode) don't have
it at all.
This causes the "fullscreen" window menu in all KDE apps grayed out, because of
this check in X11Window::isFullScreenable:
https://invent.kde.org/plasma/kwin/-/blob/68f6734d5cf758004c3328777dbf66fe9113b4d6/src/x11window.cpp#L1284
>if (rules()->checkStrictGeometry(true)) {
>// check geometry constraints (rule to obey is set)
>const QRect fullScreenArea = workspace()->clientArea(FullScreenArea,
> this);
>const QSize constrainedClientSize =
> constrainClientSize(fullScreenArea.size());
>if (rules()->checkSize(constrainedClientSize) !=
> fullScreenArea.size()) {
>return false; // the app wouldn't fit exactly fullscreen geometry
> due to its strict geometry requirements
>}
>}
Since my screen resolution is not multiple of 3, KDE apps are not allowed to
fullscreen.
And for this bug, in my laptop, all KDE apps, when launched maximized, the
window won't cover the top-right pixel. Clicking on that pixel closes the
window behind. However, if I restore that window then maximize again, it works
OK.
My guess is X11Window::manage also calls X11Window::constrainClientSize:
https://invent.kde.org/plasma/kwin/-/blob/68f6734d5cf758004c3328777dbf66fe9113b4d6/src/x11window.cpp#L694
So if the desktop area (fullscreen excluding panel) is not multiple of 3, KDE
apps won't exactly cover the whole desktop area when launched maximized.
In my case, both problems can be worked around by creating a window rule: "for
all windows, force disable Strict Geometry", which bypasses
constrainClientSize.
This also explains why Wayland doesn't have these problems, because it uses the
generic Window::constrainClientSize, which doesn't do rounding at all.
Hope this helps.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 454308] Don't let the properties window be maximized
https://bugs.kde.org/show_bug.cgi?id=454308 --- Comment #2 from saxn --- (In reply to Nate Graham from comment #1) > Being unable to minimize would drive people crazy. But limiting the ability > to maximize small dialog windows could conceivably make sense. > > This would need to be done on a window-by-window basis though. Please file a > separate bug report on each window you think should not be maximizable. We > can use this one for the properties window yes, some window is shown in latte dock when you minimize but some window don't. If it is shown in latte dock it should have a minimize button if don't we shouldn't. For example About KDE window, even we minimize the window it is not shown in latte dock so, why bother adding minimize button ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 --- Comment #4 from Tracy Poff --- This bug persists with KDE Frameworks version 5.94.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446637] QML timers linked to monitor refresh rate with AMD GPU
https://bugs.kde.org/show_bug.cgi?id=446637 --- Comment #23 from pqwoerituytruei...@gmail.com --- doubt it is graphics drivers, it affects nvidia (nouveau), amd, and intel maybe someone can test this on a raspberry pi? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453206] Paste option in context menu does not work in details mode
https://bugs.kde.org/show_bug.cgi?id=453206 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #5 from vindicator --- I have that same experience and also noticed that if the folder has other folders as well and you context-menu in an open area for any of the folders (instead of files), the paste option will show. So for now, I have to have the destination folder open in another tab and drag it there, or just use the shortcut CTRL+V which is probably better to do anyway except for needing to switch between keyboard/mouse. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454095] Active Window Control "Fill width" feature now moves all the widgets next to the Active Window Control out of reach
https://bugs.kde.org/show_bug.cgi?id=454095 Fushan Wen changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Fushan Wen --- Can reproduce. BTW the applet should be submitted to upstream. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447191] Inconsistent tooltip for ‘Target Size’ in WebP export dialogue
https://bugs.kde.org/show_bug.cgi?id=447191 amyspark changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/d25458308 |hics/krita/commit/1cd2377ce |0520760f8347f1ea03d70f3cce4 |4d521c8da80d025b531650afad2 |23dc|0baa --- Comment #3 from amyspark --- Git commit 1cd2377ce4d521c8da80d025b531650afad20baa by L. E. Segovia. Committed on 25/05/2022 at 01:03. Pushed by lsegovia into branch 'krita/5.0'. Fix suffix of "target size" in WebP (cherry picked from commit d254583080520760f8347f1ea03d70f3cce423dc) M +1-1plugins/impex/webp/dlg_webp_export.ui https://invent.kde.org/graphics/krita/commit/1cd2377ce4d521c8da80d025b531650afad20baa -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447191] Inconsistent tooltip for ‘Target Size’ in WebP export dialogue
https://bugs.kde.org/show_bug.cgi?id=447191 amyspark changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/d25458308 ||0520760f8347f1ea03d70f3cce4 ||23dc Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from amyspark --- Git commit d254583080520760f8347f1ea03d70f3cce423dc by L. E. Segovia. Committed on 25/05/2022 at 01:00. Pushed by lsegovia into branch 'master'. Fix suffix of "target size" in WebP M +1-1plugins/impex/webp/dlg_webp_export.ui https://invent.kde.org/graphics/krita/commit/d254583080520760f8347f1ea03d70f3cce423dc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454105] plasma panel widgets disappear/get misplaced after plasmashell restart if application icons are present in panel
https://bugs.kde.org/show_bug.cgi?id=454105 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454105] plasma panel widgets disappear/get misplaced after plasmashell restart if application icons are present in panel
https://bugs.kde.org/show_bug.cgi?id=454105 NoWorries changed: What|Removed |Added CC||colegrove...@gmail.com --- Comment #11 from NoWorries --- I have also experienced this problem and the only way to totally get around it is to make my desktop look like a Windows 10 desktop which is full of icons to launch applications. A partial compromise is to create 3 blank empty panels at the top of the screen, one centre, one left and the other right. Each contains one of my most frequently used applications. This approach can also be used on the left and right edges of the screen to make a total of 9 applications that can be launched easily. I hope his bug is easily fixed without having to use the above deviant approach. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #20 from Eric R --- When I did the update yesterday, I noticed that kwin-x11 got uninstalled. So I re-installed it. Now everything seems to be back to normal on an X11 session in Neon. In case it helps someone, here is what I did: sudo apt update; sudo apt install neon-desktop; sudo apt full-upgrade sudo apt install kwin-x11 sudo reboot now Please let me know if I can provide any more information. Thanks Jonathan and everyone! (In reply to Eric R from comment #19) > Jonathan, > > I tried this, and it didn’t help. The windows still don’t have title bars. > > What else can I try, or what other info can I gather? > > Thanks! > -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445955] paring keys dont match
https://bugs.kde.org/show_bug.cgi?id=445955 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/network/kdeconnect-android/-/merge_requests/286 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454149] Breeze buttons on logout screen do not properly inherit color scheme
https://bugs.kde.org/show_bug.cgi?id=454149 doncb...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #2 from doncb...@gmail.com --- (In reply to Nate Graham from comment #1) > Does it fix itself if you clear the Plasma SVG cache with `rm > ~/.cache/*plasma* ; plasmashell --replace`? Indeed it seems to. What's odd is the consistency of it. This feels like when a color compatible Plasma theme wouldn't update when you changed the color scheme until you reapplied the Plasma theme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450488] Wayland - turning DP monitor off and back on causes plasmashell hang
https://bugs.kde.org/show_bug.cgi?id=450488 --- Comment #7 from g...@section9.follonica.org --- (In reply to goo from comment #6) > (In reply to goo from comment #5) > > I have a similar problem starting from plasma 5.24.90, running on X11, not > > wayland. > > plasmashell and ui interaction hangs randomly. > > I have a bunch of: > > > > mag 25 01:30:20 darkgoo plasmashell[2070446]: requesting unexisting screen > > -1 > > > > If I disable compositing and re-enable it then it works for a while. > > Prior to upgrading to plasma 5.24.90 I never had this sort of problem. > > > > Running Fedora 36 - four monitor setup. > > Forgot to say that my primary screen is a DP monitor. Other logs that might be useful: mag 25 01:44:36 darkgoo plasmashell[2070446]: requesting unexisting screen -1 mag 25 01:44:36 darkgoo plasmashell[2070446]: requesting unexisting screen -1 mag 25 01:44:36 darkgoo plasmashell[2070446]: requesting unexisting screen -1 mag 25 01:44:36 darkgoo plasmashell[2070446]: requesting unexisting screen -1 mag 25 01:44:36 darkgoo plasmashell[2070446]: requesting unexisting screen -1 mag 25 01:44:36 darkgoo plasmashell[2070446]: requesting unexisting screen -1 mag 25 01:44:37 darkgoo baloo_file_extractor[2697474]: Qt: Session management error: Could not open network socket mag 25 01:44:38 darkgoo kwin_x11[2070413]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 49005, resource id: 138412038, major code: 18 (ChangeProperty), minor code: 0 mag 25 01:44:39 darkgoo baloo_file_extractor[2697494]: Qt: Session management error: Could not open network socket mag 25 01:44:40 darkgoo kwin_x11[2070413]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 49768, resource id: 138412038, major code: 18 (ChangeProperty), minor code: 0 mag 25 01:44:54 darkgoo kwin_x11[2070413]: kwin_core: Client KWin::X11Window(0x561ab4c54880, windowId=0x860d5f3, caption="Aggiungi etichetta", transientFor=KWin::X11Window(0x561ab570e5c0, windowId=0x8600107, caption="* Java OpenStreetMap Editor")) caused WM_TRANSIENT_FOR loop. mag 25 01:44:54 darkgoo plasmashell[2070446]: QXcbClipboard::setMimeData: Cannot set X11 selection owner mag 25 01:44:54 darkgoo plasmashell[2070446]: QXcbClipboard::setMimeData: Cannot set X11 selection owner mag 25 01:44:55 darkgoo plasmashell[2070446]: QXcbClipboard::setMimeData: Cannot set X11 selection owner mag 25 01:44:56 darkgoo plasmashell[2070446]: QXcbClipboard::setMimeData: Cannot set X11 selection owner mag 25 01:44:57 darkgoo plasmashell[2070446]: QXcbClipboard::setMimeData: Cannot set X11 selection owner mag 25 01:44:57 darkgoo plasmashell[2070446]: QXcbClipboard::setMimeData: Cannot set X11 selection owner mag 25 01:45:02 darkgoo kwin_x11[2070413]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11177, resource id: 138412038, major code: 18 (ChangeProperty), minor code: 0 mag 25 01:45:08 darkgoo kwin_x11[2070413]: kwin_core: Client KWin::X11Window(0x561ab66eb2c0, windowId=0x860d6bc, caption="Aggiungi etichetta", transientFor=KWin::X11Window(0x561ab570e5c0, windowId=0x8600107, caption="* Java OpenStreetMap Editor")) caused WM_TRANSIENT_FOR loop. mag 25 01:45:12 darkgoo kwin_x11[2070413]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28453, resource id: 140564156, major code: 20 (GetProperty), minor code: 0 mag 25 01:45:12 darkgoo kwin_x11[2070413]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28460, resource id: 140564156, major code: 20 (GetProperty), minor code: 0 mag 25 01:45:12 darkgoo kwin_x11[2070413]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28466, resource id: 140564156, major code: 20 (GetProperty), minor code: 0 mag 25 01:45:12 darkgoo kwin_x11[2070413]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28471, resource id: 140564156, major code: 15 (QueryTree), minor code: 0 mag 25 01:45:14 darkgoo kwin_x11[2070413]: kwin_core: Client KWin::X11Window(0x561ab66eb2c0, windowId=0x860d6cc, caption="Aggiungi etichetta", transientFor=KWin::X11Window(0x561ab570e5c0, windowId=0x8600107, caption="* Java OpenStreetMap Editor")) caused WM_TRANSIENT_FOR loop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454371] New: Plasmoid adaptive transoarency behaviour inconsistent
https://bugs.kde.org/show_bug.cgi?id=454371 Bug ID: 454371 Summary: Plasmoid adaptive transoarency behaviour inconsistent Product: plasmashell Version: 5.24.90 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: 31...@tuta.io CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 149194 --> https://bugs.kde.org/attachment.cgi?id=149194=edit Kickoff is opaque when it shouldn't be SUMMARY *** Plasmoids decide seemingly at random wether to be translucent or opaque. Not even explicitly setting the panel to opaque in edit mode works reliably. One pattern I've noticed is that when adaptive transparency is on and I maximize a window, the panel gets opaque and the plasmoids get translucent (if they weren't already) unmaximising the window sets the panel back to translucent, but the plasmoids to opaque. The plasmoids are doing exactly the opposite of what they're supposed to do. STEPS TO REPRODUCE 1. Maximize window 2. Minimize window 3. Open kickoff, sys tray, whatever OBSERVED RESULT Kickoff is opaque, panel is translucent EXPECTED RESULT When panel is translucent, plasmoids are translucent. When panel is opaque, plasmoids are opaque SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 +marcdeop's copr KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450488] Wayland - turning DP monitor off and back on causes plasmashell hang
https://bugs.kde.org/show_bug.cgi?id=450488 --- Comment #6 from g...@section9.follonica.org --- (In reply to goo from comment #5) > I have a similar problem starting from plasma 5.24.90, running on X11, not > wayland. > plasmashell and ui interaction hangs randomly. > I have a bunch of: > > mag 25 01:30:20 darkgoo plasmashell[2070446]: requesting unexisting screen -1 > > If I disable compositing and re-enable it then it works for a while. > Prior to upgrading to plasma 5.24.90 I never had this sort of problem. > > Running Fedora 36 - four monitor setup. Forgot to say that my primary screen is a DP monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450488] Wayland - turning DP monitor off and back on causes plasmashell hang
https://bugs.kde.org/show_bug.cgi?id=450488 g...@section9.follonica.org changed: What|Removed |Added CC||g...@section9.follonica.org --- Comment #5 from g...@section9.follonica.org --- I have a similar problem starting from plasma 5.24.90, running on X11, not wayland. plasmashell and ui interaction hangs randomly. I have a bunch of: mag 25 01:30:20 darkgoo plasmashell[2070446]: requesting unexisting screen -1 If I disable compositing and re-enable it then it works for a while. Prior to upgrading to plasma 5.24.90 I never had this sort of problem. Running Fedora 36 - four monitor setup. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #19 from Eric R --- Jonathan, I tried this, and it didn’t help. The windows still don’t have title bars. What else can I try, or what other info can I gather? Thanks! (In reply to Eric R from comment #16) > FWIW, it wasn’t just you and me. There were some other comments about this > in r/kdeneon on Reddit. > > I’ll try this when I get home from work. > > Thanks Peter and Jonathan! > > (In reply to Peter from comment #13) > > What was it about our set ups that meant only Eric and me were seeing this > > problem? Also, is there anywhere the intelligent layman can read about > > what lcms does? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454370] New: Cannot drag and drop in some scenarios Using Wayland (Wine windows apps & Unreal engine)
https://bugs.kde.org/show_bug.cgi?id=454370 Bug ID: 454370 Summary: Cannot drag and drop in some scenarios Using Wayland (Wine windows apps & Unreal engine) Product: dolphin Version: 22.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: xdm.corporat...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Run under wayland 2. Launch a windows app via wine 3. try to drag and drop content to that windows app OBSERVED RESULT open dragged content into app EXPECTED RESULT Nothing happens SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION when opening app via terminal i can see these lines of code display when i try yo drag and drop this line is spammed tons of times as you move the mouse across the app 0118:fixme:shell:IDropTargetHelper_fnDragOver (13236210)->(0011ED18 0x) and this one shows once when you try to drop 0118:fixme:shell:IDropTargetHelper_fnDrop (13236210)->(7F8EF4484F08 0011EBE8 0x0001) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453947] GMIC:Preview window exception
https://bugs.kde.org/show_bug.cgi?id=453947 --- Comment #4 from amyspark --- Interesting bug! It stretches to the introduction of the G'MIC-Qt plugin itself, back in 3.0.3: https://invent.kde.org/graphics/krita/-/commit/463213b8e04311f5c7f7c41e24cc198c5a98fb87 What is happening is that the image size command never accounted, in our side, for the layer mode; so we returned the image size each time. This is incorrect whenever a smaller layer is active, so in these cases the preview widget would have inconsistent behaviour due to the mismatching sizes. I also ported this behaviour blindly when I wrote the QMic interface, so this will require an ABI break. I'll add a version definition to the header to help things in the other side, and roll this fix up together with the translations. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453947] GMIC:Preview window exception
https://bugs.kde.org/show_bug.cgi?id=453947 amyspark changed: What|Removed |Added URL|https://github.com/c-koi/gm |https://github.com/amyspark |ic-qt/issues/145|/gmic/commit/9d7fcf3d2a245d ||467827716369b411c232a1981c -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 293888] Poor performance with mounted network locations
https://bugs.kde.org/show_bug.cgi?id=293888 flan_suse changed: What|Removed |Added CC||windows2li...@zoho.com --- Comment #39 from flan_suse --- (In reply to grannie from comment #38) > I just hit this bug when using VirtualBox (choosing an Iso image for a VM). > Are there any updates on this? It's only been 10 years. Quit being so impatient. ;) KDialog continues to be the slow bottleneck on my otherwise fast system. GTK file chooser runs laps around it. Generic Qt file chooser runs laps around it. KDialog is hilariously slow, even for local filesystems. (Slow for network locations *and* local. It's just more noticeable for network shares.) What is KDialog even doing in the background? Examining every single file inside the current directory or something? Listing the contents of a folder should be a smooth process, just like we experience with GTK file chooser, or heck, using the terminal. I'm not even using thumbnail previews, and it's still crawls with KDialog. One workaround I found in the meantime is to trick applications into using the GTK file chooser instead, but this doesn't work across the board. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454359] Crop handle uses wrong cursor
https://bugs.kde.org/show_bug.cgi?id=454359 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454028] application launcher (cascading) broken
https://bugs.kde.org/show_bug.cgi?id=454028 --- Comment #8 from David Chmelik --- You can see the menu is scrolled down past the end of everything starting with 'a' to standard preinstalled KDE stuff, but this style menu used to open another box to the right, or continue indefinitely, until your list was done, instead of forcing scroll (slower.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454361] (SIGFPE) kwin_wayland crashed in KWin::X11Window::constrainClientSize
https://bugs.kde.org/show_bug.cgi?id=454361 Aleix Pol changed: What|Removed |Added CC||aleix...@kde.org --- Comment #5 from Aleix Pol --- I cannot reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454026] can't turn off application menu translucency
https://bugs.kde.org/show_bug.cgi?id=454026 --- Comment #6 from David Chmelik --- Created attachment 149193 --> https://bugs.kde.org/attachment.cgi?id=149193=edit screen photo Logic errors. Again, I reported this when I was using KDE and want to switch back, and still use KDE software (family PC is fast enough for KDE, and I use KDE programs, just not KDE itself.) You can see Konqueror text under application launcher, make it all somewhat unreadable. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454028] application launcher (cascading) broken
https://bugs.kde.org/show_bug.cgi?id=454028 --- Comment #7 from David Chmelik --- Created attachment 149192 --> https://bugs.kde.org/attachment.cgi?id=149192=edit screen photo Logic errors. Again, I reported this when I was using KDE and want to switch back, and still use KDE software (family PC is fast enough for KDE, and I use KDE programs, just not KDE itself.) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 407195] implementation/realisation association depends on class name
https://bugs.kde.org/show_bug.cgi?id=407195 Oliver Kellogg changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||okellogg@users.sourceforge. ||net -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454028] application launcher (cascading) broken
https://bugs.kde.org/show_bug.cgi?id=454028 --- Comment #6 from David Chmelik --- Created attachment 149191 --> https://bugs.kde.org/attachment.cgi?id=149191=edit screen photo I used exact term 'application launcher' in panel widget menu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454357] Allow for column padding to the 'right'
https://bugs.kde.org/show_bug.cgi?id=454357 BEEDELL ROKE JULIAN LOCKHART changed: What|Removed |Added CC||beedellrokejulianlockhart@g ||mail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from BEEDELL ROKE JULIAN LOCKHART --- This has been added. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 robin+kdeb...@rkslot.nl changed: What|Removed |Added CC||robin+kdeb...@rkslot.nl --- Comment #24 from robin+kdeb...@rkslot.nl --- I am also running into this issue with two mice. My desktop computer is a qemu/libvirt/kvm virtual machine, which means it has my real passed through USB mouse but by default also an emulated PS/2 mouse. Whenever I unplug my USB mouse and plug it back in, settings like pointer acceleration reset. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 337653] Changed a value in a structure view isn't shown after submitting
https://bugs.kde.org/show_bug.cgi?id=337653 Friedrich W. H. Kossebau changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Version Fixed In||0.26.9 Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/e86a5b4 ||59f6ea3b43d94223183e4a60695 ||b31a62 --- Comment #5 from Friedrich W. H. Kossebau --- Git commit e86a5b459f6ea3b43d94223183e4a60695b31a62 by Friedrich W. H. Kossebau. Committed on 23/05/2022 at 14:23. Pushed by kossebau into branch '0.26'. Structures tool: properly update tree view after committing a change FIXED-IN: 0.26.9 M +9-4kasten/controllers/view/structures/structurestool.cpp M +1-0kasten/controllers/view/structures/structurestool.hpp https://invent.kde.org/utilities/okteta/commit/e86a5b459f6ea3b43d94223183e4a60695b31a62 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 420073] Umbrello does not show aggregation association
https://bugs.kde.org/show_bug.cgi?id=420073 Oliver Kellogg changed: What|Removed |Added CC||dvd2g...@yandex.ru --- Comment #3 from Oliver Kellogg --- *** Bug 452521 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 452521] I can't add an abstraction arrow. Instead, an extra entry appears in the chart
https://bugs.kde.org/show_bug.cgi?id=452521 Oliver Kellogg changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||okellogg@users.sourceforge. ||net --- Comment #1 from Oliver Kellogg --- *** This bug has been marked as a duplicate of bug 420073 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 Andrey changed: What|Removed |Added CC||aleix...@kde.org --- Comment #16 from Andrey --- (In reply to stalkermar from comment #15) > There was a widget called Input Method. And as soon as I removed it from the > panel, everything just started working again. I'm sure I didn't add it, the > thing have just appeared on me after the update. No matter how many times I > close it, the thing just re-appears after a reboot. Input Method is the usual source of such problems. But I completely unaware how it was introduced and why it re-appears. You can try forcibly disable the applet in Systray settings. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 454369] New: Yakuake doesn't respect setting
https://bugs.kde.org/show_bug.cgi?id=454369 Bug ID: 454369 Summary: Yakuake doesn't respect setting Product: yakuake Version: 22.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: he...@mattiasagar.com Target Milestone: --- Created attachment 149190 --> https://bugs.kde.org/attachment.cgi?id=149190=edit Video showing the issue SUMMARY I have a multi monitor setup I'm experiencing this weird behaviour with deciding on which monitor Yakuake should open on. It doesn't respect the quick option when setting it to 'Screen 1'. STEPS TO REPRODUCE 1. Go to quick options 2. Set 'Screen' to 'Screen 1' 3. Use hotkey to bring up Yakuake, setting is still at 'Screen 1' 4. Hotkey again to hide Yakuake 5. Hotkey again to bring up Yakuake, setting is now at "on mouse location" OBSERVED RESULT Yakuake changing setting from 'Screen 1' to 'On mouse location' after second toggle EXPECTED RESULT Should respect the setting SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux version 5.17.5-arch1-1 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454349] Searching for something automatically selects the second item instead of the first
https://bugs.kde.org/show_bug.cgi?id=454349 Joshua T changed: What|Removed |Added Ever confirmed|0 |1 CC||joshuaandre...@gmail.com Status|REPORTED|CONFIRMED --- Comment #2 from Joshua T --- I have experienced this on Arch with Plasma 5.24.90 beta. It seemed to go away after an update. Try updating with "sudo pacman -Syuu". I also disabled the "Desktop Search" application launcher plugin, so that may have fixed the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454367] Reboot/shutdown triggered while data transfer to usb device is in progress is delayed
https://bugs.kde.org/show_bug.cgi?id=454367 --- Comment #1 from Patrick Silva --- >From the end user point of view, 'Copying (Finished)' notification indicates that the data transfer was completed. Therefore, it's not clear why the reboot/shutdown is delayed after the provided steps. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454319] Basic Plasma problems after May 23 update
https://bugs.kde.org/show_bug.cgi?id=454319 --- Comment #18 from O.C.Nilsen --- So, logging in to a Plasma Wayland session works, but x11 doesn't. No titlebars or borders on windows, no compositing. Right-click menus disappear. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454368] Time line size ajustment
https://bugs.kde.org/show_bug.cgi?id=454368 --- Comment #2 from Cristino Nicolau Canga --- Comment on attachment 149189 --> https://bugs.kde.org/attachment.cgi?id=149189 Audio Mixer Interface Broken STEPS TO REPRODUCE 1. Open Kdenlive 2. Trying to resize the timeLine OBSERVED RESULT The audio mixer is locked, and doesn't allow the resizement of timeLine window EXPECTED RESULT The TimeLine should be ajustable by dragging it to the right ADDITIONAL INFORMATION The timeLine resizement works when the audio mixer is disabled in the "view" tab( in portuguese "ver") -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454368] Time line size ajustment
https://bugs.kde.org/show_bug.cgi?id=454368 --- Comment #1 from Cristino Nicolau Canga --- Comment on attachment 149189 --> https://bugs.kde.org/attachment.cgi?id=149189 Audio Mixer Interface Broken STEPS TO REPRODUCE 1. Open Kdenlive 2. Trying to resize the timeLine OBSERVED RESULT The audio mixer is locked, and doesn't allow the resizement of timeLine window EXPECTED RESULT The TimeLine should be ajustable by dragging it to the right ADDITIONAL INFORMATION The timeLine resizement works when the audio mixer is disabled in the "view" tab( in portuguese "ver") -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454368] New: Time line size ajustment
https://bugs.kde.org/show_bug.cgi?id=454368 Bug ID: 454368 Summary: Time line size ajustment Product: kdenlive Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: cristinocan...@gmail.com Target Milestone: --- Created attachment 149189 --> https://bugs.kde.org/attachment.cgi?id=149189=edit Audio Mixer Interface Broken STEPS TO REPRODUCE 1. Open Kdenlive 2. Trying to resize the timeLine OBSERVED RESULT The audio mixer is locked, and doesn't allow the resizement of timeLine window EXPECTED RESULT The TimeLine should be ajustable by dragging it to the right ADDITIONAL INFORMATION The timeLine resizement works when the audio mixer is disabled in the "view" tab( in portuguese "ver") -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454367] New: Reboot/shutdown triggered while data transfer to usb device is in progress is delayed
https://bugs.kde.org/show_bug.cgi?id=454367 Bug ID: 454367 Summary: Reboot/shutdown triggered while data transfer to usb device is in progress is delayed Product: plasmashell Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 STEPS TO REPRODUCE 1. connect a usb flash drive to usb port 2. copy a big file (I have used a 867 MiB video file in my test) to your flash drive 3. wait for 'Copying (Finished)' notification from Plasma 4. try to reboot or shutdown you computer OBSERVED RESULT my system goes to TYY, systemd says 'A stop job is running for Disk Manager (1min 30s countdown)' and the reboot/shutdown is delayed EXPECTED RESULT I'm not sure. Maybe Plasma could prevent reboot/shutdown until the data transfer is completed giving us feedback about it SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454366] Dolphin crashes when ejecting a data CD while browsing it
https://bugs.kde.org/show_bug.cgi?id=454366 --- Comment #1 from B. Kühnel --- Created attachment 149188 --> https://bugs.kde.org/attachment.cgi?id=149188=edit output from cd-info -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454366] New: Dolphin crashes when ejecting a data CD while browsing it
https://bugs.kde.org/show_bug.cgi?id=454366 Bug ID: 454366 Summary: Dolphin crashes when ejecting a data CD while browsing it Product: dolphin Version: 21.12.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kuehnel.b.kdeb...@allchangeplease.de CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.12.3) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.17.9-gentoo x86_64 Windowing System: Wayland Distribution: "Gentoo Base System release 2.7" DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: An ISO 9660 + Joliet CD was mounted through Dolphin. The file listing is still opened in the current tab (crash does not happen when Dolphin is pointed to any other directory before the following steps). While the file listing of the CD is visible, in the "Places" bar right-click on the removable media and select "Eject". Observe that the medium is not ejected from the drive and that Dolphin crashes. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7feb381ba1c9 in Solid::StorageAccess::filePath (this=0x0) at /var/tmp/portage/kde-frameworks/solid-5.92.0/work/solid-5.92.0/src/solid/devices/frontend/storageaccess.cpp:52 #5 0x56287d6abb71 in PlacesItemModel::slotStorageTearDownDone (this=0x56287f0f21a0, error=2104146480, errorData=...) at /var/tmp/portage/kde-apps/dolphin-21.12.3/work/dolphin-21.12.3/src/panels/places/placesitemmodel.cpp:454 #6 0x7feb369cee06 in QtPrivate::QSlotObjectBase::call (a=0x7ffcabb16300, r=0x56287f0f21a0, this=0x562881a0c970) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x5628818ded90, signal_index=4, argv=0x7ffcabb16300) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:3886 #8 0x7feb381a09bb in Solid::OpticalDrive::ejectDone (this=, _t1=, _t2=..., _t3=...) at /var/tmp/portage/kde-frameworks/solid-5.92.0/work/solid-5.92.0_build/src/solid/KF5Solid_autogen/H3VFCUX2PL/moc_opticaldrive.cpp:295 #9 0x7feb381a8ab9 in Solid::OpticalDrive::qt_static_metacall (_o=0x7ffcabb161c0, _c=, _id=-1414438064, _a=0x7ffcabb16490) at /var/tmp/portage/kde-frameworks/solid-5.92.0/work/solid-5.92.0_build/src/solid/KF5Solid_autogen/H3VFCUX2PL/moc_opticaldrive.cpp:162 #10 0x7feb369ceb9e in doActivate (sender=0x562880a2a1f0, signal_index=4, argv=0x7ffcabb16490) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:3898 #11 0x7feb381a086b in Solid::Backends::UDisks2::OpticalDrive::ejectDone (this=, _t1=, _t2=..., _t3=...) at /var/tmp/portage/kde-frameworks/solid-5.92.0/work/solid-5.92.0_build/src/solid/KF5Solid_autogen/EYXUHNKS25/moc_udisksopticaldrive.cpp:228 #12 0x7feb381fbb05 in QtPrivate::RefCount::deref (this=0x7feb24032480) at /usr/include/qt5/QtCore/qrefcount.h:68 #13 QString::~QString (this=0x7ffcabb164d8, __in_chrg=) at /usr/include/qt5/QtCore/qstring.h:1311 #14 Solid::Backends::UDisks2::OpticalDrive::slotEjectDone (this=0x562880a2a1f0, error=2, errorString=...) at /var/tmp/portage/kde-frameworks/solid-5.92.0/work/solid-5.92.0/src/solid/devices/backends/udisks2/udisksopticaldrive.cpp:117 #15 0x7feb381abbc3 in Solid::Backends::UDisks2::GenericInterface::qt_metacall (this=0x7ffcabb161c0, _c=QMetaObject::InvokeMetaMethod, _id=-1414438064, _a=0x0) at /var/tmp/portage/kde-frameworks/solid-5.92.0/work/solid-5.92.0_build/src/solid/KF5Solid_autogen/EYXUHNKS25/moc_udisksgenericinterface.cpp:134 #16 0x000636ce8499 in ?? () #17 0x0001 in ?? () #18 0x7ffcabb16600 in ?? () #19 0x7ffcabb165d0 in ?? () #20 0x7feb36c9ad2b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=) at /var/tmp/portage/dev-qt/qtdbus-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/tools/qvarlengtharray.h:189 #21 0x7feb369c6d06 in QObject::event (this=0x562880a2a1f0, e=0x7feb240581d0) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:1314 #22 0x7feb3749796f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x7feb3699b428 in QCoreApplication::notifyInternal2 (receiver=0x562880a2a1f0, event=0x7feb240581d0) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1064 #24 0x7feb3699ea95 in QCoreApplicationPrivate::sendPostedEvents
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #3 from Nate Graham --- It's now working for me, whereas I was able to reproduce Bug 354802, so there must be something different about our setups. I have a few questions: 1. Is the layout always reset such that the items are in alphabetical order, with folders before files? 2. Are you using a laptop or a desktop? 3. How many screens do you have connected, 4. In your ~/.config/plasmashellrc file, does the contents of the "[ScreenConnectors]" section change after you reboot? 5. In your ~/.config/plasma-org.kde.plasma.desktop-appletsrc file, does the contents of the line beginning with "positions=" change after you reboot? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454365] New: Overview touchpad gesture not working correctly.
https://bugs.kde.org/show_bug.cgi?id=454365 Bug ID: 454365 Summary: Overview touchpad gesture not working correctly. Product: plasmashell Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joshuaandre...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 149187 --> https://bugs.kde.org/attachment.cgi?id=149187=edit In the beginning of the video I try the overview by swiping directly down with four finger. Next I try slowly swiping to the bottom right of the touchpad, which activates the proper overview. SUMMARY The touchpad gesture for the overview on Plasma 5.25.90 does not work correctly. When I swipe with four fingers down, a different UI appears instead of the overview that shows when pressing "Super + W". STEPS TO REPRODUCE 1. Swipe with four fingers down on a touchpad using Plasma 5.25.90 on Arch Linux or KDENeon OBSERVED RESULT Overview UI looks different. It does not show the active desktops. It has a search bar, but it is not functional. EXPECTED RESULT Overview shows correctly with active desktops and working search bar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux w/ KDE PLasma KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel: 5.17.9-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION It is possible to get the correct overview effect when swiping carefully towards the bottom right corner of the touchpad. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 454363] Plasma prevents suspend to RAM without any feedback when data transfer to usb device is in progress in background
https://bugs.kde.org/show_bug.cgi?id=454363 --- Comment #1 from Patrick Silva --- another thing: after the provided steps, Plasma suspends the system to RAM when the file transfer in background is completed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391956] Maximized windows too small when scaling is applied on X11
https://bugs.kde.org/show_bug.cgi?id=391956 Nate Graham changed: What|Removed |Added CC||ad.liu@gmail.com --- Comment #24 from Nate Graham --- *** Bug 445741 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445741] "Fullscreen" in window menu is disabled in all KDE/Qt apps, with 250% zoom and certain screen resolution
https://bugs.kde.org/show_bug.cgi?id=445741 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Nate Graham --- Sounds right. I'll mark this as a duplicate. Would you mind posting the conclusions of your technical investigation in Bug 391956? Thanks! *** This bug has been marked as a duplicate of bug 391956 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453860] [Wayland] Mouse cursor not displayed on Wayland session
https://bugs.kde.org/show_bug.cgi?id=453860 31...@tuta.io changed: What|Removed |Added CC||31...@tuta.io --- Comment #6 from 31...@tuta.io --- I have the same issue on fedora + marcdeop's copr. Also nearly identical hardware. I found these two lines in the logs to be interesting: kwin_wayland[1383]: kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card0" kwin_wayland_drm: Could not create drm framebuffer! Invalid argument The latter one gets thrown in there a bunch of times. I tried to get the output of drm_info, but I can't get it to install & run correctly... output of `qdbus org.kde.KWin /KWin supportInformation`: https://pastebin.com/8CaWbQZv -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 454364] Phone notifications do not sync with linked desktop
https://bugs.kde.org/show_bug.cgi?id=454364 petergriffingaming354...@gmail.com changed: What|Removed |Added CC||petergriffingaming354321@gm ||ail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 454364] New: Phone notifications do not sync with linked desktop
https://bugs.kde.org/show_bug.cgi?id=454364 Bug ID: 454364 Summary: Phone notifications do not sync with linked desktop Product: kdeconnect Version: 22.04.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: petergriffingaming354...@gmail.com Target Milestone: --- SUMMARY My Android phone has successfully connected with my Ubuntu 22.04 desktop through KDE Connect (ver. 1.19.1). I can control media through my phone, send and receive files, send ping etc. but I cannot access or interact with any new notifications I receive on my phone from the desktop as of lately. STEPS TO REPRODUCE 1. Have a notification pop-up on the phone (like a new email, SMS message, reddit ban etc) OBSERVED RESULT Notification does not pop-up on the desktop. EXPECTED RESULT Said notification should also show up on the desktop while the two devices are connected. SOFTWARE/OS VERSIONS Linux: Kubuntu 22.04, kernel 5.15.0-33-generic 64 bit (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION KDE Connect Android app version 1.19.1. Installed from F-Droid. I first noticed this problem a few days ago, I'm not sure what could've triggered it -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 454363] New: Plasma prevents suspend to RAM without any feedback when data transfer to usb device is in progress in background
https://bugs.kde.org/show_bug.cgi?id=454363 Bug ID: 454363 Summary: Plasma prevents suspend to RAM without any feedback when data transfer to usb device is in progress in background Product: frameworks-kio Version: 5.94.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kdelibs-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. connect a usb flash drive to usb port 2. copy a big file (I have used a 867 MiB video file in my test) to your flash drive 3. wait for 'Copying (Finished)' notification from Plasma 4. try to suspend your system to RAM OBSERVED RESULT nothing happens and the user receives no feedback EXPECTED RESULT feedback like a notification telling us that suspend to RAM is not possible due to data transfer in progress or similar SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Graphics Platform: Wayland ADDITIONAL INFORMATION This is another consequence of the annoying bug 281270 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454361] (SIGFPE) kwin_wayland crashed in KWin::X11Window::constrainClientSize
https://bugs.kde.org/show_bug.cgi?id=454361 --- Comment #4 from postix --- It does not crash w/o MR 2288. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454361] (SIGFPE) kwin_wayland crashed in KWin::X11Window::constrainClientSize
https://bugs.kde.org/show_bug.cgi?id=454361 --- Comment #3 from postix --- The line ``` echo Xft.dpi: 192 | xrdb -merge ``` mentioned in the OT is not required to trigger the crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452243] Programs running on Xwayland randomly crash and Xwayland stops working
https://bugs.kde.org/show_bug.cgi?id=452243 --- Comment #13 from winbloc...@gmx.de --- (In reply to Matej Mrenica from comment #10) > Does installing xorg-xwayland-git from AUR fix this issue? Installed from git and after a first test the crash seems to be gone. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #15 from stalker...@gmail.com --- I've managed to determine what's causing the issue. There was a widget called Input Method. And as soon as I removed it from the panel, everything just started working again. I'm sure I didn't add it, the thing have just appeared on me after the update. No matter how many times I close it, the thing just re-appears after a reboot. When I click on a desktop, it's tooltip says "No input window". And I can't switch the language. But when I click on any input field, it changes to "Keyboard - English (US)" and I can start typing. Some of the most annoying cases (for those who think this is intended behavior): 1. Address bar in Chrome changes language every time I press backspace 2. VS Code changes language every time I click on the text When I click on the Configure option of the widget, I get the following error message (and nothing happens): "You're currently running KDE, but KCModule for fcitx couldn't be found, the package name of this KCModule is usually kcm-fcitx or kde-config-fcitx. Now it will open config file with default text editor." "Online Help" option of the widget leads into nowhere (nothing happens as well). I guess it's somehow connected to the virtual keyboard I didn't know existed and I've never used in my life. I wonder if this is an intended behavior (and how do I get rid of it). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399568] Dictionary plasmoid icon broken
https://bugs.kde.org/show_bug.cgi?id=399568 Nate Graham changed: What|Removed |Added Assignee|plasma-b...@kde.org |visual-des...@kde.org Component|dictionary |Icons Product|kdeplasma-addons|Breeze CC||m...@nueljl.in --- Comment #15 from Nate Graham --- It's broken in the icon itself. Manuel, would you be interested in making a nice new Breeze-style dictionary icon? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432088] Dark theme in Windows
https://bugs.kde.org/show_bug.cgi?id=432088 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/327d5470 ||2472003abb56d066a282516e0e2 ||f0e84 Resolution|--- |FIXED Version Fixed In||22.08 --- Comment #5 from Nate Graham --- Git commit 327d54702472003abb56d066a282516e0e2f0e84 by Nate Graham, on behalf of George Florea Bănuș. Committed on 24/05/2022 at 20:37. Pushed by ngraham into branch 'master'. Add app-wide color scheme chooser FIXED-IN: 22.08 M +9-0part/part.cpp M +2-1part/part.rc https://invent.kde.org/graphics/okular/commit/327d54702472003abb56d066a282516e0e2f0e84 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 399568] Dictionary plasmoid icon broken
https://bugs.kde.org/show_bug.cgi?id=399568 --- Comment #14 from Patrick Silva --- Created attachment 149186 --> https://bugs.kde.org/attachment.cgi?id=149186=edit broken icon in krunner As seen in the screenshot attache to this comment, Dictionary icon is broken in krunner too. Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454361] (SIGFPE) kwin_wayland crashed in KWin::X11Window::constrainClientSize
https://bugs.kde.org/show_bug.cgi?id=454361 postix changed: What|Removed |Added Summary|kwin_wayland crashed in |(SIGFPE) kwin_wayland |KWin::X11Window::constrainC |crashed in |lientSize |KWin::X11Window::constrainC ||lientSize -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 454362] New: kded5 crashed after reboot and login
https://bugs.kde.org/show_bug.cgi?id=454362 Bug ID: 454362 Summary: kded5 crashed after reboot and login Product: frameworks-kded Version: 5.94.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: fa...@kde.org Reporter: bugsefor...@gmx.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Rebooted my computer, logged in to Wayland, drkonqi shown up on the screen reporting kded5 crash. Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Graphics Platform: Wayland Thread 9 (Thread 0x7fb629a07640 (LWP 774)): #0 0x7fb6325b5faf in __GI___poll (fds=0x7fb618016870, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb631754976 in g_main_context_poll (priority=, n_fds=1, fds=0x7fb618016870, timeout=, context=0x7fb618014bc0) at ../glib/glib/gmain.c:4516 #2 g_main_context_iterate.constprop.0 (context=0x7fb618014bc0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4206 #3 0x7fb6316fd6a3 in g_main_loop_run (loop=0x7fb618014cb0) at ../glib/glib/gmain.c:4411 #4 0x7fb62ac0d6dc in gdbus_shared_thread_func (user_data=0x7fb618014b90) at ../glib/gio/gdbusprivate.c:282 #5 0x7fb63172dda5 in g_thread_proxy (data=0x7fb618002e40) at ../glib/glib/gthread.c:827 #6 0x7fb63253c54d in start_thread (arg=) at pthread_create.c:442 #7 0x7fb6325c1b14 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 Thread 8 (Thread 0x7fb62c1e3640 (LWP 681)): #0 ___pthread_mutex_lock (mutex=mutex@entry=0x5632f05d4cf8) at pthread_mutex_lock.c:77 #1 0x7fb633d917bd in wl_display_cancel_read (display=0x5632f05d4c10) at ../wayland-1.20.0/src/wayland-client.c:1850 #2 0x7fb62f0ece46 in QtWaylandClient::EventThread::run() (this=0x5632f064acb0) at /usr/src/debug/qtwayland/src/client/qwaylanddisplay.cpp:222 #3 0x7fb6329d836a in QThreadPrivate::start(void*) (arg=0x5632f064acb0) at thread/qthread_unix.cpp:331 #4 0x7fb63253c54d in start_thread (arg=) at pthread_create.c:442 #5 0x7fb6325c1b14 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 Thread 7 (Thread 0x7fb62b90a640 (LWP 682)): #0 0x7fb6325389e9 in __GI___pthread_enable_asynccancel () at cancellation.c:42 #1 0x7fb6325b1f17 in __GI___libc_read (nbytes=16, buf=0x7fb62b909aa0, fd=11) at ../sysdeps/unix/sysv/linux/read.c:26 #2 __GI___libc_read (fd=11, buf=buf@entry=0x7fb62b909aa0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #3 0x7fb6316fe7b0 in read (__nbytes=16, __buf=0x7fb62b909aa0, __fd=, __fd=, __buf=, __nbytes=) at /usr/include/bits/unistd.h:38 #4 g_wakeup_acknowledge (wakeup=0x7fb61c0039a0) at ../glib/glib/gwakeup.c:210 #5 g_main_context_check (context=0x7fb62c30, max_priority=2147483647, fds=0x7fb6200572a0, n_fds=1) at ../glib/glib/gmain.c:3963 #6 0x7fb631754877 in g_main_context_iterate.constprop.0 (context=context@entry=0x7fb62c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4208 #7 0x7fb6316fb6c5 in g_main_context_iteration (context=0x7fb62c30, may_block=1) at ../glib/glib/gmain.c:4276 #8 0x7fb632bcc7df in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fb62b70, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #9 0x7fb632b7a79c in QEventLoop::exec(QFlags) (this=0x7fb62b909c90, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #10 0x7fb6329db53f in QThread::exec() (this=this@entry=0x7fb632f39560 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #11 0x7fb632edd75a in QDBusConnectionManager::run() (this=0x7fb632f39560 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /usr/src/debug/qtbase/src/dbus/qdbusconnection.cpp:179 #12 0x7fb6329d836a in QThreadPrivate::start(void*) (arg=0x7fb632f39560 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:331 #13 0x7fb63253c54d in start_thread (arg=) at pthread_create.c:442 #14 0x7fb6325c1b14 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 Thread 6 (Thread 0x7fb62f4f3840 (LWP 673)): #0 0x7fb6325b5faf in __GI___poll (fds=fds@entry=0x7fffb9ec6ad0, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb633609ada in poll (__timeout=1000, __nfds=1, __fds=0x7fffb9ec6ad0) at /usr/include/bits/poll2.h:39 #2 pollDrKonqiSocket (sockfd=3, pid=970) at /usr/src/debug/kcrash-5.94.0/src/kcrash.cpp:865 #3 KCrash::startProcess(int, char const**, bool) (argv=argv@entry=0x7fffb9ec6c18, waitAndExit=waitAndExit@entry=true, argc=) at /usr/src/debug/kcrash-5.94.0/src/kcrash.cpp:727 #4 0x7fb63360a7d4 in
[kwin] [Bug 454361] kwin_wayland crashed in KWin::X11Window::constrainClientSize
https://bugs.kde.org/show_bug.cgi?id=454361 --- Comment #2 from postix --- It does _not_ crash for me executing ``` QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCREEN_SCALE_FACTORS=0 /usr/bin/vlc QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCREEN_SCALE_FACTORS=1 /usr/bin/vlc ``` -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #47 from RJVB --- > The problem is that currentIndex is 0 and it never bails out. This is with > the very latest release. IIRC this is one of the things my patch addresses. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454361] kwin_wayland crashed in KWin::X11Window::constrainClientSize
https://bugs.kde.org/show_bug.cgi?id=454361 --- Comment #1 from postix --- Created attachment 149185 --> https://bugs.kde.org/attachment.cgi?id=149185=edit kWin Support Info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454361] kwin_wayland crashed in KWin::X11Window::constrainClientSize
https://bugs.kde.org/show_bug.cgi?id=454361 postix changed: What|Removed |Added CC||pos...@posteo.eu Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454361] New: kwin_wayland crashed in KWin::X11Window::constrainClientSize
https://bugs.kde.org/show_bug.cgi?id=454361 Bug ID: 454361 Summary: kwin_wayland crashed in KWin::X11Window::constrainClientSize Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 149184 --> https://bugs.kde.org/attachment.cgi?id=149184=edit bt full SUMMARY checkout MR https://invent.kde.org/plasma/kwin/-/merge_requests/2288 ``` echo Xft.dpi: 192 | xrdb -merge QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCREEN_SCALE_FACTORS=2 /usr/bin/vlc ``` ``` #0 0x7fcfd96ad80c in KWin::X11Window::constrainClientSize(QSize const&, KWin::Window::SizeMode) const (this=0x2362800, size=..., mode=KWin::Window::SizeModeAny) at /home/mh/Development/kde/src/kde/workspace/kwin/src/x11window.cpp:3581 #1 0x7fcfd96a0c9a in KWin::X11Window::manage(unsigned int, bool) (this=0x2362800, w=20971526, isMapped=false) at /home/mh/Development/kde/src/kde/workspace/kwin/src/x11window.cpp:694 #2 0x7fcfd967e30d in KWin::Workspace::createX11Window(unsigned int, bool) (this=0x137ea20, windowId=20971526, is_mapped=false) at /home/mh/Development/kde/src/kde/workspace/kwin/src/workspace.cpp:655 #3 0x7fcfd94e180d in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x137ea20, e=0x7fcfcc01f850) at /home/mh/Development/kde/src/kde/workspace/kwin/src/events.cpp:219 #4 0x7fcfd955326b in KWin::Application::dispatchEvent(xcb_generic_event_t*) (this=0x7fff903e2cb0, event=0x7fcfcc01f850) at /home/mh/Development/kde/src/kde/workspace/kwin/src/main.cpp:488 #5 0x7fcfd9553409 in KWin::XcbEventFilter::nativeEventFilter(QByteArray const&, void*, long*) (this=0xe6a740, eventType=..., message=0x7fcfcc01f850, result=0x7fff903e2628) at /home/mh/Development/kde/src/kde/workspace/kwin/src/main.cpp:576 #6 0x7fcfd78d8eff in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=, eventType=..., message=0x7fcfcc01f850, result=0x7fff903e2628) at kernel/qabstracteventdispatcher.cpp:495 #7 0x004708c0 in KWin::Xwl::Xwayland::dispatchEvents() (this=0x187c280) at /home/mh/Development/kde/src/kde/workspace/kwin/src/xwayland/xwayland.cpp:123 #8 0x00472f5f in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KWin::Xwl::Xwayland::*)()>::call(void (KWin::Xwl::Xwayland::*)(), KWin::Xwl::Xwayland*, void**) (f=(void (KWin::Xwl::Xwayland::*)(KWin::Xwl::Xwayland * const)) 0x470722 , o=0x187c280, arg=0x7fff903e2860) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #9 0x00472d7a in QtPrivate::FunctionPointer::call, void>(void (KWin::Xwl::Xwayland::*)(), KWin::Xwl::Xwayland*, void**) (f=(void (KWin::Xwl::Xwayland::*)(KWin::Xwl::Xwayland * const)) 0x470722 , o=0x187c280, arg=0x7fff903e2860) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #10 0x00472acd in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x2180b70, r=0x187c280, a=0x7fff903e2860, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:418 #11 0x7fcfd7912def in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff903e2860, r=0x187c280, this=0x2180b70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate(QObject*, int, void**) (sender=0x10197c0, signal_index=3, argv=0x7fff903e2860) at kernel/qobject.cpp:3886 #13 0x7fcfd790c0cf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x10197c0, m=m@entry=0x7fcfd7baf880 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff903e2860) at kernel/qobject.cpp:3946 #14 0x7fcfd791612f in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x10197c0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #15 0x7fcfd7916935 in QSocketNotifier::event(QEvent*) (this=0x10197c0, e=) at kernel/qsocketnotifier.cpp:302 #16 0x7fcfd644137e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x10197c0, e=0x7fff903e2960) at kernel/qapplication.cpp:3632 #17 0x7fcfd78db988 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x10197c0, event=0x7fff903e2960) at kernel/qcoreapplication.cpp:1064 #18 0x7fcfd79309e3 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0xe331b0) at kernel/qeventdispatcher_unix.cpp:304 #19 0x7fcfd7930ea7 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:511 #20 0x0058805d in QUnixEventDispatcherQPA::processEvents(QFlags) (this=, flags=...) at qunixeventdispatcher.cpp:63 #21 0x7fcfd78da3fb in QEventLoop::exec(QFlags) (this=this@entry=0x7fff903e2af0, flags=...,
[systemsettings] [Bug 454360] System Settings crashes in KWin::KWinTouchScreenEdgeEffectSettings::touchBorderActivate() when opening Touch Screen Edges KCM
https://bugs.kde.org/show_bug.cgi?id=454360 Nate Graham changed: What|Removed |Added Component|general |kcm_kwintouchscreen CC||notm...@gmail.com, ||plasma-b...@kde.org Keywords||regression Priority|NOR |VHI Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Summary|System Settings crashes |System Settings crashes in |when opening Touch Screen |KWin::KWinTouchScreenEdgeEf |Edges KCM |fectSettings::touchBorderAc ||tivate() when opening Touch ||Screen Edges KCM Version|unspecified |5.24.90 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #14 from Andrey --- (In reply to stalkermar from comment #3) > Graphics Platform: X11 What's on Wayland? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454360] New: System Settings crashes when opening Touch Screen Edges KCM
https://bugs.kde.org/show_bug.cgi?id=454360
Bug ID: 454360
Summary: System Settings crashes when opening Touch Screen
Edges KCM
Product: systemsettings
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: n...@kde.org
Target Milestone: ---
Application: systemsettings (5.25.80)
(Compiled from sources)
Qt Version: 5.15.3
Frameworks Version: 5.95.0
Operating System: Linux 5.17.8-300.fc36.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.25.80 [KCrashBackend]
-- Information about the crash:
Ever since the new QML Present Windows and Desktop Grid effects were merged,
the Touch Screen Edges KCM has been crashing on launch for me.
The crash can be reproduced every time.
-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 QList::QList (this=0x7ffc38ef2f68, l=...) at
/usr/include/qt5/QtCore/qlist.h:853
#6 0x7f161d158b09 in
KWin::KWinTouchScreenEdgeEffectSettings::touchBorderActivate (this=) at
/home/nate/kde/build/kwin/src/kcmkwin/kwinscreenedges/kwintouchscreenedgeeffectsettings.h:35
#7 KWin::KWinScreenEdgesConfig::monitorLoadSettings
(this=this@entry=0x3552470) at
/home/nate/kde/src/kwin/src/kcmkwin/kwinscreenedges/touch.cpp:201
#8 0x7f161d159b41 in KWin::KWinScreenEdgesConfig::load (this=0x3552470) at
/home/nate/kde/src/kwin/src/kcmkwin/kwinscreenedges/touch.cpp:65
#9 0x7f1671bea182 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#10 0x7f1672989c22 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#11 0x7f1671bc0118 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#12 0x7f1671bc3474 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#13 0x7f1671c11197 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#14 0x7f166f642f4f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#15 0x7f166f698168 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#16 0x7f166f6408e0 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#17 0x7f1671c10c8a in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#18 0x7f1671bbeb7a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#19 0x7f1671bc6c22 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#20 0x0040cc7a in main (argc=, argv=) at
/home/nate/kde/src/systemsettings/app/main.cpp:183
[Inferior 1 (process 46892) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #13 from Andrey --- (In reply to stalkermar from comment #4) > It actually worked fine on 20.04, so your best bet would be to reproduce it > like this: > > 1. Install Kubuntu 20.04 > 2. Add 1 more input language > 3. Update the distro to 21.10. I guess I've used this manual: > https://help.ubuntu.com/community/JammyUpgrades/Kubuntu > 4. Reboot. > 5. Update to the "latest and greatest" distro- 22.10 > 6. Reboot > 7. Observe the issue. So it might be upgrade issue, can you reproduce yourself in VM? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #12 from Andrey --- (In reply to stalkermar from comment #0): > https://askubuntu.com/questions/1330324/kde-plasma-5-undesireable-keyboard- > layout-switching-behavior Did you try to follow the tips suggested? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454359] Crop handle uses wrong cursor
https://bugs.kde.org/show_bug.cgi?id=454359 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454359] New: Crop handle uses wrong cursor
https://bugs.kde.org/show_bug.cgi?id=454359 Bug ID: 454359 Summary: Crop handle uses wrong cursor Product: Spectacle Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: natalie_clar...@yahoo.de CC: k...@david-redondo.de Target Milestone: --- Created attachment 149183 --> https://bugs.kde.org/attachment.cgi?id=149183=edit hand instead of two-headed arrow SUMMARY *** Hovering over the crop handles keeps showing the pan cursor (hand symbol) instead of the resize cursor (two-headed arrow), which makes it not obvious that the user can click to crop now. *** STEPS TO REPRODUCE 1. Take a screenshot 2. Annotate 3. Crop 4. Hover over one of the squares to crop from OBSERVED RESULT Pan cursor (hand) EXPECTED RESULT Resize cursor (two-headed arrow) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Bob Igo changed: What|Removed |Added CC||b...@igo.name -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #11 from stalker...@gmail.com --- (In reply to Andrey from comment #10) > Do you have some ibus stuff installed maybe? Not that I know of. At the very leasy, ibus package from apt is not installed. -- You are receiving this mail because: You are watching all bug changes.
