[plasmashell] [Bug 360827] Android Studio window entries go missing from Task Manager

[Kai Uwe Broulik via KDE Bugzilla]

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

--- Comment #15 from Kai Uwe Broulik  ---
Ideally, Android Studio would stop setting crap properties on its window but
I'll have a look if I can still reproduce...

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

[krunner] [Bug 368139] Krunner crash because QtWebEngine::initialize failed

[Matthew Dawson via KDE Bugzilla]

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

Matthew Dawson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||matt...@mjdsystems.ca
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Matthew Dawson  ---


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

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

[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

[Matthew Dawson via KDE Bugzilla]

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

Matthew Dawson  changed:

   What|Removed |Added

 CC||bernhard+...@scheirle.de

--- Comment #13 from Matthew Dawson  ---
*** Bug 368139 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 368172] New: Cannot connect to app on Android 4.4.4 -- SSLHandshakeException

[via KDE Bugzilla]

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

Bug ID: 368172
   Summary: Cannot connect to app on Android 4.4.4 --
SSLHandshakeException
   Product: kdeconnect
   Version: 1.4
  Platform: Android
OS: Android 4.x
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: masterofex...@hotmail.com

My desktop (running kde-connect 1.0) and Android 6.0 devices cannot see my
Android 4.4.4 device and my Android 4.4.4 device cannot see any devices on the
network.  However, Android 6.0 & the desktop can see each other.  Clicking
refresh makes no difference; switching wireless networks makes no difference. 
Both Android devices are running 1.4.1.

On the desktop, I can clearly see the UDP broadcast from the Android 4.4.4
device, and it doesn't look much different from the packets sent by the Android
6.0 device.

Running logcat on the Android 4.4.4 device produces the following output:

I/KDE/LanLinkProvider( 2948): Broadcast identity package received from xxx@xxx
I/KDE/LanLinkProvider( 2948): Starting SSL handshake with xxx@xxx trusted:false
E/KDE/LanLinkProvider( 2948): Handshake failed with xxx@xxx
W/System.err( 2948): javax.net.ssl.SSLHandshakeException:
javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0x:
Failure in SSL library, usually a protocol error
W/System.err( 2948): error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no
shared cipher (external/openssl/ssl/s3_srvr.c:1381 0x:0x)
W/System.err( 2948):at
com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:449)
W/System.err( 2948):at
org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider$4.run(LanLinkProvider.java:246)
W/System.err( 2948):at java.lang.Thread.run(Thread.java:841)
W/System.err( 2948): Caused by: javax.net.ssl.SSLProtocolException: SSL
handshake aborted: ssl=0x: Failure in SSL library, usually a protocol
error
W/System.err( 2948): error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no
shared cipher (external/openssl/ssl/s3_srvr.c:1381 0x:0x)
W/System.err( 2948):at
com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
W/System.err( 2948):at
com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:406)
W/System.err( 2948):... 2 more


My wild guess is that KDE Connect requires strong ciphers to avoid a downgrade
attack, and my Android device is unfortunately too old to support the minimum. 
If I'm right, I see a few possible resolutions:
0) nothing to do (because my phone manufacturer omitted strong SSL ciphers -- I
wouldn't put it past Motorola)
1) update minimum requirements for KDE Connect on Android
2) allow weaker ciphers (possibly with a big red warning during pairing)
3) fallback to RSA encryption

Regardless, an error message for this issue would be helpful.

Reproducible: Always

Steps to Reproduce:
1. Connect Android 4.4.4 device to wireless network
2. Connect desktop to the same wireless network
3. Open KDE Connect on Android; hit refresh
4. Open KDE Connect Settings on desktop; hit refresh

Actual Results:  
No device seen in list of connectable devices

Expected Results:  
Desktop and Android 4.4.4 devices see each other and can be paired.

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

[Touchpad-KCM] [Bug 368156] No touchpad found

[Rajeesh K V via KDE Bugzilla]

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

Rajeesh K V  changed:

   What|Removed |Added

 CC||rajeeshknamb...@gmail.com

--- Comment #1 from Rajeesh K V  ---
Please confirm the plasma-desktop version, and the input drivers installed
($xlsatoms | grep -i tap)

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

[kwin] [Bug 340318] lot of QXcbConnection: XCB error: 3 (BadWindow)

[John Andersen via KDE Bugzilla]

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

John Andersen  changed:

   What|Removed |Added

 CC||jsam...@gmail.com

--- Comment #5 from John Andersen  ---
Wow.  Two years later and this stuff is still flooding everybody's logs.
People have no pride in workmanship these days.  I've fired guys for less.

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

[kate] [Bug 367786] Crash when I use VI input mode with the option "Let VI commands override Kate Shortcuts" and the Key Shift in command line ":"

[Johan Smith via KDE Bugzilla]

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

--- Comment #3 from Johan Smith  ---
I don't see nothing useful in this output :(
Doesn't ocurr in other distribution?

valgrind --track-origins=yes kate
==5233== Memcheck, a memory error detector
==5233== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==5233== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==5233== Command: kate
==5233==
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: Cannot connect (null)::returnPressed() to
KUrlRequester::returnPressed()
QObject::connect: Cannot connect (null)::returnPressed(QString) to
KUrlRequester::returnPressed(QString)
==5233== Stack overflow in thread 1: can't grow stack to 0xffe801ff8
==5233==
==5233== Process terminating with default action of signal 11 (SIGSEGV)
==5233==  Access not within mapped region at address 0xFFE801FF8
==5233==at 0x960FBF7: QMetaObject::cast(QObject const*) const (in
/usr/lib64/libQt5Core.so.5.7.0)
==5233==  If you believe this happened as a result of a stack
==5233==  overflow in your program's main thread (unlikely but
==5233==  possible), you can try to increase the size of the
==5233==  main thread stack using the --main-stacksize= flag.
==5233==  The main thread stack size used in this run was 8388608.
==5233==
==5233== HEAP SUMMARY:
==5233== in use at exit: 9,803,148 bytes in 102,511 blocks
==5233==   total heap usage: 692,599 allocs, 590,088 frees, 84,355,015 bytes
allocated
==5233==
==5233== LEAK SUMMARY:
==5233==definitely lost: 4,952 bytes in 20 blocks
==5233==indirectly lost: 1,043 bytes in 38 blocks
==5233==  possibly lost: 1,098,634 bytes in 4,033 blocks
==5233==still reachable: 8,698,519 bytes in 98,420 blocks
==5233== suppressed: 0 bytes in 0 blocks
==5233== Rerun with --leak-check=full to see details of leaked memory
==5233==
==5233== For counts of detected and suppressed errors, rerun with: -v
==5233== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
Terminado (killed)

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

[kdenlive] [Bug 366666] Crash opening old projects

[via KDE Bugzilla]

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

carion.nico...@gmail.com changed:

   What|Removed |Added

 CC||carion.nico...@gmail.com

--- Comment #1 from carion.nico...@gmail.com ---
I probably ran into the same issue (or closely related). I post a valgrind
output if this can help:
==23439== Mismatched free() / delete / delete []
==23439==at 0x4C2AD90: free (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==23439==by 0x44EAE6EA: on_start_profile (producer_xml.c:348)
==23439==by 0x44EAE6EA: on_start_element (producer_xml.c:1243)
==23439==by 0x167F47BD: xmlParseStartTag (in /usr/lib/libxml2.so.2.9.4)
==23439==by 0x168001F7: xmlParseElement (in /usr/lib/libxml2.so.2.9.4)
==23439==by 0x167FF67E: xmlParseContent (in /usr/lib/libxml2.so.2.9.4)
==23439==by 0x16800062: xmlParseElement (in /usr/lib/libxml2.so.2.9.4)
==23439==by 0x1680076A: xmlParseDocument (in /usr/lib/libxml2.so.2.9.4)
==23439==by 0x44EAF7CF: producer_xml_init (producer_xml.c:1766)
==23439==by 0x5F67089: mlt_factory_producer (mlt_factory.c:315)
==23439==by 0x3EF9015B: create_producer (producer_loader.c:78)
==23439==by 0x3EF90403: producer_loader_init (producer_loader.c:220)
==23439==by 0x5F67089: mlt_factory_producer (mlt_factory.c:315)
==23439==  Address 0x560753f0 is 0 bytes inside a block of size 16 alloc'd
==23439==at 0x4C2A7E9: operator new[](unsigned long) (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==23439==by 0xFC18F56: qstrdup(char const*) (in
/usr/lib/libQt5Core.so.5.7.0)
==23439==by 0x7D92C3: GLWidget::resetProfile(MltVideoProfile)
(glwidget.cpp:1050)
==23439==by 0x7E7951: Monitor::resetProfile(MltVideoProfile)
(monitor.cpp:1351)
==23439==by 0x7EDE80: MonitorManager::resetProfiles(MltVideoProfile,
Timecode const&) (monitormanager.cpp:256)
==23439==by 0x4E5E57: KdenliveDoc::updateProjectProfile(bool)
(kdenlivedoc.cpp:1441)
==23439==by 0x4E5CAC: KdenliveDoc::loadDocumentProperties()
(kdenlivedoc.cpp:1426)
==23439==by 0x4D8931: KdenliveDoc::KdenliveDoc(QUrl const&, QUrl const&,
QUndoGroup*, QString const&, QMap const&, QMap const&, QPoint const&, Render*, NotesPlugin*, bool*, MainWindow*)
(kdenlivedoc.cpp:251)
==23439==by 0x54CA24: ProjectManager::doOpenFile(QUrl const&,
KAutoSaveFile*) (projectmanager.cpp:515)
==23439==by 0x54C2EB: ProjectManager::openFile(QUrl const&)
(projectmanager.cpp:489)
==23439==by 0x96231F: ProjectManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (moc_projectmanager.cpp:184)
==23439==by 0xFE1B4E8: QMetaObject::activate(QObject*, int, int, void**)
(in /usr/lib/libQt5Core.so.5.7.0)
==23439== 



On a very preliminary analysis, it seems that this patch solves the issue.
diff --git a/src/monitor/glwidget.cpp b/src/monitor/glwidget.cpp
index 7306980..dfe317d 100644
--- a/src/monitor/glwidget.cpp
+++ b/src/monitor/glwidget.cpp
@@ -1047,7 +1047,7 @@ void GLWidget::resetProfile(MltVideoProfile profile)
 m_consumer->stop();
 m_consumer->purge();
 }
-m_monitorProfile->get_profile()->description =
qstrdup(profile.description.toUtf8().constData());
+m_monitorProfile->get_profile()->description =
strdup(profile.description.toUtf8().constData());
 m_monitorProfile->set_colorspace(profile.colorspace);
 m_monitorProfile->set_frame_rate(profile.frame_rate_num,
profile.frame_rate_den);
 m_monitorProfile->set_height(profile.height);

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

[plasmashell] [Bug 360827] Android Studio window entries go missing from Task Manager

[Sudhir Khanger via KDE Bugzilla]

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

--- Comment #14 from Sudhir Khanger  ---
Hi Kai Uwe Broulik,

Are you really not able to replicate this issue? The fix you released didn't
help me. Please see the updated attachments.

This issue has become very problematic to me because I have to kill plasmashell
20 times a day just to get all the windows in the task manager. It's a complete
nightmare.

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

[kdevelop] [Bug 368162] LLDB: Working directory is not changed to the one specified in configuration

[Aetf via KDE Bugzilla]

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

Aetf <7437...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #1 from Aetf <7437...@gmail.com> ---
Fixed with commit 3bf6698e63a7b65984cb7d0cc87fa764b654ae0e, but won't work
unless upstream bug fixed: https://llvm.org/bugs/show_bug.cgi?id=30265

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

[okular] [Bug 368151] Use with Xvnc and Xrdp causes immediate crash.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|grave   |crash

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

[konsole] [Bug 368155] [Idea] Place additional space between terminal lines.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||cf...@kde.org

--- Comment #1 from Christoph Feck  ---
Could you please clarify? From the title I was thinking about Profile >
Advanced > Line Spacing, but your mention of input and output leaves me
puzzled.

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

[Touchpad-KCM] [Bug 368156] No touchpad found

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Version|5.7.3   |unspecified
   Assignee|plasma-b...@kde.org |rajeeshknamb...@gmail.com
Product|systemsettings  |Touchpad-KCM
  Component|general |daemon

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

[plasmashell] [Bug 368161] Plasma (plasmashell), signal: Segmentation fault

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |5.7.3
   Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk
 CC||bhus...@gmail.com,
   ||plasma-b...@kde.org
Product|kde |plasmashell
  Component|general |general
   Target Milestone|--- |1.0

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

[kdenlive] [Bug 368171] New: Incorrect drawing of AudioGraphWidget causes crash

[via KDE Bugzilla]

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

Bug ID: 368171
   Summary: Incorrect drawing of AudioGraphWidget causes crash
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: carion.nico...@gmail.com

This bug has been triggered on an up to date arch distrib, with latest master
branch (commit c3f0470c4560a283d6f450f51a8cdf9bd6f91565) and latest version of
mlt (compiled from source).

The problem occured when saving a project but I believe it might be more
general than that.

I nailed down the problem to the following function:
void AudioGraphWidget::drawBackground()
{
QSize size(width(), height());
if (!size.isValid()) return;
m_pixmap = QPixmap(size);
if (m_pixmap.isNull()) return;
m_pixmap.fill(palette().base().color());
QPainter p(_pixmap);
QRect rect(0, 0, width() - 3, height());
p.setFont(QFontDatabase::systemFont(QFontDatabase::SmallestReadableFont));
p.setOpacity(0.6);
drawDbLabels(p, rect);
int offset = fontMetrics().width(QStringLiteral("888")) + 2;
rect.adjust(offset, 0, 0, 0);
int barWidth = (rect.width() - (2 * (AUDIBLE_BAND_COUNT - 1))) /
AUDIBLE_BAND_COUNT;
drawChanLabels(p, rect, barWidth);
rect.adjust(0, 0, 0, -fontMetrics().height());
m_rect = rect;
}

During runtime, offset=63, and width()=64. Hence after the first rect.adjust,
the value of rect is: {x1 = 63, y1 = 0, x2 = 60, y2 = 99}
Notice that x1>x2, hence the rect is invalid (negative width), which triggers a
crash in a subsequent call.

The following patch seems to resolve the issue, at least from a mathematical
point of view, but I don't know the code mechanics enough to tell if it makes
sense:
diff --git a/src/monitor/scopes/audiographspectrum.cpp
b/src/monitor/scopes/audiographspectrum.cpp
index bd1740e..5e6cc5e 100644
--- a/src/monitor/scopes/audiographspectrum.cpp
+++ b/src/monitor/scopes/audiographspectrum.cpp
@@ -222,7 +222,7 @@ void AudioGraphWidget::drawBackground()
 p.setFont(QFontDatabase::systemFont(QFontDatabase::SmallestReadableFont));
 p.setOpacity(0.6);
 drawDbLabels(p, rect);
-int offset = fontMetrics().width(QStringLiteral("888")) + 2;
+int offset = std::min(fontMetrics().width(QStringLiteral("888")) + 2,
width() - 3);
 rect.adjust(offset, 0, 0, 0);
 int barWidth = (rect.width() - (2 * (AUDIBLE_BAND_COUNT - 1))) /
AUDIBLE_BAND_COUNT;
 drawChanLabels(p, rect, barWidth);


For completness, I've included a full backtrace in additional information

Reproducible: Always

Steps to Reproduce:
Not sure how to reproduce exactly, but I have a project file that seems to
trigger it consistently.



Debug info :

Thread 44 (Thread 0x7fff47fff700 (LWP 16848)):
#0  0x7fffe8e3810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
No symbol table info available.
#1  0x7fffaea94acd in video_thread (arg=0x26985a0) at
consumer_sdl_audio.c:423
self = 0x26985a0
now = {tv_sec = 1472838169, tv_usec = 725611}
start = 1472838169725611
elapsed = 
tm = {tv_sec = 4, tv_nsec = 140737100584217}
next = 0x0
properties = 
speed = 
real_time = 1
#2  0x7fffe8e32454 in start_thread () from /usr/lib/libpthread.so.0
No symbol table info available.
#3  0x7fffebe767df in clone () from /usr/lib/libc.so.6
No symbol table info available.

Thread 43 (Thread 0x7fff3fffe700 (LWP 16847)):
#0  0x7fffebe6d551 in ppoll () from /usr/lib/libc.so.6
No symbol table info available.
#1  0x7fffe2aee99d in pa_mainloop_poll () from /usr/lib/libpulse.so.0
No symbol table info available.
#2  0x7fffe2aeef8e in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
No symbol table info available.
#3  0x7fffb8f5eeed in ?? () from /usr/lib/libSDL-1.2.so.0
No symbol table info available.
#4  0x7fffb8f32800 in ?? () from /usr/lib/libSDL-1.2.so.0
No symbol table info available.
#5  0x7fffb8f3afe8 in ?? () from /usr/lib/libSDL-1.2.so.0
No symbol table info available.
#6  0x7fffb8f7c8a9 in ?? () from /usr/lib/libSDL-1.2.so.0
No symbol table info available.
#7  0x7fffe8e32454 in start_thread () from /usr/lib/libpthread.so.0
No symbol table info available.
#8  0x7fffebe767df in clone () from /usr/lib/libc.so.6
No symbol table info available.

Thread 42 (Thread 0x7fff3f7fd700 (LWP 16846)):
#0  0x7fffe8e3810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
No symbol table info available.
#1  0x76ab7e0b in consumer_read_ahead_thread (arg=0x26985a0) at
mlt_consumer.c:842
self = 0x26985a0
priv = 0x26a38a0
properties = 0x26985a0
width = 1440
height = 1080
video_off = 0
preview_off = 
preview_format = 

[kdenlive] [Bug 368170] New: kdenlive zooms out of the picture.

[Jonas Mertens via KDE Bugzilla]

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

Bug ID: 368170
   Summary: kdenlive zooms out of the picture.
   Product: kdenlive
   Version: 16.08.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: joni410...@gmail.com

I installed the new update and then I could'nt import pictures without
kdenlive's zoom. I can edit the project, but I can't have two videos without
zooming out. 

Reproducible: Always

Steps to Reproduce:
1.adding two videos with different resolution
2.look at the monitor
3.

Actual Results:  
the video was smal

Expected Results:  
Maybe a selection of other version without that bug

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[Jochen Trumpf via KDE Bugzilla]

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

Jochen Trumpf  changed:

   What|Removed |Added

 CC||jochen.tru...@anu.edu.au

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

[valgrind] [Bug 328563] make track-fds support xml output

[Hideaki Kimura via KDE Bugzilla]

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

Hideaki Kimura  changed:

   What|Removed |Added

 CC||hideaki.kim...@gmail.com

--- Comment #1 from Hideaki Kimura  ---
I'm also hitting this, but in a bit different form from the original comment
probably due to version difference (mine is 3.11.0).

When I enable track-fds and xml output, valgrind _does_ output open-at-exit
file descriptors information in XML. However, the output is far from ideal.

For example,

// test.c
#include 
int main(void) {
  open("bluh", O_CREAT, 0);
  return 0;
}

Then
gcc test.c; rm -f bluh; valgrind --xml=yes --xml-file=out.xml --track-fds=yes
--leak-check=full --error-exitcode=1 ./a.out

a.out emits no error code:
> echo $?
0

The out.xml would look like:



4
memcheck
...snip...
20082
25595
memcheck

  
/usr/bin/valgrind
--xml=yes
--xml-file=out.xml
--track-fds=yes
--leak-check=full
--error-exitcode=1
  
  
./a.out
  


  RUNNING
  00:00:00:00.056 


  FINISHED
  00:00:00:00.242 

  

  0x4F27490
  /usr/lib64/libc-2.22.so
  __open_nocancel


  0x400552
  /home/kimurhid/a.out
  main

  





This is it. The  element shows where the open-at-exit FD was made, which
is useful but the way the xml shows it is very user-unfriendly. It doesn't even
say what this  element is about!

In my case, this is also causing an issue to integrate with other tools like
Continuous Integration (Jenkins) and CTest because the output/exit-code looks
normal even when there are leaked FDs. Jenkins/CTest just report that there
were no errors.. even when I have leaked FDs!

In sum, I suggest the following:

1. In XML, make the leaked-FD output as beefy as usual memory-leak errors,
ideally follow the same format.

2. Add an option to emit error exit-code on observing leaked-FDs, again just
like usual memory-leak errors.

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

[korganizer] [Bug 368012] Event times changed to five hours in advance when OS upgraded

[via KDE Bugzilla]

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

mandbt...@frontier.com changed:

   What|Removed |Added

   Severity|normal  |major

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

[kdenlive] [Bug 359212] Unable to use Firewire

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
Hi,

After the refactoring this feature wasn't ported and is not available anymore.
The efforts are currently focused on other aspects and this isn't in the list
at the moment. Maybe someone willing can pick this up...

cheers

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

[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|Geolocation-Editor  |Geolocation

--- Comment #1 from caulier.gil...@gmail.com ---
Sound like a Marble Widget problem when sidebar is set to show maps view at
startup.
Remember that Marble has plenty of plugins. The problem can be located in a 3rd
party component

Also, this will be interesting to see if stand alone marble application has
same problem on your computer...

Note : please specify which maps view is expected to see : GoogleMaps, OSM, or
local ?

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

[kdenlive] [Bug 368051] Transcoded clip is not added to the right folder

[Wegwerf via KDE Bugzilla]

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

--- Comment #4 from Wegwerf  ---
Can you try the testing ppa and then close if satisfyingly fixed? Otherwise I
can test in a few days and close the report.

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

[kdesvn] [Bug 368169] New: directory and contents add

[John via KDE Bugzilla]

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

Bug ID: 368169
   Summary: directory and contents add
   Product: kdesvn
   Version: 1.6.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: kdesvn-bugs-n...@kde.org
  Reporter: jlarm...@minnetronix.com

Application: kdesvn (1.6.0)
KDE Platform Version: 4.14.18
Qt Version: 4.8.6
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Adding a directory and its contents into SVN so I could commit them

-- Backtrace:
Application: kdesvn (kdesvn), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f66f36bb780 (LWP 22684))]

Thread 2 (Thread 0x7f66d7fff700 (LWP 23606)):
#0  0x7f66f066dccd in read () at /lib64/libc.so.6
#1  0x7f66efcdbb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f66efc9a999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f66efc9adf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f66efc9af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f66f31a4fde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#6  0x7f66f3176d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f66f3177045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#8  0x7f66f30744df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#9  0x7f66f3158653 in  () at /usr/lib64/libQtCore.so.4
#10 0x7f66f3076bbf in  () at /usr/lib64/libQtCore.so.4
#11 0x7f66f03800a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f66f067a02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f66f36bb780 (LWP 22684)):
[KCrash Handler]
#6  0x7f66f05ca0c7 in raise () at /lib64/libc.so.6
#7  0x7f66f05cb478 in abort () at /lib64/libc.so.6
#8  0x7f66f05c3146 in __assert_fail_base () at /lib64/libc.so.6
#9  0x7f66f05c31f2 in  () at /lib64/libc.so.6
#10 0x7f66e20a33e3 in  () at /usr/lib64/libsvn_subr-1.so.0
#11 0x7f66e2558070 in svn::Url::data(QByteArray const&) () at
/usr/lib64/libsvnqt.so.7
#12 0x7f66e255809f in svn::Url::data(QString const&) () at
/usr/lib64/libsvnqt.so.7
#13 0x7f66e2558b13 in svn::Url::Url(QString const&) () at
/usr/lib64/libsvnqt.so.7
#14 0x7f66e28170a2 in  () at /usr/lib64/kde4/kdesvnpart.so
#15 0x7f66e2854a8c in  () at /usr/lib64/kde4/kdesvnpart.so
#16 0x7f66e2855206 in  () at /usr/lib64/kde4/kdesvnpart.so
#17 0x7f66e2858ea2 in  () at /usr/lib64/kde4/kdesvnpart.so
#18 0x7f66f318c0fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#19 0x7f66f250c652 in QAction::triggered(bool) () at
/usr/lib64/libQtGui.so.4
#20 0x7f66f250e003 in QAction::activate(QAction::ActionEvent) () at
/usr/lib64/libQtGui.so.4
#21 0x7f66f2937399 in  () at /usr/lib64/libQtGui.so.4
#22 0x7f66f293b8e9 in  () at /usr/lib64/libQtGui.so.4
#23 0x7f66f1688015 in KMenu::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib64/libkdeui.so.5
#24 0x7f66f2561c5a in QWidget::event(QEvent*) () at
/usr/lib64/libQtGui.so.4
#25 0x7f66f293f73b in QMenu::event(QEvent*) () at /usr/lib64/libQtGui.so.4
#26 0x7f66f251279c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#27 0x7f66f2518e1a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#28 0x7f66f15d1e9a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#29 0x7f66f317818d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#30 0x7f66f2518613 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib64/libQtGui.so.4
#31 0x7f66f258a01c in  () at /usr/lib64/libQtGui.so.4
#32 0x7f66f258875c in QApplication::x11ProcessEvent(_XEvent*) () at
/usr/lib64/libQtGui.so.4
#33 0x7f66f25af5f2 in  () at /usr/lib64/libQtGui.so.4
#34 0x7f66efc9ac84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#35 0x7f66efc9aed8 in  () at /usr/lib64/libglib-2.0.so.0
#36 0x7f66efc9af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#37 0x7f66f31a4fbe in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#38 0x7f66f25af6a6 in  () at /usr/lib64/libQtGui.so.4
#39 0x7f66f3176d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#40 0x7f66f3177045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#41 0x7f66f317c499 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#42 0x0040a797 in  ()
#43 0x7f66f05b6b25 in 

[kdenlive] [Bug 368051] Transcoded clip is not added to the right folder

[via KDE Bugzilla]

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

--- Comment #3 from asla...@vsechno-atd.cz ---
Thanks for the fix. Should I mark it as resolved, or wait for the next version
and check it, or should it be done by someone on a higher place?

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

[kontact] [Bug 368168] New: Crash when closing kontakt AND mail list whithout text

[dieter via KDE Bugzilla]

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

Bug ID: 368168
   Summary: Crash when closing kontakt AND mail list whithout text
   Product: kontact
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: d...@gmx.de

Application: kontact (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-36-generic x86_64
Distribution: Linux Mint 18 Sarah

-- Information about the crash:
when I am viewing mails the mail details are displayed in correct manner - the
list of emails contains no text
I clicked on the close icon Upper right corner)

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb1f83e0940 (LWP 6921))]

Thread 20 (Thread 0x7fb0af7fe700 (LWP 7165)):
#0  0x7fb211694e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb20aea539c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb20aea54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb2121d7a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb21217edea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb211f9b8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb211fa084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb20b6cf6fa in start_thread (arg=0x7fb0af7fe700) at
pthread_create.c:333
#8  0x7fb2116a0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7fb0a700 (LWP 7163)):
#0  0x7fb211f989d4 in QMutex::lock() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fb2121d701f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fb20aea492d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb20aea52cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb20aea54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb2121d7a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb21217edea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb211f9b8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb211fa084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fb20b6cf6fa in start_thread (arg=0x7fb0a700) at
pthread_create.c:333
#10 0x7fb2116a0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fb138f99700 (LWP 7151)):
#0  0x7fb211694e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb20aea539c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb20aea54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb2121d7a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb21217edea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb211f9b8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb211fa084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb20b6cf6fa in start_thread (arg=0x7fb138f99700) at
pthread_create.c:333
#8  0x7fb2116a0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7fb13979a700 (LWP 7149)):
#0  0x7ffe833a59a9 in ?? ()
#1  0x7ffe833a5cd5 in clock_gettime ()
#2  0x7fb2116aefb6 in __GI___clock_gettime (clock_id=1, tp=0x7fb1397999f0)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7fb212050c16 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb2121d5529 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb2121d5a95 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb2121d6e7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb20aea492d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fb20aea52cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fb20aea54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fb2121d7a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fb21217edea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fb211f9b8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 

[digikam] [Bug 368167] New: crash on startup in geoiface QMutex::lock [cause: digikamrc]

[Jens B . Benecke via KDE Bugzilla]

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

Bug ID: 368167
   Summary: crash on startup in geoiface QMutex::lock [cause:
digikamrc]
   Product: digikam
   Version: 5.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Geolocation-Editor
  Assignee: digikam-de...@kde.org
  Reporter: jens-bugs.kde@spamfreemail.de

Digikam crashes right on startup after the console messages as follows:

(... lots of kipi.plugins loading ...)
kipi.library: Loaded plugin  "Smug"
kipi.plugins: Reading data from kipirc file..
Could not resolve property : XMLID_8_
Could not resolve property : XMLID_12_
Could not resolve property : XMLID_13_
Could not resolve property : XMLID_14_
Could not resolve property : XMLID_8_
Could not resolve property : XMLID_12_
Could not resolve property : XMLID_13_
Could not resolve property : XMLID_14_
Could not resolve property : XMLID_8_
Could not resolve property : XMLID_12_
Could not resolve property : XMLID_13_
Could not resolve property : XMLID_14_
digikam.geoiface: 
Speicherzugriffsfehler (Speicherabzug geschrieben)

This happens exactly when in digikamrc, the following section is present:
[Digikam Right Sidebar]

Removing this section allows Digikam to start again. After closing it, the
section changes as follows:

 [Digikam Right Sidebar]
-ActiveTab=3
+ActiveTab=0
 DigikamProperties Expanded=true
 FileProperties Expanded=true
 ItemProperties Expanded=true
-Minimized=false
+Minimized=true
 PhotographProperties Expanded=true
-RestoreSize=-1
+RestoreSize=209
 VideoProperties Expanded=true

and subsequent starts are successful again.
This file was written by Digikam upon exit, I did not modify it by myself.

Partial backtrace:
 Thread 1 (Thread 0x7f3822ac7b80 (LWP 7551)):
 #0  0x7f384f7d81d1 in QCoreApplication::postEvent(QObject*, QEvent*, int)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 #1  0x7f384a64c397 in ?? () from
/usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23
 #2  0x7f384a64cd30 in ?? () from
/usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23
 #3  0x7f384f805ea1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

StacktraceTop:
 QCoreApplication::postEvent(QObject*, QEvent*, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23
 ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23
 QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5



Reproducible: Always

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

[ksysguard] [Bug 368166] New: KDE crash while killing process from KsysGuard

[via KDE Bugzilla]

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

Bug ID: 368166
   Summary: KDE crash while killing process from  KsysGuard
   Product: ksysguard
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: u...@flanagan-consulting.com

Application: ksysguard (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Had told Skanlite to close from the R-click menu in the panel.  Saw that it was
still showing activity in KsysGuard, so selected it and R-clicked on the line
and attempted to end process.  KDE crashed immediately.  Skanlike is owned by
logged-in user.

- Unusual behavior I noticed:
Response to key strokes and mouse actions have been either slow or slifhtly
delayed recently.  Have manually set CPU speed to 2.6 GHz on all four threads
with little improvement.

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2fdcf9f800 (LWP 30840))]

Thread 2 (Thread 0x7f2fc0ff5700 (LWP 30841)):
#0  0x7f2fdc87cbfd in poll () from /lib64/libc.so.6
#1  0x7f2fd0bd5422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f2fd0bd700f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f2fc2d203c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f2fd7d0832f in QThreadPrivate::start (arg=0x1d8c410) at
thread/qthread_unix.cpp:331
#5  0x7f2fd07b20a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f2fdc88502d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f2fdcf9f800 (LWP 30840)):
[KCrash Handler]
#6  0x7f2fdb5ad6a4 in KNotification::flags (this=this@entry=0x23d53c0) at
/usr/src/debug/knotifications-5.21.0/src/knotification.cpp:233
#7  0x7f2fdb5cadd7 in NotifyByAudio::onAudioFinished (this=0x23dff70) at
/usr/src/debug/knotifications-5.21.0/src/notifybyaudio.cpp:140
#8  0x7f2fdb5d0525 in NotifyByAudio::qt_static_metacall (_o=, _c=, _id=, _a=) at
/usr/src/debug/knotifications-5.21.0/build/src/moc_notifybyaudio.cpp:83
#9  0x7f2fd7f13cc6 in QMetaObject::activate (sender=0x253ee80,
signalOffset=, local_signal_index=local_signal_index@entry=6,
argv=argv@entry=0x0) at kernel/qobject.cpp:3713
#10 0x7f2fd7f142e7 in QMetaObject::activate (sender=,
m=m@entry=0x7f2fd1267500 ,
local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at
kernel/qobject.cpp:3578
#11 0x7f2fd102d6a3 in Phonon::MediaObject::finished (this=)
at /usr/src/debug/phonon-4.8.3/build/phonon/moc_mediaobject.cpp:426
#12 0x7f2fd102fe75 in Phonon::MediaObject::qt_static_metacall
(_o=, _c=, _id=, _a=) at /usr/src/debug/phonon-4.8.3/build/phonon/moc_mediaobject.cpp:183
#13 0x7f2fd7f14ac6 in QObject::event (this=0x253ee80, e=) at
kernel/qobject.cpp:1239
#14 0x7f2fd8bc7e7c in QApplicationPrivate::notify_helper
(this=this@entry=0x1d71260, receiver=receiver@entry=0x253ee80,
e=e@entry=0x23d1460) at kernel/qapplication.cpp:3716
#15 0x7f2fd8b8 in QApplication::notify (this=0x7ffcb82d6790,
receiver=0x253ee80, e=0x23d1460) at kernel/qapplication.cpp:3499
#16 0x7f2fd7ee3e95 in QCoreApplication::notifyInternal
(this=0x7ffcb82d6790, receiver=0x253ee80, event=event@entry=0x23d1460) at
kernel/qcoreapplication.cpp:965
#17 0x7f2fd7ee6057 in QCoreApplication::sendEvent (event=0x23d1460,
receiver=) at kernel/qcoreapplication.h:224
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x1d707a0) at
kernel/qcoreapplication.cpp:1593
#19 0x7f2fd7ee6608 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1451
#20 0x7f2fd7f3b8f3 in postEventSourceDispatch (s=0x1daffc0) at
kernel/qeventdispatcher_glib.cpp:271
#21 0x7f2fcfe37c84 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#22 0x7f2fcfe37ed8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x7f2fcfe37f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#24 0x7f2fd7f3ad6c in QEventDispatcherGlib::processEvents (this=0x1dba5d0,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#25 0x7f2fd7ee1d53 in QEventLoop::exec (this=this@entry=0x7ffcb82d6670,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#26 0x7f2fd7ee98f6 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#27 0x7f2fdcbc1884 in kdemain (argc=1, argv=) at
/usr/src/debug/ksysguard-5.5.5/gui/ksysguard.cpp:596
#28 0x7f2fdc7c1b25 in __libc_start_main () from /lib64/libc.so.6
#29 0x004007ee in _start () at ../sysdeps/x86_64/start.S:122

Possible 

[kdenlive] [Bug 361819] git master: changing bin effect parameters does not mark project as changed

[Wegwerf via KDE Bugzilla]

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

--- Comment #3 from Wegwerf  ---
This is an important fix! Jean-Baptiste, thank you very much for squashing this
one that can bite unexpecting users rather badly.

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

[kdenlive] [Bug 368025] Persistent directories

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

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

--- Comment #2 from farid  ---
thanks jb! :D

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

[clazy] [Bug 368068] Add global option to exclude a particular check from a level

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/claz
   ||y/99de674a597182a31bfb98ff1
   ||392d0b29abd864d
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Sergio Martins  ---
Git commit 99de674a597182a31bfb98ff1392d0b29abd864d by Sergio Martins.
Committed on 02/09/2016 at 20:03.
Pushed by smartins into branch 'master'.

Allow to disable checks by prefixing with "no-"

For example, level0,no-qenums will execute all checks from level0
except qenums

M  +5-2Clazy.cpp
M  +3-1README.md
M  +34   -5checkmanager.cpp
M  +6-2checkmanager.h
M  +26   -0tests/clazy/test_requested_checks.sh
M  +77   -0tests/clazy/test_requested_checks.sh.expected

http://commits.kde.org/clazy/99de674a597182a31bfb98ff1392d0b29abd864d

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

[kdevelop] [Bug 368162] LLDB: Working directory is not changed to the one specified in configuration

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||7437...@gmail.com

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

[kdevelop] [Bug 368138] Kdevelop hangs at start and uses one cpu at 100% when started with high dpi settings

[Kevin Funk via KDE Bugzilla]

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

--- Comment #1 from Kevin Funk  ---
Can you try the following:
export KDEV_DISABLE_WELCOMEPAGE=1
kdevelop 

Does it still hang then for the 164 DPI setting?

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

[kdenlive] [Bug 361819] git master: changing bin effect parameters does not mark project as changed

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kden
   ||live/b2e1bc19f7a2e6c01be83c
   ||3f952f998a6fcf01be
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit b2e1bc19f7a2e6c01be83c3f952f998a6fcf01be by Jean-Baptiste Mardelle.
Committed on 02/09/2016 at 19:26.
Pushed by mardelle into branch 'Applications/16.08'.

Integrate master effect update and state change in undo system

M  +35   -0src/bin/bin.cpp
M  +5-0src/bin/bin.h
M  +49   -0src/bin/bincommands.cpp
M  +29   -0src/bin/bincommands.h
M  +8-0src/bin/projectclip.cpp
M  +1-0src/bin/projectclip.h
M  +4-8src/effectstack/effectstackview2.cpp
M  +3-0src/effectstack/effectstackview2.h
M  +2-0src/mainwindow.cpp

http://commits.kde.org/kdenlive/b2e1bc19f7a2e6c01be83c3f952f998a6fcf01be

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

[Breeze] [Bug 347280] Edit Application Specific Settings panel overflows the screen

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

 CC||kain...@gmail.com

--- Comment #5 from andreas  ---
+1 for 2nd point I know the dialogue and use it from time to time but I can't
say that I understand it.

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

[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations

[Fabian Vogt via KDE Bugzilla]

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

--- Comment #9 from Fabian Vogt  ---
Still happens with KWin 5.7.3. Weirdly only some windows are affected.
To clear up possible misunderstandings, I recorded a short video for
demonstration: https://www.youtube.com/watch?v=_m1lnX1lKqw

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

[konsole] [Bug 359669] If the configured font is not present, konsole show a black window

[Maximiliano Curia via KDE Bugzilla]

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

--- Comment #2 from Maximiliano Curia  ---
Sorry, it was a long time ago, and I don't remember which font I've used. But
before I forget, I'm currently using:

For system fonts the fonts-3270 and fonts-anonymous-pro packages, and for user
installed fonts the ones provided in https://github.com/ryanoasis/nerd-fonts/

In particular:
https://github.com/ryanoasis/nerd-fonts/blob/master/patched-fonts/Monofur/Regular/complete/monofur%20for%20Powerline%20Nerd%20Font%20Complete%20Mono.ttf

I'm testing konsole 16.08.0 and the issue seems almost completely gone, for the
fonts I've tested at least. When working with a system font, after removal
konsole fallsback to Monospace. But, when the font is installed in the user
home then after removal the fallback can be any font, and the font metrics for
the fallback seem to be  wrong (the glyphs are cut).

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

[kontact] [Bug 367566] Crashed creating filter

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||p...@kc.rr.com

--- Comment #4 from Denis Kurz  ---
*** Bug 368163 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 368163] kmail5 crashes when setting up anti-spam or anti-virus tools

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||denis.kurz+kdebugs@posteo.d
   ||e
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Denis Kurz  ---


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

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

[krita] [Bug 361149] Request: Move tool for frame range

[bruno brasil via KDE Bugzilla]

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

bruno brasil  changed:

   What|Removed |Added

 CC||bbrazi...@gmail.com

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

[krita] [Bug 368165] New: animation branch - play is broken

[via KDE Bugzilla]

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

Bug ID: 368165
   Summary: animation branch - play is broken
   Product: krita
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: anim...@gmail.com

Application: krita (3.0.1 Beta (git c54ca61))

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.8.0-rc2-mainline x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
On tha latest commit in animation branch, play is broken and crash krita.

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4e622be840 (LWP 4672))]

Thread 11 (Thread 0x7f4e0affa700 (LWP 4683)):
#0  0x7f4e565c84b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4e5a936b0c in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f4e5a9325ea in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f4e5a935df8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f4e565c2454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f4e59d2b7df in clone () from /usr/lib/libc.so.6

Thread 10 (Thread 0x7f4e0b7fb700 (LWP 4682)):
#0  0x7f4e565c84b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4e5a936b0c in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f4e5a9325ea in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f4e5a935df8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f4e565c2454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f4e59d2b7df in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7f4e0bffc700 (LWP 4681)):
#0  0x7f4e565c84b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4e5a936b0c in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f4e5a9325ea in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f4e5a935df8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f4e565c2454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f4e59d2b7df in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7f4e24d96700 (LWP 4680)):
#0  0x7f4e565c84b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4e5a936b0c in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f4e5a9325ea in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f4e5a935df8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f4e565c2454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f4e59d2b7df in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f4e25597700 (LWP 4678)):
#0  0x7f4e565c810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4e5a936bbb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f4e5b9eb9f9 in ?? () from /usr/lib/libQt5Widgets.so.5
#3  0x7f4e5a935df8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f4e565c2454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f4e59d2b7df in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f4e26199700 (LWP 4677)):
#0  0x7f4e59cfaffd in nanosleep () from /usr/lib/libc.so.6
#1  0x7f4e5a9d5e7d in ?? () from /usr/lib/libQt5Core.so.5
#2  0x7f4e5a935201 in QThread::msleep(unsigned long) () from
/usr/lib/libQt5Core.so.5
#3  0x7f4e60edab6a in KisTileDataSwapper::run (this=0x7f4e613636a0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at
/home/timo/kde/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:97
#4  0x7f4e5a935df8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f4e565c2454 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f4e59d2b7df in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f4e2699a700 (LWP 4676)):
#0  0x7f4e565c810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4e5a936bbb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f4e5a93009b in QSemaphore::acquire(int) () from
/usr/lib/libQt5Core.so.5
#3  0x7f4e60ec0eee in KisTileDataPooler::waitForWork (this=0x7f4e61363660
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
/home/timo/kde/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:165
#4  0x7f4e60ec163a in KisTileDataPooler::run (this=0x7f4e61363660
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
/home/timo/kde/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:187
#5  0x7f4e5a935df8 in ?? () from 

[plasmashell] [Bug 368066] Plasma causes X to leak video memory

[Ahmed Waheed via KDE Bugzilla]

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

--- Comment #2 from Ahmed Waheed  ---
@David Edmundson  any chance I can workaround this bug until it is fixed?

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

[kwin] [Bug 368164] New: Background contrast effect causes panel flickering and composition restarts while browsing through mails in KMail

[Matthias Dahl via KDE Bugzilla]

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

Bug ID: 368164
   Summary: Background contrast effect causes panel flickering and
composition restarts while browsing through mails in
KMail
   Product: kwin
   Version: 5.7.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ua_bugz_...@binary-island.eu

While browsing through mails in KMail, the composition is being restarted every
few seconds and with each mail jump, the panel flickers.

This took me quite a while to figure out, since it is not so obvious (@Thomas
Lübking: you gonna like this one): It is the background contrast effect. As
soon as it is off, everything behaves just fine.

This bug has been around a bit since I haven't used KMail for who knows long
and just am about to switch back. I remember I saw this exact behavior the last
time I tried KMail (which was already on Qt5 back then, but unfortunately I
don't know when that was).

Reproducible: Always

Steps to Reproduce:
1. Make sure composition as well as background contrast effect is on
2. Open KMail in a folder with quite a few mails
3. Browse through those mails with n and p in a pace that still shows the
individual mails


Actual Results:  
With each mail shown, the panel will flicker. After a few mails, the
composition will restart with the typical msg that something requested that
action and the inherent screen side-effects.

Expected Results:  
No flickering. No composition restarts.

KDE Applications 16.08, Frameworks 5.25.0, Plasma 5.7.4, NVIDIA Drivers 370.23
(GTX 1080)

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

[kmail2] [Bug 368163] New: kmail5 crashes when setting up anti-spam or anti-virus tools

[via KDE Bugzilla]

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

Bug ID: 368163
   Summary: kmail5 crashes when setting up anti-spam or anti-virus
tools
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: p...@kc.rr.com

Application: kmail (5.2.3)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.3.2-1.1 x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

Start kmail5, then go to Tools menu to select either Anti-Spam wizard or
Anti-Virus wizard. It will  find the appropriate tools. Now click next and
select the folder to move infected mail to. The applcation crashes at this
stage.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f98224c34c0 (LWP 4624))]

Thread 20 (Thread 0x7f978700 (LWP 4676)):
#0  0x7f9832581f8b in ?? () from /opt/gnome/lib64/libglib-2.0.so.0
#1  0x7f98325842fb in g_main_context_prepare () from
/opt/gnome/lib64/libglib-2.0.so.0
#2  0x7f9832584ca3 in ?? () from /opt/gnome/lib64/libglib-2.0.so.0
#3  0x7f9832584e7c in g_main_context_iteration () from
/opt/gnome/lib64/libglib-2.0.so.0
#4  0x7f983e761c7b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/kde/lib64/libQt5Core.so.5
#5  0x7f983e70e7ea in
QEventLoop::exec(QFlags) () from
/opt/kde/lib64/libQt5Core.so.5
#6  0x7f983e54cdbb in QThread::exec() () from
/opt/kde/lib64/libQt5Core.so.5
#7  0x7f983e551829 in ?? () from /opt/kde/lib64/libQt5Core.so.5
#8  0x7f98349a2484 in start_thread () from /lib64/libpthread.so.0
#9  0x7f983dc4f69f in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7f97a4ec4700 (LWP 4673)):
#0  0x7ffcbefd8b08 in clock_gettime ()
#1  0x7f983dc5c576 in clock_gettime () from /lib64/libc.so.6
#2  0x7f983e5f1dd1 in ?? () from /opt/kde/lib64/libQt5Core.so.5
#3  0x7f983e75fa39 in QTimerInfoList::updateCurrentTime() () from
/opt/kde/lib64/libQt5Core.so.5
#4  0x7f983e75ffa5 in QTimerInfoList::timerWait(timespec&) () from
/opt/kde/lib64/libQt5Core.so.5
#5  0x7f983e7612b6 in ?? () from /opt/kde/lib64/libQt5Core.so.5
#6  0x7f9832584359 in g_main_context_prepare () from
/opt/gnome/lib64/libglib-2.0.so.0
#7  0x7f9832584ca3 in ?? () from /opt/gnome/lib64/libglib-2.0.so.0
#8  0x7f9832584e7c in g_main_context_iteration () from
/opt/gnome/lib64/libglib-2.0.so.0
#9  0x7f983e761c7b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/kde/lib64/libQt5Core.so.5
#10 0x7f983e70e7ea in
QEventLoop::exec(QFlags) () from
/opt/kde/lib64/libQt5Core.so.5
#11 0x7f983e54cdbb in QThread::exec() () from
/opt/kde/lib64/libQt5Core.so.5
#12 0x7f983e551829 in ?? () from /opt/kde/lib64/libQt5Core.so.5
#13 0x7f98349a2484 in start_thread () from /lib64/libpthread.so.0
#14 0x7f983dc4f69f in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7f97a5b8b700 (LWP 4657)):
#0  0x7f98325c7479 in g_mutex_lock () from
/opt/gnome/lib64/libglib-2.0.so.0
#1  0x7f9832584d3a in ?? () from /opt/gnome/lib64/libglib-2.0.so.0
#2  0x7f9832584e7c in g_main_context_iteration () from
/opt/gnome/lib64/libglib-2.0.so.0
#3  0x7f983e761c7b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/kde/lib64/libQt5Core.so.5
#4  0x7f983e70e7ea in
QEventLoop::exec(QFlags) () from
/opt/kde/lib64/libQt5Core.so.5
#5  0x7f983e54cdbb in QThread::exec() () from
/opt/kde/lib64/libQt5Core.so.5
#6  0x7f983e551829 in ?? () from /opt/kde/lib64/libQt5Core.so.5
#7  0x7f98349a2484 in start_thread () from /lib64/libpthread.so.0
#8  0x7f983dc4f69f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7f97a65aa700 (LWP 4650)):
#0  0x7f983e549357 in QMutex::unlock() () from
/opt/kde/lib64/libQt5Core.so.5
#1  0x7f983e76142d in ?? () from /opt/kde/lib64/libQt5Core.so.5
#2  0x7f9832584359 in g_main_context_prepare () from
/opt/gnome/lib64/libglib-2.0.so.0
#3  0x7f9832584ca3 in ?? () from /opt/gnome/lib64/libglib-2.0.so.0
#4  0x7f9832584e7c in g_main_context_iteration () from
/opt/gnome/lib64/libglib-2.0.so.0
#5  0x7f983e761c7b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/kde/lib64/libQt5Core.so.5
#6  0x7f983e70e7ea in
QEventLoop::exec(QFlags) () from
/opt/kde/lib64/libQt5Core.so.5
#7  0x7f983e54cdbb in QThread::exec() () from
/opt/kde/lib64/libQt5Core.so.5
#8  0x7f983e551829 in ?? () from /opt/kde/lib64/libQt5Core.so.5
#9  0x7f98349a2484 in start_thread () from /lib64/libpthread.so.0
#10 0x7f983dc4f69f in clone () from /lib64/libc.so.6

Thread 16 

[kdenlive] [Bug 368051] Transcoded clip is not added to the right folder

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #2 from Wegwerf  ---
Great! This is a fix for something that has annoyed me many times while working
in my daytime projects,  where I need to transcode a lot of screen recording
footage. Thank you very much, Jean-Baptiste!

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

[kdenlive] [Bug 367904] tmp files remaining in /tmp

[Benoit Touron via KDE Bugzilla]

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

--- Comment #2 from Benoit Touron  ---
(In reply to Jean-Baptiste Mardelle from comment #1)
> The temporary file handling has been changed in Kdenlive 16.08. However I am
> not sure to understand the problem you describe:
> 
> 1) What do you mean: "Import some clips" ? Adding clips in the Project bin ? 
Yes, exactly

> 2) What temporary file are you talking about? Can you tell me the file
> names/type so that I understand?
Files like : /tmp/kdenlive.<2 letters><4 digits>
exemple: kdenlive.TJ6180

By the way, I configured kdenlive with /var/tmp as temp folder, so I would
expect those files to be stored in /var/tmp instead of /tmp

Thanks anyway for kdenlive, it's really a great job !

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

[kdenlive] [Bug 366836] 16.08.0: clip context menu: audio split does not respect target audio track, splits always to topmost audio track

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kden
   ||live/a2acf194901e217b2ac2e0
   ||a1f91de91c942608ed
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit a2acf194901e217b2ac2e0a1f91de91c942608ed by Jean-Baptiste Mardelle.
Committed on 02/09/2016 at 17:27.
Pushed by mardelle into branch 'Applications/16.08'.

Fix split audio track

M  +1-0src/timeline/customtrackview.cpp

http://commits.kde.org/kdenlive/a2acf194901e217b2ac2e0a1f91de91c942608ed

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

[kdenlive] [Bug 367652] Can't add title clip

[Gustav Ekner via KDE Bugzilla]

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

--- Comment #3 from Gustav Ekner  ---
Is there any way to check that in Kdenlive? I think I have version 6.3.0
(libmlt6 from dpkg -l)

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

[kdevelop] [Bug 368162] New: Working directory is not changed to the one specified in configuration

[Alexander Potashev via KDE Bugzilla]

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

Bug ID: 368162
   Summary: Working directory is not changed to the one specified
in configuration
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aspotas...@gmail.com

See Steps to Reproduce.

Reproducible: Always

Steps to Reproduce:
1. Add Run Configuration for a C++ application.
2. Set Working Directory in that run configuration to something different from
$HOME.
3. Switch debugger to LLDB.
4. Start debugging.

Actual Results:  
Application's working directory is set to $HOME.

Expected Results:  
Application's working directory should be set to the path specified in "Working
Directory:" field in the run configuration. It works with GDB.

Built from Git master, top commit:

commit f9b262cd926151c30f4eae42ac7a7e56c7392edf
Author: Kevin Funk 
Date:   Tue Aug 30 20:26:01 2016 +0200

lldb: Fix loading of resource with kxmlgui files

Otherwise kdevlldbui.rc can't be found

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

[kdevelop] [Bug 368162] LLDB: Working directory is not changed to the one specified in configuration

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

Summary|Working directory is not|LLDB: Working directory is
   |changed to the one  |not changed to the one
   |specified in configuration  |specified in configuration

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

[kmymoney4] [Bug 343484] Transactions created with no payee/receiver after OFX import when payee has default account

[BobSCA via KDE Bugzilla]

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

BobSCA  changed:

   What|Removed |Added

Summary|Transactions created with   |Transactions created with
   |no payee/receiver after OFX |no payee/receiver after OFX
   |import when payer has   |import when payee has
   |default account |default account

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

[kmymoney4] [Bug 343484] Transactions created with no payee/receiver after OFX import when payer has default account

[BobSCA via KDE Bugzilla]

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

--- Comment #3 from BobSCA  ---
(In reply to BobSCA from comment #1)
> Version 4.7.1
Still present in 4.8.0.

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

[kmymoney4] [Bug 343484] Transactions created with no payee/receiver after OFX import when payer has default account

[BobSCA via KDE Bugzilla]

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

BobSCA  changed:

   What|Removed |Added

Version|4.7.1   |4.8.0

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

[kdenlive] [Bug 367623] Bulk vidstab does not respect the target directory

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kden
   ||live/95a528ca9f2e4493aff112
   ||56f7fcb05a24657e63
 Resolution|--- |FIXED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 95a528ca9f2e4493aff11256f7fcb05a24657e63 by Jean-Baptiste Mardelle.
Committed on 02/09/2016 at 16:47.
Pushed by mardelle into branch 'Applications/16.08'.

Fix path problem when trying to stabilize several clips

M  +5-4src/project/clipstabilize.cpp
M  +1-1src/project/jobs/filterjob.cpp
M  +15   -4src/project/jobs/jobmanager.cpp

http://commits.kde.org/kdenlive/95a528ca9f2e4493aff11256f7fcb05a24657e63

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

[krita] [Bug 366757] Preset tags are not always loaded

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit
   |a/aace80bef36d4be6e07d43372 |a/349b5e776205e844268835f60
   |a44a02be17d7808 |3f36bf89c8eb7b3

--- Comment #5 from wolthera  ---
Git commit 349b5e776205e844268835f603f36bf89c8eb7b3 by Wolthera van Hovell tot
Westerflier, on behalf of Boudewijn Rempt.
Committed on 02/09/2016 at 16:23.
Pushed by woltherav into branch 'krita-testing-wolthera'.

Try harder to find the tag files on Windows and OSX

This is yet another KoResourcePaths problem...

M  +12   -21   libs/widgetutils/KoResourcePaths.cpp

http://commits.kde.org/krita/349b5e776205e844268835f603f36bf89c8eb7b3

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

[frameworks-ki18n] [Bug 368007] Krita 3.0.1 RC doesn't load a system language of OS

[wolthera via KDE Bugzilla]

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

--- Comment #11 from wolthera  ---
Git commit 88bf822c445752d10ea962e88b8e31c8ad8cf337 by Wolthera van Hovell tot
Westerflier, on behalf of Boudewijn Rempt.
Committed on 02/09/2016 at 16:23.
Pushed by woltherav into branch 'krita-testing-wolthera'.

Go back to ki18n 5.17 for now

To avoid the system-language bug until it's fixed.

M  +2-23rdparty/ext_frameworks/CMakeLists.txt

http://commits.kde.org/krita/88bf822c445752d10ea962e88b8e31c8ad8cf337

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

[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://

[Elvis Angelaccio via KDE Bugzilla]

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

--- Comment #16 from Elvis Angelaccio  ---
(In reply to Vadym Krevs from comment #14)
> (In reply to Elvis Angelaccio from comment #13)
> > https://git.reviewboard.kde.org/r/128796/ is an attempt to provide a generic
> > fallback. Please test :)
> 
> I've backported your fix to kio-5.25.0-142.1.src.rpm, and tested it. It
> works for the smb io slave and fixes the issue that was originally reported. 
> 
> But there seems to be a corner case where it doesn't.  The menu entry is
> still disabled the very first time one tries it. If one closes and restarts
> Dolphin (or if you have 2 smb shares in Places, and you repeat steps 3-5 on
> against the second sbm share), then it starts working.

Unfortunately I don't have samba shares for testing. But please open another
report, it might be a different issue.

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

[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kio/
   ||fcbfb61a5304554483ceb49d872
   ||8d0e947a4af9e

--- Comment #15 from Elvis Angelaccio  ---
Git commit fcbfb61a5304554483ceb49d8728d0e947a4af9e by Elvis Angelaccio.
Committed on 02/09/2016 at 15:55.
Pushed by elvisangelaccio into branch 'master'.

Provide a fallback if slaves don't list the . entry

If a slave doesn't (or can't) emit an UDSEntry for the "." entry, we do it in
the
SlaveBase base class.
REVIEW: 128796

M  +23   -0src/core/slavebase.cpp

http://commits.kde.org/kio/fcbfb61a5304554483ceb49d8728d0e947a4af9e

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

[kdenlive] [Bug 367904] tmp files remaining in /tmp

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
The temporary file handling has been changed in Kdenlive 16.08. However I am
not sure to understand the problem you describe:

1) What do you mean: "Import some clips" ? Adding clips in the Project bin ? 
2) What temporary file are you talking about? Can you tell me the file
names/type so that I understand?

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

[kdenlive] [Bug 367984] Clip Speed effect is lost after moving clips with speed fx applied, saving project, closing and opening it again

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||j...@kdenlive.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Jean-Baptiste Mardelle  ---
I cannot reproduce. Which MLT version are you using? To help us, the best way
would be to start a simple project with only 2-3 clips. Save the project and
make a backup copy. Then reproduce the bug and send us the original backup copy
and the broken project file. This might help us understand

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

[kontact] [Bug 368110] Crash at shut down

[via KDE Bugzilla]

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

alfa...@gmx.de changed:

   What|Removed |Added

 CC||alfa...@gmx.de

--- Comment #1 from alfa...@gmx.de ---
confirmed!
opensuse LEAP 42.1
I've created a new user (clean config) and see same behavior.
kmail crashes also if I edit "identities" (choosing folders for sent emails,
etc.)

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

[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers

[via KDE Bugzilla]

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

sheep...@gmail.com changed:

   What|Removed |Added

 CC||sheep...@gmail.com

--- Comment #67 from sheep...@gmail.com ---
Same issue here:  close Konsole using window 'X" and one processor goes up to
100%; have to kill it; if I close the last tab with it's 'local X' no problem;
if I close using 'exit' at CL, no problem.

Older HP laptop; GeForce 8600M GS; nVidia patched 340.96 driver.

I understand this is really an nVidia issue but here's MY issue with KDE:  no
other terminal program I use under KDE except Konsole has this problem,
therefore, is this REALLY solely nVidia's issue or are 'you KDE folks' just
kicking the turd down the road?  This has been going on for way too long
(years, for crap's sake), how about you 'KDE folks' own up to it and fix it? 
You're looking like a bunch of goofballs right now...

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

[Breeze] [Bug 367818] Password textfield is not visible when using dm-crypt

[Viorel-Cătălin Răpițeanu via KDE Bugzilla]

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

Viorel-Cătălin Răpițeanu  changed:

   What|Removed |Added

 CC||rapiteanu.cata...@gmail.com

--- Comment #2 from Viorel-Cătălin Răpițeanu  ---
Created attachment 100900
  --> https://bugs.kde.org/attachment.cgi?id=100900=edit
plymouth debug dmesg

> Depending on which git version you are talking about the background isn't 
> blue.
I was refering to the git plymouth version
(https://cgit.freedesktop.org/plymouth/), not the KDE plymouth splash screen.
The last version tested was 5.7.4.

> Sounds more like your initramfs doesn't include the png assets of the theme.
Can you tell me how verify this?  I've attached a dmesg output displays the
timestamps of the plymouth debug messages during boot.

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

[plasmashell] [Bug 367738] add to favorites "Display Config - KDE Control Module" unable to run.

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Eike Hein  ---
Thanks. Version 5.5.5 is very old, and the change that fixed this problem was
made after. This will work in a recent version of Plasma.

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

[kde] [Bug 368161] New: Plasma (plasmashell), signal: Segmentation fault

[Don Curtis via KDE Bugzilla]

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

Bug ID: 368161
   Summary: Plasma (plasmashell), signal: Segmentation fault
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bugrprt21...@online.de

Application: plasmashell (5.7.4)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.4.19-1-default x86_64
Distribution: "openSUSE Leap 42.2 Beta"

-- Information about the crash:
- What I was doing when the application crashed:
Simply closed the set-up of the Plasmoid Digital Clock.
Plasma Desktop version 5.7.4-191.3

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa11d193900 (LWP 3687))]

Thread 14 (Thread 0x7fa057d91700 (LWP 3880)):
#0  0x7fa11686449d in poll () from /lib64/libc.so.6
#1  0x7fa112edf324 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fa112edf43c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fa11717530b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7fa117122fbb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fa116f5df1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7fa116f629e9 in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7fa116063734 in start_thread () from /lib64/libpthread.so.0
#8  0x7fa11686cd3d in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7fa05637a700 (LWP 3872)):
#0  0x7fa11686449d in poll () from /lib64/libc.so.6
#1  0x7fa112edf324 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fa112edf43c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fa11717530b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7fa117122fbb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fa116f5df1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7fa11a28fb48 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7fa116f629e9 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7fa116063734 in start_thread () from /lib64/libpthread.so.0
#9  0x7fa11686cd3d in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7fa062d9a700 (LWP 3741)):
#0  0x7fa11686449d in poll () from /lib64/libc.so.6
#1  0x7fa112edf324 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fa112edf43c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fa11717530b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7fa117122fbb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fa116f5df1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7fa0641ec8f7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7fa116f629e9 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7fa116063734 in start_thread () from /lib64/libpthread.so.0
#9  0x7fa11686cd3d in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7fa06b8ea700 (LWP 3734)):
#0  0x7fa11686449d in poll () from /lib64/libc.so.6
#1  0x7fa112edf324 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fa112edf43c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fa11717530b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7fa117122fbb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fa116f5df1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7fa11ae16632 in ?? () from /usr/lib64/libQt5Quick.so.5
#7  0x7fa116f629e9 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7fa116063734 in start_thread () from /lib64/libpthread.so.0
#9  0x7fa11686cd3d in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7fa07585f700 (LWP 3733)):
#0  0x7fa1160680af in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fa07e019e73 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7fa07e0199e7 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7fa116063734 in start_thread () from /lib64/libpthread.so.0
#4  0x7fa11686cd3d in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7fa076060700 (LWP 3732)):
#0  0x7fa1160680af in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fa07e019e73 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7fa07e0199e7 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7fa116063734 in start_thread () from /lib64/libpthread.so.0
#4  0x7fa11686cd3d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7fa076861700 (LWP 3731)):
#0  0x7fa1160680af in pthread_cond_wait@@GLIBC_2.3.2 () from

[kdenlive] [Bug 368051] Transcoded clip is not added to the right folder

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 0a1f6ca62b2d3a0e5e5d536d9b2e8e8e7e0f2e17 by Jean-Baptiste Mardelle.
Committed on 02/09/2016 at 14:55.
Pushed by mardelle into branch 'Applications/16.08'.

Fix transcoded clips showing up in wrong folder

M  +28   -3src/bin/bin.cpp
M  +4-2src/bin/bin.h
M  +1-1src/core.cpp
M  +5-4src/mainwindow.cpp
M  +1-1src/mainwindow.h
M  +3-3src/project/cliptranscode.cpp
M  +3-2src/project/cliptranscode.h
M  +2-2src/project/jobs/abstractclipjob.cpp
M  +3-3src/project/jobs/abstractclipjob.h
M  +5-2src/project/jobs/cutclipjob.cpp
M  +1-1src/project/jobs/filterjob.cpp
M  +2-2src/project/jobs/jobmanager.cpp
M  +1-1src/project/jobs/jobmanager.h

http://commits.kde.org/kdenlive/0a1f6ca62b2d3a0e5e5d536d9b2e8e8e7e0f2e17

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

[kdenlive] [Bug 368025] Persistent directories

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit f5a6eb4bc059d1ee3308f965eb58f73230658a28 by Jean-Baptiste Mardelle.
Committed on 02/09/2016 at 10:22.
Pushed by mardelle into branch 'Applications/16.08'.

Remember saved project folder for future opening

M  +7-5src/project/projectmanager.cpp

http://commits.kde.org/kdenlive/f5a6eb4bc059d1ee3308f965eb58f73230658a28

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

[drkonqi] [Bug 363838] drkonqi crashed before bugzilla login page

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||spearhead...@gmail.com

--- Comment #5 from Wolfgang Bauer  ---
*** Bug 368152 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 368152] drkonqui fails to report a bug and segfaults

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Wolfgang Bauer  ---
Same backtrace as bug#363838.

As I wrote there, it may be related to a disabled kwallet.
Though it shouldn't crash of course.

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

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

[plasmashell] [Bug 368160] Panel autohides even when plasmoid of the panel is open

[Christoph via KDE Bugzilla]

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

Christoph  changed:

   What|Removed |Added

URL|http://pasteboard.co/g5VJPt |
   |v30.png |

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

[plasmashell] [Bug 368160] Panel autohides even when plasmoid of the panel is open

[Christoph via KDE Bugzilla]

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

--- Comment #1 from Christoph  ---
Created attachment 100899
  --> https://bugs.kde.org/attachment.cgi?id=100899=edit
screenshot of issue

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

[plasmashell] [Bug 368160] New: Panel autohides even when plasmoid of the panel is open

[Christoph via KDE Bugzilla]

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

Bug ID: 368160
   Summary: Panel autohides even when plasmoid of the panel is
open
   Product: plasmashell
   Version: 5.7.3
  Platform: Fedora RPMs
   URL: http://pasteboard.co/g5VJPtv30.png
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: christoph.schwi...@tu-ilmenau.de

Panel is set to auto-hide → you open a plasmoid, e.g. your networkmanager in
your systray → the extended plasmoid is still open, but without hover the panel
hides → the plasmoid stays

Reproducible: Always

Steps to Reproduce:
1. set your panel to auto-hide
2. open your nm-manager, optional: pin it
3. panel will hide

Actual Results:  
Panel hides

Expected Results:  
Panel should stay visible

This bug was fixed in an earlier version. I'm not sure, but I think it came
again in version 5.6. Thanks!

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

[kdeconnect] [Bug 343235] SFTP: Dolphin is unresponsive when copying file via directory browse

[Damien Gombault via KDE Bugzilla]

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

Damien Gombault  changed:

   What|Removed |Added

 CC||desint...@gmail.com

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

[kmymoney4] [Bug 368159] New: Report Transactions by Payee omits transactions lacking category

[BobSCA via KDE Bugzilla]

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

Bug ID: 368159
   Summary: Report Transactions by Payee omits transactions
lacking category
   Product: kmymoney4
   Version: 4.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: bobs_spa...@cox.net

Reports with "Organize: By Payee" option omits transactions which do not
specify a category, including all transactions which specify an account in the
Category/Account field.

Reproducible: Always

Steps to Reproduce:
1. Create a transaction which specifies either an account or null in the
Category/Account field.
2. Create a report with "Organize: By Payee".


Actual Results:  
Specified transaction is not shown in report.

Expected Results:  
Specified transaction is shown in report.

1. Perhaps the required fix is to add a "Include transactions without a
category" option on the Report Configuration | Categories tab.

2. Oddly, if "Organize: By Accounts" is selected, then the specified
transactions are displayed.

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

[dolphin] [Bug 366638] [16.04] sftp stuck operations. Can operate only if reopening Dolphin

[Damien Gombault via KDE Bugzilla]

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

Damien Gombault  changed:

   What|Removed |Added

 CC||desint...@gmail.com

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

[ksysguard] [Bug 368158] New: System Activity dialog always appears offscreen

[Jason Tibbitts via KDE Bugzilla]

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

Bug ID: 368158
   Summary: System Activity dialog always appears offscreen
   Product: ksysguard
   Version: 5.7.3
  Platform: Fedora RPMs
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: ti...@math.uh.edu

I have a non-rectangular desktop.  It has three monitors arranged in a square
with no monitor in the upper left hand corner.

When I open the "System Activity" dialog, either with Shift-Escape or by
running "systemmonitor" from the command line, the dialog will always (and I
really do mean 100% of the time) open in the place where I have no monitor.  I
can click on the entry in the taskbar, navigate down to the Move option and
drag the window onscreen to see it.

I tried setting up a kwin rule to ignore the initial placement for that window
(and always put it under the mouse, or on the primary monitor, or something)
but I can't seem to get that to work for whatever reason.

This isn't the only window that usually opens offscreen, of course.  Generally,
though, it's just transient dialogs that do it.  While a kwin option to prevent
things from opening offscreen would probably be a good idea, I figured I'd file
file a ticket against each individual application I run across.  Absolute
positioning is generally a bad idea unless you're just restoring the last
position where the dialog was closed, but if you're going to do it, at least
clamp to the active portion of the desktop and not just to the bounding
rectangle.

Reproducible: Always

Steps to Reproduce:
1. Have a weird non-rectangular desktop, with no monitor in the upper left-hand
portion.
2. Open the system activity dialog.
3. Notice that you can't see said dialog because it opened offscreen.

Actual Results:  
Dialog opens where there's no monitor to display it.

Expected Results:  
Dialog opens someplace where a monitor exists to display it.

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

[plasmashell] [Bug 353975] Black screen on second display.

[Michael Seifert via KDE Bugzilla]

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

--- Comment #62 from Michael Seifert  ---
I can confirm the issue and the workaround for Plasma 5.7.4 as well.

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

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

[somnium via KDE Bugzilla]

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

--- Comment #23 from somnium  ---
This is still not working. It is the same on openSUSE Tumbleweed. I use a
ejabberd server an the password is not sent to the server like explained in
this bug report. Please reopen this report or I need to create a new one.

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

[plasmashell] [Bug 353975] Black screen on second display.

[Michael Seifert via KDE Bugzilla]

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

Michael Seifert  changed:

   What|Removed |Added

 CC||mseif...@error-reports.org

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

[amarok] [Bug 368157] New: Amarok crash while updating tags with MusicBrainz

[Deuil Etoiles via KDE Bugzilla]

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

Bug ID: 368157
   Summary: Amarok crash while updating tags with MusicBrainz
   Product: amarok
   Version: 2.8.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: emichaelb...@mail.com

Application: amarok (2.8.0)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.7.2-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160812) (x86_64)"

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

Editing tags in Amarok and updating them with data from Music Brainz crashes
the application EVERY time.

The crash can be reproduced every time.

-- Backtrace:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f37b5d3e940 (LWP 1968))]

Thread 11 (Thread 0x7f366affd700 (LWP 12321)):
#0  0x7f37b12d709f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37a96350b1 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f37a990082b in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f37b12d1474 in start_thread () at /lib64/libpthread.so.0
#4  0x7f37b277a3ed in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f3704a41700 (LWP 2045)):
#0  0x7f37b12d709f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37b18cce0a in  () at /usr/lib64/libQtScript.so.4
#2  0x7f37b18cce39 in  () at /usr/lib64/libQtScript.so.4
#3  0x7f37b12d1474 in start_thread () at /lib64/libpthread.so.0
#4  0x7f37b277a3ed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f37058cb700 (LWP 2044)):
#0  0x7f37b2771a1d in poll () at /lib64/libc.so.6
#1  0x7f37abb6e036 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f37abb6e14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f37b2f7e82e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f37b2f4cb8f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f37b2f4cef5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f37b2e3b8d9 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f37b2e3e1aa in  () at /usr/lib64/libQtCore.so.4
#8  0x7f37b12d1474 in start_thread () at /lib64/libpthread.so.0
#9  0x7f37b277a3ed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f3754962700 (LWP 2042)):
#0  0x7f37b12d709f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37a98d8686 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f37a98d86b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f37b12d1474 in start_thread () at /lib64/libpthread.so.0
#4  0x7f37b277a3ed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f3757fff700 (LWP 2037)):
#0  0x7f37b12d709f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37b2e3e716 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f37af40e482 in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
() at /usr/lib64/libthreadweaver.so.4
#3  0x7f37af4108f3 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) () at /usr/lib64/libthreadweaver.so.4
#4  0x7f37af40f52d in ThreadWeaver::Thread::run() () at
/usr/lib64/libthreadweaver.so.4
#5  0x7f37b2e3e1aa in  () at /usr/lib64/libQtCore.so.4
#6  0x7f37b12d1474 in start_thread () at /lib64/libpthread.so.0
#7  0x7f37b277a3ed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f376cda8700 (LWP 2036)):
#0  0x7f37b12d709f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37b2e3e716 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f37af40e482 in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
() at /usr/lib64/libthreadweaver.so.4
#3  0x7f37af4108f3 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) () at /usr/lib64/libthreadweaver.so.4
#4  0x7f37af41090c in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) () at /usr/lib64/libthreadweaver.so.4
#5  0x7f37af41090c in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) () at /usr/lib64/libthreadweaver.so.4
#6  0x7f37af41090c in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) () at /usr/lib64/libthreadweaver.so.4
#7  0x7f37af41090c in

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

[via KDE Bugzilla]

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

tro...@free.fr changed:

   What|Removed |Added

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

--- Comment #24 from tro...@free.fr ---
Apparently not totally solved.

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

[korganizer] [Bug 368012] Event times changed to five hours in advance when OS upgraded

[via KDE Bugzilla]

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

--- Comment #1 from mandbt...@frontier.com ---
Follow up to bug report.

We have three calendars created on KOrganizer.  If we adjust all the existing
appointments (that show up 5 hours in advance) to Floating so that they appear
on the calendar at the right time, the adjustments only works on the machine
they are being done on.  The calendars on the other two machines do not adjust.
 There is a server that the calendar is on so all three calendars should update
to reflect the same changes.

The calendar is not updating.  It is not keeping new appointments and they
aren't appearing on the other two computers.  They are not syncing.

One of our calendars keeps crashing with the following error:  There was a
problem with the request.  The item has not been detected.  The file or folder
on machine4 does not exist.  We have not moved or removed any files or folders.
 All three calendars are set up the same except for username.

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

[krita] [Bug 368119] Line Tool - strange line to corner

[via KDE Bugzilla]

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

--- Comment #6 from elk...@yahoo.com ---
Created attachment 100898
  --> https://bugs.kde.org/attachment.cgi?id=100898=edit
Line tool win7 preview bug

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

[kwin] [Bug 361617] kmail is causing system instability

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|effects-window-management   |effects-tabbox

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

[krita] [Bug 368119] Line Tool - strange line to corner

[via KDE Bugzilla]

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

--- Comment #5 from elk...@yahoo.com ---
I've always assumed (and I could be wrong, because I can always be wrong) that
the Line tool is a highly specialized version of the Brush tool. 

And given the rather unusual initial error of drawing a vector to image pixel
[0,0] I think there's a good chance it's the same issue. Even if it manifests
itself somewhat differently in each tool.

One Interesting note: on Win7(haven't downloaded the Linux appimage yet) the
Line tool's unwanted vector only happens in the preview and is not actually
drawn! Weird. This happens with both  tablet and mouse. I've attached another
video demonstrating this. The first line is the mouse, the second line is the
Wacom tablet. krita 3.0.99.91

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

[kate] [Bug 366493] Crashes when refreshing a file with more than 4096 chars in a line

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

   Priority|NOR |VHI

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

[kate] [Bug 366493] Crashes when refreshing a file with more than 4096 chars in a line

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Dominik Haumann  ---
Valgrind trace of today's build:

==9727== Invalid read of size 8
==9727==at 0x4F9C7C3: QHash >::findNode(KTextEditor::Message* const&,
unsigned int*) const (qhash.h:919)
==9727==by 0x4F99EBB: QHash >::contains(KTextEditor::Message* const&) const
(qhash.h:894)
==9727==by 0x507F623: KateMessageWidget::postMessage(KTextEditor::Message*,
QList) (katemessagewidget.cpp:188)
==9727==by 0x50525DF:
KTextEditor::ViewPrivate::postMessage(KTextEditor::Message*,
QList) (kateview.cpp:3460)
==9727==by 0x4F9338C:
KTextEditor::DocumentPrivate::postMessage(KTextEditor::Message*)
(katedocument.cpp:5966)
==9727==by 0x4F7CAA5: KTextEditor::DocumentPrivate::openFile()
(katedocument.cpp:2329)
==9727==by 0x5AA7B74: KParts::ReadOnlyPartPrivate::openLocalFile()
(readonlypart.cpp:187)
==9727==by 0x5AA7801: KParts::ReadOnlyPart::openUrl(QUrl const&)
(readonlypart.cpp:150)
==9727==by 0x4F7EC73: KTextEditor::DocumentPrivate::openUrl(QUrl const&)
(katedocument.cpp:2634)
==9727==by 0x4F8842C: KTextEditor::DocumentPrivate::documentReload()
(katedocument.cpp:4258)
==9727==by 0x5048A06: KTextEditor::ViewPrivate::reloadFile()
(kateview.cpp:1396)
==9727==by 0x517EEE8:
KTextEditor::ViewPrivate::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) (moc_kateview.cpp:736)
==9727==  Address 0x48 is not stack'd, malloc'd or (recently) free'd
==9727==

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

[kwin] [Bug 357867] Window hangs in drag-to-edge/snap resize preview if window's workspace changes

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|effects-window-management   |core

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

[frameworks-ktexteditor] [Bug 366579] Line numbers in printed documents start with 0

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

   Version Fixed In||KDE Frameworks 5.26

--- Comment #2 from Dominik Haumann  ---
Fixed with KDE Frameworks 5.26. Thanks for the report!

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

[plasmashell] [Bug 365602] Multi screen issues: black screen, wrong panel positions, plasmashell segfaults

[Tim Eberhardt via KDE Bugzilla]

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

--- Comment #6 from Tim Eberhardt  ---
I could not reproduce it the same way with the live image like in my normal
setup. Could be fixed but I'm not sure. In what plasmashell version this fix
will be in?

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

[frameworks-ktexteditor] [Bug 366579] Line numbers in printed documents start with 0

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/ktex
   ||teditor/f07f72c69d163d81e51
   ||a0ab74c7cde676fe76b6d

--- Comment #1 from Dominik Haumann  ---
Git commit f07f72c69d163d81e51a0ab74c7cde676fe76b6d by Dominik Haumann.
Committed on 02/09/2016 at 14:13.
Pushed by dhaumann into branch 'master'.

Fix: Line numbers in printed documents now starts at 1

M  +1-1src/printing/printpainter.cpp

http://commits.kde.org/ktexteditor/f07f72c69d163d81e51a0ab74c7cde676fe76b6d

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

[systemsettings] [Bug 368156] New: No touchpad found

[satoshiakihito via KDE Bugzilla]

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

Bug ID: 368156
   Summary: No touchpad found
   Product: systemsettings
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: satoshiakih...@gmail.com

I am have samsung xe700t1c laptop.
touchpad works onli as mouse, without scroling
in system setting>input devices>touchpad has messege: No touchpad found

Reproducible: Always

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

[konsole] [Bug 368155] New: [Idea] Place additional space between terminal lines.

[Lach Sławomir via KDE Bugzilla]

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

Bug ID: 368155
   Summary: [Idea] Place additional space between terminal lines.
   Product: konsole
   Version: unspecified
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: sla...@lach.art.pl

I asks for possibility of adding space between text lines. In my opinion it
would be very practical option, because pressing enter in konsole window will
send it to virtual terminal and user might need to separate output or input.

Reproducible: Always

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

[krita] [Bug 368111] [appimage] first run *.desktop shortcut creation. Not working and obligatory

[David REVOY via KDE Bugzilla]

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

--- Comment #2 from David REVOY  ---
Created attachment 100897
  --> https://bugs.kde.org/attachment.cgi?id=100897=edit
[screenshot of the feature request]

Hey Probono, thanks for the answer. 
Can this file be auto-generated by the dialog? I attach here a little feature
request/mockup to ease this action.

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

[krita] [Bug 364688] Krita randomly crashes, and makes it impossible to retrieve my work

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #5 from Boudewijn Rempt  ---
I'm sorry, but we cannot do anything else with this report. The behaviour is
not normal and almost certainly caused by something specific to your system.
What that is, is important to determine from a distance.

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

[drkonqi] [Bug 368152] drkonqui fails to report a bug and segfaults

[David via KDE Bugzilla]

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

--- Comment #1 from David  ---
using kubuntu backports PPA packages!

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

[kmail] [Bug 178402] JJ: custom font settings overwritten new message list settings

[Peter Hatina via KDE Bugzilla]

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

Peter Hatina  changed:

   What|Removed |Added

 CC||phat...@gmail.com

--- Comment #18 from Peter Hatina  ---
Running KMail 5.1.3, I also experienced this bug.

The only workaround I found is to manually edit the font settings in kmailrc:
UnreadMessageFont=Monospace,10,-1,5,75,0,0,0,0,0 <- this is bold
UnreadMessageFont=Monospace,10,-1,5,50,0,0,0,0,0 <- this is not

the value 75 defines the bold font.

Please, fix this.

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

[krita] [Bug 368111] [appimage] first run *.desktop shortcut creation. Not working and obligatory

[probono via KDE Bugzilla]

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

probono  changed:

   What|Removed |Added

 CC||prob...@puredarwin.org

--- Comment #1 from probono  ---
If you do not want to be asked by any AppImage whether a desktop file should be
created, then create an empty file at one of these locations:

$HOME/.local/share/appimagekit/no_desktopintegration
/usr/share/appimagekit/no_desktopintegration
/etc/appimagekit/no_desktopintegration

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

[drkonqi] [Bug 368152] New: drkonqui fails to report a bug and segfaults

[David via KDE Bugzilla]

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

Bug ID: 368152
   Summary: drkonqui fails to report a bug and segfaults
   Product: drkonqi
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: spearhead...@gmail.com

After a plasmashell crash which had a 2 star backtrace, after signing I clicked
to sign in dr konqui crashed with this backtrace. (and am essage sorry this
program has no error reporting address associated)

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

Thread 2 (Thread 0x7f26d64b9700 (LWP 24753)):
#0  0x7f26e5a51e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f26e13cdc62 in poll (__timeout=-1, __nfds=1, __fds=0x7f26d64b8bc0)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x162d440, cond=cond@entry=0x162d480,
vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459
#3  0x7f26e13cf8d7 in xcb_wait_for_event (c=0x162d440) at
../../src/xcb_in.c:693
#4  0x7f26d8e3d629 in QXcbEventReader::run (this=0x163ae20) at
qxcbconnection.cpp:1253
#5  0x7f26e614784e in QThreadPrivate::start (arg=0x163ae20) at
thread/qthread_unix.cpp:331
#6  0x7f26e3c2a6fa in start_thread (arg=0x7f26d64b9700) at
pthread_create.c:333
#7  0x7f26e5a5db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f26e958f900 (LWP 24751)):
[KCrash Handler]
#6  QScopedPointer::data
(this=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
#7  qGetPtrHelper (p=...) at
../../include/QtCore/../../src/corelib/global/qglobal.h:983
#8  QDBusAbstractInterface::d_func (this=) at
qdbusabstractinterface.h:148
#9  QDBusAbstractInterface::asyncCallWithArgumentList (this=0x0, method=...,
args=...) at qdbusabstractinterface.cpp:502
#10 0x7f26e81a0864 in KWallet::Wallet::isOpen(QString const&) () from
/usr/lib/x86_64-linux-gnu/libKF5Wallet.so.5
#11 0x00450a0e in BugzillaLoginPage::openWallet
(this=this@entry=0x1ce7d00) at
/build/plasma-workspace-eRmZ8L/plasma-workspace-5.6.5/drkonqi/bugzillaintegration/reportassistantpages_bugzilla.cpp:177
#12 0x00453aca in BugzillaLoginPage::walletLogin (this=0x1ce7d00) at
/build/plasma-workspace-eRmZ8L/plasma-workspace-5.6.5/drkonqi/bugzillaintegration/reportassistantpages_bugzilla.cpp:187
#13 0x7f26e63635b8 in QtPrivate::QSlotObjectBase::call (a=0x7ffdea9b2620,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#14 QSingleShotTimer::timerEvent (this=0x1be4600) at kernel/qtimer.cpp:315
#15 0x7f26e6357e53 in QObject::event (this=0x1be4600, e=) at
kernel/qobject.cpp:1261
#16 0x7f26e6c1b05c in QApplicationPrivate::notify_helper
(this=this@entry=0x1609910, receiver=receiver@entry=0x1be4600,
e=e@entry=0x7ffdea9b2900) at kernel/qapplication.cpp:3716
#17 0x7f26e6c20516 in QApplication::notify (this=0x7ffdea9b2d20,
receiver=0x1be4600, e=0x7ffdea9b2900) at kernel/qapplication.cpp:3499
#18 0x7f26e632862b in QCoreApplication::notifyInternal
(this=0x7ffdea9b2d20, receiver=0x1be4600, event=event@entry=0x7ffdea9b2900) at
kernel/qcoreapplication.cpp:965
#19 0x7f26e637d89d in QCoreApplication::sendEvent (event=0x7ffdea9b2900,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#20 QTimerInfoList::activateTimers (this=0x16933b0) at
kernel/qtimerinfo_unix.cpp:637
#21 0x7f26e637dda1 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:177
#22 0x7f26e32a71a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f26e32a7400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f26e32a74ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f26e637ea9b in QEventDispatcherGlib::processEvents (this=0x167bd10,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#26 0x7f26e6325dea in QEventLoop::exec (this=this@entry=0x7ffdea9b2b40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#27 0x7f26e632de8c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#28 0x7f26e6661c3c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1542
#29 0x7f26e6c17495 in QApplication::exec () at kernel/qapplication.cpp:2976
#30 0x0041d319 in main (argc=18, argv=) at
/build/plasma-workspace-eRmZ8L/plasma-workspace-5.6.5/drkonqi/main.cpp:170

Reproducible: Didn't try

Steps to Reproduce:
1. some app crashes
2. try to report the bug with dr konqui after installing some debugging
packages
3. dr konqui itself crashes

Actual Results:  
drkonqui segfaults

[filelight] [Bug 368154] New: filelight crashes if invoked with a directory parameter

[via KDE Bugzilla]

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

Bug ID: 368154
   Summary: filelight crashes if invoked with a directory
parameter
   Product: filelight
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: p...@kc.rr.com

If I run filelight without any parameters, it crashes with the following
backtrace:
#0  0x7fffe554e313 in RadialMap::Map::paint (this=0x558dd618, 
antialias=)
at /usr/src/debug/filelight-16.08.0/src/part/radialMap/map.cpp:322
#1  0x75db5992 in QWidget::event(QEvent*) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#2  0x75d71a2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /opt/kde/lib64/libQt5Widgets.so.5
#3  0x75d78be1 in QApplication::notify(QObject*, QEvent*) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#4  0x75251688 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /opt/kde/lib64/libQt5Core.so.5
#5  0x75da7ad4 in QWidgetPrivate::propagatePaletteChange() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#6  0x75da7cc5 in QWidgetPrivate::setPalette_helper(QPalette const&) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#7  0x75da7d3e in QWidgetPrivate::resolvePalette() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#8  0x75da7b4c in QWidgetPrivate::propagatePaletteChange() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#9  0x75da7cc5 in QWidgetPrivate::setPalette_helper(QPalette const&) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#10 0x75da7d3e in QWidgetPrivate::resolvePalette() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#11 0x75da7b4c in QWidgetPrivate::propagatePaletteChange() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#12 0x75da7cc5 in QWidgetPrivate::setPalette_helper(QPalette const&) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#13 0x75da7d3e in QWidgetPrivate::resolvePalette() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#14 0x75da7b4c in QWidgetPrivate::propagatePaletteChange() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#15 0x75da7cc5 in QWidgetPrivate::setPalette_helper(QPalette const&) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#16 0x75da7d3e in QWidgetPrivate::resolvePalette() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#17 0x75da7b4c in QWidgetPrivate::propagatePaletteChange() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#18 0x75da7cc5 in QWidgetPrivate::setPalette_helper(QPalette const&) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#19 0x75da7d3e in QWidgetPrivate::resolvePalette() ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#20 0x75db5d2b in QWidget::event(QEvent*) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#21 0x75eabadb in QMainWindow::event(QEvent*) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#22 0x778eb9c7 in KMainWindow::event(QEvent*) ()
   from /opt/kde/lib64/libKF5XmlGui.so.5
#23 0x7792e3f5 in KXmlGuiWindow::event(QEvent*) ()
   from /opt/kde/lib64/libKF5XmlGui.so.5
#24 0x75d71a2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /opt/kde/lib64/libQt5Widgets.so.5
#25 0x75d78be1 in QApplication::notify(QObject*, QEvent*) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#26 0x75251688 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /opt/kde/lib64/libQt5Core.so.5
#27 0x75d74a5b in QApplicationPrivate::setPalette_helper(QPalette
const&, char const*, bool) () from /opt/kde/lib64/libQt5Widgets.so.5
#28 0x7fffe5d07472 in Qt5CTPlatformTheme::applySettings() ()
   from /opt/kde/lib64/qt5/plugins/platformthemes/libqt5ct.so
#29 0x7527c831 in QObject::event(QEvent*) ()
   from /opt/kde/lib64/libQt5Core.so.5
#30 0x75d71a2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /opt/kde/lib64/libQt5Widgets.so.5
#31 0x75d78be1 in QApplication::notify(QObject*, QEvent*) ()
   from /opt/kde/lib64/libQt5Widgets.so.5
#32 0x75251688 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /opt/kde/lib64/libQt5Core.so.5
#33 0x75253cdd in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /opt/kde/lib64/libQt5Core.so.5
#34 0x752a2853 in ?? () from /opt/kde/lib64/libQt5Core.so.5
#35 0x70073ba7 in g_main_context_dispatch ()
   from /opt/gnome/lib64/libglib-2.0.so.0
#36 0x70073dd8 in ?? () from /opt/gnome/lib64/libglib-2.0.so.0
#37 0x70073e7c in g_main_context_iteration ()
   from /opt/gnome/lib64/libglib-2.0.so.0
#38 0x752a2c5f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/kde/lib64/libQt5Core.so.5
#39 0x7524f7ea in
QEventLoop::exec(QFlags) () from

[plasmashell] [Bug 368153] New: Plasma freeze when external device is added

[via KDE Bugzilla]

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

Bug ID: 368153
   Summary: Plasma freeze when external device is added
   Product: plasmashell
   Version: 5.7.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Device Notifier
  Assignee: plasma-b...@kde.org
  Reporter: mhrus...@redhat.com

Plasma is unable to handle when new device is connected - USB or CDROM.
After plasma reset with
p=`ps aux | grep shut-up | grep -v grep | awk '{print $2}'`
for a in $p
do
kill "$a"
done
sleep 2
/usr/bin/plasmashell --shut-up 2>/dev/null &

there is need only for clicking on Most recent Device notifier and Plasma will
crash again.


Reproducible: Always

Steps to Reproduce:
1. insert USB device
or
1. click on Device Notifier

Actual Results:  
Plasma freezes

Expected Results:  
Plasma should proceed

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