[i18n] [Bug 443691] New: Wrong translation in wallpaper of the day settings

2021-10-13 Thread Rico Riedel
https://bugs.kde.org/show_bug.cgi?id=443691

Bug ID: 443691
   Summary: Wrong translation in wallpaper of the day settings
   Product: i18n
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: de
  Assignee: kde-i18n...@kde.org
  Reporter: rico.rie...@protonmail.ch
  Target Milestone: ---

SUMMARY
There are two wrong translations in the wallpaper of the day settings.

STEPS TO REPRODUCE
1. Change system language to "Schweiz - Scheizer Hochdeutsch (de_CH)"
2. Right click wallpaper
3. Choose "Arbeitsfläche und Hintergrund einrichten"
4. Choose type "Bild des Tages"

OBSERVED RESULT
The provider "Unsplash Wallpapers" is translated to "Hintergrundbilder nichts
als Startbildschirm verwenden."
The categorie "Lock Screen" is translated to "Bildschirm sperren" (which means
"to look the screen" not "a lock screen")

EXPECTED RESULT
Provider = Unsplash Wallpapers
Categorie "Lock Screen" = "Sperrbildschirm"

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
-

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

[baloo-widgets] [Bug 425014] Address field is a required information

2020-08-04 Thread Rico Tester
https://bugs.kde.org/show_bug.cgi?id=425014

Rico Tester  changed:

   What|Removed |Added

 Status|VERIFIED|CLOSED

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

[baloo-widgets] [Bug 425016] New: Address field should be blank

2020-08-04 Thread Rico Tester
https://bugs.kde.org/show_bug.cgi?id=425016

Bug ID: 425016
   Summary: Address field should be blank
   Product: baloo-widgets
   Version: unspecified
  Platform: Microsoft Windows
   URL: http://demo.guru99.com/V1/index.php
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: xzhang...@myseneca.ca
  Reporter: ricovergara1...@hotmail.com
  Target Milestone: ---

Created attachment 130643
  --> https://bugs.kde.org/attachment.cgi?id=130643=edit
Bug error screenshot

SUMMARY


STEPS TO REPRODUCE
1. Click New Customer
2. Leave address blank
3. Fill up other required fields
4. Click submit

OBSERVED RESULT
No error message is appeared


EXPECTED RESULT
Error Message appear "Address Field must not be blank"

SOFTWARE/OS VERSIONS
Windows: Windows 10
macOS: N/A
Linux/KDE Plasma:  N/A
(available in About System): N/A
KDE Plasma Version: N/A
KDE Frameworks Version: N/A
Qt Version: N/A

ADDITIONAL INFORMATION
Please address issue as soon as possible. If you need additional information
about the bug, please email or set a meeting for faster turn around.

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

[baloo-widgets] [Bug 425014] Address field is a required information

2020-08-04 Thread Rico Tester
https://bugs.kde.org/show_bug.cgi?id=425014

Rico Tester  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #10 from Rico Tester  ---
I confirmed that bug is now working.

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

[baloo-widgets] [Bug 425014] Address field is a required information

2020-08-04 Thread Rico Tester
https://bugs.kde.org/show_bug.cgi?id=425014

Rico Tester  changed:

   What|Removed |Added

 Status|VERIFIED|REOPENED
 Resolution|FIXED   |---

--- Comment #7 from Rico Tester  ---
After a day the error is back.

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

[baloo-widgets] [Bug 425014] Address field is a required information

2020-08-04 Thread Rico Tester
https://bugs.kde.org/show_bug.cgi?id=425014

Rico Tester  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #6 from Rico Tester  ---
The issue is now resolved.

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

[baloo-widgets] [Bug 425014] Address field is a required information

2020-08-04 Thread Rico Tester
https://bugs.kde.org/show_bug.cgi?id=425014

Rico Tester  changed:

   What|Removed |Added

 Resolution|REMIND  |---
 Status|NEEDSINFO   |ASSIGNED

--- Comment #4 from Rico Tester  ---
No test data need for this bug since the test case is for blank field.

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

[baloo-widgets] [Bug 425014] New: Address field is a required information

2020-08-04 Thread Rico Tester
https://bugs.kde.org/show_bug.cgi?id=425014

Bug ID: 425014
   Summary: Address field is a required information
   Product: baloo-widgets
   Version: unspecified
  Platform: Microsoft Windows
   URL: http://demo.guru99.com/V1/index.php
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: xzhang...@myseneca.ca
  Reporter: ricovergara1...@hotmail.com
  Target Milestone: ---

Created attachment 130642
  --> https://bugs.kde.org/attachment.cgi?id=130642=edit
Screenshot of error

SUMMARY


STEPS TO REPRODUCE
1. Click New Customer
2. Leave address blank
3. Fill up other required fields
4. Click submit

OBSERVED RESULT
No error message is appeared


EXPECTED RESULT
Error Message appear "Address Field must not be blank"

SOFTWARE/OS VERSIONS
Windows: Windows 10
macOS: N/A
Linux/KDE Plasma:  N/A
(available in About System): N/A
KDE Plasma Version: N/A
KDE Frameworks Version: N/A
Qt Version: N/A

ADDITIONAL INFORMATION
Please address issue as soon as possible. If you need additional information
about the bug, please email or set a meeting for faster turn around.

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

[digikam] [Bug 418162] New: additional empty popup in geolocation dialog

2020-02-24 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418162

Bug ID: 418162
   Summary: additional empty popup in geolocation dialog
   Product: digikam
   Version: 7.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Geolocation
  Assignee: digikam-bugs-n...@kde.org
  Reporter: rico.zie...@posteo.de
  Target Milestone: ---

Created attachment 126392
  --> https://bugs.kde.org/attachment.cgi?id=126392=edit
screenshot

SUMMARY
Not really an issue with impact. Sometimes appears an empty additional popup,
when geolocation popup is called. I guess it appears only if a meta data
information was changed before 

STEPS TO REPRODUCE
1. Select a picture. Open preview 
2. in sidebar go to keywords and choose and assign a tag ( do not apply)
3. now open geo location popup. 

OBSERVED RESULT
2 new popups come up. One empty in background and the expected

EXPECTED RESULT


SOFTWARE/OS VERSIONS
appimage version 7.0.0.

ADDITIONAL INFORMATION
Sometimes the additional popup disappears when the diaog is closed. Sometimes
it remains until end of the session. The poup is always in background, in the
screenshot I moved the geoloction popup

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

[digikam] [Bug 418061] Position of faces copied when rotating an image

2020-02-23 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

--- Comment #13 from Rico  ---
is there any "other application" that can read also that face rectangle?
That would help to answer this question too.

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

[digikam] [Bug 418061] Position of faces copied when rotating an image

2020-02-23 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

--- Comment #12 from Rico  ---
Created attachment 126327
  --> https://bugs.kde.org/attachment.cgi?id=126327=edit
original picture before import

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

[digikam] [Bug 418061] Position of faces copied when rotating an image

2020-02-23 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

--- Comment #11 from Rico  ---
Created attachment 126326
  --> https://bugs.kde.org/attachment.cgi?id=126326=edit
first the screensho after import of the pic

i guess the rectangle was transformed by 90 or 270°

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

[digikam] [Bug 418061] Position of faces copied when rotating an image

2020-02-23 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

--- Comment #10 from Rico  ---
Hi Maik,
that was really fast! When there is a appdata build out, including that fix, i
will retest.
Regarding the last point, do you have an idea when it was changed?
The face rectangles came not from db. I imported the files on a new
installation. Infomration came from the file. I will attach a picture last
change about 201810. ( I guess with a at that time latest stable on a unbuntu
system) But I don't know whether I added at that time the face rectangle.

Maybe it help to find out, whether it was stored wrong or imported wrong.

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

[digikam] [Bug 418061] Position of faces copied when rotating an image

2020-02-22 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

--- Comment #6 from Rico  ---
Hi Maik,
I played now around for a while and confused now. I was not able to reproduce
it 100% now. Onetime it happened directly on start up, often not. 

First thouhgt was also it happens in combination with the preview in dolphin,
or when the folder is just open but later  it happened also with closed dolphin
and worked somethimes with opened.

I think it is also file related. One time only for one file the tag was copied.
For other it worked in the same session. 

I cannot say how to reproduce but somethimes it happens.
Could digikam lock somehow itself? I was wondering about the statusbar text " x
fiels waiting for sync" (rough translated from german) .
Could that be something combined with the lazy sync option maybe in combination
with writing directly in the file?

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

[digikam] [Bug 418061] Position of faces copied when rotating an image

2020-02-22 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

--- Comment #4 from Rico  ---
metadata was written in preview of the picture, directly in the image, one time
by drwing the rectangle, entering top and confirmed pushbutton with ok.
Afterwards (directly I rotated the image in the preview. Each time, the tag was
copied on time. The position was shifted also somehow by 90°.

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

[digikam] [Bug 418061] Position of faces copied when rotating an image

2020-02-22 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

--- Comment #3 from Rico  ---
Created attachment 126314
  --> https://bugs.kde.org/attachment.cgi?id=126314=edit
original pic2

Hi Maik,
thanks for the fast response. 
I attached now the original picture, not the screenshot (the tags should be
saved 4 times in the pic). Maybe it helps to answer your question. If not let
me know where I can get the info you need.

Regarding the older pics:
It is a good thing to align with standards. Maybe one day face tags can be
interpreted by other apps too.
Do you think it is stable now and I can fix the position final?

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

[digikam] [Bug 418061] Position of faces copied when rotating an image

2020-02-22 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

--- Comment #1 from Rico  ---
Created attachment 126313
  --> https://bugs.kde.org/attachment.cgi?id=126313=edit
screenshot2

second screenshot

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

[digikam] [Bug 418061] New: Position of faces copied when rotating an image

2020-02-22 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=418061

Bug ID: 418061
   Summary: Position of faces copied when rotating an image
   Product: digikam
   Version: 7.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Faces-Maintenance
  Assignee: digikam-bugs-n...@kde.org
  Reporter: rico.zie...@posteo.de
  Target Milestone: ---

Created attachment 126312
  --> https://bugs.kde.org/attachment.cgi?id=126312=edit
screenshot1

SUMMARY
Face areas copied when rotating an image

STEPS TO REPRODUCE
1. Open a picture
2. Set in preview an face tag (screenshot 1)
3. press 4 times CTRL+SHIFT RIGHT to rotate picture (screenshot 2) 

OBSERVED RESULT
tags are copied 3 or 4 times


EXPECTED RESULT
should not be copied

SOFTWARE/OS VERSIONS

I used the latest appimage of digikam (beta3 from 20200220) on opsensuse
thumbleweed

ADDITIONAL INFORMATION
I'm useing digikam sinces some years and discover from release to release
problems with the position of tagged faces. It is hard to create a reproducable
example because I don't know whether it was an error with a earlier version
(when the tag was created) or this one (when the tag was read).

I'am pretty sure that there is/was an similar error with the postition face
areas in combination with the oriantation of the picture.
All the positions from my older, tagged pictures (2017/2018/2019); taken from
my mobile phone in potrait mode seems to rotated by 90° with that release.
Maybe in combination of rotating meta data? Tags are not copied, seems to be
moved by 90°
Do you know something that goes into that direction in the past?

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

[kmail2] [Bug 393333] kmail: columns in mail folders sizing broken, doesn't remember settings, add ghost column

2018-05-04 Thread Rico Rommel
https://bugs.kde.org/show_bug.cgi?id=39

Rico Rommel <r...@bierrommel.de> changed:

   What|Removed |Added

 CC||r...@bierrommel.de

--- Comment #1 from Rico Rommel <r...@bierrommel.de> ---
I can confirm this with kmail 5.7.3 on Debian unstable, Qt 5.10.1, kde
frameworks 5.44.

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

[Falkon] [Bug 391298] Kwallet extension save password in binary mode instead text

2018-03-03 Thread Rico Rommel
https://bugs.kde.org/show_bug.cgi?id=391298

Rico Rommel <r...@bierrommel.de> changed:

   What|Removed |Added

 CC||r...@bierrommel.de

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

[kdenlive] [Bug 378102] New: kdenlive stürzt immer ab

2017-03-26 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=378102

Bug ID: 378102
   Summary: kdenlive stürzt immer ab
   Product: kdenlive
   Version: 16.12.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: texasrange...@web.de
  Target Milestone: ---

Application: kdenlive (16.12.3)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.28.0
Operating System: Linux 4.4.0-53-generic x86_64
Distribution: Linux Mint 18.1 Serena

-- Information about the crash:
- What I was doing when the application crashed: kdenlive stürzt bei
clipüberlagerung oder im playmode ab
...

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Aborted
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 0x7ff0408d18c0 (LWP 6430))]

Thread 27 (Thread 0x7fef7affd700 (LWP 6560)):
[KCrash Handler]
#6  0x7ff03a034428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7ff03a03602a in __GI_abort () at abort.c:89
#8  0x7ff009e998ad in movit::YCbCrInput::set_gl_state(unsigned int,
std::__cxx11::basic_string
const&, unsigned int*) () from /usr/lib/x86_64-linux-gnu/libmovit.so.4
#9  0x7ff009e8b838 in movit::EffectChain::execute_phase(movit::Phase*,
bool, std::set*,
std::map,
std::allocator > >*,
std::set, std::allocator
>*) () from /usr/lib/x86_64-linux-gnu/libmovit.so.4
#10 0x7ff009e8bf70 in movit::EffectChain::render_to_fbo(unsigned int,
unsigned int, unsigned int) () from /usr/lib/x86_64-linux-gnu/libmovit.so.4
#11 0x7ff00a0f87af in
GlslManager::render_frame_texture(movit::EffectChain*, mlt_frame_s*, int, int,
unsigned char**) () from /usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#12 0x7ff00a0fb802 in ?? () from
/usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#13 0x7ff03fa86e68 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#14 0x7ff03fa9bf09 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#15 0x7ff03fa86e17 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#16 0x7ff03fa99658 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#17 0x00736cad in RenderThread::run (this=0x7fef2c818170) at
/build/kdenlive-StayKY/kdenlive-16.12.3~ubuntu16.04.1/src/monitor/glwidget.cpp:1268
#18 0x7ff03ab00808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7ff0389fb6ba in start_thread (arg=0x7fef7affd700) at
pthread_create.c:333
#20 0x7ff03a10582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fef7b7fe700 (LWP 6559)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff03fa998e3 in mlt_consumer_rt_frame () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#2  0x7ff00263cd90 in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so
#3  0x7ff0389fb6ba in start_thread (arg=0x7fef7b7fe700) at
pthread_create.c:333
#4  0x7ff03a10582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7fef7bfff700 (LWP 6548)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff016d878ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7ff0389fb6ba in start_thread (arg=0x7fef7bfff700) at
pthread_create.c:333
#3  0x7ff03a10582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 24 (Thread 0x7fef8302c700 (LWP 6547)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff016d878ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7ff0389fb6ba in start_thread (arg=0x7fef8302c700) at
pthread_create.c:333
#3  0x7ff03a10582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 23 (Thread 0x7fef8202a700 (LWP 6546)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff016d878ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7ff0389fb6ba in start_thread (arg=0x7fef8202a700) at
pthread_create.c:333
#3  0x7ff03a10582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7fef8282b700 (LWP 6545)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff016d878ae in ?? () from

[kdenlive] [Bug 378060] New: kdenlive stürzt bei clipüberlagerung ab

2017-03-25 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=378060

Bug ID: 378060
   Summary: kdenlive stürzt bei clipüberlagerung ab
   Product: kdenlive
   Version: 16.12.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: texasrange...@web.de
  Target Milestone: ---

kdenlive stürtzt immer ab wenn ich zwei clips übereinander lege, es ist immer
das selbe problem. leider sagt der absturzmanager immer das ungenügend
informationen für einen detailierten fehlerbericht vorhanden sind. 

es tut mir leid das ich noch nicht in der lage bin einen fehlerbericht auf
englisch zu verfassen, ich hoffe sie können mir trotzdem helfen. ich nutze
kdenlive für ehrenamtliche projekte.

mein system: i5 4960k, nvidia gtx 960 4gb, linux mint 18.1 kde

mfg, Rammbock

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

[kdenlive] [Bug 377957] New: beim verschieben eines clips stürtzt kdenlive ständig ab

2017-03-22 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=377957

Bug ID: 377957
   Summary: beim verschieben eines clips stürtzt kdenlive ständig
ab
   Product: kdenlive
   Version: 16.12.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: texasrange...@web.de
  Target Milestone: ---

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kdenlive...Reading symbols from
/usr/lib/debug/.build-id/d0/dd276f361be57a4384e9e405647e2b5ecbe616.debug...done.
done.
Attaching to program: /usr/bin/kdenlive, process 4276
Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Vorgang nicht zulässig.
(gdb)

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

[kdenlive] [Bug 376925] wenn ich mit mit dem curser von einem clip zum nächsten springe stürzt kdenlive immer ab

2017-02-25 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=376925

--- Comment #1 from Rico <texasrange...@web.de> ---
im übrigen nutze ich Linux Mint 18.1 KDE
und hier zusätzliche informationen vom letzten Absturz:

Application: Kdenlive (kdenlive), 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 0x7fcc752728c0 (LWP 4730))]

Thread 27 (Thread 0x7fcbb3fff700 (LWP 4787)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbb3fff700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fcbc0ff7700 (LWP 4786)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc0ff7700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7fcbc17f8700 (LWP 4785)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc17f8700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 24 (Thread 0x7fcbc1ff9700 (LWP 4784)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc1ff9700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 23 (Thread 0x7fcbc27fa700 (LWP 4783)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc27fa700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7fcbc2ffb700 (LWP 4777)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc3715595d in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc2ffb700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fcc20e73700 (LWP 4776)):
#0  0x7fcc6ea9ac21 in __GI_ppoll (fds=0x7fcc0c6ecc70, nfds=3,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x7fcc69aebebd in pa_mainloop_poll () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7fcc69aec4ae in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7fcc3cca6feb in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#4  0x7fcc3cc79920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#5  0x7fcc3cc830b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#6  0x7fcc3ccc2f59 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#7  0x7fcc6d39c6ba in start_thread (arg=0x7fcc20e73700) at
pthread_create.c:333
#8  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7fcbc37fc700 (LWP 4775)):
[KCrash Handler]
#6  0x7fcc3ec1c9f4 in MltInput::set_pixel_data(unsigned char const*) ()
from /usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#7  0x7fcc3ec1609d in ?? () from
/usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#8  0x7fcc3ec1588d in ?? () from
/usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#9  0x7fcc3ec167da in ?? () from
/usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#10 0x7fcc744269c8 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#11 0x7fcc7443ca99 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#12 0x7fcc74426977 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#13 0x7fcc7443a110 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#14 0x00736a0d in RenderThread::run (this=0x7fcc0c007b90) at
/build/kdenlive-SJVwLm/kdenlive-16.12.1/src/monitor/glwidget.cpp:1268
#15 0x7fcc6f4a1808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fcc6d39c6ba in start_thread (arg=0x7fcbc37fc700) at
pthread_create.c:333
#17 0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7fcc03bfd700 (LWP 4774)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../s

[kdenlive] [Bug 376925] New: wenn ich mit mit dem curser von einem clip zum nächsten springe stürzt kdenlive immer ab

2017-02-25 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=376925

Bug ID: 376925
   Summary: wenn ich mit mit dem curser von einem clip zum
nächsten springe stürzt kdenlive immer ab
   Product: kdenlive
   Version: 16.12.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: texasrange...@web.de
  Target Milestone: ---

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kdenlive...Reading symbols from
/usr/lib/debug/.build-id/e4/6d5556b45ac35ab0a9ba4d028c87871b2e863c.debug...done.
done.
Attaching to program: /usr/bin/kdenlive, process 4192
ptrace: Kein passender Prozess gefunden.
(gdb)

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