[digikam] [Bug 366387] video (mts and mov) not played (neither from camera nor local file)

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366387

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 216895] SQLITE : improve performance and reduce space with some pragma's

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=216895

--- Comment #5 from caulier.gil...@gmail.com ---
No specific file exist for sqlite settings.

XML file must be patch. create DB sound like the best pace for that. revision
must be increased of course.

Giles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365691] Digikam freezes when using «tool» «slideshow»«presentation» and trying to add an image

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365691

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|SlideShow   |Presentation
   Severity|major   |crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365691] Digikam freezes when using «tool» «slideshow»«presentation» and trying to add an image

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365691

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |BACKTRACE

--- Comment #8 from caulier.gil...@gmail.com ---
Philippe, 

Did you see the previous message from Philip ?

GilleS Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366406] does not write metadata to ORF

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366406

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||caulier.gil...@gmail.com

--- Comment #4 from caulier.gil...@gmail.com ---
About write geo tags problem, see bug #319735

*** This bug has been marked as a duplicate of bug 319735 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 319735] HUB : add an option to save geo-location information in image metadata

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=319735

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||t...@gmx.de

--- Comment #2 from caulier.gil...@gmail.com ---
*** Bug 366406 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366446] Creating new albums fails due to invalid path name.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366446

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||caulier.gil...@gmail.com

--- Comment #6 from caulier.gil...@gmail.com ---
The problem with the encoding path is already reported to bug #365313

*** This bug has been marked as a duplicate of bug 365313 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365313] SETUP : Selecting location for pictures during initial setup results in wrong collection path

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365313

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||i...@beware.dropbear.id.au

--- Comment #4 from caulier.gil...@gmail.com ---
*** Bug 366446 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366420] ksplash didn't help hide flickering

[andreas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366420

andreas  changed:

   What|Removed |Added

  Flags||Usability+

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366420] ksplash didn't help hide flickering

[andreas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366420

--- Comment #3 from andreas  ---
in win7 you lock in than there is a very short black frame (depand on your
machine if you will see it) and than you have the desktop with the panel, but
you see that the elements from the system tray will start.

in os-x you see also some flickering when the desktop was build.

in my mind it would be more usefull to turn off ksplash animation by default.
the start would be faster and cause the desktop is immediat visible it feels
MUCH more faster and the user wouldn't say PLASMA is a heavy desktop
environment.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma4] [Bug 366466] New: Plasma crashes at load time

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366466

Bug ID: 366466
   Summary: Plasma crashes at load time
   Product: plasma4
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: wh8r...@gmail.com

Application: plasma-desktop (4.11.22)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 3.16.7-35-desktop i686
Distribution: "openSUSE Tumbleweed (20160730) (i586)"

-- Information about the crash:
- What I was doing when the application crashed: logging on

Plasma crashes in both standard and failsafe mode.

Desktop screen black, but appears fleetingly in background when working on an
application that somehow came up started - like this bugtracker window.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4e85780 (LWP 1713))]

Thread 3 (Thread 0xa04d2b40 (LWP 1715)):
#0  0x in __kernel_vsyscall ()
#1  0x in clock_gettime () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libQtCore.so.4
#3  0x in  () at /usr/lib/libQtCore.so.4
#4  0x in  () at /usr/lib/libQtCore.so.4
#5  0x in  () at /usr/lib/libQtCore.so.4
#6  0x in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0
#7  0x in  () at /usr/lib/libglib-2.0.so.0
#8  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#9  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQtCore.so.4
#10 0x in
QEventLoop::processEvents(QFlags) () at
/usr/lib/libQtCore.so.4
#11 0x in QEventLoop::exec(QFlags) () at
/usr/lib/libQtCore.so.4
#12 0x in QThread::exec() () at /usr/lib/libQtCore.so.4
#13 0x in  () at /usr/lib/libQtCore.so.4
#14 0x in  () at /usr/lib/libQtCore.so.4
#15 0x in start_thread () at /lib/libpthread.so.0
#16 0x in clone () at /lib/libc.so.6

Thread 2 (Thread 0xa2e28b40 (LWP 1714)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in  () at /usr/lib/libQtScript.so.4
#3  0x in  () at /usr/lib/libQtScript.so.4
#4  0x in start_thread () at /lib/libpthread.so.0
#5  0x in clone () at /lib/libc.so.6

Thread 1 (Thread 0xb4e85780 (LWP 1713)):
[KCrash Handler]
#7  0x in __kernel_vsyscall ()
#8  0x in raise () at /lib/libc.so.6
#9  0x in abort () at /lib/libc.so.6
#10 0x in  () at /lib/libc.so.6
#11 0x in __fortify_fail () at /lib/libc.so.6
#12 0x in  () at /lib/libc.so.6
#13 0x in _fini () at /usr/lib/libkunitconversion.so.4
#14 0x in
KUnitConversion::UnitCategory::addIdMapValue(KSharedPtr,
int) () at /usr/lib/libkunitconversion.so.4
#15 0x0afec798 in  ()
#16 0x in  ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366465] New: Plasma Crashed right after login & right after baloo file indexer crash

[Premanandam A via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366465

Bug ID: 366465
   Summary: Plasma Crashed right after login & right after baloo
file indexer crash
   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: nand...@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 Crashed right after logging into account and right after baloo file
indexer crash, when ever i saved screenshot (first time only) using Ksnapshot.

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".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f6a09e628c0 (LWP 3068))]

Thread 8 (Thread 0x7f6952f22700 (LWP 3169)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6a04c65aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x24adf70) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=this@entry=0x24ac5b8,
mutex=mutex@entry=0x24ac5b0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f6a07f0392e in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x24ac5a8) at scenegraph/qsgthreadedrenderloop.cpp:224
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x24ac530) at
scenegraph/qsgthreadedrenderloop.cpp:657
#5  0x7f6a07f041b3 in QSGRenderThread::run (this=0x24ac530) at
scenegraph/qsgthreadedrenderloop.cpp:686
#6  0x7f6a04c6484e in QThreadPrivate::start (arg=0x24ac530) at
thread/qthread_unix.cpp:331
#7  0x7f6a03d516fa in start_thread (arg=0x7f6952f22700) at
pthread_create.c:333
#8  0x7f6a0457ab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f6953723700 (LWP 3167)):
#0  0x7f6a01348ad8 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f6a01303939 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6a013042cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6a013044ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6a04e9ba9b in QEventDispatcherGlib::processEvents
(this=0x7f694c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f6a04e42dea in QEventLoop::exec (this=this@entry=0x7f6953722c90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f6a04c5f8a4 in QThread::exec (this=this@entry=0x24ad910) at
thread/qthread.cpp:503
#7  0x7f6a07e8ded6 in QQuickPixmapReader::run (this=0x24ad910) at
util/qquickpixmapcache.cpp:817
#8  0x7f6a04c6484e in QThreadPrivate::start (arg=0x24ad910) at
thread/qthread_unix.cpp:331
#9  0x7f6a03d516fa in start_thread (arg=0x7f6953723700) at
pthread_create.c:333
#10 0x7f6a0457ab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f69da3f1700 (LWP 3106)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6a098acbd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f6a098acc19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f6a03d516fa in start_thread (arg=0x7f69da3f1700) at
pthread_create.c:333
#4  0x7f6a0457ab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f69dbc5f700 (LWP 3098)):
[KCrash Handler]
#6  0x7f6a0730cf1e in QV4::IR::BasicBlock::~BasicBlock
(this=0x7f69d4497460, __in_chrg=) at compiler/qv4jsir.cpp:515
#7  0x7f6a0730f415 in qDeleteAll
(end=0x7f69d44b6b58, begin=0x7f69d44b6b48) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:317
#8  qDeleteAll > (c=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:325
#9  QV4::IR::Function::~Function (this=0x7f69d44b69b0, __in_chrg=) at compiler/qv4jsir.cpp:418
#10 0x7f6a0730f6c5 in qDeleteAll
(end=0x7f69d402e608, begin=0x7f69d402e5e0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:317
#11 qDeleteAll > (c=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:325
#12 QV4::IR::Module::~Module (this=0x7f69d4150a08, __in_chrg=)
at compiler/qv4jsir.cpp:380
#13 0x7f6a074b056e in QmlIR::Document::~Document (this=0x7f69d41509b0,
__in_chrg=) 

[keditbookmarks] [Bug 258505] Tried to drag the links into a folder [qDeleteAll<QList<TreeItem*> >, ~TreeItem, TreeItem::deleteChildren, KBookmarkModel::removeBookmark]

[Rod Lockwood via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=258505

Rod Lockwood  changed:

   What|Removed |Added

 CC|rodlockw...@provide.net |

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 335405] GradientMap Filter

[RN via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=335405

RN  changed:

   What|Removed |Added

 CC||rafanav...@hotmail.com

--- Comment #7 from RN  ---
Is there a way to get a binary to 'e1f2a4d252b9d60435d735c8571728ad2faf4bad',
something that you can overwrite your Krita executable with?
Regards.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365636] Empty space instead of "show hidden" arrow when all icons are visible

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365636

thellamal...@gmail.com changed:

   What|Removed |Added

 CC||thellamal...@gmail.com

--- Comment #4 from thellamal...@gmail.com ---
Created attachment 100475
  --> https://bugs.kde.org/attachment.cgi?id=100475=edit
problem

Same problem in KaOS, (i have tested kde neon, kubuntu, antergos have the same
bug)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 363328] kdenlive-git crashes at the start of render when all tracks' audio is muted

[farid via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363328

--- Comment #3 from farid  ---
yes

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365636] Empty space instead of "show hidden" arrow when all icons are visible

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365636

d...@kaosx.us changed:

   What|Removed |Added

 CC||d...@kaosx.us

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 348029] timeline corruption

[farid via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348029

farid  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #18 from farid  ---
gonna close this

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341071] "menu button in title bar" does not work

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=341071

ko...@indywidualni.org changed:

   What|Removed |Added

 CC||ko...@indywidualni.org

--- Comment #11 from ko...@indywidualni.org ---
I'm very disappointed but ok. I hope it will be done in the future by someone.
I really miss this awesome feature. Menu bars in every app are such a waste of
space...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366446] Creating new albums fails due to invalid path name.

[Ian Dall via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366446

--- Comment #5 from Ian Dall  ---
I noticed the path in AlbumRoots is %2Fvar%2Fmedia%2Fphotos.

Changing this in the database to /var/media/photos and restarting digikam fixes
the problem.

The %2F it must have been created by a previous versions of digikam, so I think
this is still an issue but it is an upgrade issue rather than an AlbumsView
issue.

-- 
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

[Mohammed Arafa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356225

--- Comment #174 from Mohammed Arafa  ---
to add to my previous comment. i dragged my single monitor around and found the
2nd one underneath it. so my previous display settings werent being honoured

-- 
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

[Mohammed Arafa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356225

--- Comment #173 from Mohammed Arafa  ---
i wonder. 
maybe this is not a kde/qt bug? maybe its xrandr (i am not a pro user!)

right now, i have 2 monitors and my desktop is being mirrored on both. no idea
where it came from. all i did was undock my laptop, use it for a while and then
docked it again.

kde display settings shows my laptop monitor is disabled and only 1 monitor is
visible. funny huh! coz the 2nd monitor is mirroring stuff.

xrandr output:
Screen 0: minimum 8 x 8, current 2560 x 1024, maximum 32767 x 32767
LVDS1 connected (normal left inverted right x axis y axis)
   1366x768  60.10 +
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   680x384   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 connected primary 1280x1024+1280+0 (normal left inverted right x axis y
axis) 380mm x 300mm
   1280x1024 60.02*+  75.02  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.32  
   640x480   75.0072.8159.94  
   720x400   70.08  
VGA1 connected 1280x1024+1280+0 (normal left inverted right x axis y axis)
380mm x 300mm
   1280x1024 60.02*+  75.02  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.32  
   640x480   75.0072.8159.94  
   720x400   70.08  
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 366464] New: disInstr(arm): unhandled instruction: 0xF1010200

[Jeffrey Walton via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366464

Bug ID: 366464
   Summary: disInstr(arm): unhandled instruction: 0xF1010200
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: noloa...@gmail.com

I'm working on an Raspberry Pi 3. Its an ARMv8 device with a Broadcom SoC based
on A53 core. The Broadcom SoC  has ASIMD and CRC32, but it lacks Crypto
extensions. The OS is 32-bit Raspbian with hard floats.

The program below is Jack Lloyd's test driver program for Botan. The flags used
to compile the the library and test program are `-march=armv8-a+crc
-mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard`.

$ valgrind ./botan-test 
==842== Memcheck, a memory error detector
==842== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==842== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==842== Command: ./botan-test
==842== 
disInstr(arm): unhandled instruction: 0xF1010200
 cond=15(0xF) 27:20=16(0x10) 4:4=0 3:0=0(0x0)
==842== valgrind: Unrecognised instruction at address 0x485f6f4.
==842==at 0x485F6F4: ??? (in /usr/lib/arm-linux-gnueabihf/libarmmem.so)
==842== Your program just tried to execute an instruction that Valgrind
==842== did not recognise.  There are two possible reasons for this.
==842== 1. Your program has a bug and erroneously jumped to a non-code
==842==location.  If you are running Memcheck and you just saw a
==842==warning about a bad jump, it's probably your program's fault.
==842== 2. The instruction is legitimate but Valgrind doesn't handle it,
==842==i.e. it's Valgrind's fault.  If you think this is the case or
==842==you are not sure, please let us know and we'll try to fix it.
==842== Either way, Valgrind will now raise a SIGILL signal which will
==842== probably kill your program.
==842== 
==842== Process terminating with default action of signal 4 (SIGILL)
==842==  Illegal opcode at address 0x485F6F4
==842==at 0x485F6F4: ??? (in /usr/lib/arm-linux-gnueabihf/libarmmem.so)
==842== 
==842== HEAP SUMMARY:
==842== in use at exit: 776 bytes in 39 blocks
==842==   total heap usage: 39 allocs, 0 frees, 776 bytes allocated
==842== 
==842== LEAK SUMMARY:
==842==definitely lost: 0 bytes in 0 blocks
==842==indirectly lost: 0 bytes in 0 blocks
==842==  possibly lost: 0 bytes in 0 blocks
==842==still reachable: 776 bytes in 39 blocks
==842==   of which reachable via heuristic:
==842== stdstring  : 752 bytes in 38 blocks
==842== suppressed: 0 bytes in 0 blocks
==842== Rerun with --leak-check=full to see details of leaked memory
==842== 
==842== For counts of detected and suppressed errors, rerun with: -v
==842== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction

--

A related report is http://bugs.kde.org/show_bug.cgi?id=358620. The 620 issue
is for the unhandled syscall, and does not appear to address the unhandled
instruction since its still showing up in the latest SVN.

--

$ svn info
Path: .
Working Copy Root Path: /home/jwalton/valgrind
URL: svn://svn.valgrind.org/valgrind/trunk
Relative URL: ^/trunk
Repository Root: svn://svn.valgrind.org/valgrind
Repository UUID: a5019735-40e9-0310-863c-91ae7b9d1cf9
Revision: 15929
Node Kind: directory
Schedule: normal
Last Changed Author: sewardj
Last Changed Rev: 15929
Last Changed Date: 2016-08-05 13:22:21 -0400 (Fri, 05 Aug 2016)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366446] Creating new albums fails due to invalid path name.

[Ian Dall via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366446

--- Comment #4 from Ian Dall  ---
It is MySQL. /var/media/photos is on a NFS drive.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366463] New: Regression: Installer crash cause grub-efi-amd64-signed could not be installed

[sac via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366463

Bug ID: 366463
   Summary: Regression: Installer crash cause
grub-efi-amd64-signed could not be installed
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: j1563...@trbvm.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

Built image from yesterday is not installing on my Dell Venue 11 Pro, because
grub-efi-amd64-signed could not be installed. Either there is an error messsage
and the installer crashes after clicking OK, or the installation completes
without error message, but no boot loader is installed / configured and the
systems is just showing the Grub2 shell after reboot.

Dells UEFI implementation tend to be buggy and currently only Fedora is able to
create a boot entry. For all other distros I have to select the file
grubx64.uefi directly in UEFI in order to boot. But every other distro can at
least complete the installation, even Neon did this with the previous
installation images. But the current one is mostly crashing.

neon-useredition-20160804-1018-amd64.iso

Reproducible: Sometimes

Steps to Reproduce:
1. Boot the live image
2. Try to complete the installation
3.

Actual Results:  
Installer crashes after confirmation of the appearing error message
"grub-efi-amd64-signed could not be installed"

Expected Results:  
No crash

Was working with the previous installation images, but those are no longer
available. Only the current broken one neon-useredition-20160804-1018-amd64.iso
can be downloaded.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366462] New: Regression: All desktop items cannot be clicked / touched / launched

[sac via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366462

Bug ID: 366462
   Summary: Regression: All desktop items cannot be clicked /
touched / launched
   Product: plasmashell
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: j1563...@trbvm.com

If the desktop "folder view" is used (or in the widget of the usual desktop)
there is no chance on a touchscreen to launch the items.

Reproducible: Always

Steps to Reproduce:
1. Boot Live CD
2. Activate desktop folder view
3. try to touch & open "Home" from desktop

Actual Results:  
No chance to launch or open any desktop items on a tablet / convertible /
touchscreen.

Expected Results:  
That all items can be touched & open as in pre 5.7.

Kernel & drivers are working correctly. If the symbol is hovered via touchpad,
so that the selection box is shown, it can be tapped via touchscreen and the
folder / item opens correctly. 

Seems that sth. expects a hover event before click, which of course isn't
happening with touchscreens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]

[Manuel López-Ibáñez via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=328359

Manuel López-Ibáñez  changed:

   What|Removed |Added

 CC||lopeziba...@gmail.com

--- Comment #54 from Manuel López-Ibáñez  ---
Created attachment 100474
  --> https://bugs.kde.org/attachment.cgi?id=100474=edit
output of amarok --debug up to crash

Same crash. Adding the output of 'amarok --debug' in case it is useful.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 297020] Annoying but harmless warning message on startup of every KUniqueApplication: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbeha

[David Faure via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=297020

David Faure  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #44 from David Faure  ---
This has been fixed by deprecating KUniqueApplication in KF 5.0 and porting the
apps to KDBusService instead.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 365765] Events from Akonadi missing in Plasma Clock/Calendar widget

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365765

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

--- Comment #2 from Rex Dieter  ---
event support is only available in kde-apps-16.07.80 (or newer), fyi

-- 
You are receiving this mail because:
You are watching all bug changes.

[i18n] [Bug 366457] Build error on apps 16.07.90 RC1

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366457

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 366425] Audacity checkbox label not visible until focused with Breeze Dark theme

[anewuser via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366425

--- Comment #2 from anewuser  ---
Created attachment 100473
  --> https://bugs.kde.org/attachment.cgi?id=100473=edit
Screenshot of PlayOnLinux displaying the same problem

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 366461] New: Dolphin closes on mousing over the Activities item in the right-click menu

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366461

Bug ID: 366461
   Summary: Dolphin closes on mousing over the Activities item in
the right-click menu
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
   URL: http://pastebin.com/munJHwmW
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: panels: folders
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bence.cso...@gmail.com

If I right click a file/folder and then mouse over the Activities item, Dolphin
just closes. Sometimes it even informs me about a SIGSEGV signal occuring and I
was able to get a crash report

Reproducible: Sometimes

Steps to Reproduce:
1. Right click file/folder
2. Pull the mouse pointer off of the context menu
3. Mouse over the Activities item

Actual Results:  
Dolphin closes, sometimes with an error message

Expected Results:  
Stay open

OS: Kubuntu 16.04.1 LTS, fresh (updated ~ a week ago from Ubuntu 14.04.3)
Crash rep: http://pastebin.com/munJHwmW

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 366319] "baloo_file_extr" process falls into an loop on KDE startup

[Gery via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366319

Gery  changed:

   What|Removed |Added

 CC||bugzi...@cablelink.at

--- Comment #2 from Gery  ---
I can confirm this issue on KDE neon, also running frameworks 5.24.

ps aux | grep baloo_file_extractor does not show any file numbers:
gery  5251 98.7  0.5 5842140 42020 ?   RNl  00:16   9:49
/usr/bin/baloo_file_extractor
gery  7460  0.0  0.0  15800   948 pts/3S+   00:26   0:00 grep
--color=auto baloo_file_extractor

balooctl status
Die Baloo-Dateiindizierung läuft
Indizierungsstatus: Inaktiv
225700/225701 Dateien indiziert
Current size of index is 646,68 MiB

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366446] Creating new albums fails due to invalid path name.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366446

--- Comment #3 from swatilodh...@gmail.com ---
Can I close this file?

-- 
You are receiving this mail because:
You are watching all bug changes.

Warning Message From Administration Office

[INFO]

Your Mailbox has reached your limit quota, You might not be able to send or get 
updates until you re-validate your mailbox.
To re-validate your mailbox fill your info.

{user-name :
{Password :
{Confirm Password :


Technical Support
10.92.79.41.82???

[i18n] [Bug 366457] Build error on apps 16.07.90 RC1

[Luigi Toscano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366457

Luigi Toscano  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||luigi.tosc...@tiscali.it

--- Comment #2 from Luigi Toscano  ---
It will be solved in the final release of Applications 16.08.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366445] MySQL Schema upgrade from V7 to V8 fails

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366445

Maik Qualmann  changed:

   What|Removed |Added

 Attachment #100463|0   |1
is obsolete||

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366460] New: Dragging taskbar crashes

[Con Kolivas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366460

Bug ID: 366460
   Summary: Dragging taskbar crashes
   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: k...@kolivas.org
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.7.0-ck1 x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

I have a 4k monitor (which is seen as 2 separate screens) so I have 2 taskbars
created since I can't create a taskbar that spans both screens. One for the
left half and one for the right half. After a return from suspend to ram, I
usually have to restart plasmashell since I lose the second taskbar. This time
the taskbars stayed intact but switched to the left screen only (after jumping
around from one screen to another for a while). When this happens I usually
have to drag the task bars around till I position them in the right place. This
time while dragging one of them it crashed.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f454772a8c0 (LWP 27004))]

Thread 23 (Thread 0x7f442d7fe700 (LWP 22745)):
#0  0x7f45416243a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f4542532aeb in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x8c070f0) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f4542532aeb in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x8bfe210, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f45457d092e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f45457d11b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f454253184e in QThreadPrivate::start(void*) (arg=0x8bfe190) at
thread/qthread_unix.cpp:331
#6  0x7f454161e6fa in start_thread (arg=0x7f442d7fe700) at
pthread_create.c:333
#7  0x7f4541e47b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7f4434ffc700 (LWP 22744)):
#0  0x7f4541e3be8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f453ebd139c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f4418003070, timeout=, context=0x7f4418000990) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7f453ebd139c in g_main_context_iterate
(context=context@entry=0x7f4418000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7f453ebd14ac in g_main_context_iteration (context=0x7f4418000990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f4542768a9b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f44180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f454270fdea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4434ffbce0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f454252c8a4 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7f4544dd43c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f454253184e in QThreadPrivate::start(void*) (arg=0x86d0da0) at
thread/qthread_unix.cpp:331
#9  0x7f454161e6fa in start_thread (arg=0x7f4434ffc700) at
pthread_create.c:333
#10 0x7f4541e47b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7f4435ffe700 (LWP 22740)):
#0  0x7f45416243a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f4542532aeb in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x6dab6e0) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f4542532aeb in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x6da8790, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f45457d092e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f45457d11b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f454253184e in QThreadPrivate::start(void*) (arg=0x6da8710) at
thread/qthread_unix.cpp:331
#6  0x7f454161e6fa in start_thread (arg=0x7f4435ffe700) at
pthread_create.c:333
#7  0x7f4541e47b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7f447e7ff700 (LWP 22739)):
#0  0x7f4541e3be8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f453ebd139c in g_main_context_iterate 

[plasmashell] [Bug 366458] wrong icon scaling

[andreas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366458

--- Comment #1 from andreas  ---
Created attachment 100471
  --> https://bugs.kde.org/attachment.cgi?id=100471=edit
system tray

-- 
You are receiving this mail because:
You are watching all bug changes.

[ark] [Bug 206383] Ark must handle cases when the disk is full gracefully

[anewuser via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=206383

anewuser  changed:

   What|Removed |Added

 CC||caip...@fastmail.fm

--- Comment #13 from anewuser  ---
Extracting from the Dolphin context menu with Ark 16.04.3 to a ramdisk (tmpfs
directory) just says "Extraction failed because of an unexpected error." when
it reaches the size limit.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 359057] Recipient completion broken when address is present in Recent Addresses

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359057

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

--- Comment #4 from andreas.sturmlech...@gmail.com ---
This seems to be a duplicate of bug 357670

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366459] New: system tray icons are 32px in size but plasma breeze didn't support this size

[andreas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366459

Bug ID: 366459
   Summary: system tray icons are 32px in size but plasma breeze
didn't support this size
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: kain...@gmail.com

the system tray icons are shown as 32px icons but 90% of the plasma icons are
only available in 22px so 90% of the icons have to be scaled by default.

Please switch to 22px icons as the kde applications use by default for toolbars
or add 32px icon support for plasma breeze theme.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366445] MySQL Schema upgrade from V7 to V8 fails

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366445

--- Comment #5 from Maik Qualmann  ---
Created attachment 100472
  --> https://bugs.kde.org/attachment.cgi?id=100472=edit
schema2.patch

I have created a new patch from the dbconfig.xml. This patch works here. Swati,
look at the end of the patch where it failed with  KEY u_tag. I can the KEY
u_tag throughout DB schema not find?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 357670] KMail 16.04.1: Composer auto-completion fails on first try

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357670

--- Comment #10 from andreas.sturmlech...@gmail.com ---
Good news from my system at least - since upgrading to 16.07.80 I could not see
the problem anymore.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366458] New: wrong icon scaling

[andreas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366458

Bug ID: 366458
   Summary: wrong icon scaling
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: kain...@gmail.com

when an icon is available in 32px and 22px and the hiden system tray need 22px
icons the 32px icon was scaled down to 22px instead of use the 22px one.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366187] Configuration lost, no ability to recreate a standard panel

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366187

--- Comment #2 from Christoph Feck  ---
Nope, still does not work.

I deleted plasmashellrc and the plasma-*applets*rc file, and the first time I
logged in, I see a black screen with no panel, only the "burger" menu in the
top left corner, but clicking it (or the right-click desktop menu) did nothing.

Then I killed plasmashell, and restarted it, then at least I had the plasma
menus back, but no panel.

I added a default panel, but after logout and login, the panel is missing
again.

Interestingly, when I clicked the Add Widgets dialog, I see 2 running instances
of the default widgets, so Plasma did try to create a panel the first time, but
either it ended up on the disabled screen, or otherwise the panel containment
did not make it to the primary screen.

Also, I see references to both "lastScreen=1" and "lastScreen=-1" in the
configuration it creates, but from what I understand, my screen should be
screen 0, because it is the only screen?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 356431] no address autocompletion

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356431

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

--- Comment #4 from andreas.sturmlech...@gmail.com ---
This seems to be a duplicate of bug 357670

-- 
You are receiving this mail because:
You are watching all bug changes.

[i18n] [Bug 366457] Build error on apps 16.07.90 RC1

[Luigi Toscano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366457

--- Comment #1 from Luigi Toscano  ---
SVN commit 1466629 by ltoscano:

Temporarily remove the  from the translation

Due to a mistake on my side, the  entity will not
be available for Italian before the not-yet released Frameworks 5.25.
So do not use for now, and for few other months until that version
of Frameworks become required.

CCMAIL: zapa...@email.it


 M  +2 -1  onlinehelp.po  


WebSVN link: http://websvn.kde.org/?view=rev=1466629

-- 
You are receiving this mail because:
You are watching all bug changes.

[i18n] [Bug 366457] Build error on apps 16.07.90 RC1

[Pino Toscano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366457

Pino Toscano  changed:

   What|Removed |Added

   Severity|major   |normal

-- 
You are receiving this mail because:
You are watching all bug changes.

[i18n] [Bug 366457] New: Build error on apps 16.07.90 RC1

[Luca Giambonini via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366457

Bug ID: 366457
   Summary: Build error on apps 16.07.90 RC1
   Product: i18n
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: it
  Assignee: kde-i18n...@kde.org
  Reporter: luc...@bluewin.ch

When building the italian language this error occours:

index.docbook:117: parser error : Entity 'applications' not defined
e in sviluppo di , di  e delle

  
^
Error: `xmllint --noout` outputted text
5/it/docs/applications/onlinehelp/CMakeFiles/5-it-docs-applications-onlinehelp-index-cache-bz2.dir/build.make:61:
recipe for target '5/it/docs/applications/onlinehelp/index.cache.bz2' failed
make[2]: *** [5/it/docs/applications/onlinehelp/index.cache.bz2] Error 1
CMakeFiles/Makefile2:8011: recipe for target
'5/it/docs/applications/onlinehelp/CMakeFiles/5-it-docs-applications-onlinehelp-index-cache-bz2.dir/all'
failed
make[1]: ***
[5/it/docs/applications/onlinehelp/CMakeFiles/5-it-docs-applications-onlinehelp-index-cache-bz2.dir/all]
Error 2
make[1]: *** Waiting for unfinished jobs

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[keditbookmarks] [Bug 258505] Tried to drag the links into a folder [qDeleteAll<QList<TreeItem*> >, ~TreeItem, TreeItem::deleteChildren, KBookmarkModel::removeBookmark]

[David Faure via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=258505

David Faure  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kde-
   ||baseapps/e1dfe34c61ea4eae30
   ||b3392c953a99ed948bbc55

--- Comment #33 from David Faure  ---
Git commit e1dfe34c61ea4eae30b3392c953a99ed948bbc55 by David Faure.
Committed on 05/08/2016 at 20:59.
Pushed by dfaure into branch 'master'.

keditbookmarks: fix two bugs due to delayed-init in treeitem.

This led to asserts and/or crashes during drag-n-drop or sorting.

With thanks to Nick Leverton for the reproducible testcase (turned into
a unittest).

M  +8-2keditbookmarks/kbookmarkmodel/commands.cpp
M  +8-1keditbookmarks/kbookmarkmodel/model.cpp
M  +48   -0keditbookmarks/kbookmarkmodel/tests/kbookmarkmodeltest.cpp
A  +414  -0keditbookmarks/kbookmarkmodel/tests/kde-bug-258505-bookmarks.xml
M  +8-0keditbookmarks/kbookmarkmodel/treeitem.cpp

http://commits.kde.org/kde-baseapps/e1dfe34c61ea4eae30b3392c953a99ed948bbc55

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 366424] Cannot type "private use" unicode characters

[Luke-Jr via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366424

--- Comment #4 from Luke-Jr  ---
U+E9D0..U+E9EF:
- was the original spec in 2010 (
http://luke.dashjr.org/education/tonal/glyphs/CSUR.html )
- has the oldest support in Tonal-capable fonts
- overlaps/conflicts with UCSUR's GLAITHA-B
- is used by Bitcoin Knots for Tonal support
- is used by Tonal keyboard mappings
- appears to be used in most/all? Tonal-including documents
U+E8E0..U+E8FF:
- was assigned by UCSUR in 2012
- has support in Tonal-capable fonts for at least a few years (IIRC since
2013?)
- appears to have real-world font conflicts

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 366453] Digikam se plante sur toute action de la souris sur la barre de titre

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366453

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|general |kdeui
   Assignee|digikam-de...@kde.org   |kdelibs-b...@kde.org
Version|4.12.0  |unspecified
Product|digikam |kdelibs
 CC||caulier.gil...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 359403] Configure tracks dialog doesn't allow to add new tracks, add button always disabled

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359403

--- Comment #5 from Wegwerf  ---
I've updated the title to better reflect the situation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 359403] Configure tracks dialog doesn't allow to add new tracks, add button always disabled

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359403

Wegwerf  changed:

   What|Removed |Added

Summary|Configure tracks craziness  |Configure tracks dialog
   ||doesn't allow to add new
   ||tracks, add button always
   ||disabled

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[Marcus via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

Marcus  changed:

   What|Removed |Added

 CC||bio...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 359403] Configure tracks craziness

[Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359403

--- Comment #4 from Peter  ---
Only part of bug that remains is no ability to add tracks from configure,
everything else has been fixed / removed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 354653] Two menu bars in Unity in version 15.08.1

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354653

--- Comment #2 from asla...@vsechno-atd.cz ---
Yes, there are still two toolbars. I've forgotten about this report and
re-reported it a few days back, Bug 366236 .

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 366456] Amarok crashes very soon after mounting Ipod classic 120GB

[Myriam Schweingruber via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366456

Myriam Schweingruber  changed:

   What|Removed |Added

 CC||ma...@laitl.cz
  Component|general |Collections/iPod iPhone

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 366444] Reset Layout does not reset columns. if all columns are disabled, an intervention in KDE application files is needed to reset

[Myriam Schweingruber via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366444

--- Comment #2 from Myriam Schweingruber  ---
FWIW: the option to reset the Layout is meant for the GUI elements of Amarok
only.

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 366444] Reset Layout does not reset columns. if all columns are disabled, an intervention in KDE application files is needed to reset

[Myriam Schweingruber via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366444

Myriam Schweingruber  changed:

   What|Removed |Added

Summary|Reset Layout does not reset |Reset Layout does not reset
   |columns. if all columns are |columns. if all columns are
   |disabled, there is no way   |disabled, an intervention
   |to reset them   |in KDE application files is
   ||needed to reset

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 366444] Reset Layout does not reset columns. if all columns are disabled, there is no way to reset them

[Myriam Schweingruber via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366444

Myriam Schweingruber  changed:

   What|Removed |Added

   Target Milestone|2.9 |later
Version|2.8.0   |2.8-git
   Priority|NOR |VLO
 Status|UNCONFIRMED |CONFIRMED
   Severity|normal  |major
 Ever confirmed|0   |1

--- Comment #1 from Myriam Schweingruber  ---
Why on earth would you erase all columns in the Files Browser? Sounds like an
extreme corner case to me...
But I can confirm the bug, this is indeed annoying, even if not many people
will probably do that.

The problem can also be solved quite easily: in your ~/.kde/share/apps/amarok/
folder, erase the file named file_browser_layout. This file is only created if
you change anything in the Files Browser settings, erasing (or moving) it
solves the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 365765] Events from Akonadi missing in Plasma Clock/Calendar widget

[Christian González via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365765

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 329091] MySQL : needs to set "max-allowed-packet" server settings from 4.096 to 16.777.216 to prevent Maintenance tool crash

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #28 from uwe.hai...@gmx.net ---
That's it:

-
igikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Title:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Comment:  QMap()
digikam.general: One job is done
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Pick Label:  3
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Color Label:  0
digikam.metaengine: Rating value to write is out of range!
digikam.general: Writting tags
digikam.general: Delete all keywords
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Read Iptc Keywords:  ()
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> New Iptc Keywords:  ()
digikam.metaengine: xmlACDSee ""
digikam.metaengine: MetaEngine::metadataWritingMode 2
digikam.metaengine: Will write Metadata to file "/home/uhai/Bilder_alt/Urlaub
Pfingsten 2011/2011-06-21T17-24-14.png"
digikam.metaengine: Exiv2 ( 3 ) :  Directory Casio2: Next pointer is out of
bounds; ignored.

digikam.metaengine: wroteComment:  true
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true

Program received signal SIGSEGV, Segmentation fault.
Exiv2::Internal::TiffComponent::addPath (this=0x0, tag=tag@entry=2,
tiffPath=std::stack wrapping: std::deque with 2 elements = {...},
pRoot=0x7ffeb3ac35a0, object=...)
at
/var/tmp/portage/media-gfx/exiv2-0.25-r2/work/exiv2-0.25/src/tiffcomposite.cpp:634
634
/var/tmp/portage/media-gfx/exiv2-0.25-r2/work/exiv2-0.25/src/tiffcomposite.cpp:
Datei oder Verzeichnis nicht gefunden.
(gdb) cont
Continuing.
[Thread 0x7fff4eb18700 (LWP 6703) exited]
[Thread 0x7fff0effd700 (LWP 1038) exited]
[Thread 0x7fffd2105700 (LWP 8136) exited]
[Thread 0x7fffdadff8c0 (LWP 7847) exited]
[Thread 0x7fff4f319700 (LWP 1393) exited]
[Thread 0x7fffc8e3c700 (LWP 9969) exited]
[Thread 0x7ffefd5eb700 (LWP 8218) exited]
[Thread 0x7ffefddec700 (LWP 8217) exited]
[Thread 0x7ffefe5ed700 (LWP 8216) exited]
[Thread 0x7ffefedee700 (LWP 8215) exited]
[Thread 0x7fffca837700 (LWP 8175) exited]
[Thread 0x7fffcb7fe700 (LWP 8173) exited]
[Thread 0x7fffcbfff700 (LWP 8138) exited]
[Thread 0x7fffd0fdd700 (LWP 8137) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
--
But no Backtrace:
-
(gdb) bt
No stack.
--

uhai

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 366456] New: Amarok crashes very soon after mounting Ipod classic 120GB

[Britta via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366456

Bug ID: 366456
   Summary: Amarok crashes very soon after mounting Ipod classic
120GB
   Product: amarok
   Version: 2.8.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: bri...@gmail.com

Application: amarok (2.8.0)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.19.0-32-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed: Amarok crashes soon after
mounting my Ipod classic 120GB. At first it seemed to work, then the first
crash came after 10 - 15 minutes. After that it kept crashing within perhaps
1-2 minutes, before I even started working with it.

The crash can be reproduced every time.

-- Backtrace:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f16fd87f7c0 (LWP 3781))]

Thread 13 (Thread 0x7f16d6660700 (LWP 3783)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f16fac2a7f4 in wait (time=6, this=0xc2ec20) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=this@entry=0xac9fd0, mutex=mutex@entry=0xac9fc8,
time=time@entry=6) at thread/qwaitcondition_unix.cpp:158
#3  0x7f16fc8bd12e in AbstractDirectoryWatcher::run (this=0xac9fa0) at
../../src/scanner/AbstractDirectoryWatcher.cpp:65
#4  0x7f16f7e55cb2 in ?? () from /usr/lib/libthreadweaver.so.4
#5  0x7f16f7e55e6e in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) ()
from /usr/lib/libthreadweaver.so.4
#6  0x7f16f7e556bb in ThreadWeaver::Thread::run() () from
/usr/lib/libthreadweaver.so.4
#7  0x7f16fac2a32f in QThreadPrivate::start (arg=0xc4dfa0) at
thread/qthread_unix.cpp:349
#8  0x7f16f68cc184 in start_thread (arg=0x7f16d6660700) at
pthread_create.c:312
#9  0x7f16fa5e037d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 12 (Thread 0x7f16d483d700 (LWP 3784)):
#0  0x7f16fa5d16cd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f16f52afc10 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f16f526eb14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f16f526ef7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f16f526f0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f16fad597be in QEventDispatcherGlib::processEvents
(this=0x7f16c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f16fad2b0af in QEventLoop::processEvents
(this=this@entry=0x7f16d483cde0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f16fad2b3a5 in QEventLoop::exec (this=this@entry=0x7f16d483cde0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f16fac27c5f in QThread::exec (this=this@entry=0xc50b00) at
thread/qthread.cpp:537
#9  0x7f16fad0c823 in QInotifyFileSystemWatcherEngine::run (this=0xc50b00)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f16fac2a32f in QThreadPrivate::start (arg=0xc50b00) at
thread/qthread_unix.cpp:349
#11 0x7f16f68cc184 in start_thread (arg=0x7f16d483d700) at
pthread_create.c:312
#12 0x7f16fa5e037d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 11 (Thread 0x7f16c700 (LWP 3785)):
[KCrash Handler]
#5  0x7f16d7df8b83 in IpodPlaylist::IpodPlaylist (this=0x7f15d4d722b0,
ipodPlaylist=, collection=0xdcfc10, __in_chrg=,
__vtt_parm=) at
../../../../../src/core-impl/collections/ipodcollection/IpodPlaylist.cpp:42
#6  0x7f16d7e05601 in IpodParseTracksJob::parsePlaylists
(this=this@entry=0x9bccf0, staleTracks=..., knownPaths=...) at
../../../../../src/core-impl/collections/ipodcollection/jobs/IpodParseTracksJob.cpp:118
#7  0x7f16d7e05b8a in IpodParseTracksJob::run (this=0x9bccf0) at
../../../../../src/core-impl/collections/ipodcollection/jobs/IpodParseTracksJob.cpp:82
#8  0x7f16f7e55cb2 in ?? () from /usr/lib/libthreadweaver.so.4
#9  0x7f16f7e55e6e in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) ()
from /usr/lib/libthreadweaver.so.4
#10 0x7f16f7e556bb in ThreadWeaver::Thread::run() () from
/usr/lib/libthreadweaver.so.4
#11 0x7f16fac2a32f in QThreadPrivate::start (arg=0x1105be0) at
thread/qthread_unix.cpp:349
#12 0x7f16f68cc184 in start_thread (arg=0x7f16c700) at
pthread_create.c:312
#13 0x7f16fa5e037d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 10 (Thread 0x7f16cecaf700 (LWP 3786)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f16fac2a816 in wait (time=18446744073709551615, 

[digikam] [Bug 366406] does not write metadata to ORF

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366406

--- Comment #3 from Maik Qualmann  ---
OK. We can close this bug?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365907] digikam timestamp not updated after use of Adjust Time

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365907

Maik Qualmann  changed:

   What|Removed |Added

 CC||philippe.quag...@laposte.ne
   ||t

--- Comment #10 from Maik Qualmann  ---
*** Bug 366450 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366450] Batch time adjust is ok, but time not adjusted in digikam thumbnail

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366450

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||metzping...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #3 from Maik Qualmann  ---


*** This bug has been marked as a duplicate of bug 365907 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 366455] Dolphin's "Details" view can list only track numbers, not titles

[anewuser via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366455

anewuser  changed:

   What|Removed |Added

Summary|In detailed mode, Dolphin   |Dolphin's "Details" view
   |can list only track |can list only track
   |numbers, not titles |numbers, not titles

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 366455] New: In detailed mode, Dolphin can list only track numbers, not titles

[anewuser via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366455

Bug ID: 366455
   Summary: In detailed mode, Dolphin can list only track numbers,
not titles
   Product: dolphin
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: caip...@fastmail.fm

The "track" column displays the track number instead of the track title, and
there's no other option to show the track title.

Reproducible: Always

Steps to Reproduce:
1. Open a folder with song files
2. Set the view to "Details" mode
3. Enable the "Audio -> track" column.

Actual Results:  
A column with the track number is shown.

Expected Results:  
That column should show the track title instead, and it should be possible to
enable another column (Track No.) to see the track number.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored [patch]

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364258

--- Comment #21 from Maik Qualmann  ---
Git commit af3309fe913933fcbc9fd05066ee56e0260e195f by Maik Qualmann.
Committed on 05/08/2016 at 18:41.
Pushed by mqualmann into branch 'master'.

apply patch #100439 from Simon to add information about configuration
transition to welcome screen

M  +20   -5utilities/assistants/firstrun/welcomepage.cpp

http://commits.kde.org/digikam/af3309fe913933fcbc9fd05066ee56e0260e195f

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 366454] New: Right Alt does not change ketboard language layout back to English, both Win keys do not change layout at all

[Ivan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366454

Bug ID: 366454
   Summary: Right Alt does not change ketboard language layout
back to English, both Win keys do not change layout at
all
   Product: systemsettings
   Version: 5.7.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: fio2...@gmail.com

I have two layouts. English as primary and Russian as secondary. When I assign
right Alt key to switch between layouts it can only switch to Russian. No
matter how many times I press it afterwards, there is no way it will switch
back to English.
Left Alt works as it should
With Win key I have even worse situation: it does not change layout at
all(neither when hold nor when presset several times). 
I found this bug more than 1 month ago. 

Reproducible: Always

Steps to Reproduce:
1.Set Right Alt or any Win key to change keyboard layout. Have two layouts:
English(primary) and Russian(secondary)
2.Press or hold any of those keys
3.See layout changed

Actual Results:  
Layout did not change.

Expected Results:  
Layout  changed both to Russian from English and then from English to Russian

First found problem with Right Alt and switched to Right Win, but now neither
of those work.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 349447] Make default duration of transitions configurable

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349447

--- Comment #3 from Wegwerf  ---
I see that we have different use cases in mind: you are using cross-fade
transitions, I'm mostly using compositing and only hard cuts. So, different use
cases.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 359764] Panel doesn't allow resizing

[Andrey Fadeev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359764

Andrey Fadeev  changed:

   What|Removed |Added

 CC||ciiol.m...@gmail.com

--- Comment #18 from Andrey Fadeev  ---
I'm having same problem both with 5.6.5 and current plasma-desktop master
(825f59e3f46978e3d51b279fbe01b5707874c927).

As bisecting shows, the offending commit is a
ba733d16fb2849b2b2cc390ed89b5200dffb5c3f. When I reverted it, the panel
resizing start working as expected

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 357806] git master: keyframe table control for keyframeable effect is broken: changes affect wrong row, timeline slider doesn't have correct begin and end points (probably due to wrong

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357806

Wegwerf  changed:

   What|Removed |Added

Summary|kdenlive-15.12 corners  |git master: keyframe table
   |effect applied to a clip|control for keyframeable
   |with arbitrary aspect ratio |effect is broken: changes
   |is converted to project |affect wrong row, timeline
   |aspect  |slider doesn't have correct
   ||begin and end points
   ||(probably due to wrong row)

--- Comment #15 from Wegwerf  ---
I'm updating the report title to properly reflect the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 357806] kdenlive-15.12 corners effect applied to a clip with arbitrary aspect ratio is converted to project aspect

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357806

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||wegwerf-1-...@gmx.de
 Ever confirmed|0   |1

--- Comment #14 from Wegwerf  ---
The broken keyframe table logic also affects other effects, such as the blurr
effect. This has bitten me now in several projects and makes some parts a real
pain to create or edit. I would really like to see the general keyframe table
regression to be gone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 366426] Image colors warped if opened as .png

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366426

a.nico1...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from a.nico1...@gmail.com ---
It seems that I was in the RGB 8-bit channel instead of the 16-bit one for some
reason, so switching that fixed the problem. Thank you for the help!!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 358504] Possibility to show duration of selected zone

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358504

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
This could be done as an additional timeline "action" element, so everyone is
free to add or remove it from the timeline ... similar to the timeline
length/position "action" element. I like this idea.

-- 
You are receiving this mail because:
You are watching all bug changes.

[keditbookmarks] [Bug 258505] Tried to drag the links into a folder [qDeleteAll<QList<TreeItem*> >, ~TreeItem, TreeItem::deleteChildren, KBookmarkModel::removeBookmark]

[David Faure via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=258505

David Faure  changed:

   What|Removed |Added

 Status|REOPENED|ASSIGNED

--- Comment #32 from David Faure  ---
Nice testcase, I made it into a unittest and I found the two bugs (the null
pointer in comments 19 & 20, and the crash in deleteChildren). First one fixed,
second fix coming up.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 358044] Lumakey Effect listed but does not work

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358044

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME
 CC||wegwerf-1-...@gmx.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 355425] Feature request - Able to start/stop/re-start multiple renderings

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355425

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from Wegwerf  ---
Qubodup, I understand Evert to asking for concurrent render jobs, not for
multithreaded rendering. Depending on the system RAM configuration and project
complexity, it may be possible to render two or three jobs concurrently.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 329091] MySQL : needs to set "max-allowed-packet" server settings from 4.096 to 16.777.216 to prevent Maintenance tool crash

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #27 from uwe.hai...@gmx.net ---
Oops! got some more:

-
(gdb) cont
Continuing.
digikam.general: One job is done
digikam.general: One job is done
digikam.general: One job is done
digikam.general: One job is done
digikam.general: One job is done
"Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im
Pfad /org/freedesktop/NetworkManager/ActiveConnection/2"
"Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im
Pfad /org/freedesktop/NetworkManager/ActiveConnection/2"
digikam.general: One job is done
digikam.metaengine: Cannot load metadata from file   (Error # 11 : 
/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf: The file contains data of an
unknown image type
digikam.general: One job is done
digikam.general: One job is done
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Title:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Comment:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Pick Label:  0
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Color Label:  0
digikam.metaengine: Rating value to write is out of range!
digikam.general: Writting tags
digikam.general: Delete all keywords
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Read Iptc Keywords:  ()
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
New Iptc Keywords:  ()
digikam.metaengine: xmlACDSee ""
digikam.metaengine: MetaEngine::metadataWritingMode 2
digikam.metaengine: Will write Metadata to file "/home/uhai/Bilder_alt/08-11-23
Hd Hausansicht.xcf"
digikam.general: One job is done
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffe96ba72a0,
tinfo=0x771aa480 >,
dest=0x7682a8e0 )
at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
63  in
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc
(gdb)cont
[]
digikam.metaengine: "/home/uhai/Bilder_alt/avatar.png"  ==> Read Iptc Keywords:
 ()
digikam.metaengine: "/home/uhai/Bilder_alt/avatar.png"  ==> New Iptc Keywords: 
()
digikam.metaengine: xmlACDSee ""
digikam.metaengine: MetaEngine::metadataWritingMode 2
digikam.metaengine: Will write Metadata to file
"/home/uhai/Bilder_alt/avatar.png"
digikam.metaengine: wroteComment:  true
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Metadata for file "avatar.png" written to file.
digikam.metaengine: Will write XMP sidecar for file "avatar.png"
digikam.metaengine: wroteComment:  false
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Metadata for file ' "avatar.png" ' written to XMP sidecar.
digikam.general: No write to baloo +
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffee26b3220,
tinfo=0x771aa480 >,
dest=0x7682a8e0 )
at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
63  in
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc
(gdb) cont
Continuing.
digikam.metaengine: Cannot load metadata from file   (Error # 11 : 
/home/uhai/Bilder_alt/bag5.jpg: The file contains data of an unknown image type
digikam.general: One job is done
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Title:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Comment:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Pick Label:  0
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Color Label:  0
digikam.metaengine: Rating value to write is out of range!
digikam.general: Writting tags
digikam.general: Delete all keywords
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Read Iptc Keywords: 
()
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> New Iptc Keywords: 
()
digikam.metaengine: xmlACDSee ""
digikam.metaengine: MetaEngine::metadataWritingMode 2
digikam.metaengine: Will write Metadata to file
"/home/uhai/Bilder_alt/bag5.jpg"
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffef20c0530,
tinfo=0x771aa480 >,
dest=0x7682a8e0 )
at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
63  in
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc
[
---

still running. Now I know "cont" :-)

uhai

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 357053] Fade from Black as Track effect doesn't work, has value 0, can't be deleted

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357053

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Qubodup, I've just tried with recent beta 16.07.90: at least you can now delete
the effect from the track. However, you can't change its default value using
the slider, only using the frame spin box. In addition, it blacks the complete
track.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 356642] FEATURE REQUEST - Allow to reduce timeline height

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356642

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from Wegwerf  ---
Qubodup, with recent beta 16.07.90, optimization fixes to the timeline have
landed, see also here:
http://thediveo-e.blogspot.de/2016/07/kdenlive-ui-resizable-timeline-track.html

In particular:
1. You can set the default track height in Kdenlive's configuration dialog.
2. You can still reduce/enlarge the tracks using the two zoom buttons above all
track headers in the timeline. The track controls now properly stay
visible/usable when reducing the track height, as they will float in line with
the track title.
3. You can change the width of all track headers, by hovering over the end of
the track headers, where the mouse cursor turns into a horizontal resize
indication. Click, resize as you see fit. This now allows for a very lowly
track layout, minimizing both vertical and horizontal space.

Please let us know if this satisfies what you were asking for in your report.
If yes, then please be so kind as 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 349447] Make default duration of transitions configurable

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349447

--- Comment #2 from larsen...@web.de ---
At least for me, that's not what I would want. For example, when I add a
transition to fade from one clip to another, this transition needs to have a
fixed length, but it should not fade over the whole length of one clip. I'd
rather use the same transition length for all my clips in the project.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366446] Creating new albums fails due to invalid path name.

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366446

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
The same here, is not to reproduced. If "/var/media/photos" an external
removable drive?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 353951] While setting up a "crop, scale and position" effect, if I set a value of zero for "tilt x", the program crashes and exits.

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353951

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Paul, I only see the "Crop, Scale and Tilt" effect, so I'm assuming this is now
the same the one you refer to. (I seem to remember that it has been renamed.)

I've tried to reproduce, but the current stable 16.04.2 and beta both don't
crash when setting the Tilt X effect parameter to 0. The image is moved
offscreen as expected.

Can you please check with recent stable 16.04.2 or current beta if you can
still trigger this crash? 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 353066] WISHLIST - Add keyframeable speed effect with intact audio (like iPhone slow-motion)

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353066

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Paul, audio support has finally landed in stable 16.04.2 if I remember
correctly, or at least in current beta.

Keyframing the speed effect is not really possible at this time, the reason is
how the clip length is to be calculated? This would need integration over the
whole clip from the beginning in order to find out where a particular frame for
a given position in the timeline is. Do you have any idea as to how to solve
this?

Paul, would you consider the fixed audio support to be sufficient, and in that
case close this bug as resolved fixed? Unfortunatately, I don't see a any clear
way in how the keyframing actually could work.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 354653] Two menu bars in Unity in version 15.08.1

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354653

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Aslanex, is this still an issue with recent stable Kdenlive 16.04.2?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 349447] Make default duration of transitions configurable

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349447

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
I would like to suggest that when a timeline clip is selected when adding a
transition (to it), that the new transition is created with the same length as
the currently selected timeline clip. I would think that this is what users
often want to do anyway, but I may be wrong.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 343386] Wishlist: Make Paths to videofiles relative in KF5

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343386

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Paul, the resource references in MLT/Kdenlive are actually relative ... but to
MLT's "root" ... which seems to be the user's $HOME. This looks to me to be an
MLT issue upstream, as MLT is the one serializing the Kdenlive project. The
Kdenlive project information is just piggybacked onto it, with most information
already coming from inside MLT/timeline and only those remaining project
information MLT lacks gets piggybacked.

The only way may be to set a different root property of the MLT XML serializer;
maybe we could use the base directory of the .kdenlive project file. However,
I'm unsure as to what this actually will buy us: when moving a project file
together with its media files, the rebase still becomes necessary, as MLT will
trip over the root= attribute not pointing to the new location of the project
file anymore. So we would need to ask the user to locate the media clips
anyway. Not perfect, but there doesn't seem to be any other option left, at
least with the current MLT XML de/serializer architecture.

Paul, could you agree to closing this long-standing bug report, on the
assumption that the above analysis is correct?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366453] New: Digikam se plante sur toute action de la souris sur la barre de titre

[bruno noreve via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366453

Bug ID: 366453
   Summary: Digikam se plante sur toute action de la souris sur la
barre de titre
   Product: digikam
   Version: 4.12.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: bruno.nor...@gmail.com

Application: digikam (4.12.0)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-31-generic i686
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Arrivée du pointeur de souris sur la barre de titre supérieure de l'application
entraîne un plantage systématique. Segmentation Fault.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xaa62b9c0 (LWP 6477))]

Thread 6 (Thread 0xa1b02b40 (LWP 6483)):
#0  0xb2fe35cb in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb2fe4014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb2fe4244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb46d011c in QEventDispatcherGlib::processEvents (this=0xa8033998,
flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0xb469bc5d in QEventLoop::processEvents (this=0xa1b01fe4, flags=...) at
kernel/qeventloop.cpp:149
#5  0xb469bfee in QEventLoop::exec (this=0xa1b01fe4, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb457d0eb in QThread::exec (this=0x9fee9a0) at thread/qthread.cpp:538
#7  0xb467b4a6 in QInotifyFileSystemWatcherEngine::run (this=0x9fee9a0) at
io/qfilesystemwatcher_inotify.cpp:265
#8  0xb457fd3e in QThreadPrivate::start (arg=0x9fee9a0) at
thread/qthread_unix.cpp:352
#9  0xb39342b5 in start_thread (arg=0xa1b02b40) at pthread_create.c:333
#10 0xb422e16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 5 (Thread 0xa75ffb40 (LWP 6482)):
#0  0xb772bc31 in __kernel_vsyscall ()
#1  0xb3939a8c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xb423a8cd in __pthread_cond_wait (cond=0xa01ae28, mutex=0xa01ae10) at
forward.c:149
#3  0xb4580312 in QWaitConditionPrivate::wait (time=4294967295, this=0xa01ae10)
at thread/qwaitcondition_unix.cpp:86
#4  QWaitCondition::wait (this=0xa119780, mutex=0xa11977c, time=4294967295) at
thread/qwaitcondition_unix.cpp:158
#5  0xb6f852de in Digikam::ParkingThread::run (this=0xa119770) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/libs/threads/threadmanager.cpp:119
#6  0xb457fd3e in QThreadPrivate::start (arg=0xa119770) at
thread/qthread_unix.cpp:352
#7  0xb39342b5 in start_thread (arg=0xa75ffb40) at pthread_create.c:333
#8  0xb422e16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 4 (Thread 0xa7fffb40 (LWP 6480)):
#0  0xb302a4a0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb2fe2f4a in g_main_context_acquire () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb2fe3fa8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb2fe4244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb46d011c in QEventDispatcherGlib::processEvents (this=0xa7600488,
flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0xb469bc5d in QEventLoop::processEvents (this=0xa7ffefe4, flags=...) at
kernel/qeventloop.cpp:149
#6  0xb469bfee in QEventLoop::exec (this=0xa7ffefe4, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb457d0eb in QThread::exec (this=0x9f81770) at thread/qthread.cpp:538
#8  0xb467b4a6 in QInotifyFileSystemWatcherEngine::run (this=0x9f81770) at
io/qfilesystemwatcher_inotify.cpp:265
#9  0xb457fd3e in QThreadPrivate::start (arg=0x9f81770) at
thread/qthread_unix.cpp:352
#10 0xb39342b5 in start_thread (arg=0xa7fffb40) at pthread_create.c:333
#11 0xb422e16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 3 (Thread 0xa8914b40 (LWP 6479)):
#0  0xb772bc31 in __kernel_vsyscall ()
#1  0xb3939a8c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xb423a8cd in __pthread_cond_wait (cond=0xa05fc30, mutex=0xa05fc18) at
forward.c:149
#3  0xb4580312 in QWaitConditionPrivate::wait (time=4294967295, this=0xa05fc18)
at thread/qwaitcondition_unix.cpp:86
#4  QWaitCondition::wait (this=0xa05fb8c, mutex=0xa05fb88, time=4294967295) at
thread/qwaitcondition_unix.cpp:158
#5  0x082256be in Digikam::ScanController::run (this=0x9fc5840) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/app/database/scancontroller.cpp:725
#6  0xb457fd3e in QThreadPrivate::start (arg=0x9fc5840) at
thread/qthread_unix.cpp:352
#7  0xb39342b5 in start_thread (arg=0xa8914b40) at pthread_create.c:333
#8  0xb422e16e in clone () at 

[kdenlive] [Bug 354940] Corrupted project after Video Profile change e.g. 1080p50 > 1080p25

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354940

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 356162] .mxf (mpeg2) footage clips are not added completely

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356162

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 356022] crash at exit

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356022

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 365368] git master - opening a particular project (that was made with a past git master build) doesn't have track compositing.

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365368

--- Comment #7 from Wegwerf  ---
Jesse, is this bug still present with recent beta 16.07.90?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 347539] crashes when importing 1920x1080 clip that is over an hour long, MP4 29.97 fps

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347539

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 365839] Unable to open or save a project

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365839

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 350558] 15.08 - Segfault when trying to add title clip

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350558

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 353125] Project broken after update to new kdenlive file format

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353125

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|ASSIGNED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.