[kdenlive] [Bug 372018] New: Volume adjustments not working
https://bugs.kde.org/show_bug.cgi?id=372018 Bug ID: 372018 Summary: Volume adjustments not working Product: kdenlive Version: 16.08.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: edward.l...@gmail.com Target Milestone: --- Can't adjust the volume on a clip. I add Volume (keyframable), and in its properties I click the + and I get my marking. I adjust the volume for that and it shows on the clip as well. But when I listen the volume hasn't changed. I save, quit, and re-open my project and the marking is gone. I try to do it again but this time it won't stick. But that isn't the only one. When I add the Volume (keyframable) and try to add the adjustments by double-clicking on the clip itself, I get the mark, and I can drag it, but it won't stay at that level. If I drag it below the clip it vanishes all together. Not sure if that is intentional, but I would expect it to stay at the bottom and call it "mute". Also, would it be possible to also have a "percentage" meter? I just don't know what 5% of 0dB would be... -55? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372020] New: Ungrouped clips don't stay ungrouped.
https://bugs.kde.org/show_bug.cgi?id=372020 Bug ID: 372020 Summary: Ungrouped clips don't stay ungrouped. Product: kdenlive Version: 16.08.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: edward.l...@gmail.com Target Milestone: --- At one point I group clips so that I can keep things synced. But then I want to apply effects (like volume) so I ungroup the clips and apply what is needed. But when I save, close, and re-open the project the clips are still grouped. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372020] Ungrouped clips don't stay ungrouped.
https://bugs.kde.org/show_bug.cgi?id=372020 --- Comment #1 from Edward --- Ubuntu 16.04, if I forgot to mention that... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372018] Volume adjustments not working
https://bugs.kde.org/show_bug.cgi?id=372018 --- Comment #1 from Edward --- Ubuntu 16.04, if I forgot to mention that... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372020] Ungrouped clips don't stay ungrouped.
https://bugs.kde.org/show_bug.cgi?id=372020 --- Comment #3 from Edward --- Created attachment 102057 --> https://bugs.kde.org/attachment.cgi?id=102057&action=edit The file I was working on when discovering the problem. Here is the file I was working on. I just now loaded the project, ungrouped, and resaved. Still grouped. And yes, this is 16.08.2 as set at the very top of this page. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372020] Ungrouped clips don't stay ungrouped.
https://bugs.kde.org/show_bug.cgi?id=372020 --- Comment #4 from Edward --- Ok, I saw an update for Kdenlive (16.08.3) and thought I'd see if the issue was taken care of. Sadly, it had not. However, I thought I'd try something. I ungrouped the clips and tried shifting the audio. I could not move it. I then tried to shift the video and I could shift it. Taking a risk I shifted it a few seconds, saved and quit. When I re-opened the project the clips were ungrouped and in their last saved positions. At this point I could also shift the audio clip. But when I returned them so they aligned, saved, quit, and re-opened they were grouped again. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467823] New: There is no response on Korganizer when 'Edit' is checked
https://bugs.kde.org/show_bug.cgi?id=467823 Bug ID: 467823 Summary: There is no response on Korganizer when 'Edit' is checked Classification: I don't know Product: kde Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: edh...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Right click on Entry 2. Left click on 'Edit' 3. OBSERVED RESULT Nothing happens EXPECTED RESULT Edit window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 20.3 Cinnamon (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.
[kio-gdrive] [Bug 467428] Expired or missing access tokens for account
https://bugs.kde.org/show_bug.cgi?id=467428 Edward changed: What|Removed |Added CC||papashre...@gmail.com --- Comment #4 from Edward --- having the same problem here Platform: EndeavourOS plasma version: 5.27.5 KDE Frameworks version: 5.106.0 Graphics platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442870] New: Bookmark Commands
https://bugs.kde.org/show_bug.cgi?id=442870 Bug ID: 442870 Summary: Bookmark Commands Product: konsole Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bookmark Assignee: konsole-de...@kde.org Reporter: edward.ni...@gmail.com Target Milestone: --- SUMMARY Can you please make a feature that we can bookmark a commands and give them a alias? STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT 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.
[systemsettings] [Bug 443000] New: system setting crash after changing screen edge setting when closing after applying. Settings not saved Wayland
https://bugs.kde.org/show_bug.cgi?id=443000 Bug ID: 443000 Summary: system setting crash after changing screen edge setting when closing after applying. Settings not saved Wayland Product: systemsettings Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: papashre...@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.7-200.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.4 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: I was setting up a screen edge control in system settings, Hit apply to save the changes, and when I close the window for system settings it crashes and resets to default settings. tried a second time with exact same results. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x55ac7bdd6c70 in ?? () #5 0x7fcc547d3e47 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #6 0x7fcc547c0419 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #7 0x7fcc547dc6c3 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #8 0x7fcc5208bc04 in ffi_call_unix64 () from /lib64/libffi.so.6 #9 0x7fcc5208b107 in ffi_call () from /lib64/libffi.so.6 #10 0x7fcc5472dd10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #11 0x7fcc5472e42b in dispatch_event.isra () from /lib64/libwayland-client.so.0 #12 0x7fcc5472e61c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #13 0x7fcc547b861f in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #14 0x7fcc56dcd3f0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7fcc56deac0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7fcc56d981a2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7fcc56da06e4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x55ac7914858c in main () [Inferior 1 (process 93) detached] Possible duplicates by query: bug 442318, bug 442289, bug 441707, bug 441700, bug 441504. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 451630] New: feature request
https://bugs.kde.org/show_bug.cgi?id=451630 Bug ID: 451630 Summary: feature request Product: Elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: papashre...@gmail.com Target Milestone: --- feature request: allow Elisa to minimize to systray and keep playing music similar to rythymbox or clementine. rather than just minimizing window of app, but be able to close main window and keep music playing. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 439570] ksplashqm crashes inside mesa while watiting for login screen
https://bugs.kde.org/show_bug.cgi?id=439570 --- Comment #2 from Edward --- Created attachment 139996 --> https://bugs.kde.org/attachment.cgi?id=139996&action=edit 2021-07-11 backtrace Backtrace for current crash of ksplashqm after update restart. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 440114] New: Mouse pointer too slow
https://bugs.kde.org/show_bug.cgi?id=440114 Bug ID: 440114 Summary: Mouse pointer too slow Product: kdeconnect Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: edward.ni...@gmail.com Target Milestone: --- SUMMARY On kde connect when i want to navigate my android with a mouse i can't move my mouse across the entire screen in one move and why i have to hold left mouse button pressed in order to move the mouse on android? STEPS TO REPRODUCE 1. Can you make it more intuitively and simple? 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 KDE Plasma Spin (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.
[ksplash] [Bug 439570] New: ksplashqm will crash while watiting for login screen
https://bugs.kde.org/show_bug.cgi?id=439570 Bug ID: 439570 Summary: ksplashqm will crash while watiting for login screen Product: ksplash Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: edfreema...@gmail.com Target Milestone: --- Created attachment 139908 --> https://bugs.kde.org/attachment.cgi?id=139908&action=edit backtrace report SUMMARY: Ksplashqm will randomly crash before login credential are able to be entered on fedora 34 KDE spin using Wayland. Usually clicking on restart application will fix it, however this last time it failed to restart. Claims segmentation fault (11). no KDE add-ons enabled, no third party apps installed, happening on fresh clean install. STEPS TO REPRODUCE 1. restart computer or booting computer after a complete shutdown 2. wait for splash screen to go to login credentials OBSERVED RESULT notice of ksplashqm having segmentation fault, option to restart, cancel or report bug. click on bug report and notified that there is no address to report bug, availability to create backtrace report EXPECTED RESULT loading login screen to login to system. SOFTWARE/OS VERSIONS: Operating System: Fedora 34 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 2 × AMD E-300 APU with Radeon(tm) HD Graphics Memory: 7.4 GiB of RAM Graphics Processor: AMD PALM ADDITIONAL INFORMATION backtrace attached -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424909] New: Dolphin crash *after* copying file between USB-attached Android and external HD in tabs
https://bugs.kde.org/show_bug.cgi?id=424909 Bug ID: 424909 Summary: Dolphin crash *after* copying file between USB-attached Android and external HD in tabs Product: dolphin Version: 20.07.80 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: edwardb_...@shaw.ca CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.07.80) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 4.12.14-lp151.28.52-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: I had a USB-attached external HD open in one dolphin tab, and a USB-attached Android in another, and I dragged a movie file from the former to the latter for copying. The copying completed successfully. Then I went to close the first tab, and dolphin crashed. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 0x7f4f15dc6520 in raise () from /lib64/libc.so.6 #5 0x7f4f15dc7b01 in abort () from /lib64/libc.so.6 #6 0x7f4f15e09957 in __libc_message () from /lib64/libc.so.6 #7 0x7f4f15e10173 in malloc_printerr () from /lib64/libc.so.6 #8 0x7f4f15e11a79 in _int_free () from /lib64/libc.so.6 #9 0x7f4f0f55bb74 in QHashData::free_helper (this=0x5575bb53bbf0, node_delete=0x7f4f15abaca0 ::deleteNode2(QHashData::Node*)>) at tools/qhash.cpp:573 #10 0x7f4f15abe6c4 in QHash::freeData (this=0x7f4ef8003628, x=) at /usr/include/qt5/QtCore/qhash.h:619 #11 QHash::~QHash (this=0x7f4ef8003628, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:250 #12 KFileItemModel::ItemData::~ItemData (this=0x7f4ef8003620, __in_chrg=) at /usr/src/debug/dolphin-20.07.80-lp151.219.1.x86_64/src/kitemviews/kfileitemmodel.h:298 #13 KFileItemModel::removeItems (this=0x5575bbf00d70, itemRanges=..., behavior=KFileItemModel::DeleteItemData) at /usr/src/debug/dolphin-20.07.80-lp151.219.1.x86_64/src/kitemviews/kfileitemmodel.cpp:1296 #14 0x7f4f15acaa3a in KFileItemModel::setExpanded (this=0x5575bbf00d70, index=1, expanded=) at /usr/src/debug/dolphin-20.07.80-lp151.219.1.x86_64/src/kitemviews/kfileitemmodel.cpp:580 #15 0x7f4f15adfa43 in KItemListController::mouseReleaseEvent (this=0x5575bb8d5bf0, event=0x7ffd52f52190, transform=...) at /usr/src/debug/dolphin-20.07.80-lp151.219.1.x86_64/src/kitemviews/kitemlistcontroller.cpp:783 #16 0x7f4f15ae0fd2 in KItemListController::processEvent (this=this@entry=0x5575bb8d5bf0, event=event@entry=0x7ffd52f52190, transform=...) at /usr/src/debug/dolphin-20.07.80-lp151.219.1.x86_64/src/kitemviews/kitemlistcontroller.cpp:1060 #17 0x7f4f15aefedc in KItemListView::event (this=0x5575bb8d2f50, event=0x7ffd52f52190) at /usr/src/debug/dolphin-20.07.80-lp151.219.1.x86_64/src/kitemviews/kitemlistview.cpp:917 #18 0x7f4f10b2f2fc in QApplicationPrivate::notify_helper (this=this@entry=0x5575bb0a9ee0, receiver=receiver@entry=0x5575bb8d2f50, e=e@entry=0x7ffd52f52190) at kernel/qapplication.cpp:3671 #19 0x7f4f10b36210 in QApplication::notify (this=0x7ffd52f530b0, receiver=0x5575bb8d2f50, e=0x7ffd52f52190) at kernel/qapplication.cpp:3417 #20 0x7f4f0f713f33 in QCoreApplication::notifyInternal2 (receiver=0x5575bb8d2f50, event=0x7ffd52f52190) at kernel/qcoreapplication.cpp:1061 #21 0x7f4f0f71411e in QCoreApplication::sendSpontaneousEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1468 #22 0x7f4f10b2f615 in qt_sendSpontaneousEvent (receiver=, event=) at kernel/qapplication.cpp:4092 #23 0x7f4f10e3ff0d in QGraphicsScenePrivate::sendEvent (this=, item=0x5575bb8d2f60, event=0x7ffd52f52190) at graphicsview/qgraphicsscene.cpp:1254 #24 0x7f4f10e402f2 in QGraphicsScenePrivate::sendMouseEvent (this=this@entry=0x5575bbd744a0, mouseEvent=mouseEvent@entry=0x7ffd52f52190) at graphicsview/qgraphicsscene.cpp:1335 #25 0x7f4f10e4569a in QGraphicsScene::mouseReleaseEvent (this=, mouseEvent=0x7ffd52f52190) at graphicsview/qgraphicsscene.cpp:4123 #26 0x7f4f10e4fbc0 in QGraphicsScene::event (this=0x5575bb528930, event=0x7ffd52f52190) at graphicsview/qgraphicsscene.cpp:3436 #27 0x7f4f10b2f2fc in QApplicationPrivate::notify_helper (this=this@entry=0x5575bb0a9ee0, receiver=receiver@entry=0x5575bb528930, e=e@entry=0x7ffd52f52190) at kernel/qapplication.cpp:3671 #28 0x7f4f10b36210 in QApplication::notify (this=0x7ffd52f530b0, receiver=0x5575bb528930, e=0x7ffd52f52190) at kernel/qapplication.cpp:3417 #29 0x7f4f0f713f33 in QCoreApplication::notifyInternal2 (receiver=0x5575bb528930, event=0x7ffd52f52190) at kernel/qcoreapplication.cpp:1061 #30 0x7f4f0f71411e in QCoreApplication::sendSpontaneousEvent (receiver=, event=event@entry=0x7ffd52f52190) at kernel/qcoreapplication.c
[kio-gdrive] [Bug 464772] kio-gdrive successfully authenticates but fails to list content
https://bugs.kde.org/show_bug.cgi?id=464772 Edward changed: What|Removed |Added CC||papashre...@gmail.com --- Comment #4 from Edward --- new install within last 24 hours, this issue is still persistent in kio-gdrive keep getting the error "Expired or missing access tokens for account google1" when I go to copy files from google drive on to my system. it took me multiple attempts to be able to load the directory structure without that error. system specs: OS: EndeavourOS KDE plasma version: 5.27.9 Kernel: 6.5.9-arch2-1 kio-gdrive version: 23.08.2-1 Please notify if you need more information. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424909] Dolphin crash *after* copying file between USB-attached Android and external HD in tabs
https://bugs.kde.org/show_bug.cgi?id=424909 --- Comment #2 from Edward --- Yes, using Tree View. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 434725] New: Crashed when starting Kontact being started
https://bugs.kde.org/show_bug.cgi?id=434725 Bug ID: 434725 Summary: Crashed when starting Kontact being started Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: pub...@snowfire.org.uk Target Milestone: --- Application: akonadiserver (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.63-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: Had logged on, Kontact was being started, it raised the error on the crash. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x7f2aa06331ec in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/7/bits/atomic_base.h:396 #5 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #6 QBasicAtomicInteger::load (this=0x0) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #7 QtPrivate::RefCount::deref (this=0x0) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:66 #8 QString::operator= (this=this@entry=0x7f2a2c8b8908, other=...) at tools/qstring.cpp:2417 #9 0x55e576489855 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x55e576bbc840, request=0x7f2a2c8b88f0, errorMsg=...) at /usr/src/debug/akonadi-server-20.04.2-lp152.2.6.1.x86_64/src/server/storage/itemretrievalmanager.cpp:176 #10 0x7f2aa07b5f4f in QtPrivate::QSlotObjectBase::call (a=0x7f2a9527f710, r=0x55e576bbc840, this=0x7f2a80007430) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #11 QMetaObject::activate (sender=sender@entry=0x55e576b5b130, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f2a9527f710) at kernel/qobject.cpp:3784 #12 0x7f2aa07b6547 in QMetaObject::activate (sender=sender@entry=0x55e576b5b130, m=m@entry=0x55e5767791c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f2a9527f710) at kernel/qobject.cpp:3657 #13 0x55e5764da764 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (this=this@entry=0x55e576b5b130, _t1=, _t2=...) at /usr/src/debug/akonadi-server-20.04.2-lp152.2.6.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:135 #14 0x55e57648d164 in Akonadi::Server::ItemRetrievalJob::callFinished (this=0x55e576b5b130, watcher=) at /usr/src/debug/akonadi-server-20.04.2-lp152.2.6.1.x86_64/src/server/storage/itemretrievaljob.cpp:78 #15 0x7f2aa07b5f4f in QtPrivate::QSlotObjectBase::call (a=0x7f2a9527f900, r=0x55e576b5b130, this=0x7f2a80006760) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #16 QMetaObject::activate (sender=0x7f2a80007b50, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f2a9527f900) at kernel/qobject.cpp:3784 #17 0x7f2aa07b6547 in QMetaObject::activate (sender=, m=m@entry=0x7f2aa110f5c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f2a9527f900) at kernel/qobject.cpp:3657 #18 0x7f2aa0ef2d5f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:157 #19 0x7f2aa07b69e2 in QObject::event (this=0x7f2a80007b50, e=) at kernel/qobject.cpp:1261 #20 0x7f2aa0786311 in doNotify (event=0x7f2a900367f0, receiver=0x7f2a80007b50) at kernel/qcoreapplication.cpp:1178 #21 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1164 #22 QCoreApplication::notifyInternal2 (receiver=0x7f2a80007b50, event=0x7f2a900367f0) at kernel/qcoreapplication.cpp:1088 #23 0x7f2aa07864fe in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7f2a900367f0) at kernel/qcoreapplication.cpp:1476 #24 0x7f2aa0788ee7 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55e576b8ada0) at kernel/qcoreapplication.cpp:1825 #25 0x7f2aa0789488 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1679 #26 0x7f2aa07e3d93 in postEventSourceDispatch (s=0x7f2a80004fa0) at kernel/qeventdispatcher_glib.cpp:276 #27 0x7f2a9c354624 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f2a9c3549c0 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f2a9c354a4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x7f2aa07e33af in QEventDispatcherGlib::processEvents (this=0x7f2a8b10, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #31 0x7f2aa078457a in QEventLoop::exec (this=this@entry=0x7f2a9527fcb0, flags=..., flags@entry=...)
[k3b] [Bug 350403] DVD rip fails with [transcode] failed to open output
https://bugs.kde.org/show_bug.cgi?id=350403 edward changed: What|Removed |Added CC||ebearden60...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 462869] New: baloo doesn't do a job
https://bugs.kde.org/show_bug.cgi?id=462869 Bug ID: 462869 Summary: baloo doesn't do a job Classification: Plasma Product: krunner Version: 5.26.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: filesearch Assignee: baloo-bugs-n...@kde.org Reporter: edward.ni...@gmail.com CC: alexander.loh...@gmx.de, plasma-b...@kde.org Target Milestone: --- SUMMARY Can you improve baloo so that he can index hard drives without idle times that last forever and if you can make it more fast? SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Plasma 5.26.4 KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378953] Effect "Freeze" stops working after overlay
https://bugs.kde.org/show_bug.cgi?id=378953 --- Comment #10 from Edward --- Ok, I downloaded the latest kdenlive-19.04.2f-x86_64.appimage and running it straight off seems to work with freezing the video with an overlay ontop. Tried both without anything in between, and a dissolve. Frame was frozen ok. And I can see what you mean by the code has changed. At first I could not find Freeze, but after clicking "Show All Filters" I found it. The transition also looked different. However, my only problem with having JUST the AppImage is that all the hundreds of other effects that I have in a previous version are not listed. I suppose I'll have to insert a new repository link if I want to update the installed version with this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406996] New: Pen with WinTab uses coordinate relative to the top left of all displays potentially creating an offset.
https://bugs.kde.org/show_bug.cgi?id=406996 Bug ID: 406996 Summary: Pen with WinTab uses coordinate relative to the top left of all displays potentially creating an offset. Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: fofzequalsz2pl...@gmail.com Target Milestone: --- Note: I'm using a Monoprice 19-Inch TFT Monitor (110707) and can't test for other graphics tablets. STEPS TO REPRODUCE 1. Set your tablet display to be anywhere but the top left in an extended display configuration in the display settings. 1. Open Krita and use WinTab (restart Krita if you weren't already) 2. Identify whether pen pressure no longer registers or if there is an offset within the drawing area. When using WinTab the position of the cursor inside the drawing space uses coordinate relative to the top left of all displays and puts the cursor at that position relative to the current display. This is only within the drawing space; outside the drawing space, the system's mouse position is used. Note: the origin is considered the top left. (hence why this is relative to the top left) This creates an offset if you're using multiple monitors and you're drawing on one that's on the far left, but not at the top. If you're drawing on the right display (or the offset puts the cursor outside of the drawing area), the normal coordinates are used, but pen-pressure is not used. I would've expected Krita to be able to correct for this offset when the drawing display isn't in top left. SOFTWARE/OS VERSIONS Windows 10 Krita version 4.1.7 Monoprice 19-Inch TFT Monitor (110707) Tablet Driver version 9 (2014) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406996] Pen with WinTab uses coordinate relative to the top left of all displays potentially creating an offset.
https://bugs.kde.org/show_bug.cgi?id=406996 Edward changed: What|Removed |Added CC||fofzequalsz2pl...@gmail.com URL||https://youtu.be/iI8PNMCgKm ||o -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406996] Pen with WinTab uses coordinate relative to the top left of all displays potentially creating an offset.
https://bugs.kde.org/show_bug.cgi?id=406996 --- Comment #1 from Edward --- Video of the bug reproduced: https://youtu.be/iI8PNMCgKmo -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375716] Krita Crashes when predifined A3 @ 600P.p.i canvas creation.
https://bugs.kde.org/show_bug.cgi?id=375716 Edward changed: What|Removed |Added Alias||look7see CC||look7...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375716] Krita Crashes when predifined A3 @ 600P.p.i canvas creation.
https://bugs.kde.org/show_bug.cgi?id=375716 --- Comment #1 from Edward --- System Memory 3 Gygabytes -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375716] New: Krita Crashes when predifined A3 @ 600P.p.i canvas creation.
https://bugs.kde.org/show_bug.cgi?id=375716 Bug ID: 375716 Summary: Krita Crashes when predifined A3 @ 600P.p.i canvas creation. Product: krita Version: 3.1.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: look7...@gmail.com Target Milestone: --- pentium dual core E5700 @ 3.00ghZ AMD radeon HD5450 Driver 16.2.1 crimson ( driver 15.301.1901) Monitor resolution 1280/x1024 Tablet Huion H610pro wIN 7 pro Open gl, onno problems When selecting predefined canvas size A3 by 600p.p.i. krita crashes, tried the same predefined size in Photoshop cc, and corelPainter 2015, no problem. trying to rule out tablet other hard ware and software issues, cannot see any conflicting problems. must say that radeon driver was recently updated will try to use previous catalyst driver and see if this is the issue will comunicate any further change. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375716] Krita Crashes when predifined A3 @ 600P.p.i canvas creation.
https://bugs.kde.org/show_bug.cgi?id=375716 --- Comment #3 from Edward --- I'm using 8 bit rgb, it was OK on A4 canvas I'll try some others and let you know, Best regards. On Jan 29, 2017 6:20 PM, "wolthera" wrote: > https://bugs.kde.org/show_bug.cgi?id=375716 > > wolthera changed: > >What|Removed |Added > > > CC||griffinval...@gmail.com > > --- Comment #2 from wolthera --- > Hey there, > > Does it only happen with this canvas size? Which bitdepth are you using? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375716] Krita Crashes when predifined A3 @ 600P.p.i canvas creation.
https://bugs.kde.org/show_bug.cgi?id=375716 --- Comment #5 from Edward --- 32bits, but wouldn't Photoshop and Corel struggle also? I have just launched task manager with all processes visible, when launching Krita it uses approx 02-50% CPU, and 640mb ram, when creating A3 page@600ppi it uses approx 50% CPU and 1334 MB ram and crashes, I have open a custom page with 6000x6000@600ppi with 10 layers, using wolthera's big mop brush at 663pixels, aswell as lagging it crashed at 1474 MB ram and 85% of both cores of cpu. A standard working documents uses approx 30-50% CPU and as much as 1100 MB ram. All other predefined options work with out issue. Hope this helps reach a conclusion. Regards. On Jan 30, 2017 9:47 AM, "Boudewijn Rempt" wrote: > https://bugs.kde.org/show_bug.cgi?id=375716 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org >Platform|Other |MS Windows > > --- Comment #4 from Boudewijn Rempt --- > Are you on a 32 bits version of Windows, or a 64 bits version? I suspect > that > you're simply running out of memory. An image of that size will take > ~530MB of > memory on creation. > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375716] 32 bits Krita crashes if the initial image is too big for the available memory
https://bugs.kde.org/show_bug.cgi?id=375716 --- Comment #7 from Edward --- Thanks for the clarification. All the best. On Jan 31, 2017 9:50 AM, "Boudewijn Rempt" wrote: > https://bugs.kde.org/show_bug.cgi?id=375716 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Ever confirmed|0 |1 > Status|UNCONFIRMED |CONFIRMED > Summary|Krita Crashes when |32 bits Krita crashes if >|predifined A3 @ 600P.p.i|the initial image is too >|canvas creation.|big for the available >||memory > > --- Comment #6 from Boudewijn Rempt --- > I cannot check the code for Photoshop and Corel Painter, so whatever they > do, > isn't relevant for Krita. > > On a 32 bits Windows, you can only allocate 2GB per process. Krita by > default > allows half of the available memory for an image, that is 1GB. If the > image is > too big it tries to swap it out to disk, but that also needs memory, and I > suspect that that just isn't available. You can fiddle with the performance > settings, making Krita use 2GB of memory, for instance, instead of 3/2 = > 1.5, > reduce undo steps and so on. See https://docs.krita.org/ > Performance_Settings > > Btw, the actual PPI isn't relevant; it's only the number of pixels that is > relevant. Memory usage is width * height * number of bytes per pixel * > number > of layers + 1, roughly. > > But the bottom line is that a 7016x9920 pixel image just is too big for > your > computer. You will also have trouble actually painting on an image that > size. > There isn't much we can do at this point, I'm afraid. > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380253] New: Plasma crash on switching virtual desktops with Pager
https://bugs.kde.org/show_bug.cgi?id=380253 Bug ID: 380253 Summary: Plasma crash on switching virtual desktops with Pager Product: plasmashell Version: 5.9.95 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: edwardb_...@shaw.ca CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.95) Qt Version: 5.8.0 Frameworks Version: 5.34.0 Operating System: Linux 4.4.62-18.6-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I had just switched virtual desktops with Pager. Plasma disappeared and restarted itself. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f58aa643900 (LWP 9280))] Thread 33 (Thread 0x7f573f7fe700 (LWP 6638)): #0 0x7f58a335b0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f58a4488c8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f57a57543ff in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f57a5757dca in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f57a5757e12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f57a5757e12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f57a5757e12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f57a5757e12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f57a5757e12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f57a5757e12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f57a5755a26 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f58a4488019 in () at /usr/lib64/libQt5Core.so.5 #19 0x7f58a3356744 in start_thread () at /lib64/libpthread.so.0 #20 0x7f58a3d94d3d in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f5737fff700 (LWP 6637)): #0 0x7f58a335b0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f58a4488c8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f57a57543ff in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f57a5757dca in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f57a5757e12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f57a5757e12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f57a5755a26 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f58a4488019 in () at /usr/lib64/libQt5Core.so.5 #11 0x7f58a3356744 in start_thread () at /lib64/libpthread.so.0 #12 0x7f58a3d94d3d in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f573700 (LWP 6636)): #0 0x7f58a335b0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f58a4488c8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f57a57543ff in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f57a5757dca in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f57a575242b in ThreadWeaver::Weaver::applyForWork(ThreadW
[plasmashell] [Bug 376599] New: Plasma crashed on quickly switching to another virtual desktop and back
https://bugs.kde.org/show_bug.cgi?id=376599 Bug ID: 376599 Summary: Plasma crashed on quickly switching to another virtual desktop and back Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: edwardb_...@shaw.ca CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Switched to a different virtual desktop (using Pager) and immediately back. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8cb29c6900 (LWP 2524))] Thread 19 (Thread 0x7f8b5e3df700 (LWP 6727)): #0 0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8cb06db4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8cb06db995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8cac7e29e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8cac0f6d3d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f8b625da700 (LWP 31740)): #0 0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8cb06db4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8cb06db995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8cac7e29e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8cac0f6d3d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f8b62ddb700 (LWP 31695)): #0 0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8cb06db4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8cb06db995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8cac7e29e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8cac0f6d3d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f8b5fbe2700 (LWP 29208)): #0 0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8cb06db4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8cb06db995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8cac7e29e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8cac0f6d3d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f8b61be6700 (LWP 3656)): #0 0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8cb06db4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8cb06db995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8cac7e29e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8cac0f6d3d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f8bca7fc700 (LWP 3218)): #0 0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8cb06db4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8cb06db995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8cac7e29e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8cac0f6d3d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f8bcb7fe700 (LWP 3170)): #0 0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8cb06db4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8cb06db995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8cac7e29e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8cac0f6d3d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f8bc103e700 (LWP 2941)): #0 0x7f8cac103184 in __lib
[kgpg] [Bug 373408] New: kgpg segfault on boot and every later run
https://bugs.kde.org/show_bug.cgi?id=373408 Bug ID: 373408 Summary: kgpg segfault on boot and every later run Product: kgpg Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: edwardb_...@shaw.ca Target Milestone: --- Application: kgpg (16.11.90) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.27-2-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: - 2016-12-07 - kgpg segfault on rebooting openSuSE 42.2. - and on every subsequent attempt to start kgpg. Information for package kgpg: - Repository : kde-applications Name : kgpg Version: 16.11.90-2.3 Arch : x86_64 Vendor : obs://build.opensuse.org/KDE Installed Size : 2.0 MiB Installed : Yes Status : up-to-date Summary: Encryption Tool Description: Kgpg is a simple GUI for gpg But note that, besides the standard default package repos, I also have the following enabled: kde-applications | http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_Leap_42.2/ kde-extra| http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.2/ So it is possible that I have an unstable mix of libraries present. I would be happy to install specific versions of kgpg and/or whatever libraries in order to help troubleshoot this; just let me know. Thanks. -- Backtrace: Application: KGpg (kgpg), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa16f559900 (LWP 2488))] Thread 4 (Thread 0x7fa13fdf9700 (LWP 2531)): #0 0x7fa1690e949d in poll () at /lib64/libc.so.6 #1 0x7fa163ce4314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa163ce442c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa169c0732b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa169bb4fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa1699eff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa1699f49e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fa165118734 in start_thread () at /lib64/libpthread.so.0 #8 0x7fa1690f1d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fa14da01700 (LWP 2498)): #0 0x7fa1690e551d in read () at /lib64/libc.so.6 #1 0x7fa163d24670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa163ce3e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa163ce42a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa163ce442c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fa169c0732b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fa169bb4fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fa1699eff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fa16a2771d5 in () at /usr/lib64/libQt5DBus.so.5 #9 0x7fa1699f49e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fa165118734 in start_thread () at /lib64/libpthread.so.0 #11 0x7fa1690f1d3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fa14f847700 (LWP 2496)): #0 0x7fa1690e949d in poll () at /lib64/libc.so.6 #1 0x7fa1644073e2 in () at /usr/lib64/libxcb.so.1 #2 0x7fa164408fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fa151d5b839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fa1699f49e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fa165118734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fa1690f1d3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fa16f559900 (LWP 2488)): [KCrash Handler] #6 0x00438988 in KgpgCore::KgpgKeySubPrivate::KgpgKeySubPrivate(QString const&, unsigned int, QFlags, QFlags, QFlags, QDateTime const&, QString const&) (__m=std::memory_order_relaxed, this=0x30001) at /usr/include/c++/4.8/bits/atomic_base.h:496 #7 0x00438988 in KgpgCore::KgpgKeySubPrivate::KgpgKeySubPrivate(QString const&, unsigned int, QFlags, QFlags, QFlags, QDateTime const&, QString const&) (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:96 #8 0x00438988 in KgpgCore::KgpgKeySubPrivate::KgpgKeySubPrivate(QString const&, unsigned int, QFlags, QFlags, QFlags, QDateTime const&, QString const&) (this=0x30001) at /usr/include/qt5/QtCore/qbasicatomic.h:116 #9 0x00438988 in KgpgCore::KgpgKeySubPrivate::KgpgKeySubPrivate(QString const&, unsigned int, QFlags, QFlags, QFlags, QDateTime const&, QString const&) (this=0x30001) at /usr/include/qt5/QtCore/qrefcount.h:49 #10 0x00438988 in KgpgCore::KgpgKeySubPrivate::
[plasmashell] [Bug 373409] New: Plasma crash for no obvious reason
https://bugs.kde.org/show_bug.cgi?id=373409 Bug ID: 373409 Summary: Plasma crash for no obvious reason Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: edwardb_...@shaw.ca CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.27-2-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: What I was doing when the application crashed: - Nothing special or unusual at the time - doing common stuff with Firefox and/or Thunderbird. - I had rebooted the system (openSuSE 42.2) about fifteen minutes earlier, following updates to some core KDE packages. - I also had, on boot, kgpg segfault on me. On later attempts to run it, too. Bug#373408. - Note that, besides the standard default package repos, I also have the following enabled: kde-applications | http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_Leap_42.2/ kde-extra| http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.2/ So it is possible that I have an unstable mix of libraries present. I would be happy to install specific versions of whatever packages in order to help troubleshoot this; just let me know. Thanks. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7fe9041900 (LWP 2440))] Thread 36 (Thread 0x7f3e735da700 (LWP 6088)): #0 0x7f7fe1f770af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7fe2e5e65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7fe6d564eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f7fe6d56995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f7fe2e5d9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f7fe1f72734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7fe2771d3d in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7f7e8a5fc700 (LWP 5724)): #0 0x7f7fe1f770af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7fe2e5e65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7fe6d564eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f7fe6d56995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f7fe2e5d9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f7fe1f72734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7fe2771d3d in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7f7e8affd700 (LWP 5702)): #0 0x7f7fe1f770af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7fe2e5e65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7fe6d564eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f7fe6d56995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f7fe2e5d9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f7fe1f72734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7fe2771d3d in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7f7e8b7fe700 (LWP 5632)): #0 0x7f7fe1f770af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7fe2e5e65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7fe6d564eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f7fe6d56995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f7fe2e5d9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f7fe1f72734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7fe2771d3d in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f7e8bfff700 (LWP 5609)): #0 0x7f7fe1f770af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7fe2e5e65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7f2898b42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f7f2898edea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f7f2898945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f7f2898ee32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7f2898945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f7f2898ee32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f7f2898945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f7f2898ee32 in () at /usr/lib64/libKF5ThreadWeaver.
[plasmashell] [Bug 384824] New: System Tray Settings > Entries > Hide Dropbox reliably crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=384824 Bug ID: 384824 Summary: System Tray Settings > Entries > Hide Dropbox reliably crashes Plasma Product: plasmashell Version: 5.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: edwardb_...@shaw.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.4.87-18.29-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: System Tray Settings > Entries > Hide Dropbox pretty reliably crashes Plasma. It may not be 100%, but at least pretty close. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdab44a9900 (LWP 4776))] Thread 14 (Thread 0x7fd9db0a7700 (LWP 5643)): #0 0x7fdaad1410bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdaae26e57b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fdab1f6620b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fdab1f683b5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdaae26d74d in () at /usr/lib64/libQt5Core.so.5 #5 0x7fdaad13c744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fdaadb79aad in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fd9d98a4700 (LWP 5642)): #0 0x7fdaad1410bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdaae26e57b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fdab1f6620b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fdab1f683b5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdaae26d74d in () at /usr/lib64/libQt5Core.so.5 #5 0x7fdaad13c744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fdaadb79aad in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fd9b103e700 (LWP 5484)): #0 0x7fdaad1410bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdaae26e57b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fdab1f6620b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fdab1f683b5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdaae26d74d in () at /usr/lib64/libQt5Core.so.5 #5 0x7fdaad13c744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fdaadb79aad in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fd9b083d700 (LWP 5476)): #0 0x7fdaad1410bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdaae26e57b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fdab1f6620b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fdab1f683b5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdaae26d74d in () at /usr/lib64/libQt5Core.so.5 #5 0x7fdaad13c744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fdaadb79aad in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fd9a7fff700 (LWP 5184)): #0 0x7fdaadb6d28d in read () at /lib64/libc.so.6 #1 0x7fdaa5b23073 in () at /usr/lib64/tls/libnvidia-tls.so.384.69 #2 0x7fdaa8c3b670 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fdaa8bfae49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fdaa8bfb2a8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fdaa8bfb42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fdaae47713b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fdaae424c2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fdaae26902a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7fdaae26d74d in () at /usr/lib64/libQt5Core.so.5 #10 0x7fdaad13c744 in start_thread () at /lib64/libpthread.so.0 #11 0x7fdaadb79aad in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fd9da0a5700 (LWP 4989)): #0 0x7fdaad1410bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdaae26e57b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fdab1f6620b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fdab1f683b5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdaae26d74d in () at /usr/lib64/libQt5Core.so.5 #5 0x7fdaad13c744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fdaadb79aad in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fd9e20a5700 (LWP 4987)): #0 0x7fdaad1410bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdaae26e57b in QWaitCondition::wait(QMutex
[amarok] [Bug 377854] New: Amarok crashes while querying MusicBrainz to update album tags
https://bugs.kde.org/show_bug.cgi?id=377854 Bug ID: 377854 Summary: Amarok crashes while querying MusicBrainz to update album tags Product: amarok Version: 2.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: edwardb_...@shaw.ca Target Milestone: 2.9 Application: amarok (2.8.0) KDE Platform Version: 4.14.30 Qt Version: 4.8.6 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Querying MusicBrainz in order to update tags on Amy Winehouse's album "Lioness: Hidden Treasures". Crash happens consistently for this album in particular, with the progress bar at about fifty percent. Does not happen with other albums. My offhand guess: MusicBrainz is returning malformed data, and amarok is not catching the resulting error and handling it gracefully. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f12fbda8940 (LWP 12823))] Thread 23 (Thread 0x7f1246106700 (LWP 12857)): #0 0x7f12f767d0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f12f912c066 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f12f4a6d69c in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f12f4a70133 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #5 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #6 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #7 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #8 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #9 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #10 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #11 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #12 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #13 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #14 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #15 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #16 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #17 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #18 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #19 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #20 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #21 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #22 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #23 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #24 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #25 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #26 0x7f12f4a6ee4f in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #27 0x7f12f912bb7f in () at /usr/lib64/libQtCore.so.4 #28 0x7f12f7678734 in start_thread () at /lib64/libpthread.so.0 #29 0x7f12f8a6dd3d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f129685e700 (LWP 12854)): #0 0x7f12f767d0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f12f912c066 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f12f4a6d69c in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f12f4a70133 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #5 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #6 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #7 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #8 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #9 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #10 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #11 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.so.4 #12 0x7f12f4a6ee4f in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #13 0x7f12f912bb7f in () at /usr/lib64/libQtCore.so.4 #14 0x7f12f7678734 in start_thread () at /lib64/libpthread.so.0 #15 0x7f12f8a6dd3d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f129705f700 (LWP 12852)): #0 0x7f12f767d0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f12f912c066 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f12f4a6d69c in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f12f4a70133 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f12f4a7014c in () at /usr/lib64/libthreadweaver.s
[kdenlive] [Bug 378953] New: Effect "Freeze" stops working after overlay
https://bugs.kde.org/show_bug.cgi?id=378953 Bug ID: 378953 Summary: Effect "Freeze" stops working after overlay Product: kdenlive Version: 16.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: edward.l...@gmail.com Target Milestone: --- I have a MKV file that I wish to freeze on a certain frame. I apply the Freeze (and a Mute) and it holds the frame. I then take a PNG and place it on top of this MKV (no transitions/composites/affines). The image shows, and so does the video under that, but the Freeze effect no longer holds the frame; the animation continues. When I remove the image from this track, the Freeze still doesn't hold the frame. I have to restart the whole thing before Freeze takes affect again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379357] New: Plasma crash on switching virtual desktop
https://bugs.kde.org/show_bug.cgi?id=379357 Bug ID: 379357 Summary: Plasma crash on switching virtual desktop Product: plasmashell Version: 5.9.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: edwardb_...@shaw.ca CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.4.57-18.3-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I just switched virtual desktop with the pager widget. I do a lot of virtual-desktop switching. I get a crash like this maybe once a month or so. Much more often, plasma just freezes: individual windows are still live, but the taskbar, menu, systray, desktop are frozen. That happens probably a couple times a week. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f02fd355900 (LWP 18067))] Thread 19 (Thread 0x7f01ab7fe700 (LWP 18356)): #0 0x7f02f606f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f02f719cc8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f02fae0700b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f02fae08f45 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f02f719c019 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f02f606a744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f02f6aa8d3d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f01b1340700 (LWP 25168)): #0 0x7f02f606f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f02f719cc8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f02fae0700b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f02fae08f45 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f02f719c019 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f02f606a744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f02f6aa8d3d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f01b674a700 (LWP 31545)): #0 0x7f02f606f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f02f719cc8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f02fae0700b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f02fae08f45 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f02f719c019 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f02f606a744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f02f6aa8d3d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f01b5f49700 (LWP 21874)): #0 0x7f02f606f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f02f719cc8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f02fae0700b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f02fae08f45 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f02f719c019 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f02f606a744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f02f6aa8d3d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f01b5748700 (LWP 21481)): #0 0x7f02f606f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f02f719cc8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f02fae0700b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f02fae08f45 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f02f719c019 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f02f606a744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f02f6aa8d3d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f02097fa700 (LWP 18816)): #0 0x7f02f606f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f02f719cc8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f02fae0700b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f02fae08f45 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f02f719c019 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f02f606a744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f02f6aa8d3d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f02237f6700 (LWP 18812)): #0 0x7f02f606f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f02f719cc8b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f02fae0700b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f02fae08f45 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f02f719c019
[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in
https://bugs.kde.org/show_bug.cgi?id=381929 Edward changed: What|Removed |Added CC||edwardb_...@shaw.ca -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374739] New: Video shrunk and not rendering
https://bugs.kde.org/show_bug.cgi?id=374739 Bug ID: 374739 Summary: Video shrunk and not rendering Product: kdenlive Version: 16.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: edward.l...@gmail.com Target Milestone: --- Created attachment 103282 --> https://bugs.kde.org/attachment.cgi?id=103282&action=edit This is what I see when I load this project. Ok, this is a very strange thing that has happened... Yesterday I was working on a video and all looked ok, but when trying to render it it would immediately say "Rendering finished in 00:00:00" and never produce a file. I tried all manner of formats, even a series of PNG exports, but nothing. It was anyways late so I decided on shutting it down and maybe starting it fresh tomorrow would solve things. But things seem to only get worse... Now the wide-screen video has gotten an aspect of 4:3 and ended up in the middle of the screen as if I had a 800x600 video in a 720p project. Also, the rendering still refuses to work. The video clip is from a JVC HD camera that calls the file .MTS and I've had no problems with it in the past. /Edward Kdenlive: 16.12.0 MLT: 6.5.0 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 374834] New: Akregator crash on close
https://bugs.kde.org/show_bug.cgi?id=374834 Bug ID: 374834 Summary: Akregator crash on close Product: akregator Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: edwardb_...@shaw.ca Target Milestone: --- Application: akregator (4.14.10) KDE Platform Version: 4.14.27 Qt Version: 4.8.6 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I had added a feed to akregator (from Firefox) (and which, for some reason, was imported six times), closed the window with the 'x' button, and then right-clicked on the systray icon and selected Quit. Akregator then crashed. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4ced1f9900 (LWP 18505))] Thread 10 (Thread 0x7f4c5e7fc700 (LWP 18624)): #0 0x7f4ce53c30af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4c6c35cd39 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f4c6c35d7d9 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f4ce53be734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4ce9cdfd3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f4c5effd700 (LWP 18623)): #0 0x7f4ce53c30af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4c6c35cd39 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f4c6c35d7d9 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f4ce53be734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4ce9cdfd3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f4c5f7fe700 (LWP 18622)): #0 0x7f4ce53c30af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4c6c35cd39 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f4c6c35d7d9 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f4ce53be734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4ce9cdfd3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f4c6cf9e700 (LWP 18617)): #0 0x7f4ce9cd749d in poll () at /lib64/libc.so.6 #1 0x7f4ce45a3314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4ce45a364a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4c81eae386 in () at /usr/lib64/libgio-2.0.so.0 #4 0x7f4ce45c79a5 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4ce53be734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f4ce9cdfd3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f4c6d79f700 (LWP 18616)): #0 0x7f4ce9cd749d in poll () at /lib64/libc.so.6 #1 0x7f4ce45a3314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4ce45a342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4ce45a3469 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4ce45c79a5 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4ce53be734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f4ce9cdfd3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f4c6e32c700 (LWP 18611)): #0 0x7f4ce9cdb8e9 in syscall () at /lib64/libc.so.6 #1 0x7f4ce45e49fe in g_cond_wait_until () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4ce4578f11 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4ce457949b in g_async_queue_timeout_pop () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4c824a6b4d in () at /usr/lib64/browser-plugins/libfreshwrapper-flashplayer.so #5 0x7f4c82493b0c in () at /usr/lib64/browser-plugins/libfreshwrapper-flashplayer.so #6 0x7f4ce53be734 in start_thread () at /lib64/libpthread.so.0 #7 0x7f4ce9cdfd3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4c83bd2700 (LWP 18583)): #0 0x7f4ce53c30af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4cd1f8495d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f4cd2239806 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f4ce53be734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4ce9cdfd3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4cc90f8700 (LWP 18509)): #0 0x7f4ce9cd749d in poll () at /lib64/libc.so.6 #1 0x7f4ce45a3314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4ce45a342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4ceb61ffce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f4ceb5f1d3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f4ceb5f2035 in QEven
[kdenlive] [Bug 374739] Video shrunk and not rendering
https://bugs.kde.org/show_bug.cgi?id=374739 --- Comment #1 from Edward --- apt-get shows that kdenlive and melt was upgraded. Kdenlive: 16.12.1 MLT: 6.5.0 The aspect ratio in the video is back to normal, which is nice, but it still doesn't render. I'm guessing it might be melt. Is kdenlive not finding melt, or is melt refusing to do its job without telling kdenlive what the error is, or could this problem be deeper? (ffmpeg, avconv, avformat, etc) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374739] Video shrunk and not rendering
https://bugs.kde.org/show_bug.cgi?id=374739 --- Comment #3 from Edward --- edward@gigafirm:~/Documents/scripts$ ./1_001.sh //STARTING RENDERING: false , false , "/usr/bin/melt" , "dv_pal_wide" , "avformat" , "-" , "consumer:" , "/home/edward/kdenlive/qna/1.mpg" , () , ("qscale=3", "aq=3", "subq=3", "cmp=1", "subcmp=1", "trellis=1", "bf=2", "threads=1", "real_time=-1") , 0 , 1408 edward@gigafirm:~/Documents/scripts$ I hope that is the information you are looking for. To me, it doesn't look verbose enough. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374739] Video shrunk and not rendering
https://bugs.kde.org/show_bug.cgi?id=374739 --- Comment #5 from Edward --- Thanks. Works now. Except that the HD profile MPEG-2 only produces sound, but using VOB works just as well. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 501496] Kinfocenter is not showing the graphical Disk Usage
https://bugs.kde.org/show_bug.cgi?id=501496 --- Comment #4 from Edward --- It’s not registering the amount of space used, the text works with the sensor but the actual graph part doesn’t. Sent from my iPhone > On Mar 17, 2025, at 4:01 PM, Nate Graham wrote: > > https://bugs.kde.org/show_bug.cgi?id=501496 > > --- Comment #3 from Nate Graham --- > What's wrong with the colored part? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 501496] Kinfocenter is not showing the graphical Disk Usage
https://bugs.kde.org/show_bug.cgi?id=501496 --- Comment #2 from Edward --- I am talking the pie chart display in system monitor. The colored part in the ring or on the desktop display. Not the text. Sent from my iPhone > On Mar 17, 2025, at 1:18 PM, Nate Graham wrote: > > https://bugs.kde.org/show_bug.cgi?id=501496 > > Nate Graham changed: > > What|Removed |Added > > Assignee|plasma-b...@kde.org |ksysguard-b...@kde.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO >Product|kinfocenter |plasma-systemmonitor > Component|general |general > CC||ahiems...@heimr.nl, > ||n...@kde.org, > ||plasma-b...@kde.org > > --- Comment #1 from Nate Graham --- > To my knowledge KDE's Info Center app never had a graphical visualizer of disk > space. > > Your screenshot shows two visualizations: one on the desktop and one in System > Monitor (not Info Center), and they both seem to agree that you've used 145 > GiB > of space. > > Can you clarify what the problem is? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 501496] New: Kinfocenter is not showing the graphical Disk Usage
https://bugs.kde.org/show_bug.cgi?id=501496 Bug ID: 501496 Summary: Kinfocenter is not showing the graphical Disk Usage Classification: Applications Product: kinfocenter Version: 6.3.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: papashre...@gmail.com CC: sit...@kde.org Target Milestone: --- Created attachment 179393 --> https://bugs.kde.org/attachment.cgi?id=179393&action=edit screenshot of dekstop for visual representation SUMMARY Graphical pie chart animation is not showing information corresponding to data. This has started since the last update on March 12, 2025. Screenshot included to show what I am describing. Desktop widget is directly pulled from Kinfocenter.. STEPS TO REPRODUCE 1. click on Application Launcher=>System=>Info Center OBSERVED RESULT All graphical pie chart animations work with the exception of Disk Usage. EXPECTED RESULT All graphical pie charts should show proper animation. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION Kernel Version: 6.12.19-1-lts (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 450316] New: Unable to Copy File Into the Same Directory using Projects Viewer
https://bugs.kde.org/show_bug.cgi?id=450316 Bug ID: 450316 Summary: Unable to Copy File Into the Same Directory using Projects Viewer Product: kdevelop Version: git master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ekigw...@gmail.com Target Milestone: --- Copying a file into the same directory causes the "File Already Exists" dialog to popup and provide the user and opportunity to rename the file. Before a user can get around to renaming the file, a modal Kdevelop "Copying" dialog pops up and blocks input to the file rename dialog. This last pop up is a copy progress indicator with a pause and a stop button. STEPS TO REPRODUCE 1. Open a project 2. Using the Projects UI viewer right click a file and choose copy in context menu 3. Using the Projects UI viewer right click directory containing file in previous step and select paste OBSERVED RESULT - Rename dialog pops up but user cannot interact with it. - Kdevelop copying notification block forever until it is stopped. EXPECTED RESULT - Rename dialog modal to Copying progress dialog which is turn modal to Kdevelop main window - Ability to rename file -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 450316] Unable to Copy File Into the Same Directory using Projects Viewer
https://bugs.kde.org/show_bug.cgi?id=450316 --- Comment #2 from Edward Kigwana --- I was unaware of the that bug. This is a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 446077] VLC player does not stream video from Samba share with kio-fuse
https://bugs.kde.org/show_bug.cgi?id=446077 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com --- Comment #36 from Edward Oubrayrie --- >From what I understand, there's a lot of progress with 5.27 release in configuring global shortcuts, both in Plasma as Nate said, and in apps with the Portal support https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/80 However there's no progress on Keyboard input (macros). As workaround, in addition to what's mentioned in https://wiki.archlinux.org/title/Input_remap_utilities there is also https://github.com/snyball/Hawck, but these tools are much harder to use and can make your system unusable, unlike the basic key input functionality in the old KCM. Even after reading https://blog.martin-graesslin.com/blog/2016/12/how-input-works-keyboard-input/ something is not clear: => Can something be done in Kwin? Is even the compositor not permitted to inject keyboard events in the Wayland architecture? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464132] One pixel overlap when enabling screen
https://bugs.kde.org/show_bug.cgi?id=464132 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460404] [Regression]: Kwin 5.26.0 uses software renderer instead of GLX
https://bugs.kde.org/show_bug.cgi?id=460404 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] New: Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 Bug ID: 466373 Summary: Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Testing Edition Assignee: neon-b...@kde.org Reporter: edoubray...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Qt client apps using system Qt 5.15.8 still use the old downscaling mechanism to deal with fractional scaling, instead of wp-fractional-scale-v1, leading to visual artefacts. STEPS TO REPRODUCE 1. Set "Scale" to fractional eg 135% in Display Configuration 2. Open a Qt app OBSERVED RESULT App is upscaled to 2x then downscaled. This produces aliasing artifacts as detailed previously here [1] EXPECTED RESULT Native scaling... like what is done by XWayland in "Apply scaling themselves" mode. See attached picture. On the left is XWayland (Platfom=xcb) and on the right Wayland. SOFTWARE/OS VERSIONS KDE Neon based on ubuntu 22.04.2 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 libqt5core5a Version: 5.15.8+p22.04+tunstable+git20230209.0323-0 python3-pyqt5 Version: 5.15.9+dfsg-1+22.04+jammy+unstable+build21 ADDITIONAL INFORMATION I believe the previous scaling is offered by Qt since 5.6 and is described here [2] and [3]. And the new one was announced by Nate here [4]. I think the KWin part landed: ``` > wayland-info | rg frac interface: 'wp_fractional_scale_manager_v1', version: 1, name: 10 ``` but maybe the Qt patches were not added to Neon's patch collection? Is this [5] related? how can I verify if the Qt5 client libs have support? I attach the small PyQt sample [6] used to show that the scale given to the app is 2x and the screen geometry and physicalDotsPerInch is fake (dpi 115.834 instead of 163), with system Qt 5.15.8. [1]: https://www.reddit.com/r/kde/comments/lficfe/wayland_fractional_scaling_may_be_sort_of_a/ [2]: https://www.qt.io/blog/2015/01/27/qt-weekly-24-high-dpi-qtwayland [3]: https://www.qt.io/blog/2016/01/26/high-dpi-support-in-qt-5-6 [4]: https://pointieststick.com/2022/12/16/this-week-in-kde-wayland-fractional-scaling-oh-and-we-also-fixed-multi-screen/ [5]: https://invent.kde.org/qt/qt/qtwayland/-/commit/23d3fc7 [6]: https://gist.github.com/eddy-geek/2a682a415abb5d351537ae3fc865dffd -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #1 from Edward Oubrayrie --- Created attachment 156688 --> https://bugs.kde.org/attachment.cgi?id=156688&action=edit Shows clear scaling with XWayland(XCB), artifacts with Wayland -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #2 from Edward Oubrayrie --- Created attachment 156689 --> https://bugs.kde.org/attachment.cgi?id=156689&action=edit image used to find aliasing issues The previous screenshot has been obtained by running code in [6] with dpitest1px.png in the folder and this command: > QT_QPA_PLATFORM=xcb /usr/bin/python3 ./qt6-dpi.py 5 for the left window, and without ...xcb for the right window to better see the difference, beware that most software (Chrome, Firefox, Eye of Gnome) apply antialiasing. Gwenview is fine... without fractional scaling ;-) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #4 from Edward Oubrayrie --- Created attachment 156690 --> https://bugs.kde.org/attachment.cgi?id=156690&action=edit plasma 5.27.1 - artifacts with both XWayland(XCB) and Wayland I had not rebooted after 5.27.1 final so I was probably mostly on Neon testing from 2023-02-17 So, attaching this as the current status. Unfortunately 5.27.1 changes nothing for the platform=wayland scenario -- and it seems to regress the platform=xcb XWayland scenario, making it blurry (not that I care) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 Edward Oubrayrie changed: What|Removed |Added Ever confirmed|0 |1 Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #5 from Edward Oubrayrie --- (In reply to Nicolas Fella from comment #3) So, nothing can be done on this before Plasma 6 ? Am I missing something or is the only thing missing a backport of https://invent.kde.org/qt/qt/qtwayland/-/commit/23d3fc7 into branch `kde/5.15`? If I were to try to submit a PR for this, it would be rejected? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #6 from Edward Oubrayrie --- (I understand upstream won't backport it, this why I'm asking specifically about the KDE Qt patch collection or whatever the name of what goes into Neon) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417441] Update ~/.xsettingsd file for all changes that affect GTK apps
https://bugs.kde.org/show_bug.cgi?id=417441 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 459257] New: libkf5auth5 depends on unstable libpolkit-qt5
https://bugs.kde.org/show_bug.cgi?id=459257 Bug ID: 459257 Summary: libkf5auth5 depends on unstable libpolkit-qt5 Classification: Unclassified Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Testing Edition Assignee: neon-b...@kde.org Reporter: edoubray...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Neon 22.04 (I know it's not released yet, feel free to close this if useless) some testing packages depend on unstable ones. can be seen on http://archive.neon.kde.org/testing/dists/jammy/main/binary-amd64/Packages STEPS TO REPRODUCE sudo apt install libkf5auth5 libkf5authcore5 libkf5auth-data OBSERVED RESULT Some packages could not be installed. The following packages have unmet dependencies: libkf5authcore5 : Depends: libpolkit-qt5-1-1 (>= 0.114.0+p22.04+tunstable+git20220908.1608) but 0.114.0+p22.04+tstable+git20220908.1608-0 is to be installed E: Unable to correct problems, you have held broken packages. EXPECTED RESULT installs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.0-051900-generic KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 456968] KDE Wallet Manager window is blank
https://bugs.kde.org/show_bug.cgi?id=456968 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com --- Comment #11 from Edward Oubrayrie --- For the KDE Neon testing situation, mentioning Bug 459257 (libkf5auth5 broken) which may be related. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442265] Opening an app from konsole has no activation environment set
https://bugs.kde.org/show_bug.cgi?id=442265 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459213] Bring to front system settings pages when selecting them from the app menu when system settings is already running minimized
https://bugs.kde.org/show_bug.cgi?id=459213 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460268] Opening file manager from Disks & Devices doesn't raise Dolphin window on Wayland
https://bugs.kde.org/show_bug.cgi?id=460268 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 460283] New: Kate does not raise in wayland, missing xdg_activation_v1 protocol
https://bugs.kde.org/show_bug.cgi?id=460283 Bug ID: 460283 Summary: Kate does not raise in wayland, missing xdg_activation_v1 protocol Classification: Applications Product: kate Version: 22.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: edoubray...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 0. In a wayland session (tested with Plasma 5.26) 1. Start kate, minimize or hide it 2. Open kate from start menu. A window displays "Session 'x' is already opened in another Kate instance." 3. Click "Switch to instance" Another scenario 0. In a wayland session (tested with Plasma 5.26) 1. Start kate, minimize or hide it 2. Open any kate file eg "foo.txt" from start menu. OBSERVED RESULT Kate window is not visible. EXPECTED RESULT Kate window is raised to forefront. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 22.04 KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Xref https://invent.kde.org/plasma/kwin/-/issues/39 for more examples. protocol https://wayland.app/protocols/xdg-activation-v1 https://invent.kde.org/system/dolphin/-/merge_requests/461 for a similar dolphin fix. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460318] Wayland activation bugs
https://bugs.kde.org/show_bug.cgi?id=460318 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 489518] New: Opening an existing file or creating a new file doesn't get you to the workspace.
https://bugs.kde.org/show_bug.cgi?id=489518 Bug ID: 489518 Summary: Opening an existing file or creating a new file doesn't get you to the workspace. Classification: Applications Product: krita Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: crash Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: edwardmo...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY This is Krita 5.2.3, not 5.2.3_Beta. (The option is not in "version") If krita isn't already running, opening an existing file or creating a new file doesn't get you to the workspace and canvas, it just freezes until any item on the menu bar is clicked followed by another tap on the screen. Also, my toolbar is at the top when krita starts, instead of the bottom where I set it to be. It goes back to normal after I get in to my workspace and / or go back to the home screen to create a new file. I've recorded a video of this happening: https://drive.google.com/file/d/1bJloDN5nhqJHJ6NtY5ch5QVW_fF58Qh7/view?usp=drive_link I did not have this issue in 5.2.3_beta. STEPS TO REPRODUCE 1. Close Krita, make sure it's not running in background. 2. Start krita. 3. Create a new image or open an existing image. OBSERVED RESULT Screen freezes EXPECTED RESULT Krita should open your workspace and canvas SOFTWARE/OS VERSIONS Android: 14 This is Krita 5.2.3, not 5.2.3_Beta. (The option is not in "version") Device: Galaxy Tab S9-Ultra ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 489719] New: Play back stops after 5 or so minutes. Image freezes but time line continues. Can be fixed by inserting a cut in the video.
https://bugs.kde.org/show_bug.cgi?id=489719 Bug ID: 489719 Summary: Play back stops after 5 or so minutes. Image freezes but time line continues. Can be fixed by inserting a cut in the video. Classification: Applications Product: kdenlive Version: 24.05.1 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: edwardj.me...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Load video that's longer than 5 min. Move it on to V1. Play it. 2. After a variable time 5 - 8min playback freezes. Moving the cursor does not change the screen image. 3. Can be fixed by inserting a Cut ( Shift R). video will play and edit normally. OBSERVED RESULT 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.
[kmail2] [Bug 481283] Kmail crashes when I try to open mail
https://bugs.kde.org/show_bug.cgi?id=481283 Edward Torvalds changed: What|Removed |Added CC||wg51r...@mailer.me -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481283] Kmail crashes when I try to open mail
https://bugs.kde.org/show_bug.cgi?id=481283 --- Comment #2 from Edward Torvalds --- Created attachment 166302 --> https://bugs.kde.org/attachment.cgi?id=166302&action=edit New crash information added by DrKonqi kmail (5.20.3 (22.04.3)) using Qt 5.15.3 I have installed Plasma 5.27.1 on Kubuntu 22.04 using backports PPA. Post that system has become more unstable. Even Korganiser does not shows pop-up reminder. -- Backtrace (Reduced): #4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 [...] #6 0x77b880026877 in spd_execute_command_with_list_reply () at /lib/x86_64-linux-gnu/libspeechd.so.2 [...] #10 0x77b8934180d3 in QTextToSpeech::QTextToSpeech(QString const&, QObject*) () at /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #11 0x77b8986cd946 in KPIMTextEdit::TextToSpeech::reloadSettings() () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #12 0x77b8986cda54 in KPIMTextEdit::TextToSpeech::self() () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481283] Kmail crashes when I try to open mail
https://bugs.kde.org/show_bug.cgi?id=481283 Edward Torvalds changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|UNMAINTAINED|--- --- Comment #3 from Edward Torvalds --- I just want to add a 'LOL'. From the stack trace, I can see Kmail is crashing because of speech dispatcher. This issue has annoyed me for months. I have uninstalled all speech dispatcher related packages and Kmail wouldn't crash anymore. Glorious days of software engineering. Next issue for me to fix is to figure out why Korganiser won't show notifications for events. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 482229] New: Korganiser won't show notifications
https://bugs.kde.org/show_bug.cgi?id=482229 Bug ID: 482229 Summary: Korganiser won't show notifications Classification: Applications Product: korganizer Version: 5.20.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-b...@kde.org Reporter: wg51r...@mailer.me Target Milestone: --- SUMMARY *** Korganiser is not crashing. But it is not showing notifications for events. I used to get a dialog for my events. I had face this issue on Plasma 5.25 and still facing the issue on 5.27. *** STEPS TO REPRODUCE 1. Create an event and add reminder. 2. Wait for it to trigger 3. Notice no notification OBSERVED RESULT Notification not showing up for events EXPECTED RESULT Notification should be shown for events SOFTWARE/OS VERSIONS Linux/KDE Plasma: kUbuntu 22.04 (all updates installed) (available in About System) KDE Plasma Version: 5.27.10 (installed using backports PPA) KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448224] Main menu position drawn in wrong place (Wayland only)
https://bugs.kde.org/show_bug.cgi?id=448224 Edward Kigwana changed: What|Removed |Added CC||ekigw...@gmail.com --- Comment #7 from Edward Kigwana --- I still see this problem on wayland KF6 git yesterday but glaring when an app is stretched across two monitors -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413771] Menu does not show in right place with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=413771 Edward Kigwana changed: What|Removed |Added CC||ekigw...@gmail.com Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #5 from Edward Kigwana --- I still see this on latest wayland in git -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 444085] Popup menus from menu bar show up in wrong place.
https://bugs.kde.org/show_bug.cgi?id=444085 Edward Kigwana changed: What|Removed |Added CC||ekigw...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Edward Kigwana --- *** This bug has been marked as a duplicate of bug 413771 *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413771] Menu does not show in right place with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=413771 Edward Kigwana changed: What|Removed |Added CC||bes...@gmail.com --- Comment #6 from Edward Kigwana --- *** Bug 444085 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451168] Context menus show up on the wrong monitor, or not at all.
https://bugs.kde.org/show_bug.cgi?id=451168 Edward Kigwana changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||ekigw...@gmail.com --- Comment #2 from Edward Kigwana --- *** This bug has been marked as a duplicate of bug 413771 *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413771] Menu does not show in right place with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=413771 Edward Kigwana changed: What|Removed |Added CC||tpoke.ferr...@gmail.com --- Comment #7 from Edward Kigwana --- *** Bug 451168 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448224] Main menu position drawn in wrong place (Wayland only)
https://bugs.kde.org/show_bug.cgi?id=448224 Edward Kigwana changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #8 from Edward Kigwana --- *** This bug has been marked as a duplicate of bug 413771 *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413771] Menu does not show in right place with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=413771 Edward Kigwana changed: What|Removed |Added CC||private_l...@yahoo.com --- Comment #8 from Edward Kigwana --- *** Bug 448224 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413771] Menu does not show in right place with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=413771 Edward Kigwana changed: What|Removed |Added CC||mco78@gmail.com --- Comment #9 from Edward Kigwana --- *** Bug 466505 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 466505] Menu does not appears under item
https://bugs.kde.org/show_bug.cgi?id=466505 Edward Kigwana changed: What|Removed |Added CC||ekigw...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Edward Kigwana --- *** This bug has been marked as a duplicate of bug 413771 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 448498] Context menu appears in the middle of the screen if opened with stylus on Wayland
https://bugs.kde.org/show_bug.cgi?id=448498 Edward Kigwana changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ekigw...@gmail.com --- Comment #1 from Edward Kigwana --- *** This bug has been marked as a duplicate of bug 413771 *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413771] Menu does not show in right place with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=413771 Edward Kigwana changed: What|Removed |Added CC||hartva...@gmail.com --- Comment #10 from Edward Kigwana --- *** Bug 448498 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwayland] [Bug 444085] Popup menus from menu bar show up in wrong place.
https://bugs.kde.org/show_bug.cgi?id=444085 Edward Kigwana changed: What|Removed |Added Latest Commit||e6588e220ee3769ce715ced9bed ||77352bed89f8e CC||kwin-bugs-n...@kde.org Product|frameworks-kxmlgui |kwayland Component|general |server Assignee|kdelibs-b...@kde.org|mgraess...@kde.org Platform|Fedora RPMs |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413771] Menu does not show in right place with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=413771 --- Comment #11 from Edward Kigwana --- Doe anyone know where I can look for the menu positioning code? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481283] New: Kmail crashes when I try to open mail
https://bugs.kde.org/show_bug.cgi?id=481283 Bug ID: 481283 Summary: Kmail crashes when I try to open mail Classification: Applications Product: kmail2 Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: wg51r...@mailer.me Target Milestone: --- Application: kmail (5.20.3 (22.04.3)) Qt Version: 5.15.3 Frameworks Version: 5.104.0 Operating System: Linux 6.7.4-1-liquorix-amd64 x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: This hapens every time when I click on the email in the inbox. I had face this issue on Plasma 5.25 and still facing the issue on 5.27. Using IMAP connection. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #5 0x72955bff6aca in () at /lib/x86_64-linux-gnu/libspeechd.so.2 #6 0x72955bff7877 in spd_execute_command_with_list_reply () at /lib/x86_64-linux-gnu/libspeechd.so.2 #7 0x72956006d07a in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqtexttospeech_speechd.so #8 0x72956006f073 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqtexttospeech_speechd.so #9 0x729572c12cf1 in () at /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #10 0x729572c130d3 in QTextToSpeech::QTextToSpeech(QString const&, QObject*) () at /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #11 0x729577412946 in KPIMTextEdit::TextToSpeech::reloadSettings() () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #12 0x729577412a54 in KPIMTextEdit::TextToSpeech::self() () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #13 0x7295774156f3 in KPIMTextEdit::TextToSpeechInterface::TextToSpeechInterface(KPIMTextEdit::TextToSpeechWidget*, QObject*) () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #14 0x7295774137d1 in KPIMTextEdit::TextToSpeechWidget::TextToSpeechWidget(QWidget*) () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #15 0x729577f7af79 in MessageViewer::ViewerPrivate::createWidgets() () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi5 #16 0x729577f8db98 in MessageViewer::ViewerPrivate::ViewerPrivate(MessageViewer::Viewer*, QWidget*, KActionCollection*) () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi5 #17 0x729577f75a96 in MessageViewer::Viewer::Viewer(QWidget*, QWidget*, KActionCollection*) () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi5 #18 0x7295825eb1fb in KMReaderWin::KMReaderWin(QWidget*, QWidget*, KActionCollection*) () at /lib/x86_64-linux-gnu/libkmailprivate.so.5 #19 0x72958261d1db in KMReaderMainWin::KMReaderMainWin(MessageViewer::Viewer::DisplayFormatMessage, bool, QString const&) () at /lib/x86_64-linux-gnu/libkmailprivate.so.5 #20 0x729582628d2a in KMMainWidget::slotMessageActivated(Akonadi::Item const&) () at /lib/x86_64-linux-gnu/libkmailprivate.so.5 #21 0x729578ef1793 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7295787abc19 in MessageList::Pane::messageActivated(Akonadi::Item const&) () at /lib/x86_64-linux-gnu/libKF5MessageList.so.5abi1 #23 0x729578ef1793 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x72957872cf39 in MessageList::Widget::messageActivated(Akonadi::Item const&) () at /lib/x86_64-linux-gnu/libKF5MessageList.so.5abi1 #25 0x7295787b95da in MessageList::Widget::viewMessageActivated(MessageList::Core::MessageItem*) () at /lib/x86_64-linux-gnu/libKF5MessageList.so.5abi1 #26 0x729579bafe79 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x729579c5d422 in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x729578eb9b9a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x729579b6c702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x729579b74364 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x729578eb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x729579b72e47 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x729579bc8d40 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x729579bcbfd5 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x729579b6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x729578eb9e3a in QCoreA
[kontact] [Bug 461532] Kontact will crash when opening. Choosing "Restart application" mostly works.
https://bugs.kde.org/show_bug.cgi?id=461532 --- Comment #1 from Edward Torvalds --- Created attachment 166111 --> https://bugs.kde.org/attachment.cgi?id=166111&action=edit New crash information added by DrKonqi korganizer (5.20.3 (22.04.3)) using Qt 5.15.3 app crashes when trying to add new even by double click on day -- Backtrace (Reduced): #4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 [...] #6 0x7c273c036877 in spd_execute_command_with_list_reply () from /lib/x86_64-linux-gnu/libspeechd.so.2 [...] #10 0x7c2756ac80d3 in QTextToSpeech::QTextToSpeech(QString const&, QObject*) () from /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #11 0x7c2757d32946 in KPIMTextEdit::TextToSpeech::reloadSettings() () from /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #12 0x7c2757d32a54 in KPIMTextEdit::TextToSpeech::self() () from /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 461532] Kontact will crash when opening. Choosing "Restart application" mostly works.
https://bugs.kde.org/show_bug.cgi?id=461532 Edward Torvalds changed: What|Removed |Added CC||wg51r...@mailer.me -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept rapidly-typed keystrokes for first invocation after login, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Edward Donovan changed: What|Removed |Added CC|kde-b...@numble.net | -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 485179] New: Crashes when opening .ods file created by Libreoffice
https://bugs.kde.org/show_bug.cgi?id=485179 Bug ID: 485179 Summary: Crashes when opening .ods file created by Libreoffice Classification: Applications Product: calligrasheets Version: 3.2.1 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-sheets-bugs-n...@kde.org Reporter: wg51r...@mailer.me Target Milestone: --- Application: calligrasheets (3.2.1) Qt Version: 5.15.3 Frameworks Version: 5.104.0 Operating System: Linux 6.7.12-1-liquorix-amd64 x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.4 LTS DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Every time I open .ods file created by Libreoffice Calc, Calligra sheets crashes. The crash can be reproduced every time. -- Backtrace: Application: Calligra Sheets (calligrasheets), signal: Segmentation fault [KCrash Handler] #4 0x0171 in ?? () #5 0x7e5cf4b4cd62 in Calligra::Sheets::StyleManager::~StyleManager() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #6 0x7e5cf4b1f2c3 in Calligra::Sheets::Map::~Map() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #7 0x7e5cf4b0c43f in Calligra::Sheets::DocBase::~DocBase() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #8 0x7e5cf4f28d5d in Calligra::Sheets::Doc::~Doc() () from /lib/x86_64-linux-gnu/libcalligrasheetscommon.so.17 #9 0x7e5d06fa9881 in KoMainWindow::setRootDocument(KoDocument*, KoPart*, bool) () from /lib/x86_64-linux-gnu/libkomain.so.17 #10 0x7e5d06fb2395 in KoMainWindow::closeEvent(QCloseEvent*) () from /lib/x86_64-linux-gnu/libkomain.so.17 #11 0x7e5d061af4ee in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7e5d04f965bd in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #13 0x7e5d0616c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7e5d06f9034d in KoApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libkomain.so.17 #15 0x7e5d05cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7e5d061aa800 in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7e5d061cc128 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7e5d0616c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7e5d06f9034d in KoApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libkomain.so.17 #20 0x7e5d05cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7e5d0453df1d in QGuiApplicationPrivate::processCloseEvent(QWindowSystemInterfacePrivate::CloseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7e5d04516a2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #23 0x7e5cffaf8d6e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #24 0x7e5d03520d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7e5d03576258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7e5d0351e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7e5d05d130b8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7e5d05cb875b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7e5d05cc0cf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7e5d07027d39 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_calligrasheets.so #31 0x7e5d06c29d90 in __libc_start_call_main (main=main@entry=0x5d593ec26060, argc=argc@entry=2, argv=argv@entry=0x7ffd045d2f38) at ../sysdeps/nptl/libc_start_call_main.h:58 #32 0x7e5d06c29e40 in __libc_start_main_impl (main=0x5d593ec26060, argc=2, argv=0x7ffd045d2f38, init=, fini=, rtld_fini=, stack_end=0x7ffd045d2f28) at ../csu/libc-start.c:392 #33 0x5d593ec26095 in ?? () [Inferior 1 (process 30530) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446389] On Wayland, KWin doesn't differentiate numberpad number key shortcuts from above-the-letters number key shortcuts
https://bugs.kde.org/show_bug.cgi?id=446389 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=475605 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 465688] "Fit" on fractionally scaled wayland display doesn't actually fit
https://bugs.kde.org/show_bug.cgi?id=465688 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 487232] New: Taskbar no "control panel"
https://bugs.kde.org/show_bug.cgi?id=487232 Bug ID: 487232 Summary: Taskbar no "control panel" Classification: Plasma Product: kded-appmenu Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Titlebar menu button/popup Assignee: plasma-b...@kde.org Reporter: eddisch2...@gmail.com Target Milestone: --- Created attachment 169614 --> https://bugs.kde.org/attachment.cgi?id=169614&action=edit Screenshot Of Taskbar Icons *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Taskbar has no icons (wifi bluetooth thats what i mean) STEPS TO REPRODUCE 1. Do something?? 2. 3. OBSERVED RESULT I cant open the "show hidden icons" thing EXPECTED RESULT It would open. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A KDE Neon: 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION If i hover my moune over the "blob" i can "resize it" but if i release it it goes back to the blob thing. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 487232] Taskbar no "control panel"
https://bugs.kde.org/show_bug.cgi?id=487232 Edward Schreiber changed: What|Removed |Added CC||eddisch2...@gmail.com Platform|Other |Neon -- You are receiving this mail because: You are watching all bug changes.