[kdenlive] [Bug 365851] git master: image sequence clip length incorrectly set after expanding library (MLT) clip
https://bugs.kde.org/show_bug.cgi?id=365851 --- Comment #1 from Jean-Baptiste Mardelle --- Cannot reproduce with current 16.08 or git, maybe this was fixed by Vincent's recent work on the Library. Can you check again? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364836] git master: after you insert 2 clips at the beginning of an empty timeline if you trim the second clip it jumps forward
https://bugs.kde.org/show_bug.cgi?id=364836 Jean-Baptiste Mardelle changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358402] Segmentation fault when adding a new track
https://bugs.kde.org/show_bug.cgi?id=358402 Jean-Baptiste Mardelle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 362438] Wrong frame size when rendering VOB (DVD)
https://bugs.kde.org/show_bug.cgi?id=362438 Jean-Baptiste Mardelle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351407] KDE/kactivitymanagerd crashes when moving playhead with mouse
https://bugs.kde.org/show_bug.cgi?id=351407 Wegwerf changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349323] Crash when add directory with several FLAC files to prtoject
https://bugs.kde.org/show_bug.cgi?id=349323 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349146] Cannot use video clips
https://bugs.kde.org/show_bug.cgi?id=349146 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351758] Backwards goes forwards then backwards
https://bugs.kde.org/show_bug.cgi?id=351758 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Peter, as far as I remember, there has been some fix covering performance of play/pause. Can you please check with a recent beta from the project's ppa repos? Alternatively, can you please check the stble 16.04.2 anyway? If the bug's gone I would like to ask you to be so kind as to close this report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350398] 15.08 - White Background in title editor when using movit
https://bugs.kde.org/show_bug.cgi?id=350398 Wegwerf changed: What|Removed |Added Resolution|--- |FIXED CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362241] Rectangular Region option does not preview and does not save an image after 15.12.3-2 -> 16.04.0-1
https://bugs.kde.org/show_bug.cgi?id=362241 --- Comment #14 from Boudhayan Gupta --- Have you tried clicking the arrow next to the Save and Exit button and then clicking Preferences? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 347264] 15.04.0 Crashes at start
https://bugs.kde.org/show_bug.cgi?id=347264 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||wegwerf-1-...@gmx.de Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353537] Can't add multiple clips at once anymore
https://bugs.kde.org/show_bug.cgi?id=353537 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Michal, can you please test if the bug is still present with the recent stable Kdenlive version 16.04.2? The dialog size issue looks like an upstream Arch or KF5 issue. If the bug is gonr, then I ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353641] kdenlive-15.08.1 Track buttons in the timeline are too small for HiDPI 2880x1620
https://bugs.kde.org/show_bug.cgi?id=353641 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Anton, recent beta 16.7.90 has fixes for the track headers and buttons: you can now resize the track header width by dragging the right end of the header block, you'll notice that the mouse cursor turns into a resize cursor when hoovering over the dividing line. Can you please check if the bug has been fixed for you? If yes, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 366268] New: Kagregator failed
https://bugs.kde.org/show_bug.cgi?id=366268 Bug ID: 366268 Summary: Kagregator failed Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: enric.sanchez.dux...@gmail.com Application: kontact (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: reading news within kagregator, i seleected a new and i opened it in an other tab The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc2dc226940 (LWP 3007))] Thread 18 (Thread 0x7fc230858700 (LWP 3652)): #0 0x7fc2d95c29cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc2d2e25740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc2d2de1e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2d2de2340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc2d2de24ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc2da109a9b in QEventDispatcherGlib::processEvents (this=0x7fc218008020, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7fc2da0b0dea in QEventLoop::exec (this=this@entry=0x7fc230857c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7fc2d9ecd8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7fc2d9ed284e in QThreadPrivate::start (arg=0x44180e0) at thread/qthread_unix.cpp:331 #9 0x7fc2d360c6fa in start_thread (arg=0x7fc230858700) at pthread_create.c:333 #10 0x7fc2d95d2b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7fc24d78c700 (LWP 3599)): #0 0x7fc2d2e26ac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc2d2de1b51 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc2d2de2317 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2d2de24ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc2da109a9b in QEventDispatcherGlib::processEvents (this=0x7fc244004bc0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fc2da0b0dea in QEventLoop::exec (this=this@entry=0x7fc24d78bc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fc2d9ecd8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fc2d9ed284e in QThreadPrivate::start (arg=0x3438a30) at thread/qthread_unix.cpp:331 #8 0x7fc2d360c6fa in start_thread (arg=0x7fc24d78c700) at pthread_create.c:333 #9 0x7fc2d95d2b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fc231ffb700 (LWP 3523)): #0 0x7fc2d2e26ae4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc2d2de1920 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc2d2de22cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2d2de24ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc2da109a9b in QEventDispatcherGlib::processEvents (this=0x2ed8090, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fc2da0b0dea in QEventLoop::exec (this=this@entry=0x7fc231ffac80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fc2d9ecd8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fc2d9ed284e in QThreadPrivate::start (arg=0x2eae7f0) at thread/qthread_unix.cpp:331 #8 0x7fc2d360c6fa in start_thread (arg=0x7fc231ffb700) at pthread_create.c:333 #9 0x7fc2d95d2b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fc2327fc700 (LWP 3521)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7fc2d95c29c2 in read () at ../sysdeps/unix/syscall-template.S:84 #2 0x7fc2d2e25740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2d2de1e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc2d2de2340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc2d2de24ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc2da109a9b in QEventDispatcherGlib::processEvents (this=0x7fc2180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #7 0x7fc2da0b0dea in QEventLoop::exec (this=this@entry=0x7fc2327fbc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7fc2d9ecd8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #9 0x7fc2d9ed
[kdenlive] [Bug 353657] kdenlive-15.08.1 lower status bar buttons are too narrow for HiDPI 2880x1620
https://bugs.kde.org/show_bug.cgi?id=353657 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||wegwerf-1-...@gmx.de Resolution|--- |FIXED --- Comment #1 from Wegwerf --- This is an upstream packaging failure in the icon themes. Make sure that you've installed and selected the breeze icon theme. With recent Kdenlive versions you can now force the builtin Breeze icon theme. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361086] git master 2016-03-28 Application crash when applying layout
https://bugs.kde.org/show_bug.cgi?id=361086 --- Comment #18 from Evert Vorster --- Created attachment 100384 --> https://bugs.kde.org/attachment.cgi?id=100384&action=edit GDB Backtrace -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353678] kdenlive-15.08.1 title animation buttons are too low for HiDPI 2880x1620
https://bugs.kde.org/show_bug.cgi?id=353678 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Wegwerf --- Also loks like an icon theme issue. Make sure that you have the Breeze icon theme installed and activated. For dialog button clipping, please resize the dialog or change the system font size. Obviously the buttons don't fit into the available space, so you need to make room by resizing, and if this is not possible, by reducing system font size. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361086] git master 2016-03-28 Application crash when applying layout
https://bugs.kde.org/show_bug.cgi?id=361086 --- Comment #19 from Evert Vorster --- Created attachment 100385 --> https://bugs.kde.org/attachment.cgi?id=100385&action=edit Valgrind log of the failure Hi there. I am home again, and am able to make kdenlive crash with just applying a layout when movit is enabled. I have added a gdb and a valgrind log of the failure. Where are the profile files saved, please? I want to attach the profile that I am trying to apply as well. I have re-built kdenlive, mlt and movit with debugging symbols enabled. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353751] right after install on new system: buttons without image - click them; kdenlive crashes.
https://bugs.kde.org/show_bug.cgi?id=353751 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Wegwerf --- Maurice, this is a Mint packaging issue. Buttons without images clearly indicate that the required icons are missing. Make sure that you have installed and activated the Breeze icon theme. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354018] Color shifting when importing any clip
https://bugs.kde.org/show_bug.cgi?id=354018 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Gabriele, can you please checj with recent stable Kdenlive 16.04.2 and MLT 6.2.0 if the problem still persists? If not then I would like to ask you to be so kind as to close this report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361087] git master 2016-03-28 Application crash when dragging a clip to timeline
https://bugs.kde.org/show_bug.cgi?id=361087 --- Comment #5 from Evert Vorster --- This may be related to bug 361086. I just checked, and it still segfaults in the same way. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354497] Audio don't split
https://bugs.kde.org/show_bug.cgi?id=354497 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Gil, I cannot reproduce with stable Kdenlive 16.04.2. Can you please test with the recent stable release? If the problem still persists, can you please file a comprehensive bug report, detailing what you were doing before the bug appears, as well as supplying a minimal example project showing the bug? If the problem' gone, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 360196] can't open Kphotoalbum ("error reading next element"): found duplicate attributes in tags in index.xml photos database
https://bugs.kde.org/show_bug.cgi?id=360196 Tobias Leupold changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- 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 --- Comment #23 from Rog131 --- (In reply to gurpal2000 from comment #20) > (In reply to Rog131 from comment #17) > > At here, with the > > > > Qt 5.7.0 > > KF 5.7.2 > > Plasma 5.7.2 > > Arch Linux > > > > Disabling the lines from the plasma-workspace-5.7.2 shell/desktopview.cpp as > > told at: https://bugs.kde.org/show_bug.cgi?id=365014#c5 and > > https://phabricator.kde.org/D2121 helps. No ill effects detected. > > Sorry where is this file located on an arch file system? At here - short version: - Grabbing Arch sources from https://www.archlinux.org/packages/extra/x86_64/plasma-workspace/ - Editing the ../src/plasma-workspace-5.7.2/shell/desktopview.cpp - Building, makepkg with the '-e' option. - Installing, pacman with the '-U' option. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353641] kdenlive-15.08.1 Track buttons in the timeline are too small for HiDPI 2880x1620
https://bugs.kde.org/show_bug.cgi?id=353641 --- Comment #3 from Anton Gubarkov --- Created attachment 100386 --> https://bugs.kde.org/attachment.cgi?id=100386&action=edit small icons screenshot Hi, thank you very much for your efforts to support HiDPI displays. A lot of icons are of normal size now. However the track control buttons are still very small for me. Please see the attached screenshot. They look OK @ 1920x1080, but too small @2880x1620 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354018] Color shifting when importing any clip
https://bugs.kde.org/show_bug.cgi?id=354018 --- Comment #2 from Gabriele Musco --- It looks like it's been fixed. Thanks, I'll close this bug Il giorno sab 30 lug 2016 alle 10:11, Wegwerf via KDE Bugzilla ha scritto: > https://bugs.kde.org/show_bug.cgi?id=354018 > > Wegwerf changed: > >What|Removed |Added > > CC||wegwerf-1-...@gmx.de > > --- Comment #1 from Wegwerf --- > Gabriele, can you please checj with recent stable Kdenlive 16.04.2 > and MLT > 6.2.0 if the problem still persists? If not then I would like to ask > you to be > so kind as to close this report. Thank you very much for your > cooperation! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353641] kdenlive-15.08.1 Track buttons in the timeline are too small for HiDPI 2880x1620
https://bugs.kde.org/show_bug.cgi?id=353641 --- Comment #4 from Anton Gubarkov --- Created attachment 100388 --> https://bugs.kde.org/attachment.cgi?id=100388&action=edit screenshot with wrong/missing icons I also experience wrong/missing icons for some buttons. I tried to highlight them in the attached screenshot. Please note that I run kdenlive from gnome 3.20 desktop. I have a git version of kdenlive and breeze-icons. maybe I'm missing something else from kde. I also installed kde from git. Thanks again, Anton. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353678] kdenlive-15.08.1 title animation buttons are too low for HiDPI 2880x1620
https://bugs.kde.org/show_bug.cgi?id=353678 --- Comment #2 from Anton Gubarkov --- Created attachment 100389 --> https://bugs.kde.org/attachment.cgi?id=100389&action=edit screenshot of title editor with wrong icons The size of icons and other elemets is ok now. However the images are not correct on some icons. I run kdenlive-git (refreshed today) and breeze-icons-git (refreshed today) under Gnome 3.20 desktop. maybe I miss some vital kde component? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353641] kdenlive-15.08.1 Track buttons in the timeline are too small for HiDPI 2880x1620
https://bugs.kde.org/show_bug.cgi?id=353641 --- Comment #5 from Jean-Baptiste Mardelle --- Hi Anton, In recent Kdenlive versions, I added an option to enforce breeze icons on non KDE Desktop. This option should be enabled for new Kdenlive users, however it will not be the default if you already have a kdenlive config file. Can you try enabling it and let me know if it fixes the problem? Option is : Settings > Force Breeze Icon theme -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366246] Plasmashell restarts randomly, taskbar disappears and reappears after +/- 10 seconds
https://bugs.kde.org/show_bug.cgi?id=366246 Robby Pedrica changed: What|Removed |Added Resolution|FIXED |BACKTRACE --- Comment #5 from Robby Pedrica --- Ok so I decided to start with a new kde profile but before doing that, I removed 2 folders in ~/.kde: cache- tmp- There seems to be a big improvement: 1. plasmashell CPU process no longer takes a large amount of CPU ( at least continuously ) 2. I can no longer cause the issue when starting "About System" The original problem still occurs though ( ie. plasmashell randomly crashing and restarting ) and on 1 occasion I've received a crash report - as follows: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f65ecc8e7c0 (LWP 30106))] Thread 27 (Thread 0x7f64af75f700 (LWP 30347)): #0 0x7f65e3b3936f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f65e540dc4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f652a0d7947 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f652a0db658 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f652a0d942f in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f65e540ceb9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f65e3b33684 in start_thread () at /lib64/libpthread.so.0 #10 0x7f65e47f2efd in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f64b4f5a700 (LWP 30346)): #0 0x7f65e3b3936f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f65e540dc4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f652a0d7947 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f652a0db658 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f652a0d942f in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f65e540ceb9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f65e3b33684 in start_thread () at /lib64/libpthread.so.0 #10 0x7f65e47f2efd in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f64b575b700 (LWP 30345)): #0 0x7f65e3b3936f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f65e540dc4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f652a0d7947 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f652a0db658 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f652a0d6ba9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f652a0db6a2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f652a0d6ba9 i
[kdenlive] [Bug 353641] kdenlive-15.08.1 Track buttons in the timeline are too small for HiDPI 2880x1620
https://bugs.kde.org/show_bug.cgi?id=353641 Anton Gubarkov changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Anton Gubarkov --- YES!, after I forced the breeze icon theme all icons are in place and the size is OK. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 366269] New: konqueror crashed when i tried to open a link from kmail
https://bugs.kde.org/show_bug.cgi?id=366269 Bug ID: 366269 Summary: konqueror crashed when i tried to open a link from kmail Product: konqueror Version: 4.14.2 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: montbs+...@gmail.com Application: konqueror (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: Debian GNU/Linux 8.5 (jessie) -- Information about the crash: I was watching my email from Kmail and when I wanted to open a link, having by default application to view the URL, Konqueror, this has been fallen. The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7faaa579f780 (LWP 6476))] Thread 5 (Thread 0x7faa85d81700 (LWP 6477)): #0 0x7faaa2f34e0d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7faa92376f45 in ?? () from /usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.340.96 #2 0x7faa9fe62e50 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7faa9fe1f96c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7faa9fe1fe83 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7faa9fe1fffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7faaa43b4d37 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7faaa4384271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7faaa43845d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7faaa4278e99 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7faa9b7c3dde in ?? () from /usr/lib/libkio.so.5 #11 0x7faaa427b70f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7faaa07110a4 in start_thread (arg=0x7faa85d81700) at pthread_create.c:309 #13 0x7faaa2f4187d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7faa7fb7a700 (LWP 6479)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7faa987fd06f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7faa987fd0a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7faaa07110a4 in start_thread (arg=0x7faa7fb7a700) at pthread_create.c:309 #4 0x7faaa2f4187d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7faa7e1de700 (LWP 6480)): #0 0x7fff963ede4e in clock_gettime () #1 0x7faaa2f4e4cd in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7faaa42d2a05 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7faaa43b5b85 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7faaa43b446c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7faaa43b4535 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7faa9fe1f45d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7faa9fe1fe0b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7faa9fe1fffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7faaa43b4d37 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7faaa4384271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7faaa43845d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7faaa4278e99 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x7faaa427b70f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #14 0x7faaa07110a4 in start_thread (arg=0x7faa7e1de700) at pthread_create.c:309 #15 0x7faaa2f4187d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7faa7ce60700 (LWP 6482)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7faa9851f973 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7faa9882c7f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7faaa07110a4 in start_thread (arg=0x7faa7ce60700) at pthread_create.c:309 #4 0x7faaa2f4187d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7faaa579f780 (LWP 6476)): [KCrash Handler] #6 0x7faa97be05a3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #7 0x7faa97be008f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.s
[kdenlive] [Bug 354497] Audio don't split
https://bugs.kde.org/show_bug.cgi?id=354497 Gil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354496] unrelated transitions in command
https://bugs.kde.org/show_bug.cgi?id=354496 Gil changed: What|Removed |Added Resolution|WORKSFORME |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354018] Color shifting when importing any clip
https://bugs.kde.org/show_bug.cgi?id=354018 --- Comment #3 from Wegwerf --- Glad to hear! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351758] Backwards goes forwards then backwards
https://bugs.kde.org/show_bug.cgi?id=351758 --- Comment #3 from Peter --- (In reply to Wegwerf from comment #2) > Peter, as far as I remember, there has been some fix covering performance of > play/pause. Can you please check with a recent beta from the project's ppa > repos? Alternatively, can you please check the stble 16.04.2 anyway? If the > bug's gone I would like to ask you to be so kind as to close this report. > Thank you very much for your cooperation! I wouldn't normally change the status of a bug I'm not assigned to. Are you sure that's okay? I have several bugs reported that I could probably close at this stage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366270] New: I don't know what the problem is, I just wanted to help.
https://bugs.kde.org/show_bug.cgi?id=366270 Bug ID: 366270 Summary: I don't know what the problem is, I just wanted to help. Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: iamgr...@zoho.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was searching my mobilephone on kdeconnect then crash notification appeared. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9ab64fe7c0 (LWP 1808))] Thread 32 (Thread 0x7f9a9ff31700 (LWP 1817)): #0 0x7f9aafa01bfd in poll () at /lib64/libc.so.6 #1 0x7f9ab4955422 in () at /usr/lib64/libxcb.so.1 #2 0x7f9ab495700f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f9aa20823c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f9ab00fc32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f9a9d2ff700 (LWP 1915)): #0 0x7f9aac120cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9aac0dee4a in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9aac0def7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9ab032ed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9ab02d5d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9ab00f761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f9ab340be18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f9ab00fc32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f9a8b764700 (LWP 1929)): #0 0x7f9aaf20f03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a9628cac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f9a9628c637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f9a8af63700 (LWP 1930)): #0 0x7f9aaf20f03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a9628cac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f9a9628c637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f9a8a762700 (LWP 1931)): #0 0x7f9aaf20f03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a9628cac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f9a9628c637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f9a89f61700 (LWP 1932)): #0 0x7f9aaf20f03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a9628cac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f9a9628c637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f9a89760700 (LWP 1933)): #0 0x7f9aaf20f03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a9628cac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f9a9628c637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f9a88f5f700 (LWP 1934)): #0 0x7f9aaf20f03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a9628cac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f9a9628c637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f9a8875e700 (LWP 1935)): #0 0x7f9aaf20f03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9a9628cac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f9a9628c637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f9aaf20b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9aafa0a02d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f9
[kdenlive] [Bug 351758] Backwards goes forwards then backwards
https://bugs.kde.org/show_bug.cgi?id=351758 --- Comment #4 from Wegwerf --- Peter, as you are the reporter of this bug feel free to chnge the status. As devs are fixing errors, they may miss some bug reports also now covered by a fix. So, is this bug still present? If not, please be so kind as to close this report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366271] New: Kdenlive project XML does not validate due no missing kdenlive namespace declaration for customeffects attribute
https://bugs.kde.org/show_bug.cgi?id=366271 Bug ID: 366271 Summary: Kdenlive project XML does not validate due no missing kdenlive namespace declaration for customeffects attribute Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de Sometimes, it may be necessary or desirable to process Kdenlive project files using XML tools. Some of these tools, such as the Firefox browser as well as all libxml2-based tools, cannot process some, but not all, Kdenlive XML project files. As it turns out, sometimes Kdenlive projects contain an attribute kdenlive:customeffects. However, the project document lacks any declaration of the namespace kdenlive. In turn, these files won't be processed by XML tools, but instead turned down. To allow correct processing of such project files, it will be sufficient that Kdenlive generates a proper namespace declaration in some suitable place (opening mlt tag), such as: http://www.kdenlive.org/"; ...> Also, I see both an attribute as well as a property element both for custom effects using the same namespace and same name. Which one of the two is the real one? What if both differ? What if only one is present? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349146] Cannot use video clips
https://bugs.kde.org/show_bug.cgi?id=349146 cehuis...@web.de changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #3 from cehuis...@web.de --- Changed System in the last days to Lubuntu 16.04, installed Version kdenlive 15.12.3 works fine. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358484] movit library brightens rendered video
https://bugs.kde.org/show_bug.cgi?id=358484 Peter changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Peter --- No longer present 16.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351758] Backwards goes forwards then backwards
https://bugs.kde.org/show_bug.cgi?id=351758 Peter changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Peter --- No longer present 16.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358781] Strange monitor behaviour when switching from full to windowed repeatedly.
https://bugs.kde.org/show_bug.cgi?id=358781 Peter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Peter --- No longer present 16.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365851] git master: image sequence clip length incorrectly set after expanding library (MLT) clip
https://bugs.kde.org/show_bug.cgi?id=365851 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Wegwerf --- Hi, Jean-Baptiste, tested against my tricky library clip. This bug as such is now correctly fixed: the clip length is now correct and I can resize the timeline image sequence clip beyond all limits. So thank you very much for fixing this! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358448] Stem export should work on every track
https://bugs.kde.org/show_bug.cgi?id=358448 Peter changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Peter --- No longer present 16.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358452] stem doesn't queue jobs
https://bugs.kde.org/show_bug.cgi?id=358452 Peter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Peter --- Eh, kinda prefer the parallelism even if it isn't consistent. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366272] New: git master: expanding library MLT clip with same clip used multiple times in timeline creates multiple bin clip instances
https://bugs.kde.org/show_bug.cgi?id=366272 Bug ID: 366272 Summary: git master: expanding library MLT clip with same clip used multiple times in timeline creates multiple bin clip instances Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de With the recently fixed bug of multiple title clips disappearing during expansion of a MLT/Kdenlive library clip I now see another bug that may be caused by this fix: when a library clip has the same bin clip (image clip, title clip) used multiple times in the timeline, then after expansion the bin will hold multiple instances of the same image or title clip. Could this be a producer identity issue during expansion? This is especially unfortunate in case a title clip needs to be edited, then all its clones need to be edited separately. I would expect that all clones of the same image and title clip are being fused into a single bin clip instance, instead of multiple clone clips. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 348674] Crash Recovery only works properly for unsaved projects
https://bugs.kde.org/show_bug.cgi?id=348674 Wegwerf changed: What|Removed |Added Resolution|--- |FIXED CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353244] git master: Changing Project Settings/Project Folder - Directory not pre-selected
https://bugs.kde.org/show_bug.cgi?id=353244 Wegwerf changed: What|Removed |Added Summary|Changing Project|git master: Changing |Settings/Project Folder - |Project Settings/Project |Directory not pre-selected |Folder - Directory not ||pre-selected Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- I can confirm this behavior even for recent git master. I'm adding "git master:" to the title to signal that it's still an inconvenient bug. I'm struggling around it myself with every project. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353539] git master: Monitor starts playing previously selected clip after adding new clip with double click in file dialog
https://bugs.kde.org/show_bug.cgi?id=353539 Wegwerf changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||wegwerf-1-...@gmx.de Summary|15.08.1 Monitor starts |git master: Monitor starts |playing previously selected |playing previously selected |clip after adding new clip |clip after adding new clip ||with double click in file ||dialog --- Comment #1 from Wegwerf --- I can confirm this bug, but only when you double click on a media file in the file open dialog. If you simply press "Ok" instead, then nothing bad happens. Looks as if the dialog double click somehow gets duplicated into Kdenlive's main window. I'm updating the report title to signal it's still a present issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350177] Feature request: add mute function for playback in clip monitor
https://bugs.kde.org/show_bug.cgi?id=350177 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Wegwerf --- There's a "mute monitor" action in recent Kdenlive versions (don't know when it came in), so I think I may safely close this report as RESOLVED FIXED now. Farid, if there should be an issue with this action, feel free to either reopen, or yet better, file a new report with an approriate title referring to the "mute monitor" action. Thank you all very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 366273] New: jamendo streams are played for e while; but stopping immediately
https://bugs.kde.org/show_bug.cgi?id=366273 Bug ID: 366273 Summary: jamendo streams are played for e while; but stopping immediately Product: amarok Version: 2.8.0 Platform: openSUSE RPMs URL: http://www.jamendo.de OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Playback/Streams Assignee: amarok-bugs-d...@kde.org Reporter: ha...@gmx.net Jamendo streams are played for e while; but stopping immediately. Trying to restart, AMAROK doesnt play any stream or mp3 rsp. ogg file. You must exit or kill amarok and restart. Reproducible: Always Steps to Reproduce: 1. Play any Jamendo-file, like http://api.jamendo.com/get2/stream/track/redirect/?id=136007&streamencoding=mp32 2. After some minutes, the play stops immediately 3. Try to yuse the controls; they will not work. 4. End and restart amarok Actual Results: Amarok works well only with a playlist of local files. If you use jamendo streaming files, the error occurs by the time (after some minutes.) start debug info libhd version 21.24 (x86-64) [7688] using /var/lib/hardware kernel version is 4.7 - /proc/cmdline - BOOT_IMAGE=/boot/vmlinuz-4.7.0-5-default root=UUID=1998575c-7225-4da1-acfe-9dafd0e09524 resume=/dev/sda5 splash=silent quiet showopts - /proc/cmdline end - debug = 0xff77 probe = 0x15938fcdaa17fcf9fffe (+memory +pci +isapnp +net +floppy +misc +misc.serial +misc.par +misc.floppy +serial +cpu +bios +monitor +mouse +scsi +usb -usb.mods +modem +modem.usb +parallel +parallel.lp +parallel.zip -isa -isa.isdn +isdn +kbd +prom +sbus +int +braille +braille.alva +braille.fhp +braille.ht -ignx11 +sys -bios.vbe -isapnp.old -isapnp.new -isapnp.mod +braille.baum -manual +fb +pppoe -scan +pcmcia +fork -parallel.imm +s390 +cpuemu -sysfs -s390disks +udev +block +block.cdrom +block.part +edd +edd.mod -bios.ddc -bios.fb -bios.mode +input +block.mods +bios.vesa -cpuemu.debug -scsi.noserial +wlan -bios.crc -hal +bios.vram +bios.acpi -bios.ddc.ports=0 +modules.pata -net.eeprom +x86emu=dump -max -lxrc) shm: attached segment 9240623 at 0x7f76b2c05000 >> hal.1: read hal data >> floppy.1: get nvram - /proc/nvram - Checksum status: valid -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354549] Audio tracks auto-mute depending on their order
https://bugs.kde.org/show_bug.cgi?id=354549 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||wegwerf-1-...@gmx.de Ever confirmed|0 |1 --- Comment #2 from Wegwerf --- Chris, this sounds right like the so-called "internally added" audio mixers got, well, mixed up (sorry for the pun). I've seen this also with one of my older projects. We've found this out just these weeks and the recent Kdenlive 16.07.90 beta version already has fixes in place. There's even an online Kdenlive project analyzer that can help tracking down mixing issues: https://thediveo.github.io/kdenlive-project-analyzer/kdenlive-project-analyzer.html I would like to ask you to try your existing project loading into the recent beta version. The audio tracks then should behave as expected. If not, please add a single track, and check again, then audio mixing should be fine. You can later remove this empty track again. The reason is that Kdenlive now recreates its internal per-track audio mixers upon loading and in any case when adding or removing a timeline track. If this solves your problem, I would like to ask you to close this bug report as RESOLVED FIXED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353251] 1 video 2 audio tracks muted audio 2 kills audio 1
https://bugs.kde.org/show_bug.cgi?id=353251 Wegwerf changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #10 from Wegwerf --- Steve, this sounds right like the so-called "internally added" audio mixers got, well, mixed up (sorry for the pun). I've seen this also with one of my older projects. We've found this out just these weeks and the recent Kdenlive 16.07.90 beta version already has fixes in place. There's even an online Kdenlive project analyzer that can help tracking down mixing issues: https://thediveo.github.io/kdenlive-project-analyzer/kdenlive-project-analyzer.html I would like to ask you to try your existing project loading into the recent beta version. The audio tracks then should behave as expected. If not, please add a single track, and check again, then audio mixing should be fine. You can later remove this empty track again. The reason is that Kdenlive now recreates its internal per-track audio mixers upon loading and in any case when adding or removing a timeline track. If this solves your problem, I would like to ask you to close this bug report as RESOLVED FIXED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352428] 15.08: audio popping regression
https://bugs.kde.org/show_bug.cgi?id=352428 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #3 from Wegwerf --- Glad to see that you've found at least a workaround. As this bug is difficult to reproduce and probably is related to the distribution-specific audio system version and setup I don't see much chance to track this down properly. I would thus like to ask you that you close this bug report as RESOLVED (maybe WORKSFORME), if that's okay from your point of view. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350243] No Help no Handbooks at Kdenlive Menu: "Help"
https://bugs.kde.org/show_bug.cgi?id=350243 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- kdenlivefriend, unfortunately, I cannot reproduce your issue on my Kubuntu 16.04 installation: the KDE help app starts correctly showing the Kdenlive beginners guide. Is this bug still present? I suspect this to be a packager's problem, rather than a Kdenlive project issue -- my rationale is that my installation directly compiled from git master sources works as expected. If you don't have any indication to the contrary, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355255] Project Monitor Positions Video incorrectly if it's stacked on top of Clip Monitor initially
https://bugs.kde.org/show_bug.cgi?id=355255 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Qubodup, is this issue still present with the recent stable 16.04.2 release or the current git master/beta 16.07.90? If not, I would like to ask you to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354479] Effect Icons sometimes unreadable
https://bugs.kde.org/show_bug.cgi?id=354479 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #7 from Wegwerf --- Qubodup, is this bug report still relevant? If not, I would like to ask you to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353000] Kdenlive rotate (all incuding affine) don't recognize orientation flag
https://bugs.kde.org/show_bug.cgi?id=353000 Wegwerf changed: What|Removed |Added Resolution|--- |FIXED CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED --- Comment #5 from Wegwerf --- Downstream distro packaging issue, so closing this report here. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 348985] Clips with speed effect break if video properties altered
https://bugs.kde.org/show_bug.cgi?id=348985 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Qubodup, as there have been changes to the underlaying speed effect producer, I would like to ask you if this problem still persists? Kdenlive has switched from the old speed effect to the new timewarp producer that also supports audio. If your problem is fixed, I would like to ask you to close this report as fixed. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356066] crash on exit
https://bugs.kde.org/show_bug.cgi?id=356066 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Rouven, is this bug still present or has it been fixed? Can you please try using a recent stable Kdenlive release 16.04.2? If the bug has been fixed, then I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356535] Kdenlive does not respond to some hotkeys
https://bugs.kde.org/show_bug.cgi?id=356535 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- F, unfortunately I cannot reproduce on a recent Kdenlive 16.04.2 on Kubuntu 16.04. Do you still see this bug with the recent stable release of Kdenlive? If not, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356621] crash from affine transition
https://bugs.kde.org/show_bug.cgi?id=356621 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Farid, is this crash still present? If not ... well, you surely know the game by now... ;) Let us remove the stale stuff so the devs can better see what's still buggy. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356629] weird gui problem
https://bugs.kde.org/show_bug.cgi?id=356629 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Farid, as there were several changes and fixes to the clip properties pane, is your bug still present? If not,... ;) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353585] Effects Stack is a floating frameless window in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=353585 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Chris, is this bug still present with the recent stable Kdenlive 16.04.2 release? If not, can you please be so kind as to close this bug report? Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353125] Project broken after update to new kdenlive file format
https://bugs.kde.org/show_bug.cgi?id=353125 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #16 from Wegwerf --- Egor, can you please try again with a recent Kdenlive 16.04.2 release? Also, can you please supply some information as to which clips go missing: are there speed effects on them? Anything with the paths to these clips? What kind of clips are these? A/V clips? Title clips? Something else? Are these clips still in the project bin? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356847] New themed icons for configure Kdenlive dialog section "Timeline"
https://bugs.kde.org/show_bug.cgi?id=356847 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363329] git master: playback cannot be stopped after end of project with preview rendering
https://bugs.kde.org/show_bug.cgi?id=363329 --- Comment #2 from Wegwerf --- This seems to be a special case of my project; I'm investigating further as to what out point may have gone awry in the underlaying Kdenlive project XML document. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366242] mxf files are randomly incorrectly seeking
https://bugs.kde.org/show_bug.cgi?id=366242 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Same ffmpeg across old and new Kdenlive? -- 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 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #3 from Wegwerf --- Hi Farid, bug still present...? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 366274] New: Krunner fails to display & crashes
https://bugs.kde.org/show_bug.cgi?id=366274 Bug ID: 366274 Summary: Krunner fails to display & crashes Product: krunner Version: 5.7.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: nickgnor...@gmail.com Application: krunner (5.7.1) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.6.4-301.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: Typing name of program on the desktop to start the krunner and then the application - Unusual behavior I noticed: The krunner window does not display, but there is just a faint line where the bottom of thr window would be The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4f6883a940 (LWP 10812))] Thread 5 (Thread 0x7f4f3adeb700 (LWP 10821)): #0 0x7f4f6519332d in poll () at /lib64/libc.so.6 #1 0x7f4f5f94da46 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f4f5f94db5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f4f65fa724b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f4f65f565ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f4f65db5343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f4f681058f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f4f65db999a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f4f6188b5ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f4f6519eead in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4f3bfff700 (LWP 10818)): #0 0x7f4f61890bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4f439389a3 in radeon_drm_cs_emit_ioctl () at /usr/lib64/dri/r600_dri.so #2 0x7f4f439380e7 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x7f4f6188b5ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f4f6519eead in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4f4923b700 (LWP 10815)): #0 0x7f4f6519332d in poll () at /lib64/libc.so.6 #1 0x7f4f5f94da46 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f4f5f94db5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f4f65fa724b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f4f65f565ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f4f65db5343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f4f67471559 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f4f65db999a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f4f6188b5ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f4f6519eead in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f4f4ac2b700 (LWP 10814)): #0 0x7f4f6519332d in poll () at /lib64/libc.so.6 #1 0x7f4f63fddf80 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f4f63fdfb79 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f4f4d7aeda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f4f65db999a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f4f6188b5ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f4f6519eead in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f4f6883a940 (LWP 10812)): [KCrash Handler] #6 0x7f4f650d06f5 in raise () at /lib64/libc.so.6 #7 0x7f4f650d22fa in abort () at /lib64/libc.so.6 #8 0x7f4f604c3d04 in _dbus_abort () at /lib64/libdbus-1.so.3 #9 0x7f4f604ba73c in () at /lib64/libdbus-1.so.3 #10 0x7f4f604aac82 in dbus_message_new_method_call () at /lib64/libdbus-1.so.3 #11 0x7f4f67488f1b in QDBusMessagePrivate::toDBusMessage(QDBusMessage const&, QFlags, QDBusError*) () at /lib64/libQt5DBus.so.5 #12 0x7f4f67482e23 in QDBusConnectionPrivate::sendWithReplyAsync(QDBusMessage const&, QObject*, char const*, char const*, int) () at /lib64/libQt5DBus.so.5 #13 0x7f4f67484c26 in QDBusConnectionPrivate::sendWithReply(QDBusMessage const&, int, int) () at /lib64/libQt5DBus.so.5 #14 0x7f4f67485345 in QDBusConnectionPrivate::findMetaObject(QString const&, QString const&, QString const&, QDBusError&) () at /lib64/libQt5DBus.so.5 #15 0x7f4f67490fcd in QDBusInterfacePrivate::QDBusInterfacePrivate(QString const&, QString const&, QString const&, QDBusConnection const&) () at /lib64/libQt5DBus.so.5 #16 0x7f4f67491145 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () at /lib64/libQt5DBu
[krunner] [Bug 366274] Krunner fails to display & crashes
https://bugs.kde.org/show_bug.cgi?id=366274 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Kai Uwe Broulik --- It seems to crash in the AudioPlayerControlRunner, do you have a Media Player running and if so which one? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352428] 15.08: audio popping regression
https://bugs.kde.org/show_bug.cgi?id=352428 Dainius Masiliūnas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Dainius Masiliūnas --- Oh yea, this has been fixed for a while now in later releases, with the addition of the audio backend setting. -- 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 Ruman Gerst changed: What|Removed |Added CC||mrbo...@live.de -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 366273] jamendo streams are played for e while; but stopping immediately
https://bugs.kde.org/show_bug.cgi?id=366273 Myriam Schweingruber changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Myriam Schweingruber --- Which Phonon backend do you use? Please start amarok from the command line with these arguments: amarok -d --nofork and provide the last ca. 100 lines of output when the problem happens. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 366268] Kagregator failed
https://bugs.kde.org/show_bug.cgi?id=366268 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Laurent Montel --- it's a khtml bug. We switched to QtWebEngine now so for sure this bug will never fix in this version and it fixed in new version. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366243] Something's really wrong with the update sceduler/kisstroke/etc.
https://bugs.kde.org/show_bug.cgi?id=366243 --- Comment #1 from wolthera --- Aaaand, another one, this time on creating a new layer: Thread 1 (Thread 0x77f0e8c0 (LWP 8788)): #0 0x731a5974 in QSharedPointer::deref (d=0x12979e70) at /home/krita/Qt/5.6/gcc_64/include/QtCore/qsharedpointer_impl.h:495 #1 QSharedPointer::deref (this=) at /home/krita/Qt/5.6/gcc_64/include/QtCore/qsharedpointer_impl.h:488 #2 QSharedPointer::~QSharedPointer (this=, __in_chrg=) at /home/krita/Qt/5.6/gcc_64/include/QtCore/qsharedpointer_impl.h:309 #3 KisStrokesQueue::checkStrokeState (this=this@entry=0xd893750, hasStrokeJobsRunning=, runningLevelOfDetail=) at /home/krita/kde/src/krita/libs/image/kis_strokes_queue.cpp:493 #4 0x731a5bbf in KisStrokesQueue::processOneJob (this=this@entry=0xd893750, updaterContext=..., externalJobsPending=externalJobsPending@entry=false) at /home/krita/kde/src/krita/libs/image/kis_strokes_queue.cpp:476 #5 0x731a5d2e in KisStrokesQueue::processQueue (this=0xd893750, updaterContext=..., externalJobsPending=) at /home/krita/kde/src/krita/libs/image/kis_strokes_queue.cpp:359 #6 0x731ac7a9 in KisUpdateScheduler::processQueues (this=this@entry=0xd913938) at /home/krita/kde/src/krita/libs/image/kis_update_scheduler.cpp:359 #7 0x731ac96b in KisUpdateScheduler::barrierLock (this=0xd913938) at /home/krita/kde/src/krita/libs/image/kis_update_scheduler.cpp:335 #8 0x731bd188 in KisImage::barrierLock (this=0xd89db10, readOnly=readOnly@entry=false) at /home/krita/kde/src/krita/libs/image/kis_image.cc:411 #9 0x73250ee0 in KisLegacyUndoAdapter::addCommand (this=0xd9138a0, command=0x1297db60) at /home/krita/kde/src/krita/libs/image/kis_legacy_undo_adapter.cpp:50 #10 0x7770 in KisNodeCommandsAdapter::addNode (this=, node=..., parent=..., aboveThis=..., doRedoUpdates=doRedoUpdates@entry=false, doUndoUpdates=doUndoUpdates@entry=false) at /home/krita/kde/src/krita/libs/ui/kis_node_commands_adapter.cpp:62 #11 0x776f1493 in KisLayerManager::addLayerCommon (this=this@entry=0x4aed190, activeNode=..., layer=..., updateImage=, updateImage@entry=false) at /home/krita/kde/src/krita/libs/ui/kis_layer_manager.cc:460 #12 0x776f16cb in KisLayerManager::addLayer (this=0x4aed190, activeNode=...) at /home/krita/kde/src/krita/libs/ui/kis_layer_manager.cc:466 ---Type to continue, or q to quit--- #13 0x77706c61 in KisNodeManager::createNode (this=0xc250b28, nodeType=..., quiet=quiet@entry=false, copyFrom=...) at /home/krita/kde/src/krita/libs/ui/kis_node_manager.cpp:474 #14 0x7799afc4 in KisNodeManager::qt_static_metacall (_o=0xc250b28, _c=, _id=, _a=) at /home/krita/kde/build/libs/ui/moc_kis_node_manager.cpp:300 #15 0x75771cef in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #16 0x7577cd95 in QSignalMapper::mapped(QString const&) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #17 0x7577e1c2 in QSignalMapper::map(QObject*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #18 0x75771cef in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #19 0x76532952 in QAction::triggered(bool) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #20 0x765354ad in QAction::activate(QAction::ActionEvent) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #21 0x76535a8f in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #22 0x75771cef in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #23 0x768b54d2 in QAbstractButton::clicked(bool) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #24 0x766328c5 in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #25 0x76633624 in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #26 0x766337c4 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #27 0x766f4f4a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #28 0x7786742f in KisToolButton::mouseReleaseEvent (this=0xd6cb6e0, e=) at /home/krita/kde/src/krita/libs/ui/widgets/kis_tool_button.cpp:48 #29 0x7657e308 in QWidget::event(QEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #30 0x766f5019 in QToolButton::event(QEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #31 0x7653c04c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #32 0x76540f0e in QApplication::notify(QObject*, QEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #33 0x778d6917 in KisApplication::notify (this=, receiver=0xd6cb6e0, event=0x7fffcbc0) at /home/krita
[krita] [Bug 366243] Something's really wrong with the update sceduler/kisstroke/etc.
https://bugs.kde.org/show_bug.cgi?id=366243 --- Comment #2 from wolthera --- I think it has to do with the move-tool: Thread 1 (Thread 0x77f0e8c0 (LWP 15590)): #0 0x731a598d in KisStrokesQueue::checkStrokeState (this=this@entry=0xdb11010, hasStrokeJobsRunning=, runningLevelOfDetail=) at /home/krita/kde/src/krita/libs/image/kis_strokes_queue.cpp:534 #1 0x731a5bbf in KisStrokesQueue::processOneJob (this=this@entry=0xdb11010, updaterContext=..., externalJobsPending=externalJobsPending@entry=false) at /home/krita/kde/src/krita/libs/image/kis_strokes_queue.cpp:476 #2 0x731a5d2e in KisStrokesQueue::processQueue (this=0xdb11010, updaterContext=..., externalJobsPending=) at /home/krita/kde/src/krita/libs/image/kis_strokes_queue.cpp:359 #3 0x731ac7a9 in KisUpdateScheduler::processQueues (this=this@entry=0xdae00c8) at /home/krita/kde/src/krita/libs/image/kis_update_scheduler.cpp:359 #4 0x731ac96b in KisUpdateScheduler::barrierLock (this=0xdae00c8) at /home/krita/kde/src/krita/libs/image/kis_update_scheduler.cpp:335 #5 0x731bd188 in KisImage::barrierLock (this=0xdb14070, readOnly=readOnly@entry=false) at /home/krita/kde/src/krita/libs/image/kis_image.cc:411 #6 0x7780987b in KisToolUtils::clearImage (image=..., node=..., selection=...) at /home/krita/kde/src/krita/libs/ui/tool/kis_tool_utils.cpp:90 #7 0x777f233f in KisTool::deleteSelection (this=0xe6d9890) at /home/krita/kde/src/krita/libs/ui/tool/kis_tool.cc:554 #8 0x7775c9b5 in KisSelectionManager::clear (this=0xc231de0) at /home/krita/kde/src/krita/libs/ui/kis_selection_manager.cc:439 #9 0x75771cef in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #10 0x76532952 in QAction::triggered(bool) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #11 0x765354ad in QAction::activate(QAction::ActionEvent) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #12 0x76535e27 in QAction::event(QEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #13 0x7653c04c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #14 0x76540488 in QApplication::notify(QObject*, QEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #15 0x778d6917 in KisApplication::notify (this=, receiver=0xca02230, event=0x7fffcfb0) ---Type to continue, or q to quit--- at /home/krita/kde/src/krita/libs/ui/KisApplication.cpp:505 #16 0x75748e80 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #17 0x75d1478a in QShortcutMap::dispatchEvent(QKeyEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Gui.so.5 #18 0x75d14874 in QShortcutMap::tryShortcut(QKeyEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Gui.so.5 #19 0x75cd0a66 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Gui.so.5 #20 0x75ce5774 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Gui.so.5 #21 0x75cea465 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Gui.so.5 #22 0x75ccb6a3 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Gui.so.5 #23 0x7fffe5a68720 in ?? () from /home/krita/Qt/5.6/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5 #24 0x7fffee649127 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fffee649380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7fffee64942c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x757984e7 in QEventDispatcherGlib::processEvents(QFlags) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #28 0x75746efa in QEventLoop::exec(QFlags) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #29 0x7574ed9d in QCoreApplication::exec() () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #30 0x00404bc6 in main (argc=1, argv=) at /home/krita/kde/src/krita/krita/main.cc:230 Sometimes, selecting the move tool and doing < and > will allow me to save again when that wasn't possible before... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366244] Plasma crashed after login with new user
https://bugs.kde.org/show_bug.cgi?id=366244 --- Comment #1 from Jerry Ehlers --- I discovered that I could install nvidia-computeG02 and nvidia-gfxG02-kmp-default packages fine. But when I install the x11-video-nvidiaG02-304.131-42.1.x86_64 package then plasma5 crashes as soon as the desktop gets going. So for now I will just have to do without nvidia drivers. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363586] Kmail2 handles mailto: incorrectly. urlencoded does not work
https://bugs.kde.org/show_bug.cgi?id=363586 --- Comment #7 from Laurent Montel --- Git commit 2ee5bc147480baf205611d333fe68233f9e1aa47 by Montel Laurent. Committed on 30/07/2016 at 13:14. Pushed by mlaurent into branch 'Applications/16.08'. Convert %0A to \n M +1-1messagecore/autotests/stringutiltest.cpp M +6-0messagecore/src/utils/stringutil.cpp http://commits.kde.org/messagelib/2ee5bc147480baf205611d333fe68233f9e1aa47 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363586] Kmail2 handles mailto: incorrectly. urlencoded does not work
https://bugs.kde.org/show_bug.cgi?id=363586 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.3.0 Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdep ||im/b5411e67a29e2e74c14f7663 ||922f672a916968c5 --- Comment #8 from Laurent Montel --- Git commit b5411e67a29e2e74c14f7663922f672a916968c5 by Montel Laurent. Committed on 30/07/2016 at 13:20. Pushed by mlaurent into branch 'Applications/16.08'. Fix Bug 363586 - Kmail2 handles mailto: incorrectly. urlencoded does not work FIXED-IN: 5.3.0 M +2-1kmail/src/kmkernel.cpp http://commits.kde.org/kdepim/b5411e67a29e2e74c14f7663922f672a916968c5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363586] Kmail2 handles mailto: incorrectly. urlencoded does not work
https://bugs.kde.org/show_bug.cgi?id=363586 --- Comment #9 from Dominik George --- Hi, sorry, I do not think this patch is complete. In fact, I think it is just a new bug. Your patch simply replaces all %0A with \n in the body. In fact, the body needs to be passed through decodeMailtoUrl() or something like that just like the to= query parameter is. Moreover, the same applies to subject=, and *any* other field. (On a side note, the %xx encoding has nothing to do with HTML, it is URI encoding). You can use any mail in the Debian bug tracker and click the reply link to test whether the fix is complete. -nik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363586] Kmail2 handles mailto: incorrectly. urlencoded does not work
https://bugs.kde.org/show_bug.cgi?id=363586 --- Comment #10 from Dominik George --- Hi, my last comment actually came in between your two commits. I think the second commit might actually fix the bug. Thanks ☺! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362241] Rectangular Region option does not preview and does not save an image after 15.12.3-2 -> 16.04.0-1
https://bugs.kde.org/show_bug.cgi?id=362241 --- Comment #15 from Stuart K. Smith --- Yeah using nvidia driver here, thanks for the reply Boudhayan. I've had numerous issues with nvidia drivers higher than 340 with the newer 4.4 kernels. I don't have time to validate this right now, but I'll try reverting back to 340 and see if the issue continues. IMO, the latest nvidia drivers are crappy/buggy -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 366239] Feature Request: Missing features found in KSnapshot
https://bugs.kde.org/show_bug.cgi?id=366239 --- Comment #3 from Chris --- I used freehand selection, so at least one person used it. Bet there was a few more than no one. ;-) Looking forward to the image editor is completion. To bad about the Section of Windows being dropped it was a great feature (in my opinion at least). I used the Section of Window a lot, never had program that it failed to work with. At any rate, Rectangular Region can substitute for Section of Window, but it is not as convenient since you have to make adjustments to get the section you want in the screenshot. No adjustment needed with Section of Window. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366275] New: SDDM freezes after long time of use and locked for a while
https://bugs.kde.org/show_bug.cgi?id=366275 Bug ID: 366275 Summary: SDDM freezes after long time of use and locked for a while Product: plasmashell Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: how2h...@hotmail.es CC: plasma-b...@kde.org After more than 8 hours of usage, if the desktop gets locked for inactivity and stays for more than half an hour (or less, not sure), sddm freezes and I can't enter the password, I can see the cursor in the input field but it's frozen (not blinking). No matter what I do, I can't unlock it. I can, however, move the mouse cursor (try to click on the input from each display), and switch to another tty. I've never been 8 (or more) hours continuously, so there are moments where the desktop gets locked (for more than half an hour) and I can unlock it entering the password. Reproducible: Always Steps to Reproduce: 1. Just do whatever you do (work, play, watch videos, etc), but the computer must be running for more than 8 hours (no matter if it gets locked once in a while). 2. After said time passed, wait for half an hour without using it. 3. Move the mouse so the screen(s) turn on and try to enter your password. Actual Results: You cannot enter your password, the inputs are frozen and there are no reboot/shutdown buttons, so you have to reboot switching to another tty. Expected Results: You should be able to enter your password and continue what you were doing. I'm on Manjaro (Arch Linux) 16.01.1. OpenRC instead of Systemd. Linux 4.7. System specs: - Intel Core I5-4670k - 8 GB of RAM (2x4) - AMD R9 290 (video-ati) - 3 monitor setup -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 366276] New: escape key should close full screen view
https://bugs.kde.org/show_bug.cgi?id=366276 Bug ID: 366276 Summary: escape key should close full screen view Product: okular Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: hb_...@brueningserver.de It would be a very good idea if the full screen mode could be closed with the escape key. This is already mentioned in 269677. But I think this part of 269677 was overlooked by the developers. I create this second bug because I imagine the escape key behaviour can be implemented very easily and it is independent from 269677. Reproducible: Always Expected Results: Escape key closes full screen mode. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 366277] New: klipper systray applet autostarts on non-plasma DE's
https://bugs.kde.org/show_bug.cgi?id=366277 Bug ID: 366277 Summary: klipper systray applet autostarts on non-plasma DE's Product: klipper Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: rdie...@math.unl.edu Since, https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=fc439f63e122cd6d668fb75cf71a5b361da0b10d which changed OnlyShowIn=KDE to NotShowIn=KDE the installed file: /etc/xdg/autostart/org.kde.klipper.desktop now starts klipper everywhere and since only Plasma supports X-KDE-autostart-condition=klipperrc:General:AutoStart:false non-plasma DE's have no way to disable it either. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366278] Application menu items hidden behind auto-hide taskbar
https://bugs.kde.org/show_bug.cgi?id=366278 Martin Vuille changed: What|Removed |Added CC||mvui11e-...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366278] New: Application menu items hidden behind auto-hide taskbar
https://bugs.kde.org/show_bug.cgi?id=366278 Bug ID: 366278 Summary: Application menu items hidden behind auto-hide taskbar Product: plasmashell Version: 5.7.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: mvui11e-...@yahoo.ca CC: plasma-b...@kde.org I have panel with taskbar, launcher, etc. configured as auto-hide I am using the "Application Menu" launcher (cascading menus) When a submenu is displayed, it can sometimes extend behind the taskbar, making some items in that submenu inaccessible Reproducible: Always Steps to Reproduce: 1. Configure per above description 2. Open menu, select menu item near the bottom that has many subitems Actual Results: Bottom subitems are hidden behind taskbar Expected Results: Submenu is drawn above or in front of the taskbar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366265] Auto-hide panel stays open when desktop initialized
https://bugs.kde.org/show_bug.cgi?id=366265 Martin Vuille changed: What|Removed |Added CC||mvui11e-...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366278] Application menu items hidden behind auto-hide taskbar
https://bugs.kde.org/show_bug.cgi?id=366278 --- Comment #1 from Martin Vuille --- Created attachment 100390 --> https://bugs.kde.org/attachment.cgi?id=100390&action=edit Screen capture showing problem -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 366277] klipper systray applet autostarts on non-plasma DE's
https://bugs.kde.org/show_bug.cgi?id=366277 Hans de Goede changed: What|Removed |Added CC||jwrdego...@fedoraproject.or ||g -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366278] Application menu items hidden behind auto-hide taskbar
https://bugs.kde.org/show_bug.cgi?id=366278 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366242] mxf files are randomly incorrectly seeking
https://bugs.kde.org/show_bug.cgi?id=366242 --- Comment #2 from asla...@vsechno-atd.cz --- Not sure about that, but probably not, because I have updated the whole OS. Current ffmpeg version is 2.8.6-1ubuntu2. When playing the video in Totem video player or VLC, it works correctly. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366242] mxf files are randomly incorrectly seeking
https://bugs.kde.org/show_bug.cgi?id=366242 --- Comment #3 from Wegwerf --- Does it play and seek correctly in melt? -- 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 Martin Klapetek changed: What|Removed |Added CC|mklape...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366242] mxf files are randomly incorrectly seeking
https://bugs.kde.org/show_bug.cgi?id=366242 --- Comment #4 from asla...@vsechno-atd.cz --- No, playing in melt behaves the same way as in Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366242] mxf files are randomly incorrectly seeking
https://bugs.kde.org/show_bug.cgi?id=366242 Wegwerf changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #5 from Wegwerf --- Then this is an upstream issue and you need to contact the MLT project, http://mltframework.org/. The reason is that MLT is the engine inside Kdenlive; so if melt already chokes, then Kdenlive cannot do anything about this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366246] Plasmashell restarts randomly, taskbar disappears and reappears after +/- 10 seconds
https://bugs.kde.org/show_bug.cgi?id=366246 Eike Hein changed: What|Removed |Added Resolution|BACKTRACE |WAITINGFORINFO --- Comment #6 from Eike Hein --- Do you use the Window List plasmoid somewhere? -- You are receiving this mail because: You are watching all bug changes.
