[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup

[Sergio via KDE Bugzilla]

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

Sergio  changed:

   What|Removed |Added

 CC|sergio.calleg...@gmail.com  |

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

[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1
 Status|NEEDSINFO   |CONFIRMED

--- Comment #12 from wolthera  ---
No, the issue shpuld be happening with both methods, because it's about final
image composition.

What this bug is about is about user expectancy, with power user vs regular
user expentancies. I need to discuss this with boud proper on how to solve
this.

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

[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image

[wolthera via KDE Bugzilla]

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

--- Comment #14 from wolthera  ---
Our solution will be to add a warning to the convert dialogue when doing so to
multiple layers:
https://phabricator.kde.org/T1078

The issue is that going from 16bit linear to 8bit linear will lead to far more
visible information loss than 16bit linear to 8bit srgbtrc, so the later is
preferable default behaviour.

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

[Baloo] [Bug 350485] Baloo File Indexing Daemon crashing...

[eric via KDE Bugzilla]

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

eric  changed:

   What|Removed |Added

 CC||cloudmas...@openmailbox.org

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

[kde] [Bug 356055] login error

[venember via KDE Bugzilla]

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

--- Comment #3 from venember  ---
Created attachment 95934
  --> https://bugs.kde.org/attachment.cgi?id=95934=edit
developer bug tracking list

Developer message:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9886e77900 (LWP 18691))]

Thread 7 (Thread 0x7f986e98f700 (LWP 18693)):
#0 0x7f98803e920d in poll () at /lib64/libc.so.6
#1 0x7f98852eb432 in () at /usr/lib64/libxcb.so.1
#2 0x7f98852ed007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3 0x7f987114ae29 in () at /usr/lib64/libQt5XcbQpa.so.5
#4 0x7f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#5 0x7f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#6 0x7f98803f1b9d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f98644df700 (LWP 18699)):
#0 0x7f98803e920d in poll () at /lib64/libc.so.6
#1 0x7f987ca8c264 in () at /usr/lib64/libglib-2.0.so.0
#2 0x7f987ca8c36c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3 0x7f9880d0650f in QEventDispatcherGlib: rocessEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
#4 0x7f9880cb063a in QEventLoop::exec(QFlags)
() at /usr/lib64/libQt5Core.so.5
#5 0x7f9880adcb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x7f9883db59a5 in () at /usr/lib64/libQt5Qml.so.5
#7 0x7f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#8 0x7f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#9 0x7f98803f1b9d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f98587af700 (LWP 18710)):
#0 0x7f98803e920d in poll () at /lib64/libc.so.6
#1 0x7f987ca8c264 in () at /usr/lib64/libglib-2.0.so.0
#2 0x7f987ca8c36c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3 0x7f9880d0650f in QEventDispatcherGlib: rocessEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
#4 0x7f9880cb063a in QEventLoop::exec(QFlags)
() at /usr/lib64/libQt5Core.so.5
#5 0x7f9880adcb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x7f9883db59a5 in () at /usr/lib64/libQt5Qml.so.5
#7 0x7f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#8 0x7f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#9 0x7f98803f1b9d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f9856dcf700 (LWP 18713)):
#0 0x7f98803e920d in poll () at /lib64/libc.so.6
#1 0x7f987ca8c264 in () at /usr/lib64/libglib-2.0.so.0
#2 0x7f987ca8c36c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3 0x7f9880d0650f in QEventDispatcherGlib: rocessEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
#4 0x7f9880cb063a in QEventLoop::exec(QFlags)
() at /usr/lib64/libQt5Core.so.5
#5 0x7f9880adcb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x7f9883db59a5 in () at /usr/lib64/libQt5Qml.so.5
#7 0x7f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#8 0x7f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#9 0x7f98803f1b9d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9855427700 (LWP 18726)):
#0 0x7f987fbed07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f9886567a84 in () at /usr/lib64/libQt5Script.so.5
#2 0x7f9886567ac9 in () at /usr/lib64/libQt5Script.so.5
#3 0x7f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#4 0x7f98803f1b9d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f97c67cf700 (LWP 18727)):
#0 0x7f987cacf4d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1 0x7f987ca8c21e in () at /usr/lib64/libglib-2.0.so.0
#2 0x7f987ca8c36c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3 0x7f9880d0652b in QEventDispatcherGlib: rocessEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
#4 0x7f9880cb063a in QEventLoop::exec(QFlags)
() at /usr/lib64/libQt5Core.so.5
#5 0x7f9880adcb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x7f9884942e42 in () at /usr/lib64/libQt5Quick.so.5
#7 0x7f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#8 0x7f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#9 0x7f98803f1b9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f9886e77900 (LWP 18691)):
[KCrash Handler]
#6 0x7f988033cd38 in raise () at /lib64/libc.so.6
#7 0x7f988033e18a in abort () at /lib64/libc.so.6
#8 0x7f9880acf82e in () at /usr/lib64/libQt5Core.so.5
#9 0x7f98849ac5c4 in () at /usr/lib64/libQt5Quick.so.5
#10 0x7f98849ad545 in () at /usr/lib64/libQt5Quick.so.5
#11 0x7f98849ae44e in () at /usr/lib64/libQt5Quick.so.5
#12 0x7f9881201c3b in QWindow::event(QEvent*) () at
/usr/lib64/libQt5Gui.so.5
#13 0x7f98849e5621 in QQuickWindow::event(QEvent*) () at
/usr/lib64/libQt5Quick.so.5
#14 0x0043ff66 in DesktopView::event(QEvent*) ()
#15 0x7f98820398cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#16 0x7f988203e9d6 in 

[Baloo] [Bug 356389] New: baloo file indexing daemon crash when download with firefox

[eric via KDE Bugzilla]

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

Bug ID: 356389
   Summary: baloo file indexing daemon crash when download with
firefox
   Product: Baloo
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: m...@vhanda.in
  Reporter: cloudmas...@openmailbox.org
CC: pinak.ah...@gmail.com

baloo daemon crash all time if i start to download a file in firefox, i have
try other addon for download but same result i can't find more details in files
debugging there is only one line for explain baloo file indexing daemon crash,
someone as the same thing? kubuntu 15.10 amd 64 all packages up to date firefox
42.0

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

[kate] [Bug 356304] Kate Crashes On Startup

[via KDE Bugzilla]

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

--- Comment #5 from biplan...@outlook.com ---
Oh, and it appears as though it's chopped off the first few lines from the
second backtrace. Here they are:

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

Thread 2 (Thread 0x7f0b9f57c700 (LWP 7705)):
#0  0x7f0bb55e78dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0bb4ccdbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f0bb4ccf74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-
gnu/libxcb.so.1
#3  0x7f0ba2315a39 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins
/platforms/libqxcb.so
#4  0x7f0bb59582be in ?? () from /usr/lib/x86_64-linux-
gnu/libQt5Core.so.5
#5  0x7f0bb334f6aa in start_thread (arg=0x7f0b9f57c700) at 
pthread_create.c:333
#6  0x7f0bb55f2eed in clone () at ../sysdeps/unix/sysv/linux/x86_64
/clone.S:109

Thread 1 (Thread 0x7f0bb6e3e780 (LWP 7704)):
[KCrash Handler]

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

[systemsettings] [Bug 356281] Once a different scheme is selected via "Window Decorations" and hit OK, if you try to get back to the same "Window Decorations" subsection of "Application Style", the "S

[smihaila via KDE Bugzilla]

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

--- Comment #2 from smihaila  ---
The latest apt-get update + upgrade done via KUbuntu 15.10 brought my
plastma-desktop to version 5.4.2. How to get the 5.4.3? Should I manually add
some dev-grade PPA repositories in order to see the 5.4.3? If so, could you
please advise what PPA to add?

Thank you.

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

[kmail2] [Bug 356283] Any message contents that shows in the message preview bottom pane shows <<< Grantlee theme "" is not valid >>> prefixed to the actual msg body

[smihaila via KDE Bugzilla]

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

--- Comment #4 from smihaila  ---
Sorry for the late reply. Now I understand why I wasn't able to provide the
kmail2 version info itself - it's because the bug ticket's version drop-down
has 4.14.7 as highest version for product = kmail2.

The KDE Mail version I'm using is 5.0.2

Thank you.

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

[kwin] [Bug 348753] more issues with nvidia legacy (304.xxx) blob and explicit syncing (here on login)

[Sergio via KDE Bugzilla]

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

--- Comment #43 from Sergio  ---
Hi, I have just noticed that the version of kwin in 5.4.3 (that I got from the
kubuntu ppa) works again with the KWIN_EXPLICIT_SYNC=0 trick.  It was only
5.4.2 failing. Good news on this front.

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

[kde] [Bug 356055] login error

[venember via KDE Bugzilla]

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

venember  changed:

   What|Removed |Added

 Resolution|DOWNSTREAM  |---
 Status|RESOLVED|UNCONFIRMED

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

[Breeze] [Bug 356082] Icon for save session is missing

[Ömer via KDE Bugzilla]

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

--- Comment #4 from Ömer  ---
No i don't. Any way to find out?
The k-menu entry doesn't really help right clicking only shows add to
favourites.

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

[ksplash] [Bug 356346] Optimus KDE SESSION - ksplashqml: segfault in libnvidia-glcore.so.340.96

[ioann via KDE Bugzilla]

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

--- Comment #5 from ioann  ---
Created attachment 95937
  --> https://bugs.kde.org/attachment.cgi?id=95937=edit
glxinfo from optirun plasma session

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

[ksplash] [Bug 356346] Optimus KDE SESSION - ksplashqml: segfault in libnvidia-glcore.so.340.96

[ioann via KDE Bugzilla]

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

--- Comment #6 from ioann  ---
(In reply to Thomas Lübking from comment #3)
> The setup will be screwed, ie. a mix of MESA and nvidia libraries is used
> and you likely won't be able to even just run "glxinfo" (resp. it prints an
> error or segfaults) - if you can run "glxinfo", please attach the output.
> 
> The sheer dmesg entry doesn't say too much about the cause, sorry.
> You'll often find a switch to bypass the intel chip in the BIOS.

At now, I ran Plasma session as "vblank_mode=0 /usr/bin/primusrun
/usr/bin/startkde". I can not see visual effects, e. g. transparenty or
smoothing.

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

[ksplash] [Bug 356346] Optimus KDE SESSION - ksplashqml: segfault in libnvidia-glcore.so.340.96

[ioann via KDE Bugzilla]

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

--- Comment #8 from ioann  ---
(In reply to Thomas Lübking from comment #7)
> (In reply to ioann from comment #6)
> 
> > At now, I ran Plasma session as "vblank_mode=0 /usr/bin/primusrun
> > /usr/bin/startkde".
> 
> I kinda doubt this works - startkde just forks a bunch of processes.
> Since your core interest seems kwin, shadow it with a bash script in ~/bin
> or /usr/local/bin
> (depending on whether you're on KDE4 or 5 it's "kwin" or "kwin_x11"
> 
> #!/bin/sh
> vblank_mode=0 /usr/bin/primusrun /usr/bin/kwin_x11
> 
> Don't forget to chmod +x that, but again: 
> a) you rather want to disable the intel IGP in BIOS
> b) fullscreen unredirection is no way worth it.

My BIOS not provide select for primary card. Please, tell me, where need add
your script for run KWin on descrete card?

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

[Breeze] [Bug 356082] Icon for save session is missing

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from andreas  ---
didn't know that there is an icon. do you know the icon Name?

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

[kde] [Bug 356055] login error

[venember via KDE Bugzilla]

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

venember  changed:

   What|Removed |Added

   Severity|normal  |critical

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

[plasmashell] [Bug 356394] New: Crash at some point while monitor power cycled

[via KDE Bugzilla]

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

Bug ID: 356394
   Summary: Crash at some point while monitor power cycled
   Product: plasmashell
   Version: 5.4.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: zeroping+kdeb...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.5.1
Operating System: Linux 4.2.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
I've been experiencing several different crashes when my monitor power cycles,
and this one seems unique, so I'll go ahead and report it.

This will probbly happen again soon, so I'm happy to do whatever I can to
provide more details. At the time of the crash, I'm running Debian Stretch,
with plasma-workspace at version 4:5.4.2-1+b1.

My main monitor is running at 3840x2160@60.00 on an Nvidia GeForce GTX 750
using the debian packaging of Nvidia's driver, version 340.96-2.

The crash can be reproduced sometimes.

-- 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 0x7f28613aa940 (LWP 28185))]

Thread 18 (Thread 0x7f284a9a9700 (LWP 28186)):
#0  0x7f285bae352d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f285fba0252 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f285fba1ddf in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f284c6ef569 in QXcbEventReader::run (this=0xb4b570) at
qxcbconnection.cpp:1229
#4  0x7f285c1cf87e in QThreadPrivate::start (arg=0xb4b570) at
thread/qthread_unix.cpp:331
#5  0x7f285b2ec0a4 in start_thread (arg=0x7f284a9a9700) at
pthread_create.c:309
#6  0x7f285baec06d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 17 (Thread 0x7f284934f700 (LWP 28188)):
#0  0x7f285badf5fd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f2854686f45 in ?? () from
/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.340.96
#2  0x7f28588d44d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2858890cc4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2858891180 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f28588912ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f285c40739b in QEventDispatcherGlib::processEvents
(this=0x7f283c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7f285c3ae35a in QEventLoop::exec (this=this@entry=0x7f284934ec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7f285c1ca8d4 in QThread::exec (this=this@entry=0xbcef90) at
thread/qthread.cpp:503
#9  0x7f285ea60105 in QQmlThreadPrivate::run (this=0xbcef90) at
qml/ftw/qqmlthread.cpp:141
#10 0x7f285c1cf87e in QThreadPrivate::start (arg=0xbcef90) at
thread/qthread_unix.cpp:331
#11 0x7f285b2ec0a4 in start_thread (arg=0x7f284934f700) at
pthread_create.c:309
#12 0x7f285baec06d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 16 (Thread 0x7f283bfff700 (LWP 28189)):
#0  0x7f285bae352d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f28588911dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f28588912ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f285c40739b in QEventDispatcherGlib::processEvents
(this=0x7f28340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f285c3ae35a in QEventLoop::exec (this=this@entry=0x7f283bffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f285c1ca8d4 in QThread::exec (this=this@entry=0xce4fc0) at
thread/qthread.cpp:503
#6  0x7f285ea60105 in QQmlThreadPrivate::run (this=0xce4fc0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f285c1cf87e in QThreadPrivate::start (arg=0xce4fc0) at
thread/qthread_unix.cpp:331
#8  0x7f285b2ec0a4 in start_thread (arg=0x7f283bfff700) at
pthread_create.c:309
#9  0x7f285baec06d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 15 (Thread 0x7f283a85f700 (LWP 28193)):
#0  0x7f285bae352d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f28588911dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f28588912ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f285c40739b in QEventDispatcherGlib::processEvents
(this=0x7f282c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f285c3ae35a in QEventLoop::exec (this=this@entry=0x7f283a85ec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f285c1ca8d4 in QThread::exec 

[kwin] [Bug 348753] more issues with nvidia legacy (304.xxx) blob and explicit syncing (here on login)

[Sergio via KDE Bugzilla]

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

--- Comment #45 from Sergio  ---
I got the whole of the array of updates that arrived via the Kubuntu ppa and
that included 5.4.3.

It may have not been kwin in the end, but maybe some animation effect or
something in the theme. I must admit that I have not been diligent enough to
try disabling the effects one by one or try changing the theme.

The issue was as follow:

- Plasma started providing a screen that was looking OK
- Immediately after that the bottom panel got distorted and everything hung
- Using Ctrl-Alt-F1 and Ctrl-Alt+F7 I could go back and forth between the text
console and X and in this way plasma seemed to be able to perform operations
one step "per switch".

In any case, the system with 7025 and nvidia 304 is usable again.

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

[Breeze] [Bug 356082] Icon for save session is missing

[Ömer via KDE Bugzilla]

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

Ömer  changed:

   What|Removed |Added

URL||http://imgur.com/OePEndP

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

[kdenlive] [Bug 356030] 15.11.80: track speaker icon coloring is ambiguous and inconsistent with other track icons

[via KDE Bugzilla]

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

--- Comment #2 from wegwerf-1-...@gmx.de ---
I can make a suitable icon for "disabled audio" following the same meme as for
"disabled video"; both for breeze light & dark.

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

[calligrawords] [Bug 356397] New: Calligra Words crashes when opening a docx file

[tetris4 via KDE Bugzilla]

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

Bug ID: 356397
   Summary: Calligra Words crashes when opening a docx file
   Product: calligrawords
   Version: unspecified
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: tetr...@gmail.com

Application: calligrawords (2.9.9)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.2.6-1-CHAKRA x86_64
Distribution: "Chakra"

-- Information about the crash:
- What I was doing when the application crashed:
I tried opening a .docx file trough dolphin. Calligra Words crashed on launch
before displaying any information.

This happens every time I try to launch the file. I unfortunately can't share
the related file, hopefully the backtrace is helpful by itself.

When I try to open the file through konsole, I get this in the output, repeated
several times before the crash:
words(18684)/kotext KoTextLoader::loadParagraph: paragraph style  "P2" not
found - using default style 
words(18684)/kotext KoTextLoader::loadSpan: character style  "T2"  not found

-- Backtrace:
Application: Calligra Words (calligrawords), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#6  0x7fe39c234b8c in QTextLine::y() const () at /usr/lib/libQtGui.so.4
#7  0x7fe39a684fba in KoTextDocumentLayout::positionAnchorTextRanges(int,
int, QTextDocument const*) () at /usr/lib/libkotextlayout.so.14
#8  0x7fe39a66d586 in KoTextLayoutArea::layoutBlock(FrameIterator*) () at
/usr/lib/libkotextlayout.so.14
#9  0x7fe39a67009b in KoTextLayoutArea::layout(FrameIterator*) () at
/usr/lib/libkotextlayout.so.14
#10 0x7fe39a682fbd in KoTextLayoutRootArea::layoutRoot(FrameIterator*) ()
at /usr/lib/libkotextlayout.so.14
#11 0x7fe39a6863c9 in KoTextDocumentLayout::doLayout() () at
/usr/lib/libkotextlayout.so.14
#12 0x7fe39a686a88 in KoTextDocumentLayout::layout() () at
/usr/lib/libkotextlayout.so.14
#13 0x7fe39b5be381 in QObject::event(QEvent*) () at /usr/lib/libQtCore.so.4
#14 0x7fe39bfc901c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQtGui.so.4
#15 0x7fe39bfcfa68 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQtGui.so.4
#16 0x7fe39cb22195 in KoApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkomain.so.14
#17 0x7fe39b5a521d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib/libQtCore.so.4
#18 0x7fe39b5a85e1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQtCore.so.4
#19 0x7fe39b5d414e in  () at /usr/lib/libQtCore.so.4
#20 0x7fe3981c4a1d in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#21 0x7fe3981c4d08 in  () at /usr/lib/libglib-2.0.so.0
#22 0x7fe3981c4dbc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#23 0x7fe39b5d42be in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQtCore.so.4
#24 0x7fe39c06fb66 in  () at /usr/lib/libQtGui.so.4
#25 0x7fe39b5a8ac1 in
QCoreApplication::processEvents(QFlags) () at
/usr/lib/libQtCore.so.4
#26 0x7fe3998f80bf in KoProgressUpdater::update() () at
/usr/lib/libkowidgetutils.so.14
#27 0x7fe39b5b9d1c in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib/libQtCore.so.4
#28 0x7fe39b5b9d1c in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib/libQtCore.so.4
#29 0x7fe3998f9551 in KoUpdater::sigProgress(int) () at
/usr/lib/libkowidgetutils.so.14
#30 0x7fe3998f95e7 in KoUpdater::setProgress(int) () at
/usr/lib/libkowidgetutils.so.14
#31 0x7fe39cb2eb9a in KoDocument::openFile() () at /usr/lib/libkomain.so.14
#32 0x7fe39cb38518 in KoDocument::openUrlInternal(KUrl const&) () at
/usr/lib/libkomain.so.14
#33 0x7fe39cb38933 in KoDocument::openUrl(KUrl const&) () at
/usr/lib/libkomain.so.14
#34 0x7fe39cb43164 in KoMainWindow::openDocumentInternal(KUrl const&,
KoPart*, KoDocument*) () at /usr/lib/libkomain.so.14
#35 0x7fe39cb43721 in KoMainWindow::openDocument(KoPart*, KUrl const&) ()
at /usr/lib/libkomain.so.14
#36 0x7fe39cb1e82c in KoApplication::start() () at /usr/lib/libkomain.so.14
#37 0x7fe39d1863b0 in kdemain(int, char**) (argc=,
argv=) at
/chakra/desktop/calligra/src/calligra-2.9.9/words/app/main.cpp:42
#38 0x7fe39cdff610 in __libc_start_main () at /usr/lib/libc.so.6
#39 0x00400739 in _start ()

Possible duplicates by query: bug 345813, bug 332220.

Reported using DrKonqi

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

[kmymoney] [Bug 356399] New: crash while saving file after report change with data loss

[Michał via KDE Bugzilla]

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

Bug ID: 356399
   Summary: crash while saving file after report change with data
loss
   Product: kmymoney
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: kice...@gmail.com

I've edited one of existing report templates (Income and Expenses By Year).
After that I pressed Ctrl+S and it caused application to crash. What is worse
my .kmy file become 0 bytes in size (luckly I had fresh backup).

It happens every time I try to reproduce it.

Reproducible: Always

Steps to Reproduce:
1. edit Income and Expenses By Year report template
2. save kmy file
3. crash

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

[valgrind] [Bug 354931] Analyze of qt app results in incompatible processor message

[via KDE Bugzilla]

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

mchesh...@gmail.com changed:

   What|Removed |Added

 CC||mchesh...@gmail.com

--- Comment #1 from mchesh...@gmail.com ---
I have same thing.

Gentoo amd64
Qt 5.4.2
Intel(R) Core(TM) i7-4600M CPU @ 2.90GHz

What I found:
I have -march=native in CFLAGS, that cause gcc to enable -mrtm on my CPU

$ LANG=C gcc -march=native -Q --help=target | grep rtm
  -mrtm   [enabled]

It reflects __RTM__ define, and qCompilerCpuFeatures now includes RTM
(http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/tools/qsimd_p.h?id=fae33bfbe35f8d082b420ee09662ff60634cb355=5.4#n264),
and requires it in runtime.

But all amd64 CPUID helpers have nothing set in RBX if EAX is 0x8007.

That does not hit HLE, because Qt disable check in runtime
(http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/tools/qsimd.cpp?id=fae33bfbe35f8d082b420ee09662ff60634cb355=5.4#n499)

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

[kdevplatform] [Bug 356293] Segfault in KDevelop::Stack while parsing projects.

[via KDE Bugzilla]

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

bunge...@gmail.com changed:

   What|Removed |Added

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

--- Comment #3 from bunge...@gmail.com ---
Hmmm... I thought I was, in that I ran 'ninja' and it re-ran cmake and then did
'ninja install' on both kdevplatfrom and kdevelop. However, after taking a
closer look, it doesn't appear everything required to be rebuilt actually was.
I deleted the install directory and the build directories and rebuilt from
scratch. I'm no longer seeing this issue, so I think you're right here. I'll
make this as resolved then. Thanks for pointing out that this wasn't possible
in 5.0.

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

[muon] [Bug 347284] update notifier gets available updates count wrong

[michael via KDE Bugzilla]

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

--- Comment #8 from michael  ---
Created https://git.reviewboard.kde.org/r/126284. Security updates are now
correctly accounted for in MuonNotifier. No more double counting there. On my
machine the count can also be lower than the actually package count for
non-security updates. I don't know if this is still the case. Now works for me
if only security updates are found not yet tested in other cases.

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

[kde] [Bug 356400] New: KCrash: Application 'plasma-desktop' crashing...

[RichT via KDE Bugzilla]

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

Bug ID: 356400
   Summary: KCrash: Application 'plasma-desktop' crashing...
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: rtp...@gmail.com

Application: plasma-desktop (4.11.13)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 8.2 (jessie)

-- Information about the crash:
- What I was doing when the application crashed:
I had a folder on desktop showing contents of a file system folder.  I dragged
in and went too far and it got on my second monitor.  I tried to drag it back
and the crash occurred.

-- 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 0x7fa9a6df1800 (LWP 1543))]

Thread 3 (Thread 0x7fa97c74c700 (LWP 1558)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa99f901dea in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fa99fc02f80 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7fa99f901e19 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7fa99a12f0a4 in start_thread (arg=0x7fa97c74c700) at
pthread_create.c:309
#4  0x7fa9a67fb04d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fa8f62ff700 (LWP 1570)):
#0  0x7fff343d5e4e in clock_gettime ()
#1  0x7fa9a6807c9d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fa9a31d4a05 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fa9a32b7b85 in updateCurrentTime (this=0x7fa8f00030d0) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fa8f00030d0, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fa9a32b646c in timerSourcePrepareHelper (src=,
timeout=0x7fa8f62febb4) at kernel/qeventdispatcher_glib.cpp:136
#7  0x7fa9a32b6535 in timerSourcePrepare (source=,
timeout=) at kernel/qeventdispatcher_glib.cpp:169
#8  0x7fa99980b45d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fa99980be0b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fa99980bffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fa9a32b6d37 in QEventDispatcherGlib::processEvents
(this=0x7fa8f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fa9a3286271 in QEventLoop::processEvents
(this=this@entry=0x7fa8f62fed80, flags=...) at kernel/qeventloop.cpp:149
#13 0x7fa9a32865d5 in QEventLoop::exec (this=this@entry=0x7fa8f62fed80,
flags=...) at kernel/qeventloop.cpp:204
#14 0x7fa9a317ae99 in QThread::exec (this=this@entry=0x23bb480) at
thread/qthread.cpp:538
#15 0x7fa9a3266ac3 in QInotifyFileSystemWatcherEngine::run (this=0x23bb480)
at io/qfilesystemwatcher_inotify.cpp:265
#16 0x7fa9a317d70f in QThreadPrivate::start (arg=0x23bb480) at
thread/qthread_unix.cpp:349
#17 0x7fa99a12f0a4 in start_thread (arg=0x7fa8f62ff700) at
pthread_create.c:309
#18 0x7fa9a67fb04d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fa9a6df1800 (LWP 1543)):
[KCrash Handler]
#6  0x04ca7940 in ?? ()
#7  0x7fa984f1cb6b in GroupingContainment::sceneEventFilter(QGraphicsItem*,
QEvent*) () from /usr/lib/libplasma_groupingcontainment.so.4
#8  0x7fa9a2be68ac in QGraphicsScenePrivate::filterEvent
(this=this@entry=0x1c24a40, item=item@entry=0x1ce0340,
event=event@entry=0x7fff343b3000) at graphicsview/qgraphicsscene.cpp:1181
#9  0x7fa9a2be6941 in QGraphicsScenePrivate::sendEvent (this=0x1c24a40,
item=0x1ce0340, event=0x7fff343b3000) at graphicsview/qgraphicsscene.cpp:1209
#10 0x7fa9a2bf0af1 in QGraphicsScenePrivate::sendHoverEvent
(this=this@entry=0x1c24a40, type=type@entry=QEvent::GraphicsSceneHoverEnter,
item=0x1ce0340, hoverEvent=hoverEvent@entry=0x7fff343b3100) at
graphicsview/qgraphicsscene.cpp:1268
#11 0x7fa9a2bf0e72 in QGraphicsScenePrivate::dispatchHoverEvent
(this=this@entry=0x1c24a40, hoverEvent=hoverEvent@entry=0x7fff343b3100) at
graphicsview/qgraphicsscene.cpp:3939
#12 0x7fa9a2bf133a in QGraphicsScene::mouseMoveEvent (this=,
mouseEvent=0x7fff343b3490) at graphicsview/qgraphicsscene.cpp:4097
#13 0x7fa9a2bfe2ef in QGraphicsScene::event (this=0x1bf9920,
event=0x7fff343b3490) at graphicsview/qgraphicsscene.cpp:3451
#14 0x7fa9a25d848c in QApplicationPrivate::notify_helper

[kde] [Bug 356055] login error

[venember via KDE Bugzilla]

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

--- Comment #4 from venember  ---
kactivity segfault in libQt5Sql.so.5.5.1 

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

[ksmserver] [Bug 356021] Language indicator too narrow in locked screen

[george via KDE Bugzilla]

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

--- Comment #2 from george  ---
I see have marked it as duplicate but the other ticket says "resolved fixed"
but it is not. At least not completely.

The button size is indeed fixed but when I switch from 'us' to 'bg (phonetic)'
and back to 'us' - there is no text on the button. Again switch twice - still
no text.

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

[ksmserver] [Bug 356021] Language indicator too narrow in locked screen

[george via KDE Bugzilla]

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

--- Comment #4 from george  ---
5.4.3

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

[okular] [Bug 353401] Feature requst: "typewriter" annotation tool

[noric via KDE Bugzilla]

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

--- Comment #9 from noric  ---
I asked Poppler's devs and they say FreeText is already implemented in Poppler.
They say the actual typewriter tool needs to be implemented by Okular (and
other readers relying on Poppler).

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

[kio] [Bug 356198] Creating new link to application is missing the Application tab (KNewFileMenu, KPropertiesDialog)

[via KDE Bugzilla]

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

--- Comment #4 from bog...@hlevca.com ---
I am not the only one having the issue. See below:

https://forum.kde.org/viewtopic.php?f=289=129585=49d32f35a1f946534bb8301f11d0ea4b

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

[plasmashell] [Bug 356205] New: Applications are minimized and Windows decorations disappear after monitor turned off

[via KDE Bugzilla]

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

Bug ID: 356205
   Summary: Applications are minimized and Windows decorations
disappear after monitor turned off
   Product: plasmashell
   Version: 5.4.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bog...@hlevca.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Applications are minimized and Windows decorations disappear after monitor
turned off. 

After turning back on the monitor the running applications show only in the
task bar,  but they cannot be shown on the desktop screen
Newly started applications show on the desktop but they do not have decorations
(title bar, etc) whether they are KDE or Gnome applications. 

Running   
  "KWIN_EXPLICIT_SYNC=0 kwin_x11 --replace"
restores the decoration and application can be shown on the desktop but they
appear in a very minimized state Title bar and bottom bar.

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

[plasmashell] [Bug 356207] New: plasmashell crashes occasionally when changing connection in NM applet

[via KDE Bugzilla]

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

Bug ID: 356207
   Summary: plasmashell crashes occasionally when changing
connection in NM applet
   Product: plasmashell
   Version: 5.4.3
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rectifie...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.13 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
Switching wireless access points using NetworkManager applet icon, not tsted
with wired ethernet

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 0x7f659d1b6800 (LWP 15196))]

Thread 8 (Thread 0x7f6588159700 (LWP 15212)):
#0  0x7f6594bee40d in poll () at /lib64/libc.so.6
#1  0x7f659affc102 in  () at /usr/lib64/libxcb.so.1
#2  0x7f659affdc8f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f6589b5fa99 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f6595802f6f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f65938b1704 in start_thread () at /lib64/libpthread.so.0
#6  0x7f6594bf9aed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f657a721700 (LWP 15287)):
#0  0x7f658fbb4f84 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f658fb71f90 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f658fb728e0 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f658fb72abc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f6595a26c9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f65959d0fda in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f65957fe16c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f6599ac1845 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f6595802f6f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f65938b1704 in start_thread () at /lib64/libpthread.so.0
#10 0x7f6594bf9aed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f6570e21700 (LWP 15295)):
#0  0x7f65938b740f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f65739e63aa in  () at /usr/lib64/xorg/modules/dri/r600_dri.so
#2  0x7f65739e5bd7 in  () at /usr/lib64/xorg/modules/dri/r600_dri.so
#3  0x7f65938b1704 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6594bf9aed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f656af71700 (LWP 15296)):
#0  0x7f658fbb4f84 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f658fb7296e in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f658fb72abc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6595a26c9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f65959d0fda in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f65957fe16c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f6599ac1845 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f6595802f6f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f65938b1704 in start_thread () at /lib64/libpthread.so.0
#9  0x7f6594bf9aed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f6568c69700 (LWP 15300)):
#0  0x7f6594be9f7d in read () at /lib64/libc.so.6
#1  0x7f658fbb3c80 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f658fb724bc in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f658fb72958 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f658fb72abc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f6595a26c9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f65959d0fda in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f65957fe16c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f6599ac1845 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f6595802f6f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f65938b1704 in start_thread () at /lib64/libpthread.so.0
#11 0x7f6594bf9aed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f65631c1700 (LWP 15362)):
#0  0x7f65938b740f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f659c8a8734 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f659c8a8779 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f65938b1704 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6594bf9aed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f64dbfff700 (LWP 15588)):
#0  0x7f658fbb4f69 in 

[systemsettings] [Bug 355671] Font Preview Panel not Rendering Correctly

[Joe via KDE Bugzilla]

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

Joe  changed:

   What|Removed |Added

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

--- Comment #4 from Joe  ---
Marking as dup of 336089.

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

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

[kde] [Bug 356202] New: wake from sleep crash notification

[Brandon via KDE Bugzilla]

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

Bug ID: 356202
   Summary: wake from sleep crash notification
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: br3an...@gmail.com

Application: kdeinit5 ()

Qt Version: 5.4.1
Operating System: Linux 3.19.0-33-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed: Just had awoken the computer
from sleep when this bug notification appeared

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

Thread 4 (Thread 0x7f1935fb6700 (LWP 2074)):
#0  0x7f1947f398dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1946430b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f194643264f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f193879f099 in QXcbEventReader::run (this=0x2353ca0) at
qxcbconnection.cpp:1105
#4  0x7f19482abb0e in QThreadPrivate::start (arg=0x2353ca0) at
thread/qthread_unix.cpp:337
#5  0x7f1945b846aa in start_thread (arg=0x7f1935fb6700) at
pthread_create.c:333
#6  0x7f1947f44eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f192a287700 (LWP 2094)):
#0  0x7f1947f398dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1945127ebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1945127fcc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1948542c6c in QEventDispatcherGlib::processEvents
(this=0x7f19240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#4  0x7f19484e73e2 in QEventLoop::exec (this=this@entry=0x7f192a286e00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f19482a6b44 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f192d976cf7 in KCupsConnection::run() () from
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#7  0x7f19482abb0e in QThreadPrivate::start (arg=0x240fc90) at
thread/qthread_unix.cpp:337
#8  0x7f1945b846aa in start_thread (arg=0x7f192a287700) at
pthread_create.c:333
#9  0x7f1947f44eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f1923fff700 (LWP 2095)):
#0  0x7f1947f398dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1945127ebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1945127fcc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1948542c6c in QEventDispatcherGlib::processEvents
(this=0x7f191c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#4  0x7f19484e73e2 in QEventLoop::exec (this=this@entry=0x7f1923ffee40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f19482a6b44 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f19482abb0e in QThreadPrivate::start (arg=0x242a2b0) at
thread/qthread_unix.cpp:337
#7  0x7f1945b846aa in start_thread (arg=0x7f1923fff700) at
pthread_create.c:333
#8  0x7f1947f44eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f1949835780 (LWP 2072)):
[KCrash Handler]
#6  0x7f193ebb22f4 in KNotification::id (this=this@entry=0x493ea20) at
../../src/knotification.cpp:389
#7  0x7f193ebb3569 in KNotificationManager::notifyPluginFinished
(this=0x7f193ede7e90 <(anonymous
namespace)::Q_QGS_s_self::innerFunction()::holder>, notification=0x493ea20) at
../../src/knotificationmanager.cpp:115
#8  0x7f193ebb49ac in KNotificationManager::qt_static_metacall
(_o=0x493ea20, _c=76802592, _id=2, _a=0x7ffd8b8402d0) at
./moc_knotificationmanager_p.cpp:83
#9  0x7f194851a9c9 in QMetaObject::activate (sender=sender@entry=0x25b5eb0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffd8b8402d0) at kernel/qobject.cpp:3716
#10 0x7f194851b057 in QMetaObject::activate (sender=sender@entry=0x25b5eb0,
m=m@entry=0x7f193ede5be0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd8b8402d0)
at kernel/qobject.cpp:3582
#11 0x7f193ebd5b7f in KNotificationPlugin::finished
(this=this@entry=0x25b5eb0, _t1=0x493ea20) at moc_knotificationplugin.cpp:139
#12 0x7f193ebc5725 in KNotificationPlugin::finish
(this=this@entry=0x25b5eb0, notification=) at
../../src/knotificationplugin.cpp:52
#13 0x7f193ebc7130 in NotifyByPopup::onPassivePopupDestroyed
(this=0x25b5eb0) at ../../src/notifybypopup.cpp:309
#14 0x7f194851a9c9 in QMetaObject::activate (sender=sender@entry=0x4915a10,
signalOffset=, local_signal_index=local_signal_index@entry=0,

[systemsettings] [Bug 336089] Font preview - rendering problem

[Al via KDE Bugzilla]

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

Al  changed:

   What|Removed |Added

 CC||ahw...@verizon.net

--- Comment #23 from Al  ---
I am seeing the same as well, including the observation in comment #18.
Fedora 22 and 23 both display the problem, 22 is using NVIDIA 340 driver, 23 is
using nouveau.
Also my F22 and F23 virtual box machines have no problem at all.
All systems are current updates against the base and updates repositories, no
testing repo's.

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

[kdenlive] [Bug 356209] New: Copying Effects messes up parameters (Fade

[via KDE Bugzilla]

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

Bug ID: 356209
   Summary: Copying Effects messes up parameters (Fade
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: qubo...@gmail.com

Steps to reproduce:
1. Start Kdenlive
2. Add video clip (with audio stream)
3. Place clip twice in timeline
4. Add Fade from black and Fade in effects to first clip in timeline in this
order
5. Change effect duration parameter values to 10 and 15 frames
6. Copy the clip that has the effects
7. Paste the effects to the second clip

Expected result:
1. Second clip has identical effect parameters

Actual result:
1. Second clip's Fade in effect has 10 frames duration instead of 15.

Reproduceable always.

Video: https://youtu.be/b4VYyhZ5Pkw

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

[dolphin] [Bug 352923] Dolphin closes unexpectedly when using the context menu

[via KDE Bugzilla]

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

jcolangel...@gmail.com changed:

   What|Removed |Added

 CC||jcolangel...@gmail.com

--- Comment #2 from jcolangel...@gmail.com ---
Having the same issue, except it only happens while I'm running ffmpeg in
terminal.

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

[dolphin] [Bug 356208] New: No icons for X.509 certificate files

[via KDE Bugzilla]

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

Bug ID: 356208
   Summary: No icons for X.509 certificate files
   Product: dolphin
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: icons mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: jcolangel...@gmail.com

Icons do not display for X.509 certificate files in Dolphin

Reproducible: Always

Steps to Reproduce:
1.Open folder containing X.509 certificate files.
2.
3.

Actual Results:  
Files do not have icons.

Expected Results:  
Display the icons.

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

[plasmashell] [Bug 356026] Plasma crashed nth time - without any external display also

[via KDE Bugzilla]

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

dabs...@gmx.com changed:

   What|Removed |Added

 CC||dabs...@gmx.com

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

[kdevelop] [Bug 355685] Kdevelop C++ parser crash

[RJVB via KDE Bugzilla]

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

--- Comment #11 from RJVB  ---
No, not I, at least not that I know of ...

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

[systemsettings] [Bug 356172] kde clock is wrong even though set to automatic. unchecking auto then re-checking causes a crash but time is fixed

[via KDE Bugzilla]

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

alick_gardi...@hotmail.com changed:

   What|Removed |Added

 CC||alick_gardi...@hotmail.com

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

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

Rafael  changed:

   What|Removed |Added

  Attachment #95851|Some letters are hidden |Some letters are hidden.
description||Below the time "martes, 1
   ||de diciembre de 2015" and
   ||"Desbloquear" in the
   ||button.

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

[kdevelop] [Bug 355099] Crash when expanding project folder in Projects tab

[Alexander via KDE Bugzilla]

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

--- Comment #7 from Alexander  ---
Hi,
The project I was testing it with is not FOSS, but I re-ran kdevelop with an
open source one and still got a crash. Here's the checkout URL for easy
testing:
svn checkout svn://svn.code.sf.net/p/gsmartcontrol/code/trunk gsmartcontrol


This is the valgrind output (there are no warnings except that IOCTL one until
I expand the project tree).

> valgrind --track-origins=yes --smc-check=all-non-file kdevelop
==30551== Memcheck, a memory error detector
==30551== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==30551== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==30551== Command: kdevelop
==30551== 
Ninja plugin installed but ninja is not installed.
Could not load plugin "KDevNinjaBuilder" , it reported the error: "" Disabling
the plugin now.
Ninja plugin installed but ninja is not installed.
Could not load plugin "KDevNinjaBuilder" , it reported the error: "" Disabling
the plugin now.
The font for use in the terminal has not been matched exactly. Perhaps it has
not been found properly.
The font for use in the terminal has not been matched exactly. Perhaps it has
not been found properly.
==30551== Warning: noted but unhandled ioctl 0x6458 with no size/direction
hints.
==30551==This could cause spurious value errors to appear.
==30551==See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a
proper wrapper.
settingsFile:  "/home/alex"
settingsFile:  "/home/alex"
settingsFile:  "/home/alex"
settingsFile:  "/home/alex"
==30551== Thread 11 Queue(0x292381e0)[06]:
==30551== Invalid read of size 8
==30551==at 0x355C3420: svn_utf__cstring_is_valid (in
/usr/lib64/libsvn_subr-1.so.0.0.0)
==30551==by 0x355C2580: ??? (in /usr/lib64/libsvn_subr-1.so.0.0.0)
==30551==by 0x355C2B0B: svn_utf_cstring_from_utf8 (in
/usr/lib64/libsvn_subr-1.so.0.0.0)
==30551==by 0x355AF795: svn_path_cstring_from_utf8 (in
/usr/lib64/libsvn_subr-1.so.0.0.0)
==30551==by 0x3559C42F: svn_dirent_get_absolute (in
/usr/lib64/libsvn_subr-1.so.0.0.0)
==30551==by 0x34EF13F4: svn_client_info2 (in
/usr/lib64/libsvn_client-1.so.0.0.0)
==30551==by 0x34EF1442: svn_client_info (in
/usr/lib64/libsvn_client-1.so.0.0.0)
==30551==by 0x34C8A6C3: svn::Client::info(svn::Path const&, bool,
svn::Revision const&, svn::Revision const&) (in
/opt/local/kdevelop/lib64/plugins/kdevplatform/24/kdevsubversion.so)
==30551==by 0x34C6DF5E:
SvnInternalInfoJob::run(QSharedPointer,
ThreadWeaver::Thread*) (in
/opt/local/kdevelop/lib64/plugins/kdevplatform/24/kdevsubversion.so)
==30551==by 0x10621B9F:
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.15.0)
==30551==by 0x1062092F:
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.15.0)
==30551==by 0x1061FF39: ThreadWeaver::Thread::run() (in
/usr/lib64/libKF5ThreadWeaver.so.5.15.0)
==30551==  Address 0x29765e50 is 80 bytes inside a block of size 86 alloc'd
==30551==at 0x4C29670: operator new(unsigned long) (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==30551==by 0xC199918: std::string::_Rep::_S_create(unsigned long, unsigned
long, std::allocator const&) (in /usr/lib64/libstdc++.so.6.0.21)
==30551==by 0xC199BEA: std::string::_M_mutate(unsigned long, unsigned long,
unsigned long) (in /usr/lib64/libstdc++.so.6.0.21)
==30551==by 0xC19A20D: std::string::_M_replace_safe(unsigned long, unsigned
long, char const*, unsigned long) (in /usr/lib64/libstdc++.so.6.0.21)
==30551==by 0x34C9048A: svn::Path::init(char const*) (in
/opt/local/kdevelop/lib64/plugins/kdevplatform/24/kdevsubversion.so)
==30551==by 0x34C9032F: svn::Path::Path(char const*) (in
/opt/local/kdevelop/lib64/plugins/kdevplatform/24/kdevsubversion.so)
==30551==by 0x34C6DF28:
SvnInternalInfoJob::run(QSharedPointer,
ThreadWeaver::Thread*) (in
/opt/local/kdevelop/lib64/plugins/kdevplatform/24/kdevsubversion.so)
==30551==by 0x10621B9F:
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.15.0)
==30551==by 0x1062092F:
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.15.0)
==30551==by 0x1061FF39: ThreadWeaver::Thread::run() (in
/usr/lib64/libKF5ThreadWeaver.so.5.15.0)
==30551==by 0xBA9755E: QThreadPrivate::start(void*) (qthread_unix.cpp:331)
==30551==by 0x12FF10A3: start_thread (in /lib64/libpthread-2.19.so)
==30551== 
job started 0x41decc40
job done SvnInternalInfoJob(0x41decc40)
==30551== Thread 1:
==30551== Invalid read of size 2
==30551==at 0xB2EBB30: QTransform::type() const (in
/usr/lib64/libQt5Gui.so.5.5.0)
==30551==by 0xB27C3A9: ??? (in /usr/lib64/libQt5Gui.so.5.5.0)
==30551==by 0xB284137: QRasterPaintEngine::drawPixmap(QRectF const&,
QPixmap const&, QRectF const&) 

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[via KDE Bugzilla]

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

--- Comment #49 from tom.zoeh...@gmail.com ---
I just tested kglobalaccel 5.16 in arch linux and while 'ctrl + !' now works as
a shortcut, neither 'ctrl + "' nor 'ctrl + §' work, so this seems to only be a
partial fix.

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

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

--- Comment #89 from Rafael  ---
Created attachment 95851
  --> https://bugs.kde.org/attachment.cgi?id=95851=edit
Some letters are hidden

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

[digikam] [Bug 355831] MySQL Schema Improvements

[via KDE Bugzilla]

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

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

   What|Removed |Added

  Attachment #95824|0   |1
is obsolete||

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

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

--- Comment #88 from Rafael  ---
Ok with STR.  I must say that I ONLY have "bricky text" on the screen lock form
window. Just some hours ago I had a similar issue (see the next screenshot) but
this time I even can only enter my password in one of my monitors, exactly the
other one that have not that issue. Apparently, this problem always happen in
my DVI monitor, not in the VGA monitor (if it can help someway). 

But disable screenlock will not do nothing about the "bricked text", cause it
only appears on the screenlock window.

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

[krita] [Bug 356146] Krita doesn't honor cursor size

[via KDE Bugzilla]

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

--- Comment #2 from tylerecout...@gmail.com ---
Can you change the  pointer cursor (arrow) ,  or just the brush cursors when on
the canvas? 

Seems logical/intuitive to use the system pointer in place of the arrow, and
Krita's cursors on the canvas (brush outlines etc.) 

If there's a way to change the arrow in Krita, then that's an easy work around,
but I didn't see it.

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

[digikam] [Bug 355831] MySQL Schema Improvements

[via KDE Bugzilla]

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

--- Comment #41 from caulier.gil...@gmail.com ---
Git commit 9b543e6a84a15af6d29f70c39a4964992f42e7cf by Gilles Caulier.
Committed on 01/12/2015 at 21:34.
Pushed by cgilles into branch 'master'.

Apply patch #95825 to :
Allows the thumbnail and main image databases to be contained within the same
database.
Also ensure that thumbnail MySQL tables use the InnoDB storage engine and not
the older MyISAM engine.

M  +66   -10   data/database/dbconfig.xml.cmake.in
M  +27   -4libs/database/thumbsdb/thumbsdb.cpp
M  +1-0libs/database/thumbsdb/thumbsdb.h
M  +23   -1libs/database/thumbsdb/thumbsdbchemaupdater.cpp
M  +1-0libs/database/thumbsdb/thumbsdbchemaupdater.h

http://commits.kde.org/digikam/9b543e6a84a15af6d29f70c39a4964992f42e7cf

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

[digikam] [Bug 355831] MySQL Schema Improvements

[via KDE Bugzilla]

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

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

   What|Removed |Added

  Attachment #95825|0   |1
is obsolete||

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

[systemsettings] [Bug 356172] New: kde clock is wrong even though set to automatic. unchecking auto then re-checking causes a crash but time is fixed

[via KDE Bugzilla]

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

Bug ID: 356172
   Summary: kde clock is wrong even though set to automatic.
unchecking auto then re-checking causes a crash but
time is fixed
   Product: systemsettings
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: alick_gardi...@hotmail.com

Application: kcmshell4 (4.14.6)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-29-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

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

using opensuse 13.2 KDE desktop
auto time and date is wrong (time is usually only a few minutes out every now
and then)
navigate to adjust date and time
uncheck 'set time automatically'
re-check 'set time automatically'
crash happens
time is now correct

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Control Module (kcmshell4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2e85a9d780 (LWP 20053))]

Thread 3 (Thread 0x7f2e63fe7700 (LWP 20054)):
#0  0x7f2e830c8c5d in poll () at /lib64/libc.so.6
#1  0x7f2e801dbbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f2e801dbf0a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x7f2e642e8946 in  () at /usr/lib64/libgio-2.0.so.0
#4  0x7f2e80200b85 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f2e843640a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f2e830d108d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f2e62c00700 (LWP 20055)):
#0  0x7f2e84729271 in  () at /usr/lib64/libQtCore.so.4
#1  0x7f2e801db661 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f2e801dbb7b in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f2e801dbcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f2e847290de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7f2e846fae6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f2e846fb165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f2e845f80bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7f2e846dc783 in  () at /usr/lib64/libQtCore.so.4
#9  0x7f2e845fa79f in  () at /usr/lib64/libQtCore.so.4
#10 0x7f2e843640a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f2e830d108d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f2e85a9d780 (LWP 20053)):
[KCrash Handler]
#5  0x01c68c98 in  ()
#6  0x7f2e847113e9 in QObject::connect(QObject const*, char const*, QObject
const*, char const*, Qt::ConnectionType) () at /usr/lib64/libQtCore.so.4
#7  0x7f2e847192ec in  () at /usr/lib64/libQtCore.so.4
#8  0x7f2e847193ae in QTimer::singleShot(int, QObject*, char const*) () at
/usr/lib64/libQtCore.so.4
#9  0x7f2e69d676c3 in  () at /usr/lib64/kde4/kcm_clock.so
#10 0x7f2e74f088e7 in KCModuleProxy::save() () at
/usr/lib64/libkcmutils.so.4
#11 0x7f2e74f04b98 in  () at /usr/lib64/libkcmutils.so.4
#12 0x7f2e847101fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#13 0x7f2e8556142f in KPushButton::authorized(KAuth::Action*) () at
/usr/lib64/libkdeui.so.5
#14 0x7f2e847101fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#15 0x7f2e83ec1bb2 in QAbstractButton::clicked(bool) () at
/usr/lib64/libQtGui.so.4
#16 0x7f2e83c24fe3 in  () at /usr/lib64/libQtGui.so.4
#17 0x7f2e83c26153 in  () at /usr/lib64/libQtGui.so.4
#18 0x7f2e83c2623c in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /usr/lib64/libQtGui.so.4
#19 0x7f2e838c7c0a in QWidget::event(QEvent*) () at
/usr/lib64/libQtGui.so.4
#20 0x7f2e8387876c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#21 0x7f2e8387edea in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#22 0x7f2e8549fe0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#23 0x7f2e846fc2ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#24 0x7f2e8387e5e3 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib64/libQtGui.so.4
#25 0x7f2e838efc9b in  () at /usr/lib64/libQtGui.so.4
#26 0x7f2e838ee70c in QApplication::x11ProcessEvent(_XEvent*) () at
/usr/lib64/libQtGui.so.4
#27 0x7f2e839155c2 in  () at /usr/lib64/libQtGui.so.4
#28 0x7f2e801dba04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0

[kio] [Bug 344741] Dolphin freezes while displayed files' content are modified

[via KDE Bugzilla]

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

--- Comment #9 from tesfab...@gmail.com ---
Hi, 
this bug is still present in KIO 5.16.0 (maybe would it be the case to update
the KIO version in this bug?)

I did `time testparm -d0 -s --parameter-name` and it gives:
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
server string = %h server (Samba, Ubuntu)
server role = standalone server
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n
*Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = No
usershare path = /var/lib/samba/usershare
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb


[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
browseable = No


[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
testparm -d0 -s --parameter-name  0,02s user 0,00s system 90% cpu 0,026 total


To easily test this just update ABS (if you're on ArchLinux) while staying into
the /var/abs/extra directory.
At the end of the sync (or during?) dolphin should hang for a long time...

Thanks!

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

[plasmashell] [Bug 356189] New: Audio output switcher in systemtray

[via KDE Bugzilla]

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

Bug ID: 356189
   Summary: Audio output switcher in systemtray
   Product: plasmashell
   Version: 5.4.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: ad1r...@hotmail.fr

I have multiple audio output and i spend huge time to switch it on configure
panel, it's possible to add an output switch in system tray, on new icon or in
the audio icon. I think it can be fine :)

Reproducible: Always

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

[plasmashell] [Bug 356189] Audio output switcher in systemtray

[via KDE Bugzilla]

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

ad1r...@hotmail.fr changed:

   What|Removed |Added

 CC||ad1r...@hotmail.fr

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

[krita] [Bug 356007] Converting color space overwrites undo history

[Storm via KDE Bugzilla]

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

--- Comment #2 from Storm  ---
I can still reproduce with a fresh build of the Pentikainen LOD/Animation
branch.

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

[digikam] [Bug 355831] MySQL Schema Improvements

[via KDE Bugzilla]

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

--- Comment #51 from caulier.gil...@gmail.com ---
Git commit 5c1416f17b230a598b8938ee3a18bb31b65303d0 by Gilles Caulier.
Committed on 02/12/2015 at 21:21.
Pushed by cgilles into branch 'master'.

Apply patch #95865 to rewrite MySQL database creation and setup guidance.
The MySQL password is tied to the account not the database.

M  +10   -8libs/database/utils/dbsettingswidget.cpp

http://commits.kde.org/digikam/5c1416f17b230a598b8938ee3a18bb31b65303d0

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

[Breeze] [Bug 356212] Breeze-dark icons theme missing inherited icons (#345957 is back)

[andreas via KDE Bugzilla]

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

--- Comment #2 from andreas  ---
Hi,

in the past the breeze-dark icon set only include the monochrome icons. after
this bug breeze and breeze-dark icons are standalone so you have all icons in
breeze icons and breeze-dark icons so breeze wouldn't be the inherits of
breeze-dark.

can you submit an screenshot

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

[Breeze] [Bug 356212] Breeze-dark icons theme missing inherited icons (#345957 is back)

[andreas via KDE Bugzilla]

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

--- Comment #6 from andreas  ---
you cant use breeze dark icons on breeze color scheme. you need breeze dark
color scheme if you want to use breeze dark icons. sorry this is a design
decision when you use monochrome icons.

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

[digikam] [Bug 310106] MYSQL : try to access to database from two computers and collections get lost

[via KDE Bugzilla]

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

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

   What|Removed |Added

  Component|Database-Mysql  |Database-Multiusers

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

[Breeze] [Bug 356212] Breeze-dark icons theme missing inherited icons (#345957 is back)

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #7 from andreas  ---
you can't usw white icons in a white background.

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

[digikam] [Bug 149475] SETUP : add support of collections in read only

[via KDE Bugzilla]

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

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

   What|Removed |Added

  Component|Database-Setup  |Database-Multiusers

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

[digikam] [Bug 243205] SETUP : adding NFS4 network location to local library sees only some dirs

[via KDE Bugzilla]

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

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

   What|Removed |Added

  Component|Database-Setup  |Database-Multiusers

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

[plasmashell] [Bug 356035] Panel does not refresh/update/animate when compositor is off

[via KDE Bugzilla]

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

--- Comment #2 from emp...@adslgr.com ---
As I stated in my original post, yes it does. It seems that the elements
(icons, widgets) are in fact there but they are not being shown or getting
drawn.

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

[digikam] [Bug 355831] MySQL Schema Improvements

[via KDE Bugzilla]

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

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

   What|Removed |Added

  Attachment #95865|0   |1
is obsolete||

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

[korganizer] [Bug 356216] Time selection is truncated

[sparhawk via KDE Bugzilla]

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

sparhawk  changed:

   What|Removed |Added

Version|GIT (master)|unspecified

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

[korganizer] [Bug 356216] New: Time selection is truncated

[sparhawk via KDE Bugzilla]

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

Bug ID: 356216
   Summary: Time selection is truncated
   Product: korganizer
   Version: GIT (master)
  Platform: Archlinux Packages
   URL: https://i.imgur.com/LXIBuah.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: kdeb...@plast.id.au

If I attempt to change the time in the dropdown menu, many entries are
truncated. From the screenshot, the minutes are missing. I can expand the
window horizontally, but this does not fix the problem.

https://i.imgur.com/LXIBuah.png

Reproducible: Always

Steps to Reproduce:
1. Edit and event.
2. Click on the time to change it.

Actual Results:  
Entries are truncated, even when making the window large.

Expected Results:  
Entries are fully visible.

Korganizer 4.14.10 (this wasn't available in the selections)
Arch Linux

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

[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[via KDE Bugzilla]

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

--- Comment #11 from bluescreen_aven...@verizon.net ---
I tried to add the lines
qCWarning(KWIN_FB) << "Alpha Length: " << m_alpha.length;
qCWarning(KWIN_FB) << "Alpha Offset: " << m_alpha.offset;
qCWarning(KWIN_FB) << "Red Length: "   << m_red.length;
qCWarning(KWIN_FB) << "Red Offset: "   << m_red.offset;
qCWarning(KWIN_FB) << "Green Length: " << m_green.length;
qCWarning(KWIN_FB) << "Green Offset: " << m_green.offset;
qCWarning(KWIN_FB) << "Blue Length: "  << m_blue.length;
qCWarning(KWIN_FB) << "Blue Offset: "  << m_blue.offset;
in FramebufferBackend::queryScreenInfo()

to see if a difference there could be the cause of the late:
   QPainter::begin Paint device returned engine == 0, type 3
which occurs sometime after Xwayland starts, which that line does not appear on
my physical box when using the framebuffer at least. (if that even is related
to the issue)

and they all seem to be correct for what FramebufferBackend::imageFormat()
tries to match for in QEMU...
Alpha Length:0
Alpha Offset:0
Red Length: 8
Red Offset: 16
Green Length: 8
Green Offset: 8
Blue Length: 8
Blue Offset :0

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

[plasmashell] [Bug 356226] New: Regression - External monitor settings not remembered

[via KDE Bugzilla]

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

Bug ID: 356226
   Summary: Regression - External monitor settings not remembered
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: mlud...@logix.net.nz
CC: plasma-b...@kde.org

I work with a few external monitors - the one at home is 90° pivoted, one at
work is not, projector is meant to be a mirror of my desktop, etc. In KDE4
these different configurations used to be remembered by KDE and the monitors
were properly configured as they should be upon plug in. I guess based on their
serial numbers or something like that. 

Plasma5 however doesn't seem to differentiate and always tries to apply the
previous setting. That's particularly annoying since one monitor is 90° pivoted
and after switching between them I have to open "Configure Desktop" -> "Display
and Monitor" and try to navigate the mouse on the pivoted screen through the
settings - quite a challenge.

This is a regression from KDE4 and one single thing that seriously makes me
think of going back to an older distro.

Reproducible: Always

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

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

[via KDE Bugzilla]

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

Bug ID: 356225
   Summary: Panel moves to wrong screen when external monitor is
connected
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mlud...@logix.net.nz
CC: bhus...@gmail.com, plasma-b...@kde.org

When I plug in external monitor the panel as well as all open windows from my
laptop's LVDS screen move to the new screen. While it's easy to pull back the
"normal" windows the problem is with the Panel - the only way I found so far to
move it back to the laptop screen is to switch to an empty desktop (or minimise
all windows) unplug the external monitor and plug it back again. Then the panel
moves back to the laptop. Sometimes it takes a couple of tries, sometimes the
display resolutions go all wrong and sometimes the panel disappears altogether.
It's very annoying.

Reproducible: Always

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

[Breeze] [Bug 356212] Breeze-dark icons theme missing inherited icons (#345957 is back)

[andreas_k via KDE Bugzilla]

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

andreas_k  changed:

   What|Removed |Added

 CC||andrea...@abwesend.de

--- Comment #9 from andreas_k  ---
but we work on this problem, so thanks for helping us to get better.

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

[Breeze] [Bug 355676] Many plasmoids missing icon in panel

[andreas_k via KDE Bugzilla]

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

andreas_k  changed:

   What|Removed |Added

 CC||andrea...@abwesend.de

--- Comment #4 from andreas_k  ---
thank you very much I'm not an coding expert and forget to add the new folder
to the cmake file. thanks for your replay. the change was added to master.

https://quickgit.kde.org/?p=breeze-icons.git=commit=5b3a64f22c5b5c2db569b04b5e6c7792b92dfbfe

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

[plasmashell] [Bug 356261] everything crashes on X session startup after Upgrading Fedora from 20 to 23

[via KDE Bugzilla]

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

kde@jks.tupari.net changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #12 from kde@jks.tupari.net ---
Attached stderr.  There wasn't anything in stdout except "GOT SIGHUP"

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

[plasmashell] [Bug 356261] everything crashes on X session startup after Upgrading Fedora from 20 to 23

[via KDE Bugzilla]

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

kde@jks.tupari.net changed:

   What|Removed |Added

  Attachment #95888|0   |1
is obsolete||

--- Comment #11 from kde@jks.tupari.net ---
Created attachment 95892
  --> https://bugs.kde.org/attachment.cgi?id=95892=edit
Stderr from startx

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

[systemsettings] [Bug 355152] reassigning kde menu to ctrl+esc does not work

[illumilore via KDE Bugzilla]

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

--- Comment #3 from illumilore  ---
"Did you try to change that KRunner global shortcut, so that it is free for
other purposes?"

No

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

[plasmashell] [Bug 356242] New: Aplication Launcher causes Plasma Shell to crash when searching or viewing history tab [QSQLiteDriver::QSQLiteDriver | QSQLiteDriverPlugin::create | QSqlDatabasePrivate

[PLX via KDE Bugzilla]

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

Bug ID: 356242
   Summary: Aplication Launcher causes Plasma Shell to crash when
searching or viewing history tab
[QSQLiteDriver::QSQLiteDriver |
QSQLiteDriverPlugin::create |
QSqlDatabasePrivate::init]
   Product: plasmashell
   Version: 5.4.95
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: k...@pmc.com.pt
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.95)

Qt Version: 5.5.1
Operating System: Linux 4.3.0-desktop-2.mga6 x86_64
Distribution: "Mageia 6"

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

Aplication Launcher causes Plasma Shell to crash when searching or viewing
history tab.

- Steps To reproduce:

1) Click on the Application Launcher icon in the panel.
2) Click on the "Histórico" tab (probably "History" or "Historic" tab in
english locale).

Or

1) Click on the Application Launcher icon in the panel.
2) Click on the search ("Escreva para pesquisar..." in pt-PT locale, probably
"Write to search..." or "Type to search" in english locale) and start typing
something.

That is it. The Plasma Shell will crash every time one the the above is done.

- Unusual behavior I noticed:

Plasma Shell crashes.

- System/Version information

$ uname -a
Linux marte 4.3.0-desktop-2.mga6 #1 SMP Sun Nov 29 13:27:42 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
$ cat /etc/os-release 
NAME="Mageia"
VERSION="6"
ID=mageia
VERSION_ID=6
ID_LIKE="mandriva fedora"
PRETTY_NAME="Mageia 6"
ANSI_COLOR="1;36"
HOME_URL="http://www.mageia.org/;
SUPPORT_URL="http://www.mageia.org/support/;
BUG_REPORT_URL="https://bugs.mageia.org/;
$ rpm -qa | grep -i -e 'sqlite\|kdelibs' | sort
kdelibs4-core-4.14.13-2.mga6
kdelibs4support-5.16.0-4.mga6
lib64kf5kdelibs4support5-5.16.0-4.mga6
lib64sqlite3_0-3.9.2-1.mga6
libsqlite3_0-3.9.2-1.mga6
qt4-database-plugin-sqlite-4.8.6-9.mga5
qtbase5-database-plugin-sqlite-5.4.0-7.mga5
sqlite3-tools-3.9.2-1.mga6

The crash can be reproduced every time.

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

Thread 17 (Thread 0x7fe6ad31e700 (LWP 3372)):
#0  0x7fe6c3161d4d in poll () at /lib64/libc.so.6
#1  0x7fe6c71d7ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fe6c71d9697 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fe6af84dcc9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fe6c384c01f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fe6c295e65d in start_thread () at /lib64/libpthread.so.0
#6  0x7fe6c316dbbd in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fe6a6635700 (LWP 3380)):
#0  0x7fe6c03cb3ea in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#1  0x7fe6c03cb50c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#2  0x7fe6c3a6f92b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#3  0x7fe6c3a1980a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#4  0x7fe6c38471bc in QThread::exec() () at /lib64/libQt5Core.so.5
#5  0x7fe6c60b3cd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#6  0x7fe6c384c01f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fe6c295e65d in start_thread () at /lib64/libpthread.so.0
#8  0x7fe6c316dbbd in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fe69ed10700 (LWP 3385)):
#0  0x7fe6c315d65d in read () at /lib64/libc.so.6
#1  0x7fe6c040d750 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7fe6c03caf34 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7fe6c03cb3a8 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7fe6c03cb50c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7fe6c3a6f92b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7fe6c3a1980a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7fe6c38471bc in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7fe6c60b3cd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#9  0x7fe6c384c01f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7fe6c295e65d in start_thread () at /lib64/libpthread.so.0
#11 0x7fe6c316dbbd in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fe69d4bc700 (LWP 3393)):
#0  0x7fe6c03caa46 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#1  0x7fe6c03cb333 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe6c03cb50c in 

[kwin] [Bug 355787] KDE5 (Plasma 5) returns black screen afeter xorg-server updated to 1.18

[SinClaus via KDE Bugzilla]

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

--- Comment #14 from SinClaus  ---
Pleas read by characters: Comp with KDE4, same Nvidia driver and new Xorg works
without problems.

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

[calligrawords] [Bug 353857] comments not visible when opening file

[via KDE Bugzilla]

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

--- Comment #31 from luo0...@students.nossalhs.vic.edu.au ---
(In reply to Camilla Boemann from comment #30)
> yes - both Calligra/2.9 and master branches have the fix
> 
> so if you check either of those branches out the fix will be there - Just
> note that building requires quite a number of dependencies to build and that
> master depends on qt5/kf5 now

Back to report!

The comment in the one comment file is now visible when opened in the Calligra
Words master build (Wow! Smooth scrolling!). However, attempting to open my
fanfiction (ODT version) resulted in it crashing, with a similar error as
before. This is probably just due to the exorbitant amount of comments in it.
Should I open another bug? I'll post the error underneath anyway, just in case.


Application: Calligra Words (calligrawords), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f322ad96840 (LWP 22431))]

Thread 2 (Thread 0x7f3212bd6700 (LWP 22432)):
#0  0x7f34f18d in poll () from /usr/lib/libc.so.6
#1  0x7f321b45bae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f321b45d757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f3213a88e89 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f3222e6496e in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f321f50c4a4 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f35813d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f322ad96840 (LWP 22431)):
[KCrash Handler]
#5  0x7f32236858ce in QTextLine::y() const () from /usr/lib/libQt5Gui.so.5
#6  0x7f322a1682f8 in KoTextDocumentLayout::positionAnchorTextRanges
(this=0x2be6a90, pos=17644, length=95, effectiveDocument=0x2cdc3a0) at
/home/chromace/kde/src/calligra/libs/textlayout/KoTextDocumentLayout.cpp:620
#7  0x7f322a13ea36 in KoTextLayoutArea::layoutBlock (this=0x34323e0,
cursor=0x1394830) at
/home/chromace/kde/src/calligra/libs/textlayout/KoTextLayoutArea.cpp:1261
#8  0x7f322a13b13b in KoTextLayoutArea::layout (this=0x34323e0,
cursor=0x1394830) at
/home/chromace/kde/src/calligra/libs/textlayout/KoTextLayoutArea.cpp:598
#9  0x7f322a1661c7 in KoTextLayoutRootArea::layoutRoot (this=0x34323e0,
cursor=0x1394830) at
/home/chromace/kde/src/calligra/libs/textlayout/KoTextLayoutRootArea.cpp:69
#10 0x7f322a169201 in KoTextDocumentLayout::doLayout (this=0x2be6a90) at
/home/chromace/kde/src/calligra/libs/textlayout/KoTextDocumentLayout.cpp:820
#11 0x7f322a168856 in KoTextDocumentLayout::layout (this=0x2be6a90) at
/home/chromace/kde/src/calligra/libs/textlayout/KoTextDocumentLayout.cpp:703
#12 0x7f322a1699d6 in KoTextDocumentLayout::executeScheduledLayout
(this=0x2be6a90) at
/home/chromace/kde/src/calligra/libs/textlayout/KoTextDocumentLayout.cpp:911
#13 0x7f322a18dd7a in KoTextDocumentLayout::qt_static_metacall
(_o=0x2be6a90, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x1452300) at
/home/chromace/kde/build/calligra/libs/textlayout/moc_KoTextDocumentLayout.cpp:109
#14 0x7f3223074ff1 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#15 0x7f3223ffc01c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#16 0x7f32240014f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#17 0x7f322a78f78f in KoApplication::notify (this=0x7fff7beb7f70,
receiver=0x2be6a90, event=0x2a83ab0) at
/home/chromace/kde/src/calligra/libs/main/KoApplication.cpp:626
#18 0x7f32230459ab in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#19 0x7f3223047da6 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#20 0x7f322309bf43 in ?? () from /usr/lib/libQt5Core.so.5
#21 0x7f321d79bdc7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#22 0x7f321d79c020 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x7f321d79c0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#24 0x7f322309c34f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#25 0x7f32283331f8 in KoProgressUpdater::update (this=0x1432ff0) at
/home/chromace/kde/src/calligra/libs/widgetutils/KoProgressUpdater.cpp:166
#26 0x7f322833e25a in KoProgressUpdater::qt_static_metacall (_o=0x1432ff0,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff7beb6060) at
/home/chromace/kde/build/calligra/libs/widgetutils/moc_KoProgressUpdater.cpp:72
#27 0x7f322307412a in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#28 0x7f322833e911 in KoUpdaterPrivate::sigUpdated (this=0x280ed10) at
/home/chromace/kde/build/calligra/libs/widgetutils/moc_KoUpdaterPrivate_p.cpp:152
#29 0x7f32283367af in KoUpdaterPrivate::setProgress (this=0x280ed10,
percent=100) at
/home/chromace/kde/src/calligra/libs/widgetutils/KoUpdaterPrivate_p.cpp:45
#30 0x7f322833e733 in 

[telepathy] [Bug 356243] New: Cannot login to Google account and account settings are not remembered

[george via KDE Bugzilla]

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

Bug ID: 356243
   Summary: Cannot login to Google account and account settings
are not remembered
   Product: telepathy
   Version: 0.9.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: auth-handler
  Assignee: kde-telepathy-b...@kde.org
  Reporter: stu...@anchev.net

Not sure how to check version as this is not working but the system is openSUSE
Leap 42.1 with Plasma 5.4.3

Also /usr/share/doc/packages/telepathy-gabble/ChangeLog shows:

commit f10f557fd67ec11738670828a553496960c0d411
Author: Guillaume Desmottes 
Date:   2014-05-07 16:33:17 +0200

0.18.2

The package version in YaST is 0.9.0-2.2

Reproducible: Always

Steps to Reproduce:
1. Open System Settings > Online Accounts
2. Add new Jabber account with credentials the Gmail account and password
3. Click Advanced and enter:

Server address: talk.google.com
Sever port: 5223

Require encrypted connection - checked (but even without checked still can't
connect)

4. Click OK and try to connect
5. After a while the login prompt dialog appears and asks again for password.
Give it the password.


Actual Results:  
It can never connect/authorize. Please see the journal log for details.

Additionally when going to System Settings > Online Accounts > this same
account > Configure - the login credentials are not remembered as well as
server settings.

Expected Results:  
Successful connection and remembering of login credentials.

journalctl -f shows:

Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: New
job started. 1 jobs currently running
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  7
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  794
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unknown signature value:  795
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: No
other jobs at the moment. Starting timer.
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Job
finished. 0 jobs currently running
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: New
job started. 1 jobs currently running
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: 0
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
("X-OAUTH2", "X-GOOGLE-TOKEN", "PLAIN", "X-TELEPATHY-PASSWORD")
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Starting X-OAuth2 auth
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Status Not started
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
(process:4639): accounts-glib-CRITICAL **: ag_manager_load_account: assertion
'account_id != 0' failed
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
(process:4639): GLib-CRITICAL **: g_error_free: assertion 'error != NULL'
failed
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unable to find account for id 0
Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Retrying in 2s
Dec 03 14:26:48 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
(process:4639): accounts-glib-CRITICAL **: ag_manager_load_account: assertion
'account_id != 0' failed
Dec 03 14:26:48 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
(process:4639): GLib-CRITICAL **: g_error_free: assertion 'error != NULL'
failed
Dec 03 14:26:48 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Unable to find account for id 0
Dec 03 14:26:48 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
Retrying in 2s
Dec 03 14:26:50 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]:
(process:4639): accounts-glib-CRITICAL **: ag_manager_load_account: assertion
'account_id != 0' failed
Dec 03 14:26:50 i7 

[clazy] [Bug 356240] New: lambda args by ref

[via KDE Bugzilla]

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

Bug ID: 356240
   Summary: lambda args by ref
   Product: clazy
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: eric.lemaniss...@gmail.com
CC: smart...@kde.org

A new check could be added to check arguments passing to lambda, the same way
it is already done for functions when using -Wclazy-function-args-by-ref

Reproducible: Always

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

[systemsettings] [Bug 356237] New: Unable to change icon associated with mimetype if ~/.local/share/mime/packages does not already exist.

[Paul via KDE Bugzilla]

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

Bug ID: 356237
   Summary: Unable to change icon associated with mimetype if
~/.local/share/mime/packages does not already exist.
   Product: systemsettings
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_filetypes
  Assignee: fa...@kde.org
  Reporter: pip@gmx.com

openSUSE Tumbleweed (20151128) / KDE Frameworks 5.16.0 / System Settings 5.4.3

Attempting to change the icon associated with a mimetype (System Settings ->
Applications -> File Associations) fails to work if the subdirectory
"~/.local/share/mime/packages" does not already exist.

Within system settings it gives the appearance of having worked, however having
closed System Settings the icon is unchanged when viewing a directory listing
using Dolphin, and if one again uses System Settings it shows the original
icon.

This section of ".xsession-errors-:0" gave the clue...

m_userSpecifiedIcon has changed. Now set to "text-rdf+xml"
Entry  "application/rdf+xml"  is dirty. Saving.
m_userSpecifiedIcon has changed. Now set to "text-rdf+xml"
writing "/home/paul/.local/share/mime/packages/application-rdf+xml.xml"
Couldn't open "/home/paul/.local/share/mime/packages/application-rdf+xml.xml"
for writing
"application/rdf+xml" hasDefinitionFile: false

Specifically, the "Couldn't open..." - The subdirectory didn't exist.

Having manually created ~/.local/share/mime/packages changing the icon worked
correctly.

I have 3 users on that particular machine, none of whom had a
"~/.local/share/mime/*" subdirectory.

Interestingly, System Settings was able to create an additional subdirectory,
"~/.local/share/mime/application".

I tried again with one of the other users, initally just creating
"~/.local/share/mime" - which failed, it had to be
"~/.local/share/mime/packages".

So it seems that System Settings expects that subdirectory to "just be there",
and does not create it if missing.


Reproducible: Always

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

[Skanlite] [Bug 356124] Problem when start Skanlite and take a photo

[David via KDE Bugzilla]

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

--- Comment #12 from David  ---
Hi Kare Sars,
This afternoon I will try your solution (thanks very much!).

This morning I tried Kubuntu 14.04.03 from LiveCD (no installation).
In that release of Kubuntu, you can find only Skanlite. 
I tried Skanlite to take a photo and the result was excellent! No
red/blue/orange pixels of image.

After I installed digiKam: in the KDE-menù->Graphics you can find Skanlite and
AcquireImages (in Italian: "Acquisizioni di immagini").
So I tried to take a photo with Skanlite and the result was incorrect (the same
problem I wrote at the beginning of this discussion).
Then I tried to take a photo with AcquireImages and the result was great (like
Skanlite without digiKam).

Maybe it is a conflict between Skanlite and digiKam+AcquireImages.
Is it possible?

(Excuse me for my low-level English!)

Thanks for your help! Have a great day! :)

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

[kdenlive] [Bug 356209] Copying Effects messes up parameters (Fade from black + Fade in)

[via KDE Bugzilla]

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

qubo...@gmail.com changed:

   What|Removed |Added

Summary|Copying Effects messes up   |Copying Effects messes up
   |parameters (Fade|parameters (Fade from black
   ||+ Fade in)

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

[kstart] [Bug 277775] KDE Autostart / kstart starts 2 apps in wrong desktop (mixed up)

[via KDE Bugzilla]

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

dd...@samba.org changed:

   What|Removed |Added

 CC||dd...@samba.org

--- Comment #2 from dd...@samba.org ---
I see the same issue with using autostart with KDE Plasma 5.4.3 (openSUSE Leap
42.1).
"kstart --desktop X" is ineffective - all autostart programs start on desktop 1

This bug has also been discussed in the forums:
https://forum.kde.org/viewtopic.php?f=66=101023

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

[kontact] [Bug 356271] New: Kontact closes when I click on New Message

[clivejo via KDE Bugzilla]

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

Bug ID: 356271
   Summary: Kontact closes when I click on New Message
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: cliv...@aol.com

Every-time I click on New Message, Kontact closes.  However, the system doesn't
seem to recognise it as a crash.  To send a new message, I have to reply to an
old message and change all the fields.  

My system is Kubuntu 16.04 (Xenial) running Kontact 5.0.2 (I cant find this
version in the Scroll box above).  Please advice how to get a proper bug
report.

Reproducible: Always

Steps to Reproduce:
1. Open Kontact
2. Click on the "New Message" button

Actual Results:  
Kontact terminates

Expected Results:  
Display a window were I can write a new email message

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

[kdenlive] [Bug 356100] Image Sequence is default Render profile

[via KDE Bugzilla]

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

qubo...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from qubo...@gmail.com ---
Persists (re-introduced?) in v15.11.80-53-g0918054

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

[kdeplasma-addons] [Bug 356269] New: Can't directly type Chinese.

[via KDE Bugzilla]

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

Bug ID: 356269
   Summary: Can't directly type Chinese.
   Product: kdeplasma-addons
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Dashboard
  Assignee: h...@kde.org
  Reporter: laichiah...@outlook.com
CC: plasma-b...@kde.org

I can't directly type Chinese to search applications

Reproducible: Always

Steps to Reproduce:
1.open the dashboard
2.try to type Chinese
3.it is English

Actual Results:  
I have to type 1 letter and switch the input method, and I have to do it every
time.

Expected Results:  
I can directly type Chinese in the Dashboard.

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

[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys

[Leon via KDE Bugzilla]

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

--- Comment #18 from Leon  ---
Hi Leslie,
thanks for the link. I have found FolderView.qml (on my system it was here:
/usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/) and added
the else if clause.

But the file foldermodel.h does not seem to be on my system. 
Without those changes STRG+X and STRG+C do not work.
What should I do now?

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

[systemsettings] [Bug 356281] New: Once a different scheme is selected via "Window Decorations" and hit OK, if you try to get back to the same "Window Decorations" subsection of "Application Style", t

[smihaila via KDE Bugzilla]

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

Bug ID: 356281
   Summary: Once a different scheme is selected via "Window
Decorations" and hit OK, if you try to get back to the
same "Window Decorations" subsection of "Application
Style", the "System Settings" config app will crash,
all the time
   Product: systemsettings
   Version: 5.4.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: kcm_style
  Assignee: tibi...@kde.org
  Reporter: smiha...@gmail.com

1. Open System Settings.
2. Go to "Application Style".
3. Select "Window Decorations".
4. Download additional scheme/theme, such as Oxygen KDE4.2.2 or Oxygen DLS
(can't recall exact name because I can't go there anymore without crash)
5. Select the newly installed scheme. Hit ok.
6. Get back to "System Settings" main window.
7. Try to get back to "Window Decorations." The "System Settings" app will
crash.

This has happened due to selecting a mix of settings, or clicking the "fine
tune" tab of "Window Decorations" but not actually changing anything. Can't
recall 100% how I got into this state.

The bottom line is that now I can no longer invoke the "Window Decorations".

Reproducible: Always

Steps to Reproduce:
See "Details" section of this bug report.

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

[krunner] [Bug 355232] Krunner crash at each login, after upgrade to Kubuntu 15.10

[Florian via KDE Bugzilla]

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

Florian  changed:

   What|Removed |Added

 CC||floesc...@gmx.net

--- Comment #1 from Florian  ---
Created attachment 95880
  --> https://bugs.kde.org/attachment.cgi?id=95880=edit
krunner crash report

+1

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

[krita] [Bug 356247] New: [Feature Request Krita Animation] There is no simple way to import image sequences.

[Dimi via KDE Bugzilla]

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

Bug ID: 356247
   Summary: [Feature Request Krita Animation] There is no simple
way to import image sequences.
   Product: krita
   Version: 2.9.9
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: dimim...@gmail.com

Importing image sequences as an animated layer should be a no brainer. To fully
use Krita as an animation tool it should be possible to import videos or image
sequences.
It's critical for most animation works to be able to import line tests or video
references, whether it's for animating, doing clean up or painting frames.
Right now rotoscoping, a pretty standard and basic animation technique, is
impossible to do in Krita.

Importing footage is an essential option of any animation software

Reproducible: Always

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

[kate] [Bug 356246] Kate spins endlessly doing getcwd()

[via KDE Bugzilla]

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

--- Comment #3 from jm.ouwerk...@gmail.com ---
As you can see it appears that each call to i18n () is repeated a number of
times. Playing a bit further it seems this factor is exactly 4 on my machine,
which coincidentally is exactly the number of CPU cores/threads:

 continue
Continuing.

Breakpoint 2, __getcwd (buf=buf@entry=0x7fffb0c0 "yE|",
size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47
47  in ../sysdeps/unix/sysv/linux/getcwd.c
(gdb) bt
#0  __getcwd (buf=buf@entry=0x7fffb0c0 "yE|", size=size@entry=4098) at
../sysdeps/unix/sysv/linux/getcwd.c:47
#1  0x71f711d7 in __dcigettext (domainname=0x7c3f58 "kate",
msgid1=0x7c3078 "(c) 2000-2015 The Kate Authors", msgid2=0x0, plural=0, n=0,
category=5) at dcigettext.c:640
#2  0x756f87f7 in KCatalog::translate (this=0x7d0200, msgid=...) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/kcatalog.cpp:192
#3  0x756e75ed in KLocalizedStringPrivate::translateRaw (domain=...,
languages=..., msgctxt=..., msgid=..., msgid_plural=..., n=0, language=...,
msgstr=...) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:434
#4  0x756e7c65 in KLocalizedStringPrivate::toString (this=0x7beb30,
domain=..., languages=..., format=Kuit::UndefinedFormat, isArgument=false) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:507
#5  0x756e771f in KLocalizedString::toString (this=0x7fffc7e0) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:447
#6  0x0048447b in i18n(char const*) ()
#7  0x0047ed60 in main ()
(gdb) continue
Continuing.

Breakpoint 2, __getcwd (buf=buf@entry=0x7fffb0c0
"/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at
../sysdeps/unix/sysv/linux/getcwd.c:47
47  in ../sysdeps/unix/sysv/linux/getcwd.c
(gdb) bt
#0  __getcwd (buf=buf@entry=0x7fffb0c0
"/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at
../sysdeps/unix/sysv/linux/getcwd.c:47
#1  0x71f711d7 in __dcigettext (domainname=0x7c3f58 "kate",
msgid1=0x7c3078 "(c) 2000-2015 The Kate Authors", msgid2=0x0, plural=0, n=0,
category=5) at dcigettext.c:640
#2  0x756f87f7 in KCatalog::translate (this=0x7bd260, msgid=...) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/kcatalog.cpp:192
#3  0x756e75ed in KLocalizedStringPrivate::translateRaw (domain=...,
languages=..., msgctxt=..., msgid=..., msgid_plural=..., n=0, language=...,
msgstr=...) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:434
#4  0x756e7c65 in KLocalizedStringPrivate::toString (this=0x7beb30,
domain=..., languages=..., format=Kuit::UndefinedFormat, isArgument=false) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:507
#5  0x756e771f in KLocalizedString::toString (this=0x7fffc7e0) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:447
#6  0x0048447b in i18n(char const*) ()
#7  0x0047ed60 in main ()
(gdb) continue
Continuing.

Breakpoint 2, __getcwd (buf=buf@entry=0x7fffb0c0
"/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at
../sysdeps/unix/sysv/linux/getcwd.c:47
47  in ../sysdeps/unix/sysv/linux/getcwd.c
(gdb) bt
#0  __getcwd (buf=buf@entry=0x7fffb0c0
"/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at
../sysdeps/unix/sysv/linux/getcwd.c:47
#1  0x71f711d7 in __dcigettext (domainname=0x7c3f58 "kate",
msgid1=0x7c3078 "(c) 2000-2015 The Kate Authors", msgid2=0x0, plural=0, n=0,
category=5) at dcigettext.c:640
#2  0x756f87f7 in KCatalog::translate (this=0x7d0200, msgid=...) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/kcatalog.cpp:192
#3  0x756e75ed in KLocalizedStringPrivate::translateRaw (domain=...,
languages=..., msgctxt=..., msgid=..., msgid_plural=..., n=0, language=...,
msgstr=...) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:434
#4  0x756e7c65 in KLocalizedStringPrivate::toString (this=0x7beb30,
domain=..., languages=..., format=Kuit::UndefinedFormat, isArgument=false) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:507
#5  0x756e771f in KLocalizedString::toString (this=0x7fffc7e0) at
/home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:447
#6  0x0048447b in i18n(char const*) ()
#7  0x0047ed60 in main ()
(gdb) continue
Continuing.

Breakpoint 2, __getcwd (buf=buf@entry=0x7fffb0c0
"/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at
../sysdeps/unix/sysv/linux/getcwd.c:47
47  in ../sysdeps/unix/sysv/linux/getcwd.c
(gdb) bt
#0  __getcwd (buf=buf@entry=0x7fffb0c0
"/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at
../sysdeps/unix/sysv/linux/getcwd.c:47
#1  0x71f711d7 in __dcigettext 

[krita] [Bug 356056] Krita Animation Beta - Ctrl+drag to Copy Single Animation Frame Not Working

[Dimi via KDE Bugzilla]

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

Dimi  changed:

   What|Removed |Added

 CC||dimim...@gmail.com

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

[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[via KDE Bugzilla]

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

--- Comment #13 from bluescreen_aven...@verizon.net ---
How should I go about testing that? I have realized that there are some issues
with the way libvirt is passing CPU features, but It seems that kwin is working
under the Wayland backend under Weston on QEMU...   
...It's usually breaking some things with LLVM, causing apps to crash, so it
could be unrelated...  
So how's a good way for me to test why (or if) memory mapping for the qimage
would be failing under just QEMU, only when using the framebuffer backend

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

[ark] [Bug 355284] password protected zipx wont extract with correct password

[zezadas via KDE Bugzilla]

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

--- Comment #5 from zezadas  ---
okular as a bug too, when asking for password.
puting the correct password, okular cant decrypt the file.

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

[krita] [Bug 356251] New: [Krita animation beta] Merging layers (merge undo as well) with animation does not work

[Bhupen via KDE Bugzilla]

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

Bug ID: 356251
   Summary: [Krita animation beta] Merging layers (merge undo as
well) with animation does not work
   Product: krita
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: bhupen.a...@gmail.com

Merging layers with animation does not work.
All the keys from all layers are lost.
Undo operation does not restore the keys as well.

Reproducible: Always

Steps to Reproduce:
a1. Create 2 layers with 2 diff. animation sequences/keys.
a2. Merge the 2 layers.

b3. Undo the merge operation.

Actual Results:  
a. All keys from both layers are lost.
b. Undo does not restore all keys from both layers.

Expected Results:  
a. Resulting animation and keys should be merged
b. Layers should be separated and original keys restored.

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

[krita] [Bug 356245] New: [Krita Animation Beta] Animation playback behaves differently when moving the brush tool on the canvas.

[Dimi via KDE Bugzilla]

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

Bug ID: 356245
   Summary: [Krita Animation Beta] Animation playback behaves
differently when moving the brush tool on the canvas.
   Product: krita
   Version: 2.9.9
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: dimim...@gmail.com

When play-backing the animation it rarely plays at full speed without
stuttering. Moving or wiggling the brush tool on the canvas helps considerably.
Krita should be able to playback without slow downs.

Reproducible: Always

Steps to Reproduce:
1.Play animation
2.Move quickly the brush tool on the screen


Actual Results:  
Playback gets to full speed or close to full speed.

Expected Results:  
It shouldn't matter what the mouse is doing. Krita should always playback the
animation smoothly.

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

[kdenlive] [Bug 356187] icons missing in 15.11.80

[farid via KDE Bugzilla]

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

--- Comment #3 from farid  ---
just finished compiling and nothing changed.

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

[telepathy] [Bug 354949] Can't connect to gtalk account (Authentication failed: invalid-authzid)

[Georgy via KDE Bugzilla]

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

--- Comment #24 from Georgy  ---
(In reply to Martin Klapetek from comment #22)
> Georgy - yes, this patch is spot on. Good work! Do you have commit access?
> Otherwise I'll push it for you (I just need your full name for the commit,
> you can send that in private).

Hi Martin, i don't have commit access yet, my full name is Georgy Kirichenko

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