[kate] [Bug 362810] 15.12.3: Spelling - "Add to dictionary" does not remember added words
https://bugs.kde.org/show_bug.cgi?id=362810 Sebastian Schrader changed: What|Removed |Added CC||sebastian.schrader@ossmail. ||de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys
https://bugs.kde.org/show_bug.cgi?id=344969 --- Comment #39 from rmbg --- Leslie, your shift + delete patch works fine... any chance of having it in 5.7.3 build? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366005] New: Plasma crashed on search
https://bugs.kde.org/show_bug.cgi?id=366005 Bug ID: 366005 Summary: Plasma crashed on search Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: barnabas.s...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-31-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Plasma shell is crashing every time when I search for something in menu or with Alt+f2. The error can be reproduced any number of times. I don't use any special setting everything installed from KUbuntu. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9ad8e8a8c0 (LWP 13701))] Thread 28 (Thread 0x7f99a7fff700 (LWP 13745)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9ad3c8caeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x242df70) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x242df50, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f9a198142bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f9a198184e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f9a1981346d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f9a19818542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f9a1981346d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f9a19818542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f9a1981346d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f9a19816353 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f9ad3c8b84e in QThreadPrivate::start (arg=0x7f99bc002b90) at thread/qthread_unix.cpp:331 #12 0x7f9ad2d786fa in start_thread (arg=0x7f99a7fff700) at pthread_create.c:333 #13 0x7f9ad35a1b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 27 (Thread 0x7f99c0ff9700 (LWP 13744)): [KCrash Handler] #6 0x7f99f0e79d1d in Baloo::DocumentTimeDB::get (this=this@entry=0x7f99c0ff87d0, docId=docId@entry=60282374260260908) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/documenttimedb.cpp:91 #7 0x7f99f0e89c76 in Baloo::Transaction::documentTimeInfo (this=this@entry=0x7f99c0ff8900, id=id@entry=60282374260260908) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:135 #8 0x7f99f12cef36 in Baloo::SearchStoreoperator() (rhs=, lhs=, __closure=) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/searchstore.cpp:95 #9 __gnu_cxx::__ops::_Val_comp_iter >::operator() (__val=, __it=, this=) at /usr/include/c++/5/bits/predefined_ops.h:169 #10 std::__unguarded_linear_insert > >(unsigned long long *, __gnu_cxx::__ops::_Val_comp_iter >) (__last=, __last@entry=0x7f999c305180, __comp=__comp@entry=...) at /usr/include/c++/5/bits/stl_algo.h:1823 #11 0x7f99f12cf006 in std::__insertion_sort > >(unsigned long long *, unsigned long long *, __gnu_cxx::__ops::_Iter_comp_iter >) (__first=__first@entry=0x7f999c305178, __last=__last@entry=0x7f999c3051e0, __comp=__comp@entry=...) at /usr/include/c++/5/bits/stl_algo.h:1850 #12 0x7f99f12d31a3 in std::__final_insertion_sort > > (__comp=..., __last=0x7f999c3051e0, __first=0x7f999c305178) at /usr/include/c++/5/bits/stl_algo.h:1885 #13 std::__sort > > (__comp=..., __last=0x7f999c3051e0, __first=0x7f999c305178) at /usr/include/c++/5/bits/stl_algo.h:1966 #14 std::sort > (__comp=..., __last=, __first=) at /usr/include/c++/5/bits/stl_algo.h:4729 #15 Baloo::SearchStore::exec (this=this@entry=0x7f99c0ff89f0, term=..., offset=0, limit=10, sortResults=) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/searchstore.cpp:98 #16 0x7f99f12c1bc2 in Baloo::Query::exec (this=this@entry=0x7f99c0ff8aa0) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/query.cpp:210 #17 0x7f99f14e2f2f in SearchRunner::match (this=this@entry=0x2cf38e0, context=..., type=..., category=...) at /build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/runners/baloo/baloosearchrunner.cpp:98 #18 0x
[drkonqi] [Bug 366004] New: drkonqi crash when I cancel installation of debug packages
https://bugs.kde.org/show_bug.cgi?id=366004 Bug ID: 366004 Summary: drkonqi crash when I cancel installation of debug packages Product: drkonqi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mustafa10...@gmail.com drkonqi crash when I cancel installation of debug packages, it can't install them (already reported), and when I press cancel it crashes with this backtrace: Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2191eca8c0 (LWP 4614))] Thread 2 (Thread 0x7f217d6e4700 (LWP 4615)): #0 0x7f218d52ca7d in read () from /lib64/libc.so.6 #1 0x7f2189813d00 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f21897d0b26 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f21897d0ff4 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f21897d116c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f218de53d1b in QEventDispatcherGlib::processEvents (this=0x7f21780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f218ddfd0ea in QEventLoop::exec (this=this@entry=0x7f217d6e3cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f218dc2ab83 in QThread::exec (this=) at thread/qthread.cpp:507 #8 0x7f218f213c49 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f218dc2f986 in QThreadPrivate::start (arg=0x7f218f487d20) at thread/qthread_unix.cpp:368 #10 0x7f218b6fe474 in start_thread () from /lib64/libpthread.so.0 #11 0x7f218d5393ed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2191eca8c0 (LWP 4614)): [KCrash Handler] #6 0x0042ea79 in DebugPackageInstaller::processFinished (this=0x1f9d410, exitCode=) at /usr/src/debug/plasma-workspace-5.7.90git~20160722T123413~6344754/drkonqi/debugpackageinstaller.cpp:116 #7 0x7f218de2b3ee in QtPrivate::QSlotObjectBase::call (a=0x7ffeff7c1c30, r=0x1f9d410, this=) at ../../src/corelib/kernel/qobject_impl.h:101 #8 QMetaObject::activate (sender=sender@entry=0x21d0aa0, signalOffset=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffeff7c1c30) at kernel/qobject.cpp:3723 #9 0x7f218de2b9a7 in QMetaObject::activate (sender=sender@entry=0x21d0aa0, m=m@entry=0x7f218e241200 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffeff7c1c30) at kernel/qobject.cpp:3602 #10 0x7f218dd3162f in QProcess::finished (this=this@entry=0x21d0aa0, _t1=, _t2=) at .moc/moc_qprocess.cpp:332 #11 0x7f218dd397d3 in QProcessPrivate::_q_processDied (this=0x220d980) at io/qprocess.cpp:1186 #12 0x7f218dd39939 in QProcess::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffeff7c1dd0) at .moc/moc_qprocess.cpp:213 #13 0x7f218de2b081 in QMetaObject::activate (sender=sender@entry=0x21cd990, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeff7c1dd0) at kernel/qobject.cpp:3740 #14 0x7f218de2b9a7 in QMetaObject::activate (sender=sender@entry=0x21cd990, m=m@entry=0x7f218e2456c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeff7c1dd0) at kernel/qobject.cpp:3602 #15 0x7f218dea5c5e in QSocketNotifier::activated (this=this@entry=0x21cd990, _t1=) at .moc/moc_qsocketnotifier.cpp:135 #16 0x7f218de37652 in QSocketNotifier::event (this=0x21cd990, e=0x7ffeff7c20a0) at kernel/qsocketnotifier.cpp:266 #17 0x7f218eaf5dbc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f218eafd561 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f218ddff138 in QCoreApplication::notifyInternal2 (receiver=0x21cd990, event=event@entry=0x7ffeff7c20a0) at kernel/qcoreapplication.cpp:988 #20 0x7f218de541ad in QCoreApplication::sendEvent (event=0x7ffeff7c20a0, receiver=) at ../../src/corelib/kernel/qcoreapplication.h:231 #21 socketNotifierSourceDispatch (source=0x1e24e70) at kernel/qeventdispatcher_glib.cpp:106 #22 0x7f21897d0e57 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x7f21897d10c0 in ?? () from /usr/lib64/libglib-2.0.so.0 #24 0x7f21897d116c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x7f218de53cff in QEventDispatcherGlib::processEvents (this=0x1e75af0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x7f218ddfd0ea in QEventLoop::exec (this=this@entry=0x7ffeff7c22c0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #27 0x7f218de059dc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #28 0x0041ea2c in main (argc=, argv=) at /usr/src/debug/plasma-workspace-5.7.90git~20160722T123413~6344754/drkonqi/main.cpp:170 Reproducible: Always
[drkonqi] [Bug 365468] Dr. Konqi fails to install debug symbols on Opensuse
https://bugs.kde.org/show_bug.cgi?id=365468 Mustafa Muhammad changed: What|Removed |Added CC||mustafa10...@gmail.com --- Comment #1 from Mustafa Muhammad --- Still affects me with git packages (21-7-2016) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366003] New: System-Settings crashed by setting/change the font (Tumbleweed)
https://bugs.kde.org/show_bug.cgi?id=366003 Bug ID: 366003 Summary: System-Settings crashed by setting/change the font (Tumbleweed) Product: systemsettings Version: 5.7.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: koellnerr...@gmail.com Application: systemsettings5 (5.7.2) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.6.4-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160720) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I changed the the font for the menu NotoSans 12 to 14 then I wanted to see the change. System-Settings chrashed. Thx for work. Ralf -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f626c13e8c0 (LWP 2541))] Thread 4 (Thread 0x7f623e953700 (LWP 2546)): #0 0x7f6263e9f09f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6245cf94c3 in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6245cf8c07 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6263e99474 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6267daf3ed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f624700 (LWP 2544)): #0 0x7f62639be0c4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f626397959c in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6263979f7b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f626397a16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f62686d1aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f626867976a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f626849f3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f6268fd39b5 in () at /usr/lib64/libQt5DBus.so.5 #8 0x7f62684a42d8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f6263e99474 in start_thread () at /lib64/libpthread.so.0 #10 0x7f6267daf3ed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f62586bf700 (LWP 2543)): #0 0x7f6267da6a1d in poll () at /lib64/libc.so.6 #1 0x7f6264712410 in () at /usr/lib64/libxcb.so.1 #2 0x7f62647141a9 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f625ac2a7b9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f62684a42d8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f6263e99474 in start_thread () at /lib64/libpthread.so.0 #6 0x7f6267daf3ed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f626c13e8c0 (LWP 2541)): [KCrash Handler] #6 0x7f625715c684 in KNotification::flags() const () at /usr/lib64/libKF5Notifications.so.5 #7 0x7f625717bec7 in () at /usr/lib64/libKF5Notifications.so.5 #8 0x7f6257181575 in () at /usr/lib64/libKF5Notifications.so.5 #9 0x7f62686a91a9 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #10 0x7f62565096a5 in () at /usr/lib64/libphonon4qt5.so.4 #11 0x7f62686a9cf9 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x7f626a24eaec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x7f626a253f8f in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f626867ba20 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7f626867d99c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #16 0x7f62686d16c3 in () at /usr/lib64/libQt5Core.so.5 #17 0x7f6263979e57 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #18 0x7f626397a0c0 in () at /usr/lib64/libglib-2.0.so.0 #19 0x7f626397a16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #20 0x7f62686d1acf in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7f626867976a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x7f6268681f6c in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #23 0x0040cc21 in () #24 0x7f6267ce7741 in __libc_start_main () at /lib64/libc.so.6 #25 0x0040cc99 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366002] New: kmail does not respect the use HTML instead of plain text setting
https://bugs.kde.org/show_bug.cgi?id=366002 Bug ID: 366002 Summary: kmail does not respect the use HTML instead of plain text setting Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: kos...@kosmas.gr When setting the prefer HTML instead of plain text, the messages are presented as HTML, but after restarting kmail the emails are presented as plain text. The setting still exists but it is not respected. If you disable it and re-enable it, it then presents the messages as HTML again. This happens every time I start kmail. Reproducible: Always Steps to Reproduce: 1. Select prefer HTML instead of plain text 2. See HTML messages 3. Restart kmail Actual Results: Messages are not seen as HTML, regardless of the setting to prefer HTML. Expected Results: Messages should be shown as HTML every time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365660] File layers will not convert to Paint Layers
https://bugs.kde.org/show_bug.cgi?id=365660 --- Comment #3 from mvowada --- (Bug 365998 has been marked as a duplicate of this one) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365660] File layers will not convert to Paint Layers
https://bugs.kde.org/show_bug.cgi?id=365660 mvowada changed: What|Removed |Added CC||danilojun...@gmail.com --- Comment #2 from mvowada --- *** Bug 365998 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365998] Convert vector layer to paint layer doesn't work
https://bugs.kde.org/show_bug.cgi?id=365998 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from mvowada --- Hi, thanks. Confirming and marking this report as a duplicate of Bug 365660 *** This bug has been marked as a duplicate of bug 365660 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365660] File layers will not convert to Paint Layers
https://bugs.kde.org/show_bug.cgi?id=365660 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Here it seems that "Layer > Convert" doesn't work in all cases (FILE, FILL, FILTER, VECTOR, CLONE, GROUP). I'm on Ubuntu 14.04, using Krita 3 appimage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Sebastian Schrader changed: What|Removed |Added CC||sebastian.schrader@ossmail. ||de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366001] New: [Cintiq] Krita crashes on second brush stroke on a newly opened document.
https://bugs.kde.org/show_bug.cgi?id=366001 Bug ID: 366001 Summary: [Cintiq] Krita crashes on second brush stroke on a newly opened document. Product: krita Version: 3.0.1 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: andyvandal...@gmail.com Got latest alpha build to see if the multi-monitor resolution offset problem was fixed, or to see if at least manually changing the resolution still results in total pressure sensitivity loss but now simply performing brush strokes on a new canvas will crash Krita with 100% reproducibility. I can usually make one brush stroke, but a second one will cause a crash. I then ran it in debug mode to collect the print out from Dr. Mingw. The contents are pasted in the details section. It is a three monitor setup with a Cintiq 21UX as the third monitor on Windows 7. Reproducible: Always Steps to Reproduce: 1. Open Krita 2. Create new document. 3. Touch and drag stylus across tablet surface. Lift. 4. Touch stylus to surface again. 5. Crash. Actual Results: 100% crash. Expected Results: Performed a second brush stroke. Here is the print out from Dr. Mingw: krita.exe caused an Access Violation at location 6754BB3A in module libkritapigment.dll Reading from location . AddrPC Params 6754BB3A 0002 0020 2321F8B0 libkritapigment.dll!KoStreamedMath<(Vc_1::Implementation)6>::genericComposite, 4> 6763885D 13727960 6F63E635 2321FAF0 libkritapigment.dll!KoOptimizedCompositeOpOver32<(Vc_1::Implementation)6>::composite 674DCCBB 020004C0 023F04FF libkritapigment.dll!KoColorSpace::bitBlt 6F63197B 2321FC10 0440 0180 libkritaimage.dll!KisPainter::bitBltImpl 6F423DBF 00070001 18A3BD20 libkritaimage.dll!KisPainter::bitBlt 6F678713 16E1E570 16E1E5A8 182C36A0 libkritaimage.dll!KisIndirectPaintingSupport::mergeToLayerImpl 6F4FE2C9 18A43378 0005 libkritaimage.dll!KisIndirectPaintingSupport::mergeToLayer 66509DE6 00CF0D6F 16C2D500 libkritaui.dll!KisPainterBasedStrokeStrategy::finishStrokeCallback 6F64DE93 00ABC9EE libkritaimage.dll!KisUpdateJobItem::run 00ABE085 16C2D500 18BC6A30 16F18410 Qt5Core.dll!QThreadPool::clear 00AC050C 16F18410 Qt5Core.dll!QThread::setTerminationEnabled 07FEFF04415F 07FEFF0D1EA0 16F18410 msvcrt.dll!_endthreadex 07FEFF046EBD msvcrt.dll!_endthreadex 76EA59BD kernel32.dll!BaseThreadInitThunk 770DA2E1 ntdll.dll!RtlUserThreadStart -- You are receiving this mail because: You are watching all bug changes.
[kshisen] [Bug 366000] New: No tiles showing, and the app closes when I click anywhere in playing area.
https://bugs.kde.org/show_bug.cgi?id=366000 Bug ID: 366000 Summary: No tiles showing, and the app closes when I click anywhere in playing area. Product: kshisen Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: schwar...@kde.org Reporter: mbear...@gt.rr.com CC: kde-games-b...@kde.org Version 1.10.1 kshisen Fedora 24 (x86-64) AMD Quad-Four CPU w/ 16 GB Main Memory I open the app, to find the app window appearing properly. The title bar, menu bar, button bar, and status bar are all displaying properly. No tiles are showing. The timer is counting, and the tile tracker is showing 0/144 tiles. Still, no tiles are showing. I can choose menu choices, and help, but when I click into the playing area the app closes with no warning. Reproducible: Always Steps to Reproduce: 1. Open the app. 2. Click in the center where tiles should be. 3. The app closes. Actual Results: The app closes. Expected Results: Show the tiles. Allow me to select tile matches to remove. No system errors are reported. If you let me know about a log file I could look in, I will be happy to report that for you (or email it to you). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #2 from Pulfer --- (In reply to Pulfer from comment #0) > But in fact it only makes things worse (if backported to 5.7.2 package) - > Plasma Shell locks on load, there's only black screen without desktop and > panel. Well, it's not a deadlock. It's possible to run commands via Alt+F2. Just no desktop, panel etc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989
--- Comment #1 from Pulfer ---
https://phabricator.kde.org/D2268 seems to fix Plasma Shell deadlock on start.
But still loading default layout is broken:
--- .xsession-errors ---
...
Setting default Containment plugin: "org.kde.plasma.folder"
Failed to create and switch to the activity
"1"
Plasma Shell startup completed
...
--- .xsession-errors ---
--- layout.js ---
loadTemplate("org.kde.plasma.desktop.defaultPanel")
for (var i = 0; i < screenCount; ++i) {
var id = createActivity("Rosa Desktop", "org.kde.plasma.folder");
var desktopsArray = desktopsForActivity(id);
print(desktopsArray.length);
for( var j = 0; j < desktopsArray.length; j++) {
desktopsArray[j].wallpaperPlugin = 'org.kde.image';
desktopsArray[j].currentConfigGroup = ["General"]
desktopsArray[j].writeConfig("showToolbox", "false")
//var clock = desktopsArray[j].addWidget("org.kde.plasma.analogclock");
}
}
--- layout.js ---
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 363759] Program crashes when attempting to turn on onion skins for animation (windows)
https://bugs.kde.org/show_bug.cgi?id=363759 --- Comment #6 from wandaclayhen...@gmail.com --- This has apparently been fixed in 3.01. Much better overall. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulfer changed: What|Removed |Added CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 wandaclayhen...@gmail.com changed: What|Removed |Added CC||wandaclayhen...@gmail.com --- Comment #30 from wandaclayhen...@gmail.com --- It happens with my Yiynova22 (v3) too. on both 3 the latest test drivers for 3.01 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365999] New: Pairing with Android file system "Invalid object path:" in "dolphin"
https://bugs.kde.org/show_bug.cgi?id=365999 Bug ID: 365999 Summary: Pairing with Android file system "Invalid object path:" in "dolphin" Product: dolphin Version: 15.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: marco.schoolenb...@gmail.com When pairing an Android phone via KDE connect, having paired succesfully clicking the to navigate to file storage on phone. Dolphin fails with following error displayed in red error bar. "Internal Error Please send a full bug report at http://bugs.kde.org Invalid object path: /modules/kdeconnect/devices/36.218.3.75/sftp" Reproducible: Always Steps to Reproduce: 1. Pair an android with Kubuntu 2. Click filesystem icon on KDE connect panel. 3. Dolphin starts .. produces Invalid object path: /modules/kdeconnect/devices/xxx.xxx.xxx.xxx/sftp Actual Results: Error in dolphin: Internal Error Please send a full bug report at http://bugs.kde.org Invalid object path: /modules/kdeconnect/devices/36.218.3.75/sftp Expected Results: Show files residing on phone memory card and internal storage. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 142625] Support 'astral' Unicode planes (those beyond codepoint FFFF)
https://bugs.kde.org/show_bug.cgi?id=142625 --- Comment #17 from Christoph Feck --- Git commit 7baa78ca83ab3c47d2f03259959ec25e59b2f711 by Christoph Feck. Committed on 23/07/2016 at 01:42. Pushed by cfeck into branch 'master'. [KCharSelect] Handle characters outside BMP This is the initial commit to support Unicode code points outside of QChar range U+..U+. To fix this, multiple steps are needed: - a new API, which is not based on QChar, but uses uint datatype for code points (provided by this commit), - a new database, which has information about symbols outside the BMP range. This commit uses a temporary remapping trick to inject SMP symbols (U+1Fxxx) into the Private Use Area until we have a new data base format, - applications that use the new uint based API (not provided by this commit). See KF5 Porting Notes for porting information. REVIEW: 120904 M +---src/kcharselect-data M +133 -56 src/kcharselect.cpp M +91 -4src/kcharselect.h M +11 -11 src/kcharselect_p.h M +128 -72 src/kcharselectdata.cpp M +26 -22 src/kcharselectdata_p.h http://commits.kde.org/kwidgetsaddons/7baa78ca83ab3c47d2f03259959ec25e59b2f711 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #158 from Michael Butash --- I've been noticing this too, testing between 5.5 and 5.6 of libqt and plasma itself, it never seems to go where I tell it to. The other multi-monitor issues are compounding it, when they disappear, and kwin shuffles everything around, the taskbar will do so as well. Even more odd, do this enough, and it'll start spazzing, flickering between both screens until I force some event. Very buggy how and where this panel lands. Glad at least it is noticed and confirmed, one more thing perpetually broken with multi-monitor to watch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Michael Butash changed: What|Removed |Added CC||mich...@butash.net -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 --- Comment #10 from anewuser --- @Bollebib, since this doesn't happen to all buttons/options, please don't close either bug report. Mine is about other options and has been confirmed in the most recent version of Krita. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulfer changed: What|Removed |Added CC||h...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360219] Right Click opens files
https://bugs.kde.org/show_bug.cgi?id=360219 --- Comment #17 from Eike Hein --- Git commit 0065d3548c7db695b06d80250b11d018214967dc by Eike Hein. Committed on 23/07/2016 at 00:46. Pushed by hein into branch 'Plasma/5.7'. Don't activate it on release events when a drag was started prior to it. M +1-0applets/kicker/package/contents/ui/ItemListDelegate.qml M +1-0applets/kicker/package/contents/ui/SideBarItem.qml http://commits.kde.org/plasma-desktop/0065d3548c7db695b06d80250b11d018214967dc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360219] Right Click opens files
https://bugs.kde.org/show_bug.cgi?id=360219 --- Comment #16 from Eike Hein --- The latter is actually a bug in Kicker it seems. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 365813] options doesn't work for module-sets
https://bugs.kde.org/show_bug.cgi?id=365813 --- Comment #1 from Michael Pyne --- Created attachment 100253 --> https://bugs.kde.org/attachment.cgi?id=100253&action=edit Patch options matching named module-sets into module options The attached patch does what you want in my testing. I'm not sure if this simple change is exactly the best way to go though. Having a separate module-set-options seems needlessly user-hostile (though in fairness it is consistent with the way option handling has evolved in the code). It wouldn't be hard to adjust the config file parser to warn (or throw error) if a module-set and module both have the same name, and that would ensure that a plain 'options' block works for both. except that 'options' is also meant to work in the case of modules that are not known about in the rc-file parser, but only become visible later (e.g. if you name a module-set 'juk' but perform a 'use-modules kde/kdemultimedia' in a separate module-set, you'd have two entities named "juk" that could have options applied). That's somewhat contrived of course, I'm just worried that "options foo ... end options" could end up meaning 2 separate things depending only on events that happen at runtime. With all that said, this does seem to work and they say that the perfect is the enemy of the good, so maybe it's best to integrate it and wait for problems (if any) before worrying too much? -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 365867] Export to remote storage fails
https://bugs.kde.org/show_bug.cgi?id=365867 --- Comment #2 from Michael Rasmussen --- kipi-plugins are at version 5.0.0-1 libkipi at version 16.04.3-1 (I believe the -1 is the Arch package sub-version) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 354370] GIMP icon is bad
https://bugs.kde.org/show_bug.cgi?id=354370 andreas changed: What|Removed |Added Status|REOPENED|RESOLVED Latest Commit||http://commits.kde.org/bree ||ze-icons/038391c98c349d93e3 ||510e59b8d3413d7614e844 Resolution|--- |FIXED --- Comment #14 from andreas --- Git commit 038391c98c349d93e3510e59b8d3413d7614e844 by andreas kainz. Committed on 22/07/2016 at 22:56. Pushed by andreask into branch 'master'. update gimp icons thanks gnastyle M +113 -52 icons-dark/apps/48/gimp.svg M +113 -52 icons/apps/48/gimp.svg http://commits.kde.org/breeze-icons/038391c98c349d93e3510e59b8d3413d7614e844 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365689] KRDC missing icon
https://bugs.kde.org/show_bug.cgi?id=365689 andreas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from andreas --- breeze icon added to master thanks gnastyle -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365094] *.crt files do not show icons
https://bugs.kde.org/show_bug.cgi?id=365094 --- Comment #4 from andreas --- I can't find out how the icon name is. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=361360 --- Comment #40 from Jesse --- Looking up the version tab in the latest git master build of Kdenlive that I have, it shows this version of Qt: KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=361360 --- Comment #39 from Jesse --- The post above was in reference to my machine with two Nvidia 660's in it (it's the only way I can really distinguish my work PC's apart, by the GPU). My work laptop which has two 970ti's in it has the same result: QMake version 2.01a Using Qt version 4.8.7 in /usr/lib/x86_64-linux-gnu -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365797] Second monitor distorts when being adjusted
https://bugs.kde.org/show_bug.cgi?id=365797 --- Comment #9 from Buck Shockley --- (In reply to Martin Gräßlin from comment #8) > That looks all fine: > * xorg log doesn't have warnings > * kwin debug output is correct - it detected the screens as printed in xorg > log, compositor is active and happy > * glxinfo doesn't show any "bad" limits > > My assumption currently is that also Plasma (and other applications) get the > graphics reset from the NVIDIA driver. If that's the case you don't need to > restart the complete session. A > kquitapp5 plasmashell > plasmashell > > from e.g. KRunner should also fix it. See Comment 3. I don't know why, but a complete session restart works. However, I just realized, the only way to make the screen reset after restarting the session is disabling the Kscreen 2 startup service. I don't know if that is impacting these results. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=361360 --- Comment #38 from Jesse --- Strange, it didn't look like qmake was installed. I installed the package "qt5-qmake" (using ubuntu 16.04 package base on Linux Mint), but the command still didn't work. I installed "qt4-qmake", and the command worked, then. Here's the output: QMake version 2.01a Using Qt version 4.8.7 in /usr/lib/x86_64-linux-gnu If I'm reading that right, is my Qt version WAY behind? Has Qt made that much progress since the Ubuntu 16.04 release? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys
https://bugs.kde.org/show_bug.cgi?id=344969 --- Comment #38 from vindica...@live.com --- Leslie and Janek, the latest build works for me regarding the time taken to move a file to the trash which I posted at https://bugs.kde.org/show_bug.cgi?id=331707#c5 (which is appropriate bug). A single file was basically instant, while a folder full of subfolders/files (183) took maybe a couple seconds, but I think that is to be expected as the folders are traversed. However this build didn't have the "shift-del" deletion for the files. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365998] New: Convert vector layer to paint layer doesn't work
https://bugs.kde.org/show_bug.cgi?id=365998 Bug ID: 365998 Summary: Convert vector layer to paint layer doesn't work Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: danilojun...@gmail.com Convert vector layer to paint layer doesn't work. Reproducible: Always Steps to Reproduce: 1. create a vector layer and some vector. 2. try convert to an paint layer. 3. Actual Results: The conversion doesn't happen. Expected Results: Conversion of vector layer to an paint layer. krita 3.0 windows 7 x64 i7, 16gb ram , nvidia gtx 750 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 331707] Moving a file to trash is extremely slow
https://bugs.kde.org/show_bug.cgi?id=331707 --- Comment #5 from vindica...@live.com --- Looks to have cleared up for me with the latest upgrade to 5.7.2-1 (archlinux). I tested it, then rebooted and tested again and all is well. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=361360 --- Comment #37 from Jean-Baptiste Mardelle --- I am also seeing the slowdown on my laptop. I am wondering if this might be related to the Qt version. The big speed gain I experienced was on my PC with Qt 5.7, so maybe some optimizations in Qt make the difference. Jesse, can you check the Qt versions on your 2 machines to see if there is a difference there? qmake -v will output the Qt version... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 349789] Local Folders Disappear when Last Search Deleted
https://bugs.kde.org/show_bug.cgi?id=349789 David Faure changed: What|Removed |Added Latest Commit||http://commits.kde.org/kite ||mmodels/e2a688651cc5fb3cca6 ||82c4153866609713e76a9 Status|UNCONFIRMED |RESOLVED Version Fixed In||5.25 Resolution|--- |FIXED --- Comment #4 from David Faure --- Git commit e2a688651cc5fb3cca682c4153866609713e76a9 by David Faure. Committed on 22/07/2016 at 22:09. Pushed by dfaure into branch 'master'. KRecursiveFilterProxyModel: fix QSFPM corruption due to filtering out rowsRemoved signal If the row being removed from the source model isn't shown by KRFPM, it's correct that we don't need to emit any signals, however we still need to tell our base class QSFPM so that it updates the mappings of the visible siblings below that removed row. Testcase: deleting the Last Search folder in kmail (full integration test for this testcase will be added to mailcommon). REVIEW: 128428 FIXED-IN: 5.25 M +3-1autotests/krecursivefilterproxymodeltest.cpp M +0-20 src/krecursivefilterproxymodel.cpp http://commits.kde.org/kitemmodels/e2a688651cc5fb3cca682c4153866609713e76a9 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365997] Separating a tab to an own window is slow
https://bugs.kde.org/show_bug.cgi?id=365997 --- Comment #1 from Jan Wiele --- Created attachment 100252 --> https://bugs.kde.org/attachment.cgi?id=100252&action=edit Tab separates late from the konsole window. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365997] New: Separating a tab to an own window is slow
https://bugs.kde.org/show_bug.cgi?id=365997 Bug ID: 365997 Summary: Separating a tab to an own window is slow Product: konsole Version: 16.04.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: j...@wiele.org I often use the feature to separate a tab of one konsole to create a second konsole window. But atm you cannot grab the tab and flip it to the edge of the screen to get a new window. It takes 1-2 seconds until the the tab follows the mouse cursor. I've attached a screenshot, which shows the problem of the delay. As one can see, I'm already near the edge of my screen with the cursor, but the tab just separated. Reproducible: Always Steps to Reproduce: 1. Open konsole, create a second tab. 2. Grab the tab, dont release the mouse button, move the mouse a little bit. 3. It takes about one second until the tab is separated and follows the mouse. 4. If you dont wait until the tab is separated, nothing happens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363673] Popup menu - Create New - Link to Application does nothing useful
https://bugs.kde.org/show_bug.cgi?id=363673 David Faure changed: What|Removed |Added Latest Commit||http://commits.kde.org/kio/ ||525232d30ee682de4778667c824 ||4778b50620e67 Status|UNCONFIRMED |RESOLVED Version Fixed In||5.25 Resolution|--- |FIXED --- Comment #4 from David Faure --- Git commit 525232d30ee682de4778667c8244778b50620e67 by David Faure, on behalf of Chinmoy Ranjan Pradhan. Committed on 22/07/2016 at 22:01. Pushed by dfaure into branch 'master'. KNewFileMenu: Fix creating link to application This was broken since the switch to resource files as input files. KPropertiesDialog does not support that, so a temp file has to be created first (and deleted when the properties dialog is closed) FIXED-IN: 5.25 REVIEW: 128501 M +33 -4src/filewidgets/knewfilemenu.cpp M +1-0src/filewidgets/knewfilemenu.h http://commits.kde.org/kio/525232d30ee682de4778667c8244778b50620e67 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363538] git master: fade to black doesn't fade correctly on title clip which got resized
https://bugs.kde.org/show_bug.cgi?id=363538 Jean-Baptiste Mardelle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kden ||live/86e758e7c67edf1b0c993e ||ddaf87f2723b7e8635 Resolution|--- |FIXED --- Comment #2 from Jean-Baptiste Mardelle --- Git commit 86e758e7c67edf1b0c993eddaf87f2723b7e8635 by Jean-Baptiste Mardelle. Committed on 22/07/2016 at 21:54. Pushed by mardelle into branch 'Applications/16.08'. Fix Fade out broken on resized title/color/image clips M +1-1src/bin/projectclip.cpp M +11 -1src/mltcontroller/clipcontroller.cpp M +21 -5src/mltcontroller/clippropertiescontroller.cpp M +3-0src/mltcontroller/producerqueue.cpp M +1-0src/timeline/track.cpp http://commits.kde.org/kdenlive/86e758e7c67edf1b0c993eddaf87f2723b7e8635 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365996] New: Crash after applying Misc - Fade to a color clip
https://bugs.kde.org/show_bug.cgi?id=365996
Bug ID: 365996
Summary: Crash after applying Misc - Fade to a color clip
Product: kdenlive
Version: 16.04.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Effects & Transitions
Assignee: vpi...@kde.org
Reporter: snd.no...@gmail.com
Crash after applying Misc -> Fade effect to a color clip
Reproducible: Always
Steps to Reproduce:
1. Add color clip on timeline
2. Apply Misc-> Fade to it
3. Crash
[fade @ 0x7fff48558f40] [Eval @ 0x7fff94e61180] Undefined constant or missing
'(' in ''
[fade @ 0x7fff48558f40] Unable to parse option value ""
[fade @ 0x7fff48558f40] [Eval @ 0x7fff94e61180] Undefined constant or missing
'(' in ''
[fade @ 0x7fff48558f40] Unable to parse option value ""
[fade @ 0x7fff48558f40] Unable to parse option value "" as duration
[fade @ 0x7fff48558f40] Unable to parse option value "" as duration
[fade @ 0x7fff48558f40] Unable to parse option value "" as duration
[fade @ 0x7fff48558f40] Unable to parse option value "" as duration
[fade @ 0x7fff48558f40] Invalid 0xRRGGBB[AA] color string: ''
[fade @ 0x7fff48558f40] Unable to parse option value "" as color
[fade @ 0x7fff48558f40] Invalid 0xRRGGBB[AA] color string: ''
[fade @ 0x7fff48558f40] Unable to parse option value "" as color
Thread 992 "RenderThread" received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0x7fff94e62700 (LWP 3870)]
0x7fffbcb70806 in ?? () from /usr/lib/libavfilter.so.6
(gdb) backtrace
#0 0x7fffbcb70806 in ?? () from /usr/lib/libavfilter.so.6
#1 0x7fffbcbbd7b0 in avfilter_init_str () from /usr/lib/libavfilter.so.6
#2 0x7fffbf315c7b in ?? () from /usr/lib/mlt/libmltavformat.so
#3 0x76d82007 in mlt_frame_get_image () from /usr/lib/libmlt.so.6
#4 0x76d82007 in mlt_frame_get_image () from /usr/lib/libmlt.so.6
#5 0x7fffadb29e5d in ?? () from /usr/lib/mlt/libmltfrei0r.so
#6 0x76d82007 in mlt_frame_get_image () from /usr/lib/libmlt.so.6
#7 0x76d82007 in mlt_frame_get_image () from /usr/lib/libmlt.so.6
#8 0x7fffadb29e44 in ?? () from /usr/lib/mlt/libmltfrei0r.so
#9 0x76d82007 in mlt_frame_get_image () from /usr/lib/libmlt.so.6
#10 0x76d97f89 in ?? () from /usr/lib/libmlt.so.6
#11 0x76d82007 in mlt_frame_get_image () from /usr/lib/libmlt.so.6
#12 0x76d95620 in ?? () from /usr/lib/libmlt.so.6
#13 0x007024cd in ?? ()
#14 0x7064bd78 in ?? () from /usr/lib/libQt5Core.so.5
#15 0x7fffee113484 in start_thread () from /usr/lib/libpthread.so.0
#16 0x7fffefc5a6dd in clone () from /usr/lib/libc.so.6
(gdb) thread apply all bt
Thread 1005 (Thread 0x7ffe9fffd700 (LWP 3885)):
#0 0x7fffee1190af in pthread_cond_wait@@GLIBC_2.3.2 ()
from /usr/lib/libpthread.so.0
#1 0x7fffbcbdfc6b in ?? () from /usr/lib/libavfilter.so.6
#2 0x7fffee113484 in start_thread () from /usr/lib/libpthread.so.0
#3 0x7fffefc5a6dd in clone () from /usr/lib/libc.so.6
Thread 1004 (Thread 0x7ffeb0f6a700 (LWP 3884)):
#0 0x7fffee1190af in pthread_cond_wait@@GLIBC_2.3.2 ()
from /usr/lib/libpthread.so.0
#1 0x7fffbcbdfc6b in ?? () from /usr/lib/libavfilter.so.6
#2 0x7fffee113484 in start_thread () from /usr/lib/libpthread.so.0
#3 0x7fffefc5a6dd in clone () from /usr/lib/libc.so.6
Thread 1003 (Thread 0x7ffeca7fc700 (LWP 3883)):
#0 0x7fffee1190af in pthread_cond_wait@@GLIBC_2.3.2 ()
from /usr/lib/libpthread.so.0
#1 0x7fffbcbdfc6b in ?? () from /usr/lib/libavfilter.so.6
#2 0x7fffee113484 in start_thread () from /usr/lib/libpthread.so.0
#3 0x7fffefc5a6dd in clone () from /usr/lib/libc.so.6
Thread 1002 (Thread 0x7ffecaffd700 (LWP 3882)):
#0 0x7fffee1190af in pthread_cond_wait@@GLIBC_2.3.2 ()
from /usr/lib/libpthread.so.0
---Type to continue, or q to quit---
#1 0x7fffbcbdfc6b in ?? () from /usr/lib/libavfilter.so.6
#2 0x7fffee113484 in start_thread () from /usr/lib/libpthread.so.0
#3 0x7fffefc5a6dd in clone () from /usr/lib/libc.so.6
Thread 1001 (Thread 0x7ffecb7fe700 (LWP 3881)):
#0 0x7fffee1190af in pthread_cond_wait@@GLIBC_2.3.2 ()
from /usr/lib/libpthread.so.0
#1 0x7fffbcbdfc6b in ?? () from /usr/lib/libavfilter.so.6
#2 0x7fffee113484 in start_thread () from /usr/lib/libpthread.so.0
#3 0x7fffefc5a6dd in clone () from /usr/lib/libc.so.6
Thread 1000 (Thread 0x7ffecbfff700 (LWP 3880)):
#0 0x7fffee1190af in pthread_cond_wait@@GLIBC_2.3.2 ()
from /usr/lib/libpthread.so.0
#1 0x7fffbcbdfc6b in ?? () from /usr/lib/libavfilter.so.6
#2 0x7fffee113484 in start_thread () from /usr/lib/libpthread.so.0
#3 0x7fffefc5a6dd in clone () from /usr/lib/libc.so.6
Thread 999 (Thread 0x7ffed4c89700 (LWP 3879)):
#0 0x7fffee1190af in pthread_cond_wait@@GLIBC_2.3.2 ()
from /usr/lib/libpthread.so.0
#1
[kdenlive] [Bug 365996] Crash after applying Misc - Fade to a color clip
https://bugs.kde.org/show_bug.cgi?id=365996 farid changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362450] Capturing small rectangular regions fails
https://bugs.kde.org/show_bug.cgi?id=362450 --- Comment #5 from Jan Wiele --- Created attachment 100251 --> https://bugs.kde.org/attachment.cgi?id=100251&action=edit Broken preview of small rectangular area. The preview for a small rectangular area is still broken for me with 16.04.3. I've attached a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365072] Disappearing transitions back in git master
https://bugs.kde.org/show_bug.cgi?id=365072 Vincent PINON changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 358689] Support Qt 5.6 new highdpi environment variable
https://bugs.kde.org/show_bug.cgi?id=358689 --- Comment #9 from Weng Xuetian --- (In reply to Martin Gräßlin from comment #8) > (In reply to Weng Xuetian from comment #7) > > This setting has nothing to do with X11, it's just for Qt itself. > > > > you can set it like: > > QT_SCREEN_SCALE_FACTORS=eDP1=2;eDP2=3 > > > > So when you move window among screen, the Qt's window will be rescaled to > > the screen dpi automatically. > > That cannot work on X11, sorry. That's just Qt's "I don't know how to > multi-screen on X11". The problems here are: > * a window is not connected with an output, it has a position within the X > screen space > * QWindow allows to set the QScreen, but this does not influence whether the > window is sown on the screen > * DPI for multi-screen on common X-Servers is broken. As soon as there are > two screens, the X-Server does report a default 96 pdi AFAIK > * when moving a window from one screen to another it could result in an > infinite jumping between the different DPI modes > * the totally legit situation of one window on two screens is not handled > * the window manager does not adjust the window decoration > * I could go on and on > > Exposing a config option for that would be wrong: we cannot have different > scale factors on X11. That would just introduce another set of things which > can go wrong with Qt's utterly broken (and broken beyond repair) > multi-screen implementation on X11. Such complain doesn't solve anything. You're just pointing to some "Potential" Problem that doesn't really happen. I have been using QT_DEVICE_PIXEL_RATIO=auto (when it's still old style env var) since Qt 5.4, and it never cause me any trouble. Dynamically change window's scale factor is tricky, but it's also the same approach on Windows. I have been use it for such a long time. And if any issue you claim actually happens, Qt should fix it. Not to mention IT IS not the case. I have even seen user complain about startkde script prevent user to set QT_AUTO_SCREEN_SCALE_FACTOR to 1. It's not something badly broken, really. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365995] New: Shorter date formats for vertical taskbar users.
https://bugs.kde.org/show_bug.cgi?id=365995 Bug ID: 365995 Summary: Shorter date formats for vertical taskbar users. Product: plasmashell Version: 5.7.2 Platform: Gentoo Packages URL: http://lum.uk/temp/DigitalClock.png OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: kde-b...@lum.co.uk Currently the shortest date format available is a 10-digit format, DD/MM/ (in my locale), which is a bit too wide if you happen to prefer a vertical taskbar (useful on low-res widescreen devices). Would it be possible to provide two shorter options (DD/MM/YY and DD/MM) for users with this setup, or a custom date format option (ala T-Clock Redux for Windows) Reproducible: Always Steps to Reproduce: 1) Move the panel to the side of the screen 2) Shrink the panel to 50px or less Actual Results: Date is left-aligned and truncated with an elpisis (eg. DD/MM... as per screenshot) Expected Results: Date is centred with no elipsis. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365887] git master: internally added (mix/composite) transitions getting out of sync with project and producing large overhead
https://bugs.kde.org/show_bug.cgi?id=365887 Vincent PINON changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365014] All windows hide on repeating desktop click
https://bugs.kde.org/show_bug.cgi?id=365014 Quiralta changed: What|Removed |Added CC||rjquira...@gmail.com --- Comment #13 from Quiralta --- Have the same issue, and in fact the desktop behaves like if was a window, the other windows go "behind it" when loosing focus. Here is what xprog gives me: XdndAware(ATOM) = BITMAP WM_NAME(STRING) = "Desktop" _NET_WM_NAME(UTF8_STRING) = "Desktop — Plasma" _KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 20752 _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x1, 0x0, 0x0, 0x0 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DESKTOP _XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1 WM_CLIENT_LEADER(WINDOW): window id # 0x20c WM_HINTS(WM_HINTS): Client accepts input or input focus: True Initial state is Normal State. _NET_WM_PID(CARDINAL) = 687 _NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 33554448 WM_CLASS(STRING) = "plasmashell", "plasmashell" WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST WM_NORMAL_HINTS(WM_SIZE_HINTS): user specified location: 0, 0 user specified size: 1920 by 1080 program specified minimum size: 1920 by 1080 program specified maximum size: 1920 by 1080 window gravity: Static -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365965] git master - Position and Zoom effect isn't working properly (video example included)
https://bugs.kde.org/show_bug.cgi?id=365965 Vincent PINON changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365969] sporadic plasma-desktop crash while using PokerStars and Pokertracker via wine
https://bugs.kde.org/show_bug.cgi?id=365969 --- Comment #2 from Michael Stenzel --- Oh well, still thanks for your quick response. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365970] Demanding attention tasks are not shown on all desktops
https://bugs.kde.org/show_bug.cgi?id=365970 Eike Hein changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-workspace/da5c2fd5058e60 ||d12bfbdfa2b1863433ab20dfbb --- Comment #3 from Eike Hein --- Git commit da5c2fd5058e60d12bfbdfa2b1863433ab20dfbb by Eike Hein. Committed on 22/07/2016 at 20:48. Pushed by hein into branch 'Plasma/5.7'. Treat IsDemandingAttention as IsOnAllVirtualDesktops. M +2-1libtaskmanager/taskfilterproxymodel.cpp http://commits.kde.org/plasma-workspace/da5c2fd5058e60d12bfbdfa2b1863433ab20dfbb -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365991] Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."
https://bugs.kde.org/show_bug.cgi?id=365991 --- Comment #2 from Pip --- Creating a new user domain (wiping their home directory) allowed me to start Kontact, so it's some interaction with the user settings. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 319303] Ark is not working with unrar 5.X, ListArgs works, but parser failed
https://bugs.kde.org/show_bug.cgi?id=319303 --- Comment #10 from Martin Marques --- (In reply to Martin Marques from comment #9) > I'm using Fedora 23 and this problem persists. I actually never got ark to > work again after I upgraded to unrar 5. > > Details: > > ark-15.04.3-1.fc23.x86_64 > unrar-5.2.3-1.fc22.x86_64 I fixed my problem installing unar. Maybe the Fedora folks should add another reference to the ark package. Thanks guys -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 319303] Ark is not working with unrar 5.X, ListArgs works, but parser failed
https://bugs.kde.org/show_bug.cgi?id=319303 Martin Marques changed: What|Removed |Added CC||martin.marq...@gmail.com --- Comment #9 from Martin Marques --- I'm using Fedora 23 and this problem persists. I actually never got ark to work again after I upgraded to unrar 5. Details: ark-15.04.3-1.fc23.x86_64 unrar-5.2.3-1.fc22.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 142625] Support 'astral' Unicode planes (those beyond codepoint FFFF)
https://bugs.kde.org/show_bug.cgi?id=142625 Christoph Feck changed: What|Removed |Added Assignee|lai...@kde.org |cf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365771] Multimedia keys should change volume of active sink or global
https://bugs.kde.org/show_bug.cgi?id=365771 --- Comment #4 from Olivier Churlaud --- Your patch works for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365994] New: "Titlebar color scheme" window rule is ignored for Aurorae themes
https://bugs.kde.org/show_bug.cgi?id=365994 Bug ID: 365994 Summary: "Titlebar color scheme" window rule is ignored for Aurorae themes Product: kwin Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com The "Titlebar color scheme" window rule is not accounted for Aurorae themes. Whereas builtin themes such as Oxigen or Breeze respect this setting, color themes based on Aurorae do not and maintain their normal appearance despite the override. Reproducible: Always Steps to Reproduce: 1. Go to Configure Desktop - Window Management - Window Rules, click the New... button. 2. Under Appearance & Fixes, enable Titlebar Color Scheme, set the effect to Force, and select any scheme that has a different background and titlebar from the normal scheme. 3. Apply the rule and open any affected application. Actual Results: If you're using an Aurorae theme with colorization support, this rule will have no effect. Expected Results: The rule should be respected for Aurorae themes, just as it's respected for the builtin Breeze or Oxygen themes. Can be easily tested with one of the following themes... which use the window background color for the titlebar just like Oxygen, as well as colorized button effects: https://www.kde-look.org/p/1002614/ https://www.kde-look.org/p/1002663/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365994] "Titlebar color scheme" window rule is ignored for Aurorae themes
https://bugs.kde.org/show_bug.cgi?id=365994 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 365993] New: Featurerequest Print or Export Review-Marks
https://bugs.kde.org/show_bug.cgi?id=365993 Bug ID: 365993 Summary: Featurerequest Print or Export Review-Marks Product: okular Version: 0.22.1 Platform: Fedora RPMs URL: https://s32.postimg.org/vhfcrp3dh/okular_feature_reque st.png OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: florian...@gmail.com I just want to request a feature. I'm marking a lot of Text in a 600 pages document and want to extract only the marks (look at the picture). This feature isn't currently available in okular and could be a great asset. In simple words: Delete all other text and only extract the text with notes and marks in a new document. Notes and marks = all features under Extras->Review (F6). Reproducible: Always Steps to Reproduce: Feature Request Actual Results: Feature not available Expected Results: Print or export Review functionality only. Export in editable format and pdf desirable -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365771] Multimedia keys should change volume of active sink or global
https://bugs.kde.org/show_bug.cgi?id=365771 --- Comment #3 from David Rosca --- I don't really like the idea of changing volume of all devices, that's why it was changed in 5.7. Controlling volume of currently "active" device seems much better to me, I implemented it in https://phabricator.kde.org/D2270 , would be great if you can test it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365992] New: Krita Crashes on closing document
https://bugs.kde.org/show_bug.cgi?id=365992 Bug ID: 365992 Summary: Krita Crashes on closing document Product: krita Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: raghavendr.ra...@gmail.com Application: krita (3.0.1 Alpha (git f594e3e)) (Compiled from sources) Qt Version: 5.7.0 Frameworks Version: 5.24.0 Operating System: Linux 4.6.4-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I closed a document after working on it. Some times krita crashes when I close last remaining document after closing multiple documents. I build krita from git on linux The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4e0546c840 (LWP 7506))] Thread 5 (Thread 0x7f4dcbfff700 (LWP 7514)): #0 0x7f4df96f00af in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f4dfda10c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f4dfeaed851 in ?? () from /usr/lib/libQt5Widgets.so.5 #3 0x7f4dfda0fd78 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f4df96ea484 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f4dfce086dd in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f4dd0844700 (LWP 7512)): #0 0x7f4df96f00af in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f4dfda10c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f4dfda09e26 in QSemaphore::tryAcquire(int, int) () from /usr/lib/libQt5Core.so.5 #3 0x7f4e04000d13 in KisTileDataSwapper::waitForWork (this=) at /home/raghu/kf5/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #4 0x7f4e04000f1a in KisTileDataSwapper::run (this=0x7f4e044c9f20 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at /home/raghu/kf5/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #5 0x7f4dfda0fd78 in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7f4df96ea484 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f4dfce086dd in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f4dd1045700 (LWP 7511)): #0 0x7f4df96f00af in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f4dfda10c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f4dfda09b33 in QSemaphore::acquire(int) () from /usr/lib/libQt5Core.so.5 #3 0x7f4e03fe558d in KisTileDataPooler::waitForWork (this=0x7f4e044c9ee0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at /home/raghu/kf5/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:165 #4 KisTileDataPooler::run (this=0x7f4e044c9ee0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at /home/raghu/kf5/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:187 #5 0x7f4dfda0fd78 in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7f4df96ea484 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f4dfce086dd in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f4de3cb2700 (LWP 7508)): #0 0x7f4df7516044 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f4df74d1839 in g_main_context_query () from /usr/lib/libglib-2.0.so.0 #2 0x7f4df74d1f48 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f4df74d20ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f4dfdc3e59b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f4dfdbe80da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f4dfda0b0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f4df9037e75 in ?? () from /usr/lib/libQt5DBus.so.5 #8 0x7f4dfda0fd78 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f4df96ea484 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f4dfce086dd in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f4e0546c840 (LWP 7506)): [KCrash Handler] #5 0x7f4dfcd54295 in raise () from /usr/lib/libc.so.6 #6 0x7f4dfcd556da in abort () from /usr/lib/libc.so.6 #7 0x7f4dfd9f64a1 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #8 0x7f4dffed272d in kis_assert_common (assertion=assertion@entry=0x7f4e04fdf5ae "!sanityCheckPointer.isValid()", file=file@entry=0x7f4e04fdf988 "/home/raghu/kf5/src/krita/libs/ui/KisDocument.cpp", line=line@entry=578, throwException=throwException@entry=false, isIgnorable=isIgnorable@entry=false) at /home/raghu/kf5/src/krita/libs/global/kis_assert.cpp:90 #9 0x7f4dffed2a9a in
[kdenlive] [Bug 361822] git master: resetting effect does not work for bin effects
https://bugs.kde.org/show_bug.cgi?id=361822 --- Comment #3 from Wegwerf --- Now checked on Applications/16.08 and the bug is fixed for me too. Thank you very much for fixing this bug! This avoids another stumbling block to newcomers to Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361822] git master: resetting effect does not work for bin effects
https://bugs.kde.org/show_bug.cgi?id=361822 --- Comment #2 from Wegwerf --- Jean-Baptiste, can you please integrate this fix with master? I'm on master and the bug doesn't seem to be fixed there. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365325] unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x6 0xF 0x42 0xC1
https://bugs.kde.org/show_bug.cgi?id=365325 steve.lori...@gmail.com changed: What|Removed |Added CC||steve.lori...@gmail.com --- Comment #1 from steve.lori...@gmail.com --- Getting the same error: $ valgrind -v ./dsp/test/dsp_test ==11100== Memcheck, a memory error detector ==11100== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==11100== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==11100== Command: ./dsp/test/dsp_test ==11100== --11100-- Valgrind options: --11100---v --11100-- Contents of /proc/version: --11100-- Linux version 4.4.0-31-generic (buildd@lgw01-16) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 --11100-- --11100-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-avx-avx2-bmi --11100-- Page sizes: currently 4096, max supported 4096 --11100-- Valgrind library directory: /usr/lib/valgrind --11100-- Reading syms from /home/steve/src/vc/cay/build/dsp/test/dsp_test --11100-- Reading syms from /lib/x86_64-linux-gnu/ld-2.23.so --11100-- Considering /lib/x86_64-linux-gnu/ld-2.23.so .. --11100-- .. CRC mismatch (computed d3da0723 wanted a1c29704) --11100-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so .. --11100-- .. CRC is valid --11100-- Reading syms from /usr/lib/valgrind/memcheck-amd64-linux --11100-- Considering /usr/lib/valgrind/memcheck-amd64-linux .. --11100-- .. CRC mismatch (computed 5529a2c7 wanted 5bd23904) --11100--object doesn't have a symbol table --11100--object doesn't have a dynamic symbol table --11100-- Scheduler: using generic scheduler lock implementation. --11100-- Reading suppressions file: /usr/lib/valgrind/default.supp ==11100== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-11100-by-steve-on-??? ==11100== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-11100-by-steve-on-??? ==11100== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-11100-by-steve-on-??? ==11100== ==11100== TO CONTROL THIS PROCESS USING vgdb (which you probably ==11100== don't want to do, unless you know exactly what you're doing, ==11100== or are doing some strange experiment): ==11100== /usr/lib/valgrind/../../bin/vgdb --pid=11100 ...command... ==11100== ==11100== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==11100== /path/to/gdb ./dsp/test/dsp_test ==11100== and then give GDB the following command ==11100== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=11100 ==11100== --pid is optional if only one valgrind process is running ==11100== --11100-- REDIR: 0x401cdc0 (ld-linux-x86-64.so.2:strlen) redirected to 0x3809e181 (???) --11100-- Reading syms from /usr/lib/valgrind/vgpreload_core-amd64-linux.so --11100-- Considering /usr/lib/valgrind/vgpreload_core-amd64-linux.so .. --11100-- .. CRC mismatch (computed a30c8eaa wanted 7ae2fed4) --11100--object doesn't have a symbol table --11100-- Reading syms from /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so --11100-- Considering /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so .. --11100-- .. CRC mismatch (computed 402c2ab5 wanted 745f25ae) --11100--object doesn't have a symbol table ==11100== WARNING: new redirection conflicts with existing -- ignoring it --11100-- old: 0x0401cdc0 (strlen ) R-> (.0) 0x3809e181 ??? --11100-- new: 0x0401cdc0 (strlen ) R-> (2007.0) 0x04c31020 strlen --11100-- REDIR: 0x401b710 (ld-linux-x86-64.so.2:index) redirected to 0x4c30bc0 (index) --11100-- REDIR: 0x401b930 (ld-linux-x86-64.so.2:strcmp) redirected to 0x4c320d0 (strcmp) --11100-- REDIR: 0x401db20 (ld-linux-x86-64.so.2:mempcpy) redirected to 0x4c35270 (mempcpy) --11100-- Reading syms from /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 --11100-- Considering /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 .. --11100-- .. CRC mismatch (computed 6d893738 wanted d420bd97) --11100--object doesn't have a symbol table --11100-- Reading syms from /lib/x86_64-linux-gnu/libm-2.23.so --11100-- Considering /lib/x86_64-linux-gnu/libm-2.23.so .. --11100-- .. CRC mismatch (computed f7791cb7 wanted 92acf4be) --11100-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.23.so .. --11100-- .. CRC is valid --11100-- Reading syms from /lib/x86_64-linux-gnu/libgcc_s.so.1 --11100-- Considering /lib/x86_64-linux-gnu/libgcc_s.so.1 .. --11100-- .. CRC mismatch (computed b9a68419 wanted 29d51b00) --11100--object doesn't have a symbol table --11100-- Reading syms from /lib/x86_64-linux-gnu/libpthread-2.23.so --11100-- Considering /usr/lib/debug/.build-id/b7/7847cc9cacbca3b5753d0d25a32e5795afe75b.debug .. --11100-- .. build-id is valid --11100-- Reading syms from /lib/x86_64-linux-gnu/libc-2.23.so --11100-- Considering /lib/x86_64-linux-gnu/libc
[Akonadi] [Bug 365991] Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."
https://bugs.kde.org/show_bug.cgi?id=365991 --- Comment #1 from Pip --- kdepim-kresources removed during dist-upgrade -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365991] New: Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."
https://bugs.kde.org/show_bug.cgi?id=365991 Bug ID: 365991 Summary: Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." Product: Akonadi Version: 16.04 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: gamo...@ymail.com kontact log_messagelist: Saved theme loading failed log_messagelist: Saved theme loading failed log_messagelist: Saved theme loading failed org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 368 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." log_mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nFailed to fetch the resource collection." org.kde.akonadi.ETM: Fetch job took 415 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." log_mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nFailed to fetch the resource collection." akonadicore_log: Failed to request resource "akonadi_mixedmaildir_resource_1" : "Failed to fetch the resource collection." akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." log_mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nFailed to fetch the resource collection." akonadicore_log: Failed to request resource "akonadi_mixedmaildir_resource_1" : "Failed to fetch the resource collection." akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." log_mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nFailed to fetch the resource collection." akonadicore_log: Failed to request resource "akonadi_mixedmaildir_resource_1" : "Failed to fetch the resource collection." akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." log_mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nFailed to fetch the resource collection." akonadicore_log: Failed to request resource "akonadi_mixedmaildir_resource_1" : "Failed to fetch the resource collection." akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." log_mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nFailed to fetch the resource collection." akonadicore_log: Failed to request resource "akonadi_mixedmaildir_resource_1" : "Failed to fetch the resource collection." org.kde.akonadi.ETM: Subtree: 1 QSet(1, 150, 151) org.kde.akonadi.ETM: Fetch job took 442 msec org.kde.akonadi.ETM: was collection fetch job: collections: 3 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Subtree: 1 QSet(1, 150, 151) org.kde.akonadi.ETM: Fetch job took 445 msec org.kde.akonadi.ETM: was collection fetch job: collections: 3 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 444 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 *** KMail got signal 11 (Exiting) Segmentation fault Reproducible: Always Steps to Reproduce: 1. apt dist-upgrade 2.start kontact/kmail 3. Actual Results: As above Expected Results: Kontact running Repeated the exercise on three different laptops. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361822] git master: resetting effect does not work for bin effects
https://bugs.kde.org/show_bug.cgi?id=361822 Vincent PINON changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 365990] New: Taskbar Entry does not work for messages in incoming chat
https://bugs.kde.org/show_bug.cgi?id=365990 Bug ID: 365990 Summary: Taskbar Entry does not work for messages in incoming chat Product: telepathy Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: k...@jayeshbadwaik.in When there is an incoming chat which is not already open, I get an animated task bar entry. However, when there is a new message in an already open chat window, then there is no such taskbar entry even after enabling "Mark Taskbar Entry" for "Incoming Message in Active Chat". This is useful for cases, where the chat window is open but it is not active/on other desktop/etc Reproducible: Always Steps to Reproduce: 1. Go online 2. Open a chat with someone 3.Ask that person to send a message while keeping the chat window open Expected Results: When the option "Mark Taskbar Entry" is enabled for "Incoming Messages in Active Chat", there should be a taskbar entry even for open chat windows. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365607] kwin_x11: after screen power saving, screen stays blank
https://bugs.kde.org/show_bug.cgi?id=365607 --- Comment #4 from arne anka --- xrender is just a remnant of the various attempts to minmize the constant plasmashell crashes. since there's apparently no documentation whatsoever: what are the differences and why would OpenGL be better? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=361360 --- Comment #36 from Jesse --- I can definitely empathize with the technical struggles behind trying to make multiple tracks with clips over them playing back smoothly. I once looked at the code out of curiosity (with no programming background), and I near threw up from the confusion. I paid a therapist for a week to counsel me through the trauma. :) Whatever path you think will get the job done best, I'm all for it. From the end user's perspective, all I can say is this: the expected use and experience from the timeline is to use any number of clips (video, .png, title) in any number of tracks - overlapping each other or not - properly showing transparency on each one, and experiencing smooth playback (if their machine/CPU/GPU with movit can handle it). Having effects/filters/etc. on clips is another matter entirely, and you've given a GREAT remedy with the Preview Render feature -- truly a fantastic solution to the framerate drop when playing back clips with FX. I've used it on multiple projects, already, and it's saved me a lot of time. I know using the composite and Affine transitions over clips may seem like the best course because it's already established, but I've never really been for the Affine or composite transitions since my first encounter with Kdenlive (in the form of yellow bars) for two reasons: 1. Because it really makes the term "transition" confusing. Transitions should be moving FROM one clip TO another; one ending, and the other beginning. At least, that's how the term is used in the Industry. Using a "transition" simply to overlay one clip over another doesn't, to the non-uber-techie end user, make sense. And 2. It's making the user take an extra step to do something that they're expecting the editor to do automatically. Other editors you don't have to do anything to make sure that the transparency in any kind of clip shows normally. It's one of the reasons I was - and am - for composite tracks in the first place: it makes the timeline behave like one would expect. If having the "composite transition" built into the timeline would allow for smooth playback, using multiple clips (3 or more) over each other with proper transparency, would show in the monitor exactly how the rendered video would look, and would allow for real-time playback, then I think that would be a great decision. :) Alright, I won't beat a dead horse about it. I'll keep running some more tests from the git master version. Let's keep working to find an elite solution, you know? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=361360 --- Comment #35 from Wegwerf --- Strange: "melt -query transitions" shows "qtblend" transition. But I don't see it in Kdenlive's transition list pane??? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=361360 --- Comment #34 from Wegwerf --- Seeing also a slow-down with a test project of mine, compositing a single title clip on top of a mp4 clip. Interestingly, the fps doesn't immediately drops down as with Affine, but it takes several seconds into the title clip before the frame rate drops from 25fps to 19fps. Strange... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulfer changed: What|Removed |Added CC||ivan.cu...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulfer changed: What|Removed |Added CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] New: Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989
Bug ID: 365989
Summary: Default desktop layout is not loaded properly from
template
Product: plasmashell
Version: 5.7.2
Platform: ROSA RPMs
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Desktop Containment
Assignee: se...@kde.org
Reporter: pul...@list.ru
Default desktop layout is not loaded properly from system template. It happens
because Plasma Shell cannot create an activity ("Failed to create and switch to
the activity" message in .xsession-errors).
This commit looks like an attempt to fix it:
https://quickgit.kde.org/?p=plasma-workspace.git&a=commitdiff&h=f7ef6ee87b8957bebc976b6fc9e0df279cea05f1
But in fact it only makes things worse (if backported to 5.7.2 package) -
Plasma Shell locks on load, there's only black screen without desktop and
panel.
You can try to download ROSA Desktop ISO (with Plasma 5.7.2 + backported
f7ef6ee87b8957bebc976b6fc9e0df279cea05f1) and start it in live mode to
reproduce Plasma deadlock:
https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15706
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)
https://bugs.kde.org/show_bug.cgi?id=361360 --- Comment #33 from Jesse --- You bet. I'm still working on the other stuff, but on the project with the two non-transparent clips, I found this in the .kdenlive saved file: 3 4 0 0 qtblend 237 0 5 mix 1 1 237 3 5 0 0 qtblend 237 I'm assuming it means that it's using the qtblend, yeah? Slow playback is still occurring, today: 24fps goes down to 9fps using the same files used in the video. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364850] If any docker is in focus e.g. layer docker , canvas zoom function with mouse scrollwheel is gone. The contents of the dockers is scrolled instead of canvas zoom
https://bugs.kde.org/show_bug.cgi?id=364850 anim...@gmail.com changed: What|Removed |Added CC||anim...@gmail.com --- Comment #13 from anim...@gmail.com --- I confirm this bug happens with Qt 5.7.0. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361822] git master: resetting effect does not work for bin effects
https://bugs.kde.org/show_bug.cgi?id=361822 --- Comment #1 from Jean-Baptiste Mardelle --- Git commit f23e07f981953be5ecffbbffc1f1f02749e98e36 by Jean-Baptiste Mardelle. Committed on 22/07/2016 at 18:03. Pushed by mardelle into branch 'Applications/16.08'. Fix reset effect in clip bin M +4-1src/effectstack/effectstackview2.cpp M +11 -0src/mltcontroller/clipcontroller.cpp M +1-0src/mltcontroller/clipcontroller.h http://commits.kde.org/kdenlive/f23e07f981953be5ecffbbffc1f1f02749e98e36 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 359073] web browser widget: shown website cannot be resized, always too small
https://bugs.kde.org/show_bug.cgi?id=359073 Janet changed: What|Removed |Added Version|5.4.3 |5.6.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347195] Panel disappears after an external monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=347195 ichramm changed: What|Removed |Added CC||jramirez...@gmail.com --- Comment #16 from ichramm --- It's been happening to me since last year! 1- Panel lost when second monitor is unplugged (goes back when plugging again) 2- Same happens when having two external monitors and disabling laptop screen: I have two external monitors at work (one of them connected to a lenovo dock), both same brand and model, 1920x1080 resolution, one of them is configured as primary output (the one connected to the dock). I get black screen when docking the laptop. restaring plasmashell usually solves the problem. Panel dissapears when when undocking the laptop. 3- Random black screen when plugging / unplugging a single secondary monitor -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 365138] Regression: new taskbar icon hard to read on both default themes
https://bugs.kde.org/show_bug.cgi?id=365138 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 365297] Systray icon not showing correctly in Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=365297 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 359518] No icons in the interface.
https://bugs.kde.org/show_bug.cgi?id=359518 Jean-Baptiste Mardelle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365988] Kwin crashes on firefox start
https://bugs.kde.org/show_bug.cgi?id=365988 Thomas Lübking changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Lübking --- run "kcmshell5 kwindecoration", switch to breeze. > When will you fix this issues with KWin finally? We deal with it sind a long > time now. Never. The bug is (we're not missing an "in" here..) QtQuick/QML. Get used to it. *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 --- Comment #20 from Thomas Lübking --- *** Bug 365988 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365988] New: Kwin crashes on firefox start
https://bugs.kde.org/show_bug.cgi?id=365988 Bug ID: 365988 Summary: Kwin crashes on firefox start Product: kwin Version: 5.6.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tho@gmx.net Application: kwin_x11 (5.6.5) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.6.4-301.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Kwin crashes on firefox start Not reprodusable. When will you fix this issues with KWin finally? We deal with it sind a long time now. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb753438940 (LWP 1155))] Thread 6 (Thread 0x7fb739696700 (LWP 1503)): #0 0x7fb7636a4103 in select () at /lib64/libc.so.6 #1 0x7fb764bc06df in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7fb764bc1dd4 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /lib64/libQt5Core.so.5 #3 0x7fb764bc230a in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fb764b735ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fb7649d2343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fb76afb18f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fb7649d699a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0 #9 0x7fb7636adead in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb738e95700 (LWP 1310)): #0 0x7fb766333bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb76bf6abc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fb76bf6ac09 in () at /lib64/libQt5Script.so.5 #3 0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0 #4 0x7fb7636adead in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb73bfff700 (LWP 1254)): #0 0x7fb7636a4103 in select () at /lib64/libc.so.6 #1 0x7fb764bc06df in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7fb764bc1dd4 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /lib64/libQt5Core.so.5 #3 0x7fb764bc230a in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fb764b735ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fb7649d2343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fb76afb18f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fb7649d699a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0 #9 0x7fb7636adead in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb74a866700 (LWP 1207)): #0 0x7fb7636a4103 in select () at /lib64/libc.so.6 #1 0x7fb764bc06df in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7fb764bc1dd4 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /lib64/libQt5Core.so.5 #3 0x7fb764bc230a in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fb764b735ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fb7649d2343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fb765e2a559 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fb7649d699a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0 #9 0x7fb7636adead in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fb74bf2b700 (LWP 1200)): #0 0x7fb7636a232d in poll () at /lib64/libc.so.6 #1 0x7fb764718f80 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fb76471ab79 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fb74c9d6da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7fb7649d699a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fb76632e5ca in start_thread () at /lib64/libpthread.so.0 #6 0x7fb7636adead in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fb753438940 (LWP 1155)): [KCrash Handler] #6 0x7fb76af9cd50 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags) () at /lib64/libQt5Qml.so.5 #7 0x7fb76af9daa7 in QQmlBinding::update(QFlags) () at /lib64/libQt5Qml.so.5 #8 0x7fb76afa7615 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /lib64/libQt5Qml.so.5 #9 0x7fb76af3142e in QQmlComponentPr
[kmail2] [Bug 365987] New: Ctrl + shortcut doesn't zoom-in in KMail
https://bugs.kde.org/show_bug.cgi?id=365987 Bug ID: 365987 Summary: Ctrl + shortcut doesn't zoom-in in KMail Product: kmail2 Version: 5.2.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sud...@sudhirkhanger.com Ctrl + and Ctrl - are universally popular shortcuts to for zoom-in and zoom-out. Ctrl - works in KMail but Ctrl + doesn't. Rather it require Ctrl+Shift++ to zoom-in. Is there a specific reason for using Ctrl+Shift++ instead of Ctrl + to zoom in? Reproducible: Always Steps to Reproduce: 1. Press Ctrl + in a message 2. 3. Actual Results: message is not zoomed-in Expected Results: Ctrl + should be used for zoom-in in messages Also KMail shortcut shows keyboard shortcut for zoom-in is Ctrl++ but it doesn't work. $ localectl System Locale: LANG=en_IN.UTF-8 VC Keymap: us X11 Layout: us,in X11 Variant: ,eng -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 --- Comment #9 from Bollebib --- this is potentially a duplicate of this bug? https://bugs.kde.org/show_bug.cgi?id=344907 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 --- Comment #8 from Bollebib --- I also encounter this consisently on windows version of krita 3.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 Bollebib changed: What|Removed |Added CC||kwadraatn...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365955] crash if I insert a track
https://bugs.kde.org/show_bug.cgi?id=365955 --- Comment #8 from Wegwerf --- http://thediveo-e.blogspot.de/2016/04/new-ppas-for-kdenlive-on-ubuntu.html lists the available project ppas; take the stable one. Also, make sure that the Plasma shell for KDE 5 is installed, as well as the Breeze ixon theme. Please check the forum for more information about how to install on non-Kubuntu systems, such as Ubuntu, which is Gnome-based. Please use the forum search. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365986] New: krdc includes no application icon
https://bugs.kde.org/show_bug.cgi?id=365986 Bug ID: 365986 Summary: krdc includes no application icon Product: krdc Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: rdie...@math.unl.edu org.kde.krdc.desktop references: Icon=krdc But includes no icon itself. This was mitigated in the past since oxygen-icons includes a krdc icon, but * (kde) plasma no longer uses oxygen by default * other desktops don't use oxygen icons either the freedesktop/xdg spec recommends applications install their own icons into the hicolor icon theme. Fwiw, in fedora, we work-around the issue by copying the oxygen-styled krdc icons into hicolor in krdc packaging. It would be nice to not have to do that. :) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5
https://bugs.kde.org/show_bug.cgi?id=354082 --- Comment #22 from Sven Brauch --- Can we maybe fix this in konsole instead? Its use of the API does seem strange judging from what you describe. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 346898] audio/video desync for clips with "start:" != 00:00:00.0
https://bugs.kde.org/show_bug.cgi?id=346898 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Can you please try playing your original clip using melt to see if the desync is already happedning at the MLT layer? If yes, this needs to be reported upstream to the MLT project, otherwise it may be in Kdenlive's ballpark. -- You are receiving this mail because: You are watching all bug changes.
