date:20160916

[digikam] [Bug 288977] Sync tagged faces with Akonadi

2016-09-16 Thread via KDE Bugzilla

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

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

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from caulier.gil...@gmail.com ---
We have no plan to do it.

Gilles Caulier

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

[digikam] [Bug 365321] Scan + recognize faces does not work.

2016-09-16 Thread via KDE Bugzilla

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

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

   What|Removed |Added

   Version Fixed In||5.2.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from caulier.gil...@gmail.com ---
Since i fixed bugs #366557 and #335013, this dysfunction is not reproducible.

Here i use OpenCV 3.1.0 with Mageia 6, and the detection + recognition option
work as expected. I do not stop immediately as with previous version.

The fix will be published with next 5.2.0 release.

I close this file now.

Gilles Caulier

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

[plasma4] [Bug 366256] Plasma / Nvidia

2016-09-16 Thread Ilya Sheershoff via KDE Bugzilla

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

--- Comment #3 from Ilya Sheershoff  ---
BTW, DrKonqi says bugzilla returned 410, but I've logged in with a just-created
account. Had to copy and post through the web :-)

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #3 from n7d...@gmail.com ---
I am experience a similar (if not the same) issue with Krita 3.0.2 on OSX
10.11.6. Krita was working fine for a couple of hours then then it started to
give an throw an message which says: "Krita could not initialize the OpenGL
canvas: Failed to add vertex shader source from file: matrix_transform.vert
Krita will disable OpenGL and close now". This occurs when creating a custom
document then krita immediately crashes. This only happens when OpenGL is
enabled under preferences > display, otherwise Krita seems to be working fine.

Attached image of the error message and the error report created by OSX when
krita crashes.

Reproducible: Always

Steps to Reproduce:
1. Make sure OpenGL is enabled under preferences > display
2. Open or create a new document
3. Krita will flash an error message then immediately crash

The following is the debug statements that show up in terminal while running
krita and then crashing:

QCoreApplication::arguments: Please instantiate the QApplication object first
krita.lib.pigment: Compiled for arch: 7
krita.lib.pigment: Features supported:
krita.lib.pigment:  "SSE2" --- yes
krita.lib.pigment:  "SSSE3" --- yes
krita.lib.pigment:  "SSE4.1" --- yes
krita.lib.pigment:  "AVX " --- yes
krita.lib.pigment:  "AVX2 " --- yes
Set style "fusion"
OpenGL Info
  Vendor:  Intel Inc.
  Renderer:  Intel(R) Iris(TM) Graphics 6100
  Version:  4.1 INTEL-10.14.73
  Shading language:  4.10
  Requested format:  QSurfaceFormat(version 3.2, options QFlags(),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  1)
  Current format:QSurfaceFormat(version 4.1, options QFlags(),
depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 1, profile  1)
 Version: 4 . 1
 Supports deprecated functions false
krita has opengl true
Setting XDG_DATA_DIRS
"/Users/n7down/Source/kde/dev/i/bin/krita.app/../../share"
Available translations QSet("en_US")
Available domain translations QSet("en_US")
Override language: ""
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 1: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 2: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 3: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 4: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 6: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 7: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 8: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 9: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 11: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 12: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 13: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 14: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 15: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 16: " Invalid entry (missing '=')
"KConfigIni: In file /Users/n7down/Source/kde/dev/i/share/krita/osx.stylesheet,
line 17: " Invalid entry (missing '=')
libpng warning: iCCP: too many profiles
krita.lib.flake: "InteractionTool" : action "object_order_lower" conflicts with
canvas action "rotate_canvas_left" shortcut: "Ctrl+["
krita.lib.flake: "InteractionTool" : action "object_order_raise" conflicts with
canvas action "rotate_canvas_right" shortcut: "Ctrl+]"
krita.lib.flake: "InteractionTool" : action "object_order_lower" conflicts with
canvas action "rotate_canvas_left" shortcut: "Ctrl+["
krita.lib.flake: "InteractionTool" : action "object_order_raise" conflicts with
canvas action "rotate_canvas_right" shortcut: "Ctrl+]"
QOpenGLShader::compile(Vertex): ERROR: 0:1: '' :  version '130' is not
supported
ERROR: 0:2: '' :  #version required and missing.

*** Problematic Vertex shader source code

[plasma4] [Bug 366256] Plasma / Nvidia

2016-09-16 Thread Ilya Sheershoff via KDE Bugzilla

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

Ilya Sheershoff  changed:

   What|Removed |Added

 CC||sheersh...@gmail.com

--- Comment #2 from Ilya Sheershoff  ---
Looks similar:

Application: plasma-desktop (4.11.11)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.16.0-77-generic x86_64
Distribution: Ubuntu 14.04.5 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I booted, started google-chrome with ~280 tabs in ~17 windows, started my app
in docker-compose with ~10 machines launched. the crash happened when I
launched IntelliJ IDEA IDE (~ 6 projects in separate windows opened). Also
several programs was running: System Monitor (ksys...), telegram, skype...
I have an Acer Aspire V (V3-572G-72PX), connected to two monitors (Acer V246HL)
- by HDMI and D-SUB, configured to be by sides of the notebook screen, which is
chosen to be the main screen (the bottom launch bar is in the center).
- Unusual behavior I noticed:
Driver manager, btw, doesn't display that any of the displayed drivers are
chosen. None of the list has the radio button ticked. The provided list is the
following:
  NVIDIA binary drivers:
   - 340.96 from nvidia-340
   - 340.96 from nvidia-340-updates
   - 352.63 from nvidia-352 (Recommended Driver)
   - 352.63 from nvidia-352-updates
  X.Org X Server -- Nouveau display driver from xserver-xorg-video-nouveau
Half and a year ago I had hard time after updating NVIDIA drivers, or switching
to it (can't remember exactly) - the two attached monitors displayed the same
as the main screen (became just a duplicates) or were just black (not sure what
happened first, but there were these two states for sure, may be more states).
I spent a day to recover, so I'm not sure now what driver is running and with
what settings, but I'm not eager to experiment with changing or updating driver
settings.
Started around a month ago: sometimes one of the monitors or windows (they're
mostly full-screen) starts to flicker at left and right sides: around 5% at
left and at right (as far as i managed to notice, one of those where there's no
mouse pointer at the moment). This fixes by focusing on the flickering window
by clicking it.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f850bbb87c0 (LWP 2910))]

Thread 13 (Thread 0x7f84e197c700 (LWP 2935)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8504863ffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f8504864039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f84ff10f184 in start_thread (arg=0x7f84e197c700) at
pthread_create.c:312
#4  0x7f850b4ac37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 12 (Thread 0x7f845b8c9700 (LWP 2940)):
#0  0x7f84fea3f61d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f84fea3f979 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f84fe9fd557 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f84fe9fdf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f84fe9fe0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f85080797be in QEventDispatcherGlib::processEvents
(this=0x7f84540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f850804b0af in QEventLoop::processEvents
(this=this@entry=0x7f845b8c8de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f850804b3a5 in QEventLoop::exec (this=this@entry=0x7f845b8c8de0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f8507f47c5f in QThread::exec (this=this@entry=0x1492cc0) at
thread/qthread.cpp:537
#9  0x7f850802c823 in QInotifyFileSystemWatcherEngine::run (this=0x1492cc0)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f8507f4a32f in QThreadPrivate::start (arg=0x1492cc0) at
thread/qthread_unix.cpp:349
#11 0x7f84ff10f184 in start_thread (arg=0x7f845b8c9700) at
pthread_create.c:312
#12 0x7f850b4ac37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 11 (Thread 0x7f845906a700 (LWP 2941)):
#0  0x7f8507f49058 in QThreadData::current () at
thread/qthread_unix.cpp:249
#1  0x7f8508079af5 in postEventSourcePrepare (s=0x7f844c001350,
timeout=0x7f8459069c24) at kernel/qeventdispatcher_glib.cpp:263
#2  0x7f84fe9fd68d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f84fe9fdf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f84fe9fe0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5

[krita] [Bug 368703] Failed shader compilation causes immediate crash

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #2 from n7d...@gmail.com ---
Created attachment 101133
  --> https://bugs.kde.org/attachment.cgi?id=101133=edit
error message

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

[plasmashell] [Bug 368936] New: Screen Lock happens after waking up from sleep

2016-09-16 Thread Saurabh Minni via KDE Bugzilla

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

Bug ID: 368936
   Summary: Screen Lock happens after waking up from sleep
   Product: plasmashell
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: k...@the100rabh.otherinbox.com
CC: bhus...@gmail.com, plasma-b...@kde.org

After the system has been put to sleep by closing the lid of the laptop it so
happens that the previous screens are visible for more than a few seconds after
the system wakes up. Though no interactions are possible but everything is
visible on the screen. This is a security nightmare under certain condition.

Reproducible: Always

Steps to Reproduce:
1. Put the laptop to sleep after closing the lid while logged in
2. Open the laptop lid to wake up the system. 


Actual Results:  
You can see whatever was visible on the screen when the user was logged in

Expected Results:  
Lock screen should be displayed

Currently for security we have to first lock the screen and then put the system
to sleep

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #1 from n7d...@gmail.com ---
Created attachment 101130
  --> https://bugs.kde.org/attachment.cgi?id=101130=edit
error-report

this is the error-report produced after krita crashes

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

[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer

2016-09-16 Thread ishovkun via KDE Bugzilla

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

ishovkun  changed:

   What|Removed |Added

 CC||igs...@gmail.com

--- Comment #3 from ishovkun  ---
Same issue for me, KDE Neon, KOrganizer 5.3.0.

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

[krita] [Bug 368703] Failed shader compilation causes immediate crash

2016-09-16 Thread via KDE Bugzilla

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

n7d...@gmail.com changed:

   What|Removed |Added

 CC||n7d...@gmail.com

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

[neon] [Bug 368935] New: panel inconsistencies while unplugging/plugging monitors

2016-09-16 Thread via KDE Bugzilla

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

Bug ID: 368935
   Summary: panel inconsistencies while unplugging/plugging
monitors
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [unstable]
  Assignee: neon-b...@kde.org
  Reporter: romulu...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

First I want to say it has improved from user edition, it remember panels
position on a single setup, but still there exist some  problems with
unplugging/plugging monitors, behavior is inconsistent, I will try to explain
it telling my experience... :) 

1. I booted after the install, updated the system, all fine, disabled  a weird
"VGA display" that shows here but did not exist, move external monitor
orientation to the left of my notebook, add 2 panels (the left monitor I put
the panel on left, the wright I put the second panel on wright) and reboot. 

2. After rebooting, all fine (YAY! User edition did not remember the panels
position still). So I unplugged the monitor.

3. When I unplug the monitors, I see no panel "ok, different settings per
display setup maybe, great, it is more flexible!" I thought. So I add a panel
to my "single monitor setup" at left side of screen.

4. Then I plug monitor again and, well... It remembers my "single monitor
setup" panel... Here start the inconsistency, now I have 3 panels with 2
overlapping , on the left side of the left display.

5. Plug, unplug, and well, fine it appears to remember, so I reboot, and the
3th panel goes to the wright of the second monitor.



Reproducible: Always


Actual Results:  
Inconsistent behavior, It remember or not settings, they are disconnected? At
the moment it is a mix.

Expected Results:  
I liked when I thought that plugging or unplugging a monitor plasma get a
completely different set of settings (panels, their positions, widgets, display
monitor settings, position, what is enabled and not), but it need to be well
defined, when plugging, forget panels form "single monitor setup", when
unplugging, forget "dual monitor setup" and restore "single monitor setup".

This is my Opinion, but I will be pretty much happy if plasma stay consistent
any way (remember display characteristic... if it has only one panel, in any
setup this monitor stay the same)

It can be useful to know my external monitor is 2560x1080 and the notebook one
is 1920x1080.

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

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

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #24 from masterofex...@hotmail.com ---
Looking at the docs, it seems most of the ciphers were introduced in APIs 9
(name change), 11, & 20.  Perhaps a second API 11 cipher will round out your
list -- 2 for each major API vis-à-vis SSLSocket.  Perhaps, just to pick one,
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA?

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

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

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #23 from masterofex...@hotmail.com ---
The following patch to the android app worked for me:

diff --git a/src/org/kde/kdeconnect/Helpers/SecurityHelpers/SslHelper.java
b/src/org/kde/kdeconnect/Helpers/SecurityHelpers/SslHelper.java
index 5742329..b0ebda0 100644
--- a/src/org/kde/kdeconnect/Helpers/SecurityHelpers/SslHelper.java
+++ b/src/org/kde/kdeconnect/Helpers/SecurityHelpers/SslHelper.java
@@ -209,9 +209,13 @@ public class SslHelper {
 // These cipher suites are most common of them that are accepted by
kde and android during handshake
 ArrayList supportedCiphers = new ArrayList<>();
 if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
-supportedCiphers.add("TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384");
-supportedCiphers.add("TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256");
-supportedCiphers.add("TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA");
+supportedCiphers.add("TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384"); 
// API 20+
+supportedCiphers.add("TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256"); 
// API 20+
+supportedCiphers.add("TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA");  
// API 11+
+} else if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.HONEYCOMB) {
+supportedCiphers.add("TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA");  //
API 11+
+supportedCiphers.add("SSL_RSA_WITH_RC4_128_SHA");//
API 9+
+supportedCiphers.add("SSL_RSA_WITH_RC4_128_MD5");//
API 9+
 } else {
 // Following ciphers are for and due to old devices
 supportedCiphers.add("SSL_RSA_WITH_RC4_128_SHA");


Is there a better way to submit it?

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

[konqueror] [Bug 368705] Port to Qt5 and Add webEngine

2016-09-16 Thread Christoph Feck via KDE Bugzilla

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

--- Comment #3 from Christoph Feck  ---
Regarding QtWebKit, please see
http://qtwebkit.blogspot.de/2016/08/qtwebkit-im-back.html

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

[kdevelop] [Bug 368928] crash while quitting KDevelop with a debug session still open

2016-09-16 Thread Christoph Feck via KDE Bugzilla

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

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |5.0.0
Product|kde |kdevelop
   Assignee|unassigned-b...@kde.org |kdevelop-bugs-n...@kde.org
  Component|general |general

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

[systemsettings] [Bug 368934] New: kde control center crashed on exit

2016-09-16 Thread Mathias Homann via KDE Bugzilla

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

Bug ID: 368934
   Summary: kde control center crashed on exit
   Product: systemsettings
   Version: 5.7.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mathias.hom...@opensuse.org

Application: systemsettings5 (5.7.5)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
closing kde control center after trying to get akonadi to work

-- Backtrace:
Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7806e90780 (LWP 4441))]

Thread 3 (Thread 0x7f77dc5b3700 (LWP 4476)):
#0  0x7f7802c37ccd in read () at /lib64/libc.so.6
#1  0x7f77fa660073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.44
#2  0x7f77fce98b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f77fce57999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f77fce57df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f77fce5819a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#6  0x7f77dd378426 in  () at /usr/lib64/libgio-2.0.so.0
#7  0x7f77fce7cf65 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f77fed780a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f7802c4402d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f77ea719700 (LWP )):
#0  0x7f7802c3bbfd in poll () at /lib64/libc.so.6
#1  0x7f77fce57e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f77fce57f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7803540f7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f78034f08cb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f780333706a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f7803e444b5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f780333b899 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f77fed780a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f7802c4402d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7806e90780 (LWP 4441)):
[KCrash Handler]
#6  0x7f77db4eb0a0 in  () at /usr/lib64/libtelepathy-qt5.so.0
#7  0x7f77db4ef6da in  () at /usr/lib64/libtelepathy-qt5.so.0
#8  0x7f77db4cf7b5 in  () at /usr/lib64/libtelepathy-qt5.so.0
#9  0x7f77db4cfe7d in Tp::Connection::~Connection() () at
/usr/lib64/libtelepathy-qt5.so.0
#10 0x7f77db4cfed9 in Tp::Connection::~Connection() () at
/usr/lib64/libtelepathy-qt5.so.0
#11 0x7f77db3fd09d in  () at /usr/lib64/libtelepathy-qt5.so.0
#12 0x7f77db3fd21d in Tp::Account::~Account() () at
/usr/lib64/libtelepathy-qt5.so.0
#13 0x7f77db3fd279 in Tp::Account::~Account() () at
/usr/lib64/libtelepathy-qt5.so.0
#14 0x7f77db41c10f in  () at /usr/lib64/libtelepathy-qt5.so.0
#15 0x7f7803397619 in QHashData::free_helper(void (*)(QHashData::Node*)) ()
at /usr/lib64/libQt5Core.so.5
#16 0x7f77db4164f4 in  () at /usr/lib64/libtelepathy-qt5.so.0
#17 0x7f77db41653d in Tp::AccountManager::~AccountManager() () at
/usr/lib64/libtelepathy-qt5.so.0
#18 0x7f77db416599 in Tp::AccountManager::~AccountManager() () at
/usr/lib64/libtelepathy-qt5.so.0
#19 0x7f77dbba9100 in  () at
/usr/lib64/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so
#20 0x7f77dbba91f9 in  () at
/usr/lib64/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so
#21 0x7f77ddea3ebe in  () at /usr/lib64/qt5/plugins/kcm_kaccounts.so
#22 0x7f77ddea3f59 in  () at /usr/lib64/qt5/plugins/kcm_kaccounts.so
#23 0x7f7802b96b39 in __run_exit_handlers () at /lib64/libc.so.6
#24 0x7f7802b96b85 in  () at /lib64/libc.so.6
#25 0x7f7802b80b2c in __libc_start_main () at /lib64/libc.so.6
#26 0x0040cd89 in _start () at ../sysdeps/x86_64/start.S:122

Reported using DrKonqi

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

[plasmashell] [Bug 368933] New: Plasma crashed after clicking system tray icon

2016-09-16 Thread Franco Pellegrini via KDE Bugzilla

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

Bug ID: 368933
   Summary: Plasma crashed after clicking system tray icon
   Product: plasmashell
   Version: 5.6.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: frap...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.5)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-36-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

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

After configuring the entries to show in the system tray, I saved the settings.
Afterwards, I clicked in the icon for themounted devices, and Plasma crashed
and restarted.

Could not reproduce it and settings were saved fine.

The crash does not seem to be reproducible.

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

Thread 12 (Thread 0x7f5e3cc7f700 (LWP 3368)):
#0  0x7f5f1c10d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5f1d036aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f5f2030e92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f5f2030f1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f5f1d03584e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f1c1076fa in start_thread (arg=0x7f5e3cc7f700) at
pthread_create.c:333
#6  0x7f5f1c93eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f5e3ede6700 (LWP 3190)):
#0  0x7f5f1c10d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5f1d036aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f5f2030e92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f5f2030f1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f5f1d03584e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f1c1076fa in start_thread (arg=0x7f5e3ede6700) at
pthread_create.c:333
#6  0x7f5f1c93eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f5e5248f700 (LWP 2988)):
#0  0x7f5f1c10d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5f1d036aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f5f2030e92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f5f2030f1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f5f1d03584e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f1c1076fa in start_thread (arg=0x7f5e5248f700) at
pthread_create.c:333
#6  0x7f5f1c93eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f5e532af700 (LWP 2985)):
#0  0x7f5f196a6ae4 in g_mutex_unlock (mutex=0x7f5e4c000990) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gthread-posix.c:1347
#1  0x7f5f19661dc9 in g_main_context_check
(context=context@entry=0x7f5e4c000990, max_priority=2147483647,
fds=fds@entry=0x7f5e4c004cc0, n_fds=n_fds@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3679
#2  0x7f5f19662340 in g_main_context_iterate
(context=context@entry=0x7f5e4c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3837
#3  0x7f5f196624ac in g_main_context_iteration (context=0x7f5e4c000990,
may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f5f1d26ca9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f1d213dea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5f1d0308a4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5e557c77d7 in KCupsConnection::run() () at
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#8  0x7f5f1d03584e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f5f1c1076fa in start_thread (arg=0x7f5e532af700) at
pthread_create.c:333
#10 0x7f5f1c93eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f5e6b014700 (LWP 2568)):
#0  0x7f5f1c10d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5f1d036aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2

[krita] [Bug 368932] Sometimes, when I open Krita, the tools I have chosen have disappeared and I have to input which tools I want to use again.

2016-09-16 Thread via KDE Bugzilla

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

kkush4...@gmail.com changed:

   What|Removed |Added

   Platform|Windows CE  |unspecified

--- Comment #1 from kkush4...@gmail.com ---
The computer is a Windows 10.

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

[krita] [Bug 368932] New: Sometimes, when I open Krita, the tools I have chosen have disappeared and I have to input which tools I want to use again.

2016-09-16 Thread via KDE Bugzilla

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

Bug ID: 368932
   Summary: Sometimes, when I open Krita, the tools I have chosen
have disappeared and I have to input which tools I
want to use again.
   Product: krita
   Version: unspecified
  Platform: Windows CE
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: kkush4...@gmail.com

When I open Krita, all my tools I have selected have disappeared, and all I see
is a gray screen. Now, I have to select all my tools again, and this happens
frequently, so its tedious to do it again.

Reproducible: Sometimes

Steps to Reproduce:
1. Select tools I want to use 
2. Close Krita 
3. Open Krita

Actual Results:  
All I see is a gray screen, and I have to select all my tools I selected
already again.

Expected Results:  
Krita should save what tools I selected to use, and keep them there for the
next time I open Krita.

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

[systemsettings] [Bug 364321] No ability to switch from JEDEC to SI units in Plasma 5.x (KDE Frameworks Version : 5.22.0 / Qt 5.6.0)

2016-09-16 Thread via KDE Bugzilla

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

xaxa...@gmail.com changed:

   What|Removed |Added

 CC||xaxa...@gmail.com

--- Comment #7 from xaxa...@gmail.com ---
SI should be an option as metric is easiest for people. IMHO this should be the
default but MHO isn't particularly important.
IEC should be an option (there are times when it's useful, e.g. counting disk
"pages"). For that matter, hexidecimal is useful with IEC.

However - from a quote on Wikipedia
(https://en.wikipedia.org/wiki/Binary_prefix):

The International Bureau of Weights and Measures (BIPM), which maintains the
International System of Units (SI), expressly prohibits the use of SI prefixes
to denote binary multiples, and recommends the use of the IEC prefixes as an
alternative since units of information are not included in SI.

So using JEDEC would be against their wishes, and they're the authority on
these matters.


Also, can you please make a special one for me with capital Kilo :)

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

[konsole] [Bug 346450] Remove 1px margin [patch included]

2016-09-16 Thread Kurt Hindenburg via KDE Bugzilla

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kons
   ||ole/8e5a5b1ec1fb68e359319c9
   ||ce23a43c0434b836a
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Kurt Hindenburg  ---
Git commit 8e5a5b1ec1fb68e359319c9ce23a43c0434b836a by Kurt Hindenburg.
Committed on 17/09/2016 at 01:57.
Pushed by hindenburg into branch 'master'.

Allow profile to set margin and center flag

These 2 were hard coded - this allow them to be set in the profile.
There is currently no UI for these; add these to profile:

[General]
TerminalMargin=1
TerminalCenter=false

Thanks to Josef Kufner jk frozen doe net for patch

It appears the center flag doesn't work and perhaps hasn't for a long
time.

M  +4-0src/Profile.cpp
M  +14   -0src/Profile.h
M  +3-0src/TerminalDisplay.cpp
M  +3-3src/ViewManager.cpp

http://commits.kde.org/konsole/8e5a5b1ec1fb68e359319c9ce23a43c0434b836a

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

[plasmashell] [Bug 349289] Crash in Plotter::render

2016-09-16 Thread via KDE Bugzilla

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

wonderbread...@gmail.com changed:

   What|Removed |Added

 CC||wonderbread...@gmail.com

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

[krunner] [Bug 365248] Krunner crash when typing first letter or clicking setting button

2016-09-16 Thread Frabcisco Cribari via KDE Bugzilla

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

Frabcisco Cribari  changed:

   What|Removed |Added

 CC||crib...@gmail.com

--- Comment #13 from Frabcisco Cribari  ---
I am experiencing Plasma crashes when typing to search in the application
launcher (not menu or dashboard). It may be related to this bug. See
https://bugs.kde.org/show_bug.cgi?id=366022 and
https://bugs.kde.org/show_bug.cgi?id=366190 .

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

[plasmashell] [Bug 362131] Heavily dIstorted graphics when running KDE on Wayland

2016-09-16 Thread João Bóia via KDE Bugzilla

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

João Bóia  changed:

   What|Removed |Added

 CC||joaomiguelb...@gmail.com

--- Comment #8 from João Bóia  ---
Still present on 5.7.95
AMD RX460 on amdgpu 1.1.1 + Mesa 12.0.3

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

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

2016-09-16 Thread Greg White via KDE Bugzilla

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

Greg White  changed:

   What|Removed |Added

 CC||gwh...@kupulau.com

--- Comment #74 from Greg White  ---
I'm seeing this same behavior with plasma 5.8 beta.  A black screen on one
monitor, and the only fix is to restart plasma.

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

[systemsettings] [Bug 345234] Adding/Removing fonts shows wait dialog forever

2016-09-16 Thread orbayo via KDE Bugzilla

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

orbayo  changed:

   What|Removed |Added

 CC||carlosa...@gmail.com

--- Comment #20 from orbayo  ---
I copied my folder with my collection of type fonts on the route

/usr/share/fonts/personalfonts

Now the whole system is super slow, my opensuse 42.1 KDE is now useless.

I tried to do it with systemsettings5 and the same problem.  If you install the
fonts only for a single user the laggy is less. And the same problem with Linux
Mint KDE 18. 

if you add new fonts you  lose the system, I need the fonts to work ..

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

[kdenlive] [Bug 364559] Changing project settings and saving crashes the software

2016-09-16 Thread Jean-Baptiste Mardelle via KDE Bugzilla

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

--- Comment #11 from Jean-Baptiste Mardelle  ---
You're welcome, I hope this fixes the issue you had. Of course we try to read
the bug reports, they are very welcome and helpful, especially if you can give
us instructions to reproduce. We are a very small team so not all issues get
solved as fast as we would like but please report your issue!

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

[kdenlive] [Bug 364559] Changing project settings and saving crashes the software

2016-09-16 Thread YEK via KDE Bugzilla

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

--- Comment #10 from YEK  ---
Thanks for fixing that bug Jean-Baptiste. 

I am aware of another bug in Kdenlive 16.04 which I can easily replicate on my
Linux machine. If I were to create a bug report would you or one of the other
developers read it?

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

[kmail2] [Bug 350219] Kmail can't create IMAP top level folders

2016-09-16 Thread via KDE Bugzilla

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

h...@gmx.de changed:

   What|Removed |Added

 CC||h...@gmx.de

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

[krusader] [Bug 368931] New: Please release a fresh version > 2.4.0-beta3

2016-09-16 Thread Angelos Pikoulas via KDE Bugzilla

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

Bug ID: 368931
   Summary: Please release a fresh version > 2.4.0-beta3
   Product: krusader
   Version: Git
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: agelos.pikou...@gmail.com

All we Krusader user out there will appreciate a fresh new build of Krusader >
2.4.0-beta3
Even if its Alpha, as long as it is stable in what it does, it will be just
great!

Reproducible: Always

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

[skrooge] [Bug 365724] Driver not loaded Driver not loaded

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #6 from mspada...@yahoo.com ---
I installed 2.4.92 from your repo and it still crashes on startup.  Backtrace:

Application: Skrooge (skrooge), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f107b781800 (LWP 2059))]

Thread 9 (Thread 0x7f1008dab700 (LWP 2069)):
#0  0x7f10787b3bfd in poll () from /lib64/libc.so.6
#1  0x7f1071555e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f1071555f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f10790b8f7b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f10790688cb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f1078eaf06a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f1078eb3899 in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f10731820a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7f10787bc02d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f1009a09700 (LWP 2068)):
#0  0x7f107318603f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f106ff68443 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f107028a0a1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f10731820a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f10787bc02d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f100a20a700 (LWP 2067)):
#0  0x7f107318603f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f106ff68443 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f107028a0a1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f10731820a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f10787bc02d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f100aa0b700 (LWP 2066)):
#0  0x7f107318603f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f106ff68443 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f107028a0a1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f10731820a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f10787bc02d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f100b20c700 (LWP 2065)):
#0  0x7f107318603f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f106ff6746d in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f107028a0a1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f10731820a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f10787bc02d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f104c9ad700 (LWP 2064)):
#0  0x7f107318603f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f107025b5d3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f107025b5f9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f10731820a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f10787bc02d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f105cc99700 (LWP 2061)):
#0  0x7f10787b3bfd in poll () from /lib64/libc.so.6
#1  0x7f1071555e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f1071555f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f10790b8f7b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f10790688cb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f1078eaf06a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f10745e54b5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f1078eb3899 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f10731820a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f10787bc02d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f105e61a700 (LWP 2060)):
#0  0x7f10787b3bfd in poll () from /lib64/libc.so.6
#1  0x7f106956c422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f106956e00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f106054a3e9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f1078eb3899 in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f10731820a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f10787bc02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f107b781800 (LWP 2059)):
[KCrash Handler]
#6  QWidget::layout (this=0x0) at kernel/qwidget.cpp:10059
#7  0x7f107b31d9e3 in SKGMainPanel::displayMessage(QString const&,
SKGDocument::MessageType, QString const&) () from /usr/lib64/libskgbasegui.so.2
#8  0x7f107b31e009 in SKGMainPanel::displayErrorMessage(SKGError const&,
QAction*) () from /usr/lib64/libskgbasegui.so.2
#9  0x7f100224cca5 in SKGFilePlugin::onNew() () from
/usr/lib64/qt5/plugins/skg_file.so
#10 0x7f100224d6ac in SKGFilePlugin::setupActions(SKGDocument*, QStringList
const&) () from /usr/lib64/qt5/plugins/skg_file.so
#11 0x7f107b32ef93 in SKGMainPanel::SKGMainPanel(QSplashScreen*,
SKGDocument*,

[kdevelop] [Bug 368603] crash when starting an lldb debug session

2016-09-16 Thread Aetf via KDE Bugzilla

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

--- Comment #18 from Aetf <7437...@gmail.com> ---
I'm glad you found the reason. So the patch itself works for you now? If so,
I'm going to close this and push the change to master.

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

[konqueror] [Bug 368930] New: Konqueror crashes on aarch64

2016-09-16 Thread Paul Whalen via KDE Bugzilla

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

Bug ID: 368930
   Summary: Konqueror crashes on aarch64
   Product: konqueror
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: pwha...@redhat.com

Application: konqueror (4.14.23)
KDE Platform Version: 4.14.24 (Compiled from sources)
Qt Version: 4.8.7
Operating System: Linux 4.8.0-0.rc5.git1.1.fc25.aarch64 aarch64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed
Attempting to watch a video on youtube, crashes during normal usage.

The crash can be reproduced every time.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
86T_PSEUDO_END (SYSCALL_SYMBOL)
[Current thread is 1 (Thread 0x3ff7c0aa2c0 (LWP 5546))]

Thread 3 (Thread 0x3ff6b32f000 (LWP 5552)):
#0  0x03ff7dd4d674 in __pthread_cond_wait (cond=cond@entry=0x2aaed4ad940,
mutex=mutex@entry=0x2aaed4ad910) at pthread_cond_wait.c:186
#1  0x03ff6fde7fe4 in WTF::ThreadCondition::wait
(this=this@entry=0x2aaed4ad940, mutex=...) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:379
#2  0x03ff6fc487c0 in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x2aaed4ad800) at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#3  0x03ff6fde7a3c in WTF::wtfThreadEntryPoint (param=0x2aaed3df530) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#4  0x03ff7dd47174 in start_thread (arg=0x3ffe4f250af) at
pthread_create.c:335
#5  0x03ff7ce83ee8 in thread_start () at
../sysdeps/unix/sysv/linux/aarch64/clone.S:87

Thread 2 (Thread 0x3ff6bd7f000 (LWP 5548)):
#0  QBasicAtomicInt::operator!= (value=14, this=0x3ff6400dd60) at
../../src/corelib/thread/qbasicatomic.h:75
#1  postEventSourcePrepare (s=0x3ff6400dd00, timeout=0x3ff6bd7e57c,
timeout@entry=0x1) at kernel/qeventdispatcher_glib.cpp:283
#2  0x03ff7c3bc098 in g_main_context_prepare
(context=context@entry=0x3ff640009a0, priority=0x3ff640009a0,
priority@entry=0x3ff6bd7e640) at gmain.c:3499
#3  0x03ff7c3bca9c in g_main_context_iterate
(context=context@entry=0x3ff640009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3907
#4  0x03ff7c3bcc94 in g_main_context_iteration (context=0x3ff640009a0,
may_block=may_block@entry=1) at gmain.c:3988
#5  0x03ff7df48f44 in QEventDispatcherGlib::processEvents
(this=0x3ff640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x03ff7df15dfc in QEventLoop::processEvents
(this=this@entry=0x3ff6bd7e778, flags=...) at kernel/qeventloop.cpp:149
#7  0x03ff7df16188 in QEventLoop::exec (this=this@entry=0x3ff6bd7e778,
flags=...) at kernel/qeventloop.cpp:204
#8  0x03ff7de0c694 in QThread::exec (this=) at
thread/qthread.cpp:538
#9  0x03ff7de0f5a8 in QThreadPrivate::start (arg=0x2aaed086050) at
thread/qthread_unix.cpp:352
#10 0x03ff7dd47174 in start_thread (arg=0x3ffe4f2613f) at
pthread_create.c:335
#11 0x03ff7ce83ee8 in thread_start () at
../sysdeps/unix/sysv/linux/aarch64/clone.S:87

Thread 1 (Thread 0x3ff7c0aa2c0 (LWP 5546)):
[KCrash Handler]
#5  JSC::BlockAllocator::allocate (this=0xc0) at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.h:242
#6  JSC::WeakSet::addAllocator (this=0x3ff696e0148) at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/WeakSet.cpp:76
#7  0x03ff6ea424d8 in JSC::WeakSet::allocate () at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/WeakSetInlines.h:38
#8  JSC::PassWeak::PassWeak () at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/PassWeak.h:119
#9  WebCore::JSEventListener::JSEventListener () at
/usr/src/debug/webkit-qtwebkit-23/Source/WebCore/bindings/js/JSEventListener.cpp:46
#10 0x03ff6ea2f548 in WebCore::JSEventListener::create () at
/usr/src/debug/webkit-qtwebkit-23/Source/WebCore/bindings/js/JSEventListener.h:36
#11 WebCore::JSDOMWindow::addEventListener () at
/usr/src/debug/webkit-qtwebkit-23/Source/WebCore/bindings/js/JSDOMWindowCustom.cpp:750
#12 0x03ff6f8d72a4 in WebCore::jsDOMWindowPrototypeFunctionAddEventListener
() at generated/JSDOMWindow.cpp:12990
#13 0x03ff6fc74aac in JSC::LLInt::CLoop::execute (callFrame=0x3ff6a712d18,
bootstrapOpcodeId=JSC::op_create_activation,
bootstrapOpcodeId@entry=JSC::llint_program_prologue, isInitializationPass=96,
isInitializationPass@entry=false) at generated/LLIntAssembly.h:6253
#14 0x03ff6fc63e20 in JSC::Interpreter::execute (this=,
program=program@entry=0x3ff699171a0, callFrame=callFrame@entry=0x3ff6a6df388,
thisObj=) at

[www.kde.org] [Bug 368929] New: SSL certificate *.kde.org is vulnerable to DROWN attack

2016-09-16 Thread Thomas Bettler via KDE Bugzilla

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

Bug ID: 368929
   Summary: SSL certificate *.kde.org is vulnerable to DROWN
attack
   Product: www.kde.org
   Version: unspecified
  Platform: unspecified
   URL: https://www.ssllabs.com/ssltest/analyze.html?d=kde.org
=91.189.93.5#drownTable
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: thomas.bett...@gmail.com

According to https://test.drownattack.com/?site=212.110.188.12
developer.kde.org provides mail services via SSLv2 using the same SSL
certificate as kde.org does.

These servers reusing the same RSA keys render the SSL encryption vulnerable to
the DROWN attack. https://drownattack.com/drown-attack-paper.pdf

Reproducible: Always


Actual Results:  
see
https://www.ssllabs.com/ssltest/analyze.html?d=kde.org=91.189.93.5#drownTable

Expected Results:  
no vulnerability

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

[kde] [Bug 368928] New: crash while quitting KDevelop with a debug session still open

2016-09-16 Thread RJVB via KDE Bugzilla

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

Bug ID: 368928
   Summary: crash while quitting KDevelop with a debug session
still open
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: rjvber...@gmail.com

Application: kdevelop5 (5.0.0)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.5.7-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS

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

I had been testing the debugging of a simple Qt5 application using the lldb
plugin and lldb-mi-3.9 .
When that session became unresponsive due to excessive memory usage by the
debugger I first hit the Stop All toolbar button, and then KDevelop's window
close button before the debug session (and view) had been closed completely.

- Unusual behaviour I noticed:

My whole plasma (4) desktop had come down except for KWin.

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

Thread 5 (Thread 0x7f8cd6bbf700 (LWP 15416)):
#0  0x7f8cf4500fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f8ce7619b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f8ce761b64f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f8cd9835ac9 in QXcbEventReader::run (this=0x1c67df0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1325
#4  0x7f8cf4bafd29 in QThreadPrivate::start (arg=0x1c67df0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/thread/qthread_unix.cpp:341
#5  0x7f8cee2bb184 in start_thread (arg=0x7f8cd6bbf700) at
pthread_create.c:312
#6  0x7f8cf450e37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f8cd56c6700 (LWP 15417)):
#0  0x7f8ced47761a in g_mutex_get_impl (mutex=0x7f8cc8000990) at
/build/buildd/glib2.0-2.40.2/./glib/gthread-posix.c:120
#1  0x7f8ced4779a9 in g_mutex_unlock (mutex=mutex@entry=0x7f8cc8000990) at
/build/buildd/glib2.0-2.40.2/./glib/gthread-posix.c:228
#2  0x7f8ced435ef6 in g_main_context_iterate
(context=context@entry=0x7f8cc8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3712
#3  0x7f8ced4360ec in g_main_context_iteration (context=0x7f8cc8000990,
may_block=may_block@entry=1) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3795
#4  0x7f8cf4dcb6fb in QEventDispatcherGlib::processEvents
(this=0x7f8cc80008c0, flags=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:419
#5  0x7f8cf4d7562a in QEventLoop::exec (this=this@entry=0x7f8cd56c5e20,
flags=..., flags@entry=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qeventloop.cpp:204
#6  0x7f8cf4bab01b in QThread::exec (this=this@entry=0x7f8cf6bb2420
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/thread/qthread.cpp:500
#7  0x7f8cf6941615 in QDBusConnectionManager::run (this=0x7f8cf6bb2420
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/dbus/qdbusconnection.cpp:189
#8  0x7f8cf4bafd29 in QThreadPrivate::start (arg=0x7f8cf6bb2420 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/thread/qthread_unix.cpp:341
#9  0x7f8cee2bb184 in start_thread (arg=0x7f8cd56c6700) at
pthread_create.c:312
#10 0x7f8cf450e37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f8cc4926700 (LWP 15422)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f8cf4bb0a66 in wait_relative (time=1000, this=0x25a1310) at

[kdeconnect] [Bug 368812] Kdeconnect forgets paired devices

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #1 from accel...@yandex.com ---
I have the same bug. Android client forgets my computer every time it is force
stopped. looks like it also forgets device if killed by Android watchdog.

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

[kdevelop] [Bug 368603] crash when starting an lldb debug session

2016-09-16 Thread RJVB via KDE Bugzilla

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

--- Comment #17 from RJVB  ---
Thanks, but I just found the reason when I tried a manual debugging session.
Turns out it's more a bug in the lldb-3.9 package: it doesn't install
non-versioned binaries, but it wants an lldb-server executable.

That also explains why it worked before (when I still had a working ll**-3.8
install) and no longer after I upgraded to 3.9.0 . I noticed the issue just too
long after that upgrade so I didn't make the link (mental link, not symlink)
:-/

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

[kdeconnect] [Bug 368812] Kdeconnect forgets paired devices

2016-09-16 Thread via KDE Bugzilla

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

accel...@yandex.com changed:

   What|Removed |Added

 CC||accel...@yandex.com

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

[valgrind] [Bug 368925] New: WARNING: unhandled arm64-linux syscall: 130

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368925
   Summary: WARNING: unhandled arm64-linux syscall: 130
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=tkill01_valgrind_memory_leak_check stime=1473976160
cmdline=" valgrind -q --leak-check=full --trace-children=yes tkill01"
contacts=""
analysis=exit
<<>>
--30021-- WARNING: unhandled arm64-linux syscall: 130
--30021-- You may be able to write your own handler.
--30021-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--30021-- Nevertheless we consider this a bug.  Please report
--30021-- it at http://valgrind.org/support/bug_reports.html.
tkill01 1  TCONF  :  tkill01.c:96: syscall(130) __NR_tkill not supported on
your arch
tkill01 2  TCONF  :  tkill01.c:96: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=46 cstime=2
<<>>


Reproducible: Always

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

[plasmashell] [Bug 368927] New: Menu crash

2016-09-16 Thread vlozano via KDE Bugzilla

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

Bug ID: 368927
   Summary: Menu crash
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: vlozan...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (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:
I just search for Dolphin application in the menu and the menu crash

The crash can be reproduced sometimes.

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

Thread 15 (Thread 0x7fd027869700 (LWP 8638)):
#0  0x7fd1022c303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd1031b134b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fd04e33865f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fd04e33c43a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fd04e33c481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fd04e33c481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fd04e33c481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fd04e33c481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7fd04e33c481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7fd04e33c481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7fd04e33c481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#19 0x7fd04e33c481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#20 0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#21 0x7fd04e33a005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#22 0x7fd1031b032f in  () at /usr/lib64/libQt5Core.so.5
#23 0x7fd1022bf0a4 in start_thread () at /lib64/libpthread.so.0
#24 0x7fd102abe02d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fd02806a700 (LWP 8637)):
#0  0x7fd1022c303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd1031b134b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fd04e33865f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fd04e33c43a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fd04e33a005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fd1031b032f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fd1022bf0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fd102abe02d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fd02886b700 (LWP 8636)):
#0  0x7fd1022c303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd1031b134b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fd04e33865f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fd04e33c43a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fd04e3366cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5

[valgrind] [Bug 368926] New: WARNING: unhandled arm64-linux syscall: 97

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368926
   Summary: WARNING: unhandled arm64-linux syscall: 97
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=unshare01_valgrind_memory_leak_check stime=1473976179
cmdline=" valgrind -q --leak-check=full --trace-children=yes unshare01"
contacts=""
analysis=exit
<<>>
--30118-- WARNING: unhandled arm64-linux syscall: 97
--30118-- You may be able to write your own handler.
--30118-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--30118-- Nevertheless we consider this a bug.  Please report
--30118-- it at http://valgrind.org/support/bug_reports.html.
unshare011  TCONF  :  unshare01.c:198: unshare not supported in kernel
unshare012  TCONF  :  unshare01.c:198: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=51 cstime=3
<<>>


Reproducible: Always

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

[valgrind] [Bug 368924] New: WARNING: unhandled arm64-linux syscall: 84

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368924
   Summary: WARNING: unhandled arm64-linux syscall: 84
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sync_file_range01_valgrind_memory_leak_check stime=1473975067
cmdline=" valgrind -q --leak-check=full --trace-children=yes sync_file_range01"
contacts=""
analysis=exit
<<>>
--27072-- WARNING: unhandled arm64-linux syscall: 84
--27072-- You may be able to write your own handler.
--27072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--27072-- Nevertheless we consider this a bug.  Please report
--27072-- it at http://valgrind.org/support/bug_reports.html.
sync_file_range011  TCONF  :  sync_file_range01.c:221: syscall(84)
__NR_sync_file_range not supported on your arch
sync_file_range012  TCONF  :  sync_file_range01.c:221: Remaining cases not
appropriate for configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=46 cstime=2
<<>>


Reproducible: Always

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

[valgrind] [Bug 368923] New: WARNING: unhandled arm64-linux syscall: 268

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368923
   Summary: WARNING: unhandled arm64-linux syscall: 268
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=setns01_valgrind_memory_leak_check stime=1473974802
cmdline=" valgrind -q --leak-check=full --trace-children=yes setns01"
contacts=""
analysis=exit
<<>>
--26151-- WARNING: unhandled arm64-linux syscall: 268
--26151-- You may be able to write your own handler.
--26151-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26151-- Nevertheless we consider this a bug.  Please report
--26151-- it at http://valgrind.org/support/bug_reports.html.
setns01 1  TCONF  :  setns01.c:209: syscall(268) __NR_setns not supported
on your arch
setns01 2  TCONF  :  setns01.c:209: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=61 cstime=2
<<>>
<<>>
tag=setns01_valgrind_thread_concurrency_check stime=1473974803
cmdline=" valgrind -q --tool=helgrind --trace-children=yes setns01"
contacts=""
analysis=exit
<<>>
--26158-- WARNING: unhandled arm64-linux syscall: 268
--26158-- You may be able to write your own handler.
--26158-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26158-- Nevertheless we consider this a bug.  Please report
--26158-- it at http://valgrind.org/support/bug_reports.html.
setns01 1  TCONF  :  setns01.c:209: syscall(268) __NR_setns not supported
on your arch
setns01 2  TCONF  :  setns01.c:209: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=35 cstime=3
<<>>


Reproducible: Always

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

[valgrind] [Bug 368922] New: WARNING: unhandled arm64-linux syscall: 161

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368922
   Summary: WARNING: unhandled arm64-linux syscall: 161
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sethostname01_valgrind_memory_leak_check stime=1473974797
cmdline=" valgrind -q --leak-check=full --trace-children=yes sethostname01"
contacts=""
analysis=exit
<<>>
--26133-- WARNING: unhandled arm64-linux syscall: 161
--26133-- You may be able to write your own handler.
--26133-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26133-- Nevertheless we consider this a bug.  Please report
--26133-- it at http://valgrind.org/support/bug_reports.html.
--26133-- WARNING: unhandled arm64-linux syscall: 161
--26133-- You may be able to write your own handler.
--26133-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26133-- Nevertheless we consider this a bug.  Please report
--26133-- it at http://valgrind.org/support/bug_reports.html.
sethostname011  TFAIL  :  sethostname01.c:105: sethostname() failed ,
errno=38 : Function not implemented
sethostname010  TWARN  :  sethostname01.c:152: sethostname() failed while
restoring hostname to "pinkiepie.local": Function not implemented
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=5 corefile=no
cutime=45 cstime=1
<<>>


Reproducible: Always

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

[valgrind] [Bug 368916] New: WARNING: unhandled arm64-linux syscall: 234

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368916
   Summary: WARNING: unhandled arm64-linux syscall: 234
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=remap_file_pages01_valgrind_memory_leak_check stime=1473974430
cmdline=" valgrind -q --leak-check=full --trace-children=yes
remap_file_pages01"
contacts=""
analysis=exit
<<>>
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
==25011== Invalid read of size 1
==25011==at 0x403020: test_nonlinear (remap_file_pages01.c:203)
==25011==by 0x402B77: main (remap_file_pages01.c:133)
==25011==  Address 0x4800 is not stack'd, malloc'd or (recently) free'd
==25011== 
remap_file_pages011  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4800, page_sz=131072, window_pages=14: errno=ENOSYS(38):
Function not implemented
remap_file_pages012  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4802, page_sz=131072, window_pages=12: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed:
unlink(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed; errno=2: No such file or
directory
remap_file_pages013  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4804, page_sz=131072, window_pages=10: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed:
unlink(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed; errno=2: No such file or
directory
remap_file_pages014  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4806, page_sz=131072, window_pages=8: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed:
unlink(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed; errno=2: No such file or
directory
remap_file_pages015  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4808, page_sz=131072, window_pages=6: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed:
unlink(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed; errno=2: No such file or
directory
remap_file_pages016  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x480a, page_sz=131072, window_pages=4: errno=ENOSYS(38):
Function

[valgrind] [Bug 368921] New: WARNING: unhandled arm64-linux syscall: 162

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368921
   Summary: WARNING: unhandled arm64-linux syscall: 162
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=setdomainname01_valgrind_memory_leak_check stime=1473974763
cmdline=" valgrind -q --leak-check=full --trace-children=yes setdomainname01"
contacts=""
analysis=exit
<<>>
--26022-- WARNING: unhandled arm64-linux syscall: 162
--26022-- You may be able to write your own handler.
--26022-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26022-- Nevertheless we consider this a bug.  Please report
--26022-- it at http://valgrind.org/support/bug_reports.html.
--26022-- WARNING: unhandled arm64-linux syscall: 162
--26022-- You may be able to write your own handler.
--26022-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26022-- Nevertheless we consider this a bug.  Please report
--26022-- it at http://valgrind.org/support/bug_reports.html.
setdomainname011  TFAIL  :  setdomainname01.c:104: setdomainname() Failed,
errno = 38 : Function not implemented
setdomainname010  TWARN  :  setdomainname01.c:146: setdomainname() failed
while restoring domainname to "(none)"
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=5 corefile=no
cutime=54 cstime=2
<<>>


Reproducible: Always

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

[valgrind] [Bug 368920] New: WARNING: unhandled arm64-linux syscall: 275

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368920
   Summary: WARNING: unhandled arm64-linux syscall: 275
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sched_getattr02_valgrind_memory_leak_check stime=1473974664
cmdline=" valgrind -q --leak-check=full --trace-children=yes sched_getattr02"
contacts=""
analysis=exit
<<>>
--25462-- WARNING: unhandled arm64-linux syscall: 275
--25462-- You may be able to write your own handler.
--25462-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25462-- Nevertheless we consider this a bug.  Please report
--25462-- it at http://valgrind.org/support/bug_reports.html.
--25462-- WARNING: unhandled arm64-linux syscall: 275
--25462-- You may be able to write your own handler.
--25462-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25462-- Nevertheless we consider this a bug.  Please report
--25462-- it at http://valgrind.org/support/bug_reports.html.
--25462-- WARNING: unhandled arm64-linux syscall: 275
--25462-- You may be able to write your own handler.
--25462-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25462-- Nevertheless we consider this a bug.  Please report
--25462-- it at http://valgrind.org/support/bug_reports.html.
--25462-- WARNING: unhandled arm64-linux syscall: 275
--25462-- You may be able to write your own handler.
--25462-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25462-- Nevertheless we consider this a bug.  Please report
--25462-- it at http://valgrind.org/support/bug_reports.html.
sched_getattr021  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 3 - ESRCH: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr022  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr023  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr024  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=52 cstime=1
<<>>


Reproducible: Always

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

[valgrind] [Bug 368919] New: WARNING: unhandled arm64-linux syscall: 274

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368919
   Summary: WARNING: unhandled arm64-linux syscall: 274
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sched_setattr01_valgrind_memory_leak_check stime=1473974662
cmdline=" valgrind -q --leak-check=full --trace-children=yes sched_setattr01"
contacts=""
analysis=exit
<<>>
--25451-- WARNING: unhandled arm64-linux syscall: 274
--25451-- You may be able to write your own handler.
--25451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25451-- Nevertheless we consider this a bug.  Please report
--25451-- it at http://valgrind.org/support/bug_reports.html.
--25451-- WARNING: unhandled arm64-linux syscall: 274
--25451-- You may be able to write your own handler.
--25451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25451-- Nevertheless we consider this a bug.  Please report
--25451-- it at http://valgrind.org/support/bug_reports.html.
--25451-- WARNING: unhandled arm64-linux syscall: 274
--25451-- You may be able to write your own handler.
--25451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25451-- Nevertheless we consider this a bug.  Please report
--25451-- it at http://valgrind.org/support/bug_reports.html.
--25451-- WARNING: unhandled arm64-linux syscall: 274
--25451-- You may be able to write your own handler.
--25451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25451-- Nevertheless we consider this a bug.  Please report
--25451-- it at http://valgrind.org/support/bug_reports.html.
sched_setattr011  TFAIL  :  sched_setattr01.c:96: sched_setattr(0,attr,0)
returned: -1 expected: 0: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr012  TFAIL  :  sched_setattr01.c:109:
sched_setattr(32768,attr,0): expected: 3 - ESRCH: TEST_ERRNO=ENOSYS(38):
Function not implemented
sched_setattr013  TFAIL  :  sched_setattr01.c:109: sched_setattr(0,attr,0):
expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr014  TFAIL  :  sched_setattr01.c:109:
sched_setattr(0,attr,1000): expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38):
Function not implemented
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=54 cstime=2
<<>>


Reproducible: Always

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

[valgrind] [Bug 368918] New: WARNING: unhandled arm64-linux syscall: 127

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368918
   Summary: WARNING: unhandled arm64-linux syscall: 127
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sched_rr_get_interval01_valgrind_memory_leak_check stime=1473974647
cmdline=" valgrind -q --leak-check=full --trace-children=yes
sched_rr_get_interval01"
contacts=""
analysis=exit
<<>>
--25352-- WARNING: unhandled arm64-linux syscall: 127
--25352-- You may be able to write your own handler.
--25352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25352-- Nevertheless we consider this a bug.  Please report
--25352-- it at http://valgrind.org/support/bug_reports.html.
sched_rr_get_interval011  TFAIL  :  sched_rr_get_interval01.c:105: Test
Failed, sched_rr_get_interval()returned -1: TEST_ERRNO=ENOSYS(38): Function not
implemented
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=45 cstime=1
<<>>


Reproducible: Always

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

[valgrind] [Bug 368917] New: WARNING: unhandled arm64-linux syscall: 218

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368917
   Summary: WARNING: unhandled arm64-linux syscall: 218
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=request_key01_valgrind_memory_leak_check stime=1473974601
cmdline=" valgrind -q --leak-check=full --trace-children=yes request_key01"
contacts=""
analysis=exit
<<>>
tst_test.c:756: INFO: Timeout per run is 0h 05m 00s
--25192-- WARNING: unhandled arm64-linux syscall: 218
--25192-- You may be able to write your own handler.
--25192-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25192-- Nevertheless we consider this a bug.  Please report
--25192-- it at http://valgrind.org/support/bug_reports.html.
request_key01.c:46: FAIL: request_key() failed: ENOSYS

Summary:
passed   0
failed   1
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=51 cstime=2
<<>>


Reproducible: Always

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

[valgrind] [Bug 368914] New: WARNING: unhandled arm64-linux syscall: 142

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368914
   Summary: WARNING: unhandled arm64-linux syscall: 142
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=reboot01_valgrind_memory_leak_check stime=1473973971
cmdline=" valgrind -q --leak-check=full --trace-children=yes reboot01"
contacts=""
analysis=exit
<<>>
--24614-- WARNING: unhandled arm64-linux syscall: 142
--24614-- You may be able to write your own handler.
--24614-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24614-- Nevertheless we consider this a bug.  Please report
--24614-- it at http://valgrind.org/support/bug_reports.html.
--24614-- WARNING: unhandled arm64-linux syscall: 142
--24614-- You may be able to write your own handler.
--24614-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24614-- Nevertheless we consider this a bug.  Please report
--24614-- it at http://valgrind.org/support/bug_reports.html.
reboot011  TFAIL  :  reboot01.c:109: reboot(2) Failed for option
LINUX_REBOOT_CMD_CAD_ON
reboot012  TFAIL  :  reboot01.c:109: reboot(2) Failed for option
LINUX_REBOOT_CMD_CAD_OFF
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=44 cstime=2
<<>>


Reproducible: Always

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

[plasmashell] [Bug 368915] New: Preserve favorite apps when user changes apps menu layout

2016-09-16 Thread Dr . Chapatin via KDE Bugzilla

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

Bug ID: 368915
   Summary: Preserve favorite apps when user changes apps menu
layout
   Product: plasmashell
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: yy...@gmx.com
CC: plasma-b...@kde.org

Apps menu loses favorite apps when its layout is changed

Reproducible: Always

Steps to Reproduce:
1.open apps menu, right click on any app, select "Add to favorites"
2.rigth click on apps menu icon, select "Alternatives", alternate to any option
3.

Actual Results:  
favorite app is missing from menu. Even if I back to previous apps menu layout
the favorite app is still missing.

Expected Results:  
preserve favorite app even when alternate the apps menu layout.

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

[valgrind] [Bug 368913] New: WARNING: unhandled arm64-linux syscall: 117

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

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

Bug ID: 368913
   Summary: WARNING: unhandled arm64-linux syscall: 117
   Product: valgrind
   Version: 3.11.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=ptrace01_valgrind_memory_leak_check stime=1473972958
cmdline=" valgrind -q --leak-check=full --trace-children=yes ptrace01"
contacts=""
analysis=exit
<<>>
--23224-- WARNING: unhandled arm64-linux syscall: 117
--23224-- You may be able to write your own handler.
--23224-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23224-- Nevertheless we consider this a bug.  Please report
--23224-- it at http://valgrind.org/support/bug_reports.html.
ptrace010  TWARN  :  ptrace01.c:237: ptrace() failed in child
ptrace011  TFAIL  :  ptrace01.c:182: Test Failed
--23225-- WARNING: unhandled arm64-linux syscall: 117
--23225-- You may be able to write your own handler.
--23225-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23225-- Nevertheless we consider this a bug.  Please report
--23225-- it at http://valgrind.org/support/bug_reports.html.
ptrace010  TWARN  :  ptrace01.c:237: ptrace() failed in child
ptrace012  TFAIL  :  ptrace01.c:182: Test Failed
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=58 cstime=3
<<>>


Reproducible: Always

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

[plasmashell] [Bug 368912] Apps menu and its tooltip must use the same icon when user sets a customized menu icon

2016-09-16 Thread Dr . Chapatin via KDE Bugzilla

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

--- Comment #1 from Dr. Chapatin  ---
Created attachment 101129
  --> https://bugs.kde.org/attachment.cgi?id=101129=edit
screenshot

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

[plasmashell] [Bug 368912] New: Apps menu and its tooltip must use the same icon when user sets a customized menu icon

2016-09-16 Thread Dr . Chapatin via KDE Bugzilla

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

Bug ID: 368912
   Summary: Apps menu and its tooltip must use the same icon when
user sets a customized menu icon
   Product: plasmashell
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: yy...@gmx.com
CC: plasma-b...@kde.org

This affects both kickoff and classic menu.

Reproducible: Always

Steps to Reproduce:
1.right click on apps menu icon, select "Application launcher settings"
2.choose any customized icon and apply the change
3.

Actual Results:  
kde menu and its tooltip have different icons. See the screenshot please.

Expected Results:  
kde menu and its tooltip have the same icon.

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

[konsole] [Bug 368911] New: Konsole re-uses EWMH -name when it reuses a process

2016-09-16 Thread via KDE Bugzilla

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

Bug ID: 368911
   Summary: Konsole re-uses EWMH -name when it reuses a process
   Product: konsole
   Version: 16.08.1
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: single-process
  Assignee: konsole-de...@kde.org
  Reporter: temporalabstract...@gmail.com

When a konsole window has been created with the `-name` option to give it an
EWMH name and a new window is spawned which re-uses the process (which is
apparently automatic if not spawned from a terminal) the new window will obtain
the EWMH name already given via `-name` to the other process. A current
workaround is simply spawning with `--separate` in which case the bug does not
occur.

Reproducible: Always

Steps to Reproduce:
1. kill all existing konsole sessions
2. spawn a new konsole with `-name foo`
3. spawn another konsole session without any `-name` argument

An easy way to do it is using a hotkey daemon of some kind and just bind the
`konsole -name foo` and  `konsole` commands to two different hotkeys, this is
the exact scenario that caused the bug for me. 

Actual Results:  
The second konsole window will get the EWMH window name `foo`

Expected Results:  
The second window should get the EWMH name `konsole`

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

[kaffeine] [Bug 365067] Subtitles don't show on dvb

2016-09-16 Thread Mauro Carvalho Chehab via KDE Bugzilla

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #9 from Mauro Carvalho Chehab  ---
The DVB subtitles logic were indeed broken in a number of ways.

It should be working fine after this commit:
   http://commits.kde.org/kaffeine/63c3694da12c904a88178859c650b6c30cf748ee

Please test. Locally, I tested with both VLC 2.x and 3.x.

PS.: now, --debug will display messages related to the DVB messages.

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

[Akonadi] [Bug 325224] CalDav doesn't read server items

2016-09-16 Thread S . Bryant via KDE Bugzilla

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

--- Comment #62 from S. Bryant  ---
I've just installed the OpenSuse Leap 42.2 beta to test this (Kontact 5.1.3).
The bug is still present - Kontact is not seeing calendar events from the
server.

I should point out that I'm not using Owncloud for this either, so no
kitten-eating here.  I'm using the caldav software from Synology that's on my
diskstation (with the most up-to-date software).  Thunderbird (Lightning) and
Android (Davdroid) sync just fine here, and Synology list other software
they've tested it with.  The bug is not on the server side.

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

[KScreen] [Bug 368910] Monitor change not detected on docking

2016-09-16 Thread Matthias Blaicher via KDE Bugzilla

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

--- Comment #1 from Matthias Blaicher  ---
Created attachment 101128
  --> https://bugs.kde.org/attachment.cgi?id=101128=edit
Annotated kscreen log

Annotated kscreen log with relevant input from journald of the folliowing
sequence:

1. Boot into KDE undocked
2. Dock laptop
3. Execute xrandr
4. Close lid

While there is nothing happening in the kscreen logs, there is one entry after
docking (point 2) I'd like to point out:

Sep 16 20:51:32 meinpc kwin_x11[6183]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 10182, resource id: 94371848, major code: 18
(ChangeProperty), minor code: 0
Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter
Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter
Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter
Sep 16 20:51:32 meinpc kcminit[6975]: Initializing  "kcm_input" : 
"kcminit_mouse"
Sep 16 20:51:32 meinpc kwin_x11[6183]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 10561, resource id: 92274696, major code: 18
(ChangeProperty), minor code: 0 

Could it be, the ChangeProperty is the event we need, but it is dropped
somehow?

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

[plasmashell] [Bug 368078] Plasma-Task Manager and Wine issues

2016-09-16 Thread Eike Hein via KDE Bugzilla

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

Eike Hein  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #8 from Eike Hein  ---
I can reproduce something now - will take a closer look soon.

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

[kteatime] [Bug 279222] icon of the progress of the system tray doesn't work

2016-09-16 Thread Tomasz C . via KDE Bugzilla

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

--- Comment #17 from Tomasz C.  ---
A progress bar still does not work in version 16.08.1
Systray icon was restored with kde4 and did not fit the Plasma 5.

I think it's better to undo the change and let it be a nice icon that
corresponds to the Plasma 5, although it will not be a progress bar.

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

[plasmashell] [Bug 368579] The pager doesn't fit desktop names into the boxes anymore

2016-09-16 Thread Eike Hein via KDE Bugzilla

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

Eike Hein  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-desktop/5c941198a9f62946
   ||08588d863bc105488426249e
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Eike Hein  ---
Git commit 5c941198a9f6294608588d863bc105488426249e by Eike Hein.
Committed on 16/09/2016 at 18:54.
Pushed by hein into branch 'Plasma/5.8'.

Fix desktop label clipping.

M  +15   -1applets/pager/package/contents/ui/main.qml

http://commits.kde.org/plasma-desktop/5c941198a9f6294608588d863bc105488426249e

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

[kdevelop] [Bug 368603] crash when starting an lldb debug session

2016-09-16 Thread Aetf via KDE Bugzilla

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

--- Comment #16 from Aetf <7437...@gmail.com> ---
Could you start KDevelop from the console and check the output when starting
the debug session on Linux? You can enable debug output from KDevelop by
launching it with the command

env QT_LOGGING_CONF='logging.conf' kdevelop

where the content of logging.conf is

[Rules]
kdevelop.debuggers.lldb.debug=true
kdevelop.debuggers.common.debug=true

Also, even if the debug session ends, there should be an output panel titled
"Debug" being raised. See if there's any relevant output in that.

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

[KScreen] [Bug 368910] New: Monitor change not detected on docking

2016-09-16 Thread Matthias Blaicher via KDE Bugzilla

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

Bug ID: 368910
   Summary: Monitor change not detected on docking
   Product: KScreen
   Version: 5.7.95
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: matth...@blaicher.com

On a Lenovo Thinkpad L430, running Plasma 5.8 Beta with Arch Linux testing
packages, monitor changes due to docking/undocking are not detected. It also
had the same beviour back with Plasma 5.7. However, a simple execution of
"xrandr" makes kscreen detect the monitor change. Afterwards plasmashell need
to be killed and restarted to have a proper desktop layout.

This happens with the intel as well as the mode setting driver. The dock has
two DVI outputs, but the problem behaves the same on both ports.

Installed packages are:

kde-unstable/plasma-workspace 5.7.95-1 
kde-unstable/kscreen 5.7.95-1
kde-unstable/libkscreen 5.7.95-1

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)

Tomorrow, I will take the time to add propper logs to this bug report. If you
require specific tests, feel free to tell me. I would also be willing to try
kscreen patches.

Reproducible: Always

Steps to Reproduce:
1. Plug/Unplug laptop to dock

Actual Results:  
Nothing happens. Only detected when xrandr is executed.

Expected Results:  
Direct detection of monitor changes, proper Plasma desktop applied after
screens are adjusted.

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

[kdenlive] [Bug 364559] Changing project settings and saving crashes the software

2016-09-16 Thread Jean-Baptiste Mardelle via KDE Bugzilla

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

--- Comment #9 from Jean-Baptiste Mardelle  ---
Git commit 54554d178e00bcee5deb588a2ad1cb522d5e2c3a by Jean-Baptiste Mardelle.
Committed on 16/09/2016 at 18:36.
Pushed by mardelle into branch 'Applications/16.08'.

Fix crash when changing project fps while a clip was selected in timeline

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

http://commits.kde.org/kdenlive/54554d178e00bcee5deb588a2ad1cb522d5e2c3a

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

[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times

2016-09-16 Thread Simon Andric via KDE Bugzilla

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[plasmashell] [Bug 368578] Pager shows only 8 virtual desktops

2016-09-16 Thread Eike Hein via KDE Bugzilla

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||h...@kde.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Eike Hein  ---
Fixed the other day.

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

[plasmashell] [Bug 368579] The pager doesn't fit desktop names into the boxes anymore

2016-09-16 Thread Eike Hein via KDE Bugzilla

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

Eike Hein  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||h...@kde.org
   Assignee|plasma-b...@kde.org |h...@kde.org
 Status|UNCONFIRMED |CONFIRMED

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

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

2016-09-16 Thread Alexander Schlarb via KDE Bugzilla

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

Alexander Schlarb  changed:

   What|Removed |Added

 CC|alexander-...@xmine128.tk   |

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

[plasmashell] [Bug 368909] Regression: Windows with demands attention flag are falsely shown on all workspaces

2016-09-16 Thread Eike Hein via KDE Bugzilla

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

Eike Hein  changed:

   What|Removed |Added

 CC||h...@kde.org
   Assignee|plasma-b...@kde.org |h...@kde.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #11 from b...@beuc.net ---
Build now works from a minimal CentOS such as Docker's :)

Attached are 3 patched:
- adding missing QT build dependencies
- avoid clearing /out/* since I lost all my previous builds :/
- add documentation

I would recommend pushing it to krita/3.0.1 along with
fe518206866a6cffdc64903ce3bf18b5e7a80867
2ac3c47e3ba91005143f4b59768f4e235e6d6762
so that people checking out the stable branch get a fully-working script.

Cheers!

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

[digikam] [Bug 368862] Thumbnails for Olympus raw (ORF) in albumview are blurred

2016-09-16 Thread Maik Qualmann via KDE Bugzilla

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

--- Comment #10 from Maik Qualmann  ---
Yes, there are 2 preview images in different sizes available:

maik@linux-tpgn:~> exiv2 -pp GME15390.ORF
Preview 1: image/jpeg, 160x120 pixels, 6946 bytes
Preview 2: image/jpeg, 3200x2400 pixels, 1004415 bytes

I have searched another RAW image from this camera on the Web. At this file
libraw used the large preview for the thumbnail. However, the firmware version
from your camera is greater. Strange.

Maik

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

[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #10 from b...@beuc.net ---
Created attachment 101127
  --> https://bugs.kde.org/attachment.cgi?id=101127=edit
appimage: add documentation

appimage: add documentation

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

[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #9 from b...@beuc.net ---
Created attachment 101126
  --> https://bugs.kde.org/attachment.cgi?id=101126=edit
appimage: do not remove previously built appimages

appimage: do not remove previously built appimages

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

[krita] [Bug 368633] No keyboard when recompiling 3.0.1 appimage

2016-09-16 Thread via KDE Bugzilla

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

--- Comment #8 from b...@beuc.net ---
Created attachment 101125
  --> https://bugs.kde.org/attachment.cgi?id=101125=edit
appimage: add missing build dependencies to fix lack of keyboard support when
building from minimal CentOS environment

appimage: add missing build dependencies to fix lack of keyboard support when
building from minimal CentOS environment

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

[plasmashell] [Bug 368909] New: Regression: Windows with demands attention flag are falsely shown on all workspaces

2016-09-16 Thread Fuchs via KDE Bugzilla

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

Bug ID: 368909
   Summary: Regression: Windows with demands attention flag are
falsely shown on all workspaces
   Product: plasmashell
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Pager
  Assignee: plasma-b...@kde.org
  Reporter: deve...@fuchsnet.ch

As reported on IRC: as the same model is used for the pager as for the
task-manager, windows that have the demands attention flag set will be falsely
shown on all workspaces.

Reproducible: Always

Steps to Reproduce:
1. Have multiple workspaces and a pager
2. Place a window on one workspace, let's take the great IRC client
konversation as an example
3. Have that window trigger demands attention  (e.g. get highlighted in
konversation)

Actual Results:  
Window is shown on all workspaces in the pager, as if it was sticky

Expected Results:  
Window is only shown on the correct workspace

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

[konsole] [Bug 336007] split-view status not maintained across sessions

2016-09-16 Thread Simon Andric via KDE Bugzilla

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[bugs.kde.org] [Bug 335654] reported versions of several applications are not registered on bugs.kde.org

2016-09-16 Thread Simon Andric via KDE Bugzilla

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[korganizer] [Bug 352215] kOrganizer 5.0.0 crashes whenever I add an event which invites other participants

2016-09-16 Thread Gunter Ohrner via KDE Bugzilla

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

Gunter Ohrner  changed:

   What|Removed |Added

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

--- Comment #1 from Gunter Ohrner  ---
Does not happen any more since quite a while now. (KDE Neon packages)

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

[plasmashell] [Bug 364852] Plasmashell panel when put on the middle edge of a multi screen setup does not autohide

2016-09-16 Thread Simon Andric via KDE Bugzilla

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[plasmashell] [Bug 366833] Panels misplaced after restart

2016-09-16 Thread Simon Andric via KDE Bugzilla

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[korganizer] [Bug 366055] kOrganizer 5.1.3: Incidents inviting "myself" are invisible

2016-09-16 Thread Gunter Ohrner via KDE Bugzilla

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

Gunter Ohrner  changed:

   What|Removed |Added

 Depends on||352214

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

[korganizer] [Bug 352214] Event is not added if the invitation list contains the creator's email address

2016-09-16 Thread Gunter Ohrner via KDE Bugzilla

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

Gunter Ohrner  changed:

   What|Removed |Added

 Blocks||366055

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

[korganizer] [Bug 366055] kOrganizer 5.1.3: Incidents inviting "myself" are invisible

2016-09-16 Thread Gunter Ohrner via KDE Bugzilla

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

--- Comment #2 from Gunter Ohrner  ---
Probably a duplicate of Bug 352214
(https://bugs.kde.org/show_bug.cgi?id=352214) (or the other way around?)

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

[korganizer] [Bug 352043] Regression: kOrganizer 5 systray reminder module does not open main application window on click

2016-09-16 Thread Gunter Ohrner via KDE Bugzilla

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

Gunter Ohrner  changed:

   What|Removed |Added

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

--- Comment #4 from Gunter Ohrner  ---
Seems to be fixed as of kOrganizer Version 5.3.0 (QtWebEngine) (KDE Neon
packages).

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

[kdenlive] [Bug 368908] New: Crash when trying to play a transition

2016-09-16 Thread XYQuadrat via KDE Bugzilla

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

Bug ID: 368908
   Summary: Crash when trying to play a transition
   Product: kdenlive
   Version: 16.08.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: juliquad...@gmail.com

When trying to play a transition, KDE instantly crashes.

Reproducible: Always

Steps to Reproduce:
1. Adding any transition to a new project with two video files
2. Trying to play it in the video player

Actual Results:  
It instantly crashed.

Expected Results:  
It should play the transition.

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

Thread 22 (Thread 0x7fe1637fd700 (LWP 5777)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe1da7cf63e in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fe1f558a6fa in start_thread (arg=0x7fe1637fd700) at
pthread_create.c:333
#3  0x7fe1f6c68b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fe163ffe700 (LWP 5776)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe1da7cf63e in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fe1f558a6fa in start_thread (arg=0x7fe163ffe700) at
pthread_create.c:333
#3  0x7fe1f6c68b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7fe184ff9700 (LWP 5775)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe1da7cf63e in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fe1f558a6fa in start_thread (arg=0x7fe184ff9700) at
pthread_create.c:333
#3  0x7fe1f6c68b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7fe199ac3700 (LWP 5774)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe1da7cf63e in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fe1f558a6fa in start_thread (arg=0x7fe199ac3700) at
pthread_create.c:333
#3  0x7fe1f6c68b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fe1b2ffe700 (LWP 5773)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe1da7cf63e in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fe1f558a6fa in start_thread (arg=0x7fe1b2ffe700) at
pthread_create.c:333
#3  0x7fe1f6c68b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7fe1867fc700 (LWP 5772)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe1c61c995d in video_thread (arg=0x46bce50) at
consumer_sdl_audio.c:423
#2  0x7fe1f558a6fa in start_thread (arg=0x7fe1867fc700) at
pthread_create.c:333
#3  0x7fe1f6c68b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7fe19547c700 (LWP 5771)):
#0  0x7fe1f1d34a3c in pa_stream_get_state () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#1  0x7fe1cca98fd0 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#2  0x7fe1cca6b920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#3  0x7fe1cca750b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#4  0x7fe1ccab4f59 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#5  0x7fe1f558a6fa in start_thread (arg=0x7fe19547c700) at
pthread_create.c:333
#6  0x7fe1f6c68b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fe19731d700 (LWP 5770)):
[KCrash Handler]
#6  0x7fe19f9f025f in addition::update(double, unsigned int*, unsigned int
const*, unsigned int const*, unsigned int const*) () from
/usr/lib/frei0r-1/addition.so
#7  0x7fe19f9efa54 in f0r_update2 () from /usr/lib/frei0r-1/addition.so
#8  0x7fe1ddcfc11a in process_frei0r_item (service=service@entry=0xa7a0f00,
position=position@entry=0, time=0, prop=prop@entry=0xa7a0f00,
this=this@entry=0x7fe1801c3550, image=image@entry=0x7fe19731caf0,
width=width@entry=0x7fe19731ccc4, height=height@entry=0x7fe19731ccc8) at
frei0r_helper.c:167
#9  0x7fe1ddcfbb90 in transition_get_image
(a_frame=a_frame@entry=0x7fe1801c3550, image=image@entry=0x7fe19731ccd8,
format=format@entry=0x3e1d40c, width=width@entry=0x7fe19731ccc4,
height=height@entry=0x7fe19731ccc8, writable=writable@entry=0) at
transition_frei0r.c:71
#10 0x7fe1fc51e757 in

[konsole] [Bug 368785] konsole tab title format only uses the first program you ever ran, not the current one

2016-09-16 Thread Julio J . via KDE Bugzilla

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

Julio J.  changed:

   What|Removed |Added

 CC||julioelpo...@gmail.com

--- Comment #4 from Julio J.  ---
Yup, can confirm, it happens also when you connect to a remote host, the title
stays the same afterwards.

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

[kwordquiz] [Bug 368871] Unknown file type

2016-09-16 Thread Giovanni Rallo via KDE Bugzilla

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

--- Comment #6 from Giovanni Rallo  ---
I haven't .kvtml files becouse program can't save... another guy have the same
problem i Ubuntu... another friend debian's think that problem is from the new
Kde system i Debian Testing... is very different...

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

[plasmashell] [Bug 368078] Plasma-Task Manager and Wine issues

2016-09-16 Thread David Brooke via KDE Bugzilla

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

--- Comment #7 from David Brooke  ---
Tested plasma 5.7.95 and the results are the same. Refer to the first "Doesn't
work as expected" video.

Partition2 or C3770-P2
Gentoo AMD64 Stable
Plasma 5.7.95
Frameworks 5.26
KDE Apps 16.08.1
QT5 - version 5.6.1
xf86-video-intel 2.99.917-r2

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

[kdenlive] [Bug 364559] Changing project settings and saving crashes the software

2016-09-16 Thread YEK via KDE Bugzilla

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

--- Comment #8 from YEK  ---
Thanks for posting your well-researched and thoughtful comment. We have clearly
a confirmed bug.

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

Could you help me on this ? dont write very well in english ...

2016-09-16 Thread Jeová Desideris


Application: ktp-text-ui (0.8.1)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.19.0-32-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed:
I was in the text interface TELEPATHY window I clicked in action > invite to 
chart and then it crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Interface de texto do Telepathy (ktp-text-ui), signal: 
Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#5  SharedPtr (o=, this=0x7ffcf49ef1f0, this@entry=0x7ffcf49ef1a0) at 
/usr/include/telepathy-qt4/TelepathyQt/shared-ptr.h:105
#6  ChatWidget::account (this=this@entry=0x0) at 
/build/buildd/ktp-text-ui-0.8.1/lib/chat-widget.cpp:219
#7  0x00412777 in ChatWindow::onInviteToChatTriggered (this=0x1614860) 
at /build/buildd/ktp-text-ui-0.8.1/app/chat-window.cpp:433
#8  0x00417f05 in ChatWindow::qt_static_metacall (_o=, 
_id=, _a=, _c=) at 
/build/buildd/ktp-text-ui-0.8.1/obj-x86_64-linux-gnu/app/chat-window.moc:127
#9  0x7fc80ba2c87a in QMetaObject::activate (sender=sender@entry=0x16603d0, 
m=m@entry=0x7fc80b5e0de0 , 
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcf49ef370) 
at kernel/qobject.cpp:3539
#10 0x7fc80ab30a62 in QAction::triggered (this=this@entry=0x16603d0, 
_t1=false) at .moc/release-shared/moc_qaction.cpp:276
#11 0x7fc80ab32433 in QAction::activate (this=this@entry=0x16603d0, 
event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1257
#12 0x7fc80af60509 in QMenuPrivate::activateCausedStack 
(this=this@entry=0x38e8cb0, causedStack=..., action=action@entry=0x16603d0, 
action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at 
widgets/qmenu.cpp:1038
#13 0x7fc80af64a39 in QMenuPrivate::activateAction (this=0x38e8cb0, 
action=0x16603d0, action_e=QAction::Trigger, self=) at 
widgets/qmenu.cpp:1130
#14 0x7fc80db1a615 in KMenu::mouseReleaseEvent(QMouseEvent*) () from 
/usr/lib/libkdeui.so.5
#15 0x7fc80ab8651a in QWidget::event (this=this@entry=0x37e35b0, 
event=event@entry=0x7ffcf49efaa0) at kernel/qwidget.cpp:8376
#16 0x7fc80af6883b in QMenu::event (this=0x37e35b0, e=0x7ffcf49efaa0) at 
widgets/qmenu.cpp:2481
#17 0x7fc80ab36e2c in QApplicationPrivate::notify_helper 
(this=this@entry=0x14978c0, receiver=receiver@entry=0x37e35b0, 
e=e@entry=0x7ffcf49efaa0) at kernel/qapplication.cpp:4567
#18 0x7fc80ab3d5dd in QApplication::notify (this=, 
receiver=0x37e35b0, e=0x7ffcf49efaa0) at kernel/qapplication.cpp:4110
#19 0x7fc80da63cca in KApplication::notify(QObject*, QEvent*) () from 
/usr/lib/libkdeui.so.5
#20 0x7fc80ba184dd in QCoreApplication::notifyInternal (this=0x147ac80, 
receiver=receiver@entry=0x37e35b0, event=event@entry=0x7ffcf49efaa0) at 
kernel/qcoreapplication.cpp:953
#21 0x7fc80ab3cd93 in sendEvent (event=, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#22 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x37e35b0, 
event=event@entry=0x7ffcf49efaa0, alienWidget=alienWidget@entry=0x0, 
nativeWidget=nativeWidget@entry=0x37e35b0, 
buttonDown=buttonDown@entry=0x7fc80b61c318 , 
lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at 
kernel/qapplication.cpp:3178
#23 0x7fc80abb1d1c in QETWidget::translateMouseEvent 
(this=this@entry=0x37e35b0, event=event@entry=0x7ffcf49efdf0) at 
kernel/qapplication_x11.cpp:4568
#24 0x7fc80abb1289 in QApplication::x11ProcessEvent (this=0x147ac80, 
event=event@entry=0x7ffcf49efdf0) at kernel/qapplication_x11.cpp:3627
#25 0x7fc80abd8b32 in x11EventSourceDispatch (s=0x1497e10, callback=0x0, 
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#26 0x7fc803d6ae04 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7fc803d6b048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7fc803d6b0ec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7fc80ba457be in QEventDispatcherGlib::processEvents (this=0x143eab0, 
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#30 0x7fc80abd8be6 in QGuiEventDispatcherGlib::processEvents 
(this=, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x7fc80ba170af in QEventLoop::processEvents 
(this=this@entry=0x7ffcf49f01c0, flags=...) at kernel/qeventloop.cpp:149
#32 0x7fc80ba173a5 in QEventLoop::exec (this=this@entry=0x7ffcf49f01c0, 
flags=...) at kernel/qeventloop.cpp:204
#33 0x7fc80ba1cb79 in QCoreApplication::exec () at 
kernel/qcoreapplication.cpp:1225
#34 0x7fc80ab3537c in QApplication::exec () at kernel/qapplication.cpp:3828
#35 0x0040e995 in main (argc=1, argv=0x7ffcf49f03e8) at 
/build/buildd/ktp-text-ui-0.8.1/app/main.cpp:72

Relatar para https://bugs.kde.org/

[kaffeine] [Bug 368907] New: kaffeine sometimes uses 100% CPU

2016-09-16 Thread José JORGE via KDE Bugzilla

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

Bug ID: 368907
   Summary: kaffeine sometimes uses 100% CPU
   Product: kaffeine
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: lists.jjo...@free.fr

I use kaffeine for DVB-T, and it uses nicely VDPAU, as the CPU used is less
than 20% like other players with VDPAU. But sometimes, it starts using 100%
CPU, and then it keeps at this level even when channels are stopped.

This happens sometimes directly when I start playing the first channel, or when
changing the channel. It never starts happening when simply playing a channel.

I tried to run with debug log (-d), but I saw nothing different with between
sessions with this bug or without.

Reproducible: Sometimes

Steps to Reproduce:
1. play dvb-t
2. it is in the french TNT system


Actual Results:  
100% CPU

Expected Results:  
At least the CPU should not be used if I stop playing/

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

[konqueror] [Bug 368705] Port to Qt5 and Add webEngine

2016-09-16 Thread Simon Andric via KDE Bugzilla

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[dolphin] [Bug 365968] scrolling is unusable slow with libinput in dolphin places and folders panel

2016-09-16 Thread Jake via KDE Bugzilla

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

Jake  changed:

   What|Removed |Added

 CC||ja...@posteo.de

--- Comment #4 from Jake  ---
I have this issue also on multiple Manjaro/Arch machines, not using
xf86-input-libinput.

The bug came with version 16.08 (this includes 16.07.80 + 16.07.90). Can
someone verify this?
Version 16.04 works fine for me, as temporary workaround you could downgrade
the dolphin package without big problems.

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

[plasmashell] [Bug 368906] New: Plasma crashes when unlocking from standby

2016-09-16 Thread Roberto via KDE Bugzilla

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

Bug ID: 368906
   Summary: Plasma crashes when unlocking from standby
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: robe...@echelon-it.ro
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (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:
The computer was in standby due to no activity. 
When I move the mouse the unlocking screen shows up. I enter my user's password
and even tough everything is fine I get the pop-up with "Plasma crash". I have
dual monitors, one is primary and another is in extended mode. AMD A8 K7700
with the integrated GPU. Both displays are full hd.

The crash can be reproduced sometimes.

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

Thread 25 (Thread 0x7f74cdfe7700 (LWP 4211)):
#0  0x7f775310003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f775400034b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f7757f621cb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f7757f62663 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f7753fff32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f77530fc0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f775390902d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f76427f8700 (LWP 27370)):
#0  0x7f775310003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f775400034b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f769230965f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f769230d43a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f769230d481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f769230d481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f769230d481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f769230d481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f769230d481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7f769230d481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7f769230d481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#19 0x7f769230d481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#20 0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#21 0x7f769230b005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#22 0x7f7753fff32f in  () at /usr/lib64/libQt5Core.so.5
#23 0x7f77530fc0a4 in start_thread () at /lib64/libpthread.so.0
#24 0x7f775390902d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f7642ff9700 (LWP 27369)):
#0  0x7f775310003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f775400034b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f769230965f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f769230d43a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f76923076cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f769230d481 in  () at

[telepathy] [Bug 368030] Crash on declining invite for messenger via google+

2016-09-16 Thread jeova via KDE Bugzilla

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

jeova  changed:

   What|Removed |Added

 CC||jeova.r...@gmail.com

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

[kdevelop] [Bug 368318] Crash during session restore at startup

2016-09-16 Thread Kevin Funk via KDE Bugzilla

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

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.0.1

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

[kdevelop] [Bug 368318] Crash during session restore at startup

2016-09-16 Thread Kevin Funk via KDE Bugzilla

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

Kevin Funk  changed:

   What|Removed |Added

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

--- Comment #6 from Kevin Funk  ---
Well, assuming this particular crash got fixed. Please reopen / open another
bug report for any related crashes.

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

[kwin] [Bug 368902] Top-left cot corner doesn't work reliably when window extends to top-left corner

2016-09-16 Thread Martin Gräßlin via KDE Bugzilla

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
The cursor is pushed back and there is a cooldown delay before you can trigger
it again. Please go to systemsettings -> desktop behavior -> Screen edges and
adjust the settings to your personal preferences.

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

[krunner] [Bug 368901] Pressing ALT+f2 and entering exact executable name and pressing enter can run another program

2016-09-16 Thread Martin Gräßlin via KDE Bugzilla

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

Martin Gräßlin  changed:

   What|Removed |Added

Version|5.7.4   |5.7.5
Product|kwin|krunner
   Assignee|kwin-bugs-n...@kde.org  |k...@privat.broulik.de
  Component|general |general

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

1 2 3 >

1 - 100 of 252 matches

Mail list logo