[kdenlive] [Bug 373454] git master - Kdenlive crashes when trying to save project under Wayland display server [backtrace log included]

[Jesse]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 373454] New: git master - Kdenlive crashes when trying to save project under Wayland display server [backtrace log included]

[Jesse]

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

Bug ID: 373454
   Summary: git master - Kdenlive crashes when trying to save
project under Wayland display server [backtrace log
included]
   Product: kdenlive
   Version: git-master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com
  Target Milestone: ---

Created attachment 102699
  --> https://bugs.kde.org/attachment.cgi?id=102699=edit
backtrace log

When I tried running Kdenlive under Wayland, going to "File > Save As" caused
Kdenlive to briefly freeze, then crash with segfault error in Terminal. See
attached backtrace log for details.

Bug discovered while running Kdenlive 17.03.70 git master build. Antergos
(Arch) Linux x64, GNOME 3.22.2 desktop environment, Wayland (not X11) 1.12
display server, 4.8.12-2 kernel.

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

[kdenlive] [Bug 372367] Display version on main about page, consider showing in UI

[Jean-Baptiste Mardelle]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kxm
   ||lgui/3d28036b0ed33ef077c7df
   ||6ba30a6d4ceac61884
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 3d28036b0ed33ef077c7df6ba30a6d4ceac61884 by Jean-Baptiste Mardelle.
Committed on 09/12/2016 at 07:05.
Pushed by mardelle into branch 'master'.

Display application version in about dialog header
REVIEW: 129607

M  +3-6src/kaboutapplicationdialog.cpp

https://commits.kde.org/kxmlgui/3d28036b0ed33ef077c7df6ba30a6d4ceac61884

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

[krita] [Bug 362789] Layer docker loses focus while renaming in floating mode (undocked mode)

[Raghavendra kamath]

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

--- Comment #3 from Raghavendra kamath  ---
Yes this works in appimage and not in the git build built using qt present in
my system i.e. 5.7 so i think you are right this is an issue with krita built
with 5.7

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

[kdenlive] [Bug 346608] Use Breeze Dark theme as program's default look?

[Jesse]

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

--- Comment #55 from Jesse  ---
UPDATE: the dark theme is default so long as Breeze is installed. Without it,
color scheme defaults to a light scheme. I don't think I'm writing anything
everybody doesn't already know, but luckily the first-time wizard shows when
Breeze packages aren't installed (on distros like Arch, for example) after
installing Kdenlive. While I, personally, believe brand recognition should be
constant wherever possible, I understand that some distros don't like
unnecessary dependencies as a requirement to install certain things, and I
respect where they're coming from.

All that to say, two things would be needed to close this bug:
1. Have Dark Theme by default when Breeze is installed (done)
2. Have Breeze style as default when program starts the first time (before user
customization).

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

[krita] [Bug 373453] New: import picture from photoshop

[Leon]

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

Bug ID: 373453
   Summary: import picture from photoshop
   Product: krita
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: layer styles
  Assignee: krita-bugs-n...@kde.org
  Reporter: dap...@free.fr
  Target Milestone: ---

Created attachment 102698
  --> https://bugs.kde.org/attachment.cgi?id=102698=edit
you can see the parts where are the clip layer of psp

hi!
when i import a picture from photoshop with some clip layers, krita open them
but the clips are not seen and the picture is not good at all, so i can't work
on krita
Leon

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

[kdevelop] [Bug 373452] New: Renaming class doesn't rename destructor

[Nicolás Alvarez]

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

Bug ID: 373452
   Summary: Renaming class doesn't rename destructor
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: nicolas.alva...@gmail.com
  Target Milestone: ---

Created attachment 102697
  --> https://bugs.kde.org/attachment.cgi?id=102697=edit
Rename dialog

If I rename a class, the constructor is also renamed, but the destructor isn't
and the result doesn't compile. Strangely, the rename dialog looks as if it was
going to rename the destructor too, but then it doesn't.

Code:

class Foo {
public:
Foo();
~Foo();
};

Foo::Foo() {
}

Foo::~Foo() {
}


Right-click on the class name, select "Rename Foo". The dialog looks like it's
going to rename the destructor (screenshot attached). However, once I actually
click the Rename button, I get this:

class Bar {
public:
Bar();
~Foo();
};

Bar::Bar() {
}

Bar::~Foo() {
}

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

[digikam] [Bug 372650] When tagging multiple images a few sidecars get truncated, on OS X.

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
I build a new version of OSX installer for next release 5.4.0, using Exiv2
shared lib 0.26-svn not yet released, but including more than 200 bugfixes. It
will be interesting to see if this file still reproducible.

The OSX installer is available here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[krita] [Bug 373451] New: Krita 3.0.1.1 Language do not change from english

[Carlos Atagua]

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

Bug ID: 373451
   Summary: Krita 3.0.1.1 Language do not change from english
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Translation
  Assignee: krita-bugs-n...@kde.org
  Reporter: atacar...@gmail.com
  Target Milestone: ---

Krita 3.0.1.1 Language do not change from english I try with all languages and
NEVER can change from english (default) to spanish or another one, in the
version krita-3.0-RC-1 it works Ok, but not in this last release
(krita-3.0.1.1-x86_64.appimage)

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

[dolphin] [Bug 373450] New: File Manager crashes randomly

[Cris]

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

Bug ID: 373450
   Summary: File Manager crashes randomly
   Product: dolphin
   Version: 15.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: crisllano...@gmail.com
  Target Milestone: ---

Created attachment 102696
  --> https://bugs.kde.org/attachment.cgi?id=102696=edit
Dolphin crash report

So far Dolphin file manager has crashed 3 times in a row when opening.
Accessing an external HD or locally on root, it crashes. Was prompted to
restart after several updates installed and since then it's caused this issue.
Crash Report added.

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

[colord-kde] [Bug 372450] colord-kde 0.5 does not show any monitor

[Daniel Nicoletti]

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

--- Comment #9 from Daniel Nicoletti  ---
ok, I missread and didn't notice the DP-MST part.
So I brought a DP-DP cable and everything was fine.
Then I attached the DVI cabe to the monitor and instead of seing 3 monitors it
kept showing 2. Of course there is only 2 monitors but I believe it's the same
issue, since you have two identicals monitors it thinks it's the same, I'll
investigate further later to see what Gnome Color Manager does.
Best.

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

[krita] [Bug 373449] New: Crashing when I select some of my animation frames

[Kylen Ford]

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

Bug ID: 373449
   Summary: Crashing when I select some of my animation frames
   Product: krita
   Version: 3.0.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: fordky...@gmail.com
  Target Milestone: ---

I cannot access frames 0-16 of my animation to fix/add to it. I can play my
animation, including those frames, just fine, however; if I click on them,
Krita freezes and promptly crashes.

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Leslie Zhai]

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

--- Comment #73 from Leslie Zhai  ---
(In reply to Thomas Schmitt from comment #72)
> Hi,
> 
> > It is better to use Clang ThreadSanitizer to detect pthread related issue
> 
> I currently see no indication that the problem with CDEmu is related to
> pthreads.

Never mind ;-) it might be Clang's issue ;-P such as:
https://llvm.org/bugs/show_bug.cgi?id=31304
https://llvm.org/bugs/show_bug.cgi?id=28331
https://llvm.org/bugs/show_bug.cgi?id=15836
https://llvm.org/bugs/show_bug.cgi?id=31017


> The refusal of CDEmu on RESERVE TRACK probably stems from
>  
> https://sourceforge.net/p/cdemu/code/ci/master/tree/cdemu-daemon/src/device-
> commands.c
> function command_reserve_track in line 2199.
> One would have to find possible reasons for the two refusals with
>   cdemu_device_write_sense(self, ILLEGAL_REQUEST, COMMAND_SEQUENCE_ERROR);
> in order to learn how to avoid them.
> 
> About the reply of sg_io_hdr_t.host_status == 1 and the errno == 19
> i cannot say much. That's deeper inside the kernel's device driver
> architecture than i ever had to climb down.
> 
> As said, i cannot exclude the possibility that some of libburn's activities
> cause these problems with CDEmu. But i have no such experiences with my
> own drives and got no such reports from other users of real drives.

I will report bug to CDEmu ;-)

Regards,
Leslie Zhai

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

[frameworks-kded] [Bug 372904] kded5 maxing one CPU core after search performed in Dolphin

[Zane Tu]

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

Zane Tu  changed:

   What|Removed |Added

 CC||zan...@gmail.com

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

[ark] [Bug 373448] New: Ark crushes when opening devided rar archive with missing second part.

[bugzilla_noreply]

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

Bug ID: 373448
   Summary: Ark crushes when opening devided rar archive with
missing second part.
   Product: ark
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: cameron...@poczta.fm
CC: rthoms...@gmail.com
  Target Milestone: ---

Application: ark (16.08.2)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.36-5-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
I have archive devided in 2 part files. When the second is missing and I try to
open the first one - ark crushes (normally it shouldn't). Instead, I should be
able to extract half of my archive, but I can't. I am able to extract the first
half with file-roller.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff55ced6880 (LWP 2814))]

Thread 4 (Thread 0x7ff5302ec700 (LWP 2817)):
#0  0x7ff5554720af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff5376df533 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7ff5376ded57 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7ff55546d734 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff5590aed3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7ff541b7c700 (LWP 2816)):
#0  0x7ff554d31200 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff554d3142c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff5599b732b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7ff559964fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7ff55979ff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7ff556ddc1d5 in  () at /usr/lib64/libQt5DBus.so.5
#6  0x7ff5597a49e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ff55546d734 in start_thread () at /lib64/libpthread.so.0
#8  0x7ff5590aed3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ff549eb4700 (LWP 2815)):
#0  0x7ff5590a649d in poll () at /lib64/libc.so.6
#1  0x7ff5525c03e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7ff5525c1fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7ff54c43e839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ff5597a49e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7ff55546d734 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff5590aed3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7ff55ced6880 (LWP 2814)):
[KCrash Handler]
#6  0x7ff559802bf0 in QHashData::rehash(int) () at
/usr/lib64/libQt5Core.so.5
#7  0x7ff559785426 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ff559784a66 in
QPropertyAnimation::updateState(QAbstractAnimation::State,
QAbstractAnimation::State) () at /usr/lib64/libQt5Core.so.5
#9  0x7ff55977d960 in QAbstractAnimation::stop() () at
/usr/lib64/libQt5Core.so.5
#10 0x7ff55977df58 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7ff55977b265 in QUnifiedTimer::updateAnimationTimers(long long) () at
/usr/lib64/libQt5Core.so.5
#12 0x7ff55977bdfc in QAnimationDriver::advanceAnimation(long long) () at
/usr/lib64/libQt5Core.so.5
#13 0x7ff559991f34 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#14 0x7ff55a671e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#15 0x7ff55a67649a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#16 0x7ff559966fc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#17 0x7ff5599b6c7e in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#18 0x7ff5599b7041 in  () at /usr/lib64/libQt5Core.so.5
#19 0x7ff554d31134 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#20 0x7ff554d31388 in  () at /usr/lib64/libglib-2.0.so.0
#21 0x7ff554d3142c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#22 0x7ff5599b730c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#23 0x7ff559964fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#24 0x7ff55996cec6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#25 0x0040d368 in  ()
#26 0x7ff558fe56e5 in __libc_start_main () at /lib64/libc.so.6
#27 0x0040e0e9 in _start ()

Reported using DrKonqi

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

[digikam] [Bug 372650] When tagging multiple images a few sidecars get truncated, on OS X.

[Philip Tuckey]

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

--- Comment #1 from Philip Tuckey  ---
This problem also occurs when writing metadata to the image files. To test
this, I changed the digikam preferences to not use sidecars. The test images
are jpegs and I am writing just one tag to them, "print". The console shows a
few error messages the same as in the initial report, and for a few files the
metadata is NOT written. Again, this is running on OS X, updated to Sierra (the
initial report was under El Capitan).

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

[kphotoalbum] [Bug 370373] Please sort on saving index.xml

[Johannes Zarl-Zierl]

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

--- Comment #7 from Johannes Zarl-Zierl  ---
(In reply to Johannes Zarl-Zierl from comment #6)
> Git commit 69420290638781721128f2fd27b209829b73cd57 by Johannes Zarl-Zierl.
> Committed on 09/12/2016 at 00:16.
> Pushed by johanneszarl into branch 'master'.
> 
> Add benchmarking code for deterministic saving of DB.
> 
> On my system, deterministic saving costs about 34 msec with a database of
> just below 25k images.
> 
> Saving time, non-deterministic: 1473.2 msec
> Saving time, deterministic: 1506.9 msec
> 
> M  +34   -0XMLDB/FileWriter.cpp
> 
> https://commits.kde.org/kphotoalbum/69420290638781721128f2fd27b209829b73cd57

I forgot to mention in the commit message: the numbers were averages of 10
consecutive save operations...

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

[kphotoalbum] [Bug 370373] Please sort on saving index.xml

[Johannes Zarl-Zierl]

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

Johannes Zarl-Zierl  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kph
   ||otoalbum/728df5bb6073cb8d2d
   ||854daec1ecb26bfadd4f96
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit|https://commits.kde.org/kph |
   |otoalbum/728df5bb6073cb8d2d |
   |854daec1ecb26bfadd4f96  |
 Status|RESOLVED|CONFIRMED
 Resolution|FIXED   |---

--- Comment #5 from Johannes Zarl-Zierl  ---
Git commit 728df5bb6073cb8d2d854daec1ecb26bfadd4f96 by Johannes Zarl-Zierl.
Committed on 09/12/2016 at 00:15.
Pushed by johanneszarl into branch 'master'.

Make saving the DB deterministic

M  +6-1XMLDB/FileWriter.cpp

https://commits.kde.org/kphotoalbum/728df5bb6073cb8d2d854daec1ecb26bfadd4f96

--- Comment #6 from Johannes Zarl-Zierl  ---
Git commit 69420290638781721128f2fd27b209829b73cd57 by Johannes Zarl-Zierl.
Committed on 09/12/2016 at 00:16.
Pushed by johanneszarl into branch 'master'.

Add benchmarking code for deterministic saving of DB.

On my system, deterministic saving costs about 34 msec with a database of
just below 25k images.

Saving time, non-deterministic: 1473.2 msec
Saving time, deterministic: 1506.9 msec

M  +34   -0XMLDB/FileWriter.cpp

https://commits.kde.org/kphotoalbum/69420290638781721128f2fd27b209829b73cd57

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

[kphotoalbum] [Bug 370373] Please sort on saving index.xml

[Johannes Zarl-Zierl]

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

Johannes Zarl-Zierl  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kph
   ||otoalbum/728df5bb6073cb8d2d
   ||854daec1ecb26bfadd4f96
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit|https://commits.kde.org/kph |
   |otoalbum/728df5bb6073cb8d2d |
   |854daec1ecb26bfadd4f96  |
 Status|RESOLVED|CONFIRMED
 Resolution|FIXED   |---

--- Comment #5 from Johannes Zarl-Zierl  ---
Git commit 728df5bb6073cb8d2d854daec1ecb26bfadd4f96 by Johannes Zarl-Zierl.
Committed on 09/12/2016 at 00:15.
Pushed by johanneszarl into branch 'master'.

Make saving the DB deterministic

M  +6-1XMLDB/FileWriter.cpp

https://commits.kde.org/kphotoalbum/728df5bb6073cb8d2d854daec1ecb26bfadd4f96

--- Comment #6 from Johannes Zarl-Zierl  ---
Git commit 69420290638781721128f2fd27b209829b73cd57 by Johannes Zarl-Zierl.
Committed on 09/12/2016 at 00:16.
Pushed by johanneszarl into branch 'master'.

Add benchmarking code for deterministic saving of DB.

On my system, deterministic saving costs about 34 msec with a database of
just below 25k images.

Saving time, non-deterministic: 1473.2 msec
Saving time, deterministic: 1506.9 msec

M  +34   -0XMLDB/FileWriter.cpp

https://commits.kde.org/kphotoalbum/69420290638781721128f2fd27b209829b73cd57

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

[kmymoney4] [Bug 349938] hang freeze during QIF import

[allan]

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

--- Comment #20 from allan  ---
Just saw your commment about the ',', and I have tried that, both in a file
name and in a directory, again without problem, I'm afraid.

Allan

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

[kde] [Bug 373447] New: Another crash while playing

[Dany]

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

Bug ID: 373447
   Summary: Another crash while playing
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: d...@live.it
  Target Milestone: ---

Application: kdenlive (16.08.3)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.4.36-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was playing some clips on timeline with clip, effect, transition, and music.
No more.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f595fc80140 (LWP 9696))]

Thread 14 (Thread 0x7f59015f8700 (LWP 9744)):
#0  0x7f59560cb10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f59260be6dd in  () at /usr/lib/mlt/libmltsdl.so
#2  0x7f59560c5454 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7f5957e397df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f5901df9700 (LWP 9743)):
#0  0x7f594965bb33 in pa_detect_fork () at
/usr/lib/pulseaudio/libpulsecommon-9.0.so
#1  0x7f594fa4e4eb in pa_stream_writable_size () at /usr/lib/libpulse.so.0
#2  0x7f5925e54f02 in  () at /usr/lib/libSDL-1.2.so.0
#3  0x7f5925e28800 in  () at /usr/lib/libSDL-1.2.so.0
#4  0x7f5925e30fe8 in  () at /usr/lib/libSDL-1.2.so.0
#5  0x7f5925e728a9 in  () at /usr/lib/libSDL-1.2.so.0
#6  0x7f59560c5454 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f5957e397df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f5902ffd700 (LWP 9742)):
[KCrash Handler]
#6  0x7f5957dd4e62 in __memmove_sse2_unaligned_erms () at
/usr/lib/libc.so.6
#7  0x7f5916a44b49 in drawKdenliveTitle () at /usr/lib/mlt/libmltqt.so
#8  0x7f5916a37862 in  () at /usr/lib/mlt/libmltqt.so
#9  0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#10 0x7f5929a13021 in  () at /usr/lib/mlt/libmltxine.so
#11 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#12 0x7f592692bc07 in  () at /usr/lib/mlt/libmltcore.so
#13 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#14 0x7f592692a7ce in  () at /usr/lib/mlt/libmltcore.so
#15 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#16 0x7f592692fdec in  () at /usr/lib/mlt/libmltcore.so
#17 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#18 0x7f592693030a in  () at /usr/lib/mlt/libmltcore.so
#19 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#20 0x7f5916a47fdb in  () at /usr/lib/mlt/libmltqt.so
#21 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#22 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#23 0x7f5916a47772 in  () at /usr/lib/mlt/libmltqt.so
#24 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#25 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#26 0x7f5916a477c0 in  () at /usr/lib/mlt/libmltqt.so
#27 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#28 0x7f595ed531e9 in  () at /usr/lib/libmlt.so.6
#29 0x7f595ed3d197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#30 0x7f595ed5087f in  () at /usr/lib/libmlt.so.6
#31 0x0074a16d in  ()
#32 0x7f5958827d78 in  () at /usr/lib/libQt5Core.so.5
#33 0x7f59560c5454 in start_thread () at /usr/lib/libpthread.so.0
#34 0x7f5957e397df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f590d9b3700 (LWP 9741)):
#0  0x7f59560cb10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f595ed50bfb in mlt_consumer_rt_frame () at /usr/lib/libmlt.so.6
#2  0x7f59260beb10 in  () at /usr/lib/mlt/libmltsdl.so
#3  0x7f59560c5454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5957e397df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f58d03eb700 (LWP 9713)):
#0  0x7f5957e3048d in poll () at /usr/lib/libc.so.6
#1  0x7f594fec3786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f594fec389c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5958a5672b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5958a0023a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f59588230f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5958827d78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f59560c5454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f5957e397df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f58d9bf9700 

[kmymoney4] [Bug 349938] hang freeze during QIF import

[allan]

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

--- Comment #19 from allan  ---
The small test file still imports without problem here.

In comment #12, there is mention of a problem with an error message window
being overlaid with other windows.  Can you try that, moving superimposed
windows out of the way or closing them?

I can't think of any way to fix a problem that I can't reproduce, sadly.

Allan

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

[Books] [Bug 373446] New: build instructions are incomplete

[Walter Lapchynski]

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

Bug ID: 373446
   Summary: build instructions are incomplete
   Product: Books
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Frameworks Cookbook
  Assignee: kde-doc-engl...@kde.org
  Reporter: w...@ubuntu.com
  Target Milestone: ---

Created attachment 102695
  --> https://bugs.kde.org/attachment.cgi?id=102695=edit
incomplete build instructions

I have not been able to use this to build a PDF because the build instructions
are not complete. I have managed to figure out a lot and have created the
attached additions, which I would have just added to the repo, but they're
incomplete as you can see by the TODO.

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

[Books] [Bug 373445] New: builds invalid epub

[Walter Lapchynski]

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

Bug ID: 373445
   Summary: builds invalid epub
   Product: Books
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Frameworks Cookbook
  Assignee: kde-doc-engl...@kde.org
  Reporter: w...@ubuntu.com
  Target Milestone: ---

Created attachment 102694
  --> https://bugs.kde.org/attachment.cgi?id=102694=edit
flightcrew-cli errors

The linked ePUB on books.k.o is invalid:
https://books.kde.org/frameworks5/KDE-Frameworks-Cookbook.epub

Using the current git:
https://cgit.kde.org/kf5book.git/commit/?id=ff4008b17f889c8e381d2ea0cb208c021572d097
I attempted a rebuild but it was still invalid.

See attached output of flightcrew-cli.

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

[kdenlive] [Bug 372660] Kdenlive: please LOUDLY warn when there is proxy clips

[farid]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #4 from farid  ---
Hi Roman, 

Can you please test if it is fixed?

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

[valgrind] [Bug 342040] Valgrind mishandles clone with CLONE_VFORK | CLONE_VM that clones to a different stack

[Nach]

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

--- Comment #4 from Nach  ---
Hello Philippe,

I double checked with Valgrind 3.12.0 to ensure the bug was still occuring (it
was), and then applied your patch.
The basic code I was testing no longer crashes and seems to be mostly working
as it should with your patch!

Strace now shows: clone(child_stack=NULL,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7f8e5944d9d0) = 16514

Which I'm not sure what to make of.


Anyways, I'm setting a seperate stack to use, and some basic testing shows
things are behaving sanely, although I'm not certain the stack I'm specifying
is even being used.

Of the flags, CLONE_VM|CLONE_VFORK|SIGCHLD, SIGCHLD is indeed being delivered
to the parent, and the child appears to be scheduled before the parent (at
least when tested across a bunch of runs), although the memory is not being
shared, so it would appear CLONE_VM is being ignored.

For the needs of a well implemented posix_spawn() such as in musl or mine,
CLONE_VM and CLONE_VFORK are really just optimizations, so it matters little if
either was not respected. The main issue is to ensure a seperate stack is in
operation in the child in order to not mangle the parent's, and preliminary
testing shows it now appears to be fine.

I'll do further testing with more complicated cases (heavier stack use in
child) to ensure whatever clone mangling is done seems to work for these
scenerios. However, if a library/application is actually expecting the shared
memory semantics, it seems a little more work is required.

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

[kdenlive] [Bug 373433] Crash using motion freeze

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |vpi...@kde.org
Version|unspecified |git-master
  Component|general |Effects & Transitions
Product|kde |kdenlive

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

[kdenlive] [Bug 368427] Resource downloads fail

[farid]

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

farid  changed:

   What|Removed |Added

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

--- Comment #9 from farid  ---
fixed for 16.12

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

[kwin] [Bug 373418] "KDE 2" window decoration is not available in KDE 5

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
A minimal example is at http://developer.kde.org/~cfeck/skeleton-0.1.tar.xz

Both Oxygen and Breeze are fully ported to kdecoration2 API. The Plastik
decoration is actually an Aurorae theme (those you can download via GHNS).

https://cgit.kde.org/oxygen.git/tree/kdecoration
https://cgit.kde.org/breeze.git/tree/kdecoration

Aurorae guide at https://techbase.kde.org/User:Mgraesslin/Aurorae
https://cgit.kde.org/kwin.git/tree/plugins/kdecorations/aurorae/themes/plastik

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

[kmymoney4] [Bug 349938] hang freeze during QIF import

[Jack]

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

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #18 from Jack  ---
Unfortunately, I suspect this is not really a KMyMoney issue, but an issue with
one of the underlying KDE libraries that KMM calls to open the file.  However,
now that we know there is an issue with odd characters in filenames, it seems
more possible that someone could track it down.  Thanks for the extra
information.  (Unfortunately, I don't think there is any more work on KDE4 on
Windows - all efforts are going towards the Frameworks versions.  However, at
some point, we will be able to test this in that environment.

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

[plasmashell] [Bug 373075] Changing Resolution hides programs in task manager

[Eike Hein]

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

--- Comment #1 from Eike Hein  ---
Patch under review at https://phabricator.kde.org/D3628

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

[user-manager] [Bug 373432] [User manager] - New users are not created

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|kdelibs-b...@kde.org|j...@jriddell.org
  Component|kcmshell|kcontrol module
Product|systemsettings  |user-manager

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

[systemsettings] [Bug 373435] Keep Eyes Fresh: Redshift integration into KDE

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christoph Feck  ---


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

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

[kwin] [Bug 371494] Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||da...@ixit.cz

--- Comment #2 from Christoph Feck  ---
*** Bug 373435 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 373351] right-click on files crashes dolphin

[Russell]

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

--- Comment #2 from Russell  ---
 I didn't have kdeconnect installed in the previous version of openSUSE
(13.2) at all, as far as I know. The problem started shortly (a couple
days) after 'upgrading' the system.  I noticed that kdeconnect got
installed during the upgrade, and I was unaware of the program's existence
prior to that. I did look into it, but it wasn't functioning.

I began to discover a slew of other strange problems throughout the entire
system, so yesterday, blaming the mess on a bad 'upgrade', I decided to
format the root partition and install the new system from scratch - not at
all fun considering the many nonstandard configurations I have to make to
run the servers I have.  But the good news is that format & reinstall fixed
the crashing Dolphin and many other problems for me.   Unfortunately this
aggressive solution means I have a couple weeks of work getting the servers
back up & running right.

At this point unless other people experience the same exact problem it's
probably going to be a red herring job, so maybe the ticket ought to be
closed.  I'll leave that decision up to you.  Thanks for looking into it.

On Thu, Dec 8, 2016 at 1:13 AM, Christoph Feck 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=373351
>
> --- Comment #1 from Christoph Feck  ---
> Do you still have an old 'kdeconnect' installed from third-party
> repositories?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[umbrello] [Bug 373249] Ports on components are not aligned at component border

[Ralf Habacker]

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

--- Comment #8 from Ralf Habacker  ---
Git commit d2b7dc0a71e75e2f65f18c0d4f1452bf7544bea5 by Ralf Habacker, on behalf
of Carsten Clever.
Committed on 08/12/2016 at 22:25.
Pushed by habacker into branch 'master'.

Place ports onto parent border.

M  +3-0umbrello/CMakeLists.txt
A  +64   -0umbrello/umlwidgets/childwidgetplacement.cpp [License: GPL
(v2+)]
A  +62   -0umbrello/umlwidgets/childwidgetplacement.h [License: GPL
(v2+)]
A  +148  -0umbrello/umlwidgets/childwidgetplacementpin.cpp [License:
GPL (v2+)]
A  +47   -0umbrello/umlwidgets/childwidgetplacementpin.h [License: GPL
(v2+)]
A  +190  -0umbrello/umlwidgets/childwidgetplacementport.cpp [License:
GPL (v2+)]
A  +36   -0umbrello/umlwidgets/childwidgetplacementport.h [License: GPL
(v2+)]
M  +23   -115  umbrello/umlwidgets/pinportbase.cpp
M  +5-18   umbrello/umlwidgets/pinportbase.h

https://commits.kde.org/umbrello/d2b7dc0a71e75e2f65f18c0d4f1452bf7544bea5

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

[Akonadi] [Bug 373444] New: Notes Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2007-0 to 4:16.08.3+p16.04+git20161208.0216-0

[Gunter Ohrner]

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

Bug ID: 373444
   Summary: Notes Agent spins at 100% CPU after upgrade from
4:16.08.2+p16.04+git20161117.2007-0 to
4:16.08.3+p16.04+git20161208.0216-0
   Product: Akonadi
   Version: 5.3.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@customcdrom.de
  Target Milestone: ---

After today's KDE Neon update from Akonadi 4:16.08.2+p16.04+git20161117.2007-0
to 4:16.08.3+p16.04+git20161208.0216-0, Notes Agent spins at 100% CPU.

It starts doing this immediately after login and also continues immediately
after an "akonadictl restart".

Upon "akonadictl stop", Notes Agent crashes instead of shutting down cleanly.

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

[Akonadi] [Bug 373443] New: Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2007-0 to 4:16.08.3+p16.04+git20161208.0216-0

[Gunter Ohrner]

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

Bug ID: 373443
   Summary: Mail Dispatcher Agent spins at 100% CPU after upgrade
from 4:16.08.2+p16.04+git20161117.2007-0 to
4:16.08.3+p16.04+git20161208.0216-0
   Product: Akonadi
   Version: 5.3.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Mail Dispatcher Agent
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@customcdrom.de
CC: vkra...@kde.org
  Target Milestone: ---

After today's KDE Neon update from Akonadi 4:16.08.2+p16.04+git20161117.2007-0
to 4:16.08.3+p16.04+git20161208.0216-0, Mail Dispatcher Agent spins at 100%
CPU.

It starts doing this immediately after login and also continues immediately
after an "akonadictl restart".

Upon "akonadictl stop", Mail Dispatcher Agent crashes instead of shutting down
cleanly.

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

[Akonadi] [Bug 373442] New: Migration Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2007-0 to 4:16.08.3+p16.04+git20161208.0216-0

[Gunter Ohrner]

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

Bug ID: 373442
   Summary: Migration Agent spins at 100% CPU after upgrade from
4:16.08.2+p16.04+git20161117.2007-0 to
4:16.08.3+p16.04+git20161208.0216-0
   Product: Akonadi
   Version: 5.3.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Migration
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@customcdrom.de
  Target Milestone: ---

After today's KDE Neon update from Akonadi 4:16.08.2+p16.04+git20161117.2007-0
to 4:16.08.3+p16.04+git20161208.0216-0, Migration Agent spins at 100% CPU.

It starts doing this immediately after login and also continues immediately
after an "akonadictl restart".

Upon "akonadictl stop", Migration Agent crashes instead of shutting down
cleanly.

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

[Akonadi] [Bug 373441] New: Archive Mail Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2007-0 to 4:16.08.3+p16.04+git20161208.0216-0

[Gunter Ohrner]

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

Bug ID: 373441
   Summary: Archive Mail Agent spins at 100% CPU after upgrade
from 4:16.08.2+p16.04+git20161117.2007-0 to
4:16.08.3+p16.04+git20161208.0216-0
   Product: Akonadi
   Version: 5.3.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Archive Mail Agent
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@customcdrom.de
  Target Milestone: ---

After today's KDE Neon update from Akonadi 4:16.08.2+p16.04+git20161117.2007-0
to 4:16.08.3+p16.04+git20161208.0216-0, Archive Mail Agent spins at 100% CPU.

It starts doing this immediately after login and also continues immediately
after an "akonadictl restart".

Upon "akonadictl stop", Archive Mail Agent crashes instead of shutting down
cleanly.

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

[kmymoney4] [Bug 349938] hang freeze during QIF import

[Antoine T]

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

Antoine T  changed:

   What|Removed |Added

Version|4.7.2   |4.8.0

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

[kmymoney4] [Bug 349938] hang freeze during QIF import

[Antoine T]

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

--- Comment #16 from Antoine T  ---
Hi, any news on this? I can confirm this bug is still here in a completely
fresh install Windows 10 and fresh Kmymoney 4.8.0. This bug is random, sometime
I can have a windows asking me the date format, sometime it freezes, sometime
it works. I use this app each month, and this month particularly, it never
works, strange...

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

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[bugzilla_noreply]

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

--- Comment #38 from caulier.gil...@gmail.com ---
Please share the new patch to review the code. It will be more easy.

Gilles

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

[digikam] [Bug 373434] No exif data in pictures exported to Flickr.

[bugzilla_noreply]

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

--- Comment #5 from anty...@chelmska.waw.pl ---
WOW, that was fast!
Thank you!

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

[digikam] [Bug 345187] When naming unkown faces digikam only remembers typed characters and not the selected name for the next face [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #11 from Maik Qualmann  ---
Tested with the current version (digiKam-5.4.0), no problem found. I close this
bug.

Maik

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

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[Jan Wolter]

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

--- Comment #37 from Jan Wolter  ---
Hi Gilles,
when changes in the new ignoredDirectories settings text field are made I
trigger now a album rescan to ignore the directories. At this moment the
dbEngineParameters contain the newly inserted ignoredDirectories. But the
CollectionScanner refers to CoreDbAccess().parameters() which do NOT contain
the newly inserted ignoredDirectories.
Could you give me a hint how to update CoreDbAccess().parameters() after
performing changes at dbEngineParameters?

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

[konsole] [Bug 373440] New: konsole --new-tab opens window instead

[Cade Robinson]

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

Bug ID: 373440
   Summary: konsole --new-tab opens window instead
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: cade.robin...@gmail.com
  Target Milestone: ---

On Arch in konsole 16.08.3 "konsole --new-tab" opened a new tab.
With 16.11.80 and 16.11.90 using "konsole --new-tab" opens a new window rather
than a new tab

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

[konsole] [Bug 373438] Confirm Close always prompts, ignores "Do not ask again"

[David Biesack]

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

David Biesack  changed:

   What|Removed |Added

Version|unspecified |15.12.3
  Component|emulation   |general
   Platform|Other   |Ubuntu Packages

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

[konsole] [Bug 373439] New: tabbar uses white text on light background

[David Biesack]

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

Bug ID: 373439
   Summary: tabbar uses white text on light background
   Product: konsole
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tabbar
  Assignee: konsole-de...@kde.org
  Reporter: david.bies...@sas.com
  Target Milestone: ---

Created attachment 102692
  --> https://bugs.kde.org/attachment.cgi?id=102692=edit
screenshot showing hard to read tab labels.

The tab bar uses white text on a light background for tabs that are not
the current tab. The current tab is OK - white text on a medium dark grey bg.
See the attached image.

konsole --version
Qt: 5.5.1
KDE Frameworks: 5.18.0
Konsole: 15.12.3

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

[konsole] [Bug 373438] New: Confirm Close always prompts, ignores "Do not ask again"

[David Biesack]

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

Bug ID: 373438
   Summary: Confirm Close always prompts, ignores "Do not ask
again"
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: david.bies...@sas.com
  Target Milestone: ---

When I close a konsole with the window manager, konsole pops up a dialog
Confirm Close - Konsole
There is a check box "Do not ask again" but if I select that, then select
the [Close Window] buttom, konsole does not remember the option and
asks again the next time.

konsole --version
Qt: 5.5.1
KDE Frameworks: 5.18.0
Konsole: 15.12.3

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

[digikam] [Bug 373434] No exif data in pictures exported to Flickr.

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kip
   ||i-plugins/408a9d4c1d563d99f
   ||a8379a9b569520cd4af4c8c
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Maik Qualmann  ---
Git commit 408a9d4c1d563d99fa8379a9b569520cd4af4c8c by Maik Qualmann.
Committed on 08/12/2016 at 21:04.
Pushed by mqualmann into branch 'master'.

write metadata always to the temp image
FIXED-IN 5.4.0

M  +2-1NEWS
M  +1-1dropbox/dbtalker.cpp
M  +1-1facebook/fbwindow.cpp
M  +1-1flashexport/simpleviewer.cpp
M  +1-1flickr/flickrtalker.cpp
M  +1-1googleservices/gdtalker.cpp
M  +2-2googleservices/gptalker.cpp
M  +1-1googleservices/gswindow.cpp
M  +1-1piwigo/piwigotalker.cpp
M  +1-1rajce/rajcesession.cpp
M  +2-2sendimages/imageresize.cpp
M  +1-1smug/smugwindow.cpp
M  +1-1yandexfotki/yfwindow.cpp

https://commits.kde.org/kipi-plugins/408a9d4c1d563d99fa8379a9b569520cd4af4c8c

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

[krunner] [Bug 373437] New: Had the crash icon in system tray, no noticeable issues

[Bill Brasky]

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

Bug ID: 373437
   Summary: Had the crash icon in system tray, no noticeable
issues
   Product: krunner
   Version: 5.8.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: 411skit...@gmail.com
  Target Milestone: ---

Application: krunner (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.4.0-53-generic x86_64
Distribution: KDE neon User Edition 5.8

-- Information about the crash:
- What I was doing when the application crashed:
Had just logged into a new neon install for the 3rd time. I had just changed
the kernel boot parameter from `acpi_osi=!!` to `acpi_osi=!`.

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

Thread 4 (Thread 0x7fd5e8ace700 (LWP 2203)):
#0  0x7fd601dfdb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd5fdd1e39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd5fdd1e4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd60272823b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd6026d2cea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd6024f7fb4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd604773675 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fd6024fcb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fd5ffbe270a in start_thread (arg=0x7fd5e8ace700) at
pthread_create.c:333
#9  0x7fd601e0982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fd5ebfff700 (LWP 2170)):
#0  0x7fd5fdd62ac9 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fd5fdd1e2a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd5fdd1e4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd60272823b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd6026d2cea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd6024f7fb4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd605b377a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fd6024fcb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fd5ffbe270a in start_thread (arg=0x7fd5ebfff700) at
pthread_create.c:333
#9  0x7fd601e0982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fd5f25c9700 (LWP 2160)):
#0  0x7fd601dfdb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd6012f4c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fd6012f68d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fd5f4f4ea39 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fd6024fcb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd5ffbe270a in start_thread (arg=0x7fd5f25c9700) at
pthread_create.c:333
#6  0x7fd601e0982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fd605a158c0 (LWP 2149)):
[KCrash Handler]
#6  0x7fd5ffbed970 in _xend () at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#7  __lll_unlock_elision (lock=0x7fd5d9351008, private=128) at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#8  0x7fd602eccb25 in KSharedDataCache::clear() () from
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#9  0x7fd6018cc4cb in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5
#10 0x7fd6018cc58f in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5
#11 0x7fd6026ffb09 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fd60270c418 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7fd6027009d3 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7fd60325489c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7fd60325c296 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fd6026d4cf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fd60272716e in QTimerInfoList::activateTimers() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fd6027276a1 in 

[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7

[Bart Van Assche]

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

--- Comment #9 from Bart Van Assche  ---
Analyzing software with Helgrind and DRD may trigger other code paths compared
to analyzing the same software with memcheck. My proposal is to start with
looking into why VEX reports an unhandled instruction. Have you tried to
disassemble the executable with objdump? If not, can you do that and post here
the disassembly for the unhandled instruction bytes?

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

[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

[Jonathan Marten]

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

--- Comment #32 from Jonathan Marten  ---
@Rettich: It's unlikely that the patches will work wih the KF5-based kdepim -
there has been a lot of moving code around and rewriting.  They will need to be
ported; when I get the time and summon up enough courage to use the new kdepim,
then I'll look at the fix again.

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

[valgrind] [Bug 342040] Valgrind mishandles clone with CLONE_VFORK | CLONE_VM that clones to a different stack

[Philippe Waroquiers]

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

--- Comment #3 from Philippe Waroquiers  ---
Can you please try the patch attached to bug 373192 ?
Thanks

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

[valgrind] [Bug 373192] Calling posix_spawn completely broken

[Philippe Waroquiers]

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

--- Comment #8 from Philippe Waroquiers  ---
Created attachment 102691
  --> https://bugs.kde.org/attachment.cgi?id=102691=edit
tentative patch (ugly, only for amd64) patch to better support clone(vfork) and
stack

Can you please try the attached patch ? (patch on latest SVN version)

It seems to improve the clone test case provided in bug 342040,
and I suspect fc25 posix_spawn might fail for similar reason, i.e.
that the parent has prepared a stack for the child, but the child was just
using the copy of the parent stack.

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

[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before

[Ralf Habacker]

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

--- Comment #37 from Ralf Habacker  ---
Git commit f389d9d163d5755fb57db9a834e28d4e3b8bd9fa by Ralf Habacker.
Committed on 08/12/2016 at 20:06.
Pushed by habacker into branch 'master'.

Local fix for using deprecated Qt5 method QGraphicsScene::itemAt(QPointF).

M  +9-0umbrello/umlscene.h

https://commits.kde.org/umbrello/f389d9d163d5755fb57db9a834e28d4e3b8bd9fa

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

[digikam] [Bug 373434] No exif data in pictures exported to Flickr.

[bugzilla_noreply]

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

--- Comment #3 from anty...@chelmska.waw.pl ---
OK, I have de-selected the "write to sidecar files" option in metadata
settings, and now it works. 

It's nice it does, but the connection between metadata saving setting and the
export is far from clear.

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

[kdevelop] [Bug 373399] kdevelop crashed during startup

[Krzysztof]

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

--- Comment #3 from Krzysztof  ---
This type of crash isn't reproducible in a sense that it's not known what it
causes. It happens very rarely. However, after it crashes already it usually
would crash several times afterwards. As I remind, some time it asked me to
clear internal state or so.

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

[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7

[Tushar]

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

--- Comment #8 from Tushar  ---
Our computers are part of a $20+ million semiconductor capital equipment whose
annual maintenance contract itself runs into hundreds of thousands of dollars a
year.  So we can't drop support for legacy systems easily.  So it is very
relevant to us.

I can help with investigation and testing but some pointers would definitely
help.

To summarize my findings are

The crash only happens with 64 bit drd and helgrind test case.  memcheck is OK.
32 bit test cases have not problem with either of the checkers.

so I'm wondering if  this issue contained inside VEX or do the checkers also
have a role to play.  Am I on the right track with my thought process?

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

[digikam] [Bug 373434] No exif data in pictures exported to Flickr.

[bugzilla_noreply]

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

--- Comment #2 from anty...@chelmska.waw.pl ---
Just to understand you correctly - you mean the stdout on regular console, not
some console within the digikam?
If so - this is the output (the URLs and tokens omitted):

kipi.plugins: Creating new ImageListViewItem with url  QUrl("")  for list view 
KIPIPlugins::KPImagesListView(0x560db1791c00)
kipi.plugins: Insterting new item  "DSC_5624.JPG"
kipi.plugins: Creating new ImageListViewItem with url  QUrl("")  for list view 
KIPIPlugins::KPImagesListView(0x560db22a4ba0)
kipi.plugins: Family status set to false
kipi.plugins: Friends status set to false
kipi.plugins: Public status set to false
kipi.plugins: Safety level set to 1
kipi.plugins: Content type set to 1
kipi.plugins: Group name is :  ""
kipi.plugins: Token is :  ""
kipi.plugins: Public status set to true
kipi.plugins: Calling auth methods
kipi.plugins: Check token url:  QUrl("")
kipi.plugins: Request to update thumbnail for  QUrl("")
kipi.plugins: Request to update thumbnail for  QUrl("")
kipi.plugins: KIPI host send thumb ( QSize(512, 341) ) for  QUrl("")
kipi.plugins: Update thumb in list for  QUrl("")
kipi.plugins: Received new thumbnail for url  QUrl("")  for view 
KIPIPlugins::KPImagesListView(0x560db1791c00)
kipi.plugins: KIPI host send thumb ( QSize(512, 341) ) for  QUrl("")
kipi.plugins: Update thumb in list for  QUrl("")
kipi.plugins: Received new thumbnail for url  QUrl("")  for view 
KIPIPlugins::KPImagesListView(0x560db22a4ba0)
kipi.plugins: Token= ""
kipi.plugins: Perms= "write"
kipi.plugins: nsid= ""
kipi.plugins: username= ""
kipi.plugins: fullname= ""
kipi.plugins: Token Obtained is :  ""
kipi.plugins: SlotTokenObtained invoked setting user Display name to  ""
kipi.plugins: Group name is :  ""
kipi.plugins: Token is :  ""
kipi.plugins: Group name is :  ""
kipi.plugins: Token written of group  ""  is  ""
kipi.plugins: List photoset invoked
kipi.plugins: List photoset URL QUrl("")
kipi.plugins: CheckToken finished
kipi.plugins: parseResponseListPhotosets ""
...
kipi.plugins: GetPhotoList finished
kipi.plugins: slotPopulatePhotoSetComboBox invoked
kipi.plugins: Get max file size url:  QUrl("")
kipi.plugins: Max upload size is "209715200"
kipi.plugins: SlotUploadImages invoked
kipi.plugins: Adding images QUrl("")  to the list
kipi.plugins: Max allowed file size is :  209715200 File Size is  14220534
digikam.dimg: ""  : JPEG file identified
digikam.metaengine: Loading image history  ""
digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => 
QDateTime(2016-08-21 19:45:51.000 CEST Qt::TimeSpec(LocalTime))
digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC
profile.
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: MetaEngine::metadataWritingMode 1
digikam.metaengine: Will write XMP sidecar for file "DSC_5624.jpg"
digikam.metaengine: wroteComment:  false
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Metadata for file "DSC_5624.jpg" written to XMP sidecar.
kipi.plugins: Resizing and saving to temp file: 
"/tmp/kipi-Flickr-1877/DSC_5624.jpg"
kipi.plugins: QUrl path is  QUrl("file:///tmp/kipi-Flickr-1877/DSC_5624.jpg")
Image size after resizing (in bytes) is  4144354
kipi.plugins: SlotUploadImages done
kipi.plugins: Photoid=  "31475461966"
kipi.plugins: addPhotoToPhotoSet invoked
kipi.plugins: Add photo to Photo set url:  QUrl("")
kipi.plugins: parseResponseListPhotosets "\n\n\n"


Hope this helps (but I do not see anything suspicious here, except maybe the
sidecar files).
If you meant some other console - I have not found any in the documentation,
but I would be happy to follow instructions ;). 

M.

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

[KScreen] [Bug 373110] Screens configuration is not changed when connecting/disconnecting external monitors

[Simone Gaiarin]

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

--- Comment #1 from Simone Gaiarin  ---
journalctl output right after undocking: http://pastebin.com/QcJiHaM8

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

[Albert Vaca]

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

--- Comment #9 from Albert Vaca  ---
Git commit b7418c1db65fa4229ab929efa17642ae01468a8d by Albert Vaca.
Committed on 08/12/2016 at 19:50.
Pushed by albertvaka into branch 'master'.

Socket should be volatile to prevent data-race

M  +1-1src/org/kde/kdeconnect/Backends/LanBackend/LanLink.java

https://commits.kde.org/kdeconnect-android/b7418c1db65fa4229ab929efa17642ae01468a8d

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

[kdenlive] [Bug 373436] Crash while title transform reproduction

[Dany]

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

Dany  changed:

   What|Removed |Added

  Component|general |Effects & Transitions
Product|kde |kdenlive

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

[kde] [Bug 373436] Crash while title transform reproduction

[Dany]

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

--- Comment #1 from Dany  ---
The transform title transition has a affine transition too (inserted by
default). Deleting affine transition Kdenlive don't crash.

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

[kde] [Bug 373436] New: Crash while title transform reproduction

[Dany]

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

Bug ID: 373436
   Summary: Crash while title transform reproduction
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: d...@live.it
  Target Milestone: ---

Application: kdenlive (16.08.3)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.4.36-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was playing some clips in timeline. It crash always in the same point/frame.
In that mean it is a title with trasform transition.

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb7e9218140 (LWP 1388))]

Thread 14 (Thread 0x7fb77125e700 (LWP 1413)):
#0  0x7fb7df66310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb7af6636dd in  () at /usr/lib/mlt/libmltsdl.so
#2  0x7fb7df65d454 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7fb7e13d17df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fb7732f5700 (LWP 1411)):
#0  0x7fb7e13c44ed in read () at /usr/lib/libc.so.6
#1  0x7fb7d2c02f81 in pa_read () at
/usr/lib/pulseaudio/libpulsecommon-9.0.so
#2  0x7fb7d8fdd50e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0
#3  0x7fb7d8fddf80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7fb7af3f9eed in  () at /usr/lib/libSDL-1.2.so.0
#5  0x7fb7af3cd800 in  () at /usr/lib/libSDL-1.2.so.0
#6  0x7fb7af3d5fe8 in  () at /usr/lib/libSDL-1.2.so.0
#7  0x7fb7af4178a9 in  () at /usr/lib/libSDL-1.2.so.0
#8  0x7fb7df65d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fb7e13d17df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fb7722f3700 (LWP 1410)):
[KCrash Handler]
#6  0x7fb7e136ceb3 in __memmove_sse2_unaligned_erms () at
/usr/lib/libc.so.6
#7  0x7fb79ffe9b49 in drawKdenliveTitle () at /usr/lib/mlt/libmltqt.so
#8  0x7fb79ffdc862 in  () at /usr/lib/mlt/libmltqt.so
#9  0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#10 0x7fb7b2f77021 in  () at /usr/lib/mlt/libmltxine.so
#11 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#12 0x7fb7afed0c07 in  () at /usr/lib/mlt/libmltcore.so
#13 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#14 0x7fb7afecf7ce in  () at /usr/lib/mlt/libmltcore.so
#15 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#16 0x7fb7afed4dec in  () at /usr/lib/mlt/libmltcore.so
#17 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#18 0x7fb7afed530a in  () at /usr/lib/mlt/libmltcore.so
#19 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#20 0x7fb79ffecfdb in  () at /usr/lib/mlt/libmltqt.so
#21 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#22 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#23 0x7fb79ffec772 in  () at /usr/lib/mlt/libmltqt.so
#24 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#25 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#26 0x7fb79ffec7c0 in  () at /usr/lib/mlt/libmltqt.so
#27 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#28 0x7fb7e82eb1e9 in  () at /usr/lib/libmlt.so.6
#29 0x7fb7e82d5197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#30 0x7fb7e82e887f in  () at /usr/lib/libmlt.so.6
#31 0x0074a16d in  ()
#32 0x7fb7e1dbfd78 in  () at /usr/lib/libQt5Core.so.5
#33 0x7fb7df65d454 in start_thread () at /usr/lib/libpthread.so.0
#34 0x7fb7e13d17df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fb772af4700 (LWP 1409)):
#0  0x7fb7df66310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb7af663f4e in  () at /usr/lib/mlt/libmltsdl.so
#2  0x7fb7df65d454 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7fb7e13d17df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7fb77bfff700 (LWP 1400)):
#0  0x7fb7d94a0dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fb7d945af89 in g_main_context_query () at /usr/lib/libglib-2.0.so.0
#2  0x7fb7d945b6f8 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fb7d945b89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fb7e1fee72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fb7e1f9823a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fb7e1dbb0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  

[systemsettings] [Bug 373435] New: Keep Eyes Fresh: Redshift integration into KDE

[David Heidelberg]

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

Bug ID: 373435
   Summary: Keep Eyes Fresh: Redshift integration into KDE
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: da...@ixit.cz
  Target Milestone: ---

Why think about integrating Redshift [1] into KDE?

Because KDE could provide more pleasant experience by optimizing screen colors
to match day time, to reduce eyes strain. Very nicely it's very nicely
presented here [2].

How could it be done?

I would suggest to integrate Redshift directly into settings and allow users
set day & night colors. Also offer possibility to read current location (or
enter it manually) to figure out, when sun goes down.
Also allow possibility to disable Redshift and return original gamma and red
value, in case when it's manipulated with photographic material (webdesign
etc.) or battery is at critical level.

Inspiration could be taken from CyanogenMod 12+ systems, where this feature is
presented as LiveDisplay.

Also when considering this feature, please try Redshift or some similar program
at least 5 minutes, before eyes get used to different color. After while you'll
see eyes adapt to new default "white" and calibrate accordingly.

[1] http://jonls.dk/redshift/
[2] https://play.google.com/store/apps/details?id=com.urbandroid.lux=en

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

[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7

[Bart Van Assche]

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

--- Comment #7 from Bart Van Assche  ---
Everyone RHEL user I know either uses RHEL 6 or RHEL 7. How relevant is RHEL 4
today?

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

[konsole] [Bug 342201] Crash on Konsole exit when using proprietary nvidia drivers

[Greg Lepore]

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

Greg Lepore  changed:

   What|Removed |Added

 CC||g...@rhobard.com

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

[kwin] [Bug 373420] kwin crashes after slowness

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin  ---
You have to ask your distribution about how to get debug symbols.

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

[frameworks-baloo] [Bug 373006] Plasma crash when using search box

[bugzilla_noreply]

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

--- Comment #1 from kdebt45...@outlook.com ---
Duplicate of 369430 ?
https://bugs.kde.org/show_bug.cgi?id=369430

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

[digikam] [Bug 373434] No exif data in pictures exported to Flickr.

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
At all my test images on flickr the metadata is available. Problem is not
reproducible here. Can you upload the messages from the console when you upload
a image to flickr?

Maik

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

[kwin] [Bug 373420] kwin crashes after slowness

[Paul Haggerty]

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

--- Comment #2 from Paul Haggerty  ---
(In reply to Martin Gräßlin from comment #1)
> Unfortunately the backtrace is missing debug symbols (as normal on any Arch
> based distro). Without the backtrace we are not able to investigate the
> issue.
> 
> From what we see it looks like a crash in the proprietary nvidia driver.

Hey Martin,

This crash happens pretty regularly, is there some config I can change so that
the debug symbols will be present in the future?

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

[kwin] [Bug 373356] drawing artifacts (not updated or transparent horizontal single-pixel lines)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #6 from Martin Gräßlin  ---
Great! If it also happens in XRender it's not a problem in KWin, but somewhere
else.

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

[kwin] [Bug 373420] kwin crashes after slowness

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is missing debug symbols (as normal on any Arch
based distro). Without the backtrace we are not able to investigate the issue.

>From what we see it looks like a crash in the proprietary nvidia driver.

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

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||lashk...@landau.ac.ru

--- Comment #72 from Martin Gräßlin  ---
*** Bug 373413 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 373413] kwin_x11 crashes on KDE session startup

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin  ---
As a workaround use the breeze window decoration.

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

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

[kwin] [Bug 373412] Kwin crash at login

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is missing debug symbols. Without the backtrace we
are not able to investigate the issue.

If you are able to reproduce please attach a new backtrace with debug packages
installed.

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

[kwin] [Bug 373411] Kwin crashed after java remote terminal was started (VMWare 6.5)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is missing debug symbols (as normal on any Arch
based distro). Without the backtrace we are not able to investigate the issue.

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

[kwin] [Bug 373403] Kwin crashes randomly

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is missing debug symbols (as normal on any Arch
based distro). Without the backtrace we are not able to investigate the issue.

>From what we see it looks like a crash in the proprietary fglrx driver.

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

[digikam] [Bug 373434] No exif data in pictures exported to Flickr.

[bugzilla_noreply]

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

anty...@chelmska.waw.pl changed:

   What|Removed |Added

   Platform|Other   |Debian testing

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

[digikam] [Bug 373434] New: No exif data in pictures exported to Flickr.

[bugzilla_noreply]

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

Bug ID: 373434
   Summary: No exif data in pictures exported to Flickr.
   Product: digikam
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: libkipi
  Assignee: digikam-de...@kde.org
  Reporter: anty...@chelmska.waw.pl
  Target Milestone: ---

After updating Digikam to the 5.x.x, the flickr export apparently removes all
the exif data.
I am using digikam v5.3.0 on latest Debian Stretch on Intel,
KDE Frameworks 5.27.0,
Qt 5.7.1 (built against 5.6.1),
The xcb windowing system.

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

[kde] [Bug 373433] New: Crash using motion freeze

[Ionut Ciocirlan]

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

Bug ID: 373433
   Summary: Crash using motion freeze
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ionut.ciocir...@gmail.com
  Target Milestone: ---

Application: kdenlive (17.03.70)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.8.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
Trying to use the motion freeze effect simply crashes the application.

Using git mlt, and git kdenlive. The same happens with the official debian
testing packages.

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd991df7540 (LWP 3811))]

Thread 13 (Thread 0x7fd8efffd700 (LWP 3835)):
[KCrash Handler]
#6  0x7fd9872edb50 in pthread_mutex_lock () from
/lib/x86_64-linux-gnu/libpthread.so.0
#7  0x7fd990a82d72 in mlt_properties_find (name=name@entry=0x7fd95b2fc5ab
"_unique_id", self=self@entry=0x7fd90a50fdb0) at mlt_properties.c:513
#8  mlt_properties_get (self=self@entry=0x7fd90a50fdb0,
name=name@entry=0x7fd95b2fc5ab "_unique_id") at mlt_properties.c:789
#9  0x7fd95b2f20e2 in GlslManager::get_frame_specific_data
(service=service@entry=0x7fd90a50fdb0, frame=frame@entry=0x7fd908c1b650,
key=key@entry=0x7fd95b2fc5c9 "_movit effect", length=length@entry=0x0) at
filter_glsl_manager.cpp:281
#10 0x7fd95b2f21de in GlslManager::get_effect
(service=service@entry=0x7fd90a50fdb0, frame=frame@entry=0x7fd908c1b650) at
filter_glsl_manager.cpp:307
#11 0x7fd95b2f3866 in build_fingerprint (service=0x7fd90a50fdb0,
frame=0x7fd908c1b650, fingerprint=fingerprint@entry=0x7fd8efffca70) at
filter_movit_convert.cpp:203
#12 0x7fd95b2f3982 in build_fingerprint
(service=service@entry=0x5568d8c9cc50, frame=frame@entry=0x7fd908c1f3e0,
fingerprint=fingerprint@entry=0x7fd8efffca70) at filter_movit_convert.cpp:215
#13 0x7fd95b2f5054 in finalize_movit_chain (frame=0x7fd908c1f3e0,
leaf_service=0x5568d8c9cc50) at filter_movit_convert.cpp:312
#14 convert_image (frame=0x7fd908c1f3e0, image=0x7fd8efffcc58,
format=0x5568cf6ae38c, output_format=mlt_image_glsl_texture) at
filter_movit_convert.cpp:566
#15 0x7fd990a7c708 in mlt_frame_get_image (self=self@entry=0x7fd908c1f3e0,
buffer=buffer@entry=0x7fd8efffcc58, format=format@entry=0x5568cf6ae38c,
width=width@entry=0x7fd8efffcc44, height=height@entry=0x7fd8efffcc48,
writable=writable@entry=0) at mlt_frame.c:591
#16 0x7fd990a91d79 in producer_get_image (self=self@entry=0x7fd908041210,
buffer=buffer@entry=0x7fd8efffcc58, format=format@entry=0x5568cf6ae38c,
width=width@entry=0x7fd8efffcc44, height=height@entry=0x7fd8efffcc48,
writable=writable@entry=0) at mlt_tractor.c:370
#17 0x7fd990a7c6b7 in mlt_frame_get_image (self=self@entry=0x7fd908041210,
buffer=buffer@entry=0x7fd8efffcc58, format=format@entry=0x5568cf6ae38c,
width=width@entry=0x7fd8efffcc44, height=height@entry=0x7fd8efffcc48,
writable=writable@entry=0) at mlt_frame.c:585
#18 0x7fd990a8f58c in consumer_read_ahead_thread (arg=0x5568cfb2aa00) at
mlt_consumer.c:825
#19 0x5568cbb024d5 in RenderThread::run() ()
#20 0x7fd98ab0bd88 in QThreadPrivate::start (arg=0x7fd9000389e0) at
thread/qthread_unix.cpp:368
#21 0x7fd9872eb464 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#22 0x7fd989f0b9df in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 12 (Thread 0x7fd90dca5700 (LWP 3834)):
#0  0x7fd9872f118f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7fd990a8f77b in mlt_consumer_rt_frame
(self=self@entry=0x5568cfb2aa00) at mlt_consumer.c:1576
#2  0x7fd95a547c58 in consumer_thread (arg=0x5568cfb2aa00) at
consumer_sdl_audio.c:531
#3  0x7fd9872eb464 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7fd989f0b9df in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 11 (Thread 0x7fd92288d700 (LWP 3828)):
#0  g_mutex_unlock (mutex=0x7fd8f8000990) at ././glib/gthread-posix.c:1348
#1  0x7fd9846c492e in g_main_context_acquire (context=0x7fd8f8000990) at
././glib/gmain.c:3283
#2  0x7fd9846c58a5 in g_main_context_iterate
(context=context@entry=0x7fd8f8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3879
#3  0x7fd9846c5b0c in g_main_context_iteration (context=0x7fd8f8000990,
may_block=may_block@entry=1) at ././glib/gmain.c:3990
#4  0x7fd98ad3b6fb in QEventDispatcherGlib::processEvents
(this=0x7fd8f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fd98ace507a in QEventLoop::exec 

[kmymoney] [Bug 373431] automatic ledger change

[allan]

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

--- Comment #1 from allan  ---
It sounds like to get around the problem, you make two changes at the same
time, or more.
You use your backup file on a different PC running a different distro.
What might be more informative is if you were able to transfer your backup file
(or a copy of), to your first PC and see if that works.  If so, it might
indicate a problem with your original file.

Generally, any errors that show on saving are from the consistency check, and
are not necessarily related to the current operations, but are often historic,
from original file creations.

Allan

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

[kipiplugins] [Bug 115550] Flickr Export Loses EXIF Information

[bugzilla_noreply]

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

anty...@chelmska.waw.pl changed:

   What|Removed |Added

 CC||anty...@chelmska.waw.pl

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

[systemsettings] [Bug 373432] New: [User manager] - New users are not created

[keitalbame]

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

Bug ID: 373432
   Summary: [User manager] - New users are not created
   Product: systemsettings
   Version: 5.8.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcmshell
  Assignee: kdelibs-b...@kde.org
  Reporter: keitalb...@posteo.net
  Target Milestone: ---

The newly created user is not created on /etc/passwd nor is displayed on User
Manager after finishing creation.

In previous versions, the new users weres created. The only issue was that the
user with uid 1001 never appeared on User Manager but all users were created on
/etc/passwd.

Same issue on a fully updated Arch box.

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

[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()

[Ritesh Raj Sarraf]

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

--- Comment #11 from Ritesh Raj Sarraf  ---
As for the initial crash, for which the steps to reproduce I have, I'm not sure
if I have a better trace. It looks like Debian doesn't have the necessary
dbgsym symbols packaged. :-(


(gdb) bt
#0  0x74c4b178 in QSortFilterProxyModel::parent(QModelIndex const&)
const ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x74c4b00c in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x74c4b1b8 in QSortFilterProxyModel::parent(QModelIndex const&)
const ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x757f702b in QTreeView::isIndexHidden(QModelIndex const&) const ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x757f96ef in QTreeView::visualRect(QModelIndex const&) const ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x757a161a in  () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x757a1b6a in  () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7fffca391269 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x7fffca391919 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#9  0x7fffca395d2c in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#10 0x71137e88 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x7113a8ee in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x74cafb39 in QObject::event(QEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7556ab2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x755722e1 in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x74c83090 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x74c8581d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x74cd72d3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fffebb2d7f7 in g_main_context_dispatch (context=0x7fffc40016f0)
at ././glib/gmain.c:3203
#19 0x7fffebb2d7f7 in g_main_context_dispatch
(context=context@entry=0x7fffc40016f0)
at ././glib/gmain.c:3856
#20 0x7fffebb2da60 in g_main_context_iterate
(context=context@entry=0x7fffc40016f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3929
#21 0x7fffebb2db0c in g_main_context_iteration (context=0x7fffc40016f0,
may_block=1)
at ././glib/gmain.c:3990
#22 0x74cd76df in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x74c8107a in
QEventLoop::exec(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x74c897ec in QCoreApplication::exec() ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0xa111 in main(int, char**) (argc=,
argv=)
at ./core/app/main/main.cpp:237
(gdb)

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

[digikam] [Bug 331878] GROUP : the «grouped images icon» disapears when working on the main (front) image

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #5 from Maik Qualmann  ---
You use versioning? I think yes. Actually normal behavior. Enable the option
"Always show original images" in the settings for versioning.

Maik

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

[frameworks-kdesu] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

   Version Fixed In||5.29.0
Version|15.08.3 |5.25.0
Product|dolphin |frameworks-kdesu
  Latest Commit||https://cgit.kde.org/kdesu.
   ||git/commit/?id=e3ff52adec24
   ||9b7cfa1a375866c268485a1cd34
   ||4
  Component|general |general
 Status|UNCONFIRMED |RESOLVED
 CC||wba...@tmo.at
 Resolution|--- |FIXED
   Assignee|dolphin-bugs-n...@kde.org   |kdelibs-b...@kde.org

--- Comment #16 from Wolfgang Bauer  ---
(In reply to Anton Kuleshov from comment #15)
> This bug affect not only dolphin. I think any kde apps lauched with kdesu
> have same problem. At least i have same problem with Kate.

Yes, it was a bug in kdesu, and it should be fixed in KDE Frameworks 5.29.0.
https://cgit.kde.org/kdesu.git/commit/?id=e3ff52adec249b7cfa1a375866c268485a1cd344

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

[systemsettings] [Bug 343427] kcm_sddm : Allow keyboard layout selection

[keitalbame]

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

keitalbame  changed:

   What|Removed |Added

 CC||keitalb...@posteo.net

--- Comment #10 from keitalbame  ---
(In reply to Florian Jacob from comment #9)
> This is still an issue. While the default theme of sddm now has a keyboard
> layout chooser since November 2015, the breeze theme, which is developed as
> part of plasma and not of sddm, still lacks one in plasma workspace 5.8.3.

At the moment, using Neon user edition 5.8.4, the Layout selector only appears
when start typing and a second layout different from en_US on system settings
>> keyboard >> layouts.

Seems that the layouts are not being added to SDDM.

Using for example, I needed to use localectl set-x11-keymap --no-convert pt ,
to add the European portugues keyboard layout to SDDM.

NOTE: The always showing US layout (although the correct one is set) is still
ongoing. Manually selecting US and then, the second layout, workarounds the
problem until logout/reboot.

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

[kmymoney] [Bug 373431] New: automatic ledger change

[bugzilla_noreply]

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

Bug ID: 373431
   Summary: automatic ledger change
   Product: kmymoney
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: j915...@mvrht.com
  Target Milestone: ---

Since I upgraded kmymoney to version 4.8.0 (running on my lubuntu 16.04
notebook) I get lots of errors about my ledger entries. The complete story:

I went out online to solve the pictures issue (they don't display in the
version provided by the Ubuntu softwarecenter). I understood I had to update
Kmymoney to the newest version.

The first few new entries in the ledger goes allright. Suddenly when I'm still
entering the details of the transaction, the buttons "save" and "cancel" don't
work anymore. I can click on a "new", but then I see still the same details I
just entered, and the buttons "save" and "cancel" still don't work. When I save
it and want to close the program, I get errors about some old entries.
Especially the entries I didn't work on at the moment I get the error.
Since I don't get the message before it is getting saved, I have to go back to
my backup file in order to start the last changes all over again on my desktop
pc (ubuntu 14.04) wich is running the version of kmymoney provided in the
softwarecenter.

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

[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()

[Ritesh Raj Sarraf]

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

--- Comment #10 from Ritesh Raj Sarraf  ---
I'm not sure if I have clear steps to reproduce, for this crash [1]. But, now
I've installed some more debug packages. If the crash occurs again, and I have
a better trace, I'll share it with you

As for the video card, this is a very standard setup. Intel Haswell box with an
Intel on-board graphics.


[1] digikam crashed with SIGSEGV in QMetaObject::cast()

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

[kmail2] [Bug 362803] Can't change KMail Message List font size with custom font settings.

[Gerd Fleischer]

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

Gerd Fleischer  changed:

   What|Removed |Added

 CC||gerdfleisc...@web.de

--- Comment #6 from Gerd Fleischer  ---
Same here with KMail 5.3.0 on OpenSuse Leap 42.2.

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

[basket] [Bug 257807] Cross reference a basket with ñ in title

[bugzilla_noreply]

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

rusty.robo...@gmail.com changed:

   What|Removed |Added

 CC||rusty.robo...@gmail.com

--- Comment #1 from rusty.robo...@gmail.com ---
Thanks, fixed in 2.11

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

[basket] [Bug 263245] Basket crashes when I try to delete italicized text

[bugzilla_noreply]

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

rusty.robo...@gmail.com changed:

   What|Removed |Added

 CC||rusty.robo...@gmail.com

--- Comment #1 from rusty.robo...@gmail.com ---
Cannot reproduce, seems to be fixed in 2.10.

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

[plasmashell] [Bug 373427] Plasmashell hangs after some notifications

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #9 from David Edmundson  ---
So the plasma process is hanging but everything else is responsive?

Can you (when it's frozen) run:
sudo gdb --pid `pidof plasmashell` from a terminal

then when that attached type "thread apply all bt" to get a log.
then copy and paste that here.


It probably means plasma is blocked waiting for X to do something, but this
will tell us exactly.

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

[plasmashell] [Bug 365111] Widgets explorer is missing a lot of icons for its items

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #10 from David Edmundson  ---
This was fixed by David Rosca with some commit in KIconThemes.

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

[plasmashell] [Bug 373423] Plasma crashes when disconnecting laptop from dockingstation

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Edmundson  ---
It's a bug in Qt, I'm pretty sure it's fixed in newer versions.
5.5 is really old. Please upgrade.

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

[plasmashell] [Bug 369430] QQmlDelegateModel::_q_itemsChanged - kickoff version

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||kdebt45...@outlook.com

--- Comment #9 from David Edmundson  ---
*** Bug 373400 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 373400] Crash while browsing in Application Menu

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from David Edmundson  ---


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

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