[ark] [Bug 457812] Ark crashed during loading big archive
https://bugs.kde.org/show_bug.cgi?id=457812 Radoslav Georgiev changed: What|Removed |Added CC||rgeorgiev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 457812] Ark crashed during loading big archive
https://bugs.kde.org/show_bug.cgi?id=457812 --- Comment #1 from Radoslav Georgiev --- Created attachment 163980 --> https://bugs.kde.org/attachment.cgi?id=163980=edit New crash information added by DrKonqi ark (23.08.3) using Qt 5.15.11 Ark crashed while it was trying to open an archive containing a file which is quite big in extracted form (33.8 GiB, to be exact). -- Backtrace (Reduced): #4 archive_set_error (a=0x0, error_number=-1, fmt=0x7fdaac7426df "gzip decompression failed") at /usr/src/debug/libarchive-3.7.0/libarchive/archive_util.c:182 #5 0x7fdaac6cdfaa in gzip_filter_read (self=0x7fda8c0378b0, p=0x7fda8c037918) at /usr/src/debug/libarchive-3.7.0/libarchive/archive_read_support_filter_gzip.c:489 #6 0x7fdaac6c4272 in advance_file_pointer (filter=0x7fda8c0378b0, request=13266596352) at /usr/src/debug/libarchive-3.7.0/libarchive/archive_read.c:1583 #7 0x7fdaac6f1d83 in __archive_read_filter_consume (request=36267765760, filter=0x7fda8c0378b0) at /usr/src/debug/libarchive-3.7.0/libarchive/archive_read.c:1516 #8 __archive_read_consume (a=, request=36267765760) at /usr/src/debug/libarchive-3.7.0/libarchive/archive_read.c:1502 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469495] New: Plasma crashes while I was working in Firefox
https://bugs.kde.org/show_bug.cgi?id=469495 Bug ID: 469495 Summary: Plasma crashes while I was working in Firefox Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rgeorgiev...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.4) Qt Version: 5.15.8 Frameworks Version: 5.105.0 Operating System: Linux 6.2.10-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I was switching to another tab in Firefox when it crashed along with Plasma and all running Visual Studio Code instances. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fa956363439 in () at /lib64/libQt5Qml.so.5 #5 0x7fa956203628 in () at /lib64/libQt5Qml.so.5 #6 0x7fa956263bb0 in () at /lib64/libQt5Qml.so.5 #7 0x7fa9561df407 in () at /lib64/libQt5Qml.so.5 #8 0x7fa956172a98 in () at /lib64/libQt5Qml.so.5 #9 0x7fa9561ee7d4 in QV4::Runtime::CallQmlContextPropertyLookup::call(QV4::ExecutionEngine*, unsigned int, QV4::Value*, int) () at /lib64/libQt5Qml.so.5 #10 0x7fa9561dae0d in () at /lib64/libQt5Qml.so.5 #11 0x7fa9561df42f in () at /lib64/libQt5Qml.so.5 #12 0x7fa956171c92 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /lib64/libQt5Qml.so.5 #13 0x7fa9562fb61d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /lib64/libQt5Qml.so.5 #14 0x7fa9562ac5cf in QQmlBoundSignalExpression::evaluate(void**) () at /lib64/libQt5Qml.so.5 #15 0x7fa9562ad7b0 in () at /lib64/libQt5Qml.so.5 #16 0x7fa9562e0565 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /lib64/libQt5Qml.so.5 #17 0x7fa954b24ced in () at /lib64/libQt5Core.so.5 #18 0x7fa9383131f5 in Plasma::DataSource::sourceRemoved(QString const&) (this=, _t1=) at /usr/src/debug/plasma-framework-5.105.0/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/moc_datasource.cpp:426 #19 0x7fa954b25402 in () at /lib64/libQt5Core.so.5 #20 0x7fa956e46205 in Plasma::DataEngine::sourceRemoved(QString const&) (this=this@entry=0x564ed191a160, _t1=...) at /usr/src/debug/plasma-framework-5.105.0/build/src/plasma/KF5Plasma_autogen/include/moc_dataengine.cpp:232 #21 0x7fa956e4e032 in Plasma::DataEngine::removeSource(QString const&) (this=0x564ed191a160, source=...) at /usr/src/debug/plasma-framework-5.105.0/src/plasma/dataengine.cpp:298 #22 0x7fa9044e205b in () at /usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_mpris2.so #23 0x7fa954b25402 in () at /lib64/libQt5Core.so.5 #24 0x7fa955e20fff in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () at /lib64/libQt5DBus.so.5 #25 0x7fa955e21a2e in () at /lib64/libQt5DBus.so.5 #26 0x7fa955e21de3 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () at /lib64/libQt5DBus.so.5 #27 0x7fa955dd356b in () at /lib64/libQt5DBus.so.5 #28 0x7fa954b18e20 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #29 0x7fa9557a52ce in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #30 0x7fa954aecb28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #31 0x7fa954af0121 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #32 0x7fa954b468a3 in () at /lib64/libQt5Core.so.5 #33 0x7fa9535ecf96 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #34 0x7fa9535ed358 in () at /lib64/libglib-2.0.so.0 #35 0x7fa9535ed3ec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #36 0x7fa954b460b6 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #37 0x7fa954aeb5cb in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #38 0x7fa954af3a50 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #39 0x564ecf97b480 in () #40 0x7fa95422cbb0 in __libc_start_call_main () at /lib64/libc.so.6 #41 0x7fa95422cc79 in __libc_start_main_impl () at /lib64/libc.so.6 #42 0x564ecf97b845 in () [Inferior 1 (process 94230) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446533] The "Render" functionality does not work
https://bugs.kde.org/show_bug.cgi?id=446533 Radoslav Georgiev changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #4 from Radoslav Georgiev --- (In reply to emohr from comment #3) > According your steps you don't put any clips into the timeline, so there is > nothing to render. If this is the case you have to put first the clips from > the project bin into the timeline before you render. > > Please post a screenshot here to see how Kdenlive looks like. You're absolutely correct: I need to add the clip to the timeline first. Sorry for wasting your time; I really should have read the handbook first. Nevertheless, I think that an error message would be useful in this case: Kdenlive could tell the user that "there are no clips on the timeline to render" (or something like that). Shall I create a feature request for this? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446533] The "Render" functionality does not work
https://bugs.kde.org/show_bug.cgi?id=446533 --- Comment #2 from Radoslav Georgiev --- (In reply to emohr from comment #1) > Please try with the current Kdenlive_Nightly_Appimage to see if there are > any packaging issues > > https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/ > lastSuccessfulBuild/artifact/ I tried again using that version, and the issue is still reproducible. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446533] New: The "Render" functionality does not work
https://bugs.kde.org/show_bug.cgi?id=446533 Bug ID: 446533 Summary: The "Render" functionality does not work Product: kdenlive Version: 21.11.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: rgeorgiev...@gmail.com Target Milestone: --- SUMMARY I cannot render videos from any project which I create or open with Kdenlive. STEPS TO REPRODUCE 1. Open Kdenlive. 2. Add a video clip to the blank project using Project -> Add Clip or Folder or open a Kdenlive project. 3. Click on the "Render" button on the toolbar. 4. Click on "Render to File" in the "Rendering - Kdenlive" dialog. OBSERVED RESULT Kdenlive should start rendering the current project into a video file. EXPECTED RESULT Nothing happens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437876] New: Spectacle crashes on exit
https://bugs.kde.org/show_bug.cgi?id=437876 Bug ID: 437876 Summary: Spectacle crashes on exit Product: Spectacle Version: 21.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: rgeorgiev...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (21.04.1) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.10.40-1-lts x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Every time that I quit Spectacle, it crashes. It does not matter what I do inside the application - it always crashes when I try to close it. The crash can be reproduced every time. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x7fdbe7f8f57c in kImageAnnotator::FontPicker::~FontPicker() () from /usr/lib/libkImageAnnotator.so.0 #5 0x7fdbe7f8f79d in kImageAnnotator::FontPicker::~FontPicker() () from /usr/lib/libkImageAnnotator.so.0 #6 0x7fdbe7f4e4a9 in kImageAnnotator::AnnotationItemSettings::~AnnotationItemSettings() () from /usr/lib/libkImageAnnotator.so.0 #7 0x7fdbe7f4e5dd in kImageAnnotator::AnnotationItemSettings::~AnnotationItemSettings() () from /usr/lib/libkImageAnnotator.so.0 #8 0x7fdbe7f49f02 in kImageAnnotator::AnnotationWidget::~AnnotationWidget() () from /usr/lib/libkImageAnnotator.so.0 #9 0x7fdbe7f49fad in kImageAnnotator::AnnotationWidget::~AnnotationWidget() () from /usr/lib/libkImageAnnotator.so.0 #10 0x7fdbe7f4985f in kImageAnnotator::CoreView::~CoreView() () from /usr/lib/libkImageAnnotator.so.0 #11 0x7fdbe7f48a5b in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /usr/lib/libkImageAnnotator.so.0 #12 0x7fdbe7f48a8e in kImageAnnotator::KImageAnnotator::~KImageAnnotator() () from /usr/lib/libkImageAnnotator.so.0 #13 0x7fdbe64337de in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #14 0x7fdbe6f1d5ce in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #15 0x561d7cd76402 in KSWidget::~KSWidget() () #16 0x7fdbe64337de in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #17 0x7fdbe6f1d5ce in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #18 0x561d7cd776f1 in SpectacleCore::~SpectacleCore() () #19 0x561d7cd7250d in main () [Inferior 1 (process 3389465) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426496] Multiple monitor assignment is wrong after update to Qt 5.15.1
https://bugs.kde.org/show_bug.cgi?id=426496 Radoslav Georgiev changed: What|Removed |Added CC||rgeorgiev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421123] Notification dot remains on systray icon on an up-to-date system even after using the "Refresh..." action
https://bugs.kde.org/show_bug.cgi?id=421123 Radoslav Georgiev changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from Radoslav Georgiev --- Strangely enough, the issue is reproducible again. Even stranger is the fact that the versions of KDE Plasma/KDE Frameworks/Qt on my machine haven't changed since KDE Frameworks got updated to 5.70.0. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 419299] [kscreenlocker] spaming "kscreenlocker_greet[9912]: Could not create AF_NETLINK socket"
https://bugs.kde.org/show_bug.cgi?id=419299 Radoslav Georgiev changed: What|Removed |Added CC||rgeorgiev...@gmail.com --- Comment #2 from Radoslav Georgiev --- The issue is also reproducible on my system. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.4.39-1-lts OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421123] Notification dot remains on systray icon on an up-to-date system even after using the "Refresh..." action
https://bugs.kde.org/show_bug.cgi?id=421123 --- Comment #2 from Radoslav Georgiev --- My KDE Frameworks got updated to 5.70.0 recently, and I can no longer reproduce the issue with the new version. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421123] Notification dot remains on systray icon on an up-to-date system even after using the "Refresh..." action
https://bugs.kde.org/show_bug.cgi?id=421123 Radoslav Georgiev changed: What|Removed |Added Assignee|lei...@leinir.dk|aleix...@kde.org Component|discover|Notifier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421123] New: Notification dot remains on systray icon on an up-to-date system even after using the "Refresh..." action
https://bugs.kde.org/show_bug.cgi?id=421123 Bug ID: 421123 Summary: Notification dot remains on systray icon on an up-to-date system even after using the "Refresh..." action Product: Discover Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: rgeorgiev...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY The notification dot for pending updates remains on the Discover system tray icon after a full update of the system even after I try to refresh its state via the "Refresh..." action. STEPS TO REPRODUCE 1. Apply all pending updates to the system successfully using a means different from Discover (I used the Yay tool in my case). 2. Click on the "Refresh..." action from the context menu for the Discover system tray icon. OBSERVED RESULT The notification dot for pending updates remains on the system tray icon. EXPECTED RESULT The notification dot for pending updates should disappear from the system tray icon. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.4.38-1-lts (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION The dot disappears after I open the Discover front-end. -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 405938] New: After choosing to display only log messages with an "Emergency" priority, new messages with other priorities continue to appear
https://bugs.kde.org/show_bug.cgi?id=405938 Bug ID: 405938 Summary: After choosing to display only log messages with an "Emergency" priority, new messages with other priorities continue to appear Product: KSystemLog Version: 18.12 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.ternis...@gmail.com Reporter: rgeorgiev...@gmail.com Target Milestone: --- SUMMARY After choosing to display only log messages with an "Emergency" priority, new messages with other priorities still continue to appear. For instance, on my system various messages with priorities such as "Information" and "Warning" appear despite the fact that only the "Emergency" priority is selected. STEPS TO REPRODUCE 1. Select the "Emergency" priority for filtering from the "Select priorities" dropdown. 2. Wait a bit for new messages to appear in the log. OBSERVED RESULT New messages with all kinds of priorities appear in the log. EXPECTED RESULT Only new messages whose priority is "Emergency" should appear in the log. SOFTWARE/OS VERSIONS Kernel Version: 4.19.30-1-MANJARO KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
