date:20161209

[plasmashell] [Bug 367633] Plasmashell memory leak with PIM Events Plugin

2016-12-09 Thread dharman

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

--- Comment #6 from dharman  ---
(In reply to yves from comment #3)
> can confirm this bug with plasmashell 5.8.0.
> 
> It is always reproducible by simply activating the new PIM events plug-in
> via the Digital Clock Settings dialogue.

Exact the same for me... I'm using Owncloud calendars.

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

[plasmashell] [Bug 367633] Plasmashell memory leak with PIM Events Plugin

2016-12-09 Thread dharman

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

dharman  changed:

   What|Removed |Added

 CC||dhar...@10100.to

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

[plasmashell] [Bug 373489] runaway CPU (88%) and memory (30MB/s)

2016-12-09 Thread Jason

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

--- Comment #3 from Jason  ---
fresh start of plasmashell - 134MiB.  Not a crash, just a reference from normal
operation - started with kstart5 plasmashell and then I attached gdb
afterwards.  Notice less threads - absense of threaded-ml for instance.  And
that main landed in poll.

* 1Thread 0x7f7ab3af6900 (LWP 13389) "plasmashell" 0x7f7aad2b149d in
poll () from /lib64/libc.so.6
  2Thread 0x7f7aa05fe700 (LWP 13392) "QDBusConnection" 0x7f7aad2b149d
in poll () from /lib64/libc.so.6
  3Thread 0x7f7a9778c700 (LWP 13393) "QXcbEventReader" 0x7f7aad2b149d
in poll () from /lib64/libc.so.6
  4Thread 0x7f7a8700 (LWP 13394) "QQmlThread" 0x7f7aad2b149d in
poll () from /lib64/libc.so.6
  5Thread 0x7f7a8ebbe700 (LWP 13395) "QQmlThread" 0x7f7aad2b149d in
poll () from /lib64/libc.so.6
  6Thread 0x7f7a8cdee700 (LWP 13396) "plasmashell" 0x7f7aacabf0af in
pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
  7Thread 0x7f79f7732700 (LWP 13397) "QQuickPixmapRea" 0x7f7aad2b149d
in poll () from /lib64/libc.so.6
  8Thread 0x7f79f5e7c700 (LWP 13398) "QSGRenderThread" 0x7f7aacabf0af
in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
  9Thread 0x7f79edffe700 (LWP 13399) "QSGRenderThread" 0x7f7aacabf0af
in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
  10   Thread 0x7f79d513a700 (LWP 13400) "KCupsConnection" 0x7f7aad2b149d
in poll () from /lib64/libc.so.6
  11   Thread 0x7f79cf2d1700 (LWP 13406) "QSGRenderThread" 0x7f7aacabf0af
in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
  12   Thread 0x7f79ce171700 (LWP 13407) "QSGRenderThread" 0x7f7aacabf0af
in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
  13   Thread 0x7f79c7fff700 (LWP 13408) "QSGRenderThread" 0x7f7aacabf0af
in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0

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

[plasmashell] [Bug 373489] runaway CPU (88%) and memory (30MB/s)

2016-12-09 Thread Jason

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

--- Comment #2 from Jason  ---
compositor is disabled

The 2 instances it has crashed I mentioned is once on selecting one in a group
of konsole windows.  I'm unsure if the other instances (probably on the order
of 10 crashes to date) had other circumstances - wasn't paying attention or
forgot as time goes on.

The 2nd is when I selected 1 in a group of ROX-Filer windows.

I did not see the tooltip displayed in this latest case, with ROX-Filer.  I'm
not sure about prior cases.  Each time, nothing out of the ordinary was going
on - I was just trying to select another window from likely multitasking with
chrome.  That is no popup windows/dialogs/drag and drops were happening.

Memory normally starts up somewhere in 120-180MiB, a couple of hours ago, as
it's ran for a few days now, was at 300-400MiB.  It is presently 1.6GiB and
will grow fast after I unfreeze it. Bug has OOM'd me before if I don't kill it
or stop it in time.

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

2016-12-09 Thread Christoph Erhardt

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

Christoph Erhardt  changed:

   What|Removed |Added

 CC||k...@sicherha.de

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

[korgac] [Bug 369325] korgac used xdg autostart & session management to startup

2016-12-09 Thread Christoph Erhardt

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

Christoph Erhardt  changed:

   What|Removed |Added

 CC||k...@sicherha.de

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

[korgac] [Bug 370883] Crash on session restore

2016-12-09 Thread Christoph Erhardt

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

Christoph Erhardt  changed:

   What|Removed |Added

 CC||k...@sicherha.de

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

[plasmashell] [Bug 373489] runaway CPU (88%) and memory (30MB/s)

2016-12-09 Thread Jason

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

--- Comment #1 from Jason  ---
Created attachment 102712
  --> https://bugs.kde.org/attachment.cgi?id=102712=edit
btfull

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

[plasmashell] [Bug 373489] New: runaway CPU (88%) and memory (30MB/s)

2016-12-09 Thread Jason

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

Bug ID: 373489
   Summary: runaway CPU (88%) and memory (30MB/s)
   Product: plasmashell
   Version: 5.8.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: nev...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Kde is fine, the bug is relatively rare and I do not have a definitive way to
reproduce.

It seems, on a coincidence of 2 times that I can attest (others being
forgotten) that clicking on a grouped sest of windows in the task manager can
lead to a runaway plasmashell main thread (other slave threads to not run
away).

I have a core dump and I have several backtraces.  Sometimes I catch a dbus
request being made as evidenced by a dbus connection thread, but I generally
just catch main in:

#0  0x7fd404d892b5 in QV4::PersistentValueStorage::allocate() () at
/usr/lib64/libQt5Qml.so.5
#1  0x7fd404d898f2 in QV4::PersistentValue::set(QV4::ExecutionEngine*,
QV4::Value const&) ()
at /usr/lib64/libQt5Qml.so.5
#2  0x7fd404e0027a in
QV4::QObjectWrapper::method_connect(QV4::CallContext*) () at
/usr/lib64/libQt5Qml.so.5
#3  0x7fd404dae32b in QV4::BuiltinFunction::call(QV4::Managed const*,
QV4::CallData*) () at /usr/lib64/libQt5Qml.so.5
#4  0x7fd404e1baeb in QV4::Runtime::callProperty(QV4::ExecutionEngine*,
int, QV4::CallData*) ()
at /usr/lib64/libQt5Qml.so.5


Sometimes I catch main in a QML garbage collection.  All other threads are
waiting on the poll sys call and not using CPU.

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

[valgrind] [Bug 373488] New: Support for fanotify API on ARM64 architecture

2016-12-09 Thread Heinrich Schuchardt

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

Bug ID: 373488
   Summary: Support for fanotify API on ARM64 architecture
   Product: valgrind
   Version: 3.13 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: xypron.g...@gmx.de
  Target Milestone: ---

Created attachment 102711
  --> https://bugs.kde.org/attachment.cgi?id=102711=edit
[PATCH 1/1] Support for fanotify API on ARM64 architecture

The appended patch enables the fanotify_init and fanotify_mark system
calls for the arm64 architecture.

It is a follow up to bug report 320895.
https://bugs.kde.org/show_bug.cgi?id=320895

Reproducible: Always

Steps to Reproduce:
1. write a simple application which calls fanotify_init()
2. run it in valgrind

Actual Results:  
An error "system call unimplemented" occurs.

Expected Results:  
Fanotify_init and fanotify_mark should be supported.

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

[valgrind] [Bug 373488] Support for fanotify API on ARM64 architecture

2016-12-09 Thread Heinrich Schuchardt

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

Heinrich Schuchardt  changed:

   What|Removed |Added

 CC||xypron.g...@gmx.de

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

[i18n] [Bug 373487] New: buttons in dialog boxes are not translated

2016-12-09 Thread bugzilla_noreply

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

Bug ID: 373487
   Summary: buttons in dialog boxes are not translated
   Product: i18n
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: fr
  Assignee: kde-francoph...@kde.org
  Reporter: grouchomarx...@gmail.com
CC: an...@kde.org
  Target Milestone: ---

How to reproduce :
- open any qt5 app (dolphin, konsole, system settings, ...)
- go into the app settings or open a dialog box

Expected results :
- everything is translated

Actual results :
- buttons such as "cancel", "apply", "yes", "no", "discard", ... are in english

System : Kubuntu 16.10 and KDE Neon 5.8
all the french packages are installed

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

[okular] [Bug 373486] okular crashes every time gnome desktop switches between multiple screens

2016-12-09 Thread Naitree Zhu

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

--- Comment #1 from Naitree Zhu  ---
Also, besides crashing on switching between monitors, okular crashed on laptop
wakeup when external monitor was connected.

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

[okular] [Bug 373486] New: okular crashes every time gnome desktop switches between multiple screens

2016-12-09 Thread Naitree Zhu

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

Bug ID: 373486
   Summary: okular crashes every time gnome desktop switches
between multiple screens
   Product: okular
   Version: 0.26.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: naitr...@gmail.com
  Target Milestone: ---

Application: okular (0.26.1)
KDE Platform Version: 4.14.25
Qt Version: 4.8.7
Operating System: Linux 4.8.11-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:
I was reading pdf on an external monitor with laptop lid closed. Then I
switched on laptop lid, and gnome desktop flashed one time to load screen on
laptop internal screen. After that, okular crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9b35633300 (LWP 14869))]

Thread 3 (Thread 0x7f9b0df06700 (LWP 14994)):
#0  0x7f9b3240f63d in read () at /lib64/libpthread.so.0
#1  0x7f9b2e0a9450 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f9b2e064c60 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f9b2e0650f4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f9b2e06526c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f9b327e547e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#6  0x7f9b327b37bf in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#7  0x7f9b327b3b25 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#8  0x7f9b326a2af9 in QThread::exec() () at /lib64/libQtCore.so.4
#9  0x7f9b32793613 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#10 0x7f9b326a53ca in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#11 0x7f9b324066ca in start_thread () at /lib64/libpthread.so.0
#12 0x7f9b31613f6f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f9afeb64700 (LWP 14889)):
#0  0x7f9b3160800d in poll () at /lib64/libc.so.6
#1  0x7f9b2e065156 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9b2e06526c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9b327e547e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7f9b327b37bf in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7f9b327b3b25 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f9b326a2af9 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7f9b32793613 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#8  0x7f9b326a53ca in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#9  0x7f9b324066ca in start_thread () at /lib64/libpthread.so.0
#10 0x7f9b31613f6f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f9b35633300 (LWP 14869)):
[KCrash Handler]
#6  0x7f9b0e26fb8e in XRandROutput::update(XRandROutput::PrimaryChange) ()
at /usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#7  0x7f9b0e25efe6 in XRandR::updateCrtc(unsigned long) () at
/usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#8  0x7f9b327c9090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#9  0x7f9b0e260c54 in XRandRX11Helper::x11Event(_XEvent*) () at
/usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#10 0x7f9b3420202f in KSystemEventFilterPrivate::filterEvent(void*) () at
/lib64/libkdeui.so.5
#11 0x7f9b327a705e in QAbstractEventDispatcher::filterEvent(void*) () at
/lib64/libQtCore.so.4
#12 0x7f9b332aa3f3 in x11EventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQtGui.so.4
#13 0x7f9b2e064e42 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#14 0x7f9b2e0651c0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#15 0x7f9b2e06526c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#16 0x7f9b327e545e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#17 0x7f9b332aa5a6 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#18 0x7f9b327b37bf in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#19 0x7f9b327b3b25 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#20 0x7f9b327b9779 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#21 0x561b32e8ad83 in main ()

Reported using DrKonqi

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

2016-12-09 Thread Kim

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

Kim  changed:

   What|Removed |Added

 CC||kmbr...@yahoo.com

--- Comment #38 from Kim  ---
Purchased a Ugee 19" art tablet. My daughter loves your program, and previously
used it successfully on her old Wacom, but it is connecting strokes together on
the Ugee. When lifting the pen, it ignores and connects to the next brush
stroke. Please advise. I've read that there are other people having this same
issue. Thank you, Kim

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

[kdenlive] [Bug 373433] Crash using motion freeze

2016-12-09 Thread farid

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

farid  changed:

   What|Removed |Added

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

--- Comment #1 from farid  ---
This is because you have movit (gpu processing) enabled. Note that this feature
is currently in beta and unstable. Try without it and also share your graphics
card...

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

[kwin] [Bug 373485] New: KWIN crash unexpectedly after reboot

2016-12-09 Thread bugzilla_noreply

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

Bug ID: 373485
   Summary: KWIN crash unexpectedly after reboot
   Product: kwin
   Version: 5.8.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: shamsuddeenket...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.12-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: system upgrade after the
upgrade perform system reboot.

- Unusual behavior I noticed:KWIN often freeze unexpectedly. sometimes after
system startup or during operations. it will freeze for hours before I'd to
manually shutdown the system.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f31031df940 (LWP 1915))]

Thread 5 (Thread 0x7f30c3790700 (LWP 2060)):
#0  0x7f30fbe7810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f30ff1a7834 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f30ff1a7879 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f30fbe72454 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3102b7539f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f30d37ff700 (LWP 1994)):
[KCrash Handler]
#6  0x7f3100182244 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f310011f706 in QLockFile::tryLock(int) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f3101f2c2c9 in  () at /usr/lib64/libKF5ConfigCore.so.5
#9  0x7f3101f160b0 in KConfig::sync() () at
/usr/lib64/libKF5ConfigCore.so.5
#10 0x7f30e26d4bf5 in  () at
/usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#11 0x7f310021b21e in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#12 0x7f3100227828 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#13 0x7f310021bd13 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#14 0x7f3100ee492c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#15 0x7f3100eec0e1 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#16 0x7f31001ef200 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#17 0x7f310024271e in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#18 0x7f3100240688 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#19 0x7f31001ed1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#20 0x7f310001b8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#21 0x7f3100020558 in  () at /usr/lib64/libQt5Core.so.5
#22 0x7f30fbe72454 in start_thread () at /lib64/libpthread.so.0
#23 0x7f3102b7539f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f30e0ec2700 (LWP 1990)):
#0  0x7ffc13265b12 in clock_gettime ()
#1  0x7f3102b82246 in clock_gettime () at /lib64/libc.so.6
#2  0x7f31000c56e1 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f3100241419 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f31002419c5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3100240704 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f31001ed1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f310001b8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f30fa9a3a75 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f3100020558 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f30fbe72454 in start_thread () at /lib64/libpthread.so.0
#11 0x7f3102b7539f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f30ebab0700 (LWP 1960)):
#0  0x7f3102b6c68d in poll () at /lib64/libc.so.6
#1  0x7f30f764d876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f30f764d98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f310024379b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f31001ed1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f310001b8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f30f9b7c3e5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f3100020558 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f30fbe72454 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3102b7539f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f31031df940 (LWP 1915)):
#0  0x7f30fbe7810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f310002140b

[kdenlive] [Bug 373474] git master - crashed while clicking on a position in Timeline. [backtrace log included]

2016-12-09 Thread farid

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

farid  changed:

   What|Removed |Added

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

--- Comment #1 from farid  ---
Please provide instructions on how to reproduce it.

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

[amarok] [Bug 119539] Request: Support for multiple genres / artists / composers / etc.

2016-12-09 Thread Myriam Schweingruber

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

--- Comment #60 from Myriam Schweingruber  ---
(In reply to Ralf Engels from comment #55)
> Started implementing. Might take a while to finish.
> Proposals for implementation see here:
> http://amarok.kde.org/wiki/Proposals/Support_for_multiple_tags

The wiki has moved to
https://community.kde.org/Amarok/Proposals/Support_for_multiple_tags

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

[i18n] [Bug 373484] New: typo in smb4k

2016-12-09 Thread bugzilla_noreply

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

Bug ID: 373484
   Summary: typo in smb4k
   Product: i18n
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: fr
  Assignee: kde-francoph...@kde.org
  Reporter: grouchomarx...@gmail.com
CC: an...@kde.org
  Target Milestone: ---

"Parcoure" is wrong. It should be "Parcourt".


i18n: ectx: label, entry (PeriodicScanning), group (Network)
#: smb4k.kcfg:145
msgid "Scan the network neighborhood periodically"
msgstr "Parcoure le voisinage de réseau périodiquement"

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

[krita] [Bug 373483] New: Instant Preview turned on but brushes still lag

2016-12-09 Thread Joseph Buehrer

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

Bug ID: 373483
   Summary: Instant Preview turned on but brushes still lag
   Product: krita
   Version: 3.0.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: joebueh...@buckeye-express.com
  Target Milestone: ---

I've found that sometimes when I open Krita, the brushes will still lag even if
Instant Preview in the brush settings is turned on. I've found the fix for this
is by toggling on and off the Temporarily Save Tweaks To Brush Presets option.

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

[umbrello] [Bug 373383] Not possible to add datatypes, interfaces and enums to a class or interface from tree view or class widgete

2016-12-09 Thread Ralf Habacker

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

Ralf Habacker  changed:

   What|Removed |Added

Summary|Not possible to add |Not possible to add
   |datatypes, interfaces and   |datatypes, interfaces and
   |enums to a class or |enums to a class or
   |interface from tree view|interface from tree view or
   ||class widgete

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

[umbrello] [Bug 373383] Not possible to add datatypes, interfaces and enums to a class or interface from tree view

2016-12-09 Thread Ralf Habacker

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

--- Comment #2 from Ralf Habacker  ---
Git commit 23e23aa41557cc8dc37347cc09b025d0aac3 by Ralf Habacker.
Committed on 09/12/2016 at 23:19.
Pushed by habacker into branch 'master'.

Add adding class, interface, datatype and enums from diagram class widget.

M  +13   -0umbrello/listpopupmenu.cpp
M  +21   -0umbrello/umlwidgets/classifierwidget.cpp

https://commits.kde.org/umbrello/23e23aa41557cc8dc37347cc09b025d0aac3

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

[umbrello] [Bug 373383] Not possible to add datatypes, interfaces and enums to a class or interface from tree view or class widgets

2016-12-09 Thread Ralf Habacker

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

Ralf Habacker  changed:

   What|Removed |Added

Summary|Not possible to add |Not possible to add
   |datatypes, interfaces and   |datatypes, interfaces and
   |enums to a class or |enums to a class or
   |interface from tree view or |interface from tree view or
   |class widgete   |class widgets

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

[plasmashell] [Bug 373482] New: Crash of plasma on dolphin attempting unsuccessful mount

2016-12-09 Thread lbickley

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

Bug ID: 373482
   Summary: Crash of plasma on dolphin attempting unsuccessful
mount
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lbick...@bickleywest.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

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

-- Information about the crash:
I had inserted a double layer DVD and Dolphin was attempting to mount it. The
mount failed as the DVD reader/writer does not support double layer (so I now
know). After the mount failure, Plasma crashed.

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

Thread 12 (Thread 0x7f5cfbffe700 (LWP 2010)):
#0  0x7f5ddd86003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5dde74e34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5de266b1cb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5de266b663 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5dde74d32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5ddd85c0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5dde05b02d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f5d0ceb2700 (LWP 2007)):
#0  0x7f5ddd86003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5dde74e34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5de266b1cb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5de266b663 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5dde74d32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5ddd85c0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5dde05b02d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f5d0f815700 (LWP 1989)):
#0  0x7f5ddd86003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5dde74e34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5de266b1cb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5de266b663 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5dde74d32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5ddd85c0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5dde05b02d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f5d14fc5700 (LWP 1984)):
#0  0x7f5dde052bfd in poll () at /lib64/libc.so.6
#1  0x7f5dda72fe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5dda72ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5dde97fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5dde926d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5dde74861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f5d16611cf7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7f5dde74d32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5ddd85c0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f5dde05b02d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f5d2af1c700 (LWP 1852)):
#0  0x7f5ddd86003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5dde74e34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5de266b1cb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5de266b663 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5dde74d32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5ddd85c0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5dde05b02d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f5d2b71d700 (LWP 1851)):
#0  0x7f5dda771d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f5dda72f759 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f5dda72fdcf in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f5dda72ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f5dde97fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f5dde926d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f5dde74861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f5de25f8282 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7f5dde74d32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f5ddd85c0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f5dde05b02d in clone () at /lib64/libc.so.6

Thread 6 (Thread

[krita] [Bug 373481] New: OCIO: all drop down menus reverting to the top item when movie krita to your second monitor

2016-12-09 Thread Jean-Francois Bouchard

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

Bug ID: 373481
   Summary: OCIO: all drop down menus reverting to the top item
when movie krita to your second monitor
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: jfbouch...@rodeofx.com
  Target Milestone: ---

Hi,

I encountered this issue while using krita w/ ocio implementation:
If I change the info in any of the OCIO drop down menus:
- input color space
- display device
- view
- look
- components

And then move the krita window from one of my monitors, to my secondary monitor
(per se), all the values of thoses drop down menus will revert to the first
item of the menu.

Thanks,
JF

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

[kdenlive] [Bug 373480] New: Speed effect cuts the clip

2016-12-09 Thread Mikhas'

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

Bug ID: 373480
   Summary: Speed effect cuts the clip
   Product: kdenlive
   Version: 16.08.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: mee...@gmail.com
  Target Milestone: ---

Steps to reproduce:
- open kdenlive
- add 2 clips
- add them to timeline one after one
- add 'Mute' effect to the second clip
- add 'Speed' effect to the same clip
- set Speed to 50%
- hold Shift, select all 2 clips and move them to right
- set cursor near the end of the second clip

Reuslt: black frame in preview
Expected result: frame of the second clip appeared in preview

Please see the video demonstration of the bug here:
https://youtu.be/TmeZxu52EJg

You can also save the project, then close and open it and see that the speed
effect disappeared. That's why there was no preview for the clip after its half
(speed 50%).

OS: Ubuntu MATE 16.04 64bit
DE: MATE 1.12.1
Locale: be_BY
Hardware: ASUS G550JK-CN287H, Intel videocard
Kdenlive version: 16.08.2
MLT version: 6.3.0+git201610101603~ubuntu16.04.1
Kdenlive package and its dependencies are from this repo:
https://launchpad.net/~kdenlive/+archive/ubuntu/kdenlive-stable
Kdenlive project settings: Full HD 1080, framerate 29.72

But this bug also exists in kdenlive 15.12.3 and mlt 6.0.0 (versions from
default Ubuntu 16.04 repos) and in kdenlive-devel installed from snap package.

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

[krita] [Bug 373191] Drawing has either "no pressure sensitivity+freezing brushes" or the brush is offset from the pen depending on the info in the "Choose Screen Resolution dialog" on multiscreen (ci

2016-12-09 Thread bugzilla_noreply

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

--- Comment #12 from kirtai2...@yahoo.com ---
Proposed addition to the FAQ entry "How to fix a tablet offset on multiple
screen setup on Windows"

If you have a Wacom tablet, an offset in the canvas can be caused by a faulty
Wacom preference file which is not removed or replaced by reinstalling the
drivers.

To fix it, use the "Wacom Tablet Preference File Utility" to clear all the
preferences. This should allow Krita to detect the correct settings
automatically.
(WARNING, this will reset your tablets configuration so you will need to
recalibrate/reconfigure it).

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

[krunner] [Bug 368372] krunner crashes launching first application after login

2016-12-09 Thread Ugo Paternostro

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

Ugo Paternostro  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|FIXED   |---
Version|5.7.3   |5.8.4

--- Comment #4 from Ugo Paternostro  ---
Hi Kai,

I'm sorry to bring bad news: I had once again the same crash, but running
krunner v5.8.4 from Fedora 25 RPMs.

Please find attached the report that drkonqi prepared for me. I didn't want to
open a new ticket, so I'm going to attach it as comment here. It is very
strange that drkonqi didn't suggest #368372 as a duplicate.

I'm going to edit ticket metadata to match new situation.

Please let me know if I can do something (install a debug/test version?)

Thank you

Application: krunner (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.11-300.fc25.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

See #368372, same situation except that now I have krunner 5.8.4 from Feroda 25
RPMs.

I just logged in and tried to start Thunderbird from krunner. It makes me type
the application name, searches it, finds it, then when I hit "Enter" it
crashes.

It (almost) always crashes the firs time I use it after login. I'm sorry, I
(almost) always use it to start Thunderbird as first application, so I cannot
say if the issue depends on the started application or not.

Restarting it from CLI (almost) always solves the problem: it crashed only once
when started from CLI, but I don't have the stack trace at hand at the moment.

May it be a timing issue? Login process still going on?

Let me know if I can help anyhow. TIA.

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

Thread 20 (Thread 0x7ff49cff9700 (LWP 2687)):
#0  0x7ff4ecd0f460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff4f0ef709a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7ff4c48ca880 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7ff4c48cea38 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7ff4c48c99fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7ff4c48cc8c9 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7ff4f0ef6a1a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7ff4ecd096ca in start_thread () at /lib64/libpthread.so.0
#8  0x7ff4f02e9f6f in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7ff49d7fa700 (LWP 2686)):
#0  0x7ff4f02f7ebc in __lll_lock_wait_private () at /lib64/libc.so.6
#1  0x7ff4f0268012 in malloc () at /lib64/libc.so.6
#2  0x7ff4f0ef7445 in QArrayData::allocate(unsigned long, unsigned long,
unsigned long, QFlags) () at
/lib64/libQt5Core.so.5
#3  0x7ff4f0ef8f00 in QByteArray::QByteArray(int, Qt::Initialization) () at
/lib64/libQt5Core.so.5
#4  0x7ff4f0f74de5 in QString::toLatin1_helper(QChar const*, int) () at
/lib64/libQt5Core.so.5
#5  0x7ff4f0f74e30 in QString::toLatin1_helper(QString const&) () at
/lib64/libQt5Core.so.5
#6  0x7ff4f1114ac8 in QMimeBinaryProvider::resolveAlias(QString const&) ()
at /lib64/libQt5Core.so.5
#7  0x7ff4f11058b1 in QMimeDatabasePrivate::mimeTypeForName(QString const&)
() at /lib64/libQt5Core.so.5
#8  0x7ff4f110597e in QMimeDatabase::mimeTypeForName(QString const&) const
() at /lib64/libQt5Core.so.5
#9  0x7ff4f2b43d80 in
KPluginInfo::KPluginInfo(QExplicitlySharedDataPointer) () at
/lib64/libKF5Service.so.5
#10 0x7ff4f3c0f54d in Plasma::PluginLoader::listAppletInfo(QString const&,
QString const&) () at /lib64/libKF5Plasma.so.5
#11 0x7ff4b66c1062 in WindowedWidgetsRunner::match(Plasma::RunnerContext&)
() at /usr/lib64/qt5/plugins/krunner_windowedwidgets.so
#12 0x7ff4c4aee6e8 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at
/lib64/libKF5Runner.so.5
#13 0x7ff4c48ce1b8 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () at /lib64/libKF5ThreadWeaver.so.5
#14 0x7ff4c48ccd00 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () at /lib64/libKF5ThreadWeaver.so.5
#15 0x7ff4c48cc810 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#16 0x7ff4f0ef6a1a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#17 0x7ff4ecd096ca in start_thread () at /lib64/libpthread.so.0
#18

[krita] [Bug 372439] Export to PDF in custom size, does not export to the desired size, unfortunately, but to default size (A4).

2016-12-09 Thread felipe . facundes

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

--- Comment #3 from felipe.facundes  ---
Yeah. That's basically what I meant.

The problem only happens when I export to custom size.

I noticed that Krita does not export in custom size, regardless of size.

Export properly, if it is preset.

So it's a Bug.

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

[digikam] [Bug 373479] Database on Server but Thumbnails local

2016-12-09 Thread bugzilla_noreply

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

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

   What|Removed |Added

Version|unspecified |5.3.0
 CC||caulier.gil...@gmail.com

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

[krita] [Bug 373191] Drawing has either "no pressure sensitivity+freezing brushes" or the brush is offset from the pen depending on the info in the "Choose Screen Resolution dialog" on multiscreen (ci

2016-12-09 Thread bugzilla_noreply

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

--- Comment #11 from kirtai2...@yahoo.com ---
OK, this turned out to be a case of rogue preference files that were not
removed by uninstalling the driver.

I had to use the "Wacom Tablet Preference File Utility" to purge all of the
preference files. After I did this, Krita's autodetection facility worked
perfectly. For the record, I used the wintab setting.

Apparently it's a known problem that also affects Paint Tool SAI.
Some more information in the second answer here 
https://www.systemax.jp/en/sai/faq_tablet.html

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

[KXStitch] [Bug 372987] Non-optimal precision for cloth counts in various dialogues

2016-12-09 Thread Steve Allewell

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

Steve Allewell  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1

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

[KXStitch] [Bug 372985] Display cloth count units in import dialogue

2016-12-09 Thread Steve Allewell

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

Steve Allewell  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

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

[KXStitch] [Bug 372984] Use locale units for cloth count by default

2016-12-09 Thread Steve Allewell

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

Steve Allewell  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

--- Comment #1 from Steve Allewell  ---
In the configuration dialogue for Pattern, 'Pattern Size' units are
Stitches|Inches|Centimeters and the 'Cloth Count' units are
Inches|Centimetres|Default, Default will be suffixed by (Inches) or
(Centimetres) depending on locale.

I will change the installed default to 'Default (Locale Setting)'

Do you think that if a user selects Inches or Centimetres in the 'Pattern
Size', the 'Cloth Count' should change to suit, or should it retain a mixed
measurement system?

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

[digikam] [Bug 373479] New: Database on Server but Thumbnails local

2016-12-09 Thread bugzilla_noreply

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

Bug ID: 373479
   Summary: Database on Server but Thumbnails local
   Product: digikam
   Version: unspecified
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Database-Multiusers
  Assignee: digikam-de...@kde.org
  Reporter: jakob.br...@posteo.de
  Target Milestone: ---

Hi,

I'm trying to set up digikam for a small work group.
The images are located on a common, mounted nas.
The problem is, I can't set up a database locally. Therefore I would like to
run the mysql-server on my hosted server and connect over the Internet. But
this solution is unacceptable slow. So I figured out, that the bottle leak is
probably loading the thumbnails. My question is, if there is a way to store the
thumbnails in a local sqllite database and just load the core-database over the
Internet.

Thanks,
Jakob

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

[dolphin] [Bug 373478] New: Dolphin does not run if launched via sudo

2016-12-09 Thread Buck Shockley

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

Bug ID: 373478
   Summary: Dolphin does not run if launched via sudo
   Product: dolphin
   Version: 16.08.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: darkwingbuc...@gmail.com
  Target Milestone: ---

Running the command 'sudo dolphin' in Konsole will print out the following:

[buck@archie ~]$ sudo dolphin
[sudo] password for buck: 
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
"Session bus not found\nTo circumvent this problem try the following command
(with Linux and bash)\nexport $(dbus-launch)"

This is 100% reproducible. Running printed command (export $(dbus-launch)) does
nothing. Opening with KDE su results in the same problem.

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

[okular] [Bug 372161] okular crash on startup

2016-12-09 Thread Lóránt Farkas

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

--- Comment #7 from Lóránt Farkas  ---
It cannot be nouveau specific as I use radeon driver.

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

[kdevplatform] [Bug 373475] crash when starting the patchreview plugin (NULL ptr dereference in Sublime::IdealController::raiseView)

2016-12-09 Thread RJVB

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

--- Comment #1 from RJVB  ---
Below is the backtrace from a related crash that occurred when I closed a patch
review.

This is another example of using Q_ASSERT where instead a simple check against
NULL can be used (calling qCritical() in release mode and qFatal() in debug
mode).


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

Thread 11 (Thread 0x7f52dd3bc700 (LWP 8578)):
#0  0x7f52fb011fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f52eb8b2b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f52eb8b464f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f52e0033f09 in QXcbEventReader::run (this=0x2129ea0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1331
#4  0x7f52fb6c0cf9 in QThreadPrivate::start (arg=0x2129ea0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qthread_unix.cpp:365
#5  0x7f52f4beb184 in start_thread (arg=0x7f52dd3bc700) at
pthread_create.c:312
#6  0x7f52fb01f37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 10 (Thread 0x7f52d7de4700 (LWP 8579)):
#0  0x7f52fb011fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f52f3d65fe4 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f52d0010870, timeout=-1, context=0x7f52d990) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:4028
#2  g_main_context_iterate (context=context@entry=0x7f52d990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3729
#3  0x7f52f3d660ec in g_main_context_iteration (context=0x7f52d990,
may_block=may_block@entry=1) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3795
#4  0x7f52fb8dcb0b in QEventDispatcherGlib::processEvents
(this=0x7f52d8c0, flags=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:419
#5  0x7f52fb8867aa in QEventLoop::exec (this=this@entry=0x7f52d7de3e20,
flags=..., flags@entry=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/kernel/qeventloop.cpp:206
#6  0x7f52fb6bbfdb in QThread::exec (this=this@entry=0x7f52fd704420
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qthread.cpp:500
#7  0x7f52fd493615 in QDBusConnectionManager::run (this=0x7f52fd704420
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/dbus/qdbusconnection.cpp:189
#8  0x7f52fb6c0cf9 in QThreadPrivate::start (arg=0x7f52fd704420 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qthread_unix.cpp:365
#9  0x7f52f4beb184 in start_thread (arg=0x7f52d7de4700) at
pthread_create.c:312
#10 0x7f52fb01f37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7f52caf47700 (LWP 8581)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f52fb6c1a36 in wait_relative (time=1000, this=0x2b2dc70) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:126
#2  wait (time=1000, this=0x2b2dc70) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:134
#3  QWaitCondition::wait (this=this@entry=0x2b26fc8,
mutex=mutex@entry=0x2b26fd0, time=time@entry=1000) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:208
#4  0x7f52f91443a8 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x2b26fb0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kdevplatform5/kf5-kdevplatform-devel/work/kf5-kdevplatform-5/language/duchain/duchain.cpp:282
#5  0x7f52fb6c0cf9 in QThreadPrivate::start

[kdeplasma-addons] [Bug 373410] Turn on "Offer shutdown options" doesn't re-enable Restart and Shutdown buttons in Dashboard.

2016-12-09 Thread bugzilla_noreply

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

--- Comment #2 from sun...@hotmail.ru ---
I see, never thought of that. Thanks.

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

[gwenview] [Bug 373477] New: Gwenview crashes with too many open files when tagging many photos

2016-12-09 Thread Andrew Findlay

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

Bug ID: 373477
   Summary: Gwenview crashes with too many open files when tagging
many photos
   Product: gwenview
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: andrew.find...@skills-1st.co.uk
CC: myr...@kde.org
  Target Milestone: ---

Application: gwenview (4.14.0 pre)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-48-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
I was rating photos in a folder with 598 files. I had tagged about 210 images
when the crash occurred.
Starting Gwenview again I noticed that every tag operation opens 4 Baloo files
again rather than re-using the open file descriptors.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efc88d03840 (LWP 21152))]

Thread 2 (Thread 0x7efc7088d700 (LWP 21153)):
#0  0x7ffc66d3abb6 in  ()
#1  0x in  ()

Thread 1 (Thread 0x7efc88d03840 (LWP 21152)):
[KCrash Handler]
#5  0x7efc7d5a40d8 in Xapian::Database::get_document(unsigned int) const ()
at /usr/lib64/libxapian.so.22
#6  0x7efc7d12f8a4 in Baloo::XapianDatabase::document(unsigned int) () at
/usr/lib64/libbalooxapian.so.4
#7  0x7efc836d92ed in Baloo::FileModifyJob::doStart() () at
/usr/lib64/libbaloofiles.so.4
#8  0x7efc87b2c59e in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#9  0x7efc8640c76c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#10 0x7efc86412cad in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#11 0x7efc87124e0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#12 0x7efc87b142ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#13 0x7efc87b1757d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#14 0x7efc87b418fe in  () at /usr/lib64/libQtCore.so.4
#15 0x7efc812d2a04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#16 0x7efc812d2c48 in  () at /usr/lib64/libglib-2.0.so.0
#17 0x7efc812d2cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#18 0x7efc87b410be in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#19 0x7efc864a9676 in  () at /usr/lib64/libQtGui.so.4
#20 0x7efc87b12e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#21 0x7efc87b13165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#22 0x7efc87b185b9 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#23 0x00429ded in  ()
#24 0x7efc856d5b05 in __libc_start_main () at /lib64/libc.so.6
#25 0x0042a092 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 354329.

Possible duplicates by query: bug 354329, bug 347915.

Reported using DrKonqi

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

[konversation] [Bug 373476] New: Unable to connect with SSL cert authentication enabled

2016-12-09 Thread bugzilla_noreply

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

Bug ID: 373476
   Summary: Unable to connect with SSL cert authentication enabled
   Product: konversation
   Version: 1.6
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: protocol
  Assignee: konversation-de...@kde.org
  Reporter: mailbox@gmail.com
  Target Milestone: ---

When I enable client SSL certificate as a method of authentication and add my
certificate, Konversation immediately disconnects from every server. The
message says (my rough translation) that connection was lost due to unknown
error.

I am able to connect with SSL encryption just fine, as long as I don't use
client SSL certificate.

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

[plasmashell] [Bug 371734] Multiscreen lost configuration of the desktop

2016-12-09 Thread Gábor Katona

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

Gábor Katona  changed:

   What|Removed |Added

 CC||kato...@gmail.com

--- Comment #16 from Gábor Katona  ---
I think my problem, commented to bug #362812 has the same origin. My comment
from that bug:

I also have this, or a very similar problem. Running Opensuse Tumbleweed with
Plasma 5.8.4, Frameworks 5.28.0.

The symptoms are the same, I have folder view set up for the desktop, and it
resets itself back to desktop view. However I use different monitor setups and
I suspect that, at least in my case, the reset is connected to switching
between the different setups.

I use a notebook, sometimes on its own, sometimes using a dock with 2 monitors
connected (the notebook screen is switched off) and sometimes with a projector
with the notebook screen on. I noticed, that changing the monitor settings,
which happens automatically upon connection of the projector or docking he
notebook, sometimes resets back the primary screen (!) to the default desktop
view with the default wallpaper. But only the primary screen.

Also when I try to set up folder view again, the icons are not in the arranged
order, and moreover, in some cases I simply cannot change the layout to folder
view. This latter only happens on activities that were created by me, never
with the original activity.

I have tried deleting plasma-org.kde.plasma.desktop-appletsrc and
plasmashellrc, but the problem stays.

If my problem seems different, I will file a new bug.

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

[dolphin] [Bug 166708] "Switch to root mode" button wish

2016-12-09 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||david.lingu...@gmail.com

--- Comment #5 from Elvis Angelaccio  ---
*** Bug 180970 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 180970] Add ‘paste as root’, ‘delete as root’ etc to file manager

2016-12-09 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||elvis.angelac...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #5 from Elvis Angelaccio  ---


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

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

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

2016-12-09 Thread Tushar

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

--- Comment #10 from Tushar  ---
Based on the crash information, I did disassemble the library in question
(/lib64/tls/libpthread-2.3.4.so) and looked at the instructions at the address
0x382BF0A2F0.  The instructions are

  382bf0a2d1:   e8 92 ab ff ff  callq  382bf04e68 
  382bf0a2d6:   49 83 fc ff cmp$0x,%r12
  382bf0a2da:   74 23   je 382bf0a2ff

  382bf0a2dc:   48 8d 15 3d fe ff fflea-0x1c3(%rip),%rdx#
382bf0a120 <__sem_search>
  382bf0a2e3:   48 8d 35 66 a0 10 00lea0x10a066(%rip),%rsi#
382c014350 <__sem_mappings>
  382bf0a2ea:   48 89 dfmov%rbx,%rdi
  382bf0a2ed:   e8 46 ad ff ff  callq  382bf05038 
  382bf0a2f2:   48 85 c0test   %rax,%rax
  382bf0a2f5:   74 08   je 382bf0a2ff

  382bf0a2f7:   4d 89 e7mov%r12,%r15
  382bf0a2fa:   e9 74 ff ff ff  jmpq   382bf0a273

  382bf0a2ff:   48 89 dfmov%rbx,%rdi
  382bf0a302:   e8 71 ad ff ff  callq  382bf05078 
  382bf0a307:   e9 67 ff ff ff  jmpq   382bf0a273

  382bf0a30c:   45 31 c9xor%r9d,%r9d
  382bf0a30f:   45 89 f0mov%r14d,%r8d

The thing that caught my attention is that data @ 0x382BF0A2F0 seems to be part
of  callq instruction @ 382bf0a2ed.  VEX seems to think it is the start of a
new instruction.

The disassembly of the test code (sem_open) itself at the are of interest is

  400aca:   ba f6 0d 40 00  mov$0x400df6,%edx
  400acf:   be 20 00 00 00  mov$0x20,%esi
  400ad4:   b8 00 00 00 00  mov$0x0,%eax
  400ad9:   e8 e2 fd ff ff  callq  4008c0 
  400ade:   48 8d 7d c0 lea-0x40(%rbp),%rdi
  400ae2:   b9 01 00 00 00  mov$0x1,%ecx
  400ae7:   ba 80 01 00 00  mov$0x180,%edx
  400aec:   be c0 00 00 00  mov$0xc0,%esi
  400af1:   b8 00 00 00 00  mov$0x0,%eax
  400af6:   e8 25 fe ff ff  callq  400920 
  400afb:   48 89 05 b6 07 20 00mov%rax,0x2007b6(%rip)#
6012b8 
  400b02:   48 83 3d ae 07 20 00cmpq   $0x0,0x2007ae(%rip)#
6012b8 
  400b09:   00
  400b0a:   75 24   jne400b30 
  400b0c:   48 8d 55 c0 lea-0x40(%rbp),%rdx
  400b10:   be 10 0e 40 00  mov$0x400e10,%esi
  400b15:   48 8b 3d 7c 07 20 00mov0x20077c(%rip),%rdi#
601298 
  400b1c:   b8 00 00 00 00  mov$0x0,%eax
  400b21:   e8 ea fd ff ff  callq  400910 



I hope this information helps

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

[kdeplasma-addons] [Bug 373410] Turn on "Offer shutdown options" doesn't re-enable Restart and Shutdown buttons in Dashboard.

2016-12-09 Thread Eike Hein

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Hein  ---
They aren't actually gone - they disappear and reappear in the "Power and
Session" category in realtime as needed. Disabling the options automatically
removes them from the favorites, and it's true they're not re-added
automatically; you need to add them back as favorites yourself.

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

[kdevplatform] [Bug 373475] New: crash when starting the patchreview plugin (NULL ptr dereference in Sublime::IdealController::raiseView)

2016-12-09 Thread RJVB

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

Bug ID: 373475
   Summary: crash when starting the patchreview plugin (NULL ptr
dereference in Sublime::IdealController::raiseView)
   Product: kdevplatform
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: patchreview
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com
CC: david.nolden@art-master.de
  Target Milestone: ---

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

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

I used the patchreview plugin through the git/Show differences context menu in
order to obtain a patchfile. The crash was immediate.

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

Thread 11 (Thread 0x7f486b332700 (LWP 6505)):
#0  0x7f4888f87fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4879828b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f487982a64f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f486dfa9f09 in QXcbEventReader::run (this=0x1a3eea0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1331
#4  0x7f4889636cf9 in QThreadPrivate::start (arg=0x1a3eea0) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qthread_unix.cpp:365
#5  0x7f4882b61184 in start_thread (arg=0x7f486b332700) at
pthread_create.c:312
#6  0x7f4888f9537d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 10 (Thread 0x7f4869e28700 (LWP 6506)):
#0  0x7f4888f866cd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4881d1cc10 in read (__nbytes=16, __buf=0x7f4869e27c30,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7f48640015b0) at
/build/buildd/glib2.0-2.40.2/./glib/gwakeup.c:210
#3  0x7f4881cdbb14 in g_main_context_check
(context=context@entry=0x7f485c000990, max_priority=2147483647,
fds=fds@entry=0x7f485c0108f0, n_fds=n_fds@entry=1) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3532
#4  0x7f4881cdbf7b in g_main_context_iterate
(context=context@entry=0x7f485c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3731
#5  0x7f4881cdc0ec in g_main_context_iteration (context=0x7f485c000990,
may_block=may_block@entry=1) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3795
#6  0x7f4889852b0b in QEventDispatcherGlib::processEvents
(this=0x7f485c0008c0, flags=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:419
#7  0x7f48897fc7aa in QEventLoop::exec (this=this@entry=0x7f4869e27e20,
flags=..., flags@entry=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/kernel/qeventloop.cpp:206
#8  0x7f4889631fdb in QThread::exec (this=this@entry=0x7f488b67a420
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qthread.cpp:500
#9  0x7f488b409615 in QDBusConnectionManager::run (this=0x7f488b67a420
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/dbus/qdbusconnection.cpp:189
#10 0x7f4889636cf9 in QThreadPrivate::start (arg=0x7f488b67a420 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.2/qtbase/src/corelib/thread/qthread_unix.cpp:365
#11 0x7f4882b61184 in start_thread (arg=0x7f4869e28700) at
pthread_create.c:312
#12 0x7f4888f9537d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7f4858c94700 (LWP 6518)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f4889637a36 in wait_relative (time=1000, this=0x2423d10) at

[plasmashell] [Bug 362812] Desktop resets to regular desktop when using Folder View

2016-12-09 Thread Gábor Katona

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

--- Comment #4 from Gábor Katona  ---
Additionally plasmashell crashes occasionally when disconnecting monitors

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

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

2016-12-09 Thread Johannes Zarl-Zierl

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

Johannes Zarl-Zierl  changed:

   What|Removed |Added

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

--- Comment #8 from Johannes Zarl-Zierl  ---
Fix was confirmed in pm to me...

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

[krita] [Bug 373191] Drawing has either "no pressure sensitivity+freezing brushes" or the brush is offset from the pen depending on the info in the "Choose Screen Resolution dialog" on multiscreen (ci

2016-12-09 Thread Boudewijn Rempt

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

--- Comment #10 from Boudewijn Rempt  ---
A tablet works like this: it first sends a tablet event. If the tablet event is
not accepted, and most things like menus and toolbars don't send tablet events,
it is sent again as a mouse event. Since that's much simpler and much more
standard and less likely to be influenced by things like the difference between
monitor resolution & tablet resolution, much less can go wrong.

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

[kgpg] [Bug 372063] Revocation certificate is created, but an error message is also shown

2016-12-09 Thread Rolf Eike Beer

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

Rolf Eike Beer  changed:

   What|Removed |Added

Summary|Unable to create a  |Revocation certificate is
   |revocation certificate  |created, but an error
   ||message is also shown

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

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

2016-12-09 Thread Jan Wolter

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

--- Comment #39 from Jan Wolter  ---
Created attachment 102709
  --> https://bugs.kde.org/attachment.cgi?id=102709=edit
New version of Patch

Hi Gilles,
see attached the patch. To update the paramters in CoreDbAccess according to
the dbEngineParameters, I call setupdatebase.cpp:
CoreDbAccess::setParameters(params);

See the complete snippet here:
if (d->databaseWidget->getDbEngineParameters().ignoredDirectories !=
d->databaseWidget->orgDatabasePrm().ignoredDirectories)
{
qCDebug(DIGIKAM_GENERAL_LOG) << "Ignored directories settings changes.
Update...";
DbEngineParameters params = d->databaseWidget->getDbEngineParameters();
settings->setDbEngineParameters(params);
settings->saveSettings();
CoreDbAccess::setParameters(params);
ScanController::instance()->completeCollectionScanInBackground(false);
}

But unfortunately, this crashed the hole application:
*** Error in `/opt/kf5/bin/digikam': double free or corruption (fasttop):
0x7fffc00dcbe0 ***
Program received signal SIGABRT, Aborted.

Do you know a way to update the parameters in CoreDbAccess correctly?

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

[kgpg] [Bug 373408] kgpg segfault on boot and every later run

2016-12-09 Thread Rolf Eike Beer

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

Rolf Eike Beer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
Version|unspecified |git
   Version Fixed In||16.12.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||86b868474fb9b9eb1bf7092bc5c
   ||c7aae03f4090e

--- Comment #1 from Rolf Eike Beer  ---
Git commit 86b868474fb9b9eb1bf7092bc5cc7aae03f4090e by Rolf Eike Beer.
Committed on 08/12/2016 at 12:35.
Pushed by dakon into branch 'Applications/16.12'.

fix crash when GnuPG does not output curve fields for keys, take 2

This is also needed for subkeys.

Related: bug 371410

M  +2-1kgpginterface.cpp

https://commits.kde.org/kgpg/86b868474fb9b9eb1bf7092bc5cc7aae03f4090e

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

[kgpg] [Bug 371410] kgpg crashes on startup and otherwise

2016-12-09 Thread Rolf Eike Beer

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

--- Comment #6 from Rolf Eike Beer  ---
See also bug 373408

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

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

2016-12-09 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

   Assignee|digikam-de...@kde.org   |kde-imag...@kde.org
  Component|libkipi |Flickr
   Version Fixed In||5.4.0
Product|digikam |kipiplugins

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

[plasmashell] [Bug 371219] Plasma going in to visual stasis when a game that block compositing, starts

2016-12-09 Thread Ruman Gerst

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

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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

[kdenlive] [Bug 373474] git master - crashed while clicking on a position in Timeline. [backtrace log included]

2016-12-09 Thread Jesse

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

Jesse  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 372309] Appearance -> Colors -> Edit Scheme (dialog breakup on vertical expand)

2016-12-09 Thread bugzilla_noreply

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

andydecle...@gmail.com changed:

   What|Removed |Added

 CC||andydecle...@gmail.com

--- Comment #1 from andydecle...@gmail.com ---
Quite inconvenient for looking at as many color as possible simultaneously.
Just came here now to report this, thanks for doing it first.

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

[kdenlive] [Bug 373474] New: git master - crashed while clicking on a position in Timeline. [backtrace log included]

2016-12-09 Thread Jesse

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

Bug ID: 373474
   Summary: git master - crashed while clicking on a position in
Timeline. [backtrace log included]
   Product: kdenlive
   Version: git-master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com
  Target Milestone: ---

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

I'd originally been using gdb to record for a different bug, but this came up
in the process. I think I noticed Kdenlive froze and Terminal reported crash
after I had left-clicked a location in the timeline.

Crash bug discovered while using Kdenlive 17.03.70 git master ppa on Antergos
(Arch) Linux x64, GNOME 3.22.2 desktop environment, Xorg 1.18, kernel 4.8.12-13
ARCH.

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

[krita] [Bug 372677] Perspective transform loses entire layer content for full document layers

2016-12-09 Thread Dmitry Kazakov

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/15888ba4f919e73af7d3add9 |ta/050f8354c1506af25e501153
   |83ed6113e8de4f7a|e11551699d63cd20

--- Comment #7 from Dmitry Kazakov  ---
Git commit 050f8354c1506af25e501153e11551699d63cd20 by Dmitry Kazakov.
Committed on 09/12/2016 at 17:58.
Pushed by dkazakov into branch 'rempt/impex-refactoring'.

Fix a NaN transformation when using 4-point perspective transform

It appeared that my matrix decomposition could not decompose an
identity matrix :( Well, we need to implement a better one, e.g.
from CSS. For now just avoid division by zero.

Most probably, the problem appeared after introduction of cursor
snapping. Before snapping identity matrix was almost impossible
to get with a mouse cursor.
Ref T4840

M  +28   -15  
plugins/tools/tool_transform2/kis_perspective_transform_strategy.cpp

https://commits.kde.org/krita/050f8354c1506af25e501153e11551699d63cd20

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

[krita] [Bug 372677] Perspective transform loses entire layer content for full document layers

2016-12-09 Thread Dmitry Kazakov

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kri
   ||ta/15888ba4f919e73af7d3add9
   ||83ed6113e8de4f7a
 Resolution|--- |FIXED

--- Comment #6 from Dmitry Kazakov  ---
Git commit 15888ba4f919e73af7d3add983ed6113e8de4f7a by Dmitry Kazakov.
Committed on 09/12/2016 at 17:58.
Pushed by dkazakov into branch 'krita/3.1'.

Fix a NaN transformation when using 4-point perspective transform

It appeared that my matrix decomposition could not decompose an
identity matrix :( Well, we need to implement a better one, e.g.
from CSS. For now just avoid division by zero.

Most probably, the problem appeared after introduction of cursor
snapping. Before snapping identity matrix was almost impossible
to get with a mouse cursor.
Ref T4840

M  +28   -15  
plugins/tools/tool_transform2/kis_perspective_transform_strategy.cpp

https://commits.kde.org/krita/15888ba4f919e73af7d3add983ed6113e8de4f7a

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

[plasmashell] [Bug 362812] Desktop resets to regular desktop when using Folder View

2016-12-09 Thread Gábor Katona

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

Gábor Katona  changed:

   What|Removed |Added

 CC||kato...@gmail.com

--- Comment #3 from Gábor Katona  ---
I also have this, or a very similar problem. Running Opensuse Tumbleweed with
Plasma 5.8.4, Frameworks 5.28.0.

The symptoms are the same, I have folder view set up for the desktop, and it
resets itself back to desktop view. However I use different monitor setups and
I suspect that, at least in my case, the reset is connected to switching
between the different setups.

I use a notebook, sometimes on its own, sometimes using a dock with 2 monitors
connected (the notebook screen is switched off) and sometimes with a projector
with the notebook screen on. I noticed, that changing the monitor settings,
which happens automatically upon connection of the projector or docking he
notebook, sometimes resets back the primary screen (!) to the default desktop
view with the default wallpaper. But only the primary screen.

Also when I try to set up folder view again, the icons are not in the arranged
order, and moreover, in some cases I simply cannot change the layout to folder
view. This latter only happens on activities that were created by me, never
with the original activity.

I have tried deleting plasma-org.kde.plasma.desktop-appletsrc and
plasmashellrc, but the problem stays.

I would suggest reassigning it to Desktop Containment and/or Multi-screen
support. Alternatively I should file a new bug, it the others doesn't use
different screen setups.

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

[krita] [Bug 373473] New: make frame 1 step longer/shorter with shortcuts or RMB

2016-12-09 Thread Bollebib

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

Bug ID: 373473
   Summary: make frame 1 step longer/shorter with shortcuts or RMB
   Product: krita
   Version: 3.0.2 Alpha
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: kwadraatn...@hotmail.com
  Target Milestone: ---

if you select a frame and press a shortcut (usually + and -,but should be
customizable)) then you add or remove a frame to that keyframe. Every frame
that follows either gets pushed back (+) or pulled in (-)


Adding a frame doesnt duplicate or make a newframe it  just makes the keyframe
longer.
Removing instances should not delete single keyframes,they remain a single
keyframe (length=1) 


Selecting a range of frames will work the same
for every keyframe that is selected,add or remove 1 from their framecount.

Selecting a range of frames and removing instances constantly should result in
only the keyframes remaining.



This will help tremendously with frame managment and speed up timing opetations

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

[kwin] [Bug 373470] Kwin compositing falls after launch SDL-version PPSSPP (Sony PSP) emulator

2016-12-09 Thread Aleksey Samoilov

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

--- Comment #4 from Aleksey Samoilov  ---
Hm, yes, you're right. This is not a bug.

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

[kmail2] [Bug 373467] Cannot display date in iso8601 YYYY-MM-DDTHH:MM:SSZ format

2016-12-09 Thread Ken Fallon

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

--- Comment #4 from Ken Fallon  ---
In both the Viewer and message list. Basically anywhere the date is displayed.

If there is a configuration option to set the date to ISO8601 from within
KMAIL, then it is not obvious.

if there is not a option to set the date to ISO8601 from within KMAIL then this
is a bug.

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

[kmail2] [Bug 373467] Cannot display date in iso8601 YYYY-MM-DDTHH:MM:SSZ format

2016-12-09 Thread Ken Fallon

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

--- Comment #3 from Ken Fallon  ---
Created attachment 102708
  --> https://bugs.kde.org/attachment.cgi?id=102708=edit
Kmail showing undesirable date format

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

[kmail2] [Bug 373467] Cannot display date in iso8601 YYYY-MM-DDTHH:MM:SSZ format

2016-12-09 Thread Ken Fallon

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

Ken Fallon  changed:

   What|Removed |Added

 Attachment #102707|Kmail showing undesirable   |Thunderbird showing ISO8601
description|date format |Time format

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

[kwin] [Bug 373470] Kwin compositing falls after launch SDL-version PPSSPP (Sony PSP) emulator

2016-12-09 Thread Martin Gräßlin

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #3 from Martin Gräßlin  ---
That's not a bug, but a feature.

The application provides a hint to the compositor that compositing should be
disabled. KWin honors that request and stops compositing. With 5.8 the
Compositor options provide a setting to disable this behavior.

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

[kmail2] [Bug 373467] Cannot display date in iso8601 YYYY-MM-DDTHH:MM:SSZ format

2016-12-09 Thread Ken Fallon

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

--- Comment #2 from Ken Fallon  ---
Created attachment 102707
  --> https://bugs.kde.org/attachment.cgi?id=102707=edit
Kmail showing undesirable date format

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

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

2016-12-09 Thread Martin Gräßlin

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

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

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

[kwin] [Bug 373472] Kwin Crashed During Eclipse Close Project

2016-12-09 Thread Martin Gräßlin

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

Martin Gräßlin  changed:

   What|Removed |Added

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

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

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

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

[kwin] [Bug 373470] Kwin compositing falls after launch SDL-version PPSSPP (Sony PSP) emulator

2016-12-09 Thread Aleksey Samoilov

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

--- Comment #2 from Aleksey Samoilov  ---
Sorry for my english. I mean, after launch PPSSPP-SDL, compositing disabled
(just like after pressing Shift+Alt+F12). After closing PPSSPP-SDL -
compositing enabled.

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

[digikam] [Bug 312054] Cannot add a collection on the network in Gnome-based environment

2016-12-09 Thread bugzilla_noreply

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

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

   What|Removed |Added

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

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

[kwin] [Bug 373472] New: Kwin Crashed During Eclipse Close Project

2016-12-09 Thread bugzilla_noreply

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

Bug ID: 373472
   Summary: Kwin Crashed During Eclipse Close Project
   Product: kwin
   Version: 5.8.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: deeppurplefed...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.4)

Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.6.7-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I was attempting to close a project in Eclipse when Kwin crashed; it closed
just fine but for some reason Kwin crashed and recovered.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa48b5e4940 (LWP 1338))]

Thread 6 (Thread 0x7fa46bfff700 (LWP 2028)):
#0  0x7fa49b66c343 in select () at /lib64/libc.so.6
#1  0x7fa49c46cbcf in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7fa49c46e2c4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7fa49c46e7fa in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fa49c41f81a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fa49c27e353 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fa4a2f92525 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7fa49c2829ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fa49e4fb5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fa49b6760ed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fa46b7fe700 (LWP 1526)):
#0  0x7fa49e500bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa4a3d3d1a4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7fa4a3d3d1e9 in  () at /lib64/libQt5Script.so.5
#3  0x7fa49e4fb5ca in start_thread () at /lib64/libpthread.so.0
#4  0x7fa49b6760ed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fa473fff700 (LWP 1517)):
#0  0x7fa49b66c343 in select () at /lib64/libc.so.6
#1  0x7fa49c46cbcf in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7fa49c46e2c4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7fa49c46e7fa in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fa49c41f81a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fa49c27e353 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fa4a2f92525 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7fa49c2829ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fa49e4fb5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fa49b6760ed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fa48280e700 (LWP 1420)):
#0  0x7fa49b66c343 in select () at /lib64/libc.so.6
#1  0x7fa49c46cbcf in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7fa49c46e2c4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7fa49c46e7fa in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fa49c41f81a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fa49c27e353 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fa49dff8559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fa49c2829ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fa49e4fb5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fa49b6760ed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fa483ed1700 (LWP 1389)):
#0  0x7fa49b66a56d in poll () at /lib64/libc.so.6
#1  0x7fa49ddcaf80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fa49ddccb79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fa484b7ff99 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fa49c2829ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fa49e4fb5ca in start_thread () at /lib64/libpthread.so.0
#6  0x7fa49b6760ed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fa48b5e4940 (LWP 1338)):
[KCrash Handler]
#6  0x7fa4a2f7dc10 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/lib64/libQt5Qml.so.5
#7  0x7fa4a2f7e967 in
QQmlBinding::update(QFlags) () at
/lib64/libQt5Qml.so.5
#8  0x7fa4a2f88105 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at
/lib64/libQt5Qml.so.5
#9  0x7fa4a2f1217e in

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

2016-12-09 Thread Larry

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

--- Comment #12 from Larry  ---
Created attachment 102706
  --> https://bugs.kde.org/attachment.cgi?id=102706=edit
Finally happened again.  gdb outpu attachedt

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

[kopete] [Bug 231941] Kopete crashed on closing a chat window

2016-12-09 Thread Luca Niverini

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

--- Comment #3 from Luca Niverini  ---
new version 1.10.1 works

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

[umbrello] [Bug 373471] New: Painting artifacts in case class documentation display is enabled

2016-12-09 Thread Ralf Habacker

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

Bug ID: 373471
   Summary: Painting artifacts in case class documentation display
is enabled
   Product: umbrello
   Version: 2.20.80 (KDE Applications 16.11.80)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de
  Target Milestone: ---

Version 2.20.80 umbrello supports display of class documentation in class
diagrams. Enabling class documentation display for classes without any methods
and class members 

How to reproduce:
1. start umbrello
2. Add class to diagram
3. Right-click on class and enable display->documentation
4. Add some text (for example the first or second paragraph from
http://www.agilemodeling.com/artifacts/componentDiagram.htm) to the class
documentation 
-> the class widget is displayed very small in horizontal direction and very
large in vertical direction.
6. Enlarge the widget in horizontal direction
7. Move the widget

-> The widget returns to the size in step 4 and a large vertival part of the
documentation is displayed outside the widget.

What is expected ? 

The widget should remain to the size set in step 6 and the documentation should
be displayed inside the widget

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

[plasmashell] [Bug 306238] Thunderbird compose mail window opens on wrong activity

2016-12-09 Thread Gábor Katona

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

Gábor Katona  changed:

   What|Removed |Added

 CC||plasma-b...@kde.org
Version|4.8.5   |5.8.4
   Target Milestone|--- |1.0
Product|plasma4 |plasmashell
  Component|activities  |Activity Switcher

--- Comment #2 from Gábor Katona  ---
This bug is still present in KDE Plasma 5.8.4, Frameworks 5.28.0, using
Opensuse Tumbleweed with Thunderbird 45.5.1

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

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

2016-12-09 Thread Serge Moreau

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

Serge Moreau  changed:

   What|Removed |Added

 CC||smorea...@orange.fr

--- Comment #3 from Serge Moreau  ---
The only way to get a new user using user-manager is to check the box admin for
this user. In that case polkit display the window asking for your password and
the new user is created with the expected rights.
Using Maui with Plasma 5.8.3

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

[kmail2] [Bug 373467] Cannot display date in iso8601 YYYY-MM-DDTHH:MM:SSZ format

2016-12-09 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Hi,
in which component ?
Viewer ?
messagelist ?

How do you configure it ?

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

[kwin] [Bug 373470] Kwin compositing falls after launch SDL-version PPSSPP (Sony PSP) emulator

2016-12-09 Thread Martin Gräßlin

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

--- Comment #1 from Martin Gräßlin  ---
Sorry I don't understand what you mean with "Kwin compositing falls and restart
after exit from PPSSPP-SDL"

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

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

2016-12-09 Thread Eike Hein

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/pla
   ||sma-workspace/0b0d14639a1a0
   ||eb2766d74daa3358c0939b6d8b3

--- Comment #2 from Eike Hein  ---
Git commit 0b0d14639a1a0eb2766d74daa3358c0939b6d8b3 by Eike Hein.
Committed on 09/12/2016 at 16:50.
Pushed by hein into branch 'Plasma/5.8'.

Refresh the ScreenGeometry data role whenever a screen is added or changes its
geometry.

Summary:
As this happens the screen filtering higher up in the proxy chain
culimating in TasksModel needs to be re-executed, as it compares
ScreenGeometry against a property value set on the model. Without
this update, tasks may disappear from views using TasksModel.

Mapping the trigger conditions to affected rows is deliberately
maximally coarse; see implementation comment in code.

Reviewers: #plasma, davidedmundson

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D3628

M  +2-0libtaskmanager/CMakeLists.txt
A  +60   -0libtaskmanager/abstractwindowtasksmodel.cpp [License: BSD]
A  +53   -0libtaskmanager/abstractwindowtasksmodel.h [License: BSD]
M  +1-1libtaskmanager/waylandtasksmodel.cpp
M  +2-2libtaskmanager/waylandtasksmodel.h
M  +1-1libtaskmanager/xwindowtasksmodel.cpp
M  +2-2libtaskmanager/xwindowtasksmodel.h

https://commits.kde.org/plasma-workspace/0b0d14639a1a0eb2766d74daa3358c0939b6d8b3

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

[umbrello] [Bug 349622] Display "documentation" in Umbrello's diagrams

2016-12-09 Thread Ralf Habacker

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

Ralf Habacker  changed:

   What|Removed |Added

   Version Fixed In|2.20.80 (KDE Applications   |2.21.80 (KDE Applications
   |16.11.80)   |17.03.80)

--- Comment #11 from Ralf Habacker  ---
2.21.0 is already out. Feature will be in next stable release.

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

[kwin] [Bug 373470] New: Kwin compositing falls after launch SDL-version PPSSPP (Sony PSP) emulator

2016-12-09 Thread Aleksey Samoilov

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

Bug ID: 373470
   Summary: Kwin compositing falls after launch SDL-version PPSSPP
(Sony PSP) emulator
   Product: kwin
   Version: 5.8.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: samoilov@gmail.com
  Target Milestone: ---

Overview: After launch SDL-version PPSSPP (Sony PSP) emulator, Kwin compositing
falls and restart after exit from PPSSPP-SDL. Version PPSSPP - 1.3.0, but
Git-builds has same effect.

Steps to Reproduce: just install and run PPSSPP-SDL from official site, or PPA,
or compile it yourself.

Additional Information: my system: CPU: Intel Core i3-550; RAM: 8G; Graphics
card: Nvidia GTX 760 2G; Nvidia driver: 375.20; OS: KDE Neon 5.8.4.

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

[umbrello] [Bug 349622] Display "documentation" in Umbrello's diagrams

2016-12-09 Thread Ralf Habacker

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/umbr
   ||ello/739f263d374ebe09b192bb
   ||7e08beff17ee585838
 Status|ASSIGNED|RESOLVED
   Version Fixed In||2.20.80 (KDE Applications
   ||16.11.80)

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

[kdenlive] [Bug 373468] Offset in timeline marker and pointer

2016-12-09 Thread Jean-Baptiste Mardelle

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kde
   ||nlive/10b08d573c5396c3fbf3d
   ||5e194ccbb798d951f7b

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 10b08d573c5396c3fbf3d5e194ccbb798d951f7b by Jean-Baptiste Mardelle.
Committed on 09/12/2016 at 16:44.
Pushed by mardelle into branch 'Applications/16.12'.

Fix timeline cursor offset after changing track height

M  +2-1src/timeline/timeline.cpp

https://commits.kde.org/kdenlive/10b08d573c5396c3fbf3d5e194ccbb798d951f7b

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

[kile] [Bug 373469] New: File-Statistics crashes kile

2016-12-09 Thread S . Umar

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

Bug ID: 373469
   Summary: File-Statistics crashes kile
   Product: kile
   Version: 2.9.60
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

Hi. Using the latest git snapshot pulling down Statistics from the File menu
crashes kile every time.

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

[dolphin] [Bug 373162] Terminal Panel crash with zsh

2016-12-09 Thread Olivier BELLEUX

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

--- Comment #2 from Olivier BELLEUX  ---
Hello Killian,

I think this is actually a zsh packaging problem because I was able to solve
this bug by installing zsh 5.2 (x86_64-suse-linux-gnu) from
http://download.opensuse.org/ Repositories / shells / openSUSE_Leap_42.2 /
repo.shell.

Nevertheless it is possible that there is a problem in the code of Dolphin or
Konsole part.

I hope this post will allow you to solve this Dolphin crash.

Goodbye

Olivier BELLEUX

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

[kile] [Bug 364238] cite command not showing bibliography entries

2016-12-09 Thread S . Umar

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

--- Comment #2 from S. Umar  ---
This issue is still there in latest git snapshot.

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

[kdenlive] [Bug 358178] git master - Title editor, have middle mouse button click pan around title window?

2016-12-09 Thread Jesse

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

--- Comment #2 from Jesse  ---
@Farid, totally.

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

[kdenlive] [Bug 373468] Offset in timeline marker and pointer

2016-12-09 Thread farid

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

farid  changed:

   What|Removed |Added

   Severity|major   |normal

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

[kdenlive] [Bug 373468] Offset in timeline marker and pointer

2016-12-09 Thread farid

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

farid  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from farid  ---
Ha, I found that this happens after you change the track height. So it is not
as grave as I thought. Downgrading importance.

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

[kdenlive] [Bug 373468] New: Offset in timeline marker and pointer

2016-12-09 Thread farid

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

Bug ID: 373468
   Summary: Offset in timeline marker and pointer
   Product: kdenlive
   Version: git-master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: snd.no...@gmail.com
  Target Milestone: ---

Created attachment 102705
  --> https://bugs.kde.org/attachment.cgi?id=102705=edit
offset

See attachment

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

[kdenlive] [Bug 373463] Cannot edit guide unless mapped to a shortcut

2016-12-09 Thread farid

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

farid  changed:

   What|Removed |Added

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

--- Comment #1 from farid  ---
In the bottom right corner of the timeline there is a button which has a waving
flag which enables/disables the guide comments, does that fix your issue?

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

[kmail2] [Bug 373467] New: Cannot display date in iso8601 YYYY-MM-DDTHH:MM:SSZ format

2016-12-09 Thread Ken Fallon

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

Bug ID: 373467
   Summary: Cannot display date in iso8601 -MM-DDTHH:MM:SSZ
format
   Product: kmail2
   Version: 5.3.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: usability
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@kenfallon.com
  Target Milestone: ---

In kmail I cannot set the display format for messages to ISO8601 format.

The format reads "Today 12:25 PM" instead of "2016-12-09T11:25:00Z"

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

[krita] [Bug 373076] [HANVON] No tablet interaction with Hanvon Graphic Pal 0806

2016-12-09 Thread bugzilla_noreply

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

--- Comment #9 from edgar.ej.mercad...@gmail.com ---
Created attachment 102704
  --> https://bugs.kde.org/attachment.cgi?id=102704=edit
tablet log 3

Here's a better log file.

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

[krita] [Bug 373316] center or follow layer in timeline when going down the layer stack

2016-12-09 Thread Dmitry Kazakov

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/895967cde6d204282e603247 |ta/62f8c3b3b2937ac24e2ca7d4
   |11995e90393bcbdd|0cf425985d406960

--- Comment #2 from Dmitry Kazakov  ---
Git commit 62f8c3b3b2937ac24e2ca7d40cf425985d406960 by Dmitry Kazakov.
Committed on 09/12/2016 at 15:20.
Pushed by dkazakov into branch 'rempt/impex-refactoring'.

Sync layer scroll-visibility in the timeline when using PgUp and PgDown
Fixes T4837

M  +1-0plugins/dockers/animation/timeline_frames_model.cpp
M  +1-0plugins/dockers/animation/timeline_frames_model.h
M  +11   -0plugins/dockers/animation/timeline_frames_view.cpp
M  +2-0plugins/dockers/animation/timeline_frames_view.h
M  +1-6plugins/dockers/animation/timeline_layers_header.cpp
M  +0-3plugins/dockers/animation/timeline_layers_header.h

https://commits.kde.org/krita/62f8c3b3b2937ac24e2ca7d40cf425985d406960

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

[krita] [Bug 373316] center or follow layer in timeline when going down the layer stack

2016-12-09 Thread Dmitry Kazakov

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kri
   ||ta/895967cde6d204282e603247
   ||11995e90393bcbdd
 Resolution|--- |FIXED

--- Comment #1 from Dmitry Kazakov  ---
Git commit 895967cde6d204282e60324711995e90393bcbdd by Dmitry Kazakov.
Committed on 09/12/2016 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Sync layer scroll-visibility in the timeline when using PgUp and PgDown
Fixes T4837

M  +1-0plugins/dockers/animation/timeline_frames_model.cpp
M  +1-0plugins/dockers/animation/timeline_frames_model.h
M  +11   -0plugins/dockers/animation/timeline_frames_view.cpp
M  +2-0plugins/dockers/animation/timeline_frames_view.h
M  +1-6plugins/dockers/animation/timeline_layers_header.cpp
M  +0-3plugins/dockers/animation/timeline_layers_header.h

https://commits.kde.org/krita/895967cde6d204282e60324711995e90393bcbdd

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

[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps

2016-12-09 Thread Sacha C

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

Sacha C  changed:

   What|Removed |Added

 CC||sach...@gmail.com

--- Comment #18 from Sacha C  ---
I've run in to the same issue.
Option 3 seems most reasonable to me since option 4 cannot be done. Hopefully
it won't be a lot of work to maintain that list.

Out of curiosity, does anyone know how Gnome (or maybe it's GTK) handles it? I
just tried with both VirtualBox and VMWare, and it seems to be able to suppress
the meta key on the host and send it only to the guest.

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

1 2 >

1 - 100 of 158 matches

Mail list logo