[plasmashell] [Bug 490365] Dolphin's notification about the background process takes up half the width in Notifications and overlaps the lower content with action buttons
https://bugs.kde.org/show_bug.cgi?id=490365 Alexey changed: What|Removed |Added CC||alexi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490365] New: Dolphin's notification about the background process takes up half the width in Notifications and overlaps the lower content with action buttons
https://bugs.kde.org/show_bug.cgi?id=490365 Bug ID: 490365 Summary: Dolphin's notification about the background process takes up half the width in Notifications and overlaps the lower content with action buttons Classification: Plasma Product: plasmashell Version: 6.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 171708 --> https://bugs.kde.org/attachment.cgi?id=171708=edit Demo See the attachment. STEPS TO REPRODUCE 1. Run some operation in Dolphin, e.g. Compress directory; 2. Minimize notification; 3. Open "Notifications"; 4. Delete some notification under Dolphin's operation notification. OBSERVED RESULT See attachments. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel version: 6.9.9-arch1-1 (64-bit) Graphics platform: Wayland (with fractional scaling 1.25) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477673] KDEConnect - sshfs finished with exit code 1 when attempting to browse
https://bugs.kde.org/show_bug.cgi?id=477673 Alexey changed: What|Removed |Added CC||alexi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 325574] Unable to modify file on Android device using kio-mtp
https://bugs.kde.org/show_bug.cgi?id=325574 Alexey changed: What|Removed |Added CC||alexi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485771] Desktop icons disappear after icon update (including the trash icon)
https://bugs.kde.org/show_bug.cgi?id=485771 Alexey changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Ever confirmed|1 |0 CC||alsubb...@gmail.com --- Comment #23 from Alexey --- Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Bug is still unfixed. To reproduce just 1. right click on *.desktop icon on the desktop 2. press OK button Icon is disappears from Desktop although it is in the ~/Desktop folder. To restore icon visibility I change room mode from folder to desktop and back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488832] Add a button/option that will show the logout screen with all options
https://bugs.kde.org/show_bug.cgi?id=488832 Alexey Arutyunov changed: What|Removed |Added CC||alexei.arutyu...@gmail.com --- Comment #6 from Alexey Arutyunov --- (In reply to filip.kendes1 from comment #4) > If you open Shortcuts -> Session Management -> Show Logout Prompt > (Ctrl+Alt+Del) you get the logout prompt with all the options available. > > Maybe we can add this option (whatever this shortcut triggers, I'm not sure) > to the Lock/Logout widget? As a workaround I created $HOME/.local/share/applications/logoutprompt.desktop file with the following contents: --- [Desktop Entry] Type=Application Name=Logout Comment=Logout Prompt Categories=Utility; OnlyShowIn=KDE; Exec=qdbus-qt6 org.kde.LogoutPrompt /LogoutPrompt promptAll Icon=system-shutdown-symbolic StartupNotify=false --- Then dragged it's entry from Utilities menu to the place on the panel where I had the logout button. This icon widget works exactly like the logout button used to work for me. Hope this helps until proper fix for the widget. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488519] Panel changes wallpapers at background
https://bugs.kde.org/show_bug.cgi?id=488519 Alexey changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488519] Panel changes wallpapers at background
https://bugs.kde.org/show_bug.cgi?id=488519 Alexey changed: What|Removed |Added Version|6.0.1 |6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488519] New: Panel changes wallpapers at background
https://bugs.kde.org/show_bug.cgi?id=488519 Bug ID: 488519 Summary: Panel changes wallpapers at background Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 170513 --> https://bugs.kde.org/attachment.cgi?id=170513=edit Bug demonstration *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY If the panel height is from 32 to 38 inclusive, there is a fill below and to the right of the floating panel. OBSERVED RESULT See attachment. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Desktop resolution: 1920x1080 Scaling: 1.25 (Wayland) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487816] No clean way to change the wallpaper for distributions
https://bugs.kde.org/show_bug.cgi?id=487816 Alexey Min changed: What|Removed |Added CC||alexey@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487557] Inconsistency in window activation under Wayland in multi-window applications.
https://bugs.kde.org/show_bug.cgi?id=487557 --- Comment #4 from Alexey Ivanov --- > Qt 6.8 release plan > Final Release 25.09.2024 Holly Molly it will take ONE YEAR for fix to land into Linux distributives. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487557] Inconsistency in window activation under Wayland in multi-window applications.
https://bugs.kde.org/show_bug.cgi?id=487557 --- Comment #2 from Alexey Ivanov --- Also happens in Fedora 40 with KDE6 manually installed from official repository. In VirtualBox. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460318] Wayland activation bugs
https://bugs.kde.org/show_bug.cgi?id=460318 Alexey Ivanov changed: What|Removed |Added CC||kra...@zohomail.com --- Comment #2 from Alexey Ivanov --- https://bugs.kde.org/show_bug.cgi?id=487557 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487557] Inconsistency in window activation under Wayland in multi-window applications.
https://bugs.kde.org/show_bug.cgi?id=487557 --- Comment #1 from Alexey Ivanov --- IIRC, this bug also existed in KDE 6.0 when it landed in Neon User Edition. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487557] New: Inconsistency in window activation under Wayland in multi-window applications.
https://bugs.kde.org/show_bug.cgi?id=487557 Bug ID: 487557 Summary: Inconsistency in window activation under Wayland in multi-window applications. Classification: Plasma Product: kwin Version: 6.0.5 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kra...@zohomail.com Target Milestone: --- Created attachment 169836 --> https://bugs.kde.org/attachment.cgi?id=169836=edit activation example, cmake/Qt project SUMMARY KDE 6 Wayland xdg_activation protocol implementation is inconsistent. Let's say developer want to create a multi-window application, using 3 QMainWindow. CASE 1: When you create QMainWindow -> showMinimized() -> activateWindow() never works in first call, only second try starts working. This is a bug! CASE 2: When you create QMainWindow -> show(), then switching to that new window, resize it, and try to activateWindow() also never works in first try, only second. This is also a bug! When you create minimized window first and then normal one (or vice versa, doesn't matter) then both activateWindow works. STEPS TO REPRODUCE CASE 1: 1. Run activation-example from archive attached. 2. Click Show Minimized 3. Click Try Activate Minimized 4. Window won't get activated and still minimized on taskbar. STEPS TO REPRODUCE CASE 2: 1. Run activation-example from archive attached. 2. Click Show Normal 3. Click on that newly showed window. 4. Move it and resize it. 5. Click on example window with 4 buttons. 6. Also move it and resize it. 7. Click on Try Activate Normal 8. Window won't get activated. Linux: KDE Neon Testin Edition KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 486975] New: When i open console and trying to write something it crashes
https://bugs.kde.org/show_bug.cgi?id=486975 Bug ID: 486975 Summary: When i open console and trying to write something it crashes Classification: Applications Product: konsole Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: alexbesporoc...@gmail.com Target Milestone: --- Created attachment 169447 --> https://bugs.kde.org/attachment.cgi?id=169447=edit System parameters *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY [alexbespik@pc ~]$ konsole Segmentation fault (core dumped) STEPS TO REPRODUCE 1. open xterm 2. type konsole 3. or tap on icon OBSERVED RESULT konsole krashes EXPECTED RESULT konsole open SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486971] New: "Activities" switching not working after update to plasma 6
https://bugs.kde.org/show_bug.cgi?id=486971 Bug ID: 486971 Summary: "Activities" switching not working after update to plasma 6 Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: alexbesporoc...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Before updete i switched Activities with alt+q but now its not working and i ever not see such settings STEPS TO REPRODUCE 1. alt+q 2. 3. OBSERVED RESULT nothing EXPECTED RESULT changing activity SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485840] Panel attracts the cursor to itself on some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=485840 Alexey changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 472453] krfb asserts in PWFrameBuffer::cursorPosition
https://bugs.kde.org/show_bug.cgi?id=472453 Alexey Min changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/krfb/-/commit/6e7a5ba56 |ork/krfb/-/commit/d2f4b34fc |966ea1b67400be9ab7c82885abb |bfb75ae76cca7792dd3fb66c163 |76be|51fc --- Comment #11 from Alexey Min --- Git commit d2f4b34fcbfb75ae76cca7792dd3fb66c16351fc by Alexey Minnekhanov, on behalf of Yaroslav Sidlovsky. Committed on 22/04/2024 at 16:46. Pushed by alexeymin into branch 'release/24.05'. Fixed crash calling PWFrameBuffer::cursorPosition() Return default QPoint when `d->cursor` is not set. M +6-1framebuffers/pipewire/pw_framebuffer.cpp https://invent.kde.org/network/krfb/-/commit/d2f4b34fcbfb75ae76cca7792dd3fb66c16351fc -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485879] Incorrect text placement when renaming in Dolphin
https://bugs.kde.org/show_bug.cgi?id=485879 --- Comment #1 from Alexey --- I just saw recent reports with renaming, where the authors do not pay attention to left alignment; maybe I'm overthinking something? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485879] New: Incorrect text placement when renaming in Dolphin
https://bugs.kde.org/show_bug.cgi?id=485879 Bug ID: 485879 Summary: Incorrect text placement when renaming in Dolphin Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: alexi...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 168728 --> https://bugs.kde.org/attachment.cgi?id=168728=edit Bug demonstration SUMMARY After upgrading to Plasma 6, I started to feel something strange when renaming files in Dolphin. After some observation, I realized that the rename text was no longer centered and was positioned to the left. STEPS TO REPRODUCE 1. Open Dolphin; 2. Select "Rename" for some entry. OBSERVED RESULT Text is shifted to the left after the rename field is changed. EXPECTED RESULT Text must be centered during renaming. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION This is a late report; the bug was discovered in the Plasma 6 release version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485840] Panel attracts the cursor to itself on some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=485840 --- Comment #3 from Alexey --- (In reply to fanzhuyifan from comment #2) > Is this on wayland or x11? It's Wayland, but something tells me that it's reproducible regardless of session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485840] Panel attracts the cursor to itself on some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=485840 --- Comment #1 from Alexey --- An important point: in the demo you can see that some of the triggers of the mentioned bug 474488 still cause windows to flicker. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485840] New: Panel attracts the cursor to itself on some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=485840 Bug ID: 485840 Summary: Panel attracts the cursor to itself on some fullscreen games Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- Created attachment 168709 --> https://bugs.kde.org/attachment.cgi?id=168709=edit Bug demonstration SUMMARY This bug report is related to https://bugs.kde.org/show_bug.cgi?id=474488 (maybe). As in the mentioned bug, this bug affects some full-screen games and is not reproducible on other compositors like Mutter or Hyprland. Like the previous issue involving the annoying flickering of the full screen game window with the visible system bar (the hidden panel did not caused this behavior), this issue has the same "triggers" but has a different observable result: the cursor moves to the bar (only when system panel is visible too). There seem to be too many bugs associated with the panel lately, from apps losing focus when there are standalone widgets in the panel, to less detectable bugs like this that can persist for years. As a complete amateur in such questions, I am sincerely interested in why this is even possible. STEPS TO REPRODUCE 1. Set "Always visible" to panel; 2. Launch game with detectable behavior (for example, HoMM3); 3. Perform “trigger” actions that lead to an issue (see attachments). OBSERVED RESULT ... EXPECTED RESULT ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474488] Panel flickering at the top of some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=474488 Alexey changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #24 from Alexey --- (In reply to Alexey from comment #23) > (In reply to Zamundaaa from comment #22) > > The problem is that the window is not actually fullscreen. > The problem is not reproducible in other desktop environments, so even if > the change didn't fix the problem, it's still a problem on the KWin side. Today I was able to reproduce the bug with Diablo II under Wine. Yes, this bug report should be reopened. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482629] FPS games sometimes respond incorrectly to mouse input after upgrading from 5.27.10 to 6.0.0
https://bugs.kde.org/show_bug.cgi?id=482629 Alexey Boltenko changed: What|Removed |Added CC||docar...@gmail.com --- Comment #18 from Alexey Boltenko --- I'm also facing this with many games (happened at least once with: Garry's Mod (native), Garry's Mod (proton), VotV, Tower Unite, Deep Rock Galactic, Risk of Rain 2, Outer Wilds, etc) Opening the debug console as per an earlier comment did not help. I've also tested with a low-dpi mouse (some ancient asus), and it seems that doesn't affect the outcome. This did not happen on 5.27 (Wayland - did not test x11) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 484383] New: Breeze GTK strange black lines between some elements
https://bugs.kde.org/show_bug.cgi?id=484383 Bug ID: 484383 Summary: Breeze GTK strange black lines between some elements Classification: Plasma Product: Breeze Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com CC: agrine...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 167699 --> https://bugs.kde.org/attachment.cgi?id=167699=edit bug demonstration STEPS TO REPRODUCE 1. Set Breeze as theme for GTK applications; 2. Open Lutris. OBSERVED RESULT Black lines on left panel. EXPECTED RESULT No black lines on left panel (like with "default" GTK theme). SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 Alexey changed: What|Removed |Added CC||alexi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #10 from Alexey --- (In reply to Roman from comment #8) > New info[2]: > If you add display of the layout to the SYSTEM TRAY on the panel, the bug > does not appear. > Only if it is a separate widget, then it appears. Yes, it looks like the issue only applies to the widget position of the Keyboard layout component. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #9 from Alexey --- (In reply to Roman from comment #7) > New info: > This problem will be solved if you remove the keyboard layout widget from > the tray. > That exist in both modes (X11/wayland) Yes, but temporary; after reboot the issue restores. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #18 from Alexey --- (In reply to Marco Martin from comment #15) > *** Bug 482720 has been marked as a duplicate of this bug. *** Bug 482722 may also be related to this issue but the artifacts described there achieved through certain actions. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #17 from Alexey --- Created attachment 166603 --> https://bugs.kde.org/attachment.cgi?id=166603=edit 1920x1080 125% (System settings dialog 2) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #16 from Alexey --- Created attachment 166602 --> https://bugs.kde.org/attachment.cgi?id=166602=edit 1920x1080 125% (System settings dialog) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482722] New: Fonts break when reaching the very bottom of the left panel
https://bugs.kde.org/show_bug.cgi?id=482722 Bug ID: 482722 Summary: Fonts break when reaching the very bottom of the left panel Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- Created attachment 166593 --> https://bugs.kde.org/attachment.cgi?id=166593=edit Bug demonstration STEPS TO REPRODUCE 1. Minimize System Settings application window; 2. Scroll to the bottom of the left settings panel. OBSERVED RESULT Some of the text is cut off, some of the characters are smudged or are at different heights. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482720] New: Desktop icons text is blurry
https://bugs.kde.org/show_bug.cgi?id=482720 Bug ID: 482720 Summary: Desktop icons text is blurry Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com CC: h...@kde.org Target Milestone: 1.0 Created attachment 166592 --> https://bugs.kde.org/attachment.cgi?id=166592=edit Desktop icons text demo SUMMARY After update to Plasma 6 I noticed that the text of desktop icons looked blurry... more blurry than usual. Related to: https://www.reddit.com/r/kde/comments/1b8dhhn/wayland_plasma_6_and_blurry_text/. STEPS TO REPRODUCE 1. Open Plasma 6 (Wayland session with 1920x1080 125% display). 2. Compare text under icon with text in edit mode. OBSERVED RESULT Text under desktop icons looks blurry. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Unfortunately, I can't provide a demo of what the font looked like before the update, but I hope that what I described in this demo is not just my imagination. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #5 from Alexey --- It looks like the bug belongs to the 'plasmashell' product and the 'Keyboard Layout' component, but I don't see this component when editing the bug report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #3 from Alexey --- Created attachment 166586 --> https://bugs.kde.org/attachment.cgi?id=166586=edit keyboard settings Added keyboard settings to attachments. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #2 from Alexey --- (In reply to Vlad Zahorodnii from comment #1) > Cannot reproduce Did you add the Keyboard layout widget? Maybe you need to reboot your system, because sometimes this is not reproducible for some reason. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] New: Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 Bug ID: 482653 Summary: Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- Created attachment 166547 --> https://bugs.kde.org/attachment.cgi?id=166547=edit demo STEPS TO REPRODUCE 1. Add some keyboard layouts; 2. Add keyboard layout widget / system tray entry; 3. Switch layout with shortcut / click on widget; OBSERVED RESULT Switching keyboard layout leads to Application launcher focus/unfocus. EXPECTED RESULT Switching keyboard layout just switches keyboard layout. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 473668] Plasmashell crashes in NetworkModel::updateItem() when trying to connect to OpenVPN shortly after disconnecting
https://bugs.kde.org/show_bug.cgi?id=473668 Alexey Shildyakov changed: What|Removed |Added CC||ashl1fut...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472176] Plasma crash after enabling wireguard/openvpn VPN
https://bugs.kde.org/show_bug.cgi?id=472176 Alexey Shildyakov changed: What|Removed |Added CC||ashl1fut...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476161] Ability to use the new Cube effect as animation when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=476161 Alexey Neyman changed: What|Removed |Added CC||sti...@att.net -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 481758] app-office/calligra-3.2.1-r8: segfault at 56177c5d0116 ip 00007f326d174fbc sp 00007fff91dd3ae0 error 4 in libcalligrasheetsodf.so.17.0.0[7f326d061000+1a8000]
https://bugs.kde.org/show_bug.cgi?id=481758 --- Comment #5 from Alexey Dobriyan --- Each core is ~300 MiB. -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 481758] app-office/calligra-3.2.1-r8: segfault at 56177c5d0116 ip 00007f326d174fbc sp 00007fff91dd3ae0 error 4 in libcalligrasheetsodf.so.17.0.0[7f326d061000+1a8000]
https://bugs.kde.org/show_bug.cgi?id=481758 --- Comment #4 from Alexey Dobriyan --- coredump #2 this is ::unlink(QCache::Node&)+108> calligrasheets[11781]: segfault at 55f493375191 ip 7f6bc4f81acc sp 7fffb2edd9b0 error 4 in libcalligrasheetsodf.so.17.0.0[7f6bc4e61000+1a8000] likely on CPU 14 (core 14, socket 0) Code: 4d 8b 5e 10 8b 46 10 4c 8b 6e 08 41 29 46 1c 48 8b 1e 41 8b 53 14 85 d2 75 24 4d 85 ed 0f 84 2b 01 00 00 49 8b 45 00 4c 89 ef <48> 8b 40 08 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f ff e0 41 8b -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 481758] app-office/calligra-3.2.1-r8: segfault at 56177c5d0116 ip 00007f326d174fbc sp 00007fff91dd3ae0 error 4 in libcalligrasheetsodf.so.17.0.0[7f326d061000+1a8000]
https://bugs.kde.org/show_bug.cgi?id=481758 --- Comment #3 from Alexey Dobriyan --- Created attachment 166057 --> https://bugs.kde.org/attachment.cgi?id=166057=edit bt full (segfault #2) -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 481758] app-office/calligra-3.2.1-r8: segfault at 56177c5d0116 ip 00007f326d174fbc sp 00007fff91dd3ae0 error 4 in libcalligrasheetsodf.so.17.0.0[7f326d061000+1a8000]
https://bugs.kde.org/show_bug.cgi?id=481758 --- Comment #2 from Alexey Dobriyan --- Created attachment 166056 --> https://bugs.kde.org/attachment.cgi?id=166056=edit bt full (segfault #1) -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 481758] app-office/calligra-3.2.1-r8: segfault at 56177c5d0116 ip 00007f326d174fbc sp 00007fff91dd3ae0 error 4 in libcalligrasheetsodf.so.17.0.0[7f326d061000+1a8000]
https://bugs.kde.org/show_bug.cgi?id=481758 --- Comment #1 from Alexey Dobriyan --- coredump 1 This is calligrasheets[5175]: segfault at 56177c5d0116 ip 7f326d174fbc sp 7fff91dd3ae0 error 4 in libcalligrasheetsodf.so.17.0.0[7f326d061000+1a8000] likely on CPU 13 (core 13, socket 0) Code: 41 5c 41 5d c3 66 0f 1f 84 00 00 00 00 00 48 8b 43 58 48 89 fd 48 85 c0 74 24 0f 1f 40 00 48 8b 78 08 48 85 ff 74 0a 48 8b 07 50 08 48 8b 43 58 48 8b 40 20 48 89 43 58 48 85 c0 75 e0 4c 8b see bt-full-001.log -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 481758] New: app-office/calligra-3.2.1-r8: segfault at 56177c5d0116 ip 00007f326d174fbc sp 00007fff91dd3ae0 error 4 in libcalligrasheetsodf.so.17.0.0[7f326d061000+1a8000]
https://bugs.kde.org/show_bug.cgi?id=481758 Bug ID: 481758 Summary: app-office/calligra-3.2.1-r8: segfault at 56177c5d0116 ip 7f326d174fbc sp 7fff91dd3ae0 error 4 in libcalligrasheetsodf.so.17.0.0[7f326d061000+1a8000] Classification: Applications Product: calligrasheets Version: 3.2.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: opendocument Assignee: calligra-sheets-bugs-n...@kde.org Reporter: adobri...@gmail.com Target Milestone: --- Created attachment 166055 --> https://bugs.kde.org/attachment.cgi?id=166055=edit segfaulting ODS spreadsheet SUMMARY random segfault (not 100% reproducible) while typing in cells and marking text dark green. STEPS TO REPRODUCE 1. load attached ODS file 2. select A-F columns, on any line 3. make text green (Format/Font/Color, ...) 4. type something in E column, move to F column and type something else OBSERVED RESULT at least 2 different segfaults SOFTWARE/OS VERSIONS Linux/KDE Plasma: gentoo (-march=native -O2, nothing crazy) KDE Plasma Version: 5.27.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474488] Panel flickering at the top of some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=474488 --- Comment #23 from Alexey --- (In reply to Zamundaaa from comment #22) > The problem is that the window is not actually fullscreen. The problem is not reproducible in other desktop environments, so even if the change didn't fix the problem, it's still a problem on the KWin side. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459680] Sidebar animation stutter that can magically be resolved by clicking into "Appearance"
https://bugs.kde.org/show_bug.cgi?id=459680 Alexey Boltenko changed: What|Removed |Added CC||docar...@gmail.com --- Comment #4 from Alexey Boltenko --- This is still relevant as of 6.0 RC1. This happens in Settings until going into Colors & Themes, and this happens to the overview effect. X11 or Wayland doesn't seem to matter. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480402] KDE causes some fullscreen Wine/Proton games to twitch when interacting
https://bugs.kde.org/show_bug.cgi?id=480402 --- Comment #1 from Alexey --- Created attachment 165287 --> https://bugs.kde.org/attachment.cgi?id=165287=edit Bug demonstration -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480402] New: KDE causes some fullscreen Wine/Proton games to twitch when interacting
https://bugs.kde.org/show_bug.cgi?id=480402 Bug ID: 480402 Summary: KDE causes some fullscreen Wine/Proton games to twitch when interacting Classification: Plasma Product: kwin Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Add bottom Panel with "Always Visible" visibility option; 2. Launch Wine application that forces fullscreen resolution (in my case - HoMM3 under wine-ge-8-25); 3. Try to do some actions (in my case - click some in-game buttons). OBSERVED RESULT Fullscreen window shrinks making free space on top and in place of the panel, then returns to its original position. EXPECTED RESULT Nothing like this. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.114.0 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-arch1-1 (64-bit) ADDITIONAL INFORMATION Tested both on X11 and Wayland sessions. Observed on: - HotA (HoMM3 + HD) under Wine while interact with some action buttons; - Path of Exile under Steam's Proton Experimental while interact with options menu. Seems like this effect doesn't appears when Panel has "Auto Hide" or "Windows Can Cover" visibility option. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479766] kickoff unstable on wayland
https://bugs.kde.org/show_bug.cgi?id=479766 Alexey changed: What|Removed |Added Flags|X11?|X11- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479766] kickoff unstable on wayland
https://bugs.kde.org/show_bug.cgi?id=479766 Alexey changed: What|Removed |Added Flags||performance-, Wayland+, ||X11? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479766] New: kickoff unstable on wayland
https://bugs.kde.org/show_bug.cgi?id=479766 Bug ID: 479766 Summary: kickoff unstable on wayland Classification: Plasma Product: plasmashell Version: 5.92.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: alexey@icloud.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 164878 --> https://bugs.kde.org/attachment.cgi?id=164878=edit The video shows the problem Unable to use application launcher The problem occurs even if a different applet is created to run the applications, they both may not work, and may work at random times I haven't noticed this problem on x11 The problem is also present in plasma 5 STEPS TO REPRODUCE 1. Use wayland session 2. Do your business 3. After some time, the problem appears OBSERVED RESULT Kickoff don't work SOFTWARE/OS VERSIONS Linux kernel: 6.6.10-zen1-1-zen GPU: NVIDIA GEFORCE RTX 4060 Ti with proprietary driver [545.29.06] KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 Alexey changed: What|Removed |Added CC||ale...@toklovich.com --- Comment #15 from Alexey --- (In reply to Felipe Castilho from comment #14) > It seems to be happening again on 5.27.8, maybe a regression or something? > (I can provide video proof and/or more information if needed) I can confirm, it happens on my setup as well, 5.27.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475864] Error on switch from yandex browser to desktop
https://bugs.kde.org/show_bug.cgi?id=475864 Alexey Borealis changed: What|Removed |Added CC||a.n.borea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472175] Fetching updates lasts hours and hours.
https://bugs.kde.org/show_bug.cgi?id=472175 Alexey changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472175] Fetching updates lasts hours and hours.
https://bugs.kde.org/show_bug.cgi?id=472175 --- Comment #5 from Alexey --- (In reply to Nate Graham from comment #3) > Thanks, that's helpful. I guess it's stuck reloading the cache or some repo > over and over again? Have you installed any non-default RPM repos on your > system? Hi, again! Yes, I have several non-default RPM repos: ode Visual Studio Code docker-ce-stable Docker CE Stable - x86_64 expressvpn-repo expressvpn fedoraFedora 38 - x86_64 fedora-cisco-openh264 Fedora 38 openh264 (From Cisco) - x86_64 fedora-modularFedora Modular 38 - x86_64 google-chrome google-chrome oneAPIIntel® oneAPI repository rpmfusion-nonfree RPM Fusion for Fedora 38 - Nonfree rpmfusion-nonfree-nvidia-driver RPM Fusion for Fedora 38 - Nonfree - NVIDIA Driver rpmfusion-nonfree-steam RPM Fusion for Fedora 38 - Nonfree - Steam rpmfusion-nonfree-updates RPM Fusion for Fedora 38 - Nonfree - Updates updates Fedora 38 - x86_64 - Updates updates-modular Fedora Modular 38 - x86_64 - Updates -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472175] Fetching updates lasts hours and hours.
https://bugs.kde.org/show_bug.cgi?id=472175 --- Comment #2 from Alexey --- [asubbota ~]$ pkmon Transactions: [none] daemon connected=1 network status=online Transactions: 1 /2414_caacaedc Transactions: 1 /2414_caacaedc 2 /2415_dcdcabeb /2414_caacaedc allow_cancel 1 /2414_caacaedc percentage 32 /2414_caacaedc role refresh-cache /2414_caacaedc sender /usr/bin/plasma-discover /2414_caacaedc status loading-cache /2415_dcdcabeb allow_cancel 1 /2415_dcdcabeb percentage -1 /2415_dcdcabeb role refresh-cache /2415_dcdcabeb sender /usr/libexec/DiscoverNotifier /2415_dcdcabeb status wait ^[[2;5~/2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 38 /2414_caacaedc percentage 39 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 44 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 51 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 57 /2414_caacaedc percentage 58 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 63 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 70 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 76 /2414_caacaedc percentage 77 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 82 ... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 --- Comment #7 from Alexey --- Can I add here that I have the same bug in Fedora which uses dnf as a package manager instead of apt? Or should I create a new bug? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 Alexey changed: What|Removed |Added CC||alsubb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419055] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=419055 --- Comment #3 from Alexey --- I have the same bug on my system: Discover 5.27.6 Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.6-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Creator Z16 A11UE System Version: REV:1.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419055] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=419055 Alexey changed: What|Removed |Added CC||alsubb...@gmail.com Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 Bug 466693 depends on bug 419055, which changed state. Bug 419055 Summary: Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog. https://bugs.kde.org/show_bug.cgi?id=419055 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407403] Transformation and Mirror mode
https://bugs.kde.org/show_bug.cgi?id=407403 --- Comment #1 from Alexey --- We can draw in mirroring mode, but we can't make selection or transform mirrored. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472746] Snap to pixel: completely overlaps all other snapping options
https://bugs.kde.org/show_bug.cgi?id=472746 --- Comment #2 from Alexey --- (In reply to tomtomtomreportingin from comment #1) > On my end, a fresh install of Krita has "Snap to Pixel" disabled by default. But still, we need a way to work with both the grid and the pixel at the same time -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472746] New: Snap to pixel: completely overlaps all other snapping options
https://bugs.kde.org/show_bug.cgi?id=472746 Bug ID: 472746 Summary: Snap to pixel: completely overlaps all other snapping options Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- By default 'Snap to pixel' is enabled. And this completely overlaps all other snapping options. Like snap to grid or guides, which is needed more often. SIMPLE SOLUTION Disable 'Snap to pixel' by default COMPLEX SOLUTION Add priority parameters for binding types. For example. If we set the priority of the grid above the pixel, the result will be: "snap to pixel", but "snap to grid" if the distance to the grid line is less than 20 pixels (this should be in settings) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472743] Splitting lines by Shift+Enter: works in the edit window, but not on the canvas
https://bugs.kde.org/show_bug.cgi?id=472743 --- Comment #1 from Alexey --- Created attachment 160585 --> https://bugs.kde.org/attachment.cgi?id=160585=edit shift+enter -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472743] New: Splitting lines by Shift+Enter: works in the edit window, but not on the canvas
https://bugs.kde.org/show_bug.cgi?id=472743 Bug ID: 472743 Summary: Splitting lines by Shift+Enter: works in the edit window, but not on the canvas Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 160584 --> https://bugs.kde.org/attachment.cgi?id=160584=edit enter The lines can be separated by pressing Enter. The expected behavior occurs. But when you press Shift+Enter, the lines are separated in the editor window, but not on the canvas, which is not the expected behavior. This is misleading, as if the function does not work. STEPS TO REPRODUCE 1. add some words 2. move the text to another line by pressing Shift+Enter 3. apply text changes OBSERVED RESULT the text shows an undivided string EXPECTED RESULT the text shows a line break SOFTWARE/OS VERSIONS all os -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472175] New: Fetching updates lasts hours and hours.
https://bugs.kde.org/show_bug.cgi?id=472175 Bug ID: 472175 Summary: Fetching updates lasts hours and hours. Classification: Applications Product: Discover Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (offline) Assignee: plasma-b...@kde.org Reporter: alsubb...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 160241 --> https://bugs.kde.org/attachment.cgi?id=160241=edit Discover shows this for hours SUMMARY *** Fetching updates lasts hours and hours. *** STEPS TO REPRODUCE 1. Wait for "updates ready" notification 2. Open discover and click on fetching updates OBSERVED RESULT Fetching updates progress bar is about to finish but gets stuck there for hours EXPECTED RESULT It finishes in reasonable time (most in 1 minute I suppose) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 38 (KDE Plasma spin) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470321] New: dolphin crashed during creation and deletion of loop devices
https://bugs.kde.org/show_bug.cgi?id=470321
Bug ID: 470321
Summary: dolphin crashed during creation and deletion of loop
devices
Classification: Applications
Product: dolphin
Version: 22.12.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: alexey@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (22.12.3)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.2-gentoo x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
I was running postmarketOS bootstrap tool (pmbootstrap) and it creates
filesystem images by creating loop devices, mounting them, formatting, copying
files and umounting. I suppose bug is somewhere in solid in device enumeration?
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x21) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/atomic_base.h:486
#7 QAtomicOps::loadRelaxed (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239
#8 QBasicAtomicInteger::loadRelaxed (this=0x21) at
/usr/include/qt5/QtCore/qbasicatomic.h:107
#9 QtPrivate::RefCount::ref (this=0x21) at
/usr/include/qt5/QtCore/qrefcount.h:55
#10 QString::QString (other=..., this=this@entry=0x7ffcc8da6b80) at
/usr/include/qt5/QtCore/qstring.h:1094
#11 Solid::DevicePrivate::udi (this=0x557814437890) at
/usr/src/debug/kde-frameworks/solid-5.106.0/solid-5.106.0/src/solid/devices/frontend/device_p.h:32
#12 Solid::Device::udi (this=this@entry=0x55781364a230) at
/usr/src/debug/kde-frameworks/solid-5.106.0/solid-5.106.0/src/solid/devices/frontend/device.cpp:70
#13 0x7f32751830a8 in KFilePlacesItem::updateDeviceInfo
(this=this@entry=0x55781364a200, udi=...) at
/usr/src/debug/kde-frameworks/kio-5.106.0/kio-5.106.0/src/filewidgets/kfileplacesitem.cpp:461
#14 0x7f327518394d in KFilePlacesItem::setBookmark
(this=this@entry=0x55781364a200, bookmark=...) at
/usr/src/debug/kde-frameworks/kio-5.106.0/kio-5.106.0/src/filewidgets/kfileplacesitem.cpp:161
#15 0x7f327518d460 in KFilePlacesModelPrivate::reloadBookmarks
(this=this@entry=0x557812aea470) at
/usr/src/debug/kde-frameworks/kio-5.106.0/kio-5.106.0/src/filewidgets/kfileplacesmodel.cpp:842
#16 0x7f327518eca4 in KFilePlacesModelPrivate::deviceAdded (udi=...,
this=0x557812aea470) at
/usr/src/debug/kde-frameworks/kio-5.106.0/kio-5.106.0/src/filewidgets/kfileplacesmodel.cpp:783
#17 operator() (device=..., __closure=) at
/usr/src/debug/kde-frameworks/kio-5.106.0/kio-5.106.0/src/filewidgets/kfileplacesmodel.cpp:761
#18 QtPrivate::FunctorCall, QtPrivate::List, void, KFilePlacesModelPrivate::initDeviceList():: >::call (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#19 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#20
QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#21 0x7f32731adaa3 in QtPrivate::QSlotObjectBase::call
(this=0x557812ac8610, r=0x557812abb260, a=0x7ffcc8da6eb0) at
/usr/src/debug/dev-qt/qtcore-5.15.9/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#22 0x7f32731ef3b7 in doActivate (sender=0x557812af4ce0,
signal_index=3, argv=0x7ffcc8da6eb0) at
/usr/src/debug/dev-qt/qtcore-5.15.9/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3923
#23 0x7f32731e8a7d in QMetaObject::activate (sender=0x557812af4ce0,
m=0x7f3274b90ca0 ,
local_signal_index=0, argv=0x7ffcc8da6eb0) at
/usr/src/debug/dev-qt/qtcore-5.15.9/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3983
#24 0x7f3274af9af2 in Solid::DeviceNotifier::deviceAdded (this=, _t1=...) at
/usr/src/debug/kde-frameworks/solid-5.106.0/solid-5.106.0_build/src/solid/KF5Solid_autogen/include/moc_devicenotifier.cpp:144
#25 0x7f32731ef465 in doActivate (sender=0x557812b17090,
signal_index=3, argv=0x7ffcc8da7030) at
/usr/src/debug/dev-qt/qtcore-5.15.9/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3935
#26 0x7f32731e8a7d in QMetaObject::activate (sender=0x557812b17090,
m=0x7f3274b90480 ,
local_signal_index=0, argv=0x7ffcc8da7030) at
/usr/src/debug/dev-qt/qtcore-5.15.9/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3983
#27 0x7f3274ae6e22 in Solid::Ifaces::DeviceManager::deviceAdded
(this=this@entry=0x557812b17090, _t1=...)
[gcompris] [Bug 469326] Green/white tick are too far in activity "Letter in which word"
https://bugs.kde.org/show_bug.cgi?id=469326 --- Comment #4 from Alexey --- Created attachment 158805 --> https://bugs.kde.org/attachment.cgi?id=158805=edit gcompris with installed "qt5-image-formats-plugins", activity "Letter in which word" I've installed a package `qt5-image-formats-plugins` and now I see pictures together with words. I will try to create a bugreport for maintainers. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 469326] New: Green/white tick are too far in activity "Letter in which word"
https://bugs.kde.org/show_bug.cgi?id=469326 Bug ID: 469326 Summary: Green/white tick are too far in activity "Letter in which word" Classification: Applications Product: gcompris Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: vazh...@boot-keys.org Target Milestone: --- Created attachment 158671 --> https://bugs.kde.org/attachment.cgi?id=158671=edit gcompris activity "Letter in which word" with ticks SUMMARY I use package gcompris-qt from Devuan testing repository. In activity "Letter in which word", when I select words, green ticks are placed too far from the word. It would be great to place ticks closer to the selected word, or maybe just highlight selected words instead of using ticks (or even both). STEPS TO REPRODUCE 1. Choose activity "Letter in which word". 2. Click on any word. 3. Observe green/white tick. OBSERVED RESULT Ticks are too far from selected words. EXPECTED RESULT The selected words has ticks near, or words are highlighted as an alternative. SOFTWARE/OS VERSIONS gcompris-qt: 3.1-2. Linux/KDE Plasma: Devuan 5 daedalus/ceres (based on Debian 12 bookworm). Desktop environment: XFCE 4.18.2. KDE Plasma Version: - KDE Frameworks Version: - Qt Version: 5.15.8 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 428863] The letter sounds should be the phonemes, not the letter names
https://bugs.kde.org/show_bug.cgi?id=428863 Alexey changed: What|Removed |Added CC||fuxfwgc4a2i...@gmail.com --- Comment #2 from Alexey --- *** Bug 446848 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 446848] Gcompris say alphabet letter names instead of actual letter sound.
https://bugs.kde.org/show_bug.cgi?id=446848 Alexey changed: What|Removed |Added CC||vazh...@boot-keys.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Alexey --- Is it a duplicate for https://bugs.kde.org/show_bug.cgi?id=428863 ? *** This bug has been marked as a duplicate of bug 428863 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Alexey Sokolov changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=463755 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 463755] Fetched articles are sometimes put to wrong feed
https://bugs.kde.org/show_bug.cgi?id=463755 Alexey Sokolov changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=458116 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Alexey Sokolov changed: What|Removed |Added CC||alexey+...@asokolov.org --- Comment #39 from Alexey Sokolov --- mel from https://bugs.kde.org/show_bug.cgi?id=463755 saw this issue on 5.101 too -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 463755] Fetched articles are sometimes put to wrong feed
https://bugs.kde.org/show_bug.cgi?id=463755 --- Comment #2 from Alexey Sokolov --- (In reply to mel from comment #1) What's your Akregator version? that's separate 2 numbers from frameworks etc. Available in Help/About above the tabs -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 463755] New: Fetched articles are sometimes put to wrong feed
https://bugs.kde.org/show_bug.cgi?id=463755 Bug ID: 463755 Summary: Fetched articles are sometimes put to wrong feed Classification: Applications Product: akregator Version: 5.21.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: alexey+...@asokolov.org Target Milestone: --- Created attachment 154975 --> https://bugs.kde.org/attachment.cgi?id=154975=edit Screenshot SUMMARY Fetched articles are sometimes put to wrong feed STEPS TO REPRODUCE 1. unknown, potentially this has something to do with unstable network 2. 3. OBSERVED RESULT Since recently I see that randomly some entries are in wrong feed. See the screenshot attached: it shows "asio" articles in "yaml-cpp" feed, and the "asio" feed shows broken icon instead of the usual feed favicon (of github in this case). If I just tell the broken feed (asio on the screenshot) to refresh, it successfully does so. But every time this happens I also need to clean the feed which received these articles. Whenever it breaks again, I see the notification about 10 new articles. I saw this happening not only with github feeds. This feels like some kind of race between different feeds starting the fetch and asynchronously getting the result or the error. EXPECTED RESULT Every article should be put to the correct place SOFTWARE/OS VERSIONS Linux/KDE Plasma: kernel 5.15.80-gentoo x86_64 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: kde-frameworks/plasma-5.99.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma Mobile Dialer] [Bug 462892] Crashes under X
https://bugs.kde.org/show_bug.cgi?id=462892 --- Comment #1 from Alexey Andreyev --- (In reply to genghiskhan from comment #0) > Is this a bug or is this program exclusive to Wayland? > There are distros using X, which I use because of some programs I need, and > it would be nice to make calls from desktop. > > Tested on Alpine Linux. Hi! Yeah, unfortunately for X11, the default build uses Wayland-specific feature, kde_lockscreen_overlay_v1 (https://invent.kde.org/plasma-mobile/plasma-dialer/-/blob/d59dc52006707d7f94d93142d94ac19c03cea954/plasma-dialer/org.kde.phone.dialer.desktop#L82). This feature provides dialer UI on top of the lockscreen and is not implemented for X11. Currently it's even kwin and plasma-wayland-protocols specific (see also: https://invent.kde.org/libraries/plasma-wayland-protocols/-/merge_requests/41 and https://invent.kde.org/plasma/kwin/-/merge_requests/2385) There's CMakeLists DIALER_BUILD_SHELL_OVERLAY option for it: https://invent.kde.org/plasma-mobile/plasma-dialer/-/blob/d59dc52006707d7f94d93142d94ac19c03cea954/CMakeLists.txt#L10 Turning it off at built time should prevent the crash at X11 environment. Not sure is it makes sense to try to detect it at runtime, but ready to think about better implementations. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Mobile Dialer] [Bug 462601] Plasma-dialer 22.11 segfaults when started, core dump included
https://bugs.kde.org/show_bug.cgi?id=462601 --- Comment #6 from Alexey Andreyev --- (In reply to Alexey Andreyev from comment #5) > Hi! Could you please also provide the versions info for the kirigami-addons > and kwin? > There's CMake flag for the dialer: `DIALER_BUILD_SHELL_OVERLAY` to build the > package with or without lockscreen overlay support. Lockscreen overlay is > only working with kwin (fresh enough, see also: > https://invent.kde.org/plasma/kwin/-/merge_requests/3232) > Also fresh kirigami-addons is needed, see also: > https://invent.kde.org/plasma-mobile/plasma-dialer/-/merge_requests/109 ah, sorry for the late reply, you probably also received same info via the matrix chat -- You are receiving this mail because: You are watching all bug changes.
[Plasma Mobile Dialer] [Bug 462601] Plasma-dialer 22.11 segfaults when started, core dump included
https://bugs.kde.org/show_bug.cgi?id=462601 --- Comment #5 from Alexey Andreyev --- Hi! Could you please also provide the versions info for the kirigami-addons and kwin? There's CMake flag for the dialer: `DIALER_BUILD_SHELL_OVERLAY` to build the package with or without lockscreen overlay support. Lockscreen overlay is only working with kwin (fresh enough, see also: https://invent.kde.org/plasma/kwin/-/merge_requests/3232) Also fresh kirigami-addons is needed, see also: https://invent.kde.org/plasma-mobile/plasma-dialer/-/merge_requests/109 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460790] Plasma crashes in QScreen::geometry() after reboot
https://bugs.kde.org/show_bug.cgi?id=460790 --- Comment #2 from Alexey Chernyak --- Created attachment 153726 --> https://bugs.kde.org/attachment.cgi?id=153726=edit New crash information added by DrKonqi plasmashell (5.26.3) using Qt 5.15.5 Crash happened while changing X server configuration via NVIDIA Settings. -- Backtrace (Reduced): #4 QScreen::geometry() const (this=0x0) at /mnt/tmpfs/portage/dev-qt/qtgui-5.15.5-r2/work/qtbase-everywhere-src-5.15.5/src/gui/kernel/qscreen.cpp:419 #5 0x55de27f286bf in PanelView::geometryByDistance(int) const (this=this@entry=0x55de29d88970, distance=0) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.26.3-r1/work/plasma-workspace-5.26.3/shell/panelview.cpp:533 #6 0x55de27f28b30 in PanelView::positionPanel() (this=this@entry=0x55de29d88970) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.26.3-r1/work/plasma-workspace-5.26.3/shell/panelview.cpp:519 #7 0x55de27f2a0ce in PanelView::updateFloating() (this=this@entry=0x55de29d88970) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.26.3-r1/work/plasma-workspace-5.26.3/shell/panelview.cpp:1562 #8 0x55de27f2a1a7 in PanelView::handleQmlStatusChange(QQmlComponent::Status) (this=0x55de29d88970, status=) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.26.3-r1/work/plasma-workspace-5.26.3/shell/panelview.cpp:1380 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460790] Plasma crashes in QScreen::geometry() after reboot
https://bugs.kde.org/show_bug.cgi?id=460790 Alexey Chernyak changed: What|Removed |Added CC||alexey_...@chernyak.id.au -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460790] New: Plasma crashes in QScreen::geometry() after reboot
https://bugs.kde.org/show_bug.cgi?id=460790 Bug ID: 460790 Summary: Plasma crashes in QScreen::geometry() after reboot Classification: Plasma Product: plasmashell Version: 5.26.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexey_...@chernyak.id.au CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.26.1) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.99.0 Operating System: Linux 6.0.2-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.26.1 [KCrashBackend] -- Information about the crash: Plasmashell segfaults on login after a reboot. Most likely related to bug 450068. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 QScreen::geometry() const (this=0x0) at /mnt/tmpfs/portage/dev-qt/qtgui-5.15.5-r2/work/qtbase-everywhere-src-5.15.5/src/gui/kernel/qscreen.cpp:419 #5 0x560b9ad116bf in PanelView::geometryByDistance(int) const (this=this@entry=0x560b9b9b3770, distance=0) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.26.1/work/plasma-workspace-5.26.1/shell/panelview.cpp:533 #6 0x560b9ad11b30 in PanelView::positionPanel() (this=this@entry=0x560b9b9b3770) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.26.1/work/plasma-workspace-5.26.1/shell/panelview.cpp:519 #7 0x560b9ad130ce in PanelView::updateFloating() (this=this@entry=0x560b9b9b3770) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.26.1/work/plasma-workspace-5.26.1/shell/panelview.cpp:1562 #8 0x560b9ad131a7 in PanelView::handleQmlStatusChange(QQmlComponent::Status) (this=0x560b9b9b3770, status=) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.26.1/work/plasma-workspace-5.26.1/shell/panelview.cpp:1380 #9 0x7fcebc8497cd in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd475b5c00, r=0x560b9b9b3770, this=0x560b9bfc09a0) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate(QObject*, int, void**) (sender=0x560b9b9b3770, signal_index=38, argv=0x7ffd475b5c00) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:3886 #11 0x7fcebc84383f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fcebe99dac0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd475b5c00) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:3946 #12 0x7fcebe995bee in KQuickAddons::QuickViewSharedEngine::statusChanged(QQmlComponent::Status) (this=, _t1=) at /mnt/tmpfs/portage/kde-frameworks/kdeclarative-5.99.0/work/kdeclarative-5.99.0_build/src/quickaddons/KF5QuickAddons_autogen/include/moc_quickviewsharedengine.cpp:251 #13 0x7fcebc8497cd in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd475b5d00, r=0x560b9b9b3770, this=0x560b9bd4e810) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate(QObject*, int, void**) (sender=0x560b9bd958a0, signal_index=4, argv=0x7ffd475b5d00) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:3886 #15 0x7fcebc84383f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fcebe6dfb60 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd475b5d00) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:3946 #16 0x7fcebe6d79e1 in KDeclarative::QmlObject::statusChanged(QQmlComponent::Status) (this=, _t1=) at /mnt/tmpfs/portage/kde-frameworks/kdeclarative-5.99.0/work/kdeclarative-5.99.0_build/src/kdeclarative/KF5Declarative_autogen/include/moc_qmlobject.cpp:241 #17 0x7fcebc841a14 in QObject::event(QEvent*) (this=0x560b9bd958a0, e=0x560b9b68f6e0) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:1314 #18 0x7fcebd4a3fde in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x560b9bd958a0, e=0x560b9b68f6e0) at /mnt/tmpfs/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qapplication.cpp:3637 #19 0x7fcebc8176a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x560b9bd958a0, event=0x560b9b68f6e0) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qcoreapplication.cpp:1064 #20 0x7fcebc81a964 in
[Discover] [Bug 460360] New: Plasma discover notifier crashes after sleep
https://bugs.kde.org/show_bug.cgi?id=460360 Bug ID: 460360 Summary: Plasma discover notifier crashes after sleep Classification: Applications Product: Discover Version: 5.24.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: plasma-b...@kde.org Reporter: ashl1fut...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: DiscoverNotifier (5.24.6) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-50-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Closed laptop lid for several hours, then opened it, entered user password. The crash can be reproduced sometimes. -- Backtrace: Application: Уведомления центра программ Discover (DiscoverNotifier), signal: Segmentation fault [KCrash Handler] #4 QHashData::nextNode (node=node@entry=0x55b88270ba30) at tools/qhash.cpp:591 #5 0x7f9e44515ee8 in QHash::const_iterator::operator++ (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:425 #6 KIdleTimePrivate::timeoutReached (msec=, this=0x55b882711010) at ./src/kidletime.cpp:291 #7 operator() (msec=, __closure=) at ./src/kidletime.cpp:88 #8 QtPrivate::FunctorCall, QtPrivate::List, void, KIdleTime::KIdleTime():: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #9 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #10 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl (which=, r=, ret=, a=, this_=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #11 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:436 #12 0x7f9e4309c793 in QtPrivate::QSlotObjectBase::call (a=0x7ffc7370ce60, r=0x55b8827d6b50, this=0x55b8827112c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x55b8827ccab0, signal_index=4, argv=0x7ffc7370ce60) at kernel/qobject.cpp:3886 #14 0x7f9e43095aa7 in QMetaObject::activate (sender=sender@entry=0x55b8827ccab0, m=m@entry=0x7f9e4451da60 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc7370ce60) at kernel/qobject.cpp:3946 #15 0x7f9e44515c75 in AbstractSystemPoller::timeoutReached (this=this@entry=0x55b8827ccab0, _t1=) at ./obj-x86_64-linux-gnu/src/KF5IdleTime_autogen/EWIEGA46WW/moc_abstractsystempoller.cpp:189 #16 0x7f9e35c52e3b in XSyncBasedPoller::xcbEvent (event=0x7f9e380043d0, this=0x55b8827ccab0) at ./src/plugins/xsync/xsyncbasedpoller.cpp:295 #17 XSyncBasedPoller::xcbEvent (event=0x7f9e380043d0, this=0x55b8827ccab0) at ./src/plugins/xsync/xsyncbasedpoller.cpp:279 #18 XSyncBasedPollerHelper::nativeEventFilter (result=, message=0x7f9e380043d0, eventType=..., this=0x7f9e35c57060 <(anonymous namespace)::Q_QGS_s_globalXSyncBasedPoller::innerFunction()::holder>) at ./src/plugins/xsync/xsyncbasedpoller.cpp:44 #19 XSyncBasedPollerHelper::nativeEventFilter (this=0x7f9e35c57060 <(anonymous namespace)::Q_QGS_s_globalXSyncBasedPoller::innerFunction()::holder>, eventType=..., message=0x7f9e380043d0, result=) at ./src/plugins/xsync/xsyncbasedpoller.cpp:39 #20 0x7f9e43062207 in QAbstractEventDispatcher::filterNativeEvent (this=, eventType=..., message=message@entry=0x7f9e380043d0, result=result@entry=0x7ffc7370cef8) at kernel/qabstracteventdispatcher.cpp:495 #21 0x7f9e3eeedb05 in QXcbConnection::handleXcbEvent (this=this@entry=0x55b882664290, event=event@entry=0x7f9e380043d0) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:536 #22 0x7f9e3eeef116 in QXcbConnection::processXcbEvents (this=0x55b882664290, flags=...) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:1014 #23 0x7f9e3ef15d67 in xcbSourceDispatch (source=) at ./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:103 #24 0x7f9e41a90d1b in g_main_dispatch (context=0x7f9e38005010) at ../../../glib/gmain.c:3417 #25 g_main_context_dispatch (context=0x7f9e38005010) at ../../../glib/gmain.c:4135 #26 0x7f9e41ae56f8 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f9e38005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4211 #27 0x7f9e41a8e3c3 in g_main_context_iteration (context=0x7f9e38005010, may_block=1) at ../../../glib/gmain.c:4276 #28 0x7f9e430be0b8 in QEventDispatcherGlib::processEvents (this=0x55b8827371f0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #29 0x7f9e4306375b in QEventLoop::exec (this=this@entry=0x7ffc7370d180, flags=..., flags@entry=...) at
[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 --- Comment #251 from Alexey Chernyak --- (In reply to Fushan Wen from comment #248) > (In reply to Bug Janitor Service from comment #247) > > A possibly relevant merge request was started @ > > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2186 > > Could people seeing the bug try this patch to see if the bug is ""mitigated"? Tried with the patch applied to v5.26 Plasma on Gentoo. Issue remains. After waking two DisplayPort monitors from sleep, one of them has black screen with no wallpaper, no icons, no context menu. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455534] plasma-apply-lookandfeel crash in KCMLookandFeel::save()
https://bugs.kde.org/show_bug.cgi?id=455534 Alexey Shildyakov changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Alexey Shildyakov --- After upgrading to Ubuntu 22.04 the problem is gone -- 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 Alexey Chernyak changed: What|Removed |Added CC||alexey_...@chernyak.id.au --- Comment #193 from Alexey Chernyak --- Bug still present in X11 Plasma 5.25.3. The bug is triggered depending 3 things: 1. Which monitor is set as the X Primary Display for X Screen (not sure if Wayland has a similar concept) 2. Which monitor wakes up first from sleep 3. Which monitor is configured to have Plasma Taskbar. Reproducible: Always Steps to reproduce: 1. Get 2 different monitor models that have different sleep/wakeup latency - in my case both are DisplayPort with different resolutions. My understanding is that DisplayPort sleep/wakeup is equivalent to disconnectintg/reconnecting cable. 2. Set the faster waking monitor as the Primary Display for X Screen - in my case I can do this with a tick-box in NVIDIA Settings application. 3. Place Plasma Taskbar onto the non-Primary monitor. 4. Leave system idle until both monitors go to sleep - in my case system itself doesn't sleep, only monitors and no screen locking. 5. Wake monitors up. Actual Results: Monitors wake up with Plasma missing - no taskbar, no desktop icons, no wallpaper, black screen, right click not working. Windows can be dragged between monitors. Can Alt-Tab between windows. No DrKonqi crash reports. During first wakeup cycle KDE screens configuration seems to get reconfigured (depending on monitor wake-up order), and subsequent sleep/wake cycles could have different results and screen configuration (though taskbar always missing) depending on each pre-sleep state. Expected Results: Plasmashell not to disappear. Workaround Fix: Make the slower waking monitor as the Primary Display for the X Screen (in NVIDIA Settings tool), and have Plasma Taskbar residing on the faster waking screen. With this configuration every sleep/wakeup cycle works without any issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455328] X11 Plasma crashes in QScreen::geometry() after dual DisplayPort monitors on nvidia wake up from sleep
https://bugs.kde.org/show_bug.cgi?id=455328 --- Comment #12 from Alexey Chernyak --- (In reply to Fushan Wen from comment #11) > Did you try the two commits? They are included in 5.25.2. I now have upgraded to 5.25.2. It looks like this patch has also made it into 5.25.2 - so I didn't have to explicitly apply it. On first wakeup - taskbar disappeared and desktop icons moved to another monitor.. On second wakeup - taskbar still gone, desktop icons disappeared, and one of monitor wallpapers disappeared, has just black background now. No KCrash Handler dialogs. So I guess this particular crash itself may be fixed, but Plasma remains messed up and unusable after monitor sleeps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455328] X11 Plasma crashes in QScreen::geometry() after dual DisplayPort monitors on nvidia wake up from sleep
https://bugs.kde.org/show_bug.cgi?id=455328 --- Comment #10 from Alexey Chernyak --- I have applied the patch, and the issue seems to be somewhat better. The first time when monitors woke up from sleep - everything looked good - for the first time in months. Second time, however, the taskbar was missing again. Desktop icons did return but on a different screen from before sleep. There was no KCrash Handler dialog box, so don't know what it was (sometimes it doesn't appear). Some thoughts about how it ends up in this state... My understanding is that when a DisplayPort monitor goes to sleep, it's as if it has been completely disconnected from the system, and when it wakes up - it's as it it was plugged in again. My two DisplayPort monitors are different models, and they have different wake-up latency. So one of them usually wakes up a second or two before the other. On wakeup I usually observe windows on my screen do all kinds of acrobatics: * A windows that was full screen on one of the monitors, suddenly becomes widely stretched full screen across both monitors, and then returns back to being fullscreen on one monitor. * Desktop icons end up on the monitor different to the one they were on before sleep. * Some open application windows also end up on monitor different to the one they were on before sleep. I would suspect that Plasma goes haywire in the interim state in between one of the monitors being already awake, and the other one not awake yet. I think the observed results may be slightly different depending on: * Which monitor was the primary display for X before sleep. * Which monitor had the KDE taskbar and desktop icons before sleep. * Which monitor gets put to sleep (i.e. disconnected) first. * Which of the two monitors wakes up and reconnects first. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455328] X11 Plasma crashes in QScreen::geometry() after dual DisplayPort monitors on nvidia wake up from sleep
https://bugs.kde.org/show_bug.cgi?id=455328 --- Comment #4 from Alexey Chernyak --- Is this enough, or you need more? Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 QScreen::geometry() const (this=0x0) at /mnt/tmpfs/portage/dev-qt/qtgui-5.15.5/work/qtbase-everywhere-src-5.15.5/src/gui/kernel/qscreen.cpp:413 #5 0x5598c2fe614f in PanelView::geometryByDistance(int) const (this=this@entry=0x5598c65b9190, distance=0) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.25.1/work/plasma-workspace-5.25.1/shell/panelview.cpp:533 #6 0x5598c2fe9411 in PanelView::resizeEvent(QResizeEvent*) (this=0x5598c65b9190, ev=0x7ffce5689c70) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.25.1/work/plasma-workspace-5.25.1/shell/panelview.cpp:841 #7 0x7f32cb896ce5 in QWindow::event(QEvent*) (this=0x5598c65b9190, ev=) at /mnt/tmpfs/portage/dev-qt/qtgui-5.15.5/work/qtbase-everywhere-src-5.15.5/src/gui/kernel/qwindow.cpp:2438 #8 0x7f32cc107f5e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x5598c65b9190, e=0x7ffce5689c70) at /mnt/tmpfs/portage/dev-qt/qtwidgets-5.15.5/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qapplication.cpp:3637 #9 0x7f32cb48b138 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5598c65b9190, event=0x7ffce5689c70) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qcoreapplication.cpp:1064 #10 0x7f32cb8886ce in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) (e=) at /mnt/tmpfs/portage/dev-qt/qtgui-5.15.5/work/qtbase-everywhere-src-5.15.5/src/gui/kernel/qguiapplication.cpp:2607 #11 0x7f32cb86b16c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) (flags=flags@entry=...) at /mnt/tmpfs/portage/dev-qt/qtgui-5.15.5/work/qtbase-everywhere-src-5.15.5/src/gui/kernel/qwindowsysteminterface.cpp:1169 #12 0x7f32c69c1b1a in xcbSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at /mnt/tmpfs/portage/dev-qt/qtgui-5.15.5/work/qtbase-everywhere-src-5.15.5/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105 #13 0x7f32c99ebac9 in g_main_dispatch (context=0x7f32c0005010) at ../glib-2.72.2/glib/gmain.c:3417 #14 g_main_context_dispatch (context=0x7f32c0005010) at ../glib-2.72.2/glib/gmain.c:4135 #15 0x7f32c99ebd58 in g_main_context_iterate (context=context@entry=0x7f32c0005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.72.2/glib/gmain.c:4211 #16 0x7f32c99ebdec in g_main_context_iteration (context=0x7f32c0005010, may_block=1) at ../glib-2.72.2/glib/gmain.c:4276 #17 0x7f32cb4daf16 in QEventDispatcherGlib::processEvents(QFlags) (this=0x5598c3c85b10, flags=...) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #18 0x7f32cb489c0b in QEventLoop::exec(QFlags) (this=this@entry=0x7ffce5689ef0, flags=..., flags@entry=...) at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5/work/qtbase-everywhere-src-5.15.5/include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x7f32cb491a56 in QCoreApplication::exec() () at /mnt/tmpfs/portage/dev-qt/qtcore-5.15.5/work/qtbase-everywhere-src-5.15.5/include/QtCore/../../src/corelib/global/qflags.h:121 #20 0x7f32cb88060c in QGuiApplication::exec() () at /mnt/tmpfs/portage/dev-qt/qtgui-5.15.5/work/qtbase-everywhere-src-5.15.5/src/gui/kernel/qguiapplication.cpp:1867 #21 0x7f32cc107ed5 in QApplication::exec() () at /mnt/tmpfs/portage/dev-qt/qtwidgets-5.15.5/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qapplication.cpp:2829 #22 0x5598c2fd1725 in main(int, char**) (argc=, argv=) at /mnt/tmpfs/portage/kde-plasma/plasma-workspace-5.25.1/work/plasma-workspace-5.25.1/shell/main.cpp:240 [Inferior 1 (process 4376) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455328] X11 Plasma crashes in QScreen::geometry() after dual DisplayPort monitors on nvidia wake up from sleep
https://bugs.kde.org/show_bug.cgi?id=455328 --- Comment #2 from Alexey Chernyak --- Still happens after upgrade to: Qt: v5.15.5 Plasma: v5.25.1 Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f123bd01150 in QScreen::geometry() const () at /usr/lib64/libQt5Gui.so.5 #5 0x557dad6162bf in () #6 0x557dad6195a2 in () #7 0x7f123bce6b65 in QWindow::event(QEvent*) () at /usr/lib64/libQt5Gui.so.5 #8 0x7f123c56071f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #9 0x7f123b8d93d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7f123bcd8699 in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () at /usr/lib64/libQt5Gui.so.5 #11 0x7f123bcbb02c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #12 0x7f1236e2756a in () at /usr/lib64/libQt5XcbQpa.so.5 #13 0x7f1239e4fc0c in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #14 0x7f1239e4feb8 in () at /usr/lib64/libglib-2.0.so.0 #15 0x7f1239e4ff6f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #16 0x7f123b9298d8 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #17 0x7f123b8d7e6b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #18 0x7f123b8e01a0 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #19 0x557dad601758 in () #20 0x7f123b28820a in () at /lib64/libc.so.6 #21 0x7f123b2882bc in __libc_start_main () at /lib64/libc.so.6 #22 0x557dad601971 in () [Inferior 1 (process 4381) detached] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455534] plasma-apply-lookandfeel crash in KCMLookandFeel::save()
https://bugs.kde.org/show_bug.cgi?id=455534 Alexey Shildyakov changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Alexey Shildyakov --- Yes, I see in a souce code, that it's almost rewrited Unfortunately, I use Kubuntu and they've been blocked new Ubuntu 22.04 release due some fatal errors with kde applications and I'm waiting for next fix release 22.04.1 expected only at August. The problem wasn't presented from the start. I've changed the theme to Dark first and work with this for a month. Thus I assume the problem in a configuration. As of today how can I clear KDE configiration files? I remembered I can clear som .kde directory to start KDE from the scratch? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455534] plasma-apply-lookandfeel crash
https://bugs.kde.org/show_bug.cgi?id=455534 --- Comment #1 from Alexey Shildyakov --- kde-workspace version looks like 5.22.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455534] New: plasma-apply-lookandfeel crash
https://bugs.kde.org/show_bug.cgi?id=455534 Bug ID: 455534 Summary: plasma-apply-lookandfeel crash Product: systemsettings Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: ashl1fut...@gmail.com Target Milestone: --- Application: plasma-apply-lookandfeel (1.0) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.13.0-51-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: Ubuntu 21.10 -- Information about the crash: - What I was doing when the application crashed: 0. Dark theme has alredy been selected but not applied. This is not a first time app was crashed 1. Choose Light mode. Apply. Interface has been blinked, because I've already have light interface 2. Choose Dark mode. Apply. Crash on aplying The crash can be reproduced every time. -- Backtrace: Application: Инструмент для выбора оформления рабочей среды (plasma-apply-lookandfeel), signal: Segmentation fault [KCrash Handler] #4 KCMLookandFeel::save (this=) at ./kcms/lookandfeel/kcm.cpp:427 #5 0x55adcff1ed92 in main (argc=, argv=) at ./kcms/lookandfeel/lnftool.cpp:114 [Inferior 1 (process 22605) detached] Possible duplicates by query: bug 455260, bug 454500, bug 454322, bug 454240, bug 454201. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455328] X11 Plasma crashes in QScreen::geometry() after dual DisplayPort monitors on nvidia wake up from sleep
https://bugs.kde.org/show_bug.cgi?id=455328 Alexey Chernyak changed: What|Removed |Added Platform|Compiled Sources|Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455328] New: X11 Plasma crashes in QScreen::geometry() after dual DisplayPort monitors on nvidia wake up from sleep
https://bugs.kde.org/show_bug.cgi?id=455328 Bug ID: 455328 Summary: X11 Plasma crashes in QScreen::geometry() after dual DisplayPort monitors on nvidia wake up from sleep Product: plasmashell Version: 5.25.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexey_...@chernyak.id.au CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.0) (Compiled from sources) Qt Version: 5.15.4 Frameworks Version: 5.95.0 Operating System: Linux 5.18.4-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.25.0 [KCrashBackend] -- Information about the crash: SUMMARY My Plasma has been crashing every time I wake up my dual DisplayPort monitors on nVIDIA from sleep for the past few releases. I suspect it started happening when I upgraded to Qt v5.15.3 a few months ago and continues happening with Qt v5.15.4. Blowing away ~/.config and creating new profile did not fix it. STEPS TO REPRODUCE 1. Login to X11 session using dual monitors connected to nVIDIA video card via DisplayPort cables. 2. Leave it idle until monitors go to sleep (desktop should be configured not to go to sleep). 3. Wake monitors up and get back into the session (with or withour screen lock, it doesn't matter). OBSERVED RESULT Plasma crashes every time, with taskbar, desktop icons and wallpapers all gone. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS X.org Version: 21.1.3 nVIDIA Drivers Version: 515.48.07 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fea5ef46160 in QScreen::geometry() const () at /usr/lib64/libQt5Gui.so.5 #5 0x5652efca82bf in () #6 0x5652efcab5a2 in () #7 0x7fea5ef2bb75 in QWindow::event(QEvent*) () at /usr/lib64/libQt5Gui.so.5 #8 0x7fea5f7a56df in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #9 0x7fea5eb21398 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7fea5ef1d6a9 in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () at /usr/lib64/libQt5Gui.so.5 #11 0x7fea5ef0003c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #12 0x7fea5a06a42a in () at /usr/lib64/libQt5XcbQpa.so.5 #13 0x7fea5d097c0c in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #14 0x7fea5d097eb8 in () at /usr/lib64/libglib-2.0.so.0 #15 0x7fea5d097f6f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #16 0x7fea5eb71898 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #17 0x7fea5eb1fe2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #18 0x7fea5eb28160 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #19 0x5652efc93758 in () #20 0x7fea5e4d020a in () at /lib64/libc.so.6 #21 0x7fea5e4d02bc in __libc_start_main () at /lib64/libc.so.6 #22 0x5652efc93971 in () [Inferior 1 (process 4567) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
