[plasmashell] [Bug 432551] New: Plasma crash after fiddling with (frozen) System Monitor widget settings
https://bugs.kde.org/show_bug.cgi?id=432551 Bug ID: 432551 Summary: Plasma crash after fiddling with (frozen) System Monitor widget settings Product: plasmashell Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugs.kde@tenkate.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-41-lowlatency x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: As mentioned before - fiddling with System Monitor widget settings since it stopped updating info. Then Plasma crashed. - Unusual behavior I noticed: See above - System Monitor widget info 'froze', i.e. memory usage stays at 64.3% regardless of *real* memory usage. This is the second time I noticed this behaviour, which was gone for a brief moment when I rebooted the system. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f32410b1b8e in QQmlData::wasDeleted(QObject const*) (object=0x55d539e512d0) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338 #5 QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (engine=engine@entry=0x55d539c32d30, qmlContext=qmlContext@entry=0x55d53fa5ce60, object=0x55d539e512d0, name=0x7f32331b1720, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7ffc833f32d8, property=0x7ffc833f32e0) at jsruntime/qv4qobjectwrapper.cpp:360 #6 0x7f3241091f0a in QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*, QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) (resource=, id=..., receiver=, hasProperty=0x7ffc833f3357, base=0x7f32331b16f8, lookup=0x0) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #7 0x7f32410927e3 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) (l=0x55d53c3bab30, engine=0x55d539c32d30, base=0x7f32331b16f8) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #8 0x7f32410e20f9 in QV4::Runtime::CallQmlContextPropertyLookup::call(QV4::ExecutionEngine*, unsigned int, QV4::Value*, int) (engine=0x55d539c32d30, index=, argv=0x7f32331b16a8, argc=4) at jsruntime/qv4scopedvalue_p.h:238 #9 0x7f32410cecf3 in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) (frame=0x7ffc833f3590, engine=0x55d539c32d30, code=0x7f31d3c3e28b "H\020\022\071\030\n\022=\030\v\022>\030\f\260\b\003\n\030\006\002P") at jsruntime/qv4vme_moth.cpp:784 #10 0x7f32410d30b7 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (frame=frame@entry=0x7ffc833f3590, engine=engine@entry=0x55d539c32d30) at jsruntime/qv4vme_moth.cpp:463 #11 0x7f324107008d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) (this=this@entry=0x55d53bf5b700, thisObject=, argv=argv@entry=0x7f32331b1658, argc=, context=) at jsruntime/qv4function.cpp:69 #12 0x7f32411d6a15 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) (this=this@entry=0x55d541152b20, callData=0x7f32331b1628, isUndefined=isUndefined@entry=0x7ffc833f376f) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #13 0x7f32411dbdb8 in QQmlBinding::evaluate(bool*) (this=this@entry=0x55d541152b20, isUndefined=isUndefined@entry=0x7ffc833f376f) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #14 0x7f32411dfcfb in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x55d541152b20, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:246 #15 0x7f32411dda14 in QQmlBinding::update(QFlags) (this=0x55d541152b20, flags=...) at qml/qqmlbinding.cpp:186 #16 0x7f32411bc67d in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=0x0) at qml/qqmlnotifier.cpp:104 #17 0x7f323fb0be75 in doActivate(QObject*, int, void**) (sender=0x55d53c06b0b0, signal_index=21, argv=0x0) at kernel/qobject_p.h:110 #18 0x7f324116e022 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:375 #19 0x7f32411df51e in QQmlPropertyData::writeProperty(QObject*, void*, Q
[neon] [Bug 438390] Regression: Installation fails on BTRFS
https://bugs.kde.org/show_bug.cgi?id=438390 --- Comment #4 from iGadget --- Upstream bug report: https://github.com/calamares/calamares/issues/1682 This mentions a possible workaround: 1.Download https://github.com/calamares/calamares/blob/calamares/src/modules/mount/mount.conf 2. Copy the file to the /calamares/desktop/modules/ on live cd before start calamares 3. Start calamares and start installation Also, this issue has apparently already been reported before. Marking as duplicate. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438390] Regression: Installation fails on BTRFS
https://bugs.kde.org/show_bug.cgi?id=438390 iGadget changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from iGadget --- *** This bug has been marked as a duplicate of bug 436005 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436005] Kde neon Not installed on Btrfs
https://bugs.kde.org/show_bug.cgi?id=436005 iGadget changed: What|Removed |Added CC||bugs.kde@tenkate.net --- Comment #6 from iGadget --- *** Bug 438390 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436005] Kde neon Not installed on Btrfs
https://bugs.kde.org/show_bug.cgi?id=436005 --- Comment #7 from iGadget --- So, if a workaround / fix is available, why isn't it included in the Neon live images? Seems trivial to me: 1. Download https://github.com/calamares/calamares/blob/calamares/src/modules/mount/mount.conf 2. Replace existing /calamares/desktop/modules/mount.conf on Live image Done. What's the holdup? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438609] New: panes not updating correctly when externally invoked
https://bugs.kde.org/show_bug.cgi?id=438609 Bug ID: 438609 Summary: panes not updating correctly when externally invoked Product: systemsettings Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugs.kde@tenkate.net Target Milestone: --- Created attachment 139305 --> https://bugs.kde.org/attachment.cgi?id=139305&action=edit screenshot of the issue in its full glory SUMMARY Settings panes are not updated correctly when externally invoked while System Settings is already open and displaying a different item then the one being invoked. STEPS TO REPRODUCE 1. Open System Settings 2. Navigate to an entry which contains sub-entries (i.e. Workspace Behavior) 3. Open Application Launcher 4. Search for another Settings item (i.e. users) and launch it OBSERVED RESULT 'Manage Users' is displayed, but with the 'Workspace Behavior' pane still opened on the left. EXPECTED RESULT Since 'Manage Users' is not a sub-entry of 'Workspace Behavior', I expect System Settings to close the pane and display 'Users' instead. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon User Edition (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438609] panes not updating correctly when externally invoked
https://bugs.kde.org/show_bug.cgi?id=438609 iGadget changed: What|Removed |Added CC||bugs.kde@tenkate.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438391] HWE kernel missing
https://bugs.kde.org/show_bug.cgi?id=438391 --- Comment #3 from iGadget --- (In reply to Jonathan Riddell from comment #2) > Unstable image now uses HWE linux 5.8, please test to confirm > https://files.kde.org/neon/images/unstable/20210615-1355/ Awesome Jonathan, thanks. Just tested with the image in your link, Neon Live USB now boots fine on my Ryzen 4500U laptop. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436005] Kde neon Not installed on Btrfs
https://bugs.kde.org/show_bug.cgi?id=436005 --- Comment #8 from iGadget --- Wanting to help move this forward, I tried creating a merge request, only to find out that's already been done on May 11: https://invent.kde.org/neon/neon/calamares-settings/-/merge_requests/1 Please merge and get this bug fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477034] New: Crashed when resuming from suspend, with power cycle on external display
https://bugs.kde.org/show_bug.cgi?id=477034 Bug ID: 477034 Summary: Crashed when resuming from suspend, with power cycle on external display Classification: Plasma Product: plasmashell Version: 5.24.7 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugs.kde@tenkate.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 6.5.6-76060506-generic x86_64 Windowing System: Wayland Distribution: Pop!_OS 22.04 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Resumed my workstation from suspend, but before I got the login / lock screen I accidentaly switched off the power to my external display connected via DP. Turned the power to my external display back on and got a grey screen (Pop!_OS theme) with a frozen mouse cursor. Switched to another VT (CTRL+Alt+F2 / F3) and got a new login screen. After logging in, my session was resumed and I got the notification of the crash. - Unusual behavior I noticed: No login / lock screen appeared after resuming from suspend, but instead only a grey screen with a frozen mouse cursor. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f1eb6a7d275 in QQuickWindow::mouseGrabberItem() const () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f1eb6a7faef in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1eb6a67195 in QQuickItemPrivate::derefWindow() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f1eb6a67d58 in QQuickItem::setParentItem(QQuickItem*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f1eb6a6801a in QQuickItem::~QQuickItem() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f1eaf2e9abd in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #10 0x7f1eb4ee71c3 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f1eb5b6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f1eb4eb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1eb4ebcf27 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f1eb4f13a67 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f1eb3520d3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f1eb3576258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f1eb351e3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f1eb4f130b8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f1eb4eb875b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f1eb4ec0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x560b21ae8dce in () #22 0x7f1eb4429d90 in __libc_start_call_main (main=main@entry=0x560b21ae7f70, argc=argc@entry=1, argv=argv@entry=0x7fff9ab8bef8) at ../sysdeps/nptl/libc_start_call_main.h:58 #23 0x7f1eb4429e40 in __libc_start_main_impl (main=0x560b21ae7f70, argc=1, argv=0x7fff9ab8bef8, init=, fini=, rtld_fini=, stack_end=0x7fff9ab8bee8) at ../csu/libc-start.c:392 #24 0x560b21ae8ef5 in () [Inferior 1 (process 4132) detached] The reporter indicates this bug may be a duplicate of or related to bug 461077, bug 449856. Possible duplicates by query: bug 476072, bug 476043, bug 474335, bug 470861, bug 468952. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431795] New: Crashes when activating hot corner (kwin 5.19.5)
https://bugs.kde.org/show_bug.cgi?id=431795 Bug ID: 431795 Summary: Crashes when activating hot corner (kwin 5.19.5) Product: kwin Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bugs.kde@tenkate.net Target Milestone: --- Application: kwin_x11 (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-38-lowlatency x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: Activated hot corner (located in the lower left corner by default on Ubuntu Studio 20.10). Note: Supposedly this bug was fixed in 5.18.6, but I'm running 5.19.5 and I'm still experiencing the issue. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7f392ee104ee in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () at /lib/x86_64-linux-gnu/libkwin.so.5 #5 0x7f392da884ef in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=, eventType=..., message=message@entry=0x7f392002e780, result=result@entry=0x7fff47b1a3e8) at kernel/qabstracteventdispatcher.cpp:488 #6 0x7f39277db505 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x5561c013a7d0, event=event@entry=0x7f392002e780) at qxcbnativeinterface.h:101 #7 0x7f39277dca46 in QXcbConnection::processXcbEvents(QFlags) (this=0x5561c013a7d0, flags=...) at qxcbconnection.cpp:1029 #8 0x7f39277ff740 in QXcbUnixEventDispatcher::processEvents(QFlags) (this=0x5561c0197020, flags=...) at qxcbeventdispatcher.cpp:61 #9 0x7f392da89a4b in QEventLoop::exec(QFlags) (this=this@entry=0x7fff47b1a530, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #10 0x7f392da91fc6 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #11 0x5561bf01ca6d in () #12 0x7f392d411cb2 in __libc_start_main (main=0x5561bf01c6a0, argc=1, argv=0x7fff47b1a7b8, init=, fini=, rtld_fini=, stack_end=0x7fff47b1a7a8) at ../csu/libc-start.c:314 #13 0x5561bf01cf8e in _start () [Inferior 1 (process 2246) detached] The reporter indicates this bug may be a duplicate of or related to bug 423319. Possible duplicates by query: bug 431564, bug 430945, bug 430328, bug 430197, bug 430180. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438390] New: Regression: Installation fails on BTRFS
https://bugs.kde.org/show_bug.cgi?id=438390 Bug ID: 438390 Summary: Regression: Installation fails on BTRFS Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: bugs.kde@tenkate.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY As per https://www.reddit.com/r/kdeneon/comments/nw6y94/neon_installation_clusterf/ - The Calamares installer does not seem to work with BTRFS on the latest Neon ISOs. STEPS TO REPRODUCE 1. Run installer on Neon Live ISO 2. When reaching 'Partitions', choose 'Manual partitioning' 3. Select an existing partition (though this might be caused with a new partition as well), click 'Edit' 4. Click 'Format' 5. Choose BTRFS as filesystem 6. Select '/' as mount point and click 'OK' 7. Select your EFI partition, click 'Edit', keep the content and set '/boot/efi' as mount point, flags 'boot'. 8. Continue installation OBSERVED RESULT When Grub is being configured / installed, I get this error: 8< Installation Failed Boost.Python error in job "bootloader" Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=neon --force' returned non-zero status exit 1. Installing for x86_64-efi platform. grub-install: error: cannot find a device for /boot/grub (is /dev mounted?). Traceback: File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py, line 477, in run prepare_bootloader(fw_type) File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py, line 449, in prepare_bootloader install(efi_directory, fw_type) File ", line 5, in 8< Also, when mounting the target BTRFS partition, it is empty. Instead, the system appears to be 'installed' into /tmp. EXPECTED RESULT The Neon installer should work fine with BTRFS (and it has in the past, so this is a regression!) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon Live USB (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I used neon-user-20210527-0944.iso, but previous versions apparently have this regression as well. As per the comments on the linked Reddit thread, 'older' images do not seem to have this issue, but I don't know which version(s) exactly. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438391] New: HWE kernel missing
https://bugs.kde.org/show_bug.cgi?id=438391 Bug ID: 438391 Summary: HWE kernel missing Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: bugs.kde@tenkate.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Even though the HWE kernel is shipping by default for months now with the Ubuntu 20.04 ISO's, neon-user-20210527-0944.iso *still* ships with 5.4. This makes the installation on newer hardware (i.e. Ryzen 4600U) a pain since the user then has to boot the installer in safe graphics mode, install the system, manually install the HWE kernel AND then manually remove safe graphics mode since it's persistent. STEPS TO REPRODUCE 1. Boot KDE Neon ISO on any (graphics) hardware not supported by kernel 5.4 (i.e. Ryzen 4600U) 2. Observe failing to boot into graphics mode 3. Reboot KDE Neon ISO, now choosing 'safe graphics' OBSERVED RESULT System boots, but with quirks (i.e. I constantly get the 'Switch to external screen'-popup). Safe graphics mode persists after installation, with no easy way for the user to a) Install the HWE kernel b) Undo safe graphics mode EXPECTED RESULT Neon ships with HWE kernel as soon as it becomes available OR (perhaps more future-proof) The user is prompted post-install by a nice 'wizard' to install the HWE kernel and undo safe graphics mode. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon (available in About System) KDE Plasma Version: 5.21 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION https://www.reddit.com/r/kdeneon/comments/nggslr/kernel_58_by_default_when/ -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438391] HWE kernel missing
https://bugs.kde.org/show_bug.cgi?id=438391 --- Comment #1 from iGadget --- Update - problem still persists in neon-user-20210609-1125.iso. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438390] Regression: Installation fails on BTRFS
https://bugs.kde.org/show_bug.cgi?id=438390 --- Comment #1 from iGadget --- Using neon-user-20210609-1125.iso, the installer produces a crash when it's displaying 'formatting /dev/nvme0n1p1 as btrfs' (which is pretty disturbing by itself, since nvme0n1p1 is the EFI partition, NOT the partition I'm install Neon to!). Perhaps this crash is because the partition was now formatted as EXT4 instead of already being BTRFS. Other than that, the installation seems to continue after that and, unfortunately, the original issue remains. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438390] Regression: Installation fails on BTRFS
https://bugs.kde.org/show_bug.cgi?id=438390 --- Comment #2 from iGadget --- Worse - even though the installer claims it could not install GRUB, it does in fact mess up the existing boot configuration - I now just get a GRUB prompt after booting, no menu, nothing. This bug *really* sucks. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438390] Regression: Installation fails on BTRFS
https://bugs.kde.org/show_bug.cgi?id=438390 iGadget changed: What|Removed |Added CC||bugs.kde@tenkate.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438391] HWE kernel missing
https://bugs.kde.org/show_bug.cgi?id=438391 iGadget changed: What|Removed |Added CC||bugs.kde@tenkate.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429626] New: Crashes when changing refresh rate of non-enabled monitor.
https://bugs.kde.org/show_bug.cgi?id=429626 Bug ID: 429626 Summary: Crashes when changing refresh rate of non-enabled monitor. Product: systemsettings Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugs.kde@tenkate.net Target Milestone: --- Application: systemsettings5 (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-29-lowlatency x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: Set the refresh rate of my hdmi-connected (not yet enabled) second monitor from 24Hz to 30Hz. - Unusual behavior I noticed: When the second monitor was automatically enabled at boot, the exact right half of the screen was completely distorted. That's why I started changing refresh rates and trying to disable / enable the monitor, to see if that made any difference. Before I could finish, I ran into this crash. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 KScreen::Mode::size (this=this@entry=0x0) at ./src/mode.cpp:102 #5 0x7feee828da82 in operator() (mode=..., __closure=) at ./kcm/output_model.cpp:373 #6 __gnu_cxx::__ops::_Iter_pred >::operator() >::const_iterator> (__it=..., this=) at /usr/include/c++/10/bits/predefined_ops.h:316 #7 std::__find_if >::const_iterator, __gnu_cxx::__ops::_Iter_pred > > (__pred=..., __last=..., __first=...) at /usr/include/c++/10/bits/stl_algobase.h:1915 #8 std::__find_if >::const_iterator, __gnu_cxx::__ops::_Iter_pred > > (__pred=..., __last=..., __first=...) at /usr/include/c++/10/bits/stl_algobase.h:1977 #9 std::find_if >::const_iterator, OutputModel::setRefreshRate(int, int):: > (__pred=..., __last=..., __first=...) at /usr/include/c++/10/bits/stl_algo.h:3928 #10 OutputModel::setRefreshRate (this=0x55a72f287aa0, outputIndex=1, refIndex=) at ./kcm/output_model.cpp:375 #11 0x7fef387290fd in QQmlDMAbstractItemModelData::setValue (value=..., role=269, this=0x55a72f289a80) at qqmladaptormodel.cpp:419 #12 QQmlDMCachedModelData::metaCall (this=0x55a72f289a80, call=, id=, arguments=) at qqmladaptormodel.cpp:296 #13 0x7fef39c2c520 in QQmlPropertyData::writeProperty (flags=..., value=0x7ffe2608c5d0, target=0x55a72f289a80, this=0x55a72df0cad8) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:290 #14 QQmlPropertyPrivate::write (object=0x55a72f289a80, property=..., value=..., context=, flags=...) at qml/qqmlproperty.cpp:1305 #15 0x7fef39b6439b in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:119 #16 0x7fef39b64db7 in QV4::QObjectWrapper::setQmlProperty (engine=0x55a72ebba0a0, qmlContext=, object=0x55a72f289a80, name=, revisionMode=QV4::QObjectWrapper::IgnoreRevision, value=...) at jsruntime/qv4qobjectwrapper.cpp:435 #17 0x7fef39b64f55 in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/include/c++/10/bits/atomic_base.h:420 #18 0x7fef39b30dab in QV4::Object::put (receiver=0x7feed44f2550, v=..., id=..., this=0x7feed44f2550) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:82 #19 QV4::Object::virtualResolveLookupSetter (object=0x7feed44f2550, engine=0x55a72ebba0a0, lookup=0x55a72f290210, value=...) at jsruntime/qv4object.cpp:804 #20 0x7fef39b7d178 in QV4::Moth::VME::interpret (frame=0x7ffe2608c970, engine=0x55a72ebba0a0, code=0x7feee814de21 "\016\002") at jsruntime/qv4vme_moth.cpp:653 #21 0x7fef39b810b7 in QV4::Moth::VME::exec (frame=frame@entry=0x7ffe2608c970, engine=engine@entry=0x55a72ebba0a0) at jsruntime/qv4vme_moth.cpp:463 #22 0x7fef39b1e08d in QV4::Function::call (this=this@entry=0x55a72f28b2a0, thisObject=, argv=argv@entry=0x7feed44f2508, argc=, context=) at jsruntime/qv4function.cpp:69 #23 0x7fef39c84a15 in QQmlJavaScriptExpression::evaluate (this=this@entry=0x55a72f504e40, callData=callData@entry=0x7feed44f24d8, isUndefined=isUndefined@entry=0x0) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #24 0x7fef39c3c07b in QQmlBoundSignalExpression::evaluate (this=, a=) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #25 0x7fef39c3c558 in QQmlBoundSignal_callback (e=0x55a72f4fefc0, a=0x7ffe2608e5e0) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69 #26 0x7fef39c6a67d in QQmlNotifier::emitNotify (endpoint=, a=0x7ffe2608e5e0) at qml/
[systemsettings] [Bug 429626] Crashes when changing refresh rate of non-enabled monitor.
https://bugs.kde.org/show_bug.cgi?id=429626 --- Comment #6 from iGadget --- Sorry, can't test this anymore as my setup has changed drastically since I reported this issue almost two years ago. No longer working with 2 monitors and, sorry to say, no longer working with KDE. Working around all the issues just took too much time. Still believe in KDE's potential however, so I might try again some day. Keep up the good work! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 422855] New: Crashes while logging in / auto restore of apps
https://bugs.kde.org/show_bug.cgi?id=422855 Bug ID: 422855 Summary: Crashes while logging in / auto restore of apps Product: Discover Version: 5.19.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: bugs.kde@tenkate.net CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.19.0) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: Nothing. The system had cold-booted, I had just logged in and as all my applications were being restored, this crash occured. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 flatpak_dir_list_refs (self=self@entry=0x0, kind=kind@entry=0x7f17deb98e9f "app", refs_out=refs_out@entry=0x7f17c88dba80, cancellable=cancellable@entry=0x7f1808004da0, error=error@entry=0x7f17c88dbba0) at common/flatpak-dir.c:6249 #5 0x7f17deb51578 in flatpak_installation_list_installed_refs (self=self@entry=0x55937527c100, cancellable=cancellable@entry=0x7f1808004da0, error=error@entry=0x7f17c88dbba0) at common/flatpak-installation.c:908 #6 0x7f17deb539c2 in flatpak_installation_list_installed_refs_for_update (self=0x55937527c100, cancellable=0x7f1808004da0, error=error@entry=0x7f17c88dbba0) at common/flatpak-installation.c:1087 #7 0x7f17dede7c82 in FlatpakBackendoperator() (__closure=0x5593781ec338) at ./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:815 #9 QtConcurrent::RunFunctionTask<_GPtrArray*>::run (this=0x5593781ec310) at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #10 0x7f181eadc382 in QThreadPoolThread::run (this=0x559376563a10) at thread/qthreadpool.cpp:99 #11 0x7f181ead8c2c in QThreadPrivate::start (arg=0x559376563a10) at thread/qthread_unix.cpp:342 #12 0x7f181a9126db in start_thread (arg=0x7f17c88dc700) at pthread_create.c:463 #13 0x7f181e3cd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7f181853775f in g_cond_wait () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f18184f0875 in g_main_context_wait () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f18184f1903 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f17cb4ee401 in fwupd_client_update_metadata () from /usr/lib/x86_64-linux-gnu/libfwupd.so.2 #5 0x7f17cb71804b in FwupdBackend::refreshRemote (backend=0x559376d1e7b0, remote=remote@entry=0x7f17a846c400, cacheAge=cacheAge@entry=86400, cancellable=0x55937527bda0) at ./libdiscover/backends/FwupdBackend/FwupdBackend.cpp:341 #6 0x7f17cb719218 in FwupdBackendoperator() (__closure=0x55937603f7e8) at ./libdiscover/backends/FwupdBackend/FwupdBackend.cpp:446 #8 QtConcurrent::RunFunctionTask<_GPtrArray*>::run (this=0x55937603f7c0) at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #9 0x7f181eadc382 in QThreadPoolThread::run (this=0x559376d0bf00) at thread/qthreadpool.cpp:99 #10 0x7f181ead8c2c in QThreadPrivate::start (arg=0x559376d0bf00) at thread/qthread_unix.cpp:342 #11 0x7f181a9126db in start_thread (arg=0x7f17c98de700) at pthread_create.c:463 #12 0x7f181e3cd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7f181ead7e06 in get_thread_data () at thread/qthread_unix.cpp:173 #2 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:220 #3 0x7f181ed27e21 in postEventSourcePrepare (timeout=0x0, s=0x7f17b4003ad0) at kernel/qeventdispatcher_glib.cpp:253 #4 postEventSourceCheck (source=0x7f17b4003ad0) at kernel/qeventdispatcher_glib.cpp:270 #5 0x7f18184f0fe1 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f18184f1570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f18184f16dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f181ed277cb in QEventDispatcherGlib::processEvents (this=0x7f17b4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #9 0x7f181ecc6d2a in QEventLoop::exec (this=this@entry=0x7f17ca0dec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #10 0x7f181ead7757 in QThread::exec (this=) at thread/qthread.cpp:536 #11 0x7f181ead8c2c in QThreadPrivate::start (arg=0x559375e60520) at thread/qthread_unix.cpp:342 #12 0x7f181a9126db in start_thread (arg=0x7f17ca0df700) at pthread_create.c:463 #13 0x7f181e3cd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7f18184f05e4 in g_main_context_release () from /usr/lib/x86_64-linux-gnu/libgl
[kdenlive] [Bug 387846] Consumes 2x 90% CPU time, even when idle
https://bugs.kde.org/show_bug.cgi?id=387846 --- Comment #2 from iGadget --- (In reply to iGadget from comment #1) > Just tested with 17.12.0 AppImage - same result. Apparently this was a pre-17.12.0 version. Tested again with the 'official' 17.12.0, but the problem remains. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387846] Consumes 2x 90% CPU time, even when idle
https://bugs.kde.org/show_bug.cgi?id=387846 --- Comment #6 from iGadget --- Yes, 17.12.0b doesn't have the problem any more. Checked on 2 separate systems. Great job guys! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 501583] startup crash on Apple Silicon mac
https://bugs.kde.org/show_bug.cgi?id=501583 iGadget changed: What|Removed |Added CC||bugs.kde@tenkate.net --- Comment #4 from iGadget --- I'm getting this on Apple x86_64 (running macOS Monterey 12.7.6) as well. Proposed workaround results in this error: error: The specified item could not be found in the keychain. What am I missing? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 501583] startup crash on Apple Silicon mac
https://bugs.kde.org/show_bug.cgi?id=501583 --- Comment #6 from iGadget --- (In reply to emohr from comment #5) > The signature issue is not solved yet. > Please follow the steps in https://bugs.kde.org/show_bug.cgi?id=501583#c1 I followed the steps, I'm just getting a different error: owner@mac ~ % sudo codesign --force --sign -"Applications/kdenlive.app" Password: error: The specified item could not be found in the keychain. No message on the top right asking for Terminal full disk access. -- You are receiving this mail because: You are watching all bug changes.
