[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 436518] New: Skrooge titlebar and Task Manager entry has generic icon in Wayland
https://bugs.kde.org/show_bug.cgi?id=436518 Bug ID: 436518 Summary: Skrooge titlebar and Task Manager entry has generic icon in Wayland Product: skrooge Version: Trunk from git Platform: Flatpak OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: skierp...@gmail.com CC: steph...@mankowski.fr Target Milestone: --- SUMMARY Skrooge has a generic (W) icon in its titlebar and in the KDE Task Manager when running in kwin_wayland. STEPS TO REPRODUCE 1. Run skrooge package or `flatpak run org.kde.skrooge` 2. Confirm Help > About Skrooge > Libraries displays "The wayland windowing system" 3. Look at its titlebar and Task Manager entry. OBSERVED RESULT Both Fedora 34's Skrooge 2.23.0 and the kdeapps flatpak show a generic white 'W' on orange icon. EXPECTED RESULT Skrooge's icon. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: ?? KDE Frameworks Version: 5.81.0 Qt Version: Qt 5.15.3 (built against 5.15.3) The wayland windowing system ADDITIONAL INFORMATION Many other KDE applications have this issue, e.g. bug 417449, bug 424823, etc. For comparison, SpeedCrunch flatpak app has the generic titlebar icon but its own icon in the Task Manager. https://community.kde.org/Guidelines_and_HOWTOs/Wayland_Porting_Notes#Application_Icon says "setWindowIcon() no longer works", and skrooge/main.cpp#89 calls this. Some of my skrooge.desktop files have Icon=skrooge (/usr/share/applications/org.kde.skrooge.desktop) and others have Icon=org.kde.skrooge (/var/lib/flatpak/exports/share/applications/org.kde.skrooge.desktop and /var/lib/flatpak/app/org.kde.skrooge/x86_64/master/blahblah/files/share/applications/org.kde.skrooge.desktop), I don't know if this is relevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436517] New: Implement a search icon in searchboxes
https://bugs.kde.org/show_bug.cgi?id=436517 Bug ID: 436517 Summary: Implement a search icon in searchboxes Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: lv215...@anonaddy.me CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 138107 --> https://bugs.kde.org/attachment.cgi?id=138107=edit searchboxes with a search icon vs searchboxes without the icon SUMMARY In KDE apps, none of the searchboxes have a search icon. STEPS TO REPRODUCE OBSERVED RESULT EXPECTED RESULT If all searchboxes had search icons, this would help the user to quickly find them, cause, well, that's what iconography does. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-16-generic ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436515] Enhancement: standardize app top panels
https://bugs.kde.org/show_bug.cgi?id=436515 Ninguém changed: What|Removed |Added Summary|Standardize app top panels |Enhancement: standardize ||app top panels --- Comment #2 from Ninguém --- Note: when I said class, I was actually referring to CSS, where a class can give the same style for multiple elements. I have no idea if this concept exists in KDE apps. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 --- Comment #1 from Mathias Homann --- Created attachment 138106 --> https://bugs.kde.org/attachment.cgi?id=138106=edit New crash information added by DrKonqi kopete (1.13.0) using Qt 5.15.2 - What I was doing when the application crashed: again, crash on exit. there is no additional iformation to be added. -- Backtrace (Reduced): #4 KHTMLPart::begin(QUrl const&, int, int) (this=this@entry=0x557e2be9af40, url=..., xOffset=xOffset@entry=0, yOffset=yOffset@entry=0) at /usr/src/debug/khtml-5.81.0-lp152.218.1.x86_64/src/khtml_part.cpp:2074 #5 0x7f47aee2b037 in ChatMessagePart::writeTemplate() (this=this@entry=0x557e2be9af40) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/chatwindow/chatmessagepart.cpp:1291 #6 0x7f47aee328ad in ChatMessagePart::changeStyle() (this=0x557e2be9af40) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/chatwindow/chatmessagepart.cpp:1269 #7 0x7f47aee27185 in ChatMessagePart::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/build/kopete/chatwindow/kopetechatwindow_shared_autogen/EWIEGA46WW/moc_chatmessagepart.cpp:238 #8 0x7f47ddbaf63b in QObject::event(QEvent*) (this=0x557e2be9af40, e=0x557e2c152500) at kernel/qobject.cpp:1314 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436515] Standardize app top panels
https://bugs.kde.org/show_bug.cgi?id=436515 --- Comment #1 from Ninguém --- Note: when I said class, I was actually referring to CSS, where a class can give the same style for multiple elements. I have no idea if this concept exists in KDE apps. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436516] New: Kopete does nto start as "online" even when configured to do so
https://bugs.kde.org/show_bug.cgi?id=436516 Bug ID: 436516 Summary: Kopete does nto start as "online" even when configured to do so Product: kopete Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Kopete does nto start as "online" even when configured to do so STEPS TO REPRODUCE 1. start kopete 2. configure the startup statzs to be "online" 3. restart kopete OBSERVED RESULT kopete does not log in to your messenger accounts even when the "startup state" setting does indeed say "online" EXPECTED RESULT I would expect this to work. 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.
[kdenlive] [Bug 357153] Increasing "Video quality" number in render panel actually reduces quality + increases compression
https://bugs.kde.org/show_bug.cgi?id=357153 Alex changed: What|Removed |Added CC||alex...@protonmail.com --- Comment #9 from Alex --- As of 21.04.0, this is still a little confusing, but at least the basic view (with "More options" unchecked") is pretty intuitive, because the Quality slider is just "higher slider = higher quality". And this slider persists in the advanced view. I agree with the above comments though, "smaller file" on one end of the slider, and "better quality" on the other end is easier to understand. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436515] New: Standardize app top panels
https://bugs.kde.org/show_bug.cgi?id=436515 Bug ID: 436515 Summary: Standardize app top panels Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: lv215...@anonaddy.me CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 138105 --> https://bugs.kde.org/attachment.cgi?id=138105=edit app titles and toolbars SUMMARY Some apps have inconsistent spacement in the titles and other elements such as search bars. STEPS TO REPRODUCE 1. Go to System Settings > Colors and go to KDE Connect > Pair. OBSERVED RESULT In KDE Connect, the "pair" title has more spacement than "Colors". This doesn't happens only in these apps, I attached a screenshot showing a bit more, like Dolphin settings. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-16-generic ADDITIONAL INFORMATION Maybe a solution would be creating a class that would provide fixed padding and margins to these sections. This wouldn't required to set specific margins to all KDE apps. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436514] New: kopete does not change UI settings on exit
https://bugs.kde.org/show_bug.cgi?id=436514 Bug ID: 436514 Summary: kopete does not change UI settings on exit Product: kopete Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Kopete 1.13 does not save changed UI settings STEPS TO REPRODUCE 1. start kopete 2. change some UI settings, i.e. hide the menu, change the toolbar layout, etc 3. quit kopete 4. start kopete OBSERVED RESULT the changes are gone EXPECTED RESULT i would expect such changes to be saved in the settings file. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.72-preempt OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] New: kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 Bug ID: 436513 Summary: kopete crashed on exit Product: kopete Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kopete (1.13.0) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.3.18-lp152.72-preempt x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: kopete crashed on exit. on stdout i had literally hundreds of lines like this: QFSFileEngine::open: No file name specified The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #4 KHTMLPart::begin(QUrl const&, int, int) (this=this@entry=0x5577f82a9320, url=..., xOffset=xOffset@entry=0, yOffset=yOffset@entry=0) at /usr/src/debug/khtml-5.81.0-lp152.218.1.x86_64/src/khtml_part.cpp:2074 #5 0x7fe44789f037 in ChatMessagePart::writeTemplate() (this=this@entry=0x5577f82a9320) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/chatwindow/chatmessagepart.cpp:1291 #6 0x7fe4478a68ad in ChatMessagePart::changeStyle() (this=0x5577f82a9320) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/chatwindow/chatmessagepart.cpp:1269 #7 0x7fe44789b185 in ChatMessagePart::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/build/kopete/chatwindow/kopetechatwindow_shared_autogen/EWIEGA46WW/moc_chatmessagepart.cpp:238 #8 0x7fe47676f63b in QObject::event(QEvent*) (this=0x5577f82a9320, e=0x5577f825c990) at kernel/qobject.cpp:1314 #9 0x7fe4776e037c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x5577f6344be0, receiver=receiver@entry=0x5577f82a9320, e=e@entry=0x5577f825c990) at kernel/qapplication.cpp:3632 #10 0x7fe4776e7170 in QApplication::notify(QObject*, QEvent*) (this=0x7fff3c103f20, receiver=0x5577f82a9320, e=0x5577f825c990) at kernel/qapplication.cpp:3156 #11 0x7fe47673b443 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5577f82a9320, event=0x5577f825c990) at kernel/qcoreapplication.cpp:1063 #12 0x7fe47673b61e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=receiver@entry=0x5577f82a9320, event=event@entry=0x5577f825c990) at kernel/qcoreapplication.cpp:1458 #13 0x7fe47673de61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x5577f631b0d0) at kernel/qcoreapplication.cpp:1817 #14 0x7fe47673e3e8 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1676 #15 0x7fe47679e523 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5577f6486940) at kernel/qeventdispatcher_glib.cpp:277 #16 0x7fe46e000624 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x7fe46e0009c0 in () at /usr/lib64/libglib-2.0.so.0 #18 0x7fe46e000a4c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x7fe47679dbcc in QEventDispatcherGlib::processEvents(QFlags) (this=0x5577f6495520, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #20 0x7fe476739cca in QEventLoop::exec(QFlags) (this=this@entry=0x7fff3c103e40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232 #21 0x7fe4767434c7 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1371 #22 0x5577f439299b in main(int, char**) (argc=, argv=) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/main.cpp:121 [Inferior 1 (process 8864) detached] The reporter indicates this bug may be a duplicate of or related to bug 393807. Possible duplicates by query: bug 409464, bug 401181, bug 400283, bug 393807, bug 393662. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 338649] Extend C++ import for C++11
https://bugs.kde.org/show_bug.cgi?id=338649 --- Comment #20 from Oliver Kellogg --- (In reply to milasudril from comment #18) > Any update on this task? A added support for C++11 "enum class" and it is working in a Qt4 based build. However, on trying to import https://invent.kde.org/sdk/umbrello/-/blob/master/test/import/cxx/cxx11-strongly-typed-enumerations.h in a Qt5 based build I get a crash: Application: Umbrello UML Modeller (umbrello5), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fc078f12e80 (LWP 9736))] [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #7 0x7fc07c02c864 in __GI_abort () at abort.c:79 #8 0x7fc07c60b10b in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #9 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fff14653b78, msg=msg@entry=0x7fc07c90aea0 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:893 #10 0x7fc07c60a558 in qt_assert(char const*, char const*, int) (assertion=, file=, line=) at global/qglobal.cpp:3358 #11 0x007b9354 in Lexer::getOffset(QChar const*) const (this=0x7fff14654468, p=0x1852138) at /tools/umbrello-master/lib/cppparse r/lexer.h:265 #12 0x007bb835 in Lexer::currentPosition() const (this=0x7fff14654468) at /tools/umbrello-master/lib/cppparser/lexer.h:853 #13 0x007b4845 in Lexer::nextToken(Token&, bool) (this=0x7fff14654468, tk=..., stopOnNewline=false) at /tools/umbrello-master/li b/cppparser/lexer.cpp:255 #14 0x007b660e in Lexer::tokenize() (this=0x7fff14654468) at /tools/umbrello-master/lib/cppparser/lexer.cpp:497 #15 0x007b3e93 in Lexer::setSource(QString const&) (this=0x7fff14654468, source=...) at /tools/umbrello-master/lib/cppparser/lex er.cpp:143 #16 0x007ab000 in Driver::ParseHelper::ParseHelper(QString const&, bool, Driver*, bool, QString) (this=0x7fff14654420, fileName= ..., force=false, driver=0x10c0260, reportMessages=true, includedFrom=...) at /tools/umbrello-master/lib/cppparser/driver.cpp:321 #17 0x007a0ebc in Driver::parseFile(QString const&, bool, bool, bool) (this=0x10c0260, fileName=..., onlyPreProcess=false, force =false, macrosGlobal=false) at /tools/umbrello-master/lib/cppparser/driver.cpp:555 #18 0x00777b8e in CppImport::parseFile(QString const&) (this=0x15e51d0, fileName=...) at /tools/umbrello-master/umbrello/codeimp ort/cppimport.cpp:145 #19 0x00776edd in ClassImport::importFile(QString const&) (this=0x15e51d0, fileName=...) at /tools/umbrello-master/umbrello/code import/classimport.cpp:120 #20 0x0050c44c in CodeImpThread::run() (this=0x10cb250) at /tools/umbrello-master/umbrello/codeimpwizard/codeimpthread.cpp:62 #21 0x00509d8d in CodeImpStatusPage::importCodeFile(bool) (this=0x7fc07000d050, noError=true) at /tools/umbrello-master/umbrello /codeimpwizard/codeimpstatuspage.cpp:192 #22 0x005098a9 in CodeImpStatusPage::importCode() (this=0x7fc07000d050) at /tools/umbrello-master/umbrello/codeimpwizard/codeimp statuspage.cpp:161 #23 0x00479103 in CodeImpStatusPage::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x7fc07000d050, _c=QMetaOb ject::InvokeMetaMethod, _id=0, _a=0x7fff14654a40) at /tools/umbrello-master/build/umbrello/libumbrello_autogen/6MVZBMHENV/moc_codeimpsta tuspage.cpp:114 #24 0x7fc07c85fc50 in doActivate(QObject*, int, void**) (sender=0x1734400, signal_index=9, argv=argv@entry=0x7fff14654a40) at kernel/qobject.cpp:3898 #25 0x7fc07c858f60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x1734400, m=m@entry=0x7 fc07d99f4e0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff14654a40) at kerne l/qobject.cpp:3946 #26 0x7fc07d5736a2 in QAbstractButton::clicked(bool) (this=this@entry=0x1734400, _t1=) at .moc/moc_qabstractbutton.cp p:308 #27 0x7fc07d57391a in QAbstractButtonPrivate::emitClicked() (this=0x1734440) at widgets/qabstractbutton.cpp:415 #28 0x7fc07d575970 in QAbstractButtonPrivate::click() (this=0x1734440) at widgets/qabstractbutton.cpp:408 #29 0x7fc07d575b91 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) (this=0x1734400, e=0x7fff14654fc0) at widgets/qabstractbutton .cpp:1044 #30 0x7fc07d4c1b4e in QWidget::event(QEvent*) (this=0x1734400, event=0x7fff14654fc0) at kernel/qwidget.cpp:9019 #31 0x7fc07d47faff in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0xbbfc00, receiver=receiver@entry=0x173 4400, e=e@entry=0x7fff14654fc0) at kernel/qapplication.cpp:3632 #32 0x7fc07d4870cb in QApplication::notify(QObject*, QEvent*) (this=0x7fff14654cf0, receiver=0x1734400, e=0x7fff14654fc0) at kernel/ qapplication.cpp:3076 #33 0x7fc07c82913a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x1734400, event=0x7fff14654fc0) at kernel/qcor eapplication.cpp:1063 #34 0x7fc07d486103 in
[Discover] [Bug 430620] Discover shows apps/packages as recommended that I have already installed
https://bugs.kde.org/show_bug.cgi?id=430620
--- Comment #8 from Philipp Reichmuth ---
Maybe the issue is just with the German translation, which translates
"Featured" as "Empfohlen" ("Recommended"). A featured app and a recommended app
are not the same thing, the translation carries the connotation that it's
recommended for me specifically. You can feature something even when it's
already there, while recommending it doesn't make sense.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 436511] In Dolphin settings, there's an outline that doesn't fit anymore with Breeze Light
https://bugs.kde.org/show_bug.cgi?id=436511 --- Comment #1 from Ninguém --- The "General" title gets squeezed in this outline. For example, System Settings, KDE Connect don't have this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436512] New: Popup used to add sensors refuses to close
https://bugs.kde.org/show_bug.cgi?id=436512 Bug ID: 436512 Summary: Popup used to add sensors refuses to close Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 138104 --> https://bugs.kde.org/attachment.cgi?id=138104=edit screen recording SUMMARY Please watch the attached screen recording. Popup to add a sensor opens when I click on "Text-only sensors" row and closes as expected when I click outside it. But if I click on "Text-only sensors" row again I no longer can close the popup clicking outside it. When I reopen the widget settings and click on "Sensors details", the popup is open as it was when the widget settings was closed. EXPECTED RESULT popup used to add sensors should always be closed when we click outside it SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436511] New: In Dolphin settings, there's an outline that doesn't fit anymore with Breeze Light
https://bugs.kde.org/show_bug.cgi?id=436511 Bug ID: 436511 Summary: In Dolphin settings, there's an outline that doesn't fit anymore with Breeze Light Product: dolphin Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: lv215...@anonaddy.me CC: kfm-de...@kde.org Target Milestone: --- Created attachment 138103 --> https://bugs.kde.org/attachment.cgi?id=138103=edit The outline SUMMARY Now that Breeze Light ditched the visual distinction between the content and the titlebar, there's still a outline in window content. STEPS TO REPRODUCE OBSERVED RESULT EXPECTED RESULT I don't know, maybe the line needs to go away? It looks awkward now. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 431505] Kdenlive crashes instantly on Wayland due to EGL format mismatch
https://bugs.kde.org/show_bug.cgi?id=431505 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 431505] Kdenlive crashes instantly on Wayland due to EGL format mismatch
https://bugs.kde.org/show_bug.cgi?id=431505 Alex changed: What|Removed |Added CC||t...@r.je --- Comment #5 from Alex --- *** Bug 433393 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433393] kdenlive crashes at startup (segfault) on plasma wayland 5.21
https://bugs.kde.org/show_bug.cgi?id=433393 Alex changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||alex...@protonmail.com --- Comment #6 from Alex --- It's the exact same crash, and this bug report is newer, so I'll mark this one as a duplicate. *** This bug has been marked as a duplicate of bug 431505 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435806] Hitting F3 in split view always closes right pane, even when it has the focus
https://bugs.kde.org/show_bug.cgi?id=435806 Philipp Reichmuth changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435806] Hitting F3 in split view always closes right pane, even when it has the focus
https://bugs.kde.org/show_bug.cgi?id=435806 --- Comment #4 from Philipp Reichmuth --- No, still happens with 21.04: 1) Open Dolphin 2) Hit F3. There are now two panes showing the same location. 3) Click in the right pane 4) Navigate somewhere else in the right pane 5) Hit F3 again. The right pane (which has the focus) disappears, the left pane (with the original location) remains. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435163] crash on highlighter usage only after save
https://bugs.kde.org/show_bug.cgi?id=435163 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 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.
[kdenlive] [Bug 431604] Transition *.pgm locations are saved as absolute paths
https://bugs.kde.org/show_bug.cgi?id=431604 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.
[lattedock] [Bug 425996] latte panel glitches when I play videos in fullscreen on mpv (Profile gpu-hq, hwdec=auto enabled)
https://bugs.kde.org/show_bug.cgi?id=425996 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394123] Problems with the work of some options
https://bugs.kde.org/show_bug.cgi?id=394123 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 430124] On first start up windows cannot be moved or resized
https://bugs.kde.org/show_bug.cgi?id=430124 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Artikulate] [Bug 436510] New: Artikulate crashes while trying to download courses for first time
https://bugs.kde.org/show_bug.cgi?id=436510
Bug ID: 436510
Summary: Artikulate crashes while trying to download courses
for first time
Product: Artikulate
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: cordlandw...@kde.org
Reporter: rahul...@gmail.com
Target Milestone: ---
Application: artikulate (1.0.0)
Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.11.0-16-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:
Launched artikulate and clicked on download for all the 4 available courses.
- Unusual behavior I noticed:
Crashed while trying to download them.
- Custom settings of the application: None
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Artikulate (artikulate), signal: Segmentation fault
[KCrash Handler]
#4 std::__atomic_base::operator++() (this=) at
/usr/include/c++/10/bits/atomic_base.h:325
#5 QAtomicOps::ref(std::atomic&) (_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:283
#6 QBasicAtomicInteger::ref() (this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:118
#7 QObjectPrivate::Connection::ref() (this=) at
kernel/qobject_p.h:177
#8 QMetaObject::Connection::operator=(QMetaObject::Connection const&)
(this=this@entry=0x562a251ff6a8, other=...) at kernel/qobject.cpp:5272
#9 0x7f4c554e3fbb in
QVector::insert(QMetaObject::Connection*, int,
QMetaObject::Connection const&) (t=..., n=1, before=,
this=0x562a24cf0c18) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:855
#10 QVector::insert(int, QMetaObject::Connection
const&) (this=this@entry=0x562a24cf0c18, i=i@entry=-1, t=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:467
#11 0x7f4c554e2daa in
CourseModel::onCourseAboutToBeAdded(std::shared_ptr, int)
(this=0x562a24cf0c00, course=std::shared_ptr (use count
822085440, weak count 113352) = {...}, row=-1) at
./src/models/coursemodel.cpp:137
#12 0x7f4c554e3a00 in QtPrivate::FunctorCall,
QtPrivate::List, int>, void, void
(CourseModel::*)(std::shared_ptr, int)>::call(void
(CourseModel::*)(std::shared_ptr, int), CourseModel*, void**)
(arg=, o=, f=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152
#13 QtPrivate::FunctionPointer,
int)>::call, int>, void>(void
(CourseModel::*)(std::shared_ptr, int), CourseModel*, void**)
(arg=, o=, f=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185
#14 QtPrivate::QSlotObject,
int), QtPrivate::List, int>, 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:418
#15 0x7f4c53e88b0e in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffb4b72ea0, r=0x562a24cf0c00, this=0x562a24cf02f0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x7fffb4b7c5d0,
signal_index=3, argv=argv@entry=0x7fffb4b72ea0) at kernel/qobject.cpp:3886
#17 0x7f4c53e81cb8 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x7fffb4b7c5d0, m=m@entry=0x7f4c555125c0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffb4b72ea0)
at kernel/qobject.cpp:3946
#18 0x7f4c554a3507 in
IResourceRepository::courseAboutToBeAdded(std::shared_ptr, int)
(this=this@entry=0x7fffb4b7c5d0, _t1=std::shared_ptr (use count
4, weak count 1) = {...}, _t2=) at
./obj-x86_64-linux-gnu/src/artikulatecore_autogen/TAC5DWH4SE/moc_iresourcerepository.cpp:167
#19 0x7f4c554bc122 in ResourceRepository::loadCourse(QString const&)
(this=this@entry=0x7fffb4b7c5d0, resourceFile=...) at
./src/core/resourcerepository.cpp:125
#20 0x7f4c554bc83a in operator() (dir=..., __closure=0x7fffb4b73030) at
./src/core/resourcerepository.cpp:97
#21 std::__invoke_impl&, QDir> (__f=...) at
/usr/include/c++/10/bits/invoke.h:60
#22 std::__invoke_r&,
QDir> (__fn=...) at /usr/include/c++/10/bits/invoke.h:153
#23 std::_Function_handler >::_M_invoke(const
std::_Any_data &, QDir &&) (__functor=..., __args#0=) at
/usr/include/c++/10/bits/std_function.h:291
#24 0x7f4c554bbb16 in std::function::operator()(QDir) const
(__args#0=..., this=0x7fffb4b73030) at
/usr/include/c++/10/bits/std_function.h:622
#25 ResourceRepository::reloadCourses() (this=) at
./src/core/resourcerepository.cpp:106
#26 0x7f4c53e88b44 in doActivate(QObject*, int, void**)
(sender=0x562a24947e20, signal_index=59, argv=argv@entry=0x7fffb4b73420) at
kernel/qobject.cpp:3898
#27 0x7f4c53e81ef1 in QMetaObject::activate(QObject*, int, int, void**)
(sender=, signalOffset=,
local_signal_index=,
[kontact] [Bug 436509] New: HTML preview not available for google calendar event emails under description.
https://bugs.kde.org/show_bug.cgi?id=436509 Bug ID: 436509 Summary: HTML preview not available for google calendar event emails under description. Product: kontact Version: 5.16.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: rahul...@gmail.com Target Milestone: --- Created attachment 138102 --> https://bugs.kde.org/attachment.cgi?id=138102=edit screenshot of how the description currently looks like on my system. SUMMARY While rendering a google calendar event email the description does not render it as HTML content even if the settings are configured to display HTML over plain-text. The description contains the HTML tags hardcoded and directly dumped on the UI. STEPS TO REPRODUCE 1. Schedule any google calendar event from the web UI. 2. Add descriptions while creating the event. 3. For the email sent/received check under the description section for the corresponding event. OBSERVED RESULT The text contains HTML tags hardcoded. EXPECTED RESULT The description, if containing HTML tags, and if kmail settings are configured to prefer HTML over plain-text, needs to be rendered accordingly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Attached a screenshot of how the description currently looks like on my system. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436508] New: Simplified Chinese translation alone cannot be loaded in Nightly Appimage
https://bugs.kde.org/show_bug.cgi?id=436508 Bug ID: 436508 Summary: Simplified Chinese translation alone cannot be loaded in Nightly Appimage Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Translation Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- In the lastest Appimage krita-5.0.0-prealpha-c0b6649-x86_64.appimage (2021-05-03), all languages are now listed in Switch Application Language dialogue. However, for some reason, Krita does not load Simplified Chinese translation, and will only use English regardless of the settings. Other languages work fine. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 352994] Give the possibility to improve the management of the accounts
https://bugs.kde.org/show_bug.cgi?id=352994 g_fre...@hotmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436497] Fedora 34 KDE Wayland is not usable - no multi-monitor detection, 1024x768 resolution only for eDP1 on Dell Precision 5540
https://bugs.kde.org/show_bug.cgi?id=436497 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 436507] New: Bypass Client Isolation
https://bugs.kde.org/show_bug.cgi?id=436507 Bug ID: 436507 Summary: Bypass Client Isolation Product: kdeconnect Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: doti...@126.com Target Milestone: --- SUMMARY Is it possible to connect KDEConnect through WiFi Direct so that I could bypass the client isolation in a bar or at my univ. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436331] Kate 21.04 from Binary Factory stable build crash at launch
https://bugs.kde.org/show_bug.cgi?id=436331 --- Comment #2 from Gary Wang --- Thanks for the fix, it works now with kate-21.04.0-1264-windows-msvc2019_64-cl.exe :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436386] Save timeline zone to bin - issue
https://bugs.kde.org/show_bug.cgi?id=436386 --- Comment #9 from chibo --- (In reply to emohr from comment #8) > Unfortunately the video doesn’t start. turn off ad block or track block (it's yandex, you can trust) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436506] New: Display indicator for programs running in the background
https://bugs.kde.org/show_bug.cgi?id=436506 Bug ID: 436506 Summary: Display indicator for programs running in the background Product: plasmashell Version: 5.21.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kde.podag...@slmail.me Target Milestone: 1.0 Programs that can keep running in the background usually have an option to display some icon in the systray, but if the user prefers to hide the icon so that it is not always visible, taking up space and filling this area with different things, there will be no indicator (other than the hidden icon) that the program is active. This is also, in my humble opinion, a matter of consistency. Because it prevents the systray from getting polluted with program icons that are already in the apps panel. And these icons often have nothing to do with the default icons of the Breeze theme, which only makes the situation worse (the screenshots I will put right below demonstrate this). It also maintains a consistency as to the organization and separation of native plasma widgets from the systray and other user programs. Because it keeps the systray clean and dedicated to its primary purpose: displaying system information. This is a big discussion, and some desktops have even completely removed support for program icons in the systray, I am very much against this, but I think it can be improved with a few tweaks. Take this screenshot example (https://i.imgur.com/tTFzIdq.png), all six of these programs highlighted with the red line are currently active, but I don't have any visual feedback on this. They can display an icon in the systray, but this would turn it into a completely messy kitchen, besides duplicating the display of the same icons and taking up unnecessary space. This is what happens if I choose to display the icons in the systray: https://i.imgur.com/c29IS0k.png A total mess. When everything is organized following basic criteria, this is the result: https://i.imgur.com/qrc7a9z.png No duplicate icons and a much more objective notification area. Of course there is an obvious option to simply disable the background running and not have this problem, but it would generate another one. Because they are tools that we usually need to keep running, but often not necessarily in the foreground, which brings us to the problem again. To sum it all up: an indicator on the app icon telling that it is open in the background removes the need to have the same icon in the systray and keeps everything more organized and consistent. Apps where apps should be, and widgets where widgets should be. Please don't get me wrong, I'm not criticizing the work of amazing volunteers, but rather suggesting a possible solution to one of the things that bothers me the most. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 435309] 3b06b6f22 makes selection near invisible with some foreground/background color combinations
https://bugs.kde.org/show_bug.cgi?id=435309 --- Comment #21 from Ahmad Samir --- It looks like we'll either have to revert the whole change or add (yet) another option to the settings dialog. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436505] New: Opening large file through dolphin causes large increase in dolphin memory use
https://bugs.kde.org/show_bug.cgi?id=436505 Bug ID: 436505 Summary: Opening large file through dolphin causes large increase in dolphin memory use Product: dolphin Version: 21.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: holle...@cs.dal.ca CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open dolphin, memory use ~25MB 2. Click to open a large (e.g. 1GB) file in another program OBSERVED RESULT Dolphin memory usage jumps to >500MB. EXPECTED RESULT Memory use is not significantly affected by clicking to open a file in another program. COMMENTS I have observed this behavior also in Dolphin 20.12, and across multiple file types, such as an archive opened in Ark, and a video. The detective work was done by another in bug 398908, and also reproduced by a third user. In all cases, memory use did not increase if the file was opened via right click and selecting "Open with " in the menu. I am creating this report because 398908 is a reopened bug from 3 years ago for a presumably unrelated issue. KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 436434] UI problems and legibility
https://bugs.kde.org/show_bug.cgi?id=436434 David Jarvie changed: What|Removed |Added Version Fixed In||21.04.1 Latest Commit|093949ddb6a037e27813493c7ad |a70a2aea022840b52967b710ba2 |86e74bfcc14b1 |02af3a020b661 --- Comment #4 from David Jarvie --- The hiding of the alarm date has now been fixed by commit a70a2aea022840b52967b710ba202af3a020b661 in 21.04 branch. This fix will also be in KDE apps release 21.04.1. Thank you for reporting this bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436301] Embedded Libreoffice files are not shown as embedded files in the File menu.
https://bugs.kde.org/show_bug.cgi?id=436301 --- Comment #5 from Peter Maiwald --- (In reply to Albert Astals Cid from comment #4) > As far as I can see there's no attachment in that file. > > What makes you think there is one? Open it in Libreoffice Draw. There is the pdf and the Libreoffice Draw in this File. But nobody can see this in Okular. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 Paul changed: What|Removed |Added CC||holle...@cs.dal.ca --- Comment #83 from Paul --- I am also experiencing this issue. Memory usage jumps to 550MB if I open a large file by clicking it, and not if I open through the menu. Nice detective work. This seems like a very specific issue. Should it perhaps go in its own bug report? Arch Linux Dolphin 20.12.3 Frameworks 5.81 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436473] Cursor is stuck to resize icon when hovering into panels across the movable dividers
https://bugs.kde.org/show_bug.cgi?id=436473 --- Comment #2 from tomtomtomreportin...@gmail.com --- Let's take the Places panel for example, which contains your bookmarked folders. If placed to the left of the main view of the current directory, a user can resize the Places panel using the divider between the Places panel and the main view. This divider is what I'm referring to when I say "movable divider". The cursor switches to a sort of resize icon when shifting this divider. More specific steps to reproduce the buggy behavior: 1. Place cursor over the main view (showing the files and folders of the current directory) 2. Shift the cursor to the left, moving across the divider and into the Places panel to the left of the main view. No clicking/dragging is necessary to reproduce. It seems that the cursor will "inherit" the resize icon as it moves across the movable divider seperating the panel and main view. It doesn't always happen, but it happens most of the time for both me and a friend. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436501] Cache mechanism in Dolphin is making it completely unreliable.
https://bugs.kde.org/show_bug.cgi?id=436501 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 436504] Sleep/suspend is broken on KDE Neon Testing Edition
https://bugs.kde.org/show_bug.cgi?id=436504 techxga...@outlook.com changed: What|Removed |Added Summary|Sleep/suspend is broken on |Sleep/suspend is broken on |KDE Neon|KDE Neon Testing Edition -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 436504] New: Sleep/suspend is broken on KDE Neon
https://bugs.kde.org/show_bug.cgi?id=436504 Bug ID: 436504 Summary: Sleep/suspend is broken on KDE Neon Product: Powerdevil Version: 5.21.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: techxga...@outlook.com Target Milestone: --- SUMMARY Whenever I want my computer to sleep via power button on my desktop or directly from Kickoff, the computer logs out instead STEPS TO REPRODUCE * Click the logout from Kickoff * Press the power button OBSERVED RESULT The screen would shut off, like it's about to sleep, but would instead log me out. EXPECTED RESULT PC is supposed to sleep SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-7614-generic OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1060 6GB/PCIe/SSE2 ADDITIONAL INFORMATION This might be the wrong section, but I'm not sure where to report the bug. Feel free to move it or point me to the right direction. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436350] Plasma crash a few seconds after login following an upgrade to Plasma 5.21.4
https://bugs.kde.org/show_bug.cgi?id=436350
--- Comment #39 from Vaclav Masin ---
(In reply to Konrad Materka from comment #36)
> Created attachment 138098 [details]
> patch: workaround + logs attempt3
>
> This is super strange...
>
> To recheck: before starting of KTorrent (just after plasmashell restart)
> everything should look fine: you should see all items in System Tray setting
> with no empty row.
This seems to be correct.
> After running KTorrent you should see empty rows in setting and few icons
> missing (KMix, KMail).
Yes, those empty rows in system tray settings windows are now actually even all
over the place - see the attached screenshot.
> After kded5 restart you should around 5 or 6 empty
> rows and KMix, KMail etc visible again.
>
Yes, this recovers the icons in the systray but those empty items in system
tray settings are still there.
> To summarize what I found:
> In System There is an internal list of SNI items with service id +
> StatusNotifierItemService pointer. You can see it as Item(...) in logs.
> Everything looks fine until you start new application - existing items in
> the list are for whatever reason cleared! Service id is empty (""). This of
> course breaks everything. I still don't know why...
>
> Just to double check, can you apply attached patch (revert earlier patches)?
> It will log state just before item add and just after.
>
Done - see the attached log called " Plasma shell extended logging 2".
> One more test: it seems that on start you have exactly 6 SNI icons (KMix,
> KMail, Kwallet etc). Can you close two of them, restart plasmashell, run
> something (for example KTorrent) and check logs? Is there "No DataSource
> for"?
There are those "No DataContainer for" (I'm guessing you meant that and not "No
DataSource for") after restarting Plasmashell, but not after starting up one
app after that.
> If not, start more apps with icons (can be these two you closed before
> start). This is to check if 6 is important (it is an initial capacity of the
> internal list).
Yeah, all the hell seems to break loose once I start the +1 app. There are some
more "No DataContainer for" messages and some icons disappear from the sys tray
and there are suddenly those empty items in System Tray settings.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 375602] Debug and run should save the current file when working in python
https://bugs.kde.org/show_bug.cgi?id=375602 Ashark changed: What|Removed |Added CC||ash...@linuxcomp.ru --- Comment #3 from Ashark --- I have found another workaround. In the "External Scripts" panel create a script. Add the command "%f". In "Save mode" option set "Save Active Document". Then assign a shortcut for the script. Then use that shortcut instead of Execute and Save buttons/shortcuts. See the video for details: https://youtu.be/nQ5Iqr8-Ftc -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 407918] Does not find music on other partition (ext4 or NTFS) even when added to search paths
https://bugs.kde.org/show_bug.cgi?id=407918 Shawn changed: What|Removed |Added CC||shawn.peter...@gmx.com --- Comment #28 from Shawn --- I am unclear if this bug is still open, but I am having the same issue on my manjaro system. Difference being my music folder is the main partition in the default place (still ext4). Sometimes it scans the music, sometimes it does not. And when it does find them, it is probably gone when I restart the application. It can find them and play them just fine through the internal file browser. I have better luck with the "scan files directly" toggled on, but better only means that I sometimes see the music. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375602] Debug and run should save the current file when working in python
https://bugs.kde.org/show_bug.cgi?id=375602 Ashark changed: What|Removed |Added CC||jurajora...@mailo.com --- Comment #2 from Ashark --- *** Bug 413674 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 413674] Script Launcher: Save files before running
https://bugs.kde.org/show_bug.cgi?id=413674 Ashark changed: What|Removed |Added Status|REPORTED|RESOLVED CC||ash...@linuxcomp.ru Resolution|--- |DUPLICATE --- Comment #1 from Ashark --- Thanks for the report. I am closing it as duplicate, as there is already very similar bug report which was reported earlier and already has some votes. *** This bug has been marked as a duplicate of bug 375602 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436350] Plasma crash a few seconds after login following an upgrade to Plasma 5.21.4
https://bugs.kde.org/show_bug.cgi?id=436350 --- Comment #38 from Vaclav Masin --- Created attachment 138101 --> https://bugs.kde.org/attachment.cgi?id=138101=edit System Tray settings screenshot - empty items -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436350] Plasma crash a few seconds after login following an upgrade to Plasma 5.21.4
https://bugs.kde.org/show_bug.cgi?id=436350 Vaclav Masin changed: What|Removed |Added Attachment #138100|Plasma sh |Plasma shell extended description||logging 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436350] Plasma crash a few seconds after login following an upgrade to Plasma 5.21.4
https://bugs.kde.org/show_bug.cgi?id=436350 --- Comment #37 from Vaclav Masin --- Created attachment 138100 --> https://bugs.kde.org/attachment.cgi?id=138100=edit Plasma sh -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436503] New: Dolphin Properties window has cutoff tabs
https://bugs.kde.org/show_bug.cgi?id=436503 Bug ID: 436503 Summary: Dolphin Properties window has cutoff tabs Product: dolphin Version: 21.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: aiden.gr...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 138099 --> https://bugs.kde.org/attachment.cgi?id=138099=edit Properties window, notice the top SUMMARY The file-properties window does not have space to fit all of its tabs. STEPS TO REPRODUCE 1. Open Dolphin 2. Right-click on a file to open its Properties 3. OBSERVED RESULT The window has an arrow control to scroll through the tabs. EXPECTED RESULT The window should be wide enough to fit everything inside it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: yes, dolphin 21.04.0 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The displayed window is in DejaVu Sans, but it will also happen in the default Noto Sans. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436500] Crash when opening then closing a display
https://bugs.kde.org/show_bug.cgi?id=436500 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/932 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436501] Cache mechanism in Dolphin is making it completely unreliable.
https://bugs.kde.org/show_bug.cgi?id=436501 --- Comment #3 from Leinier Cruz Salfran --- It seems you didn’t read the part when I wrote “my cousin reported to me that he doesn’t find some music he had on his flash memory”. Did you read the entire report? > On 2 May 2021, at 5:03 PM, Kai Uwe Broulik wrote: > > https://bugs.kde.org/show_bug.cgi?id=436501 > > Kai Uwe Broulik changed: > > What|Removed |Added > > Severity|critical|normal > CC||k...@privat.broulik.de > > --- Comment #2 from Kai Uwe Broulik --- > Lowering severity as no data loss occurs, merely a display issue. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 359903] ktorrent sequential download UI wishlist
https://bugs.kde.org/show_bug.cgi?id=359903 King_DuckZ changed: What|Removed |Added CC||king_du...@gmx.com --- Comment #5 from King_DuckZ --- A bit late to the party but I got here trying to solve an issue: I double clicked on a media file the whose preview was *not* available yet, and KTorrent asked me if I wanted to activate sequential mode for that file. I clicked "yes" just to see what happened, but now I want to disable it. I spent quite a bit of time looking around in the various menus and then on the internet but I can't find a way to disable this mode once activated. Does this bug report mean that there is no way to deactivate sequential mode once it's activated? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436501] Cache mechanism in Dolphin is making it completely unreliable.
https://bugs.kde.org/show_bug.cgi?id=436501 Kai Uwe Broulik changed: What|Removed |Added Severity|critical|normal CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- Lowering severity as no data loss occurs, merely a display issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436350] Plasma crash a few seconds after login following an upgrade to Plasma 5.21.4
https://bugs.kde.org/show_bug.cgi?id=436350
Konrad Materka changed:
What|Removed |Added
Attachment #138063|0 |1
is obsolete||
Attachment #138073|0 |1
is obsolete||
Attachment #138074|0 |1
is obsolete||
Attachment #138082|0 |1
is obsolete||
Attachment #138083|0 |1
is obsolete||
Attachment #138084|0 |1
is obsolete||
Attachment #138089|0 |1
is obsolete||
Attachment #138090|0 |1
is obsolete||
--- Comment #36 from Konrad Materka ---
Created attachment 138098
--> https://bugs.kde.org/attachment.cgi?id=138098=edit
patch: workaround + logs attempt3
This is super strange...
To recheck: before starting of KTorrent (just after plasmashell restart)
everything should look fine: you should see all items in System Tray setting
with no empty row.
After running KTorrent you should see empty rows in setting and few icons
missing (KMix, KMail). After kded5 restart you should around 5 or 6 empty rows
and KMix, KMail etc visible again.
To summarize what I found:
In System There is an internal list of SNI items with service id +
StatusNotifierItemService pointer. You can see it as Item(...) in logs.
Everything looks fine until you start new application - existing items in the
list are for whatever reason cleared! Service id is empty (""). This of course
breaks everything. I still don't know why...
Just to double check, can you apply attached patch (revert earlier patches)? It
will log state just before item add and just after.
One more test: it seems that on start you have exactly 6 SNI icons (KMix,
KMail, Kwallet etc). Can you close two of them, restart plasmashell, run
something (for example KTorrent) and check logs? Is there "No DataSource for"?
If not, start more apps with icons (can be these two you closed before start).
This is to check if 6 is important (it is an initial capacity of the internal
list).
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 436487] IPTC:ObjectAttributeReference and XMP:IntellectualGenre
https://bugs.kde.org/show_bug.cgi?id=436487 Maik Qualmann changed: What|Removed |Added Platform|Other |unspecified OS|Other |All -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436497] Fedora 34 KDE Wayland is not usable - no multi-monitor detection, 1024x768 resolution only for eDP1 on Dell Precision 5540
https://bugs.kde.org/show_bug.cgi?id=436497 Nicolas Fella changed: What|Removed |Added Severity|critical|normal CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436487] IPTC:ObjectAttributeReference and XMP:IntellectualGenre
https://bugs.kde.org/show_bug.cgi?id=436487 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436444] Question to translation of album categories
https://bugs.kde.org/show_bug.cgi?id=436444 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.3.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436487] IPTC:ObjectAttributeReference and XMP:IntellectualGenre
https://bugs.kde.org/show_bug.cgi?id=436487 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/cbbe13f ||c2d208110d823ec2c8cc3760f8b ||9bc8ed Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Maik Qualmann --- Git commit cbbe13fc2d208110d823ec2c8cc3760f8b9bc8ed by Maik Qualmann. Committed on 02/05/2021 at 20:49. Pushed by mqualmann into branch 'master'. optimize dialog layout from the Metadata Edit M +2-1NEWS M +2-2 core/dplugins/generic/metadata/metadataedit/dialog/multistringsedit.cpp M +2-2 core/dplugins/generic/metadata/metadataedit/dialog/objectattributesedit.cpp M +5-4 core/dplugins/generic/metadata/metadataedit/xmp/xmpproperties.cpp https://invent.kde.org/graphics/digikam/commit/cbbe13fc2d208110d823ec2c8cc3760f8b9bc8ed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436422] Concentric ellipse assistant tool fails to draw a perfect circle when using "snap to assistants"
https://bugs.kde.org/show_bug.cgi?id=436422 --- Comment #4 from Autumn Lansing --- As it happens with a mouse and even with my tablet unplugged, it's probably not related to tablet settings. I've previously reported the so-far unaddressed bug 434269, which can sometimes cause freehand curves to jump and give a straight line, but in that case it only happens if I don't wait the three seconds or so for the freeze to happen before starting my stroke. If I wait until after the brief freeze, then I can draw a freehand curve without any problems. In this new bug, there is no freeze. It happens whenever I draw a circle /ellipse with the tool, regardless. It's mostly unnoticeable at large scale, but when drawing small circles, it's highly noticeable. The smaller the circle, the more noticeable it is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436061] Extreme memory usage on idle system
https://bugs.kde.org/show_bug.cgi?id=436061 --- Comment #3 from Miguel Hernandez --- I think I've found the root cause on my system: the slideshow background changer. After set a static image as wallpaper the plasmashell process decrease to 321MB. I use Wikimedia Commons as provider and the daily image is really too big (https://upload.wikimedia.org/wikipedia/commons/f/f9/Lady_with_an_Ermine_-_Leonardo_da_Vinci_-_Google_Art_Project.jpg). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436502] New: [PipeWire] Audio icon displayed next to every program except program playing audio
https://bugs.kde.org/show_bug.cgi?id=436502 Bug ID: 436502 Summary: [PipeWire] Audio icon displayed next to every program except program playing audio Product: plasmashell Version: 5.21.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: xlkil...@gmail.com Target Milestone: 1.0 Created attachment 138097 --> https://bugs.kde.org/attachment.cgi?id=138097=edit Screenshot of audio icons SUMMARY After a while of playing audio, the icons are displayed next to every app icon except the one playing audio and the ones, which programs are opened (on that virtual desktop). STEPS TO REPRODUCE 1. Play audio from any program 2. Wait 3. OBSERVED RESULT False icon positioning; clicking the icon still works and changes the visual state for all icons. EXPECTED RESULT Icon should be at correct position. SOFTWARE/OS VERSIONS X11 Linux/KDE Plasma: Fedora 34 (5.10.33) (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 PipeWire: 0.3.26 ADDITIONAL INFORMATION Maybe related to 375943? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 436383] give more control and visibility to user which microphone is being used and how sensitive it is
https://bugs.kde.org/show_bug.cgi?id=436383 --- Comment #2 from Marian Klein --- marian@HPSpectre:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofsoundwire [sof-soundwire], device 1: Headset mic (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 3: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 4: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436061] Extreme memory usage on idle system
https://bugs.kde.org/show_bug.cgi?id=436061 Miguel Hernandez changed: What|Removed |Added CC||poetahal...@protonmail.com --- Comment #2 from Miguel Hernandez --- Today I've observed this problem on Manjaro. The plasmashell process consumes until 11GB on startup and after a few seconds it decreases to 5GB (24GB RAM). SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Xorg: 1.20.11 Kernel: 5.12.0 OS-Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395171] Remove UTF-16 and other non ASCII compatible encodings
https://bugs.kde.org/show_bug.cgi?id=395171 --- Comment #15 from Egmont Koblinger --- I did indeed make a technical mistake. For some mysterious reason, what I incorrectly had in my mind was that the boundary beyond BMP (i.e. at U+) is where UTF-8 increases from 2 bytes to 3. This is indeed not correct, this is where it increases from 3 bytes to 4. The increase from 2 bytes to 3 happens at a much lower codepoint. Therefore, indeed, there are many letter-based scripts that use 3 bytes per letter in UTF-8. I wrote the CJK stuff with this mistake in mind. I was technically incorrect, and for this I do apologize from everyone. * * * That being said: - Jayadevan still does not understand, and apparently still refuses to even try to understand, that UTF-16 cannot be made to work in terminals for a plethora of reasons, including, but not limited to the fact that all components of the system that interact with terminals only support ASCII-compatible encodings there; - ignores that UTF-16 mode never worked; that is, firmly speaks up against removing something that, again, *never* *worked*, *still* *does* *not* *work* and *can* *not* *be* *fixed*; - ignores that the work happening inside terminal emulators is typically English-centric by its nature; - ignores that the difference in the byte count simply does not matter at all; - ignores that choosing one technical solution over the other, even if that technical solution results in a higher network traffic for some languages vs. a lower one for some others, is no discrimination whatsoever (and even if it was, the right place to complain would be the Unicode Consortium, and not Konsole); - ignores that even if terminals and their surrounding infrastructure could implement UTF-16 support (which, again, they cannot reasonably do), this would mean switching from 1 standard to 2 incompatible ones being used concurrently, which would obviously bring plenty of problems (the very exact problem that Unicode was meant to fix) and would not solve anything; - in comments 7 & 9 used wording that are at the very least borderline unacceptable. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436501] Cache mechanism in Dolphin is making it completely unreliable.
https://bugs.kde.org/show_bug.cgi?id=436501 --- Comment #1 from Leinier Cruz Salfran --- Created attachment 138096 --> https://bugs.kde.org/attachment.cgi?id=138096=edit The demonstration of the last bad thing I've detected on Dolphin Here is the video that demonstrate that the "cache" system you've implemented in Dolphin must be wiped completely. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395171] Remove UTF-16 and other non ASCII compatible encodings
https://bugs.kde.org/show_bug.cgi?id=395171 --- Comment #14 from tcanabr...@kde.org --- Jayadevan, As a Konsole developer, I prefer to have things based on facts as explained by Egmont. *Even* if it was just *one* issue with a language it's enough reason to not use UTF16. *I don't care* if UTF16 makes things less anglocentric, I care that "cat" understands what's a newline and I care that grep undestands what's a "\t", not to mention pipe, <<, and other special chars that are handled by the terminal running inside of konsole. You stepped out of line as soon as you used the 'racist' card, and *i will not* tolarate this kind of accusation. You had one warning, I urge you to not have three. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436501] New: Cache mechanism in Dolphin is making it completely unreliable.
https://bugs.kde.org/show_bug.cgi?id=436501 Bug ID: 436501 Summary: Cache mechanism in Dolphin is making it completely unreliable. Product: dolphin Version: 20.12.0 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: leinie...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Hello Dolphin developers. You're doing a great work with Dolphin, I really like the user interface and the possibilities it gives me, besides it is the intrinsic files explorer of the desktop environment, so it is interconnected with other stuff of the ecosystem. But, and here I go, there is something that is making Dolphin completely unreliable and it is happening from some years ago when I detected for the first time a problem with a transfer of files I made. I didn't reported it at the time but now. The source of that bad behavior is the "cache" system you've implemented in it. Please, let me tell you that the "cache system" is badly coded (100%) and it is causing problems with the visualization and transfer of files between locations and visualization of disk information like free space, among other things I'm pretty sure it is happening, but I didn't see them yet. I've lost files because of wrong copies (files not copied) and about a week ago my cousin reported to me that he didn't find some music files he had in the flash memory he gave me to make an organizational operation (he had a lot of musics on the root directory and he wanted me to put those musics into several directories). The last bad thing I detected was on Apr-30-2021: - I copied a first SVG image from one location to another. - Dolphin showed me the preview of the first image correctly. - I found a second image I liked more. - I deleted the first image from the destination location. - I transferred the second image to the destination location. - Dolphin showed me the preview of the second image correctly. - I changed the name of the second image to the name of the first image. - The problem: Dolphin showed me the image of the first image instead of the second. Dolphin is a critical piece of the KDE Desktop Environment. It job is to work directly with files and directories, those who are important to everybody, so, it have to do it work completely well and beyond (200%). Do you imagine that you loss some important files of a project of yours because Dolphin didn't copied them correctly to the backup device, or you loss your favorites music and films, or you get embarrassed in your school or work when it is your turn to do a presentation in front of an auditorium and the "thing" doesn't work because of the lack of files in the memory flash? That must not happen never. I have a proposal and it would be great if you all take it very seriously: - Eliminate completely the cache system in Dolphin and make Dolphin do the work it need every time it need to do it. -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 436498] WindowSystem::window(WId wid) returns the wrong window
https://bugs.kde.org/show_bug.cgi?id=436498 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- At least it's found. As for this bug - we definitely need to fix krunner. Super worst case, we just if guard round that call. As for this bug, I think the right call is to strip all plasmaWindowManagement from kwayland-integration to leave only things that meddle with our windows not 3rd party windows. It's a broken concept to try and retroactively fit into our old API. Only plasma should meddle with other windows, and we have native API for that so should have no regressions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436500] New: Crash when opening then closing a display
https://bugs.kde.org/show_bug.cgi?id=436500 Bug ID: 436500 Summary: Crash when opening then closing a display Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: aleix...@kde.org Target Milestone: --- Here's a detailed valgrind backtrace that shows how certain egl pointers are cleaned up twice. ==15995== Invalid read of size 8 [162/1932] ==15995==at 0x11EE0B0F: ??? (in /usr/lib/libEGL_mesa.so.0.0.0) ==15995==by 0xEA60B25: KWin::GbmSurface::releaseBuffer(gbm_bo*) (devel/frameworks/kwin/src/plugins/platforms/drm/gbm_surface.cpp:41) ==15995==by 0xEA5F725: KWin::GbmBuffer::~GbmBuffer() (devel/frameworks/kwin/src/plugins/platforms/drm/drm_buffer_gbm.cpp:53) ==15995==by 0xEA60028: KWin::DrmGbmBuffer::~DrmGbmBuffer() (devel/frameworks/kwin/src/plugins/platforms/drm/drm_buffer_gbm.cpp:87) ==15995==by 0xEA5E835: QtSharedPointer::ExternalRefCountWithContiguousData::deleter(QtSharedPointer::ExternalRefCountData*) (devel/kde5/include/QtCore/qsharedpointer_impl.h:248) ==15995==by 0xEA1CE85: QtSharedPointer::ExternalRefCountData::destroy() (devel/kde5/include/QtCore/qsharedpointer_impl.h:149) ==15995==by 0xEA3673E: QSharedPointer::deref(QtSharedPointer::ExternalRefCountData*) (devel/kde5/include/QtCore/qsharedpointer_impl.h:458) ==15995==by 0xEA366F8: QSharedPointer::deref() (devel/kde5/include/QtCore/qsharedpointer_impl.h:453) ==15995==by 0xEA363F4: QSharedPointer::~QSharedPointer() (devel/kde5/include/QtCore/qsharedpointer_impl.h:310) ==15995==by 0xEA362FE: QSharedPointer::operator=(QSharedPointer const&) (devel/kde5/include/QtCore/qsharedpointer_impl.h:333) ==15995==by 0xEA3DE95: KWin::DrmPlane::setCurrent(QSharedPointer const&) (devel/frameworks/kwin/src/plugins/platforms/drm/drm_object_plane.h:81) ==15995==by 0xEA39379: KWin::DrmOutput::teardown() (devel/frameworks/kwin/src/plugins/platforms/drm/drm_output.cpp:67) ==15995==by 0xEA48463: KWin::DrmGpu::removeOutput(KWin::DrmOutput*) (devel/frameworks/kwin/src/plugins/platforms/drm/drm_gpu.cpp:426) ==15995==by 0xEA496B8: KWin::DrmGpu::updateOutputs() (devel/frameworks/kwin/src/plugins/platforms/drm/drm_gpu.cpp:305) ==15995==by 0xEA1DDC4: KWin::DrmBackend::updateOutputs() (devel/frameworks/kwin/src/plugins/platforms/drm/drm_backend.cpp:336) ==15995==by 0xEA1FA86: KWin::DrmBackend::handleUdevEvent() (devel/frameworks/kwin/src/plugins/platforms/drm/drm_backend.cpp:266) ==15995==by 0xEA28910: QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KWin::DrmBackend::*)()>::call(void (KWin::DrmBackend::*)(), KWin::DrmBackend*, void**) (devel/kde5/include/QtCore/qobjectdefs_impl.h:152) ==15995==by 0xEA28877: void QtPrivate::FunctionPointer::call, void>(void (KWin::DrmBackend::*)(), KWin::DrmBackend*, void**) (devel/kde5/include/QtCore/qobjectdefs_impl.h:185) ==15995==by 0xEA287A4: QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (devel/kde5/include/QtCore/qobjectdefs_impl.h:418) ==15995==by 0x801D3D5: call (qobjectdefs_impl.h:398) ==15995==by 0x801D3D5: void doActivate(QObject*, int, void**) (qobject.cpp:3886) ==15995==by 0x802081E: QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (moc_qsocketnotifier.cpp:178) ==15995==by 0x802101A: QSocketNotifier::event(QEvent*) (qsocketnotifier.cpp:302) ==15995==by 0x6C8517E: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3632) ==15995==by 0x7FE6DF9: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1064) ==15995==by 0x803B54A: QEventDispatcherUNIXPrivate::activateSocketNotifiers() (qeventdispatcher_unix.cpp:304) ==15995==by 0x803B9AA: QEventDispatcherUNIX::processEvents(QFlags) (qeventdispatcher_unix.cpp:511) ==15995==by 0x1C66DC: QUnixEventDispatcherQPA::processEvents(QFlags) (qunixeventdispatcher.cpp:63) ==15995==by 0x7FE57AA: QEventLoop::exec(QFlags) (qeventloop.cpp:232) ==15995==by 0x7FEDA2F: QCoreApplication::exec() (qcoreapplication.cpp:1375) ==15995==by 0x1953CF: main (devel/frameworks/kwin/src/main_wayland.cpp:726) ==15995== Address 0x1223ebb8 is 552 bytes inside a block of size 808 free'd ==15995==at 0x483F9AB: free (vg_replace_malloc.c:538) ==15995==by 0x11EE2AB1: ??? (in /usr/lib/libEGL_mesa.so.0.0.0)
[konsole] [Bug 395171] Remove UTF-16 and other non ASCII compatible encodings
https://bugs.kde.org/show_bug.cgi?id=395171 --- Comment #13 from Jayadevan --- (In reply to tcanabrava from comment #11) > This thread is now under Community Working Group supervision. > > (1) All strings should be sanitised, so that they will be perfectly safe, > and will not break anything. > > You clearly are ignoring the issues pointed out by Egmond, sanitization has > nothing to do with this. > > (2) It is racist to suggest that all non-English people are Chinese (or > Japanese or Korean). > > Please take a look at the KDE Code of Conduct, we will not tolerate > accusations of racism on what as meat to be an explanation based on a > example. if there is more than CJK that uses more bytes per enconding, is > irrelevant. > > Most scripts in the world are given only 3 byte encodings per character in > UTF-8, and not a code point per spoken word, as you say. That is a lie. > > (3) The world has still not settled on UTF-16. But modern languages and > platforms tend to do so. Java, Dotnet, ICU, KDE, QT, Windows NT, JavaScript, > Dart, Flutter... > In today's world, support for both the modern UTF-16 and the legacy UTF-8 is > needed. > > Patches welcome, I won't spend time working on this untill the *base > software* (bash, zsh, etc) supports it. He mentioned that Scripts other than English are having one code point to stand for one "syllable or an entire word". He used CJK as an example. That is a cherry-picked example to prove a wrong point. The conclusion was that 1 code point can have 3 bytes for non-Latin scripts, as they have one word per code point. Most scripts like Devanagari, Bengali, Gurmukhi, Gujarati, Oriya, Tamil, Telugu, Kannada, Malayalam, Sinhala, Thai, Lao, Tibetan, Myanmar, Georgian, Ethiopic, Cherokee, Unified Canadian Aboriginal Syllabics, Khmer, and many others, used by billions of people are having 3 bytes per code-point, and have only one phoneme per code point, unlike he mentioned. His cherry-picking of examples to prove a wrong point. He said "The only sense in which one can perhaps claim that UTF-8 is Anglo-centric, is that it uses 1 byte for English letters vs. 3 bytes for CJK (Chinese, Japanese, Korean) symbols; whereas UTF-16 uses 2 for both. Given that an English letter represents, well, a single letter of a word, whereas a CJK symbol represents a syllable or an entire word, I actually do think UTF-8's 1:3 split is a way more fair system." The implication is clearly that other than English (or Latin), the only scripts which matter is CJK. That is clearly inappropriate against people from South Asia, SE Asia, Cherokee, Canadian Aboriginals etc. The scripts of South Asia, SE Asia, Cherokee, Canadian Aboriginals etc. deserve equal status as English. These scripts are used by billions of people. Claiming that "The only sense in which one can perhaps claim that UTF-8 is Anglo-centric, is that it uses 1 byte for English letters vs. 3 bytes for CJK" ignores the importance of scripts used by billions of humans. It is a factually wrong statement, and not just a case of using a bad example. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436499] New: PC becomes unusable when dragging window and moving it across virtual desktops
https://bugs.kde.org/show_bug.cgi?id=436499 Bug ID: 436499 Summary: PC becomes unusable when dragging window and moving it across virtual desktops Product: kwin Version: 5.21.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: t...@tfld.dev Target Milestone: --- SUMMARY If you are dragging a window with the mouse, and simultaneously move it to a different virtual desktop using a shortcut, the mouse becomes unusable and you cannot focus any other window. STEPS TO REPRODUCE 1. Add a shortcut for "Move window to next virtual desktop". 2. Drag a window with the mouse. 3. Simultaneously use that shortcut. OBSERVED RESULT It is no longer possible to use the mouse, the cursor remains the "move window" cursor. It is also no longer possible to focus any other window. The window itself also no longer responds. EXPECTED RESULT The desktop should remain usable. This is the case if doing the same but using the "Change to next virtual desktop" shortcut. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.11.16-arch1-1 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION The exact names for the shortcuts may be wrong, since I'm using KDE in German. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414111] Krita startup takes very long depending on size of files in recent files list
https://bugs.kde.org/show_bug.cgi?id=414111 --- Comment #10 from Felipe Lema --- Created merge request for a fix https://invent.kde.org/graphics/krita/-/merge_requests/830 -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 436498] New: WindowSystem::window(WId wid) returns the wrong window
https://bugs.kde.org/show_bug.cgi?id=436498
Bug ID: 436498
Summary: WindowSystem::window(WId wid) returns the wrong window
Product: kwayland-integration
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: fab...@ritter-vogt.de
Target Milestone: ---
It does this:
const auto =
WaylandIntegration::self()->plasmaWindowManagement()->windows();
auto it = std::find_if(windows.begin(), windows.end(), [wid] (PlasmaWindow
*w) { return w->internalId() == wid; } );
wid is the internally generated window id in the client process, while
internalId() returns the internally generated window id from the compositor.
Those do not match, which essentially means that any KWindowSystem functions on
wayland which take a WId act on a random window instead.
krunner for instance calls KWindowSystem::forceActiveWindow(winId()); after the
window is shown, but actually activates the desktop (plasmashell) instead.
krunner's View is the first QWaylandWindow instance and gets winId 1, while
plasmashell is the first window created by kwayland-server.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 436497] Fedora 34 KDE Wayland is not usable - no multi-monitor detection, 1024x768 resolution only for eDP1 on Dell Precision 5540
https://bugs.kde.org/show_bug.cgi?id=436497 --- Comment #2 from Arcadiy Ivanov --- Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1955961 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436497] Fedora 34 KDE Wayland is not usable - no multi-monitor detection, 1024x768 resolution only for eDP1 on Dell Precision 5540
https://bugs.kde.org/show_bug.cgi?id=436497 --- Comment #1 from Arcadiy Ivanov --- Created attachment 138095 --> https://bugs.kde.org/attachment.cgi?id=138095=edit F34 KDE on Wayland Plasma -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436497] New: Fedora 34 KDE Wayland is not usable - no multi-monitor detection, 1024x768 resolution only for eDP1 on Dell Precision 5540
https://bugs.kde.org/show_bug.cgi?id=436497 Bug ID: 436497 Summary: Fedora 34 KDE Wayland is not usable - no multi-monitor detection, 1024x768 resolution only for eDP1 on Dell Precision 5540 Product: kwin Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: arca...@ivanov.biz Target Milestone: --- Created attachment 138094 --> https://bugs.kde.org/attachment.cgi?id=138094=edit F34 KDE on X11 Plasma Operating System: Fedora 34 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.16-300.fc34.x86_64 OS Type: 64-bit Graphics Platform: Wayland Processors: 16 × Intel® Core™ i9-9980HK CPU @ 2.40GHz Memory: 62.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 KDE X11 Plasma session works in F34 as well as F33. Login into Wayland session, there is no multi-monitor detection, primary monitor is detected as "manufacturer_TODO" at 1024x768 only. The Wayland session is, basically, useless. Screens are attached. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 436496] New: Hyperlinks not highlighted/underlined
https://bugs.kde.org/show_bug.cgi?id=436496
Bug ID: 436496
Summary: Hyperlinks not highlighted/underlined
Product: Falkon
Version: 3.1.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: now...@gmail.com
Reporter: walt.tuv...@gmail.com
Target Milestone: ---
Created attachment 138093
--> https://bugs.kde.org/attachment.cgi?id=138093=edit
Screenshot of bug
SUMMARY
Hyperlinks aren't highlighted/underlined, at least not on my website.
STEPS TO REPRODUCE
1. Visit, for example
https://readingma.us/GovtZone/SchoolCommittee/Main/CapHillIncident/Emails.
OBSERVED RESULT
Notice that there are lots of hyperlinks, which can be observed by
mouse-hovering. But they're not underlined, as they should be. But regular
(non-hyperlink) underlines do appear. See attached screenshot.
main#content div.content /*article div.node__content*/ a
{text-decoration:none;}
main#content div.content /*article div.node__content*/ a:link
{text-decoration:underline solid 12.5% var(--celtsBeige);}
main#content div.content /*article div.node__content*/ a:hover
{background-color:var(--celtsBeigePreHover);}
main#content div.content /*article div.node__content*/ a:visited
{text-decoration:underline solid 12.5% var(--bruinsGold);}
main#content div.content /*article div.node__content*/ a:visited:hover
{background-color:var(--bruinsGoldPreHover);}
(where Bruins Gold=#FFB81C, Celts Beige=#E59E6D, Boston team colors)
EXPECTED RESULT
Try any other browser, they're underlined.
SOFTWARE/OS VERSIONS
Fedora 34, installed a couple days ago, all up-to-date.
Plasma/X11
Application version 3.1.0
QtWebEngine version 5.15.2
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
Falkon/3.1.0 Chrome/83.0.4103.122 Safari/537.36
ADDITIONAL INFORMATION
I looked for a setting in Preferences but couldn't find.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 436331] Kate 21.04 from Binary Factory stable build crash at launch
https://bugs.kde.org/show_bug.cgi?id=436331 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Christoph Cullmann --- Could you try this build: https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/1264/ I patched some stuff in KTextEditor that did cause crashs for me. Now at least here I no longer have such startup or document close/quit crashs. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436220] Typo in Session tab of configure kate
https://bugs.kde.org/show_bug.cgi?id=436220 Christoph Cullmann changed: What|Removed |Added Version Fixed In||21.04.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- This seems to be fixed in the current master development branch and 21.04 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 436434] UI problems and legibility
https://bugs.kde.org/show_bug.cgi?id=436434 --- Comment #3 from medin --- Created attachment 138092 --> https://bugs.kde.org/attachment.cgi?id=138092=edit Hidden date -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 436434] UI problems and legibility
https://bugs.kde.org/show_bug.cgi?id=436434 --- Comment #2 from medin --- (In reply to David Jarvie from comment #1) > A fix has been implemented to show the color for selected alarms (commit > 093949ddb6a037e27813493c7ad86e74bfcc14b1 in 21.04 branch). This will be in > KDE apps release 21.04.1. > > On my system, selected alarms' dates are not hidden. On your system, is the > date ALWAYS hidden when you select an alarm, or does it only happen for some > alarms? If it only happens for some alarms, can you please give some example > dates for alarms whose dates are hidden? It happens with only alarms that have single digit in hour. See attached video for more info. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436495] New: OpenGL Rendering backend crashes KWin
https://bugs.kde.org/show_bug.cgi?id=436495 Bug ID: 436495 Summary: OpenGL Rendering backend crashes KWin Product: kwin Version: 5.21.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: vladma...@gmail.com Target Milestone: --- Application: kwin_x11 (5.21.4) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.10.33-1-lts x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: Arch Linux -- Information about the crash: This just happened out of nowhere, everything worked fine yesterday, I didn't even update anything. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x in () #5 0x7fdca585d9d3 in KWin::SceneOpenGL::createScene(QObject*) () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #6 0x7fdca586d81e in KWin::OpenGLFactory::create(QObject*) const () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #7 0x7fdcd0041973 in KWin::Compositor::setupStart() () at /usr/lib/libkwin.so.5 #8 0x7fdcd0044d8a in KWin::X11Compositor::start() () at /usr/lib/libkwin.so.5 #9 0x7fdcd0043817 in KWin::Compositor::reinitialize() () at /usr/lib/libkwin.so.5 #10 0x7fdcd0044665 in KWin::X11Compositor::reinitialize() () at /usr/lib/libkwin.so.5 #11 0x7fdcd0058819 in KWin::CompositorDBusInterface::reinitialize() () at /usr/lib/libkwin.so.5 #12 0x7fdccffd76e4 in KWin::CompositorDBusInterface::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib/libkwin.so.5 #13 0x7fdccffd79b1 in KWin::CompositorDBusInterface::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libkwin.so.5 #14 0x7fdccd40e066 in () at /usr/lib/libQt5DBus.so.5 #15 0x7fdccd179352 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7fdcce34a762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x55b83e54585d in KWin::ApplicationX11::notify(QObject*, QEvent*) () #18 0x7fdccd14c84a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7fdccd14f343 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #20 0x7fdccd1a27ac in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #21 0x7fdcc56bc56f in () at /usr/lib/libQt5XcbQpa.so.5 #22 0x7fdccd14b1ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #23 0x7fdccd153664 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #24 0x55b83e547069 in main () [Inferior 1 (process 54725) detached] The reporter indicates this bug may be a duplicate of or related to bug 432570. Possible duplicates by query: bug 432570, bug 432496, bug 431863, bug 431529, bug 429383. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433516] Kate exits when click on 'Configure Kate...'
https://bugs.kde.org/show_bug.cgi?id=433516 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED CC||cullm...@kde.org Resolution|--- |WORKSFORME --- Comment #1 from Christoph Cullmann --- Sorry that this crashes for you. Could you try a new build, e.g. from https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/ That works for me, I will update the Windows Store version to a fresh build in the next days, too. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 426093] Crash when trying to open some about dialogs
https://bugs.kde.org/show_bug.cgi?id=426093 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED CC||cullm...@kde.org Resolution|--- |WORKSFORME --- Comment #1 from Christoph Cullmann --- I tried this with the latest build https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/ 21.04 Works for me, but on Windows 10. Please try out some recent version, too, thanks! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436301] Embedded Libreoffice files are not shown as embedded files in the File menu.
https://bugs.kde.org/show_bug.cgi?id=436301 --- Comment #4 from Albert Astals Cid --- As far as I can see there's no attachment in that file. What makes you think there is one? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436494] New: Displays double after browsing samba shares
https://bugs.kde.org/show_bug.cgi?id=436494 Bug ID: 436494 Summary: Displays double after browsing samba shares Product: dolphin Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: woodguy552...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.11.15-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: - Unusual behavior I noticed: After browsing samba share on local wired network all file folders are displayed double then it crashes when changing to local file system. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f15b259d9bc in KFileItem::~KFileItem() () from /lib64/libKF5KIOCore.so.5 #5 0x7f15b2b36a2f in KFileItemModel::~KFileItemModel() () from /lib64/libdolphinprivate.so.5 #6 0x7f15b2b36dcd in KFileItemModel::~KFileItemModel() () from /lib64/libdolphinprivate.so.5 #7 0x7f15b0cff93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #8 0x7f15b0d052ef in QObject::~QObject() () from /lib64/libQt5Core.so.5 #9 0x7f15b2b4f95b in KItemListContainer::~KItemListContainer() () from /lib64/libdolphinprivate.so.5 #10 0x7f15b2b4f9ad in KItemListContainer::~KItemListContainer() () from /lib64/libdolphinprivate.so.5 #11 0x7f15b0cff93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #12 0x7f15b186d246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #13 0x7f15b2b929fd in DolphinView::~DolphinView() () from /lib64/libdolphinprivate.so.5 #14 0x7f15b0cff93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #15 0x7f15b186d246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #16 0x7f15b2e2897d in DolphinViewContainer::~DolphinViewContainer() () from /lib64/libkdeinit5_dolphin.so #17 0x7f15b0cff93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #18 0x7f15b186d246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #19 0x7f15b19da07d in QSplitter::~QSplitter() () from /lib64/libQt5Widgets.so.5 #20 0x7f15b0cff93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #21 0x7f15b186d246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #22 0x7f15b2e7111f in DolphinTabPage::~DolphinTabPage() [clone .lto_priv.0] () from /lib64/libkdeinit5_dolphin.so #23 0x7f15b0cff93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #24 0x7f15b186d246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #25 0x7f15b19def6d in QStackedWidget::~QStackedWidget() () from /lib64/libQt5Widgets.so.5 #26 0x7f15b0cff93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #27 0x7f15b186d246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #28 0x7f15b2e71380 in DolphinTabWidget::~DolphinTabWidget() [clone .lto_priv.0] () from /lib64/libkdeinit5_dolphin.so #29 0x7f15b0cff93a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #30 0x7f15b186d246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #31 0x7f15b2e186bc in DolphinMainWindow::~DolphinMainWindow() () from /lib64/libkdeinit5_dolphin.so #32 0x7f15b0cffb21 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #33 0x7f15b232781d in KXmlGuiWindow::event(QEvent*) () from /lib64/libKF5XmlGui.so.5 #34 0x7f15b1830ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #35 0x7f15b0cd7bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #36 0x7f15b0cda8c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #37 0x7f15b0d24c27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #38 0x7f15aec7fa9f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #39 0x7f15aecd1a98 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #40 0x7f15aec7ce73 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #41 0x7f15b0d246f3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #42 0x7f15b0cd657b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #43 0x7f15b0cde1b4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #44 0x7f15b2e17d5e in kdemain () from /lib64/libkdeinit5_dolphin.so #45 0x7f15b2c1d1e2 in __libc_start_main () from /lib64/libc.so.6 #46 0x555bcac460ae in _start () [Inferior 1
[Breeze] [Bug 395010] If scroll up/down buttons are visible, always show them in the scrollbar gutter
https://bugs.kde.org/show_bug.cgi?id=395010 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/breeze/-/merge_requests/99 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435258] Sometimes kwin_wayland crashes in QtWaylandServer::org_kde_kwin_blur_manager::bind_func() when I change global theme
https://bugs.kde.org/show_bug.cgi?id=435258 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/931 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 436493] New: Some pages on pageStack still remain visible and active after having been popped or cleared
https://bugs.kde.org/show_bug.cgi?id=436493 Bug ID: 436493 Summary: Some pages on pageStack still remain visible and active after having been popped or cleared Product: frameworks-kirigami Version: 5.81.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: b...@mogwai.be Target Milestone: Not decided Created attachment 138091 --> https://bugs.kde.org/attachment.cgi?id=138091=edit Minimal qml file to reproduce pageStack issue SUMMARY Under certain circumstances pages on the pageStack of a ApplicationWindow remain visible and active after they have been popped or cleared. STEPS TO REPRODUCE 1. Open the attached qml file (qml pagestack-bug.qml). 2. You should now see 3 ScrollablePages on the pageStack (red, green and yellow). 3. From the globaldrawer, select "Blue page". This will clear the pageStack, push a blue page and then add a large bottomMargin. 4. Observer that the green page is still fully visible and active in the background (through the bottom margin of the blue page). OBSERVED RESULT Popped pages which were on the pageStack are still visible and active behind the new pages. EXPECTED RESULT Pages not being active or visible anymore after they have been popped or cleared. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 436434] UI problems and legibility
https://bugs.kde.org/show_bug.cgi?id=436434 David Jarvie changed: What|Removed |Added Latest Commit||093949ddb6a037e27813493c7ad ||86e74bfcc14b1 --- Comment #1 from David Jarvie --- A fix has been implemented to show the color for selected alarms (commit 093949ddb6a037e27813493c7ad86e74bfcc14b1 in 21.04 branch). This will be in KDE apps release 21.04.1. On my system, selected alarms' dates are not hidden. On your system, is the date ALWAYS hidden when you select an alarm, or does it only happen for some alarms? If it only happens for some alarms, can you please give some example dates for alarms whose dates are hidden? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436487] IPTC:ObjectAttributeReference and XMP:IntellectualGenre
https://bugs.kde.org/show_bug.cgi?id=436487 --- Comment #4 from Maik Qualmann --- Git commit f261bd748ce1c91be1f2c7d5efea6667d24e44e1 by Maik Qualmann. Committed on 02/05/2021 at 17:10. Pushed by mqualmann into branch 'master'. add genre text when edit field is empty M +13 -2 core/dplugins/generic/metadata/metadataedit/dialog/objectattributesedit.cpp M +12 -1 core/dplugins/generic/metadata/metadataedit/xmp/xmpproperties.cpp https://invent.kde.org/graphics/digikam/commit/f261bd748ce1c91be1f2c7d5efea6667d24e44e1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436472] Dolphin (and rest of session) Crash under Wayland when disconnecting Secondary display
https://bugs.kde.org/show_bug.cgi?id=436472 Méven Car changed: What|Removed |Added Version|unspecified |5.21.4 Product|kde |kwin Component|general |platform-wayland Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org --- Comment #1 from Méven Car --- Thank you for those details regarding your screen setup, this is quite helpful. Plasma 5.22 may already have a fix for this. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 436472] Dolphin (and rest of session) Crash under Wayland when disconnecting Secondary display
https://bugs.kde.org/show_bug.cgi?id=436472 Méven Car changed: What|Removed |Added Keywords||wayland CC||meve...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436473] Cursor is stuck to resize icon when hovering into panels across the movable dividers
https://bugs.kde.org/show_bug.cgi?id=436473 Méven Car changed: What|Removed |Added CC||meve...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Méven Car --- I don't understand what `Cross the cursor across the movable dividers into any panel.` means. By "cross across" do you mean move over, or drag ? Could you explain what path your cursor did from which border and components, clicks you did, and the setup you have most notably the panels displayed. In other words Can you describe more precisely how to reproduce this ? -- You are receiving this mail because: You are watching all bug changes.
