[kded-appmenu] [Bug 421645] New: Global Menu widget disappears when dragged to second monitor, impossible to remove
https://bugs.kde.org/show_bug.cgi?id=421645 Bug ID: 421645 Summary: Global Menu widget disappears when dragged to second monitor, impossible to remove Product: kded-appmenu Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: top menubar Assignee: plasma-b...@kde.org Reporter: d...@angelhill.net Target Milestone: --- Created attachment 128528 --> https://bugs.kde.org/attachment.cgi?id=128528&action=edit Screenshot of the widget about to be dragged to second monitor SUMMARY STEPS TO REPRODUCE 1. Add a Global Menu widget 2. Drag it to the edge of the monitor where it appears OBSERVED RESULT The widget disappears completely and becomes impossible to remove until the application bar is killed or session restarted, at which point the menu widget appears somewhere on the target monitor. EXPECTED RESULT The widget should appear on the target monitor immediately and not after a restart. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION This may seem similar to #420418, but it's a different situation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420418] Global menu disappesrs when application moved to second monitor
https://bugs.kde.org/show_bug.cgi?id=420418 Dimo changed: What|Removed |Added CC||d...@angelhill.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421645] Global Menu widget disappears when dragged to second monitor, impossible to remove
https://bugs.kde.org/show_bug.cgi?id=421645 Dimo changed: What|Removed |Added Assignee|plasma-b...@kde.org |k...@privat.broulik.de CC||mvourla...@gmail.com, ||plasma-b...@kde.org Target Milestone|--- |1.0 Component|top menubar |Global Menu Product|kded-appmenu|plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395170] New: Sharpen filter causes a crash when video file is named "9-15.avi"
https://bugs.kde.org/show_bug.cgi?id=395170 Bug ID: 395170 Summary: Sharpen filter causes a crash when video file is named "9-15.avi" Product: kdenlive Version: 18.04.1 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: doftor.liv...@gmail.com Target Milestone: --- Created attachment 113165 --> https://bugs.kde.org/attachment.cgi?id=113165&action=edit A zip file containing the troublesome video, and a core dump The attached video "9-15.avi" causes a crash when Sharpen filter is applied. Steps to reproduce: - Add the video to a project (any project settings are fine) - Drag it to the timeline at the bottom - Add sharpen filter to it - either by right-clicking on the clip and selecting it with the mouse, or by searching in the filters list and dragging it to the list of filters. At the last step Kdenlive freezes for a moment then it terminates. Renaming the video file fixes the problem. In the terminal, I get the following errors: QXcbConnection: XCB error: 8 (BadMatch), sequence: 21905, resource id: 2097494, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 21937, resource id: 2097494, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 21940, resource id: 2097494, major code: 130 (Unknown), minor code: 3 Segmentation fault (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395170] Sharpen filter causes a crash when video file is named "9-15.avi"
https://bugs.kde.org/show_bug.cgi?id=395170 --- Comment #1 from Dimo --- Update on the bug. Renaming the file only helps if this is the only file in a project. Otherwise, Kdenlive still crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420418] Global menu disappesrs when application moved to second monitor
https://bugs.kde.org/show_bug.cgi?id=420418 --- Comment #6 from Dimo Fedortchenko --- I can understand the dilemma, but technically only 1 application can ever be active at one time, even with multiple displays, and global menu is supposed to display the active application, so shouldn't that mean that it respects any running application even if it's on another screen? If you look at how for example Apple does it in macos, which is what I suspect Global Menu is an attempt at replicating, the top menu bar (and it's "global menu") in macos always shows the menu for the active application no matter what screen it's on. As for the workaround, forcing the creation of additional panels on secondary screens is not a good solution because it means you have to spend time setting up your secondary monitors, adds complexity to a setup, and can cause other unintended side effects. If you happen to unplug an external monitor with a global menu panel on it, the panel and thus the global menu still lives somewhere in the void and you can then never remove that widget without hacking the KDE configuration! If you replug the same monitor you will in most cases see the panel again, but if kde does not recognise the monitor for some reason or if your monitor breaks, you're screwed - i had this issue before where I lost panels with global menu widgets on them in the void and had to hack the config files. So my suggestion would be to just emulate the macos solution, since I guess that's the basis for global menu anyway. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Dimo Fedortchenko changed: What|Removed |Added CC||d...@angelhill.net --- Comment #52 from Dimo Fedortchenko --- I still have this issue in KDE 5.22.3, but I have discovered a very interesting "workaround" that completely solves the issue. In the KRunner settings, if I change the Krunner Position on Screen to "top", it takes at least 3-5 seconds to open up no matter the enabled plugins. However, changing it to "Center" opens Krunner immediately even with a bunch of plugins. I have a Ryzen 9 3900x running in this case Fedora 34 (slowness has been around since I started in Fedora 31). However, on my machine I have discovered that my plasma bar is also very slow, like clicking the Volume icon is extremely slow and laggy, and my plasma bar is at the top of the screen, not sure if the slowness of the plasma bar causes krunner to also be slow when it opens at the top (where the plasma bar is). Or maybe it's completely unrelated, but in any case, if you're having KRunner open slowly, try to change it's placement to the Center of the screen, it solved the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358874] New: System Settings crashing on exit
https://bugs.kde.org/show_bug.cgi?id=358874 Bug ID: 358874 Summary: System Settings crashing on exit Product: systemsettings Version: unspecified Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: drgrigo...@gmail.com Application: systemsettings (4.11.22) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.4.0-smp i686 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: I changed default manager from Konqueror to Dolphin, saved and changed back. After I closed the settings it crashed. I think similar crash have happened in the recent past. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [KCrash Handler] #6 0x0805cb40 in QString::shared_null () #7 0x in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /usr/lib/qt/lib/libQtCore.so.4 #8 0x in KParts::PartManager::~PartManager() () at /usr/lib/libkparts.so.4 #9 0x in KParts::PartManager::~PartManager() () at /usr/lib/libkparts.so.4 #10 0x in QObjectPrivate::deleteChildren() () at /usr/lib/qt/lib/libQtCore.so.4 #11 0x in QObject::~QObject() () at /usr/lib/qt/lib/libQtCore.so.4 #12 0x in KParts::Part::~Part() () at /usr/lib/libkparts.so.4 #13 0x in KParts::ReadOnlyPart::~ReadOnlyPart() () at /usr/lib/libkparts.so.4 #14 0x in KHTMLPart::~KHTMLPart() () at /usr/lib/libkhtml.so.5 #15 0x in KHTMLPart::~KHTMLPart() () at /usr/lib/libkhtml.so.5 #16 0x in qDeleteInEventHandler(QObject*) () at /usr/lib/qt/lib/libQtCore.so.4 #17 0x in QObject::event(QEvent*) () at /usr/lib/qt/lib/libQtCore.so.4 #18 0x in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/qt/lib/libQtGui.so.4 #19 0x in QApplication::notify(QObject*, QEvent*) () at /usr/lib/qt/lib/libQtGui.so.4 #20 0x in KApplication::notify(QObject*, QEvent*) () at /usr/lib/libkdeui.so.5 #21 0x in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/qt/lib/libQtCore.so.4 #22 0x in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/qt/lib/libQtCore.so.4 #23 0x in QCoreApplication::sendPostedEvents(QObject*, int) () at /usr/lib/qt/lib/libQtCore.so.4 #24 0x in QCoreApplication::exec() () at /usr/lib/qt/lib/libQtCore.so.4 #25 0x in QApplication::exec() () at /usr/lib/qt/lib/libQtGui.so.4 #26 0x0805097e in () #27 0x in __libc_start_main () at /lib/libc.so.6 #28 0x08050a76 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
