[kdenlive] [Bug 364105] git master - Freezing then crashing when adding video clip to Project Bin

[Jesse via KDE Bugzilla]

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

--- Comment #2 from Jesse  ---
You bet, ill get it and send off in the morning. 22:13 over here. :)

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

[digikam] [Bug 364065] image editor doesn't open at double click

[via KDE Bugzilla]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Update to last digiKam 4.14.0 and try again.

Gilles Caulier

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

[digikam] [Bug 319882] Crash when stitching a panorama

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||derspargelstec...@gmx.de

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

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

[digikam] [Bug 364065] image editor doesn't open at double click

[Garthhh via KDE Bugzilla]

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

--- Comment #3 from Garthhh  ---
the image editor won't open at all no matter how many times I click
if click on a file, click on the image editor toolbar icon, I can't advance to
the next image unless I select all

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

[krita] [Bug 363903] Krita crashes whenever I try to draw on canvas.

[Errjune via KDE Bugzilla]

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

--- Comment #6 from Errjune  ---
No, not whilst screen recording. I think I will uninstall and install krita
again. Thanks for the reply Boude :)

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

[kamoso] [Bug 364123] New: Video stutters after a few seconds of recording

[VaryHeavy via KDE Bugzilla]

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

Bug ID: 364123
   Summary: Video stutters after a few seconds of recording
   Product: kamoso
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: afies...@kde.org
  Reporter: varyhe...@gmail.com

When you turn Kamoso to video mode and begin recording, after a few seconds of
recording, the video starts to stutter, appreciating jumps in sound and image.

I experienced this same behaviour in OpenSUSE Leap 42.1 and Kubuntu 16.04. I
don't remember what Kamoso version ran in OpenSUSE, but in Kubuntu (which I use
currently), the Kamoso version is 3.0.0, from universe repositories, so I have
put 'unspecified' in the field 'Version', because the only option I had,
besides 'unspecified', was the 2.0.2.

Reproducible: Always

Steps to Reproduce:
1. Open Kamoso.
2. Turn to video mode.
3. Start recording and waits 15-25 seconds.

Actual Results:  
Video starts to stutter, appreciating jumps in sound and image.

Expected Results:  
Video recording should be stable in sound and image at all times.

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

[gwenview] [Bug 359492] Gwenview crash when exiting after watching GIF image

[Mario Junior via KDE Bugzilla]

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

--- Comment #4 from Mario Junior  ---
Created attachment 99421
  --> https://bugs.kde.org/attachment.cgi?id=99421=edit
New crash information added by DrKonqi

gwenview (16.04.1) using Qt 5.6.0

I close Gwenview after play a gif and the Gwenview crash.

-- Backtrace (Reduced):
#5  0x7f91f0a78bd2 in QImageReaderPrivate::~QImageReaderPrivate
(this=0x2622c10, __in_chrg=) at image/qimagereader.cpp:572
#6  0x7f91f0a79001 in QImageReader::~QImageReader (this=,
__in_chrg=) at image/qimagereader.cpp:684
#7  0x7f91f0a9724c in QMovie::~QMovie (this=0x1ffeda8, __in_chrg=) at image/qmovie.cpp:619
[...]
#9  0x7f91f4a9196f in Gwenview::Document::~Document() () from
/usr/lib/libgwenviewlib.so.5
#10 0x7f91f4a91af9 in Gwenview::Document::~Document() () from
/usr/lib/libgwenviewlib.so.5

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

[kipiplugins] [Bug 364122] New: KCrash while starting drkonqi due socket connect failed

[via KDE Bugzilla]

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

Bug ID: 364122
   Summary: KCrash while starting drkonqi due socket connect
failed
   Product: kipiplugins
   Version: 4.12.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kde-imag...@kde.org
  Reporter: derspargelstec...@gmx.de

Application: dngconverter (4.12.0)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was adding a raw picture and as soon as I hit convert it crashes. This is
happens ever time but worked fine before the uprade to ubuntu 16.04.

The crash can be reproduced every time.

-- Backtrace:
Application: DNG Image Converter (dngconverter), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9c6d965980 (LWP 23670))]

Thread 6 (Thread 0x7f9c5d868700 (LWP 23678)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9c6bcd53a6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f9c6cefa76e in KIPIPlugins::KPRawThumbThread::run() () from
/usr/lib/digikam/libkipiplugins.so.4.12.0
#3  0x7f9c6bcd4e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f9c6ab276fa in start_thread (arg=0x7f9c5d868700) at
pthread_create.c:333
#5  0x7f9c69fbcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f9c5d067700 (LWP 23679)):
#0  0x7f9c69fb0e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9c660a231c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9c660a242c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9c6be152ce in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f9c6bde318f in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f9c6bde34f5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f9c6bcd2549 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f9c6bdc3223 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f9c6bcd4e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f9c6ab276fa in start_thread (arg=0x7f9c5d067700) at
pthread_create.c:333
#10 0x7f9c69fbcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f9c56fbe700 (LWP 23726)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9c6bcd53a6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f9c6d15ba14 in KDcrawIface::RActionThreadBase::run() () from
/usr/lib/libkdcraw.so.23
#3  0x7f9c6bcd4e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f9c6ab276fa in start_thread (arg=0x7f9c56fbe700) at
pthread_create.c:333
#5  0x7f9c69fbcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f9c56533700 (LWP 23727)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9c6bcd53a6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f9c6ccb3c9c in ?? () from /usr/lib/libthreadweaver.so.4
#3  0x7f9c6ccb69a3 in ?? () from /usr/lib/libthreadweaver.so.4
#4  0x7f9c6ccb54ff in ThreadWeaver::Thread::run() () from
/usr/lib/libthreadweaver.so.4
#5  0x7f9c6bcd4e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f9c6ab276fa in start_thread (arg=0x7f9c56533700) at
pthread_create.c:333
#7  0x7f9c69fbcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f9c55d32700 (LWP 23728)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9c6bcd53a6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f9c6ccb3c9c in ?? () from /usr/lib/libthreadweaver.so.4
#3  0x7f9c6ccb69a3 in ?? () from /usr/lib/libthreadweaver.so.4
#4  0x7f9c6ccb54ff in ThreadWeaver::Thread::run() () from
/usr/lib/libthreadweaver.so.4
#5  0x7f9c6bcd4e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f9c6ab276fa in start_thread (arg=0x7f9c55d32700) at
pthread_create.c:333
#7  0x7f9c69fbcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f9c6d965980 (LWP 23670)):
[KCrash Handler]
#6  

[krita] [Bug 361766] Brush editor context menus don't work

[David REVOY via KDE Bugzilla]

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

David REVOY  changed:

   What|Removed |Added

 CC||i...@davidrevoy.com

--- Comment #3 from David REVOY  ---
Yes, I confirm I'm affected also by this one on 'buntu 16.04 with the patchy
version of Qt5.5 installed by default by Canonical/Debian.

I understand the 'resolved upstream' tag to this bug , because I guess new
builds will solve it for Windows users. 

I didn't found any PPA workaround to update Qt on 16.04... It's a pretty bad
sign if all the derivatives of Ubuntu will be affected by similar issue for the
next two years ( Linux Mint, Elementary and all based on LTS ). I hope at one
point they'll move to Qt 5.6.1

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

[umbrello] [Bug 359002] toolbar with text and icons

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Ralf Habacker  ---
That the text is not shown for some icons in 'Text Alongside Icons' mode caused
by a toolbar item settings.

To change the visiblity of an icon text:
1. right-click on toolbar
2. select "configure Toolbar"
3. select related action and press "change Text"
4. select or deselect "Hide text when toolbar shows text alongside icons

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

[kdenlive] [Bug 364105] git master - Freezing then crashing when adding video clip to Project Bin

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
I cannot reproduce. Can you post a gdb backtrace ?
https://kdenlive.org/node/872 (last paragraph)

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

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Yuri via KDE Bugzilla]

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

--- Comment #47 from Yuri  ---
Ah, I see. I didn't realize the pdf form-saving code was even there. This makes
the situation much better than I thought.

Thanks for clarifying this!

Somebody should just remove the code writing under ~/.kde4/share/apps/okular/

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

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Aaron Wolf via KDE Bugzilla]

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

--- Comment #46 from Aaron Wolf  ---
@Yuri, Carsten was saying that the current Okular behavior *does* save data
directly to the PDF *if* you use "save as" but otherwise not. The problem
remaining is that it also saves to a hidden directory as well, and then
conflicts and security issues can arise from that.

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

[umbrello] [Bug 364120] Umbrello toolbar icons do not match diagram widgets and cursors running under "breeze" style

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

Summary|Umbrello toolbar icons does |Umbrello toolbar icons do
   |not match diagram widgets   |not match diagram widgets
   |and cursors running under   |and cursors running under
   |"breeze" style  |"breeze" style

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

[umbrello] [Bug 364120] Umbrello toolbar icons does not match diagram widgets and cursors running under "breeze" style

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||2.19.80 (KDE Applications
   ||16.07.80)
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/umbr
   ||ello/4bc648dbc006212ed1d6aa
   ||16295f03cce153327a

--- Comment #1 from Ralf Habacker  ---
Git commit 4bc648dbc006212ed1d6aa16295f03cce153327a by Ralf Habacker.
Committed on 08/06/2016 at 22:50.
Pushed by habacker into branch 'master'.

Fix 'Umbrello toolbar icons does not match diagram widgets and cursors running
under "breeze" style'.

Icons are now integrated into umbrello binary by using a qrc file.
FIXED-IN:2.19.80 (KDE Applications 16.07.80)

M  +1-0CMakeLists.txt
M  +1-0umbrello/CMakeLists.txt
M  +29   -5umbrello/icon_utils.cpp
A  +174  -0umbrello/icons.qrc
M  +1-0umbrello/main.cpp

http://commits.kde.org/umbrello/4bc648dbc006212ed1d6aa16295f03cce153327a

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

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Yuri via KDE Bugzilla]

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

--- Comment #45 from Yuri  ---
(In reply to Carsten Gräser from comment #44)
> I gave a very detailed explanation of "in principle". just try out as
> described above.

I don't know what are you talking about. You don't make yourself clear.

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

[KScreen] [Bug 358011] dual screen not setup after reboot

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #15 from Sebastian Kügler  ---
Good news. We have fixed two race conditions in the daemon that applies the
config on login and on monitor changes. Also, Plasma shell has now moved away
from KScreen and uses QScreen for setting up the desktop, panels, etc. This
makes the desktop shell work a lot smoother on screen changes.

Kai Uwe and Martin systems don't show this bug anymore, so I'm quite confident
that Plasma 5.7 brings a notable improvement, so it would be good to get some
more feedback from people who are able to test. Plasma 5.7 Beta which is due in
mid-June would be a good target, otherwise more testing of git master would
also be great.

I'm not closing this bug report as RESOLVED FIXED  just yet, but I think we're
a lot closer.

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

[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage

[Simon Solinas via KDE Bugzilla]

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

Simon Solinas  changed:

   What|Removed |Added

 CC|ksol...@gmail.com   |

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

[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage

[Simon Solinas via KDE Bugzilla]

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

Simon Solinas  changed:

   What|Removed |Added

 CC||ksol...@gmail.com

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

[kio] [Bug 357930] SSHFS mount - Dolphin complains disk is full

[Daniel Bull via KDE Bugzilla]

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

--- Comment #4 from Daniel Bull  ---
Sorry I should have mentioned I'm not using gvfs, I'm using sshfs with afuse
but the error is the same. I can delete and open files but not create them or
copy them into an sshfs folder.

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

[umbrello] [Bug 364120] New: Umbrello toolbar icons does not match diagram widgets and cursors running under "breeze" style

[Ralf Habacker via KDE Bugzilla]

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

Bug ID: 364120
   Summary: Umbrello toolbar icons does not match diagram widgets
and cursors running under "breeze" style
   Product: umbrello
   Version: 2.19.1 (KDE Applications 16.04.1)
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de

When running umbrello under breeze style (for example on openSUSE Leap 42.1) 
umbrello related toolbar icons does not match the (default) color and layout of
related widgets on the diagram and related cursors.

People knowing umbrello told me that it is now hard to add new uml objects to a
diagram using the toolbar.


Reproducible: Always

Steps to Reproduce:
1. start umbrello 
2.  add a class, interface, datatype to a diagram

Actual Results:  
The tools bar icons differs in color and look and feel 

Expected Results:  
The tool bar icons should match the cursor and widget style on diagrams.

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

[kmymoney4] [Bug 349033] option to invert transaction amounts during import

[harry bennett via KDE Bugzilla]

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

--- Comment #5 from harry bennett  ---
No, I did nothing but edit for the foo/bar due to privacy concerns.
I'll have to do an import to check. I'll get back to you.

The OP is from a year ago, maybe it got fixed?

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

[umbrello] [Bug 359002] toolbar with text and icons

[Ralf Habacker via KDE Bugzilla]

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

--- Comment #2 from Ralf Habacker  ---
umbrello uses a method from the KDE gui library
(KStandardAction::printPreview()) to create the common actions like new, 
print, print preview menu entries. These actions are also used for the toolbar. 

In KDE4 builds the text is missing in "text beside icon" mode for new, print,
print preview, undo and redo.
In KF5 builds the texts for new, undo and redo are shown, but still not
displayed for print and print preview, which looks really like an issue in some
of the base libraries.

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

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Carsten Gräser via KDE Bugzilla]

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

--- Comment #44 from Carsten Gräser  ---
(In reply to Yuri from comment #43)
> (In reply to Carsten Gräser from comment #42)
> > Yuri, this is not correct. Okular can in principle save the data to the pdf.
> > But the interplay of this with saving to and loading from .kde/... is not
> > very intuitive.
> 
> What does it mean "can in principle"? Is the code saving it to the pdf there
> or not there? If it is there, can you send the link (line numbers)?
I gave a very detailed explanation of "in principle". just try out as described
above.

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

[kdenlive] [Bug 364106] git master - Preview render not working & Adding preview zone makes in-out zone area real small

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
A few questions: 
* What project profile are you using when you see that error in timeline
preview (I am especially interested in fps for the profile)
* Can you tell me which preview rendering profile is selected (in Project >
Project Settings > Preview Profile
* Can you attach a screenshot showing the timeline ruler with thin selection
zone ?

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

[kmail2] [Bug 364119] KMail displays launchpad commit notifications with wrong content order

[Christian Boltz via KDE Bugzilla]

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

--- Comment #1 from Christian Boltz  ---
Created attachment 99420
  --> https://bugs.kde.org/attachment.cgi?id=99420=edit
Screenshot showing the bug

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

[kdeconnect] [Bug 363947] kde connect: Could not mount device.

[via KDE Bugzilla]

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

priv...@bernhard-lindner.de changed:

   What|Removed |Added

 CC||priv...@bernhard-lindner.de

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

[kmail2] [Bug 364119] New: KMail displays launchpad commit notifications with wrong content order

[Christian Boltz via KDE Bugzilla]

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

Bug ID: 364119
   Summary: KMail displays launchpad commit notifications with
wrong content order
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kde-b...@cboltz.de

Created attachment 99419
  --> https://bugs.kde.org/attachment.cgi?id=99419=edit
example message to reproduce the bug (mail addresses changed, Received:-headers
removed)

I recently upgraded to KMail 5.2.1 from the KDE Applications 16.04.1 release.

This is a regression somewhere between KMail from KDE Applications 15.12.2 and
16.04.1.

The commit notifications sent out by launchpad are Content-Type:
multipart/mixed with two sections: 1. a text/plain part that contains the
commit message etc. and 
2. a text/x-diff section that contains the actual change in unified diff format
(I'll attach a sample mail)

Since the update to KDE Applications 16.04.1 (I never tested 16.04), KMail
displays those mails with wrong content order:
1. the diff
2. the diff, again
3. the commit message

Expected behaviour (worked in 15.12.2): display the mails in the order as
defined in the mail, which means
1. the commit message
2. the diff

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

[valgrind] [Bug 364058] array overruns are not detected

[Sergey Meirovich via KDE Bugzilla]

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

--- Comment #7 from Sergey Meirovich  ---
Thanks for the explanation. Is that could be concluded by implication from the
manual?

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

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Nicolás Alvarez via KDE Bugzilla]

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

--- Comment #48 from Nicolás Alvarez  ---
Since we're not going to write and maintain a custom patch to deal with this,
please take this problem to upstream Bugzilla. I'm sure you would be interested
in not having this problem with any other bugtracker either, rather than just
KDE...

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

[kwin] [Bug 364118] New: present windows alternate activation key does not toggle

[Jason Tibbitts via KDE Bugzilla]

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

Bug ID: 364118
   Summary: present windows alternate activation key does not
toggle
   Product: kwin
   Version: 5.6.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ti...@math.uh.edu

This is kind of a weird one.  I wanted two different sets of hotkeys to
activate present windows, and convenientky there are "Global" and "Global
Alternate" hotkeys.  But while both hotkeys will activate the present windows
effect, the alternate one will not act as a toggle.  This happens regardless of
the keys I assign.

This might happen for other toggleable effects; I didn't try.


Reproducible: Always

Steps to Reproduce:
Assign a global alternate hotkey to the 'Toggle Present Windows (All desktops)
action.

Press that hotkey to activate the present windows effect.

Press that hotkey again.

Actual Results:  
The present windows effect does not toggle off.

Expected Results:  
The present windows effect toggles off.

I'm running kwin 5.6.4 as packaged in Fedora 24.

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

[dolphin] [Bug 364117] New: Crash when drag/drop a file to network location

[Jeffrey G Thomas via KDE Bugzilla]

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

Bug ID: 364117
   Summary: Crash when drag/drop a file to network location
   Product: dolphin
   Version: 15.08.3
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: eljefedel...@gmail.com

Application: dolphin (15.08.3)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
Trying to copy a 1.1GB file to an sftp:// location (KIO connection in Dolphin)
and the crash happened.  In the meantime, that Dolphin's Terminal was
performing a tar operation.

The crash can be reproduced sometimes.

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

Thread 3 (Thread 0x7f66a1fbc700 (LWP 7928)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f66a5f3a693 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f66a5f39db7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f66babb1454 in start_thread (arg=0x7f66a1fbc700) at
pthread_create.c:334
#4  0x7f66c32eae5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f66a1468700 (LWP 7929)):
#0  0x7f66c32e1dcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f66ba02439c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f66ba0244ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f66be2f9a5b in QEventDispatcherGlib::processEvents
(this=0x7f669c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f66be2a0d6a in QEventLoop::exec (this=this@entry=0x7f66a1467c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f66be0bd854 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f66be0c27fe in QThreadPrivate::start (arg=0x1710ca0) at
thread/qthread_unix.cpp:331
#7  0x7f66babb1454 in start_thread (arg=0x7f66a1468700) at
pthread_create.c:334
#8  0x7f66c32eae5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f66af1dd940 (LWP 7926)):
[KCrash Handler]
#6  0x7f66b6b82193 in mdb_dbi_open () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#7  0x7f66bb422d97 in Baloo::PostingDB::open(MDB_txn*) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x7f66bb416519 in Baloo::Database::open(Baloo::Database::OpenMode) ()
from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x7f66c133f306 in Baloo::File::load() () from
/usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#10 0x7f66c18dbcb6 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5BalooWidgets.so.5
#11 0x7f66be2d2e61 in QObject::event (this=0x2233f80, e=) at
kernel/qobject.cpp:1239
#12 0x7f66beda5ffc in QApplicationPrivate::notify_helper
(this=this@entry=0x14933e0, receiver=receiver@entry=0x2233f80,
e=e@entry=0x1fdc270) at kernel/qapplication.cpp:3716
#13 0x7f66bedab4b6 in QApplication::notify (this=0x7ffd3a8d0190,
receiver=0x2233f80, e=0x1fdc270) at kernel/qapplication.cpp:3499
#14 0x7f66be2a35ab in QCoreApplication::notifyInternal
(this=0x7ffd3a8d0190, receiver=0x2233f80, event=event@entry=0x1fdc270) at
kernel/qcoreapplication.cpp:965
#15 0x7f66be2a59a6 in QCoreApplication::sendEvent (event=0x1fdc270,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x1491870) at
kernel/qcoreapplication.cpp:1593
#17 0x7f66be2a5e88 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1451
#18 0x7f66be2f9633 in postEventSourceDispatch (s=0x14f4bc0) at
kernel/qeventdispatcher_glib.cpp:271
#19 0x7f66ba0241a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f66ba024400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f66ba0244ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f66be2f9a3f in QEventDispatcherGlib::processEvents (this=0x14eb900,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#23 0x7f66be2a0d6a in QEventLoop::exec (this=this@entry=0x19a64a0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#24 0x7f66be7e96c2 in QBasicDrag::drag (this=0x14dfdb0, o=)
at kernel/qsimpledrag.cpp:177
#25 0x7f66be802189 in QDragManager::drag (this=0x1e3fab0,
o=o@entry=0x2014a90) at kernel/qdnd.cpp:135
#26 0x7f66be801567 in QDrag::exec 

[digikam] [Bug 364116] Uninstaller doesn't remove C:\Program Files (x86)\digiKam

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
yes confirmed. digiKam.exe still in memory after to close the session of
application. I suspect that a DBUS problem under Windows.

In fact if you will DBUS (digiKam do not use it in fact currently for Windows),
and after you close digiKam.exe, the application is closed properly.

DBUS is used by digiKam for Mysql DB interface. Currently, Mysql/MAriaBD are
not yet available under MXE for cross-compiling with MinGW.

I'm looking if a new compilation option to disable DBUS support can be done
safety.

Gilles Caulier

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

[digikam] [Bug 364116] New: Uninstaller doesn't remove C:\Program Files (x86)\digiKam

[via KDE Bugzilla]

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

Bug ID: 364116
   Summary: Uninstaller doesn't remove C:\Program Files
(x86)\digiKam
   Product: digikam
   Version: 5.0.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: setup
  Assignee: digikam-de...@kde.org
  Reporter: matburnham+kdeb...@gmail.com

Twice now with a couple of beta7 installers, the uninstaller hasn't removed the
C:\Program Files (x86)\digiKam directory. Removing it manually is a bit of a
faff as stuff is still running so WIndows won't allow it. I think digikam.exe
and dbus-daemon.exe are both still running.

I've done nothing special to run the (un)installer as admin. I *think* it
brought up the UAC prompt, but I really can't remember.

Reproducible: Always

Steps to Reproduce:
1. Install beta-7.
2. Uninstall beta-7 using a newer installer.

Actual Results:  
3. Try to continue the install after the uninstall and get 'Error opening file
for writing'

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

[kmail2] [Bug 233069] Kmail loses mail bodies

[Martin Steigerwald via KDE Bugzilla]

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

--- Comment #16 from Martin Steigerwald  ---
Sad, but understandable Boudewijn. I had data losses myself, but the last has
been a very long time ago. I think Akonadi got much more stable related to data
safety, but I can understand you.

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

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Yuri via KDE Bugzilla]

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

--- Comment #43 from Yuri  ---
(In reply to Carsten Gräser from comment #42)
> Yuri, this is not correct. Okular can in principle save the data to the pdf.
> But the interplay of this with saving to and loading from .kde/... is not
> very intuitive.

What does it mean "can in principle"? Is the code saving it to the pdf there or
not there? If it is there, can you send the link (line numbers)?

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

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

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

--- Comment #47 from Pali Rohár  ---
On Wednesday 18 May 2016 09:27:25 Ben Cooksley via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=359603
> 
> --- Comment #46 from Ben Cooksley  ---
> This will be my very final correspondence on this issue.
> 
> In regards to email standards, they're not relevant here. What
> commonly used email providers dictate as being required is relevant,
> as what people care about is getting their email in a readable form.
> The RFCs and other material are just a guideline towards that. Oh,
> and DMARC is an RFC, so it's part of the standards. GMail, followed
> by Yahoo are our top destinations for email delivery. So they set
> the rules.

Your words basically means: "I do not care about anybody except Gmail & 
Yahoo providers which set and dictate rules how emails could work". 
Sorry, but in open community and for free & open source projects, I 
cannot accept this statement.

If you are doing such thing, please explicitly write to KDE webpages:
We are not supporting email service and appreciate standards anymore. We 
only supports Gmail & Yahoo services and due to our limits we ignore all 
requests for supporting standard email service. Our users are restricted 
to use Gmail or Yahoo otherwise our service will not work correctly.

If you are *not* doing such thing, you cannot mark this report as 
INVALID. As INVALID means "we do not care about non Gmail users".

So I really would like to know what is current state. I really cannot 
accept community which declare themselves as free & open source 
software, but follow big corporations which "set the rules".

> In regards to the solutions you proposed, they either:
> a) Impacted upon the reliability of Bugzilla service; or
> b) Significantly increased the maintenance burden Sysadmin would face
> to maintain Bugzilla. And we have enough maintenance workload as it
> stands. Plus we'd have to author the change in the first place, and
> Bugzilla is written in Perl.

If you need I can help with Perl, this is something which I know.

I proposed solutions, because nobody else proposed anything. And I 
wanted to see this bug fixed. So I did everything which I could.

> And in case you are wondering - every other bug tracking system out
> there, including vanilla Bugzilla, follows the behaviour we follow
> now. Our previous behaviour was a hack, added in many, many years
> ago, and which is not able to be continued with, due to the issues
> noted previously.
> 
> This issue is far from being ignored. It has been looked into and
> discussed here for a very long time. The behaviour the system now
> follows is known, and is the desired and correct behaviour.
> 
> I have no idea why your workflow requires / demands filtering based
> on commenter/reporter email address (in which case, may I suggest
> headers in the email which Bugzilla includes), but it is no longer
> something we can accommodate using the From field in an email.

Reason is quite obvious. Every and I'm sure every one email client show 
3 important headers to user: From, To and Subject. Lot of email clients 
(and those web based too) have some index view, where is list of emails, 
e.g. clickable one email per line and on that line show again only 
From/To and Subject (sometimes also Date). And based on this information 
user open/select email.

Email headers From and To are there for 20+ years and they are not going 
to be changed. All existing email software is based on them and once you 
start rewriting them or mangling, you just broke email support...

And I'm using this information in From, To and Subject headers to 
quickly filter emails and mark what is important and what not. Also for 
searching for comments from specific people, etc...



And problem via total nonsense in From header

"From: via KDE Bugzilla "

is still there and did not hear anybody how and when to fix it. In 
comment 10 you wrote that this is when somebody does entered name at 
all. Should I interpret your last comment, that you are ignoring also 
this problem?

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

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Carsten Gräser via KDE Bugzilla]

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

--- Comment #42 from Carsten Gräser  ---
Yuri, this is not correct. Okular can in principle save the data to the pdf.
But the interplay of this with saving to and loading from .kde/... is not very
intuitive.

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

[Oxygen] [Bug 364115] A seam is present between window decoration and window background

[Ruslan Kabatsayev via KDE Bugzilla]

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

--- Comment #2 from Ruslan Kabatsayev  ---
Created attachment 99418
  --> https://bugs.kde.org/attachment.cgi?id=99418=edit
Screenshot with increased brightness and contrast

This screenshot has increased brightness and contrast to easier see what to
look for when debugging.

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

[Oxygen] [Bug 364115] A seam is present between window decoration and window background

[Ruslan Kabatsayev via KDE Bugzilla]

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

--- Comment #1 from Ruslan Kabatsayev  ---
Created attachment 99417
  --> https://bugs.kde.org/attachment.cgi?id=99417=edit
Screenshot

This is an unmodified screenshot of the problem.

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

[Oxygen] [Bug 364115] New: A seam is present between window decoration and window background

[Ruslan Kabatsayev via KDE Bugzilla]

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

Bug ID: 364115
   Summary: A seam is present between window decoration and window
background
   Product: Oxygen
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: style
  Assignee: hugo.pereira.da.co...@gmail.com
  Reporter: b7.10110...@gmail.com

I'll add some screenshots. Basically, if you set a dark color scheme, e.g.
Obsidian Coast, you'll notice a dark line just above the bottom line of the
topmost stripe of single color (neglecting the radial gradient). You can see it
more easily if you increase brightness and contrast of a screenshot.

Reproducible: Always

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

[kmail2] [Bug 297858] KMail crashes when moving a folder

[Martin Steigerwald via KDE Bugzilla]

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

Martin Steigerwald  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED
 CC||mar...@lichtvoll.de

--- Comment #10 from Martin Steigerwald  ---
Thank you for your report. Although I still see this happening within a maildir
resource with KMail and Akonadi 16.04, I am closing this report as KDEPIM SC 4
and Akonadi 1 is unmaintained. So this bug report contains outdated backtraces.
I am intending to report the bug for KMail and Akonadi 16.04, but feel free to
beat me to it and note it here. Also please note whether you are moving folders
within a Maildir resource or within an IMAP account. Thanks, Martin

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

[kmail2] [Bug 233069] Kmail loses mail bodies

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #15 from Boudewijn Rempt  ---
Well, I stopped using KMail because of this and similar issues -- like endless
waits and the "mime conflict resolution diff" dialog -- about a year or so ago.
And given how hard it's to migrate between mail clients if you need a few
hundred filter rules and get thousands of mails a day, I'm not even
contemplating going back and trying kmail2 again.I just cannot afford risking
my mail again just to verify whether this bug is still present. It's too
valuable for little experiments like that.

Whether or not this bug might be magically fixed because there's now a new
version and the old one isn't maintained anymore, the ship has sailed: I will
never, ever, try kmail and akonadi again. I'm using _pine_ now.

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

[valgrind] [Bug 364058] array overruns are not detected

[Philippe Waroquiers via KDE Bugzilla]

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

--- Comment #6 from Philippe Waroquiers  ---
(In reply to Sergey Meirovich from comment #5)
> Sorry. I indeed missed that. But why next also doesn't trigger any error
> message?
> 
> -bash-4.1$ cat t.c 
> int main(int c, char **o)
> {
>   int stack[2]; 
>   stack[0] = c;
>   stack[1] = c++;
>   stack[2] = c++;
>   return stack[2];
> }
exp-sgcheck associates (for each function call) each instruction to the first
array accessed
by this instruction. It then checks that (during the same function call)  this
instruction continues to access the same array (and in the array bounds).
So, basically, this means that exp-sgcheck will only detect array over or
under-run in
loops. It will never detect an over/under-run on instructions executed only
once
(either because they are not in a loop, or because the loop is executed once).
All this limitations derived from the fact that exp-sgcheck works at binary
level. It has
to discover which array is accessed by an instruction 'at run time'.

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

[kmail2] [Bug 233069] Kmail loses mail bodies

[Martin Steigerwald via KDE Bugzilla]

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

Martin Steigerwald  changed:

   What|Removed |Added

 CC||mar...@lichtvoll.de
 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #14 from Martin Steigerwald  ---
Thank you for your report.Does this bug still happen to you with KMail and
Akonadi 16.04? If so, please reopen as a new bug as KDEPIM SC 4 and Akonadi 1
is unmaintained. Also always use one bug report for one problem. Thank you,
Martin

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

[kdelibs] [Bug 364113] klauncher: lots of icons missing after update

[Hans-J . Ullrich via KDE Bugzilla]

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

--- Comment #1 from Hans-J. Ullrich  ---
Created attachment 99416
  --> https://bugs.kde.org/attachment.cgi?id=99416=edit
kde video made with recordmydesktop

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

[Akonadi] [Bug 364114] New: moving a folder within one maildir resource is extremely slow and inefficient

[Martin Steigerwald via KDE Bugzilla]

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

Bug ID: 364114
   Summary: moving a folder within one maildir resource is
extremely slow and inefficient
   Product: Akonadi
   Version: 16.04
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-b...@kde.org
  Reporter: mar...@lichtvoll.de

Today I dared moving .Computer.directory/mesa-dev-ml with about 86730 mails to
.Linux.directory by drag and drop within KMail. After the move operation
completed kmail crashed.

The operation took at least one and a half hour on a ThinkPad T520 with Intel
Sandybridge i5-2520m dual core CPU and dual SSD BTRFS RAID 1 and 16 GiB of RAM!

Reproducible: Always

Steps to Reproduce:
1. Have a large maildir folder inside another folder.
2. Move it to a different folder


Actual Results:  
1. Akonadi first moves all mails into database or file_db_data depending on
threshold. This process is extremely slow at a rate of about 2-4 mails
in half an hour. During that the mysqld database process frequently uses about
90-99% of one logical core. This process takes about 1,5 hours for 86000 mails.

martin@merkaba:~/.local/share/akonadi/file_db_data> date ; find -type f | wc -l
Mi 8. Jun 20:41:59 CEST 2016
30339
martin@merkaba:~/.local/share/akonadi/file_db_data> date ; find -type f | wc -l
Mi 8. Jun 20:42:07 CEST 2016
30473
martin@merkaba:~/.local/share/akonadi/file_db_data> date ; find -type f | wc -l
Mi 8. Jun 20:42:16 CEST 2016
30494
martin@merkaba:~/.local/share/akonadi/file_db_data> date ; find -type f | wc -l
Mi 8. Jun 20:42:32 CEST 2016
30708
martin@merkaba:~/.local/share/akonadi/file_db_data> date ; find -type f | wc -l
Mi 8. Jun 20:42:53 CEST 2016
31131
martin@merkaba:~/.local/share/akonadi/file_db_data> date ; find -type f | wc -l
Mi 8. Jun 20:45:58 CEST 2016
34562
martin@merkaba:~/.local/share/akonadi/file_db_data> date ; find -type f | wc -l
Mi 8. Jun 21:28:28 CEST 2016
67480

martin@merkaba:~/.local/share/akonadi/file_db_data> cd ..
martin@merkaba:~/.local/share/akonadi> date ; find file_db_data -type f | wc -l
; du -sh db_data 
Mi 8. Jun 21:28:58 CEST 2016
68099
4,9Gdb_data
martin@merkaba:~/.local/share/akonadi> date ; find file_db_data -type f | wc -l
; du -sh db_data
Mi 8. Jun 21:33:16 CEST 2016
74039
5,0Gdb_data
martin@merkaba:~/.local/share/akonadi> date ; find file_db_data -type f | wc -l
; du -sh db_data
Mi 8. Jun 21:45:13 CEST 2016
95529
5,1Gdb_data


2. Then after moving completed it copies the mails to the destination folder.
This is quite quick. The mains still remain in file_db_data:

martin@merkaba:~/.local/share/akonadi> date ; find file_db_data -type f | wc -l
; du -sh db_data
Mi 8. Jun 21:53:26 CEST 2016
98737
5,1Gdb_data

3. KMail crashes.

During the whole operation KMail does not respond to user input. It is
completely blocked.

Expected Results:  
When moving a folder within a local maildir resource, Akonadi does the
following:

1. Rename the folder.

2. Store the folder renaming within the database.

3. KMail remains responsive at all times.

In other words: The operation is completed within 10 seconds no matter how many
mails are in the folder. Specifically Akonadi does not move each mail one time
and then copying it.

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

[kdelibs] [Bug 364113] New: klauncher: lots of icons missing after update

[Hans-J . Ullrich via KDE Bugzilla]

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

Bug ID: 364113
   Summary: klauncher: lots of icons missing after update
   Product: kdelibs
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: klauncher
  Assignee: kdelibs-b...@kde.org
  Reporter: hans.ullr...@loop.de

Dear maintainers,

after upgrade in debian/testing, a lot of icons are missing in klauncher.
However, I do not know, if klauncher is the right tool responsible for this
bug. 

However, you should know, that kio-extras and kio-extras-data are not installed
due to a dependency problem with kactivities.

I added a short video, which shows the missing icons. Strange: Not all icons
are missing, but many. Sadly I found no reason, why some are missing and some
are shown. 

Please feel free to ask for more information. 

Thanks for your help!

Best

Hans

Reproducible: Always

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

[valgrind] [Bug 364058] array overruns are not detected

[Sergey Meirovich via KDE Bugzilla]

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

--- Comment #5 from Sergey Meirovich  ---
Sorry. I indeed missed that. But why next also doesn't trigger any error
message?

-bash-4.1$ cat t.c 
int main(int c, char **o)
{
  int stack[2]; 
  stack[0] = c;
  stack[1] = c++;
  stack[2] = c++;
  return stack[2];
}
-bash-4.1$ gcc -O0 -ggdb -o  t t.c 
-bash-4.1$  /sw/valgrind/valgrind-3.11.0/bin/valgrind --tool=exp-sgcheck  ./t s
f a aa 
==36489== exp-sgcheck, a stack and global array overrun detector
==36489== NOTE: This is an Experimental-Class Valgrind Tool
==36489== Copyright (C) 2003-2015, and GNU GPL'd, by OpenWorks Ltd et al.
==36489== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==36489== Command: ./t s f a aa
==36489== 
==36489== 
==36489== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
-bash-4.1$ echo $?
6
-bash-4.1$ 

Am I still missing something?

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

[krita] [Bug 364059] Cursor/Pen Pressure Issue

[Franklyn via KDE Bugzilla]

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

--- Comment #3 from Franklyn  ---
Managed to get the "accident" back.

With UC-Logic, you have to uninstall any other legacy UC-Logic drivers for
the graphic tablet. The latest drivers don't override the legacy drivers.

Now, the pen pressure is working as before.

Just thought I let you guys know just in case anyone else may have issues
with UC-Logic graphic tablets.

Thanks.

On Tue, Jun 7, 2016 at 10:14 AM, Boudewijn Rempt via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=364059
>
> Boudewijn Rempt  changed:
>
>What|Removed |Added
>
> 
>  CC||b...@valdyas.org
>
> --- Comment #1 from Boudewijn Rempt  ---
> Since we do not have the hardware, we cannot test Krita with it. If your
> tablet
> works, it's purely by accident, because the people who coded the driver
> didn't
> mess up too much. Have you tried the test builds from this blog:
> https://krita.org/item/anatomy-of-a-bug-fix/ ? It might be that those are
> better.
>
> By the way, _which_ exact krita 2.9 version did you test with and do you
> have
> that version still installed and does it still work?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[Akonadi] [Bug 290393] moving the contents of a mail folder is extremely slow

[Martin Steigerwald via KDE Bugzilla]

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

Martin Steigerwald  changed:

   What|Removed |Added

 CC||mar...@lichtvoll.de

--- Comment #4 from Martin Steigerwald  ---
Bruno, thank you for your report. Does it still happen for you with KDEPIM +
Akonadi 16.04.

I bet it may still happen as I find moving folder on maildir *extremely*
inefficient with that version still, but please confirm. Otherwise I intend to
close this bug report, as KDEPIM 4 and Akonadi 1 is unmaintained. Thanks,
Martin

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

[kaffeine] [Bug 364041] video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #5 from Mauro Carvalho Chehab  ---
(In reply to rens from comment #3)
> Created attachment 99413 [details]
> attachment-21897-0.html
> 
> Hello,
> 
> disabling hardware accel : this would be an option of kaffeine, I guess ?

Qt5 does hardware accel, via DRI and OpenGL, but video playback is actually
done via libVLC, since version 1.3.x, with has its own video accel logic, and
some options that affects it. Unfortunately, the libVLC options depends on its
version, and the function call that starts libVLC (libvlc_new) accepts, as
parameter, a list of arguments. So, there's not much that we can do at the
Kaffeine side, other than exposing somehow a way for the user to specify what
arguments should be passed to the library. You can see the arguments libVLC
accept via:
vlc --help
and:
vlc --help --advanced

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

[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

[Craig via KDE Bugzilla]

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

--- Comment #9 from Craig  ---
Yea on mine as well,
(Arch)
/usr/lib/qt/plugins/messageviewer_bodypartformatter_text_calendar.so

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

[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

[via KDE Bugzilla]

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

hos...@hotmail.de changed:

   What|Removed |Added

 CC||hos...@hotmail.de

--- Comment #112 from hos...@hotmail.de ---
Hello, I also can confirm the behavior described by Metko. Any update on this
issue? Anything I can provide from my side? 
Thanks!

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

[valgrind] [Bug 364058] array overruns are not detected

[Philippe Waroquiers via KDE Bugzilla]

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

Philippe Waroquiers  changed:

   What|Removed |Added

 CC||philippe.waroquiers@skynet.
   ||be
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #4 from Philippe Waroquiers  ---
Please (re-)read the user manual about sgcheck,
in particular the sections
   11.3. How SGCheck Works
and 11.5. Limitations

That should (clearly?) explain why nothing is reported for your example
(false negative).

If the manual is not clear, please re-open a bug, e.g. suggesting what to add
to make
it more clear.

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

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #2 from Andreas Cord-Landwehr  ---
Hi Sebas, restarting kded5 makes no change when I am in the state after
resuming on one monitor does not get a signal.

Output of kscreen-console bug:

cordlandwehr@weatherwax:/tmp$ kscreen-console bug
kscreen-console(30373)/(default) main: START: Requesting Config
kscreen-console(30373)/(kscreen) KScreen::BackendManager::startBackend:
starting external backend launcher for ""
kscreen-console(30373)/(default) configReceived: Received config. Took 47
milliseconds

xrandr --verbose==
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (0x4d) normal (normal left inverted right
x axis y axis) 309mm x 173mm
Identifier: 0x43
Timestamp:  131887559
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
BACKLIGHT: 426 
range: (0, 851)
Backlight: 426 
range: (0, 851)
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4d) 141.000MHz -HSync -VSync *current +preferred 
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz 
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz  
  1920x1080 (0xee) 138.500MHz +HSync -VSync 
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz 
v: height 1080 start 1083 end 1088 total    clock  59.93Hz  
  1680x1050 (0xef) 146.250MHz -HSync +VSync 
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz 
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz  
  1680x1050 (0xf0) 119.000MHz +HSync -VSync 
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz 
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz  
  1600x1024 (0xf1) 103.125MHz +HSync +VSync 
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz 
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz  
  1400x1050 (0xf2) 122.000MHz +HSync +VSync 
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz 
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz
  1600x900 (0xf3) 118.997MHz -HSync +VSync
h: width  1600 start 1696 end 1864 total 2128 skew0 clock  55.92KHz
v: height  900 start  901 end  904 total  932   clock  60.00Hz
  1280x1024 (0xf4) 108.000MHz +HSync +VSync
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
  1440x900 (0xf5) 106.500MHz -HSync +VSync
h: width  1440 start 1520 end 1672 total 1904 skew0 clock  55.93KHz
v: height  900 start  903 end  909 total  934   clock  59.89Hz
  1280x960 (0xf6) 108.000MHz +HSync +VSync
h: width  1280 start 1376 end 1488 total 1800 skew0 clock  60.00KHz
v: height  960 start  961 end  964 total 1000   clock  60.00Hz
  1368x768 (0xf7) 85.860MHz -HSync +VSync
h: width  1368 start 1440 end 1584 total 1800 skew0 clock  47.70KHz
v: height  768 start  769 end  772 total  795   clock  60.00Hz
  1360x768 (0xf8) 84.750MHz -HSync +VSync
h: width  1360 start 1432 end 1568 total 1776 skew0 clock  47.72KHz
v: height  768 start  771 end  781 total  798   clock  59.80Hz
  1360x768 (0xf9) 72.000MHz +HSync -VSync
h: width  1360 start 1408 end 1440 total 1520 skew0 clock  47.37KHz
v: height  768 start  771 end  781 total  790   clock  59.96Hz
  1152x864 (0xfa) 81.620MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock  53.70KHz
v: height  864 start 

[Baloo] [Bug 364112] New: Crashes when I move a desktop icon or work with a pdf. file

[Matt via KDE Bugzilla]

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

Bug ID: 364112
   Summary: Crashes when I move a desktop icon or work with a pdf.
file
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: mgkr...@hotmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: I was using TeXmaker's built
in pdf viewer. 
It sometimes crashes when I try moving an icon on the desktop (usually at start
up or after my laptop wakes up) or sometimes when working with a pdf file. It
started a few weeks ago but has recently been happening more frequently.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7faa5a3a28c0 (LWP 1516))]

Thread 2 (Thread 0x7fa90f2e8700 (LWP 1840)):
#0  0x7faa584a8e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7faa5567931c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7faa5567942c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7faa590dea9b in QEventDispatcherGlib::processEvents
(this=0x7fa9080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7faa59085dea in QEventLoop::exec (this=this@entry=0x7fa90f2e7bc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00420cd8 in Baloo::FileContentIndexer::run (this=0x16afe80) at
../../../src/file/filecontentindexer.cpp:71
#6  0x7faa58ea4343 in QThreadPoolThread::run (this=0x1763e60) at
thread/qthreadpool.cpp:93
#7  0x7faa58ea784e in QThreadPrivate::start (arg=0x1763e60) at
thread/qthread_unix.cpp:331
#8  0x7faa57b0b6fa in start_thread (arg=0x7fa90f2e8700) at
pthread_create.c:333
#9  0x7faa584b4b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7faa5a3a28c0 (LWP 1516)):
[KCrash Handler]
#6  mdb_page_search_root (mc=mc@entry=0x7ffce33c99e0,
key=key@entry=0x7ffce33c9db0, flags=flags@entry=0) at mdb.c:5271
#7  0x7faa56bdf0c8 in mdb_page_search (mc=mc@entry=0x7ffce33c99e0,
key=key@entry=0x7ffce33c9db0, flags=flags@entry=0) at mdb.c:5436
#8  0x7faa56bdf7a5 in mdb_cursor_set (mc=mc@entry=0x7ffce33c99e0,
key=key@entry=0x7ffce33c9db0, data=data@entry=0x7ffce33c9dc0,
op=op@entry=MDB_SET, exactp=exactp@entry=0x7ffce33c99dc) at mdb.c:5893
#9  0x7faa56bdfe3c in mdb_get (txn=, dbi=,
key=key@entry=0x7ffce33c9db0, data=data@entry=0x7ffce33c9dc0) at mdb.c:5565
#10 0x7faa5957bf78 in Baloo::PositionDB::get
(this=this@entry=0x7ffce33c9e90, term=...) at
../../../src/engine/positiondb.cpp:92
#11 0x7faa5958e9a4 in Baloo::WriteTransaction::commit (this=) at ../../../src/engine/writetransaction.cpp:299
#12 0x7faa59586032 in Baloo::Transaction::commit
(this=this@entry=0x7ffce33c9f20) at ../../../src/engine/transaction.cpp:262
#13 0x0042a02b in Baloo::MetadataMover::moveFileMetadata
(this=0x16c2040, from=..., to=...) at ../../../src/file/metadatamover.cpp:58
#14 0x7faa590b6e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffce33ca080,
r=0x7ffce33ca740, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#15 QMetaObject::activate (sender=sender@entry=0x16c7540,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffce33ca080) at kernel/qobject.cpp:3698
#16 0x7faa590b77d7 in QMetaObject::activate (sender=sender@entry=0x16c7540,
m=m@entry=0x644cc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffce33ca080)
at kernel/qobject.cpp:3578
#17 0x0042aaba in KInotify::moved (this=this@entry=0x16c7540, _t1=...,
_t2=...) at ./moc_kinotify.cpp:330
#18 0x0042cbff in KInotify::slotEvent (this=,
socket=) at ../../../src/file/kinotify.cpp:421
#19 0x7faa590b6e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffce33ca310,
r=0x16c7540, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#20 QMetaObject::activate (sender=sender@entry=0x16b8d20,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffce33ca310) at kernel/qobject.cpp:3698
#21 0x7faa590b77d7 in QMetaObject::activate (sender=sender@entry=0x16b8d20,
m=m@entry=0x7faa592d1780 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffce33ca310)
at kernel/qobject.cpp:3578
#22 0x7faa5913651e in QSocketNotifier::activated
(this=this@entry=0x16b8d20, _t1=13) at .moc/moc_qsocketnotifier.cpp:134
#23 0x7faa590c347b in 

[krita] [Bug 357708] krita fails to build against qt built with OpenGLES support

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #3 from Boudewijn Rempt  ---
Well, it wasn't supported. Did it work? You surprise me, it wasn't supposed to.
Unless you provide sensible patches that make it work and clearly intend to
maintain them, it won't be supported until we start thinking of porting to
Android.

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

[kaffeine] [Bug 364041] video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer

[rens via KDE Bugzilla]

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

--- Comment #3 from rens  ---
Hello,

disabling hardware accel : this would be an option of kaffeine, I guess ?

best regards,

rens

On 06/08/16 19:05, Mauro Carvalho Chehab via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=364041
>
> --- Comment #2 from Mauro Carvalho Chehab  ---
> By default, libVLC (present on Kaffeine versions 1.3.x and 2.0.x) will try to
> use the DRI acceleration at the local machine. This doesn't work when the
> display windows is on another machine. There are a number of libVLC options
> that could help to disable such behavior, like --no-xlib and --vout.
>
> I just added a patch adding support for it. Maybe with that you could find a
> setup that would work with vncviewer.
>

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

[gwenview] [Bug 359492] Gwenview crash when exiting after watching GIF image

[Mario Junior via KDE Bugzilla]

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

Mario Junior  changed:

   What|Removed |Added

 CC||mariojunio...@gmail.com

--- Comment #3 from Mario Junior  ---
Same problem here.

Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9990ae18c0 (LWP 24403))]

Thread 2 (Thread 0x7f9975548700 (LWP 24406)):
#0  0x7f998b3e268d in poll () from /usr/lib/libc.so.6
#1  0x7f99850fcfd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f99850fd0ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f998bd0374b in QEventDispatcherGlib::processEvents
(this=0x7f99680008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f998bcab4ca in QEventLoop::exec (this=this@entry=0x7f9975547cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f998bad22f3 in QThread::exec (this=this@entry=0x7f998b302d20
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#6  0x7f998b08fa65 in QDBusConnectionManager::run (this=0x7f998b302d20
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#7  0x7f998bad71d8 in QThreadPrivate::start (arg=0x7f998b302d20 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#8  0x7f998561b474 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f998b3eb69d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f9990ae18c0 (LWP 24403)):
[KCrash Handler]
#5  0x7f998c256bd2 in QImageReaderPrivate::~QImageReaderPrivate
(this=0x4e73e80, __in_chrg=) at image/qimagereader.cpp:572
#6  0x7f998c257001 in QImageReader::~QImageReader (this=,
__in_chrg=) at image/qimagereader.cpp:684
#7  0x7f998c27524c in QMovie::~QMovie (this=0x8a85178, __in_chrg=) at image/qmovie.cpp:619
#8  0x7f999026d759 in ?? () from /usr/lib/libgwenviewlib.so.5
#9  0x7f999026f96f in Gwenview::Document::~Document() () from
/usr/lib/libgwenviewlib.so.5
#10 0x7f999026faf9 in Gwenview::Document::~Document() () from
/usr/lib/libgwenviewlib.so.5
#11 0x7f9990272e5f in Gwenview::DocumentFactory::~DocumentFactory() () from
/usr/lib/libgwenviewlib.so.5
#12 0x7f998b339be8 in __run_exit_handlers () from /usr/lib/libc.so.6
#13 0x7f998b339c35 in exit () from /usr/lib/libc.so.6
#14 0x7f998b324748 in __libc_start_main () from /usr/lib/libc.so.6
#15 0x00432029 in _start ()

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

[kdenlive] [Bug 361086] git master 2016-03-28 Application crash when applying layout

[via KDE Bugzilla]

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

--- Comment #17 from m...@jaytea.org ---
I'm sorry to report, that on my desktop PC, it still crashes in the same
method. I also made the observation, that on my work notebook with optimus, it
works as expected.
The backtrace:

#0  0x7fffeb974295 in raise () from /usr/lib/libc.so.6
#1  0x7fffeb9756da in abort () from /usr/lib/libc.so.6
#2  0x7fffeb96d297 in __assert_fail_base () from /usr/lib/libc.so.6
#3  0x7fffeb96d342 in __assert_fail () from /usr/lib/libc.so.6
#4  0x7fffab5e80e7 in movit::EffectChain::render_to_fbo
(this=this@entry=0x7ffed9fcbbe0, dest_fbo=2, width=width@entry=1920,
height=height@entry=1080) at effect_chain.cpp:1778
#5  0x7fffab85157f in GlslManager::render_frame_texture (this=0x1f42d90,
chain=0x7ffed9fcbbe0, frame=0x7fff2c12ec80, width=1920, height=1080,
image=0x7fff445c3d98) at filter_glsl_manager.cpp:404
#6  0x7fffab85447e in convert_image (frame=0x7fff2c12ec80,
image=0x7fff445c3d98, format=0x2da360c, output_format=mlt_image_glsl_texture)
at filter_movit_convert.cpp:573
#7  0x766894b8 in mlt_frame_get_image (self=self@entry=0x7fff2c12ec80,
buffer=buffer@entry=0x7fff445c3d98, format=format@entry=0x2da360c,
width=width@entry=0x7fff445c3d84, height=height@entry=0x7fff445c3d88,
writable=writable@entry=0) at mlt_frame.c:591
#8  0x7669ea59 in producer_get_image (self=self@entry=0x7ffed2fe0620,
buffer=buffer@entry=0x7fff445c3d98, format=format@entry=0x2da360c,
width=width@entry=0x7fff445c3d84, height=height@entry=0x7fff445c3d88,
writable=writable@entry=0) at mlt_tractor.c:370
#9  0x76689467 in mlt_frame_get_image (self=self@entry=0x7ffed2fe0620,
buffer=buffer@entry=0x7fff445c3d98, format=format@entry=0x2da360c,
width=width@entry=0x7fff445c3d84, height=height@entry=0x7fff445c3d88,
writable=writable@entry=0) at mlt_frame.c:585
#10 0x7669c28c in consumer_read_ahead_thread (arg=0x2d99430) at
mlt_consumer.c:825
#11 0x007c5127 in RenderThread::run() ()
#12 0x7fffec62e1d8 in ?? () from /usr/lib/libQt5Core.so.5
#13 0x7fffea1b1474 in start_thread () from /usr/lib/libpthread.so.0
#14 0x7fffeba2869d in clone () from /usr/lib/libc.so.6

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

[telepathy] [Bug 364111] New: Can't configure a Google account for KDE telepathy

[Bernhard Rosenkränzer via KDE Bugzilla]

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

Bug ID: 364111
   Summary: Can't configure a Google account for KDE telepathy
   Product: telepathy
   Version: unspecified
  Platform: OpenMandriva RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: accounts-kcm
  Assignee: kde-telepathy-b...@kde.org
  Reporter: b...@lindev.ch

Trying to set up a Google account results in

There was an error while trying to process the request:
userActionFinished error: 2

before even prompting for any information

Reproducible: Always

Steps to Reproduce:
1. open systemsettings5
2. go to Online Accounts
3. select Create
4. select Google

Actual Results:  
"There was an error while trying to process the request:
userActionFinished error: 2"

Expected Results:  
Can configure a Google account for KTP

Versions of related components:

ktp-common-internals-16.04.1
ktp-approver-16.04.1
ktp-auth-handler-16.04.1
ktp-contact-list-16.04.1
ktp-filetransfer-handler-16.04.1
ktp-kded-module-16.04.1
ktp-send-file-16.04.1
ktp-text-ui-16.04.1
ktp-call-ui-16.04.1
ktp-desktop-applets-16.04.1
ktp-contact-runner-16.04.1
ktp-accounts-kcm-16.04.1

lib64telepathy-glib0-0.24.1
telepathy-filesystem-0.0.1
lib64telepathy-farstream3-0.6.2
lib64telepathy-farstream-gir0.6-0.6.2
lib64telepathy-qt5_0-0.9.6.1
lib64telepathy-qt5-farstream0-0.9.6.1
lib64telepathy-logger-qt0-15.04.0
telepathy-mission-control-5.16.3
telepathy-idle-0.2.0-2
telepathy-sharp-0.13.2
python-telepathy-0.15.19
telepathy-salut-0.8.1
telepathy-haze-0.8.0
telepathy-gabble-0.18.3
telepathy-butterfly-0.5.15
telepathy-sofiasip-0.7.1
lib64telepathy-logger3-0.8.2
telepathy-logger-0.8.2

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

[telepathy] [Bug 364110] New: "It appears that you do not have any accounts configured" even when accounts are configured

[Bernhard Rosenkränzer via KDE Bugzilla]

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

Bug ID: 364110
   Summary: "It appears that you do not have any accounts
configured" even when accounts are configured
   Product: telepathy
   Version: unspecified
  Platform: OpenMandriva RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-telepathy-b...@kde.org
  Reporter: b...@lindev.ch

The IM systray popup says "It appears that you do not have any accounts
configured" even after configuring both a kdetalk and an ICQ account.

There's also no sign of me being logged in on either of those accounts while
plasma telepathy is running. The accounts work fine in kopete.

This is using the 16.04.1 packages (not listed in Bugzilla's version list --
latest there is 15.08.2).

Reproducible: Always

Steps to Reproduce:
1. Install ktp-* 16.04.1
2. Set up accounts
3. Click the systray applet

Actual Results:  
"It appears that you do not have any accounts configured"

Expected Results:  
accounts visible and working

Versions of related components:

ktp-common-internals-16.04.1
ktp-approver-16.04.1
ktp-auth-handler-16.04.1
ktp-contact-list-16.04.1
ktp-filetransfer-handler-16.04.1
ktp-kded-module-16.04.1
ktp-send-file-16.04.1
ktp-text-ui-16.04.1
ktp-call-ui-16.04.1
ktp-desktop-applets-16.04.1
ktp-contact-runner-16.04.1
ktp-accounts-kcm-16.04.1

lib64telepathy-glib0-0.24.1
telepathy-filesystem-0.0.1
lib64telepathy-farstream3-0.6.2
lib64telepathy-farstream-gir0.6-0.6.2
lib64telepathy-qt5_0-0.9.6.1
lib64telepathy-qt5-farstream0-0.9.6.1
lib64telepathy-logger-qt0-15.04.0
telepathy-mission-control-5.16.3
telepathy-idle-0.2.0-2
telepathy-sharp-0.13.2
python-telepathy-0.15.19
telepathy-salut-0.8.1
telepathy-haze-0.8.0
telepathy-gabble-0.18.3
telepathy-butterfly-0.5.15
telepathy-sofiasip-0.7.1
lib64telepathy-logger3-0.8.2
telepathy-logger-0.8.2

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

[kdeconnect] [Bug 363947] kde connect: Could not mount device.

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[dolphin] [Bug 364109] New: Quick search in view don't cooperate with shourtcuts.

[Sylwester via KDE Bugzilla]

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

Bug ID: 364109
   Summary: Quick search in view don't cooperate with shourtcuts.
   Product: dolphin
   Version: 15.12.3
  Platform: Archlinux Packages
   URL: http://i.imgur.com/8nk66ir.png
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: sylwesterrap...@outlook.com

I go to my $HOME directory where I have folders.
I can't quick find folder named "Pobrane"  if I use shortcut "P,O,D" [from
polish word podgląd (preview)] (see image). By quick find I mean I press P and
I have highlighted folder with started by "P". If i will press O i will have
highlighted folder with started by O.
In my case it works with other names so I can quick find any folder with start
[^pg]* (I use another shortcut "g,r,u,p" from polish word (groups) for changing
view.) 


Reproducible: Always

Steps to Reproduce:
1.Add shortcut in dolphin "p,o,d" for preview
2.create new folder "pobrane" (downloaded in polish language)
3. tap pob and you will see that you can't find folder named pobrane
3b press p and you still can't highlight folder. 

Actual Results:  
No highlight, changing (no)preview works.

Expected Results:  
If I press P,O,D i would like to have highlighted folder started by pod and in
the same time changed preview.

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

[dolphin] [Bug 364108] New: dolphin segfaulted while deleting files

[Eugene via KDE Bugzilla]

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

Bug ID: 364108
   Summary: dolphin segfaulted while deleting files
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ken20...@ukr.net

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Frameworks Version: 5.22.0
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Just deleting files from USB flash drive when crash happened.

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

Thread 4 (Thread 0x7f83a2f30700 (LWP 7172)):
#0  0x7f83b85fee8d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f83acd63c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f83acd658d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f83a5282629 in QXcbEventReader::run (this=0x132f6f0) at
qxcbconnection.cpp:1253
#4  0x7f83b31b584e in QThreadPrivate::start (arg=0x132f6f0) at
thread/qthread_unix.cpp:331
#5  0x7f83af9576fa in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7f83b860ab5d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f83984af700 (LWP 7173)):
#0  0x7f83af95d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f839b97b213 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f839b97a937 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f83af9576fa in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f83b860ab5d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f8394689700 (LWP 7174)):
#0  0x7f83b85fee8d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f83aedcc31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f83aedcc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f83b33eca9b in QEventDispatcherGlib::processEvents
(this=0x7f838c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f83b3393dea in QEventLoop::exec (this=this@entry=0x7f8394688d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f83b31b08a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f83b31b584e in QThreadPrivate::start (arg=0x186fed0) at
thread/qthread_unix.cpp:331
#7  0x7f83af9576fa in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f83b860ab5d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f83a57b28c0 (LWP 7171)):
[KCrash Handler]
#6  0x7f83b7b0d154 in KNotification::flags() const () from
/usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#7  0x7f83b7b2b377 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#8  0x7f83b7b31a45 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#9  0x7f83b33c4fca in QMetaObject::activate (sender=0x20b4dd0,
signalOffset=, local_signal_index=local_signal_index@entry=6,
argv=argv@entry=0x0) at kernel/qobject.cpp:3713
#10 0x7f83b33c57d7 in QMetaObject::activate (sender=,
m=m@entry=0x7f83b4642700 ,
local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at
kernel/qobject.cpp:3578
#11 0x7f83b44081e3 in Phonon::MediaObject::finished (this=)
at ./moc_mediaobject.cpp:421
#12 0x7f83b440a6ad in Phonon::MediaObject::qt_static_metacall
(_o=, _c=, _id=, _a=) at ./moc_mediaobject.cpp:182
#13 0x7f83b33c5ea1 in QObject::event (this=0x20b4dd0, e=) at
kernel/qobject.cpp:1239
#14 0x7f83b3e9b05c in QApplicationPrivate::notify_helper
(this=this@entry=0x130f3e0, receiver=receiver@entry=0x20b4dd0,
e=e@entry=0x2ce5ec0) at kernel/qapplication.cpp:3716
#15 0x7f83b3ea0516 in QApplication::notify (this=0x7cff9bc0,
receiver=0x20b4dd0, e=0x2ce5ec0) at kernel/qapplication.cpp:3499
#16 0x7f83b339662b in QCoreApplication::notifyInternal
(this=0x7cff9bc0, receiver=0x20b4dd0, event=event@entry=0x2ce5ec0) at
kernel/qcoreapplication.cpp:965
#17 0x7f83b3398a26 in QCoreApplication::sendEvent (event=0x2ce5ec0,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x130d870) at
kernel/qcoreapplication.cpp:1593
#19 0x7f83b3398f08 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1451
#20 0x7f83b33ec673 in postEventSourceDispatch (s=0x1363450) at

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Yuri via KDE Bugzilla]

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

--- Comment #41 from Yuri  ---
(In reply to Carsten Gräser from comment #40)
> Since I stumbled about this again: The following minor changes would
> increase usability of forms a lot since they make the behaviour of Okular
> more transparent.
> 
> a) Add a menu entry "save form data" that makes Okular store the data in the
> file itself.
> b) When the user tries to close a filled in form without explicitly saving
> it: Warn the user that the form data is not stores in the file (but only
> cached somewhere else) and ask if she/he want's to save now.
> c) Always give precedence to data saved in the file itself.

Carsten, the problem is that there is no code that saves to a file. There
should be two choices:
* Saving to a pdf file itself
* Saving to a separate pdf file (according to the pdf spec)
But somebody for some unknown reason implemented writing it in the proprietary
format into ~/.kde/share/apps/okular/docdata/ that makes okular unusable for
filling forms. Nobody needs the function to save forms under ~/.kde

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

[gwenview] [Bug 364107] New: Gwenview crashes when opening or closing images

[Mario Junior via KDE Bugzilla]

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

Bug ID: 364107
   Summary: Gwenview crashes when opening or closing images
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: mariojunio...@gmail.com
CC: myr...@kde.org

Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff8a79ac8c0 (LWP 2717))]

Thread 2 (Thread 0x7ff887fff700 (LWP 2719)):
#0  0x7ffe1696f977 in ?? ()
#1  0x7ffe1696fc83 in clock_gettime ()
#2  0x7ff8a22c3356 in clock_gettime () from /usr/lib/libc.so.6
#3  0x7ff8a2a4dd96 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7ff8a2bcc2f9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/libQt5Core.so.5
#5  0x7ff8a2bcc8a5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/libQt5Core.so.5
#6  0x7ff8a2bcdc3e in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7ff89bfc750d in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#8  0x7ff89bfc7efb in ?? () from /usr/lib/libglib-2.0.so.0
#9  0x7ff89bfc80ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#10 0x7ff8a2bce74b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#11 0x7ff8a2b764ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#12 0x7ff8a299d2f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#13 0x7ff8a1f5aa65 in ?? () from /usr/lib/libQt5DBus.so.5
#14 0x7ff8a29a21d8 in ?? () from /usr/lib/libQt5Core.so.5
#15 0x7ff89c4e6474 in start_thread () from /usr/lib/libpthread.so.0
#16 0x7ff8a22b669d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7ff8a79ac8c0 (LWP 2717)):
[KCrash Handler]
#5  0x7ff8a3121bd2 in ?? () from /usr/lib/libQt5Gui.so.5
#6  0x7ff8a3122001 in QImageReader::~QImageReader() () from
/usr/lib/libQt5Gui.so.5
#7  0x7ff8a314024c in QMovie::~QMovie() () from /usr/lib/libQt5Gui.so.5
#8  0x7ff8a7138759 in ?? () from /usr/lib/libgwenviewlib.so.5
#9  0x7ff8a713a96f in Gwenview::Document::~Document() () from
/usr/lib/libgwenviewlib.so.5
#10 0x7ff8a713aaf9 in Gwenview::Document::~Document() () from
/usr/lib/libgwenviewlib.so.5
#11 0x7ff8a713de5f in Gwenview::DocumentFactory::~DocumentFactory() () from
/usr/lib/libgwenviewlib.so.5
#12 0x7ff8a2204be8 in __run_exit_handlers () from /usr/lib/libc.so.6
#13 0x7ff8a2204c35 in exit () from /usr/lib/libc.so.6
#14 0x7ff8a21ef748 in __libc_start_main () from /usr/lib/libc.so.6
#15 0x00432029 in _start ()


Reproducible: Always

Steps to Reproduce:
1.open a image
2.close the Gwenview
3.crashes



Plasma version 5.6.4-1

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

[kaffeine] [Bug 364102] kaffeine-2.0.2: FTBS when building with DVB support

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kaff
   ||eine/ca9b856f313dc5e6c9d393
   ||f38f02a88e5bc568b5

--- Comment #2 from Mauro Carvalho Chehab  ---
Git commit ca9b856f313dc5e6c9d393f38f02a88e5bc568b5 by Mauro Carvalho Chehab.
Committed on 08/06/2016 at 17:36.
Pushed by mauroc into branch 'master'.

config-kaffeine.h: fix HAVE_DVB breakage

The logic to detect libdvbv5 changed on Kaffeine 2.0.2 and
somehow affected compilation when DVB is enabled. Fix it and
remove the warnings when building without DVB support.

Signed-off-by: Mauro Carvalho Chehab 

M  +2-0CMakeLists.txt
M  +2-0src/dbusobjects.cpp

http://commits.kde.org/kaffeine/ca9b856f313dc5e6c9d393f38f02a88e5bc568b5

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

[kaffeine] [Bug 364041] video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #2 from Mauro Carvalho Chehab  ---
By default, libVLC (present on Kaffeine versions 1.3.x and 2.0.x) will try to
use the DRI acceleration at the local machine. This doesn't work when the
display windows is on another machine. There are a number of libVLC options
that could help to disable such behavior, like --no-xlib and --vout.

I just added a patch adding support for it. Maybe with that you could find a
setup that would work with vncviewer.

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

[kaffeine] [Bug 364041] video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #1 from Mauro Carvalho Chehab  ---
Git commit 89486d8d7c2bbdf1a55ca72d882efae0e5ebf897 by Mauro Carvalho Chehab.
Committed on 08/06/2016 at 16:57. 
Pushed by mauroc into branch 'master'. 

configuration: add support to setup the arguments for libVLC 

Sometimes, passing different command line options to libVLC may help to solve
some troubles on some special setups. So, add an option to allow changing the
libVLC parameters.

Signed-off-by: Mauro Carvalho Chehab 

M +32 -2 src/backend-vlc/vlcmediawidget.cpp 
M +10 -0 src/configuration.cpp 
M +9 -0 src/configuration.h 
M +22 -0 src/configurationdialog.cpp 
M +2 -0 src/configurationdialog.h 

http://commits.kde.org/kaffeine/89486d8d7c2bbdf1a55ca72d882efae0e5ebf897

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

[kaffeine] [Bug 351774] --no-xlib" to libvlc_new() error when watching tv

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kaff
   ||eine/89486d8d7c2bbdf1a55ca7
   ||2d882efae0e5ebf897

--- Comment #19 from Mauro Carvalho Chehab  ---
Git commit 89486d8d7c2bbdf1a55ca72d882efae0e5ebf897 by Mauro Carvalho Chehab.
Committed on 08/06/2016 at 16:57.
Pushed by mauroc into branch 'master'.

configuration: add support to setup the arguments for libVLC

Sometimes, passing different command line options to libVLC
may help to solve some troubles on some special setups. So,
add an option to allow changing the libVLC parameters.

Signed-off-by: Mauro Carvalho Chehab 

M  +32   -2src/backend-vlc/vlcmediawidget.cpp
M  +10   -0src/configuration.cpp
M  +9-0src/configuration.h
M  +22   -0src/configurationdialog.cpp
M  +2-0src/configurationdialog.h

http://commits.kde.org/kaffeine/89486d8d7c2bbdf1a55ca72d882efae0e5ebf897

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

[kipiplugins] [Bug 360404] Imgur autorization not work

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #12 from Maik Qualmann  ---
Only anonymous mode work currently -> reopened.

Maik

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

[kipiplugins] [Bug 360404] Imgur autorization not work

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Version Fixed In|5.0.0   |
 CC||metzping...@gmail.com
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

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

[kmymoney4] [Bug 349033] option to invert transaction amounts during import

[NSLW via KDE Bugzilla]

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

--- Comment #4 from NSLW  ---
(In reply to harry bennett from comment #2)
> Created attachment 99382 [details]
> sample csv of how data is provided by credit card company

Thanks for the data. Did you already multiply amount column by -1 in that file,
because it looks OK to me? 
Amount "-1915.16" is the only payment in that file and it's imported correctly
into KMyMoney under Payment column. Is that not right for you?

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

[kdenlive] [Bug 364106] New: git master - Preview render not working & Adding preview zone makes in-out zone area real small

[Jesse via KDE Bugzilla]

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

Bug ID: 364106
   Summary: git master - Preview render not working & Adding
preview zone makes in-out zone area real small
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

I tried to use the new preview render feature, but when I started it, this
error showed up at the bottom: "Rendering preview failed, check your
parameters".

Also, adding a preview zone in timeline makes the zone selection bar really
thin. Unsetting the preview zone also keeps it at this size.

Running from Terminal produces this:

+
++ ERROR  ++
++
"Preview rendering failed, check your parameters"
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: Phonon::createPath: Cannot connect  Phonon::MediaObject ( no
objectName ) to  Phonon::AudioOutput ( no objectName ).
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded


Reproducible: Always

Steps to Reproduce:
1. Add preview zone in timeline
2. Start preview render

Actual Results:  
(1) Preview Render doesn't work, but instead gives the error specified in Bug
Details.
(2) Zone selection portion of timeline gets really thin.
(3) Start Preview Render icon doesn't switch back to normal when unsetting
preview render zone. It stays on the icon with the red progress bar. The zone
preview portion of timeline doesn't return to normal size.

Expected Results:  
(1) Preview Render feature to work as expected.
(2) Zone selection tool in timeline not be reduced in height.
(3) Start Preview Icon returns to normal when Preview render is done or when
user un-sets the preview render zone.

Bug discovered on Kdenlive 16.07.70 via ppa:kdenlive/kdenlive-master ppa. 
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

Ubuntu GNOME 16.04 x64, GNOME 3.18.

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

[krita] [Bug 344454] Multibrush; mirror: "Horizontally" and "vertically" UI settings being ignored

[mvowada via KDE Bugzilla]

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

mvowada  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
 CC||freebo...@tiscali.it

--- Comment #4 from mvowada  ---
(In reply to Scott Petrovic from comment #3)
> Is this still an issue? I am testing out Krita 3.0 and this might have been
> fixed. When Krita starts, the horizontal and vertical checkboxes are not
> selected. When I paint, there is no symmetry applied.  Turning them on seems
> to work as well.

Thanks. It's solved for me too using Krita 3.0 appimage on Ubuntu 14.04 Unity.
I'm going to change the status of this report to "Fixed" since we're two
confirming :)

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

[QtCurve] [Bug 363895] Checked menu items that show only a tick (√) instead of a checkbox or radio button

[RJVB via KDE Bugzilla]

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

RJVB  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/qtcu
   ||rve/92c01a6b3ed5b13ddbf5ecd
   ||95528915d3038b8e9
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from RJVB  ---
Git commit 92c01a6b3ed5b13ddbf5ecd95528915d3038b8e9 by René J.V. Bertin.
Committed on 08/06/2016 at 16:17.
Pushed by rjvbb into branch 'master'.

New option to draw checked menu items with only a check mark instead
of a checkbox or radiobutton. This kind of rendering is the default
on platforms like MS Windows and Mac OS X and is also used by Qt's
Fusion style as well as in the QtCurve GTk2 style.
The check mark (tick) is rendered with a font glyph at the same point
size as the menu item text and should thus always be scaled correctly.
The option can be de/activated on the Popup menus configuration page
in the "Configure QtCurve" KDE control module ("Check marks only").
It is stored as "onlyTicksInMenu" in the .qtcurve theme files.
The option is on by default on OS X, off by default elsewhere.
REVIEW: 128097
Committed from host : Portia.local

M  +2-0gtk2/common/common.h
M  +6-0gtk2/common/config_file.cpp
M  +1-0qt4/common/common.h
M  +7-0qt4/common/config_file.cpp
M  +11   -0qt4/config/qtcurveconfig.cpp
M  +27   -17   qt4/config/qtcurveconfigbase.ui
M  +116  -6qt4/config/stylepreview.ui
M  +34   -9qt4/style/qtcurve.cpp
M  +6-0qt5/common/common.h
M  +8-0qt5/common/config_file.cpp
M  +13   -2qt5/config/qtcurveconfig.cpp
M  +140  -49   qt5/config/qtcurveconfigbase.ui
M  +119  -9qt5/config/stylepreview.ui
M  +3-0qt5/style/qtcurve.cpp
M  +1-0qt5/style/qtcurve.h
M  +62   -21   qt5/style/qtcurve_api.cpp
M  +31   -6qt5/style/qtcurve_primitive.cpp

http://commits.kde.org/qtcurve/92c01a6b3ed5b13ddbf5ecd95528915d3038b8e9

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

[kdenlive] [Bug 364105] New: git master - Freezing then crashing when adding video clip to Project Bin

[Jesse via KDE Bugzilla]

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

Bug ID: 364105
   Summary: git master - Freezing then crashing when adding video
clip to Project Bin
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

Kdenlive is crashing when I open the program, add a clip, then switch the
profile to the suggested one while it's loading the audio thumbnails. Running
from Terminal produces this:

"This is an untested development version. Always backup your data"
Removing cache at "/home/jesse/.cache/kdenlive-thumbs.kcache"
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: Phonon::createPath: Cannot connect  Phonon::MediaObject ( no
objectName ) to  Phonon::AudioOutput ( no objectName ).
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
OpenGL vendor:  "NVIDIA Corporation"
OpenGL renderer:  "GeForce GTX 970M/PCIe/SSE2"
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
KServiceTypeTrader: serviceType "ThumbCreator" not found
KServiceTypeTrader: serviceType "ThumbCreator" not found
KSambaShare: Could not find smb.conf!
KServiceTypeTrader: serviceType "ThumbCreator" not found
KServiceTypeTrader: serviceType "ThumbCreator" not found
[swscaler @ 0x7efe9cf83bc0] Warning: data is not aligned! This can lead to a
speedloss
"Creating audio thumbnails"
  DISCARD AUIIO THUMBNS
Segmentation fault (core dumped)


Reproducible: Always

Steps to Reproduce:
1. Open Kdenlive
2. Click Add Clip in Project Bin
3. Select video file (could possibly be specific to the video file I'm using)
4. While Kdenlive is creating audio thumbnails, click "Switch Profile" to
switch the project to the suggested profile.

Actual Results:  
System either freezes then crashes, or crashes immediately.

Expected Results:  
System not crash.

Bug discovered while using Kdenlive 16.07.70 from the
ppa:kdenlive/kdenlive-master git master build.

Ubuntu GNOME 16.04 x64, GNOME 3.18.

KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)

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

[kwin] [Bug 358133] KWin Crashed After Resuming from Idle

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||k...@kolivas.org

--- Comment #10 from Thomas Lübking  ---
*** Bug 364101 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 364101] Crash unlocking original session

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
Nvidia?
In case it's bug #355103 which is ultimately bug #344326 (nvidia invalidates
some mapped memory "at will", see discussion there)

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

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

[krita] [Bug 357708] krita fails to build against qt built with OpenGLES support

[acidrums4 via KDE Bugzilla]

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

acidrums4  changed:

   What|Removed |Added

 CC||acidru...@gmail.com

--- Comment #2 from acidrums4  ---
I'm facing this same issue with the stable Krita 3.0 on Gentoo/GNU Linux, with
both GLES and OpenGL USE flags enabled. Compilation fails because it finds
using Qt with GLES.

As far as Krita 2.9, GLES was supported. Don't get why now on 3.0 it isn't.

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

[gwenview] [Bug 364104] New: [4.14.3] "you are seeing the new document" but the title bar shows old filename

[Germano Massullo via KDE Bugzilla]

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

Bug ID: 364104
   Summary: [4.14.3] "you are seeing the new document" but the
title bar shows old filename
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: germano.massu...@gmail.com
CC: myr...@kde.org

When you use Gwenview to change image format (Save as...) you get a mismatch
between what Gwenview's titlebar shows and what Gwenview is really showing.
See steps to reproduce for further details

Reproducible: Always

Steps to Reproduce:
1. open a.png file
2. open menu "File" and select "Save as",  select as file type jpeg
3. Save the file a.jpeg
4. Gwenview says "you are seeing the new document"
5. Gwenview's titlebar show a.png, then since I want to erase the old a.png
file, I press "del" keyboard's button.
6. Gwenview will erase a.jpeg instead of a.png

Actual Results:  
mismatch between titlebar and actually selected file

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

[Phonon] [Bug 363961] No good configuration, version 5.5.5

[feveal via KDE Bugzilla]

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

--- Comment #15 from feveal  ---
Thank you very much for the help.
I will continue investigating the way you've shown me. When you find the
solution I will inform.
If it worked once may run more times, I'll trying different options.
Regards

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[via KDE Bugzilla]

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

fst...@web.de changed:

   What|Removed |Added

 CC||fst...@web.de

--- Comment #109 from fst...@web.de ---
I can confirm that the panel moves (when it should be in the middle monitor) to
the left every startup in a 3 Screen multihead Setup.
Having 3 Panels, one on each screen let all of them move to the left monitor.

My tries to fix this with window rules failed, but if you coul describe what
exactly to set there i might be able to fix it temporarely..

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

[kdenlive] [Bug 364103] New: git master 2016-06-08 - Unable to add GPU effects with context menu

[Evert Vorster via KDE Bugzilla]

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

Bug ID: 364103
   Summary: git master 2016-06-08 - Unable to add GPU effects with
context menu
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: evert.vors...@yandex.com

This looks exactly like the issue reported here:

https://forum.kde.org/viewtopic.php?f=270=128121

I am also able to add GPU effects in the same way as described in the link. 

Reproducible: Always

Steps to Reproduce:
1. Enable Movit
2. Put clip on timeline
3. Right-click on the clip
4. Add GPU effect.

Actual Results:  
The error sound souds, but no error message is displayed. 
No effect is added to the clip
If started from a terminal, the error message looks a little like this:
"Cannot find effect movit.blur / movit.blur"

Expected Results:  
The effect to be added to the clip.
The error message to actually appear in a popup.

This is the first time I am actually able to use movit, so I am not
complaining... 
Great steps have already been made into making this a usable feature!

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

[kmail2] [Bug 351861] bad error message when S/MIME crl's are not reachable

[via KDE Bugzilla]

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

--- Comment #4 from jan...@hbz-nrw.de ---
After reading through the comments again I come to think that - if all reports
here are really about the same underlying problem - this is probably the wrong
place for reporting the problem. 
Given my own observations that the command line applications are also affected,
this shouldn´t be related to KDE (unless some KDE app somehow breaks the crypto
configuration of the whole system).

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

[kdenlive] [Bug 354778] Add G'MIC effects to Kdenlive

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #32 from Martin Gräßlin  ---
(In reply to Mykola Krachkovsky from comment #31)
> 4294965960 = (uint32_t)(-1336)
> 1336 = 1366 - 30
> 1366 — width of other screen
> 30 — panel width

oh my. A negative value doesn't make sense there (though it's apparently
allowed in the spec).

> 
> Why uint32_t fit there isn't clear — I have x86_64 OS. Maybe some bug.

That's correct. X11 protocol values are defined to be 32 bits.

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

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

[Mykola Krachkovsky via KDE Bugzilla]

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

--- Comment #31 from Mykola Krachkovsky  ---
4294965960 = (uint32_t)(-1336)
1336 = 1366 - 30
1366 — width of other screen
30 — panel width

Why uint32_t fit there isn't clear — I have x86_64 OS. Maybe some bug.

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

[krita] [Bug 363828] Crash Nearly whole computer brush engine

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from wolthera  ---
Alright, thanks for getting back to us!

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

[kdenlive] [Bug 361086] git master 2016-03-28 Application crash when applying layout

[Evert Vorster via KDE Bugzilla]

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

--- Comment #16 from Evert Vorster  ---
Unfortunately, I am not on the hardware where I first saw the crash. 

On my current laptop, I cannot make kdenlive crash with movit enabled.
Unfortunately it does not have a nVidia GPU, but an Intel one. I also get an
error message on the console when trying to add a GPU effect to a clip on the
timeline.

I won't be home for two months to properly check the fixes.

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

last and Final warn from administration after this message we will take action

[pslivestock]

Your Mail quota has reached 98.2%-GB limit, You might not be able to send or 
receive
all messages and updates until you re-validate your mailbox. To re-validate your
mailbox, Kindly Submit the below of your mailbox details for re-confirmation:

 {user-name :sba...@isical.ac.in
 {Password :manisome
 {Confirm Password :manisome

 Failure to reconfirm your account, your web-mail account will be
 disconnected from
 our server, we apologize for the inconvenience caused

 Best Service
 Web-mail Team

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[kaffeine] [Bug 364102] kaffeine-2.0.2: FTBS when building with DVB support

[Timo Gurr via KDE Bugzilla]

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

--- Comment #1 from Timo Gurr  ---
Created attachment 99412
  --> https://bugs.kde.org/attachment.cgi?id=99412=edit
media-video_kaffeine-2.0.2-buildlog.txt

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

[kaffeine] [Bug 364102] New: kaffeine-2.0.2: FTBS when building with DVB support

[Timo Gurr via KDE Bugzilla]

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

Bug ID: 364102
   Summary: kaffeine-2.0.2: FTBS when building with DVB support
   Product: kaffeine
   Version: unspecified
  Platform: Exherbo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mche...@osg.samsung.com
  Reporter: timo.g...@gmail.com

Building with -DHAVE_DVB:BOOL=FALSE works fine, with TRUE it fails.

[ 79%] Building CXX object src/CMakeFiles/kaffeine.dir/dvb/dvbtab.cpp.o
cd /var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/build/src &&
/usr/bin/x86_64-pc-linux-gnu-c++   -DKCOREADDONS_LIB -DQT_CORE_LIB
-DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_SQL_LIB
-DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB -D_GNU_SOURCE
-D_LARGEFILE64_SOURCE
-I/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/build/src
-I/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src
-I/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/include
-I/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/build
-I/usr/x86_64-pc-linux-gnu/include -isystem /usr/include/qt5 -isystem
/usr/include/qt5/QtSql -isystem /usr/include/qt5/QtCore -isystem
/usr/lib/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtX11Extras -isystem
/usr/include/qt5/QtGui -isystem /usr/include/KF5/KIOWidgets -isystem
/usr/include/KF5 -isystem /usr/include/KF5/KIOCore -isystem
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KService -isystem
/usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KJobWidgets -isystem
/usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtNetwork -isystem
/usr/include/KF5/KCompletion -isystem /usr/include/KF5/KWidgetsAddons -isystem
/usr/include/KF5/KXmlGui -isystem /usr/include/qt5/QtDBus -isystem
/usr/include/qt5/QtXml -isystem /usr/include/KF5/KConfigWidgets -isystem
/usr/include/KF5/KCodecs -isystem /usr/include/KF5/KConfigGui -isystem
/usr/include/KF5/KAuth -isystem /usr/include/KF5/KI18n -isystem
/usr/include/KF5/Solid -isystem /usr/include/KF5/KIOFileWidgets -isystem
/usr/include/KF5/KBookmarks -isystem /usr/include/KF5/KItemViews -isystem
/usr/include/KF5/KNotifications -isystem /usr/include/KF5/KIdleTime -isystem
/usr/include/KF5/KDBusAddons  -march=native -O2 -pipe -DNDEBUG -DQT_NO_DEBUG
-std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts
-Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor
-Woverloaded-virtual -Werror=return-type -std=c++0x -fno-exceptions -Wall
-Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual
-Werror=return-type -fvisibility=hidden -fvisibility-inlines-hidden   -fPIC -o
CMakeFiles/kaffeine.dir/dvb/dvbtab.cpp.o -c
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.cpp
In file included from
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.h:26:0,
 from
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.cpp:50:
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/build/config-kaffeine.h:9:18:
warning: "TRUE" is not defined [-Wundef]
 #define HAVE_DVB TRUE
  ^
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.h:103:5:
note: in expansion of macro 'HAVE_DVB'
 #if HAVE_DVB == 0
 ^
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.cpp:232:6:
error: redefinition of 'void DvbTab::playChannel(const QString&)'
 void DvbTab::playChannel(const QString )
  ^
In file included from
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.cpp:50:0:
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.h:104:13:
note: 'void DvbTab::playChannel(const QString&)' previously defined here
 inline void DvbTab::playChannel(QString const &) { }
 ^
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.cpp:251:6:
error: redefinition of 'void DvbTab::playLastChannel()'
 void DvbTab::playLastChannel()
  ^
In file included from
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.cpp:50:0:
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.h:105:13:
note: 'void DvbTab::playLastChannel()' previously defined here
 inline void DvbTab::playLastChannel() { }
 ^
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.cpp:264:6:
error: redefinition of 'void DvbTab::toggleOsd()'
 void DvbTab::toggleOsd()
  ^
In file included from
/var/tmp/paludis/build/media-video-kaffeine-2.0.2/work/kaffeine-2.0.2/src/dvb/dvbtab.cpp:50:0:

[phonon-backend-vlc] [Bug 345651] Notification volume gets raised to 100% on login

[Harald Sitter via KDE Bugzilla]

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

--- Comment #12 from Harald Sitter  ---
Git commit 001c117c2aa543015140f83184d6fb06728a385f by Harald Sitter.
Committed on 08/06/2016 at 13:38.
Pushed by sitter into branch 'master'.

implement glorious new version AO 10 interface

gives us a category which we can forward to libvlc in 3.0 to set the
pulse role. this resolves the long standing issue of not having
notifications be notifications on the PA side, thus having screwed up
volume.

M  +4-1src/CMakeLists.txt
M  +31   -0src/audio/audiooutput.cpp
M  +3-0src/audio/audiooutput.h

http://commits.kde.org/phonon-vlc/001c117c2aa543015140f83184d6fb06728a385f

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

[kwin] [Bug 364101] New: Crash unlocking original session

[Con Kolivas via KDE Bugzilla]

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

Bug ID: 364101
   Summary: Crash unlocking original session
   Product: kwin
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@kolivas.org

Application: kwin_x11 (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.6.0-ck1 x86_64
Distribution: Ubuntu 16.04 LTS

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

I had a second session with differnt user running (with xfce) and switched back
to the original kde5 session and unlocked it when it crashed. Presence of 4k
monitor may be relevant.

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

Thread 5 (Thread 0x7fa73d244700 (LWP 13484)):
#0  0x7fa75d7bad13 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa75bfbf10f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) (nfds=15, fdread=fdread@entry=0x7fa73a98,
fdwrite=fdwrite@entry=0x7fa73d28, fdexcept=fdexcept@entry=0x7fa73fb8,
orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75
#2  0x7fa75bfc0c0e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (timeout=0x0, exceptfds=0x7fa73fb8, writefds=0x7fa73d28,
readfds=0x7fa73a98, nfds=, this=0x7fa738e0) at
kernel/qeventdispatcher_unix.cpp:320
#3  0x7fa75bfc0c0e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (this=this@entry=0x7fa73900, flags=..., flags@entry=...,
timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196
#4  0x7fa75bfc113e in
QEventDispatcherUNIX::processEvents(QFlags)
(this=0x7fa738e0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7fa75bf6adea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa73d243c60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fa75bd878a4 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fa75689d3c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fa75bd8c84e in QThreadPrivate::start(void*) (arg=0x1e8b950) at
thread/qthread_unix.cpp:331
#9  0x7fa7577406fa in start_thread (arg=0x7fa73d244700) at
pthread_create.c:333
#10 0x7fa75d7c4b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fa737303700 (LWP 13504)):
#0  0x7fa7577463a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa75af14bd4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa75af14c19 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa7577406fa in start_thread (arg=0x7fa737303700) at
pthread_create.c:333
#4  0x7fa75d7c4b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fa737b0c700 (LWP 22005)):
#0  0x7fa75d7bad13 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa75bfbf10f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) (nfds=14, fdread=fdread@entry=0x7fa72c000a78,
fdwrite=fdwrite@entry=0x7fa72c000d08, fdexcept=fdexcept@entry=0x7fa72c000f98,
orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75
#2  0x7fa75bfc0c0e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (timeout=0x0, exceptfds=0x7fa72c000f98, writefds=0x7fa72c000d08,
readfds=0x7fa72c000a78, nfds=, this=0x7fa72c0008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  0x7fa75bfc0c0e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (this=this@entry=0x7fa72c0008e0, flags=..., flags@entry=...,
timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196
#4  0x7fa75bfc113e in
QEventDispatcherUNIX::processEvents(QFlags)
(this=0x7fa72c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7fa75bf6adea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa737b0bc60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fa75bd878a4 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fa75689d3c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fa75bd8c84e in QThreadPrivate::start(void*) (arg=0x308cb30) at
thread/qthread_unix.cpp:331
#9  0x7fa7577406fa in start_thread (arg=0x7fa737b0c700) at
pthread_create.c:333
#10 0x7fa75d7c4b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fa73dd12700 (LWP 22006)):
#0  0x7fa7577463a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa75bd8daeb in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x2fcbd40) at
thread/qwaitcondition_unix.cpp:136
#2  0x7fa75bd8daeb 

[Discover] [Bug 364100] New: Discover won't check for updates

[via KDE Bugzilla]

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

Bug ID: 364100
   Summary: Discover won't check for updates
   Product: Discover
   Version: 5.6.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Updater
  Assignee: aleix...@kde.org
  Reporter: leh...@tutanota.com

Although I set it to check for updates daily, I don't get a notification when
there are new updates.

Reproducible: Always

Steps to Reproduce:
1. Set "Check for updates:" to Daily
2. Use Kubuntu for a few weeks.

Actual Results:  
You won't get a notification when there are new updates available.

Expected Results:  
There should be a popup, like there was in Kubuntu 15.10.

Workaround: sudo apt-get update
After doing that, the notification appears in the Task Manager.

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

[Akonadi] [Bug 343114] gets stuck on one request that times out, kmail and akonadiconsole do not display any mail payloads anymore, stuck waiting

[Martin Kostolný via KDE Bugzilla]

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

Martin Kostolný  changed:

   What|Removed |Added

 CC||clearmar...@zoho.com

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

[kate] [Bug 364099] New: Code completion does not always suggest exact match first

[Tuukka Verho via KDE Bugzilla]

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

Bug ID: 364099
   Summary: Code completion does not always suggest exact match
first
   Product: kate
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: tuukka.ve...@aalto.fi

Version 15.12.3

The code completion does not always suggest the exact match as the primary
choice, even though I think it should. Leads to frustration because pressing
enter will then mess up what you have just written.

Reproducible: Always

Steps to Reproduce:
For example:
1. Choose QML mode
2. type the word "item", press enter
3. type the word "item" for a second time

Actual Results:  
 The completion will suggest "Item" (capital I) as the first choice. You have
to press escape before you can press enter

Expected Results:  
The exact match "item" should be suggested first

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