[kmymoney] [Bug 435581] Stable Windows builds miss aqbanking plugin and languages
https://bugs.kde.org/show_bug.cgi?id=435581 Bug 435581 depends on bug 435866, which changed state. Bug 435866 Summary: No ledger icon in the pane of the left side https://bugs.kde.org/show_bug.cgi?id=435866 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435866] No ledger icon in the pane of the left side
https://bugs.kde.org/show_bug.cgi?id=435866 Dawid Wróbel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.1.3 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/-/commit/32c7f2 ||a16ad14f50834f43d9e338b939c ||05dcef1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435866] No ledger icon in the pane of the left side
https://bugs.kde.org/show_bug.cgi?id=435866 Dawid Wróbel changed: What|Removed |Added Ever confirmed|0 |1 CC||m...@dawidwrobel.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438931] In split editing view, the "Delete split" button is missing
https://bugs.kde.org/show_bug.cgi?id=438931 Dawid Wróbel changed: What|Removed |Added Resolution|LATER |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438931] In split editing view, the "Delete split" button is missing
https://bugs.kde.org/show_bug.cgi?id=438931 Dawid Wróbel changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438522] App menu username text is black, should be white.
https://bugs.kde.org/show_bug.cgi?id=438522 --- 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.
[krita] [Bug 437882] Render animation gives unknown error.
https://bugs.kde.org/show_bug.cgi?id=437882 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438680] Feature request: Large play queue
https://bugs.kde.org/show_bug.cgi?id=438680 --- 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.
[kde] [Bug 438543] Voice Input not working at all for speech to text
https://bugs.kde.org/show_bug.cgi?id=438543 --- 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.
[plasmashell] [Bug 438605] Plasma's new transparent elements are too bright
https://bugs.kde.org/show_bug.cgi?id=438605 --- 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.
[kdenlive] [Bug 438544] I can't start kdenlive
https://bugs.kde.org/show_bug.cgi?id=438544 --- 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.
[kde] [Bug 438642] When I try to change the icon for the application dashboard,then my desktop vanishes.
https://bugs.kde.org/show_bug.cgi?id=438642 --- Comment #4 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.
[plasma-nm] [Bug 438461] Widget fails to load
https://bugs.kde.org/show_bug.cgi?id=438461 --- Comment #5 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.
[plasmashell] [Bug 438439] Panel Opacity Menu Crash
https://bugs.kde.org/show_bug.cgi?id=438439 --- 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.
[Discover] [Bug 438448] EVERY Login Discover-Notifier tells me to restart
https://bugs.kde.org/show_bug.cgi?id=438448 --- 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.
[kwin] [Bug 438046] kwin_wayland crashed
https://bugs.kde.org/show_bug.cgi?id=438046 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436548] App icon menus opens on the screen at the left of the current window
https://bugs.kde.org/show_bug.cgi?id=436548 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 419163] System Tray has no context menu
https://bugs.kde.org/show_bug.cgi?id=419163 --- Comment #10 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.
[frameworks-plasma] [Bug 387797] Scrollviews automatically scroll up or down when you hover over a partially-visible list item
https://bugs.kde.org/show_bug.cgi?id=387797 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439323] timeline scrolls up when dragging clip from project bin
https://bugs.kde.org/show_bug.cgi?id=439323 --- Comment #1 from S. Christian Collins --- Created attachment 139759 --> https://bugs.kde.org/attachment.cgi?id=139759=edit video showing the bug -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439323] New: timeline scrolls up when dragging clip from project bin
https://bugs.kde.org/show_bug.cgi?id=439323 Bug ID: 439323 Summary: timeline scrolls up when dragging clip from project bin Product: kdenlive Version: git-master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: s_chriscoll...@hotmail.com Target Milestone: --- SUMMARY When there are more tracks than can be displayed on the timeline at once, trying to drag a clip to the bottom track results in the timeline view scrolling up. Please see the attached video. STEPS TO REPRODUCE 1. Create a large number of tracks, more than can fit in the timeline view at once (vertical scrolling must be used to see the remaining tracks). 2. Vertically scroll the timeline so that the bottom track is visible. 3. Drag a clip from the project bin to the bottom track. OBSERVED RESULT When the dragged clip crosses the boundary between the project bin and the timeline (assuming the project bin's default position above the timeline), the timeline view scrolls up automatically, and the bottom track is no longer visible. EXPECTED RESULT The view shouldn't scroll up when a clip is initially dragged onto the timeline. SOFTWARE/OS VERSIONS Linux: KDE neon 5.22 User Edition KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION This bug happens with 21.04.2 both from neon packages and the AppImage, and also with the latest daily AppImage (8ecff03). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438340] Animation curves - Rotation with Transform Mask - Glitches
https://bugs.kde.org/show_bug.cgi?id=438340 Eoin O'Neill changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/b347ab13a ||326fc571c6ff6e1f51f515c3e5d ||5a78 --- Comment #5 from Eoin O'Neill --- Git commit b347ab13a326fc571c6ff6e1f51f515c3e5d5a78 by Eoin O'Neill. Committed on 30/06/2021 at 02:47. Pushed by eoinoneill into branch 'master'. Prevent recalculate transform mask job from interrupting animation playback. M +3-1libs/image/kis_recalculate_transform_mask_job.cpp https://invent.kde.org/graphics/krita/commit/b347ab13a326fc571c6ff6e1f51f515c3e5d5a78 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439322] New: Krita is not using system color profile by default
https://bugs.kde.org/show_bug.cgi?id=439322 Bug ID: 439322 Summary: Krita is not using system color profile by default Product: krita Version: 4.4.5 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- Krita has an option to enable using system color profile: Configure Krita -> Color Management -> Display This checkbox is unchecked by default, making color managed display profiles useless. I think we should enable this option by default, because: 1) For those monitors that without a proper driver/profile, enabling this makes no difference. The default is always sRGB, so it will do no display color conversion. 2) For those monitors that have been calibrated and profiled, it provides a working-out-of-the-box color management experience. 3) Wide-gamut displays are widely used today. Working with those displays NEEDS to enable this option to get proper sRGB color. 4) This option is hidden quite deep, although at a logical place. New users might have difficulty finding it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438470] Color Palette Docker loads nothing by default on non-English locales
https://bugs.kde.org/show_bug.cgi?id=438470 --- Comment #18 from Tyson Tan --- Created attachment 139758 --> https://bugs.kde.org/attachment.cgi?id=139758=edit Krita Layers Docker root name not translated The "root"prefix of a merged layer is not translated. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438470] Color Palette Docker loads nothing by default on non-English locales
https://bugs.kde.org/show_bug.cgi?id=438470 --- Comment #17 from Tyson Tan --- Created attachment 139757 --> https://bugs.kde.org/attachment.cgi?id=139757=edit Krita Layers Docker default Background Layer name string has no translation -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438470] Color Palette Docker loads nothing by default on non-English locales
https://bugs.kde.org/show_bug.cgi?id=438470 --- Comment #16 from Tyson Tan --- Hi Tiar, I can confirm the default palette is now loading and the translated names of palettes and gradients are now showing in the tooltips. Thanks! For the untranslated things I noticed: Brushe presets has no translation, krita.pot don't have entries for them. I think it's very important to make them translatable. Are you still planning to have translation for them in the future? The "Background" name string for default Background layer in Layers docker does not show translation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430874] desktop cube background always black
https://bugs.kde.org/show_bug.cgi?id=430874 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424303] Export report as csv file gives a html file
https://bugs.kde.org/show_bug.cgi?id=424303 Dawid Wróbel changed: What|Removed |Added Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/kmymoney/commit/6ee4bb91 |ce/kmymoney/commit/23590f4d |21182d0e39065e3850348d1e2e7 |7f18f89e21549cbea42e977425b |66ed6 |19483 --- Comment #2 from Dawid Wróbel --- Git commit 23590f4d7f18f89e21549cbea42e977425b19483 by Dawid Wrobel, on behalf of Dawid Wróbel. Committed on 30/06/2021 at 01:24. Pushed by wrobelda into branch 'master'. Use mime types in Reports export dialog FIXED-IN: 5.1.3 (cherry picked from commit 6ee4bb9121182d0e39065e3850348d1e2e766ed6) M +14 -3kmymoney/plugins/views/reports/kreportsview.cpp M +3-3kmymoney/plugins/views/reports/kreportsview_p.h https://invent.kde.org/office/kmymoney/commit/23590f4d7f18f89e21549cbea42e977425b19483 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424303] Export report as csv file gives a html file
https://bugs.kde.org/show_bug.cgi?id=424303 Dawid Wróbel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/commit/6ee4bb91 ||21182d0e39065e3850348d1e2e7 ||66ed6 Version Fixed In||5.1.3 Status|REPORTED|RESOLVED --- Comment #1 from Dawid Wróbel --- Git commit 6ee4bb9121182d0e39065e3850348d1e2e766ed6 by Dawid Wróbel. Committed on 30/06/2021 at 01:22. Pushed by wrobelda into branch '5.1'. Use mime types in Reports export dialog FIXED-IN: 5.1.3 M +14 -3kmymoney/plugins/views/reports/kreportsview.cpp M +3-3kmymoney/plugins/views/reports/kreportsview_p.h https://invent.kde.org/office/kmymoney/commit/6ee4bb9121182d0e39065e3850348d1e2e766ed6 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438976] Clazy crashes when parsing Qt 6.1.0 with old-style-connect check enabled
https://bugs.kde.org/show_bug.cgi?id=438976 --- Comment #6 from ts826848+...@gmail.com --- Created attachment 139756 --> https://bugs.kde.org/attachment.cgi?id=139756=edit LLVM 12 test.cpp crash reproducer -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438976] Clazy crashes when parsing Qt 6.1.0 with old-style-connect check enabled
https://bugs.kde.org/show_bug.cgi?id=438976 --- Comment #5 from ts826848+...@gmail.com --- Created attachment 139755 --> https://bugs.kde.org/attachment.cgi?id=139755=edit Preprocessed LLVM 12 test.cpp -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438976] Clazy crashes when parsing Qt 6.1.0 with old-style-connect check enabled
https://bugs.kde.org/show_bug.cgi?id=438976 --- Comment #4 from ts826848+...@gmail.com --- I appear to get the same crash with LLVM 12.0.0 from Homebrew if I build either tag v1.9 + a29528ec87474a28258e34e7556fb38c5ba34a96 (Fix build with Clang 12) cherry-picked on top or the tip of the 1.9 branch. I've attached preprocessed .cpp and .sh files from both LLVM 11 and 12. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439321] New: plasmashell crash when dragging panel
https://bugs.kde.org/show_bug.cgi?id=439321 Bug ID: 439321 Summary: plasmashell crash when dragging panel Product: plasmashell Version: 5.22.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: alexey@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.1) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.13-gentoo x86_64 Windowing System: Wayland Drkonqi Version: 5.22.1 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: In desktop edit mode tried to drag the panel from one screen to another. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (LWP 915)] [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #7 0x7ffa2f15e536 in __GI_abort () at abort.c:79 #8 0x7ffa2f584181 in qt_message_fatal(QtMsgType, QMessageLogContext const&, QString const&) (context=..., message=...) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/global/qlogging.cpp:1914 #9 0x7ffa2f5805da in QMessageLogger::fatal(char const*, ...) const (this=0x7ffe912aaa00, msg=0x7ffa2d42e798 "The Wayland connection experienced a fatal error: %s") at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/global/qlogging.cpp:893 #10 0x7ffa2d380fe9 in QtWaylandClient::QWaylandDisplay::checkError() const (this=0x564e7a6cc130) at /usr/src/debug/dev-qt/qtwayland-5.15.2-r1/qtwayland-everywhere-src-5.15.2/src/client/qwaylanddisplay.cpp:211 #11 0x7ffa2d381051 in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x564e7a6cc130) at /usr/src/debug/dev-qt/qtwayland-5.15.2-r1/qtwayland-everywhere-src-5.15.2/src/client/qwaylanddisplay.cpp:222 #12 0x7ffa2d3bba2a in QtWaylandClient::QWaylandDisplay::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x564e7a6cc130, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffe912aaba0) at .moc/moc_qwaylanddisplay_p.cpp:77 #13 0x7ffa2f845d5b in doActivate(QObject*, int, void**) (sender=0x564e7a72f980, signal_index=4, argv=0x7ffe912aaba0) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:3898 #14 0x7ffa2f83f691 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=0x564e7a72f980, m=0x7ffa2fbc5a00 , local_signal_index=1, argv=0x0) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:3946 #15 0x7ffa2f7edae3 in QAbstractEventDispatcher::awake() (this=0x564e7a72f980) at .moc/moc_qabstracteventdispatcher.cpp:149 #16 0x7ffa2f8871e1 in QEventDispatcherGlib::processEvents(QFlags) (this=0x564e7a72f980, flags=...) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:430 #17 0x7ffa2f7f0109 in QEventLoop::processEvents(QFlags) (this=0x7ffe912aad40, flags=...) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventloop.cpp:139 #18 0x7ffa2f7f042f in QEventLoop::exec(QFlags) (this=0x7ffe912aad40, flags=...) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventloop.cpp:232 #19 0x7ffa2f7f3dcc in QCoreApplication::exec() () at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1371 #20 0x7ffa2fcf865c in QGuiApplication::exec() () at /usr/src/debug/dev-qt/qtgui-5.15.2-r1/qtbase-everywhere-src-5.15.2/src/gui/kernel/qguiapplication.cpp:1867 #21 0x7ffa305c8cf5 in QApplication::exec() () at /usr/src/debug/dev-qt/qtwidgets-5.15.2/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:2824 #22 0x564e798677d4 in main(int, char**) (argc=, argv=0x7ffe912aaea0) at /usr/src/debug/kde-plasma/plasma-workspace-5.22.2/plasma-workspace-5.22.2/shell/main.cpp:254 [Inferior 1 (process 915) detached] Possible duplicates by query: bug 429344, bug 427384, bug 424911, bug 423222, bug 423132. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439320] New: systemsettings srashes when saving window management behavior
https://bugs.kde.org/show_bug.cgi?id=439320 Bug ID: 439320 Summary: systemsettings srashes when saving window management behavior Product: systemsettings Version: 5.22.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexey@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.1) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.13-gentoo x86_64 Windowing System: Wayland Drkonqi Version: 5.22.1 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: In systemsettings navigate to Window management, Window behavior, Advanced tab. Change window placement from "Minimal overlapping" to "Centered", observe crash. Lauch again, navigate same way, change from "Centered" to "Minimal Overlapping" - crash again. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fc0a2cdb880 (LWP 1607))] [KCrash Handler] #6 0x7fc0a531da47 in QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x5602dae44db0, registry=0x5602d85267a0, id=53, interface=..., version=1) at /usr/src/debug/dev-qt/qtwayland-5.15.2-r1/qtwayland-everywhere-src-5.15.2/src/client/global/qwaylandclientextension.cpp:67 #7 0x7fc0a52f7781 in QtWaylandClient::QWaylandDisplay::registry_global (this=0x5602d8526110, id=53, interface=..., version=1) at /usr/src/debug/dev-qt/qtwayland-5.15.2-r1/qtwayland-everywhere-src-5.15.2/src/client/qwaylanddisplay.cpp:396 #8 0x7fc0a532c27c in QtWayland::wl_registry::handle_global (data=0x5602d8526120, object=0x5602d85267a0, name=53, interface=0x5602d972b450 "org_kde_kwin_blur_manager", version=1) at qwayland-wayland.cpp:94 #9 0x7fc0a2d6bbbd in ffi_call_unix64 () at /usr/src/debug/dev-libs/libffi-3.3-r2/libffi-3.3/src/x86/unix64.S:101 #10 0x7fc0a2d6b14a in ffi_call_int (cif=0x7fff8bc2bbf0, fn=0x7fc0a532c218 , rvalue=, avalue=, closure=) at /usr/src/debug/dev-libs/libffi-3.3-r2/libffi-3.3/src/x86/ffi64.c:669 #11 0x7fc0a526d59b in wl_closure_invoke (closure=0x5602d972b370, flags=1, target=0x5602d85267a0, opcode=0, data=0x5602d8526120) at ../wayland-1.19.0/src/connection.c:1018 #12 0x7fc0a526a5d8 in dispatch_event (display=0x5602d8526650, queue=0x5602d8526720) at ../wayland-1.19.0/src/wayland-client.c:1452 #13 0x7fc0a526a8be in dispatch_queue (display=0x5602d8526650, queue=0x5602d8526720) at ../wayland-1.19.0/src/wayland-client.c:1598 #14 0x7fc0a526ab91 in wl_display_dispatch_queue_pending (display=0x5602d8526650, queue=0x5602d8526720) at ../wayland-1.19.0/src/wayland-client.c:1840 #15 0x7fc0a526abf9 in wl_display_dispatch_pending (display=0x5602d8526650) at ../wayland-1.19.0/src/wayland-client.c:1903 #16 0x7fc0a52f603e in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x5602d8526110) at /usr/src/debug/dev-qt/qtwayland-5.15.2-r1/qtwayland-everywhere-src-5.15.2/src/client/qwaylanddisplay.cpp:221 #17 0x7fc0a5330a2a in QtWaylandClient::QWaylandDisplay::qt_static_metacall (_o=0x5602d8526110, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff8bc2c040) at .moc/moc_qwaylanddisplay_p.cpp:77 #18 0x7fc0a7a0ad5b in doActivate (sender=0x5602d85960e0, signal_index=3, argv=0x7fff8bc2c040) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:3898 #19 0x7fc0a7a04691 in QMetaObject::activate (sender=0x5602d85960e0, m=0x7fc0a7d8b3e0 , local_signal_index=0, argv=0x7fff8bc2c040) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:3946 #20 0x7fc0a7a13f8e in QSocketNotifier::activated (this=0x5602d85960e0, _t1=..., _t2=QSocketNotifier::Read, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #21 0x7fc0a7a13ad5 in QSocketNotifier::event (this=0x5602d85960e0, e=0x7fff8bc2c430) at /usr/src/debug/dev-qt/qtcore-5.15.2-r2/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qsocketnotifier.cpp:302 #22 0x7fc0a87bed7f in QApplicationPrivate::notify_helper (this=this@entry=0x5602d8520560, receiver=receiver@entry=0x5602d85960e0, e=e@entry=0x7fff8bc2c430) at /usr/src/debug/dev-qt/qtwidgets-5.15.2/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3632 #23 0x7fc0a87c7a30 in QApplication::notify (this=0x7fff8bc2c7c0, receiver=0x5602d85960e0, e=0x7fff8bc2c430) at /usr/src/debug/dev-qt/qtwidgets-5.15.2/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3156 #24 0x7fc0a79b859b in QCoreApplication::notifyInternal2 (receiver=0x5602d85960e0, event=0x7fff8bc2c430) at
[valgrind] [Bug 439090] unhandled amd64-linux syscall: 436 (close_range)
https://bugs.kde.org/show_bug.cgi?id=439090 Paul Wise changed: What|Removed |Added CC||pa...@bonedaddy.net -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 432734] Linux Report CSS has wrong fonts and doesn't make totals bold
https://bugs.kde.org/show_bug.cgi?id=432734
Dawid Wróbel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED|NEEDSINFO
CC||m...@dawidwrobel.com
--- Comment #1 from Dawid Wróbel ---
Mark,
> The CSS supplied with Linux distros references Windows fonts
> Linux fonts should be specified for Linux versions of the program
That's not how our CSS file works and how any CSS should work. The fonts
referenced are part of "font-family" property, as opposed to "font", which
means they are a *hint* for which font should be chosen ("A prioritized list of
font family names and/or generic family names"). While you see references to
Verdana and Arial and Helvetica, the "sans-serif" is a generic name for a font
family that the operating system/browser should choose to substitute them,
should those exact fonts not be available.
See here: https://www.w3schools.com/CSSref/pr_font_font-family.asp and also
here https://www.w3schools.com/cssref/css_websafe_fonts.asp
In other words, none of those Windows fonts are causing the issues you're
seeing. The problem is likely a matter of the font you have configured in your
system as a default provider for "sans-serif".
In any case, please attach a screenshot of what seems to be the problem.
--
You are receiving this mail because:
You are watching all bug changes.
[clazy] [Bug 438976] Clazy crashes when parsing Qt 6.1.0 with old-style-connect check enabled
https://bugs.kde.org/show_bug.cgi?id=438976 ts826848+...@gmail.com changed: What|Removed |Added Attachment #139754|test.sh crash reproducer|LLVM 11 test.sh crash description||reproducer -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438976] Clazy crashes when parsing Qt 6.1.0 with old-style-connect check enabled
https://bugs.kde.org/show_bug.cgi?id=438976 ts826848+...@gmail.com changed: What|Removed |Added Attachment #139753|Preprocessed test.cpp |Preprocessed LLVM 11 description||test.cpp -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390810] Icons do not appear on home page for payments
https://bugs.kde.org/show_bug.cgi?id=390810 Dawid Wróbel changed: What|Removed |Added CC||m...@dawidwrobel.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Dawid Wróbel --- Calvin, Is this still an issue? If so, can you please attach a screenshot, as suggested? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397226] Action icons are missing
https://bugs.kde.org/show_bug.cgi?id=397226 Dawid Wróbel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||m...@dawidwrobel.com --- Comment #1 from Dawid Wróbel --- Arnaud, Is this still a problem? We fixed a lot of icon-related issues since 5.0. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438976] Clazy crashes when parsing Qt 6.1.0 with old-style-connect check enabled
https://bugs.kde.org/show_bug.cgi?id=438976 ts826848+...@gmail.com changed: What|Removed |Added Attachment #139753|text/plain |application/octet-stream mime type|| -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438976] Clazy crashes when parsing Qt 6.1.0 with old-style-connect check enabled
https://bugs.kde.org/show_bug.cgi?id=438976 --- Comment #3 from ts826848+...@gmail.com --- Created attachment 139754 --> https://bugs.kde.org/attachment.cgi?id=139754=edit test.sh crash reproducer -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438976] Clazy crashes when parsing Qt 6.1.0 with old-style-connect check enabled
https://bugs.kde.org/show_bug.cgi?id=438976 --- Comment #2 from ts826848+...@gmail.com --- Created attachment 139753 --> https://bugs.kde.org/attachment.cgi?id=139753=edit Preprocessed test.cpp -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439319] New: Can't login to X11 session
https://bugs.kde.org/show_bug.cgi?id=439319 Bug ID: 439319 Summary: Can't login to X11 session Product: kwin Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: benaventeadr...@gmail.com Target Milestone: --- Created attachment 139752 --> https://bugs.kde.org/attachment.cgi?id=139752=edit The .xsession-errors file SUMMARY After updating to Plasma 5.22.1 to 5.22.2, I can't login to the X11 session, only Wayland works. When I try to login on a X11 session, after a few seconds I automatically go back to SDDM. The tail of the .xsession-errors is: XIO: fatal IO error 0 (Conseguido) on X server ":0" after 208 requests (6 known processed) with 0 events remaining. Application::crashHandler() called with signal 11; recent crashes: 1 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kwin_x11 path = /usr/bin pid = 1831 KCrash: Arguments: /usr/bin/kwin_x11 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key/usr/bin/kwin_x11: FATAL ERROR while trying to open display :0 Unable to start Dr. Konqi Re-raising signal for core dump handling. I attach the full .xsession-errors file that I hope might be of some help SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.22 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439318] Automatically discovered, but removed printers reappear instantly again
https://bugs.kde.org/show_bug.cgi?id=439318 Tobias G. changed: What|Removed |Added Summary|Automatically, but removed |Automatically discovered, |discovered printers |but removed printers |reappear instantly again|reappear instantly again -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439318] New: Automatically, but removed discovered printers reappear instantly again
https://bugs.kde.org/show_bug.cgi?id=439318 Bug ID: 439318 Summary: Automatically, but removed discovered printers reappear instantly again Product: systemsettings Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: tobi.goerg...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Hey guys, the printer manager automatically discovered printers in my network (which is great), but doesn't use the correct driver by default (which is not so great), but the worst thing is that every time I remove the printer (by pressing on "remove printer"), the printer just reappears again, bloating my printer menu with printers I can't use, since they don't work correctly / of printers I don't use. Even automatically recognized printers should stay removed, as they could easily be re-added when needed and it's just confusing that they reappear and might lead to confusion on what printer to use for an inexperienced user (the badly configured driver is a different story here) STEPS TO REPRODUCE 1. have a printer in the network that can be discovered 2. remove it from the printer list 3. wait for half a second OBSERVED RESULT the removed printer reappears EXPECTED RESULT the removed printer stays removed Operating System: Kubuntu 21.04 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-23-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439317] New: Add support for the DUR
https://bugs.kde.org/show_bug.cgi?id=439317 Bug ID: 439317 Summary: Add support for the DUR Product: Discover Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: tobi.goerg...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Hey there, the DUR (Debian User Repository) was announced a few days ago as Debian's alternative to the AUR. It would be really cool, if Discover added support for installing packages using the DUR in the future on Debian based systems. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439316] New: Desktop settings window weird launch
https://bugs.kde.org/show_bug.cgi?id=439316 Bug ID: 439316 Summary: Desktop settings window weird launch Product: plasmashell Version: 5.21.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: med.medin.2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139751 --> https://bugs.kde.org/attachment.cgi?id=139751=edit Desktop settings window weird launch If you maximize Desktop settings window then close it, then you open it again you will see that the window starts maximized then get smaller then gets maximized. See attached video for more info. Operating System: Manjaro Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.4.124-1-MANJARO OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438889] Can't cancel flood fill tool
https://bugs.kde.org/show_bug.cgi?id=438889 alphalimata...@runbox.com changed: What|Removed |Added CC||alphalimata...@runbox.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438977] AppImage doesn't start
https://bugs.kde.org/show_bug.cgi?id=438977 Dawid Wróbel changed: What|Removed |Added Version|5.1.1 |5.1.2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439299] Latte-dock height
https://bugs.kde.org/show_bug.cgi?id=439299 --- Comment #10 from Michail Vourlakos --- When the issue appears if you move your dock at the left edge and back to bottom, is it fixed? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 432372] FormLayout text gets elided too early when using a fractional font size
https://bugs.kde.org/show_bug.cgi?id=432372 Patrick Silva changed: What|Removed |Added CC||n_s_mend...@hotmail.com --- Comment #5 from Patrick Silva --- *** Bug 439271 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439271] Input Devices Settings: labels cropped in irrelevant situation
https://bugs.kde.org/show_bug.cgi?id=439271 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 432372 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 439315] Power management inhibition cannot be disabled
https://bugs.kde.org/show_bug.cgi?id=439315 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 439315] New: Power management inhibition cannot be disabled
https://bugs.kde.org/show_bug.cgi?id=439315 Bug ID: 439315 Summary: Power management inhibition cannot be disabled Product: Powerdevil Version: 5.22.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: popov...@ukr.net Target Milestone: --- SUMMARY In the "Battery and Brightness" applet, after unchecking the "Inhibit automatic sleep and screen locking" checkbox, the power management inhibition remains active. Only restarting plasmashell resets all inhibitions. I found, that after unchecking the above checkbox, PlasmaCore.DataSource for the "powermanagement" engine still contains the "plasmashell" inhibition (https://invent.kde.org/plasma/plasma-workspace/-/blob/master/applets/batterymonitor/package/contents/ui/logic.js#L77). STEPS TO REPRODUCE 1. Open "System Settings" 2. Go to "Power Management" > "Energy Saving" 3. Check "Dim screen" checkbox and set delay to 1 minute 4. Open "Battery and Brightness" applet 5. Check the "Inhibit automatic sleep and screen locking" checkbox to enable power management inhibition and wait a few seconds (it takes a few seconds to turn it on) 6. Uncheck the above checkbox to disable power management inhibition 7. Wait 1 minute until the screen goes dim OBSERVED RESULT The screen doesn't dim. EXPECTED RESULT The screen dims. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210626 KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439272] Kwin-Script: Better Quick Tiles - Windows moving without using shortcut
https://bugs.kde.org/show_bug.cgi?id=439272 --- Comment #9 from cysli...@posteo.de --- Can you please test if you also get this behavior when you disable "Better quick tiles" but use the normal 2x2, built in, quick tile shortcuts? I still bet this is due to the position not being saved and something triggering a "restore last position" that will then not restore the last quick position but instead the last user manipulated position. Also, quite conveniently, KDE Settings now can show you all settings you changed from default (Highlight Changed Settings in the lower left). Make sure you checked this out to not miss some setting you might have forgotten about. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439281] Folder View widget context menu opens in wrong location on multi screen setups.
https://bugs.kde.org/show_bug.cgi?id=439281 networkException changed: What|Removed |Added CC||k...@nwex.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439314] New: System Monitor crashed after changing display style
https://bugs.kde.org/show_bug.cgi?id=439314 Bug ID: 439314 Summary: System Monitor crashed after changing display style Product: plasma-systemmonitor Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: kdebugs@maciej.website CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.21.4) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-22-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: 1) Create new page 2) Add "Individual Core Usage" to it 3) Change "Display Style" to "Process table" 4) Change "Display Style" to "Application table" 5) Crash :( - It also works the other way around: 1) Create new page 2) Add "Individual Core Usage" to it 3) Change "Display Style" to "Application table" 4) Change "Display Style" to "Process table" 5) Crash :( And probably with other widgets etc. The crash can be reproduced every time. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x7f07cd0b7861 in ?? () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #5 0x7f07cd0acd17 in QQuickControlPrivate::updateImplicitContentWidth() () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #6 0x7f07cd0b79f5 in ?? () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #7 0x7f07cd3e71cd in QQuickItemPrivate::implicitWidthChanged() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f07cd3eb0fb in QQuickItem::setImplicitSize(double, double) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f07cc031802 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #10 0x7f07cc033e7e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #11 0x7f07cc030978 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #12 0x7f07cc033e42 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #13 0x7f07cc03b565 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #14 0x7f07d2c67e1e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f07d2c72cc4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f07c59692a9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #17 0x7f07d2c67e1e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f07d2c72cc4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f07c596ae42 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #20 0x7f07d2c67e1e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f07d2c72cc4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f07c4073c69 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/ksysguard/faces/libFacesPlugin.so #23 0x7f07d2c6a063 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f07d37a6173 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f07d2c3d22a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f07d2c3fd01 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f07d2c96f37 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f07d16de84b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f07d1731c68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f07d16dbf83 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f07d2c96594 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f07d2c3bb8b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f07d2c44024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x564c5ea4e9d1 in ?? () #35 0x7f07d25a9565 in __libc_start_main (main=0x564c5ea4d530, argc=1, argv=0x7ffc02bf4ee8, init=, fini=, rtld_fini=, stack_end=0x7ffc02bf4ed8) at ../csu/libc-start.c:332 #36 0x564c5ea4ea9e in ?? () [Inferior 1 (process 48105) detached] Possible duplicates by query: bug 436010, bug 435813, bug 435304, bug 435053. Reported using
[kscreenlocker] [Bug 439312] SimulateUserActivity doesn't unlock the screen, even when unlocking without password is enabled
https://bugs.kde.org/show_bug.cgi?id=439312 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439313] Discover Update Notification persistent because of Libc++1 Update that cannot be installed
https://bugs.kde.org/show_bug.cgi?id=439313 --- Comment #1 from diceLibrarian --- Meant to write "most recent version available." forgot to add Available to the first paragraph -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438727] Shortcuts for opening the activity selector don't work
https://bugs.kde.org/show_bug.cgi?id=438727 t...@tutanota.com changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439313] New: Discover Update Notification persistent because of Libc++1 Update that cannot be installed
https://bugs.kde.org/show_bug.cgi?id=439313 Bug ID: 439313 Summary: Discover Update Notification persistent because of Libc++1 Update that cannot be installed Product: Discover Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: aleix...@kde.org Reporter: solon.sandi...@gmail.com Target Milestone: --- SUMMARY Started about two weeks ago. It's happening because libc++1 depends on libc++1-11-dev which itself depends on libc++1-11 which is at the most recent version. However, libc++1-11-dev is a version past that, which affects libc++1. This isn't the best spot to report the dependency conflict, but this dependency conflict is causing Discover to erroneously report an update. Only figured this one out by manually updating in a command line. Removing the notification asks me to exit "discover-notifier". STEPS TO REPRODUCE 1. I have absolutely no idea, but it happens every time I start my PC OBSERVED RESULT Notification on the panel that there are updates available every time I restart my computer. EXPECTED RESULT Lack of a Notification on the panel every time. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This is my first Ticket, I'm not sure if this is how it's supposed to be laid out. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 429344] All Mail Accounts (on KMail) crashed after latest updates
https://bugs.kde.org/show_bug.cgi?id=429344 Peter Huyoff changed: What|Removed |Added CC||peter.huy...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439310] Unable to set shortcuts in Okular
https://bugs.kde.org/show_bug.cgi?id=439310 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Works fine for me. -- You are receiving this mail because: You are watching all bug changes.
[SeExpr] [Bug 431436] 4.0.1.0 fails to build on 32bit openSUSE
https://bugs.kde.org/show_bug.cgi?id=431436 --- Comment #5 from Wolfgang Bauer --- I also noticed a discrepancy for the double variant between KSeExprUI/Utils.cpp and KSeExprUI/Utils.h, btw. You changed it to bool KSeExpr::Utils::parseRangeComment(const std::string , double , double ) in Utils.cpp, and in Utils.h it is bool parseRangeComment(const std::string , double , double_t );. I.e. you changed it to "double " in Utils.cpp, but not in Utils.h where it's still "double_t ". -- You are receiving this mail because: You are watching all bug changes.
[SeExpr] [Bug 431436] 4.0.1.0 fails to build on 32bit openSUSE
https://bugs.kde.org/show_bug.cgi?id=431436
Wolfgang Bauer changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED|REOPENED
--- Comment #4 from Wolfgang Bauer ---
Sorry, but it still fails:
[ 140s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/ControlSpec.cpp: In
constructor 'KSeExpr::ExprScalarAssignSpec::ExprScalarAssignSpec(const
KSeExpr::ExprAssignNode&)':
[ 140s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/ControlSpec.cpp:89:62:
error: cannot bind non-const lvalue reference of type 'float_t&' {aka 'long
double&'} to a value of type 'float'
[ 140s]89 | if (KSeExpr::Utils::parseRangeComment(comment, fmin,
fmax)) {
[ 140s] |
^~~~
[ 140s] In file included from
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/ControlSpec.cpp:11:
[ 140s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Utils.h:14:82: note:
initializing argument 3 of 'bool KSeExpr::Utils::parseRangeComment(const
string&, float&, float_t&)'
[ 140s]14 | bool parseRangeComment(const std::string ,
float , float_t );
[ 140s] |
~^~
[ 140s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/ControlSpec.cpp: In
constructor 'KSeExpr::ExprVectorAssignSpec::ExprVectorAssignSpec(const
KSeExpr::ExprAssignNode&)':
[ 140s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/ControlSpec.cpp:135:62:
error: cannot bind non-const lvalue reference of type 'float_t&' {aka 'long
double&'} to a value of type 'float'
[ 140s] 135 | if (KSeExpr::Utils::parseRangeComment(comment, fmin,
fmax)) {
[ 140s] |
^~~~
[ 140s] In file included from
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/ControlSpec.cpp:11:
[ 140s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Utils.h:14:82: note:
initializing argument 3 of 'bool KSeExpr::Utils::parseRangeComment(const
string&, float&, float_t&)'
[ 140s]14 | bool parseRangeComment(const std::string ,
float , float_t );
[ 140s] |
~^~
and:
[ 141s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Editable.cpp: In
member function 'virtual bool NumberEditable::parseComment(const string&)':
[ 141s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Editable.cpp:51:62:
error: cannot bind non-const lvalue reference of type 'float_t&' {aka 'long
double&'} to a value of type 'float'
[ 141s]51 | if (KSeExpr::Utils::parseRangeComment(comment, fmin,
fmax)) {
[ 141s] |
^~~~
[ 141s] In file included from
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Editable.cpp:17:
[ 141s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Utils.h:14:82: note:
initializing argument 3 of 'bool KSeExpr::Utils::parseRangeComment(const
string&, float&, float_t&)'
[ 141s]14 | bool parseRangeComment(const std::string ,
float , float_t );
[ 141s] |
~^~
[ 141s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Editable.cpp: In
member function 'virtual bool VectorEditable::parseComment(const string&)':
[ 141s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Editable.cpp:100:68:
error: cannot bind non-const lvalue reference of type 'float_t&' {aka 'long
double&'} to a value of type 'float'
[ 141s] 100 | bool parsed = KSeExpr::Utils::parseRangeComment(comment,
fmin, fmax);
[ 141s] |
^~~~
[ 141s] In file included from
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Editable.cpp:17:
[ 141s]
/home/abuild/rpmbuild/BUILD/kseexpr-4.0.2.0/src/KSeExprUI/Utils.h:14:82: note:
initializing argument 3 of 'bool KSeExpr::Utils::parseRangeComment(const
string&, float&, float_t&)'
[ 141s]14 | bool parseRangeComment(const std::string ,
float , float_t );
[ 141s] |
~^~
The "to" parameter of KSeExpr::Utils::parseRangeComment() is still float_t...
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 439312] SimulateUserActivity doesn't unlock the screen, even when unlocking without password is enabled
https://bugs.kde.org/show_bug.cgi?id=439312 Forest changed: What|Removed |Added Summary|SimulateUserActivity|SimulateUserActivity |doesn't unlock the screen, |doesn't unlock the screen, |even unlocking without |even when unlocking without |password is enabled |password is enabled -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439312] New: SimulateUserActivity doesn't unlock the screen, even unlocking without password is enabled
https://bugs.kde.org/show_bug.cgi?id=439312 Bug ID: 439312 Summary: SimulateUserActivity doesn't unlock the screen, even unlocking without password is enabled Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fores...@sonic.net CC: bhus...@gmail.com Target Milestone: --- SUMMARY The SimulateUserActivity doesn't actually simulate user activity. Once the lock screen appears, moving the mouse or pressing a key will wake the screen (so long as it's still within the "Allow unlocking without password" time). However, a call to SimulateUserActivity() at that time is ignored, leaving the screen locked. STEPS TO REPRODUCE 1. Workspace Behavior: Screen Locking: Lock screen automatically: After 1 minute 2. Workspace Behavior: Screen Locking: Allow unlocking without password for: 300 seconds 3. In a shell: sleep 70; qdbus org.freedesktop.ScreenSaver /ScreenSaver SimulateUserActivity 4. Idle for 60 seconds 5. Notice the screen locker activate 6. Continue idling for 10 more seconds 7. Notice that the screen does not wake when SimulateUserActivity is called 8. Generate actual user activity (move the mouse or press a key) and notice that the screen does wake OBSERVED RESULT Screen doesn't wake in response to SimulateUserActivity EXPECTED RESULT Screen should wake, just as it does with actual user activity SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Problem exists with Wayland and X11 sessions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439246] The "configure energy saving" button does nothing
https://bugs.kde.org/show_bug.cgi?id=439246 --- Comment #3 from ifs6n...@anonaddy.me --- The system settings wasn't opened. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439246] The "configure energy saving" button does nothing
https://bugs.kde.org/show_bug.cgi?id=439246 --- Comment #2 from ifs6n...@anonaddy.me --- Is working now that I switched to X. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439311] New: Merge the login screen and the lock screen
https://bugs.kde.org/show_bug.cgi?id=439311 Bug ID: 439311 Summary: Merge the login screen and the lock screen Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ifs6n...@anonaddy.me CC: plasma-b...@kde.org Target Milestone: 1.0 - Both login screen and lock screen shows the clock and the media controls. There is nothing that the lock screen shows that the login screen doesn't; - When locking the session, the lock screen quickly disappears when the screen turns off; - The lock screen quickly disappears when re-awakening the computer. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439290] No Reports available
https://bugs.kde.org/show_bug.cgi?id=439290 Thomas Baumgart changed: What|Removed |Added Version|5.1.2 |git (master) -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 439307] heaptrack launch script help text shows wrong option name for --output-file
https://bugs.kde.org/show_bug.cgi?id=439307 Milian Wolff changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||heaptrack/commit/7367ae25d7 ||23f1b88e32453ea4d15008f7276 ||fbb Status|REPORTED|RESOLVED --- Comment #1 from Milian Wolff --- Git commit 7367ae25d723f1b88e32453ea4d15008f7276fbb by Milian Wolff. Committed on 29/06/2021 at 18:55. Pushed by mwolff into branch 'master'. Also parse `--output` as alias according to help output for `-o` Keep the `--output-file` form for backwards compat. M +1-1src/track/heaptrack.sh.cmake https://invent.kde.org/sdk/heaptrack/commit/7367ae25d723f1b88e32453ea4d15008f7276fbb -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439310] New: Unable to set shortcuts in Okular
https://bugs.kde.org/show_bug.cgi?id=439310 Bug ID: 439310 Summary: Unable to set shortcuts in Okular Product: okular Version: 21.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: rafael.palma.l...@gmail.com Target Milestone: --- Created attachment 139749 --> https://bugs.kde.org/attachment.cgi?id=139749=edit Bug details (LibreOffice Draw format) SUMMARY In "Configure Keyboard Shortcuts" there's no way to set any custom shortcut. I type the shortcut and it gets shown in the custom shortcut control, but it doesn't get saved no matter what I do. STEPS TO REPRODUCE 1. Go to Settings > Configure keyboard shortcuts 2. Choose any option, f.i. Rotate left 3. Choose Custom and click the button where it's written "None" 4. Press the desired shortcut (in my case Ctrl + Shift + L) 5. The shortcut is identified by the control but it doesn't get shown where it's supposed to (see attached file); actually it keeps catching more shortcuts if I keep pressing keys 6. Click OK in the main dialog OBSERVED RESULT The shortcut is not saved. I tried it multiple times and all the times it gets caught duplicated. One weird thing: if I press Enter while it's catching the shortcut, then it gets saved, but it also saves Enter as the shortcut. However, the desired shortcut does not work. EXPECTED RESULT The shortcut should be saved and work. Operating System: Kubuntu 21.04 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-22-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: GeForce GTX 1660/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439272] Kwin-Script: Better Quick Tiles - Windows moving without using shortcut
https://bugs.kde.org/show_bug.cgi?id=439272 --- Comment #8 from schuhmann.sebast...@gmail.com --- OK sorry for the new reply again. It seems, that this unwanted behaviour is not solved by just deactivating "slide behind"-effect. I uploaded another screen-cast after i installed a screen key application to show you my strokes In the Screen capture of the bug for Notifications gif you see 1. super+3 --> Sets the window size to lower right 2. Vol+ --> My custom key vor "next song" media control --> This causes a popup to appear to show the next title 3. During the notification is shown i hit super+3 again --> Window size change during notification is still present 3. Wait for notification to disappear after timer --> Window size changes without any keystroke Here again you can see some connections to Window activities, causing window size and position changes for windows changed by "Better Quick Tiles" If i deactivate Better Quick Tiles --> No error present anymore I tried to see if the same error occurs if im doing the same thing but only using super+arrowRight --> This does NOT cause an error --> Only shifting windows with "Better Quick Tiles" shifts the window I also checked if the meta+num+1-9 shortcut is used by other functions --> I could not find these shortcuts to be used double --> And as you see in the gif --> The unintended Windows size/position-change is not related to any keystroke -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439272] Kwin-Script: Better Quick Tiles - Windows moving without using shortcut
https://bugs.kde.org/show_bug.cgi?id=439272 --- Comment #7 from schuhmann.sebast...@gmail.com --- Created attachment 139748 --> https://bugs.kde.org/attachment.cgi?id=139748=edit Screen capture of the bug for Notifications -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439309] New: the Media Player plasmoid doesn't clear the player list until all players are closed
https://bugs.kde.org/show_bug.cgi?id=439309 Bug ID: 439309 Summary: the Media Player plasmoid doesn't clear the player list until all players are closed Product: plasmashell Version: 5.22.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: k...@privat.broulik.de Reporter: this.is.r...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY the Media Player plasmoid doesn't clear the player list until all players are closed STEPS TO REPRODUCE 1. open 2 media player and make sure they both get added to the plasmoid 2. close one 3. check the plasmoid OBSERVED RESULT the closed player won't get removed from the list; closing all players will however properly clear the list EXPECTED RESULT players should get removed from the list as they're closed SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439308] New: Reproducible reset of multi-mon layout config w/Blockout II app in fullscreen ;-)
https://bugs.kde.org/show_bug.cgi?id=439308 Bug ID: 439308 Summary: Reproducible reset of multi-mon layout config w/Blockout II app in fullscreen ;-) Product: kwin Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: c...@encapsule.io Target Milestone: --- SUMMARY I have 3 x 4K monitors connected to a single graphics card that I have positioned normally for a large wrap-around desktop. If I install the old BlockOut II game (available in Software Center) and run that app in full-screen mode, it resets the screen layout so that all three desktops are on top of each other (i.e. if you go to System Settings | Hardware | Display and Monitors you'll see _one_ display monitor (w/the other two apparently missing). Dragging the one visible monitor reveals the 2nd, and so on... It would not seem that the app should be able to persistently alter these settings? STEPS TO REPRODUCE 1. Install Blockout II 2. Launch game in full-screen mode 3. Exit the game OBSERVED RESULT Multi-monitor screen layout data is reset persistently requiring that I go back into Display and Monitor and re-arrange the display monitors. What's not great about this is that it's not immediately obvious what happened or how to fix it. EXPECTED RESULT No persistent changes to multi-monitor screen layout settings (i.e. settings restored) on exit from app. 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.
[kwin] [Bug 438521] Move the icon and label from the center of the thumbnail
https://bugs.kde.org/show_bug.cgi?id=438521 --- Comment #7 from popov895 --- Any news? -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 439307] New: heaptrack launch script help text shows wrong option name for --output-file
https://bugs.kde.org/show_bug.cgi?id=439307 Bug ID: 439307 Summary: heaptrack launch script help text shows wrong option name for --output-file Product: Heaptrack Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: m...@milianw.de Reporter: k...@mattwhitlock.name Target Milestone: --- The output from "heaptrack --help" claims the existence of an option "-o, --output", but actually trying to specify an "--output" argument yields: Error: Debuggee "--output" was not found. Examining the script source reveals that the actual name of the long option is "--output-file". The usage help text should be corrected. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438640] vex x86->IR: unhandled instruction bytes: 0xF2 0xF 0x38 0xF1
https://bugs.kde.org/show_bug.cgi?id=438640 --- Comment #8 from Tom Hughes --- If somebody writes a patch to implement support for that instruction then sure. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438640] vex x86->IR: unhandled instruction bytes: 0xF2 0xF 0x38 0xF1
https://bugs.kde.org/show_bug.cgi?id=438640 --- Comment #7 from amita dwivedi --- Is it possible to fix in valgrind by applying some patch ? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439299] Latte-dock height
https://bugs.kde.org/show_bug.cgi?id=439299 --- Comment #9 from Vladimir Yerilov --- Created attachment 139747 --> https://bugs.kde.org/attachment.cgi?id=139747=edit debug window part 2 The second part. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439299] Latte-dock height
https://bugs.kde.org/show_bug.cgi?id=439299 --- Comment #8 from Vladimir Yerilov --- Created attachment 139746 --> https://bugs.kde.org/attachment.cgi?id=139746=edit debug window part 1 Here it is. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439272] Kwin-Script: Better Quick Tiles - Windows moving without using shortcut
https://bugs.kde.org/show_bug.cgi?id=439272 --- Comment #6 from schuhmann.sebast...@gmail.com --- Hello and thank you very much for your reply! To get a better idea where some connections could be (causing this error) i played a bit with my settings - This error ONLY occurs if Better Quick Tiles is active --> Has to do with this script - I erased all of my virtual desktops --> Error still present - BUT: I deactivated the "slide behind" effect in "Effects >> Activation >> Slide behind" and this seems to solve the problem Could it be, that there is some connection to the "Slide behind" effect when a new window appears? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439266] Menubar not visible after using global menu
https://bugs.kde.org/show_bug.cgi?id=439266 Paul Worrall changed: What|Removed |Added Version|21.04.1 |5.22.2 Target Milestone|--- |1.0 Component|application |Global Menu Assignee|kwrite-bugs-n...@kde.org|k...@privat.broulik.de CC||mvourla...@gmail.com, ||p.r.worr...@gmail.com, ||plasma-b...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Product|kate|plasmashell --- Comment #1 from Paul Worrall --- I can reproduce this on Kate, and some other applications (tried K3B and Ark), therefore changing product to plasmashell-Global Menu Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: Wayland Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: AMD CEDAR -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 439283] CMake libs fails to build under Apple Silicon
https://bugs.kde.org/show_bug.cgi?id=439283 Dawid Wróbel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pack ||aging/craft/commit/e958ee7c ||1ef24a3fe312b3c0ac1a3170377 ||0dcbb Status|ASSIGNED|RESOLVED --- Comment #2 from Dawid Wróbel --- Git commit e958ee7c1ef24a3fe312b3c0ac1a31703770dcbb by Dawid Wróbel. Committed on 29/06/2021 at 01:50. Pushed by wrobelda into branch 'master'. cmake: update to 3.19.2, fix Apple Silicon builds 3.19.2 is the first version that supports Apple Silicon M +8-4blueprints/dev-utils/cmake-base/cmake-base.py https://invent.kde.org/packaging/craft/commit/e958ee7c1ef24a3fe312b3c0ac1a31703770dcbb -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438630] Adding zero variants of arm64 v8.2 FCMEQ, FCMGE, FCMGT, FCMLE and FCMLT instructions
https://bugs.kde.org/show_bug.cgi?id=438630 ahashmi changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438630] Adding zero variants of arm64 v8.2 FCMEQ, FCMGE, FCMGT, FCMLE and FCMLT instructions
https://bugs.kde.org/show_bug.cgi?id=438630 ahashmi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from ahashmi --- Landed 393732dda164c1cc0fc511eadc0b8f06008ade4f -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438038] Addition of arm64 v8.2 FCCMP, FCCMPE, FCMEQ, FCMGE and FCMGT instructions
https://bugs.kde.org/show_bug.cgi?id=438038 ahashmi changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438038] Addition of arm64 v8.2 FCCMP, FCCMPE, FCMEQ, FCMGE and FCMGT instructions
https://bugs.kde.org/show_bug.cgi?id=438038 ahashmi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from ahashmi --- Landed c5331315d7a62ec1c117ff773fadfeb0bf433b02 -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439299] Latte-dock height
https://bugs.kde.org/show_bug.cgi?id=439299 Michail Vourlakos changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Michail Vourlakos --- hm, the thing is that I started your layout six times in my system and I can not reproduce. I dont think this is related to KWin. Try to start Latte from command line with: "latte-dock -d --with-window" when the problem appears take a screenshot of Debug Window, if it does not fit in screenshot please scroll it down and take a secondary screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439278] Freeze then crash on changing currently playing song
https://bugs.kde.org/show_bug.cgi?id=439278
--- Comment #5 from Wyatt Childers ---
Alright I got GDB attached, and hopefully I've got some useful information now
(backtrace of all threads has already been attached).
Beyond that plasmashell thread seems to be stuck in a loop here trying to
figure out where to allocate a page (though this may be unrelated/just
statistically significantly reentered hot logic):
jsruntime/qv4persistent.cpp
│ 196 Value *PersistentValueStorage::allocate()
│ 197 {
│ 198 Page *p = static_cast(firstPage);
│ 199 while (p) {
│ >200 if (p->header.freeList != -1)
│ 201 break;
│ 202 p = p->header.next;
│ 203 }
│ 204 if (!p)
│ 205 p = allocatePage(this);
│ 206
│ 207 Value *v = p->values + p->header.freeList;
│ 208 p->header.freeList = v->int_32();
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 439278] Freeze then crash on changing currently playing song
https://bugs.kde.org/show_bug.cgi?id=439278 --- Comment #4 from Wyatt Childers --- Created attachment 139745 --> https://bugs.kde.org/attachment.cgi?id=139745=edit Log of thread backtraces -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439306] New: More gmail kmail failings
https://bugs.kde.org/show_bug.cgi?id=439306 Bug ID: 439306 Summary: More gmail kmail failings Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: dav1dblunk...@hotmail.com Target Milestone: --- v 5.13.3 So today kmail borked with gmail in a horribly familiar way, it just hung trying to sync the inbox only this time with a message in the status bar "trying to update an item" or similar. So begins the many rounds of restarting akonadi - no effect, restarting kmail - no effect, rebooting the computer - no effect. Provoking kmail to reauthenticate with gmail - back to the familiar problems, kmail is not a trusted browser so can't get in. So I resort to the "authenticate as plain" solution to this and modify my account but this does not fix the problem. Back to the next solution: add a parallel gmail account and this is where the new bug comes in: I need to add a gmail account and I need this to be "plain", I can bodge the wizard to make this happen and I can create the account and the account works BUT I cannot dismiss the wizard. I either have back or forward buttons but the finish button is never ungreyed. The cancel button works but this deletes my nice new working account. Not matter what I try I can only get to the point where I have a working account and an open wizard, any attempt to get rid of the wizard removes the account. The fix (if you can call it that) is to go through the process and then "kill -9 xxx" kmail and restart it. This gains the working account without the unwanted wizard. So... gmail authentication should work (but doesn't), plain authentication should be easy to set up (but isn't because kmail insists you want gmail authentication) and it should be able to add a non-functional account (which can be fixed later) but you can't because the only exit from the account set up is "cancel" (which removes things). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices after connecting the device for 2nd time
https://bugs.kde.org/show_bug.cgi?id=438874 nucleo changed: What|Removed |Added CC||nuc...@fedoraproject.org --- Comment #10 from nucleo --- The same bug on Fedora 34. Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #75 from PGillespie --- (In reply to Jeffrey Bouter from comment #74) > Sadly, this didn't work for me either :-( I followed these steps first: https://userbase.kde.org/Plasma/Tips#Windows.2FMeta_Key Though that still may not help you? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439299] Latte-dock height
https://bugs.kde.org/show_bug.cgi?id=439299 --- Comment #6 from Vladimir Yerilov --- Created attachment 139744 --> https://bugs.kde.org/attachment.cgi?id=139744=edit My latte layout I think this has something to do with Kwin effects, because the first instance of Latte started during Plasma start-up has no blur effect applied to it (despite explicitly set to have blur in settings), and auto-opened apps from restored session use wrong minimize effect for the first time they are being minimized. Looks to be better with OpenGL 2.0 set as rendering backend in Compositor settings: now all the above happens only from time to time. Here's a layout exported as a template. Interesting idea btw, Weather widget could be the culprit. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #74 from Jeffrey Bouter --- (In reply to PGillespie from comment #73) > (In reply to Jeffrey Bouter from comment #72) > > I think I'm being affected by this bug as well. It started occuring when I > > changed the meta key to launch the menu on latte dock, and then after > > reverted back to using the default plasma panel. > > > > Confusingly, the global shortcut configuration "Activate Application > > Launcher Widget" in the plasma category, shows up three times. > > The same thing happened to me when I reassigned META to the latte dock—an I > also don't see the point to the three instances in global settings(?). > Resetting META through global shortcuts accomplished nothing. Right clicking > on the app/widget in the panel allowed me to successfully reset the META key > and also fixed the problem with my inability to invoke the Applications > Launcher via the touchscreen. > > https://bugs.kde.org/show_bug.cgi?id=438612 Sadly, this didn't work for me either :-( -- You are receiving this mail because: You are watching all bug changes.
