[kipiplugins] [Bug 213340] "rotate left" and "rotate right" actually rotate by 180 degrees

[Dan Dascalescu]

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

Dan Dascalescu  changed:

   What|Removed |Added

 CC||ddascalescu+...@gmail.com

--- Comment #10 from Dan Dascalescu  ---
Created attachment 103584
  --> https://bugs.kde.org/attachment.cgi?id=103584=edit
I still see this bug in the 5.5.0 appimage. Sample attached.

After the first incorrect rotation, subsequent rotations work correctly, but
the first rotation is 180 degrees instead of 90.

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

[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[bugzilla_noreply]

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

mrpeac...@web.de changed:

   What|Removed |Added

 CC||mrpeac...@web.de

--- Comment #13 from mrpeac...@web.de ---
same here on arch linux

Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f99811d1840 (LWP 1980))]

Thread 2 (Thread 0x7f996e3ad700 (LWP 1982)):
#0  0x7f9980c1248d in poll () from /usr/lib/libc.so.6
#1  0x7f99761c4786 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f99761c489c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f997d2583eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f997d201c1a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f997d0239f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f9979cd00c5 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f997d028658 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f9977c88454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f9980c1b7df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f99811d1840 (LWP 1980)):
[KCrash Handler]
#6  0x7f996d163138 in wl_map_insert_at (map=,
flags=flags@entry=0, i=, data=) at
src/wayland-util.c:249
#7  0x7f996d15efbe in proxy_destroy (proxy=0x25c5cf0) at
src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=0x25c5cf0) at src/wayland-client.c:442
#9  0x7f996c2891e5 in KWayland::Client::Registry::release() () from
/usr/lib/libKF5WaylandClient.so.5
#10 0x7f996c28920e in KWayland::Client::Registry::~Registry() () from
/usr/lib/libKF5WaylandClient.so.5
#11 0x7f996c2892e9 in KWayland::Client::Registry::~Registry() () from
/usr/lib/libKF5WaylandClient.so.5
#12 0x7f997d22d791 in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#13 0x7f997d2370ef in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#14 0x7f99660fe393 in ?? () from
/usr/lib/qt/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so
#15 0x7f9980b68990 in __run_exit_handlers () from /usr/lib/libc.so.6
#16 0x7f9980b689ea in exit () from /usr/lib/libc.so.6
#17 0x7f9980b53298 in __libc_start_main () from /usr/lib/libc.so.6
#18 0x0040066a in _start ()

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

[digikam] [Bug 375110] Open with doesn't remember application association

[Dan Dascalescu]

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

Dan Dascalescu  changed:

   What|Removed |Added

 Attachment #103432|0   |1
is obsolete||

--- Comment #8 from Dan Dascalescu  ---
Created attachment 103583
  --> https://bugs.kde.org/attachment.cgi?id=103583=edit
I no longer see this problem in 5.5.0

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

[kwin] [Bug 375400] KWIN crashes at start of second application

[Rüdiger Bente]

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

Rüdiger Bente  changed:

   What|Removed |Added

 CC||ruediger.be...@gmx.de

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

[kwin] [Bug 375400] New: KWIN crashes at start of second application

[Rüdiger Bente]

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

Bug ID: 375400
   Summary: KWIN crashes at start of second application
   Product: kwin
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ruediger.be...@gmx.de
  Target Milestone: ---

Created attachment 103582
  --> https://bugs.kde.org/attachment.cgi?id=103582=edit
kwin qdbus support information

After login, starting the second application, kwin crashes. Does no matter,
which are this application, most of the time is start first Firefox and after
that Thunderbird, but the problem occurs on other scenarios as well.
Got some debug information:
 Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6905958940 (LWP 1552))]

Thread 4 (Thread 0x7f684700 (LWP 1763)):
#0  0x7f69054439e3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6903c47e5f in qt_safe_select (nfds=15,
fdread=fdread@entry=0x7f68480df878, fdwrite=fdwrite@entry=0x7f68480dfb08,
fdexcept=fdexcept@entry=0x7f68480dfd98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f6903c4995e in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f68480dfd98, writefds=0x7f68480dfb08, readfds=0x7f68480df878,
nfds=, this=0x7f6848146070) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f68480df6e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f6903c49e8e in QEventDispatcherUNIX::processEvents
(this=0x7f6848146070, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f6903bf3b4a in QEventLoop::exec (this=this@entry=0x7f684fffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f6903a10834 in QThread::exec (this=this@entry=0x2c6d270) at
thread/qthread.cpp:503
#7  0x7f68fe5263c5 in QQmlThreadPrivate::run (this=0x2c6d270) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f6903a157be in QThreadPrivate::start (arg=0x2c6d270) at
thread/qthread_unix.cpp:331
#9  0x7f68ff3c96ba in start_thread (arg=0x7f684700) at
pthread_create.c:333
#10 0x7f690544d82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f68db7fe700 (LWP 1586)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6902b9dbd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f6902b9dc19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f68ff3c96ba in start_thread (arg=0x7f68db7fe700) at
pthread_create.c:333
#4  0x7f690544d82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f68e1515700 (LWP 1583)):
#0  0x7f6903a0dd5f in QBasicAtomicOps<8>::testAndSetRelaxed
(currentValue=, newValue=0x0, expectedValue=0x1,
_q_value=@0x290b638: 0x0) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259
#1  QGenericAtomicOps >::testAndSetRelease (currentValue=, newValue=0x0,
expectedValue=, _q_value=@0x290b638: 0x0) at
../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:175
#2  QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=,
this=this@entry=0x290b638) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:278
#3  QBasicMutex::fastTryUnlock (current=,
this=this@entry=0x290b638) at thread/qmutex.h:85
#4  QMutex::unlock (this=this@entry=0x290b638) at thread/qmutex.cpp:264
#5  0x7f6903c49d83 in QMutexLocker::unlock (this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:138
#6  QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:132
#7  QThreadData::canWaitLocked (this=) at
../../include/QtCore/5.5.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:240
#8  QEventDispatcherUNIX::processEvents (this=0x7f68d40008c0, flags=...) at
kernel/qeventdispatcher_unix.cpp:582
#9  0x7f6903bf3b4a in QEventLoop::exec (this=this@entry=0x7f68e1514c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#10 0x7f6903a10834 in QThread::exec (this=this@entry=0x28aa9d0) at
thread/qthread.cpp:503
#11 0x7f68fe5263c5 in QQmlThreadPrivate::run (this=0x28aa9d0) at
qml/ftw/qqmlthread.cpp:141
#12 0x7f6903a157be in QThreadPrivate::start (arg=0x28aa9d0) at
thread/qthread_unix.cpp:331
#13 0x7f68ff3c96ba in start_thread (arg=0x7f68e1515700) at
pthread_create.c:333
#14 0x7f690544d82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f6905958940 (LWP 1552)):
[KCrash Handler]
#6  QV4::Managed::d (this=0x0) at jsruntime/qv4managed_p.h:134
#7  

[plasmashell] [Bug 375229] Non-storage of Desktop icons across sessions

[bugzilla_noreply]

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

acer11kubu...@gmail.com changed:

   What|Removed |Added

 CC||acer11kubu...@gmail.com

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

[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution

[bugzilla_noreply]

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

--- Comment #12 from acer11kubu...@gmail.com ---
(In reply to Christoph Feck from comment #9)
> > MINOR?! Are you serious?
> 
> Fixed. The original reporter actually states that it is a major issue.
> 
> Certainly not a junior-job.

Thanks, Christoph.

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

[digikam] [Bug 375357] No video preview

[bugzilla_noreply]

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

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

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.5.0
 Resolution|--- |DOWNSTREAM

--- Comment #3 from caulier.gil...@gmail.com ---
Same problem than bug #375399. See my comment here : 

https://bugs.kde.org/show_bug.cgi?id=375399#c1

Gilles Caulier

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

[digikam] [Bug 375399] No preview of video files

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||5.5.0

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

[digikam] [Bug 375399] No preview of video files

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Well, video support is a compilation option. Report this problem to Fedora
maintainer as DOWNSTREAM problem.

Note : you can use AppImage universal Linux bundle. Video support is enabled.
The pre version 5.5.0 is available at this place :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 375399] No preview of video files

[bugzilla_noreply]

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

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

   What|Removed |Added

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

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

[digikam] [Bug 375399] New: No preview of video files

[Jim Shipman]

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

Bug ID: 375399
   Summary: No preview of video files
   Product: digikam
   Version: 5.4.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Preview
  Assignee: digikam-de...@kde.org
  Reporter: jims...@sbcglobal.net
  Target Milestone: ---

My System - Fedora 25
After upgrade to 5.4.0-1 from the standard fedora 25 repository, I no longer
get previews of video files (any type).
1) Pressing the fullscreen button on the thumbnails give the fullscreen viewer
with an error message.  It works fine with photos.
2) All video formats play perfectly with every player installed on my system.
3) I have install QtAV and the qtav-player works perfectly with my videos.
4) Qt = 5.7.1, EXIV2 = 0.25
5) Component list shows "Media Player Support = no". All other components are
yes or a version number.

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

[dolphin] [Bug 375398] New: Folder panel mouse-scrolls at different speed to files (main view) panel

[Jedd]

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

Bug ID: 375398
   Summary: Folder panel mouse-scrolls at different speed to files
(main view) panel
   Product: dolphin
   Version: 16.08.3
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: folders
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: b...@jeddi.org
  Target Milestone: ---

Using the 'details' view, scrolling in the main file panel works at around 3
lines per 'click' of the scroll button.

The folder panel moves at about 24x slower - it takes about 8 scroll clicks to
move the contents by one line's worth.

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

[kwin] [Bug 375332] KWin crashed after closing my wine application.

[bugzilla_noreply]

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

--- Comment #5 from x-u...@bk.ru ---
Added new backtrace in attachments.

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

[kwin] [Bug 375332] KWin crashed after closing my wine application.

[bugzilla_noreply]

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

--- Comment #4 from x-u...@bk.ru ---
Created attachment 103581
  --> https://bugs.kde.org/attachment.cgi?id=103581=edit
Backtrace

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

[Discover] [Bug 375397] New: Spurious software upgrade notifications

[bugzilla_noreply]

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

Bug ID: 375397
   Summary: Spurious software upgrade notifications
   Product: Discover
   Version: 5.7.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Updater
  Assignee: aleix...@kde.org
  Reporter: mabbott...@gmail.com
  Target Milestone: ---

The System Notification Helper pops up a window to notify "Software upgrade
notifications are available" every few minutes for the duration of every login
session, even though no updates are actually available if one goes to Discover
and checks.  

This began happening about 9-10 months ago under Kubuntu 16.04 and has
persisted across all updates since including upgrade to 16.10.  I've
installed/uninstalled various update managers over the period with no effect. 
It isn't clear to me which component is responsible for generating the
notifications so I am filing this under the Discover updater.

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

[plasmashell] [Bug 369142] Crash in QQuickItem::isEnabled on startup

[kafei]

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

--- Comment #19 from kafei  ---
I don't believe I've had this crash occur since I upgraded to Plasma 5.8.4, and
I definitely haven't had it occur with Plasma 5.8.5. I just checked through all
the duplicates, and all of them report a plasma version <5.8.4, so it's
possible the crash was fixed in that version.

Fwiw, I was never able to get the crash to occur under Valgrind.

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

[krunner] [Bug 375396] Opening files with krunner can spawn subprocesses which use 100% CPU

[kafei]

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

--- Comment #1 from kafei  ---
Created attachment 103580
  --> https://bugs.kde.org/attachment.cgi?id=103580=edit
Open file handles for krunner parent and child

It's strange how krunner has open file handles to /dev/nvidia0 and the like...
I suppose krunner somehow uses GPU acceleration?

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

[krunner] [Bug 375396] New: Opening files with krunner can spawn subprocesses which use 100% CPU

[kafei]

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

Bug ID: 375396
   Summary: Opening files with krunner can spawn subprocesses
which use 100% CPU
   Product: krunner
   Version: 5.8.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: matthewisrip...@gmail.com
  Target Milestone: ---

Created attachment 103579
  --> https://bugs.kde.org/attachment.cgi?id=103579=edit
htop screenshot of krunner cpu usage

My system was acting sluggish today, so I opened htop to discover that krunner
had pegged all 4 of my cores at 100% usage! It seemed to have spawned 4
subprocesses, each of which was using 100% of a core.

I restarted my PC and my CPU usage was normal again. I managed to reproduce the
bug as follows (with opening krunner by pressing alt+space):

* Start okular through krunner: CPU usage normal
* Search for a PDF through krunner and open it in the previous okular instance:
one core starts running at 100%
* Search and open a second PDF: a second core starts running at 100%
* Try opening a few more PDFs: no change in CPU usage, still 2 cores pegged at
100%
* Open gwenview through krunner: no change
* Try opening another PDF: a third core starts running at 100%
* Open spectacle through krunner: a fourth core starts running at 100%

So the bug is reproducible after using krunner enough times, but not every
usage results in another subprocess being spawned using 100% CPU.

I've attached a screenshot of htop, as well as the open file handles for both
the parent krunner process and one of the children using 100% CPU. Bug 364268
also seems to describe this problem, however I can confirm that the bug does
not only happen when opening OpenGL apps.

System specs:
Kernel version: 4.8.13-1-ARCH
plasma version: 5.8.5
kf5 version: 5.30.0
kapps version: 16.12.1
CPU: i5-4690K
GPU: Nvidia GTX 970 with proprietary driver, version 375.26

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

[plasmashell] [Bug 375395] New: Plasma consumes all memory when showing calendar popup

[Jure Repinc]

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

Bug ID: 375395
   Summary: Plasma consumes all memory when showing calendar popup
   Product: plasmashell
   Version: 5.8.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Calendar
  Assignee: plasma-b...@kde.org
  Reporter: j...@holodeck1.com
  Target Milestone: 1.0

Created attachment 103578
  --> https://bugs.kde.org/attachment.cgi?id=103578=edit
complete valgrind log

I get this memory consumption bug ever since I created a TODO from within
KMail. What happens now is this. I click the clock plasmoid in Plasma panel to
show calendar popup and plasmashell process starts to consume a lot of memory
very fast until it uses all of 32 GiB of memory and is eventually killed by OOM
killer. I have run plasmashell via valgrind (valgrind --leak-check=full
--track-origins=yes --show-leak-kinds=all -v plasmashell) and these reports
appear to be related with this memory leak:

==5244== 1,073,741,824 bytes in 1 blocks are still reachable in loss record
65,127 of 65,128
==5244==at 0x4C2BE3F: operator new[](unsigned long) (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==5244==by 0xA9E1B04: QHashData::rehash(int) (qhash.cpp:687)
==5244==by 0xC1EEE72F: willGrow (qhash.h:104)
==5244==by 0xC1EEE72F: insertMulti (qhash.h:777)
==5244==by 0xC1EEE72F: insert (qhash.h:1012)
==5244==by 0xC1EEE72F:
EventDataVisitor::insertResult(CalendarEvents::EventData const&)
(eventdatavisitor.cpp:179)
==5244==by 0xC1EEF3B2:
EventDataVisitor::visit(QSharedPointer const&,
CalendarEvents::EventData::EventType) (eventdatavisitor.cpp:157)
==5244==by 0xC1EEF777:
EventDataVisitor::visit(QSharedPointer const&)
(eventdatavisitor.cpp:171)
==5244==by 0xC27D055F: KCalCore::Todo::accept(KCalCore::Visitor&,
QSharedPointer const&) (in
/usr/lib64/libKF5CalendarCore.so.5.4.0)
==5244==by 0xC1EEF9BD:
BaseEventDataVisitor::act(QVector const&)
(eventdatavisitor.cpp:53)
==5244==by 0xC1EE946A: PimEventsPlugin::loadEventsForDateRange(QDate
const&, QDate const&) (pimeventsplugin.cpp:66)
==5244==by 0xC1AC7C28: DaysModel::update() (daysmodel.cpp:105)
==5244==by 0xC1AC618F: Calendar::updateData() [clone .part.7]
(calendar.cpp:300)
==5244==by 0xC1AC660C: updateData (calendar.cpp:96)
==5244==by 0xC1AC660C: Calendar::resetToToday() (calendar.cpp:95)
==5244==by 0xC1AD0414: Calendar::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (moc_calendar_LUV6MJZILS5OPX.cpp:237)
==5244== 
==5244== 3,203,348,064 bytes in 100,104,627 blocks are still reachable in loss
record 65,128 of 65,128
==5244==at 0x4C2B0AF: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==5244==by 0xA9E15C8: QHashData::allocateNode(int) (qhash.cpp:501)
==5244==by 0xC1EEE799: createNode (qhash.h:548)
==5244==by 0xC1EEE799: insertMulti (qhash.h:781)
==5244==by 0xC1EEE799: insert (qhash.h:1012)
==5244==by 0xC1EEE799:
EventDataVisitor::insertResult(CalendarEvents::EventData const&)
(eventdatavisitor.cpp:179)
==5244==by 0xC1EEF3B2:
EventDataVisitor::visit(QSharedPointer const&,
CalendarEvents::EventData::EventType) (eventdatavisitor.cpp:157)
==5244==by 0xC1EEF777:
EventDataVisitor::visit(QSharedPointer const&)
(eventdatavisitor.cpp:171)
==5244==by 0xC27D055F: KCalCore::Todo::accept(KCalCore::Visitor&,
QSharedPointer const&) (in
/usr/lib64/libKF5CalendarCore.so.5.4.0)
==5244==by 0xC1EEF9BD:
BaseEventDataVisitor::act(QVector const&)
(eventdatavisitor.cpp:53)
==5244==by 0xC1EE946A: PimEventsPlugin::loadEventsForDateRange(QDate
const&, QDate const&) (pimeventsplugin.cpp:66)
==5244==by 0xC1AC7C28: DaysModel::update() (daysmodel.cpp:105)
==5244==by 0xC1AC618F: Calendar::updateData() [clone .part.7]
(calendar.cpp:300)
==5244==by 0xC1AC660C: updateData (calendar.cpp:96)
==5244==by 0xC1AC660C: Calendar::resetToToday() (calendar.cpp:95)
==5244==by 0xC1AD0414: Calendar::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (moc_calendar_LUV6MJZILS5OPX.cpp:237)

Complete valgrind.log is attached

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

[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes

[Christian Muehlhaeuser]

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

--- Comment #2 from Christian Muehlhaeuser  ---
I see what's happening now: the screen-locker is active on multiple monitors
and only lets me enter the password on one of them. All the other monitors show
the locker, but don't react to input.

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

[plasmashell] [Bug 360645] Cannot open configuration for more than one widget inside one containment

[Alexander Potashev]

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

--- Comment #1 from Alexander Potashev  ---
Same problem with Plasma 5.8.95.

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

[partitionmanager] [Bug 375394] New: application crash if started without root permission

[bugzilla_noreply]

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

Bug ID: 375394
   Summary: application crash if started without root permission
   Product: partitionmanager
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: mombelli.ma...@gmail.com
  Target Milestone: ---

Application: partitionmanager (3.0.1)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.10.0-rc4-mainline x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I choosen to start the application without ROOT permission, as i wanted to only
llok at the schema and not modify it

- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager), signal: Segmentation
fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f98876d4d00 (LWP 2515))]

Thread 4 (Thread 0x7f985b900700 (LWP 2720)):
[KCrash Handler]
#6  0x7f988710080a in FS::lvm2_pv::getPVs(QList const&) () at
/usr/lib/libkpmcore.so.4
#7  0x7f9887122944 in DeviceScanner::scan() () at /usr/lib/libkpmcore.so.4
#8  0x7f988385dce8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f987f64b454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f98831737df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f986ca65700 (LWP 2517)):
#0  0x7f988316a48d in poll () at /usr/lib/libc.so.6
#1  0x7f987dda2786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f987dda289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9883a8d48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9883a36e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9883859053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f98815a2de5 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f988385dce8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f987f64b454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f98831737df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f9874ec2700 (LWP 2516)):
#0  0x7f988316a48d in poll () at /usr/lib/libc.so.6
#1  0x7f987d9338e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f987d935679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f9876e0f789 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f988385dce8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f987f64b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f98831737df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f98876d4d00 (LWP 2515)):
#0  0x7f987f65110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f987d933b57 in  () at /usr/lib/libxcb.so.1
#2  0x7f987d93539f in  () at /usr/lib/libxcb.so.1
#3  0x7f987d9354b2 in xcb_wait_for_reply () at /usr/lib/libxcb.so.1
#4  0x7f9876397f61 in xcb_icccm_get_wm_hints_reply () at
/usr/lib/libxcb-icccm.so.4
#5  0x7f9876e2a654 in QXcbWindow::show() () at /usr/lib/libQt5XcbQpa.so.5
#6  0x7f9883f87e7b in QWindow::setVisible(bool) () at
/usr/lib/libQt5Gui.so.5
#7  0x7f988474e1cc in QWidgetPrivate::show_sys() () at
/usr/lib/libQt5Widgets.so.5
#8  0x7f98847565f0 in QWidgetPrivate::show_helper() () at
/usr/lib/libQt5Widgets.so.5
#9  0x7f98847593f5 in QWidget::setVisible(bool) () at
/usr/lib/libQt5Widgets.so.5
#10 0x004285ec in main ()

Reported using DrKonqi

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

[plasmashell] [Bug 375393] New: Plasma crashed after closing multiple windows

[Simon Heimbach]

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

Bug ID: 375393
   Summary: Plasma crashed after closing multiple windows
   Product: plasmashell
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: s.heimb...@explosive-software.de
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.36-8-default x86_64
Distribution: "openSUSE Leap 42.2"

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

I quickly closed several windows with the "Close-Button" in the window top.

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

Thread 22 (Thread 0x7fdad7d3d700 (LWP 8003)):
#0  0x7fdbb67990af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fdbb768065b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fdaf9e0242f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fdaf9e05dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fdaf9e05e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fdaf9e05e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fdaf9e05e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fdaf9e05e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7fdaf9e05e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7fdaf9e05e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7fdaf9e03a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7fdbb767f9e9 in  () at /usr/lib64/libQt5Core.so.5
#19 0x7fdbb6794734 in start_thread () at /lib64/libpthread.so.0
#20 0x7fdbb6f93d3d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7fdad853e700 (LWP 8002)):
#0  0x7fdbb67990af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fdbb768065b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fdaf9e0242f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fdaf9e05dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fdaf9e05e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fdaf9e03a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fdbb767f9e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fdbb6794734 in start_thread () at /lib64/libpthread.so.0
#10 0x7fdbb6f93d3d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7fdad8d3f700 (LWP 8001)):
#0  0x7fdbb67990af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fdbb768065b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fdaf9e0242f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fdaf9e05dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fdaf9e0045b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fdaf9e05e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fdaf9e0045b in

[digikam] [Bug 375390] "Set as Tag Thumbnail" in Tag View doesn't work.

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Platform|Kubuntu Packages|Appimage

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

[kteatime] [Bug 375383] kteatime system tray icon looks more like oxygen than breeze

[Marco Parillo]

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

--- Comment #1 from Marco Parillo  ---
In Kubuntu ZZ, it is version 1.3 Using:
KDE Frameworks 5.28.0
Qt 5.7.1 (built against 5.6.1)
The xcb windowing system

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

[digikam] [Bug 375357] No video preview

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
Your error messages are normal for videos. The video thumbnailer is not yet
called. Please post a longer section of the log.

Maik

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

[frameworks-kconfig] [Bug 375392] KConfig 5.3.0 do not compile with Macports under OSX Yosemite

[bugzilla_noreply]

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

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

   What|Removed |Added

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

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

[frameworks-kconfig] [Bug 375392] New: KConfig 5.3.0 do not compile with Macports under OSX Yosemite

[bugzilla_noreply]

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

Bug ID: 375392
   Summary: KConfig 5.3.0 do not compile with Macports under OSX
Yosemite
   Product: frameworks-kconfig
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matt...@mjdsystems.ca
  Reporter: caulier.gil...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

5.29 compile fine with same environnement.
Compile trace is given below :

-- extracting...

src='/Users/gilles/Devel/5.x/project/bundles/macports/temp.dwnld/kconfig-5.30.0.tar.xz'

dst='/Users/gilles/Devel/5.x/project/bundles/macports/temp.build/ext_kf5/ext_kconfig-prefix/src/ext_kconfig'
-- extracting... [tar xfz]
-- extracting... [analysis]
-- extracting... [rename]
-- extracting... [clean up]
-- extracting... done
[  0%] Performing patch step for 'ext_kconfig'
[ 33%] No update step for 'ext_kconfig'
[ 33%] Performing configure step for 'ext_kconfig'
Installing to /opt/digikam for target x86_64 with build mode debug
-- The C compiler identification is AppleClang 6.1.0.6020053
-- The CXX compiler identification is AppleClang 6.1.0.6020053
-- Check for working C compiler:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- 

-- Looking for __GLIBC__
-- Looking for __GLIBC__ - not found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Could not set up the appstream test. appstreamcli is missing.
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- 
-- The following REQUIRED packages have been found:

 * ECM (required version >= 5.30.0) , Extra CMake Modules. ,

 * Qt5 (required version >= 5.5.0)
 * Qt5Gui (required version >= 5.5.0)
 * Qt5Xml (required version >= 5.5.0)
 * Qt5Core (required version >= 5.5.0)
 * Qt5LinguistTools

-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

DIGIKAMSC_CHECKOUT_DOC
DIGIKAMSC_CHECKOUT_PO
DIGIKAMSC_COMPILE_DIGIKAM
DIGIKAMSC_COMPILE_DOC
DIGIKAMSC_COMPILE_KIPIPLUGINS
DIGIKAMSC_COMPILE_LIBKIPI
DIGIKAMSC_COMPILE_LIBKSANE
DIGIKAMSC_COMPILE_LIBKVKONTAKTE
DIGIKAMSC_COMPILE_LIBMEDIAWIKI
DIGIKAMSC_COMPILE_PO
ENABLE_AKONADICONTACTSUPPORT
ENABLE_APPSTYLES
ENABLE_DBUS
ENABLE_INTERNALMYSQL
ENABLE_KFILEMETADATASUPPORT
ENABLE_KIO
ENABLE_MEDIAPLAYER
ENABLE_MYSQLSUPPORT
ENABLE_OPENCV3
QT_LIBRARY_DIR
QT_QMAKE_EXECUTABLE
QT_QT_INCLUDE_DIR


-- Build files have been written to:
/Users/gilles/Devel/5.x/project/bundles/macports/temp.build/ext_kf5/ext_kconfig-prefix/src/ext_kconfig/build
[ 66%] Performing build step for 'ext_kconfig'
make[4]: warning: jobserver unavailable: using -j1.  Add `+' to parent make
rule.
Scanning dependencies of target translations_60
[  0%] Generating nn/kconfig5_qt.qm
[  0%] Built target translations_60
Scanning dependencies of target translations_63
[  0%] Generating pl/kconfig5_qt.qm
[  0%] Built target translations_63
Scanning dependencies of target translations_30
[  1%] Generating gl/kconfig5_qt.qm
[  1%] Built target translations_30
Scanning dependencies of target translations_12
[  1%] Generating ca@valencia/kconfig5_qt.qm
[  1%] Built target translations_12
Scanning dependencies of target translations_43
[  1%] Generating kk/kconfig5_qt.qm
[  1%] Built target translations_43
Scanning dependencies of target translations_86
[  2%] Generating uz@cyrillic/kconfig5_qt.qm
[  2%] Built target translations_86
Scanning dependencies of target translations_66
[  2%] Generating ro/kconfig5_qt.qm
[  2%] Built target translations_66
Scanning dependencies of target translations_90
[  2%] Generating zh_CN/kconfig5_qt.qm
[  2%] Built target translations_90
Scanning 

[digikam] [Bug 374313] wrong icon usage revisited [patch]

[bugzilla_noreply]

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

--- Comment #45 from caulier.gil...@gmail.com ---
Simon,

I don't understand why it do not work for you in 64 bits shared.

I recommend to post a dile in MXE bugzilla. The team respond quickly in
general...

Gilles

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

[digikam] [Bug 374313] wrong icon usage revisited [patch]

[bugzilla_noreply]

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

--- Comment #44 from caulier.gil...@gmail.com ---
No problem to build and link lensfun with MXE 64 bits :

[100%] Built target ext_opencv
== Using MXE wrapper:
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/bin/x86_64-w64-mingw32.shared-cmake
== Skip using MXE toolchain:
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/x86_64-w64-mingw32.shared/share/cmake/mxe-conf.cmake
Scanning dependencies of target ext_lensfun
[ 50%] Performing before_download step for 'ext_lensfun'
[ 50%] Creating directories for 'ext_lensfun'
WARNING: timestamping does nothing in combination with -O. See the manual
for details.

--2017-01-21 19:54:28-- 
http://downloads.sourceforge.net/project/lensfun/0.3.2/lensfun-0.3.2.tar.gz
Resolving downloads.sourceforge.net (downloads.sourceforge.net)...
216.34.181.59
Connecting to downloads.sourceforge.net
(downloads.sourceforge.net)|216.34.181.59|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
https://vorboss.dl.sourceforge.net/project/lensfun/0.3.2/lensfun-0.3.2.tar.gz
[following]
--2017-01-21 19:54:29-- 
https://vorboss.dl.sourceforge.net/project/lensfun/0.3.2/lensfun-0.3.2.tar.gz
Resolving vorboss.dl.sourceforge.net (vorboss.dl.sourceforge.net)...
5.10.152.194
Connecting to vorboss.dl.sourceforge.net
(vorboss.dl.sourceforge.net)|5.10.152.194|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 784825 (766K) [application/x-gzip]
Saving to:
‘/mnt/devel/GIT/5.x/project/bundles/mxe/temp.dwnld/lensfun-0.3.2.tar.gz’

 0K .. .. .. .. ..  6%  228K 3s
50K .. .. .. .. .. 13%  443K 2s
   100K .. .. .. .. .. 19% 86.6K 4s
   150K .. .. .. .. .. 26%  158K 3s
   200K .. .. .. .. .. 32%  658K 3s
   250K .. .. .. .. .. 39% 92.4K 3s
   300K .. .. .. .. .. 45% 52.3K 3s
   350K .. .. .. .. .. 52%  367K 3s
   400K .. .. .. .. .. 58% 69.7K 3s
   450K .. .. .. .. .. 65%  640K 2s
   500K .. .. .. .. .. 71% 88.2K 2s
   550K .. .. .. .. .. 78%  328K 1s
   600K .. .. .. .. .. 84% 50.3K 1s
   650K .. .. .. .. .. 91%  600K 1s
   700K .. .. .. .. .. 97% 40.6K 0s
   750K .. .. 100% 2.07M=6.8s

2017-01-21 19:54:39 (113 KB/s) -
‘/mnt/devel/GIT/5.x/project/bundles/mxe/temp.dwnld/lensfun-0.3.2.tar.gz’ saved
[784825/784825]

[ 50%] Performing download step (verify and extract) for 'ext_lensfun'
-- verifying file...

file='/mnt/devel/GIT/5.x/project/bundles/mxe/temp.dwnld/lensfun-0.3.2.tar.gz'
-- verifying file... done
-- extracting...

src='/mnt/devel/GIT/5.x/project/bundles/mxe/temp.dwnld/lensfun-0.3.2.tar.gz'

dst='/mnt/devel/GIT/5.x/project/bundles/mxe/temp.build/ext_lensfun/ext_lensfun-prefix/src/ext_lensfun'
-- extracting... [tar xfz]
-- extracting... [analysis]
-- extracting... [rename]
-- extracting... [clean up]
-- extracting... done
[100%] No update step for 'ext_lensfun'
[100%] Performing patch step for 'ext_lensfun'
patching file CMakeLists.txt
[100%] Performing configure step for 'ext_lensfun'
MXE target : 64 bits shared
Installing to /mnt/devel/GIT/5.x/project/bundles/mxe/build.win64 for target
x86_64-w64-mingw32.shared with build mode RelWithDebInfo and configure options
-DBUILD_TESTING=false
== Using MXE wrapper:
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/bin/x86_64-w64-mingw32.shared-cmake
== Using MXE toolchain:
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/x86_64-w64-mingw32.shared/share/cmake/mxe-conf.cmake
== Using MXE runresult:
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/share/cmake/modules/TryRunResults.cmake
loading initial cache file
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/share/cmake/modules/TryRunResults.cmake
-- The C compiler identification is GNU 4.9.4
-- The CXX compiler identification is GNU 4.9.4
-- Check for working C compiler:
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/bin/x86_64-w64-mingw32.shared-gcc
-- Check for working C compiler:
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/bin/x86_64-w64-mingw32.shared-gcc
-- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler:
/mnt/devel/GIT/5.x/project/bundles/mxe/build.win64/usr/bin/x86_64-w64-mingw32.shared-g++
-- Check for working CXX compiler:

[kmymoney4] [Bug 375391] Kmymoney crashes after attempting to create new account

[bob]

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

--- Comment #1 from b...@mroczka.com  ---
Here is an alternate stack dump showing a bit more debug symbols.

Application: KMyMoney (kmymoney), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f986f7cf900 (LWP 9987))]

Thread 2 (Thread 0x7f98540ef700 (LWP 10017)):
#0  0x7f9865096992 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9865096aec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f986ab2022e in QEventDispatcherGlib::processEvents
(this=0x7f984c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#3  0x7f986aaee12f in QEventLoop::processEvents
(this=this@entry=0x7f98540eec80, flags=...) at kernel/qeventloop.cpp:149
#4  0x7f986aaee495 in QEventLoop::exec (this=this@entry=0x7f98540eec80,
flags=...) at kernel/qeventloop.cpp:204
#5  0x7f986a9dd549 in QThread::exec (this=this@entry=0x5583d7f31f50) at
thread/qthread.cpp:538
#6  0x7f986aace1c3 in QInotifyFileSystemWatcherEngine::run
(this=0x5583d7f31f50) at io/qfilesystemwatcher_inotify.cpp:265
#7  0x7f986a9dfe3c in QThreadPrivate::start (arg=0x5583d7f31f50) at
thread/qthread_unix.cpp:352
#8  0x7f986557f6ca in start_thread (arg=0x7f98540ef700) at
pthread_create.c:333
#9  0x7f98699350af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f986f7cf900 (LWP 9987)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x7f98698643ea in __GI_abort () at abort.c:89
#8  0x7f986985abb7 in __assert_fail_base (fmt=,
assertion=assertion@entry=0x7f9851e99385 "buffer",
file=file@entry=0x7f9851e7d56b "buffer.c", line=line@entry=1017,
function=function@entry=0x7f9851e79b00 "GWEN_Buffer_AppendString") at
assert.c:92
#9  0x7f986985ac62 in __GI___assert_fail (assertion=0x7f9851e99385
"buffer", file=0x7f9851e7d56b "buffer.c", line=1017, function=0x7f9851e79b00
"GWEN_Buffer_AppendString") at assert.c:101
#10 0x7f9851dddcdf in GWEN_Buffer_AppendString () from
/usr/lib/libgwenhywfar.so.60
#11 0x7f9851729e41 in AB_Job_new (jt=jt@entry=AB_Job_TypeTransfer,
a=a@entry=0x5583d8e7d4c0) at job.c:85
#12 0x7f985173223d in AB_JobSingleTransfer_new (a=a@entry=0x5583d8e7d4c0)
at jobsingletransfer.c:28
#13 0x7f98520e172e in KBankingPlugin::availableJobs (this=0x5583d8e7d830,
accountId=...) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/mymoneybanking.cpp:632
#14 0x7f986db44c7b in onlineJobAdministration::canSendCreditTransfer
(this=0x7f986ddb2380 ) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/onlinejobadministration.cpp:311
#15 0x5583d4ecc9d0 in KMyMoneyApp::slotUpdateActions
(this=this@entry=0x5583d77aa980) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:6407
#16 0x5583d4ed203e in KMyMoneyApp::slotSelectAccount
(this=this@entry=0x5583d77aa980, obj=...) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:6923
#17 0x5583d4f1b55a in KMyMoneyApp::qt_static_metacall (_o=0x5583d77aa980,
_c=, _id=, _a=0x7ffdf66a8640) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/moc_kmymoney.cpp:605
#18 0x7f986ab03f70 in QMetaObject::activate
(sender=sender@entry=0x5583d7d30ff0, m=m@entry=0x5583d5738e40
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdf66a8640)
at kernel/qobject.cpp:3567
#19 0x5583d4f82cb2 in KAccountsView::selectObject
(this=this@entry=0x5583d7d30ff0, _t1=...) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/views/moc_kaccountsview.cpp:161
#20 0x5583d4f8c500 in KAccountsView::slotTabCurrentChanged
(this=this@entry=0x5583d7d30ff0, index=) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/views/kaccountsview.cpp:198
#21 0x5583d4f8d918 in KAccountsView::slotLoadAccounts
(this=this@entry=0x5583d7d30ff0) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/views/kaccountsview.cpp:168
#22 0x5583d4f83e68 in KAccountsView::qt_static_metacall (_o=0x5583d7d30ff0,
_c=, _id=4, _a=0x7ffdf66a8b40) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/views/moc_kaccountsview.cpp:94
#23 0x7f986ab03f70 in QMetaObject::activate
(sender=sender@entry=0x7f986ddb1c80 ,
m=m@entry=0x7f986ddaf960 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3567
#24 0x7f986db49b00 in MyMoneyFile::dataChanged
(this=this@entry=0x7f986ddb1c80 ) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/mymoney/moc_mymoneyfile.cpp:112
#25 0x7f986dac8b2c in MyMoneyFile::commitTransaction
(this=this@entry=0x7f986ddb1c80 ) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/mymoneyfile.cpp:446
#26 0x7f986dac8cc5 in MyMoneyFileTransaction::commit
(this=this@entry=0x7ffdf66a8c20) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/mymoneyfile.cpp:3227
#27 

[Discover] [Bug 375083] Plasma Crashes on opening.

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[Discover] [Bug 375083] Plasma Crashes on opening.

[Aleix Pol]

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

--- Comment #5 from Aleix Pol  ---
Looks reproducible in Neon, if somebody can provide a backtrace with debug
symbols that would be great.

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

[Discover] [Bug 375371] Segmentation fault on dev version

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[Discover] [Bug 375083] Plasma Crashes on opening.

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||kont...@soee.pl

--- Comment #4 from Aleix Pol  ---
*** Bug 375371 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 375291] Crash when closing disover

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[Discover] [Bug 375083] Plasma Crashes on opening.

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||kde...@gmail.com

--- Comment #3 from Aleix Pol  ---
*** Bug 375352 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 375352] Discover crashes when clicking on the Applications section/panel

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[Discover] [Bug 375083] Plasma Crashes on opening.

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||michaelmarott...@gmail.com

--- Comment #2 from Aleix Pol  ---
*** Bug 375052 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 375052] discover crashes upon start

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Aleix Pol  ---


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

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

[Discover] [Bug 375083] Plasma Crashes on opening.

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||palette...@hotmail.com

--- Comment #1 from Aleix Pol  ---
*** Bug 375291 has been marked as a duplicate of this bug. ***

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

[kmymoney4] [Bug 375391] New: Kmymoney crashes after attempting to create new account

[bob]

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

Bug ID: 375391
   Summary: Kmymoney crashes after attempting to create new
account
   Product: kmymoney4
   Version: 4.8.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: b...@mroczka.com
  Target Milestone: ---

Application: kmymoney (4.8.0)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.8.0-32-generic x86_64
Distribution: Ubuntu 16.10

-- Information about the crash:
I tried creating a new credit card account but after clicking OK after its
shows the account summary the application crashes.  Same thing occurs if I try
to create a checking account.

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f63b034a900 (LWP 4279))]

Thread 2 (Thread 0x7f6394c6a700 (LWP 4280)):
#0  0x7f63aa49fc8d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f63a5c55c60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f63a5c11485 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f63a5c11974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f63a5c11aec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f63ab69b22e in QEventDispatcherGlib::processEvents
(this=0x7f6398c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f63ab66912f in QEventLoop::processEvents
(this=this@entry=0x7f6394c69c80, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f63ab669495 in QEventLoop::exec (this=this@entry=0x7f6394c69c80,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f63ab558549 in QThread::exec (this=this@entry=0x55f593264c50) at
thread/qthread.cpp:538
#9  0x7f63ab6491c3 in QInotifyFileSystemWatcherEngine::run
(this=0x55f593264c50) at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f63ab55ae3c in QThreadPrivate::start (arg=0x55f593264c50) at
thread/qthread_unix.cpp:352
#11 0x7f63a60fa6ca in start_thread (arg=0x7f6394c6a700) at
pthread_create.c:333
#12 0x7f63aa4b00af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f63b034a900 (LWP 4279)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x7f63aa3df3ea in __GI_abort () at abort.c:89
#8  0x7f63aa3d5bb7 in __assert_fail_base (fmt=,
assertion=assertion@entry=0x7f638e9dd385 "buffer",
file=file@entry=0x7f638e9c156b "buffer.c", line=line@entry=1017,
function=function@entry=0x7f638e9bdb00 "GWEN_Buffer_AppendString") at
assert.c:92
#9  0x7f63aa3d5c62 in __GI___assert_fail (assertion=0x7f638e9dd385
"buffer", file=0x7f638e9c156b "buffer.c", line=1017, function=0x7f638e9bdb00
"GWEN_Buffer_AppendString") at assert.c:101
#10 0x7f638e921cdf in GWEN_Buffer_AppendString () from
/usr/lib/libgwenhywfar.so.60
#11 0x7f638e26de41 in ?? () from /usr/lib/libaqbanking.so.35
#12 0x7f638ec2572e in KBankingPlugin::availableJobs (this=0x55f5941b0040,
accountId=...) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/mymoneybanking.cpp:632
#13 0x7f63ae6bfc7b in onlineJobAdministration::canSendCreditTransfer
(this=0x7f63ae92d380 ) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/onlinejobadministration.cpp:311
#14 0x55f5919299d0 in KMyMoneyApp::slotUpdateActions
(this=this@entry=0x55f592addc40) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:6407
#15 0x55f59192f03e in KMyMoneyApp::slotSelectAccount
(this=this@entry=0x55f592addc40, obj=...) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:6923
#16 0x55f59197855a in KMyMoneyApp::qt_static_metacall (_o=0x55f592addc40,
_c=, _id=, _a=0x7ffc05acc7c0) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/moc_kmymoney.cpp:605
#17 0x7f63ab67ef70 in QMetaObject::activate
(sender=sender@entry=0x55f593063880, m=m@entry=0x55f592195e40
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc05acc7c0)
at kernel/qobject.cpp:3567
#18 0x55f5919dfcb2 in KAccountsView::selectObject
(this=this@entry=0x55f593063880, _t1=...) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/views/moc_kaccountsview.cpp:161
#19 0x55f5919e9500 in KAccountsView::slotTabCurrentChanged
(this=this@entry=0x55f593063880, index=) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/views/kaccountsview.cpp:198
#20 0x55f5919ea918 in KAccountsView::slotLoadAccounts
(this=this@entry=0x55f593063880) at
/build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/views/kaccountsview.cpp:168
#21 0x55f5919e0e68 in KAccountsView::qt_static_metacall (_o=0x55f593063880,

[dolphin] [Bug 366203] Information panel: scroll bar has ugly background

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dol
   ||phin/c1d9becda259c0df58b144
   ||7b69f573b6ef13bfa1
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||16.12.2

--- Comment #3 from Elvis Angelaccio  ---
Git commit c1d9becda259c0df58b1447b69f573b6ef13bfa1 by Elvis Angelaccio.
Committed on 21/01/2017 at 22:38.
Pushed by elvisangelaccio into branch 'Applications/16.12'.

informationpanel: don't change color of scrollarea's viewport

This code was added a long time ago in b1c9b5126d, but the commit
message doesn't explain why. If we remove it nothing seems to change and
we fix the ugly background on the scrollbar when Breeze draws a frame
around dockable panels.
FIXED-IN: 16.12.2
REVIEW: 129861

M  +0-4src/panels/information/informationpanelcontent.cpp

https://commits.kde.org/dolphin/c1d9becda259c0df58b1447b69f573b6ef13bfa1

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

[kdenlive] [Bug 373972] Press render choose options, no video in file, just audio

[DAVE]

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

--- Comment #5 from DAVE  ---
I have the issue solved now, Thanks.

I went into render settings and set it to render video also.

I do think an update caused this issue, as it always worked great before that
update

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

[kajongg] [Bug 375385] Kajongg does not load its translation catalog from local install folder

[Burkhard Lueck]

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

--- Comment #4 from Burkhard Lueck  ---
(In reply to Wolfgang Rohdewald from comment #2)
> Maybe using the Qt translations path might help. If you apply the following
> patch to master and start kajongg from shell, it will print that path. For
> me, that is 
> 
> Qt translation path:/usr/share/qt5/translations
> 
Here it is (local installation of 5.6.1)
/home/kdeframeworks/Qt5.6.1/5.6/Src/qttranslations/translations/

Use the dirs you get with
"$ qtpaths --paths GenericDataLocation
/home/kdeframeworks/.local5:/home/kdeframeworks/kf5/share:/usr/share"
to search for locale/[LANG]/LC_MESSAGES/kajongg.po 
(or kajongg_qt.qm for qt translation system)
and you will pick up the correct catalog - first user install, second system
install


> Is there a formal method to compute the correct KF5 .mo path from this one?
> But that will probably only help if you also build qt5 in the same local
> install folder. Is that the standard case when building kf5?
> 
No, see above

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

[gwenview] [Bug 367868] Animated GIFs playback too slow

[Gustavo Alvarez]

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

--- Comment #3 from Gustavo Alvarez  ---
any notice of this?

still have this issue in gwenview stable 16.12.1

greetings

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

[kwin] [Bug 375369] Decorations crash when change theme

[bugzilla_noreply]

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

--- Comment #2 from francisco.dominguez.le...@gmail.com ---
(In reply to Martin Gräßlin from comment #1)
> Please provide output of
> qdbus org.kde.KWin /KWin supportInformation

Version
===
KWin version: 5.8.5
Qt Version: 5.7.1
Qt compile version: 5.7.1
XCB compile version: 1.12

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11901000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.breeze
Theme: 
Blur: 0
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Options
===
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
colorCorrected: false
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: false
glStrictBindingFollowsDriver: true
glCoreProfile: false
glPreferBufferSwap: 0
glPlatformInterface: 1
windowsBlockCompositing: true

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Multi-Head: no
Active screen follows mouse:  no
Number of Screens: 1

Screen 0:
-
Name: HDMI-0
Geometry: 0,0,1920x1080
Refresh Rate: 60


Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 660/PCIe/SSE2
OpenGL version string: 4.5.0 NVIDIA 375.26
OpenGL platform interface: GLX
OpenGL shading language version string: 4.50 NVIDIA
Driver: NVIDIA
Driver version: 375.26
GPU class: Unknown
OpenGL version: 4.5
GLSL version: 4.50
X server version: 1.19.1
Linux kernel version: 4.4.41
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---
zoom
slidingpopups
kwin4_effect_login
slide
screenshot
kwin4_effect_windowaperture
minimizeanimation
kwin4_effect_translucency
desktopgrid
kwin4_effect_maximize
kwin4_effect_morphingpopups
kwin4_effect_fade
kwin4_effect_dialogparent
presentwindows
highlightwindow
blur
contrast
startupfeedback
screenedge
kscreen

Currently Active Effects:
-
kwin4_effect_fade
blur
contrast

Effect Settings:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1

slidingpopups:
fadeInTime: 150
fadeOutTime: 250

kwin4_effect_login:

slide:

screenshot:

kwin4_effect_windowaperture:

minimizeanimation:

kwin4_effect_translucency:

desktopgrid:
zoomDuration: 300
border: 10
desktopNameAlignment: 0
layoutMode: 0
customLayoutRows: 2
usePresentWindows: true

kwin4_effect_maximize:

kwin4_effect_morphingpopups:

kwin4_effect_fade:

kwin4_effect_dialogparent:

presentwindows:
layoutMode: 0
showCaptions: true
showIcons: true
doNotCloseWindows: false
ignoreMinimized: false
accuracy: 20
fillGaps: true
fadeDuration: 150
showPanel: false

[krita] [Bug 375217] Render Animation silently fails to export with 32bit float depth.

[wolthera]

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

--- Comment #5 from wolthera  ---
Oh, for your other question. We've found the problem, but are kind of wondering
what is friendliest way to solve it.

32bit float images need some color management to display and convert right.
Krita has all that, but ffmpeg doesn't. So if we export exr to ffmpeg, we give
supersmooth colors, but ffmpeg will make the colors way too dark because it
cannot do that color management.

So we can also try to convert it down to 8bit, but then ffmpeg cannot make the
super-smooth colors go into the file(though the maximum any video format can
have is 10bit per channel... That's about a billion). But, that might be
accetable? Because poeple who need to use 32bit float might be quite smart
people who might prefer to use the exrs to render in another program. The
render they do in Krita might just be tiny example videos.

So we're trying to choose between these two.

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

[digikam] [Bug 375345] App icon doesn't appear in the Unity Dash

[Dan Dascalescu]

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

--- Comment #5 from Dan Dascalescu  ---
I already have Kate installed, and when I launched the new Kate appimage, it
didn't prompt for anything. The appimage used the same Unity launcher icon as
the installed Kate, so I'm not sure how useful my setup/test is.

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

[krita] [Bug 375217] Render Animation silently fails to export with 32bit float depth.

[wolthera]

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

--- Comment #4 from wolthera  ---
Well, I am somewhat surprised that you need 32bit float per channel, 8bit
integer per channel is the maximum 90% of all computers can show at all...

The discolouration might be caused by converting from a linear to a
gamma-corrected colorspace, which changes the result of layer blending. You can
try merging all layers together before converting to avoid that type of change.

People often confuse 8bit per channel with 8bit color in total. The latter is
like the maximum colors gif can have, 2^8=256. But 8bit per channel is that per
color channel, so for RGBA, that is 4 channels, 8*4=32 so the total amount of
colors in a 8bit per channel image is 2^32, which is a bit more than 16
million, and quite a bit more than 256 colors. :)

32bit float per channel then is 32*4=128, so it's 2^128 colors, which is kinda
a lot.

You can use applications like blender to render exrs to video files, but unless
you are doing specialised things with mixing colors, you should not be needing
32bit float per channel. I am telling you this because it can make your files
super-big. It's like, the type of color quality used for Hollywood movies, it
seems a bit odd to use it for small gifs :D

There's more on it in the manual:
https://docs.krita.org/Bit_Depth
https://docs.krita.org/Gamma_and_Linear
https://docs.krita.org/Color_Managed_Workflow#Exporting

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

[kajongg] [Bug 375385] Kajongg does not load its translation catalog from local install folder

[Burkhard Lueck]

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

--- Comment #3 from Burkhard Lueck  ---
(In reply to Wolfgang Rohdewald from comment #1)
> I  have no idea how to find the correct path for .mo files. Right now
> /usr/local/share/locale and /usr/share/locale are hard coded.
> 
> Does kf5-config --path locale return the correct path for you?
> 
> But - I have not been able to find the source code for kf5-config. Can you
> give me a hint?
> 
Forget kf5-config, it is in frameworks/kdelibs4support/, therefore deprecated

> Please remember that this is Python and there are currently no usable KF5
> bindings for Python, so I cannot simply use KF5 classes - I have to simulate
> what they do. This will never be perfect, but right now at least it should
> work for standard installations.
> 
asked on #kde-games about kf5 python bindings when kajongg switched to kf5 and
got these replies:
[Dienstag, 17. Januar 2017] [22:14:38 CET]  looks like they were
added after 5.30:
https://cgit.kde.org/ki18n.git/commit/?id=ff1e3a6f3e916ebc70288459c55c1145d413f55f
[Dienstag, 17. Januar 2017] [22:15:08 CET]  no clue how functional
they are

But why use ki18n when there are no python bindings for it?
Beside frameworks we have some application using qt translation system:
zanshin, kcachegrind, marble, step, gcompris and all of them are fully
translated in my system with a user installation

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

[digikam] [Bug 375390] New: "Set as Tag Thumbnail" in Tag View doesn't work.

[Wolfgang Scheffner]

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

Bug ID: 375390
   Summary: "Set as Tag Thumbnail" in Tag View doesn't work.
   Product: digikam
   Version: 5.5.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: wscheffn...@gmail.com
  Target Milestone: ---

Whether you drag an image onto a tag in the Left Sidebar or choose "Set as Tag
Thumbnail" from the context menu on an Icon in the Image Area nothing happens.
The only way to set an image as tag thumbnail is via the tag properties with
the "Selct Icon" dialog, but only if it is png.

Reproducible: always

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

[kajongg] [Bug 375385] Kajongg does not load its translation catalog from local install folder

[Wolfgang Rohdewald]

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

--- Comment #2 from Wolfgang Rohdewald  ---
Maybe using the Qt translations path might help. If you apply the following
patch to master and start kajongg from shell, it will print that path. For me,
that is 

Qt translation path:/usr/share/qt5/translations

Is there a formal method to compute the correct KF5 .mo path from this one?
But that will probably only help if you also build qt5 in the same local
install folder. Is that the standard case when building kf5?

diff --git a/src/kdestub.py b/src/kdestub.py
index aeefa25c..772581b9 100644
--- a/src/kdestub.py
+++ b/src/kdestub.py
@@ -211,6 +211,7 @@ class KApplication(QApplication):

 def initQtTranslator(self):
 """load translators using Qt .qm files"""
+print('Qt translation
path:{}'.format(QLibraryInfo.location(QLibraryInfo.TranslationsPath)))
 for language in
reversed(list(MLocale.extendRegionLanguages(KGlobal.currentLanguages(:
 self.installTranslatorFile(os.path.join(
 QLibraryInfo.location(QLibraryInfo.TranslationsPath),
'qtbase_{}.qm'.format(language)))

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

[kajongg] [Bug 375385] Kajongg does not load its translation catalog from local install folder

[Wolfgang Rohdewald]

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

Wolfgang Rohdewald  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||wolfg...@rohdewald.de
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Wolfgang Rohdewald  ---
I  have no idea how to find the correct path for .mo files. Right now
/usr/local/share/locale and /usr/share/locale are hard coded.

Does kf5-config --path locale return the correct path for you?

But - I have not been able to find the source code for kf5-config. Can you give
me a hint?

Please remember that this is Python and there are currently no usable KF5
bindings for Python, so I cannot simply use KF5 classes - I have to simulate
what they do. This will never be perfect, but right now at least it should work
for standard installations.



*qt.pm are a different case:
1. using QLibraryInfo.location(QLibraryInfo.TranslationsPath),
'qtbase_{}.qm'.format(language)))
2. qtpaths does not seem to return that path at all  (see qtpaths --types)
3. kajongg does actually load *.qm but makes no use of them because KDE has
support for many more languages and until now I found no place where kajongg
actually needs them. Will remove loading *.qm. (see commits 9c429f29 and
8b98952)

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

[kwin] [Bug 375389] New: Kwin chrashes when adding new album

[Peter Wendel]

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

Bug ID: 375389
   Summary: Kwin chrashes when adding new album
   Product: kwin
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: p...@thefan1968.de
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.36-8-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
I use two screens.

Kwin chrashes when clicking on add ne album in digiKam

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7f81a5d31700 (LWP 14351)):
#0  0x7f81c7e24b03 in select () at /lib64/libc.so.6
#1  0x7f81c54e0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f81c54e20c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f81c54e2527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f81c5491fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f81c52ccf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f81bfe669b8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f81c52d19e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f81c80f2734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f81c7e2bd3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f8197f4f700 (LWP 2990)):
#0  0x7f81c80f70af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f81c445593b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f81c4455969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f81c80f2734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f81c7e2bd3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f81a5041700 (LWP 2754)):
#0  0x7f81c7e24b03 in select () at /lib64/libc.so.6
#1  0x7f81c54e0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f81c54e20c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f81c54e2527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f81c5491fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f81c52ccf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f81bfe669b8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f81c52d19e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f81c80f2734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f81c7e2bd3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f81a7379700 (LWP 2734)):
#0  0x7f81c7e24b03 in select () at /lib64/libc.so.6
#1  0x7f81c54e0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f81c54e20c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f81c54e2527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f81c5491fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f81c52ccf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f81bf0391d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f81c52d19e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f81c80f2734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f81c7e2bd3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f81ad549700 (LWP 2726)):
#0  0x7f81c7e2349d in poll () at /lib64/libc.so.6
#1  0x7f81c6fa53e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f81c6fa6fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f81ae643839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f81c52d19e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f81c80f2734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f81c7e2bd3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f81c86c6940 (LWP 2725)):
[KCrash Handler]
#6  0x7f81bfe52dd0 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/usr/lib64/libQt5Qml.so.5
#7  0x7f81bfe5424a in
QQmlBinding::update(QFlags) () at
/usr/lib64/libQt5Qml.so.5
#8  0x7f81bfe5d2f6 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f81bfdeb93b in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5
#10 0x7f81bfdeb9f7 in QQmlComponentPrivate::completeCreate() () at
/usr/lib64/libQt5Qml.so.5
#11 0x7f81bfdeb880 in 

[krita] [Bug 375217] Render Animation silently fails to export with 32bit float depth.

[bugzilla_noreply]

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

--- Comment #3 from ninpi...@gmail.com ---
(In reply to wolthera from comment #2)
> Ok, a bit of an update.
> 
> 1. exr frame export saves odd. It saves as frame.*.exr and so on. This
> is silly.
> 
> 2. While ffmpeg can do all the tricks with exr that it can with png, it does
> NOT take into account that exr files are always linear encoded, so the
> colors are off. We might be better warning the user that we will
> automatically convert to 8bit, and that if they want higher quality output
> they'll need to use external software.

Okay, so I tried to make an animation with the same dimensions as before, but
with 8-Bit Float depth. And it was a success!!! I was able to render the
animation as a .GIF as well as a .MP4 file (the mp4 was actually smaller in
memory size)! ^^ Albeit, I believe there was a slight discoloration like you
said. What is it you mean by "external software"? Is there a way to make the
animation render with proper colour? Is that the current mystery undergoing
investigation?

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

[plasmashell] [Bug 375388] plasmashell segfault when clicking hamburger icon on desktop, widgets locked

[Piotr Kloc]

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

--- Comment #1 from Piotr Kloc  ---
Same issue after logging off:

So it seems that it really doesn't matter if I unlock widgets, still happens.
Cool thing that yakuake is on standby.



Application: Plazma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa33613e800 (LWP 1531))]

Thread 7 (Thread 0x7fa2804d8700 (LWP 1662)):
#0  0x7fa32a65add4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fa32a614c7c in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fa32a6156ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fa32a61589c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fa3301113eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fa3300bac1a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fa32fedc9f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fa333bccfd6 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7fa32fee1658 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fa32edac454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fa32f7f67df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fa30bfff700 (LWP 1655)):
#0  0x7fa32edb210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa3358c2244 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fa3358c2289 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fa32edac454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa32f7f67df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fa315d6e700 (LWP 1646)):
#0  0x7fa32f7ed48d in poll () at /usr/lib/libc.so.6
#1  0x7fa32a615786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa32a61589c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa3301113eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa3300bac1a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa32fedc9f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa333017e75 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fa32fee1658 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa32edac454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa32f7f67df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fa317dfa700 (LWP 1588)):
#0  0x7fa32a65adb9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fa32a614c95 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fa32a6156ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fa32a61589c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fa3301113eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fa3300bac1a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fa32fedc9f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fa333017e75 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7fa32fee1658 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fa32edac454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fa32f7f67df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fa31d9b9700 (LWP 1554)):
#0  0x7fa32f7ed48d in poll () at /usr/lib/libc.so.6
#1  0x7fa32a615786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa32a61589c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa3301113eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa3300bac1a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa32fedc9f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa330c610c5 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7fa32fee1658 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa32edac454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa32f7f67df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fa31f612700 (LWP 1546)):
#0  0x7fa32f7ed48d in poll () at /usr/lib/libc.so.6
#1  0x7fa3347e88e0 in  () at /usr/lib/libxcb.so.1
#2  0x7fa3347ea679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7fa321551239 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7fa32fee1658 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fa32edac454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fa32f7f67df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fa33613e800 (LWP 1531)):
[KCrash Handler]
#6  0x7fa333c77d06 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib/libQt5Quick.so.5
#7  0x7fa333c77dda in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib/libQt5Quick.so.5
#8  0x7fa333c77dda in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib/libQt5Quick.so.5
#9  0x7fa333c77f34 in QQuickItem::setVisible(bool) () at
/usr/lib/libQt5Quick.so.5
#10 0x7fa335bf54bc in  () at /usr/lib/libKF5PlasmaQuick.so.5
#11 

[plasmashell] [Bug 375388] New: plasmashell segfault when clicking hamburger icon on desktop, widgets locked

[Piotr Kloc]

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

Bug ID: 375388
   Summary: plasmashell segfault when clicking hamburger icon on
desktop, widgets locked
   Product: plasmashell
   Version: 5.8.95
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pepk...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.95)

Qt Version: 5.8.0
Frameworks Version: 5.30.0
Operating System: Linux 4.9.5-1-ck-ivybridge x86_64
Distribution (Platform): Archlinux Packages

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

I dedided to click hamburger icon on desktop, that one which was always in the
corner.
It crashed plasmashell with nice segfault, I've tried a couple of times and it
always ends with crash.

Unlocking and locking widgets seems to fix any issues, gotta relog and test.

qt 5.8 
plasma 5.8.95

The crash can be reproduced every time.

-- Backtrace:
Application: Plazma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fda2e36a800 (LWP 978))]

Thread 7 (Thread 0x7fd9786f7700 (LWP 989)):
#0  0x7fda27a1948d in poll () at /usr/lib/libc.so.6
#1  0x7fda22841786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fda2284189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fda2833d3eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fda282e6c1a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fda281089f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fda2bdf8fd6 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7fda2810d658 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fda26fd8454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fda27a227df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fda03fff700 (LWP 983)):
#0  0x7fda26fde10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fda2daee244 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fda2daee289 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fda26fd8454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fda27a227df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fda0df73700 (LWP 982)):
#0  0x7fda27a1948d in poll () at /usr/lib/libc.so.6
#1  0x7fda22841786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fda2284189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fda2833d3eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fda282e6c1a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fda281089f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fda2b243e75 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fda2810d658 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fda26fd8454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fda27a227df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fda0700 (LWP 981)):
#0  0x7fda27a154ed in read () at /usr/lib/libc.so.6
#1  0x7fda22885a10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fda22841235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fda22841724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fda2284189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fda2833d3eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fda282e6c1a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fda281089f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fda2b243e75 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7fda2810d658 in  () at /usr/lib/libQt5Core.so.5
#10 0x7fda26fd8454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7fda27a227df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fda15be5700 (LWP 980)):
#0  0x7fda27a154ed in read () at /usr/lib/libc.so.6
#1  0x7fda22885a10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fda22841235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fda22841724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fda2284189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fda2833d3eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fda282e6c1a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fda281089f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fda28e8d0c5 in  () at /usr/lib/libQt5DBus.so.5
#9  0x7fda2810d658 in  () at /usr/lib/libQt5Core.so.5
#10 0x7fda26fd8454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7fda27a227df in 

[kmail2] [Bug 375387] New: Crash after wrong recipient name while forwarding message

[Evgeny]

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

Bug ID: 375387
   Summary: Crash after wrong recipient name while forwarding
message
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: ydgins...@gmail.com
  Target Milestone: ---

Application: kmail (4.14.10)
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:
- What I was doing when the application crashed:

1. Forward message in body
2. Type "ivy" in recepient address
3. Switch to Russian layout

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f910ddb8700 (LWP 2148)):
#0  0x7f912e76403f in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9123e5d686 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f9123e5d6b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f912e7600a4 in start_thread (arg=0x7f910ddb8700) at
pthread_create.c:309
#4  0x7f91309616ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f90ccc25700 (LWP 2206)):
#0  0x7f912e76403f in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9123bcfe7d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f9123e851e6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f912e7600a4 in start_thread (arg=0x7f90ccc25700) at
pthread_create.c:309
#4  0x7f91309616ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f90c7bff700 (LWP 2211)):
#0  0x7f91309592bd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f912868bbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f912868bcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f9131fb40de in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f90c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f9131f85e6f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f90c7bfede0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f9131f86165 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f90c7bfede0, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f9131e830bf in QThread::exec() (this=) at
thread/qthread.cpp:538
#7  0x7f9131e8579f in QThreadPrivate::start(void*) (arg=0x27416f0) at
thread/qthread_unix.cpp:349
#8  0x7f912e7600a4 in start_thread (arg=0x7f90c7bff700) at
pthread_create.c:309
#9  0x7f91309616ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f90c4db3700 (LWP 4706)):
#0  0x7f91309592bd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f912868bbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f912868bcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f9131fb40de in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f90bc003380, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f9131f85e6f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f90c4db2da0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f9131f86165 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f90c4db2da0, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f9131e830bf in QThread::exec() (this=this@entry=0x66fdb70) at
thread/qthread.cpp:538
#7  0x7f9131f67783 in QInotifyFileSystemWatcherEngine::run()
(this=0x66fdb70) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f9131e8579f in QThreadPrivate::start(void*) (arg=0x66fdb70) at
thread/qthread_unix.cpp:349
#9  0x7f912e7600a4 in start_thread (arg=0x7f90c4db3700) at
pthread_create.c:309
#10 0x7f91309616ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f913365a800 (LWP 2126)):
[KCrash Handler]
#5  0x7f91308af0a7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#6  0x7f91308b0458 in __GI_abort () at abort.c:78
#7  0x7f9130ea0145 in __gnu_cxx::__verbose_terminate_handler() () at
/usr/lib64/libstdc++.so.6
#8  0x7f9130e9e2e6 in  () at /usr/lib64/libstdc++.so.6
#9  0x7f9130e9e313 in  () at /usr/lib64/libstdc++.so.6
#10 0x7f9130e9e586 in __cxa_rethrow () at /usr/lib64/libstdc++.so.6
#11 0x7f9131f86356 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffd1d8c0e90, flags=...) at kernel/qeventloop.cpp:218
#12 0x7f9131f8b5b9 in QCoreApplication::exec() () at

[Phonon] [Bug 375386] Hotplugged HDMI audio not available

[Saurav Sengupta]

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

Saurav Sengupta  changed:

   What|Removed |Added

Version|4.8.3   |unspecified

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

[Phonon] [Bug 375386] New: Hotplugged HDMI audio not available

[Saurav Sengupta]

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

Bug ID: 375386
   Summary: Hotplugged HDMI audio not available
   Product: Phonon
   Version: 4.8.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: saurav1@gmail.com
CC: myr...@kde.org, romain.per...@gmail.com
  Target Milestone: 4.8

KDE SC 5.8.5

On a Lenovo Ideapad 110-15ISK (80UD) the Intel HDMI port operates by
hotplugging. However, connecting a TV does not make the HDMI audio output
available, although the video works. The laptop's own speaker output continues
to function. Manually selecting any HDMI configuration/profile creates a dummy
output with no sound. In other desktop environments, such as GNOME, the HDMI
audio output becomes available automatically on connecting the TV.

Output of aplay -l is:-
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

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

[systemsettings] [Bug 370521] [Regresion] SDDM breeze theme unable to change backgound.

[Piotr Kloc]

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

Piotr Kloc  changed:

   What|Removed |Added

 CC||pepk...@gmail.com

--- Comment #4 from Piotr Kloc  ---
*** Bug 375380 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 375380] SDDM wallpaper keeps resetting, is not actually set.

[Piotr Kloc]

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

Piotr Kloc  changed:

   What|Removed |Added

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

--- Comment #2 from Piotr Kloc  ---
Seems like the same problem. I need to step up my searching.

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

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

[valgrind] [Bug 354809] Error message for unsupported platform is unhelpful

[Austin English]

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

--- Comment #1 from Austin English  ---
With:
austin@debian-laptop:~/src/valgrind$ ./vg-in-place --version -v
valgrind-3.13.0.SVN-16209-vex-3299

the error message has improved (64-bit valgrind, 32-bit binary):
austin@debian-laptop:~/src/valgrind$ ./vg-in-place /tmp/a.out 
valgrind: failed to start tool 'memcheck' for platform 'x86-linux': No such
file or directory

Recompiling as 64-bit binary:
austin@debian-laptop:~/src/valgrind$ ./vg-in-place /tmp/a.out 
==19785== Memcheck, a memory error detector
==19785== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==19785== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright
info
==19785== Command: /tmp/a.out
==19785== 
Alive==19785== 
==19785== HEAP SUMMARY:
==19785== in use at exit: 0 bytes in 0 blocks
==19785==   total heap usage: 1 allocs, 1 frees, 1,024 bytes allocated
==19785== 
==19785== All heap blocks were freed -- no leaks are possible
==19785== 
==19785== For counts of detected and suppressed errors, rerun with: -v
==19785== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)


Fixed.

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

[kaffeine] [Bug 374693] kaffeine does not tune into dvb-s

[bugzilla_noreply]

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

--- Comment #3 from julius...@gmail.com ---
an additional test with kaffeine -d : 

[Debug   ] tune to: S 11836500 H 2750 3/4
[Debug   ] tuning failed on 11836.50 MHz

then, vlc, close vlc, start kaffeine -d again: 

[Debug   ] tune to: S 11836500 H 2750 3/4   
[Debug   ] tuning succeeded on 11836.50 MHz

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

[frameworks-kactivities] [Bug 371924] KActivities shouldn't signal currentActivityChanged() unless it actually changed.

[Jamie Smith]

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

--- Comment #9 from Jamie Smith  ---
(In reply to Christoph Feck from comment #7)
> Reopening the bug. Please only close if the patch is committed.

Any time frame for when that may happen?

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

[kajongg] [Bug 375385] New: Kajongg does not load its translation catalog from local install folder

[Burkhard Lueck]

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

Bug ID: 375385
   Summary: Kajongg does not load its translation catalog from
local install folder
   Product: kajongg
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: wolfg...@rohdewald.de
  Reporter: lu...@hube-lueck.de
CC: kde-games-b...@kde.org
  Target Milestone: ---

master kf5 (l10n-kf5, frameworks, workspace, applications, extragear,
playground) build from sources as separate user installed in dir
$KF5=/home/kdeframeworks/kf5

strace kajongg 2>&1  | grep $KF5/share/locale/|grep kajongg shows no hit, i.e.
it does not load the translation catalog in $KF5

full strace output shows that the frameworks catalogs *_qt.qm in $KF5 are
loaded

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

[digikam] [Bug 375345] App icon doesn't appear in the Unity Dash

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
And with Kate AppImage ?

Note : I'm suprized that Krita do not propose Desktop integration. This feature
is aprovided by AppImage SDK, abd Krita script was been the reference that i
use to write digiKam one.

Gilles Caulier

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

[valgrind] [Bug 189143] (wine) crash when running using wine to run vcsetup.exe under valgrind

[Philippe Waroquiers]

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

Philippe Waroquiers  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[valgrind] [Bug 189143] (wine) crash when running using wine to run vcsetup.exe under valgrind

[Philippe Waroquiers]

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

Philippe Waroquiers  changed:

   What|Removed |Added

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

--- Comment #3 from Philippe Waroquiers  ---
As indicated by Austin, this is working with more recent Valgrind.

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

[Skanlite] [Bug 367974] Skanlite returns "invalid argument" when using the scan button

[Kåre Särs]

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

Kåre Särs  changed:

   What|Removed |Added

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

--- Comment #3 from Kåre Särs  ---
Sorry for not answering earlier.

It is a problem specific to the backend (HPAIO)

To get more debug info could you run skanlite with debug environment variable
set in the terminal?

SANE_DEBUG_HPAIO=16 skanlite


I'm not 100% sure about the environment variable. If you don't get any extra
printouts it is wrong...

Can you then post the output here?

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

[digikam] [Bug 328457] BQM Watermark tool : doesn't apply zero margins

[Ahmed Fathi]

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

--- Comment #2 from Ahmed Fathi  ---
Created attachment 103577
  --> https://bugs.kde.org/attachment.cgi?id=103577=edit
Screen shots for before and after the batch

Screen shots for 
1- before the batch
2- after the batch with the new Checkbox Checked
3- after the batch with the new Checkbox UnChecked

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

[digikam] [Bug 374313] wrong icon usage revisited [patch]

[Simon]

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

--- Comment #43 from Simon  ---
That doesn't change anything. For completeness the full log of makeall.sh:
http://pastebin.com/Q8KM5GPK The problem is still the same.

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

[digikam] [Bug 328457] BQM Watermark tool : doesn't apply zero margins

[Ahmed Fathi]

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

Ahmed Fathi  changed:

   What|Removed |Added

 CC||ahmed.fathi.abdelmageed@gma
   ||il.com

--- Comment #1 from Ahmed Fathi  ---
Created attachment 103576
  --> https://bugs.kde.org/attachment.cgi?id=103576=edit
a patch to solve the margin problem

HI , I solved this "bug" and here is the batch .
In the following post I will send screenshots

There were two problems :-

First in the function calls : watermarkRect.moveTopRight() ,
watermarkRect.moveBottomLeft(), watermarkRect.moveBottomRight() , We needed to
pass (Width -1 ) and (height -1 ) instead of Width and height.

The second problem was that the watermark photo has a different aspect ration
than the original photo. An option to "Keep Aspect ratio" of the waterMark was
used, so however large the watermark Image was , keeping its aspect ratio will
always leave spaces in the actual image. 
Changing the option from Qt::KeepAspectRatio  to  Qt::IgnoreAspectRatio  will
solve the problem and make the watermark always have the aspect ratio of the
original photo as @mnaugendre requires. but it is not logical to Always ignore
the aspect ratio of the watermark and stretch it to be exactly like the image.
So I added a new checkbox to allow the user to ignore the water mark aspect
ratio If that is what he really needs , which is unchecked by default.

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

[frameworks-baloo] [Bug 375384] New: Baloo file extractor crashes when loging into KDE

[Andesite]

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

Bug ID: 375384
   Summary: Baloo file extractor crashes when loging into KDE
   Product: frameworks-baloo
   Version: 5.29.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: pinak.ah...@gmail.com
  Reporter: da...@andesite.org
  Target Milestone: ---

Application: baloo_file_extractor (5.29.0)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.9.4-201.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:  Logged into KDE after boot
up, baloo file extractor crash notification.  Happens every time after booting.
 If restart is selected from crash report baloo file extractors consumes all
available system memory after about 10 minutes (16Gb).  Memory usage reported
by ksysguard.  If not restarted process baloo_file_extractor shows status of
'stopped'.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc488cd48c0 (LWP 1901))]

Thread 3 (Thread 0x7fc46a900700 (LWP 1907)):
#0  0x7fc485cca01d in poll () at /lib64/libc.so.6
#1  0x7fc4818bd156 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fc4818bd26c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fc486ad073b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fc486a8173a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fc4868de5f3 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fc488df0739 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fc4868e29da in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fc4852186ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fc485cd5f7f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fc473c37700 (LWP 1904)):
#0  0x7fc485cca01d in poll () at /lib64/libc.so.6
#1  0x7fc4809f7d10 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fc4809f9aa9 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fc4782c2d69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fc4868e29da in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fc4852186ca in start_thread () at /lib64/libpthread.so.0
#6  0x7fc485cd5f7f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc488cd48c0 (LWP 1901)):
[KCrash Handler]
#6  0x7fc485c0391f in raise () at /lib64/libc.so.6
#7  0x7fc485c0551a in abort () at /lib64/libc.so.6
#8  0x7fc487a71a82 in  () at /lib64/liblmdb.so.0.0.0
#9  0x7fc487a66bb5 in mdb_page_dirty () at /lib64/liblmdb.so.0.0.0
#10 0x7fc487a67de3 in mdb_page_alloc.isra () at /lib64/liblmdb.so.0.0.0
#11 0x7fc487a68059 in mdb_page_touch () at /lib64/liblmdb.so.0.0.0
#12 0x7fc487a69cff in mdb_cursor_touch () at /lib64/liblmdb.so.0.0.0
#13 0x7fc487a6e07a in mdb_cursor_del () at /lib64/liblmdb.so.0.0.0
#14 0x7fc487a6f6a4 in mdb_del0 () at /lib64/liblmdb.so.0.0.0
#15 0x7fc4880a93d2 in Baloo::MTimeDB::del(unsigned int, unsigned long long)
() at /lib64/libKF5BalooEngine.so.5
#16 0x7fc4880bf88c in Baloo::WriteTransaction::removeDocument(unsigned long
long) () at /lib64/libKF5BalooEngine.so.5
#17 0x55563de7eb21 in Baloo::App::index(Baloo::Transaction*, QString
const&, unsigned long long) ()
#18 0x55563de7f2be in Baloo::App::processNextFile() ()
#19 0x7fc486ab5a26 in QSingleShotTimer::timerEvent(QTimerEvent*) () at
/lib64/libQt5Core.so.5
#20 0x7fc486aaa82b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#21 0x7fc4872c2ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#22 0x7fc4872ca671 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#23 0x7fc486a827aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#24 0x7fc486acfd3b in QTimerInfoList::activateTimers() () at
/lib64/libQt5Core.so.5
#25 0x7fc486ad0291 in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() at /lib64/libQt5Core.so.5
#26 0x7fc4818bce42 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#27 0x7fc4818bd1c0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#28 0x7fc4818bd26c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#29 0x7fc486ad071f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#30 0x7fc486a8173a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#31 0x7fc486a8923c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#32 0x55563de7e1ff in 

[kwin] [Bug 375355] Meta/Modifier only shortcuts don't work when CapsLock is on

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin  ---
Git commit 5dc942ac5e3611ae7db8f2902bb092b66920edeb by Martin Gräßlin.
Committed on 21/01/2017 at 19:13.
Pushed by graesslin into branch 'Plasma/5.9'.

[autotests] Add test case for modifier only trigger when capslock enabled

This extends the testCapsLock to ensure that modifier only shortcut
trigger when capslock is enabled. So far the test only ensured that
capslock doesn't trigger the shift modifier only shortcut.

As the test shows currently when capslock is on, the meta key doesn't
trigger any more.

This test case goes into Plasma/5.9 branch and not in Plasma/5.8 as a
fix will most likely need the new xkbcommon 0.7 code paths which we do
not have in Plasma/5.8.

M  +16   -1autotests/integration/modifier_only_shortcut_test.cpp

https://commits.kde.org/kwin/5dc942ac5e3611ae7db8f2902bb092b66920edeb

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

[kteatime] [Bug 375383] New: kteatime system tray icon looks more like oxygen than breeze

[Marco Parillo]

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

Bug ID: 375383
   Summary: kteatime system tray icon looks more like oxygen than
breeze
   Product: kteatime
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: k...@hilefoks.org
  Reporter: marco_pari...@hotmail.com
  Target Milestone: ---

On Kubuntu ZZ, it seemed to revert to an Oxygen look from a Breeze look
yesterday, perhaps with KDE Apps 16.12.1

On Manjaro Stable, it is version 1.3 Using:
KDE Frameworks 5.29.0
Qt 5.7.1 (built against 5.7.1)
The xcb windowing system

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

[kdepim] [Bug 345959] When an individual folder is set to prefer HTML to Plaintext, some E-mails with both HTML and plaintext parts will display the plaintext part

[Denis Kurz]

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

Denis Kurz  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
Version|unspecified |5.3.*
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #3 from Denis Kurz  ---
I guess that's not your fault ;) thank you for the feedback. Since I cannot
reproduce it myself, I leave the bug unconfirmed for now. If you find an
afflicted message that you can share with us, please consider uploading it as
an attachment to this bug.

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

[kdepim] [Bug 359349] Fancy Headers: when CC field has a collapse/expand button, text is misaligned

[Denis Kurz]

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

Denis Kurz  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---
Version|unspecified |5.4.*
 Ever confirmed|0   |1

--- Comment #3 from Denis Kurz  ---
OK, I managed to find a message with many receivers myself. I think the commas
are now aligned properly. The collapse icon is still too high, though.

Btw, the direction of the arrows on the expand/collapse buttons are confusing,
too. The button is in front of the receiver list. In collapsed state, the
arrows point away from the list. Arrows towards the collapsed list are more
common, and common in KDE, too. Examples: Collapsed folders in Dolphin's
Details View Mode,  collapsed code blocks in KDevelop, or even folders in the
folder list of KMail itself.

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

[kwin] [Bug 375355] Meta/Modifier only shortcuts don't work when CapsLock is on

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
  Flags||Wayland+, X11+

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

[krunner] [Bug 353026] KRunner closes when focus is lost

[bugzilla_noreply]

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

k...@web.de changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #12 from k...@web.de ---
My workaround: If you switch the desktop with the "show desktop" shortcut (or
applet) before calling krunner, nothing will steal the focus from krunner
because the windows are hidden. Closing krunner will go back from the desktop
to what you have done before.

So the only thing that is needed for a workaround is a dbus command that calls
the "show desktop" thing and then opens krunner.

qdbus-qt5 org.kde.plasmashell /PlasmaShell toggleDashboard && \
qdbus-qt5 org.kde.krunner /App display

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

[kwallet-pam] [Bug 375236] kwallet-pam doesn't work in conjunction with dm-crypt-encrypted /home which gets unlocked with pam_mount

[Denis Kurz]

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

Denis Kurz  changed:

   What|Removed |Added

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

--- Comment #3 from Denis Kurz  ---
Ok, in this case, I'm lost, sorry. I reopen so someone with more insight can
review the bug and judge whether it's fixable from our side.

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

[digikam] [Bug 375345] App icon doesn't appear in the Unity Dash

[Dan Dascalescu]

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

--- Comment #3 from Dan Dascalescu  ---
Krita doesn't offer to integrate itself with the system when I launch its
appimage, so when I search in the Dash for Krita, I only find the appimage
file, not the installed app.

When I search the Dash for "digiKam", I find both, as seen in the screenshot.

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

[systemsettings] [Bug 375380] SDDM wallpaper keeps resetting, is not actually set.

[Rog131]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #1 from Rog131  ---
Probably dublicate of Bug 370521 - [Regresion] SDDM breeze theme unable to
change backgound - https://bugs.kde.org/show_bug.cgi?id=370521

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

[systemsettings] [Bug 356901] Remove Klipper KDE component from Global Keyboard Shortcuts

[bugzilla_noreply]

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

k...@web.de changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #1 from k...@web.de ---
It's annoying two have the same settings listed twice. Please remove the
duplicated entries.
But i would still prefer to have the Klipper shortcuts in a seperate list from
other Plasma shortcuts.

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

[kscreenlocker] [Bug 375368] Screen not locking when "Active windows" or "Desktop Grid" is showing windows/desktops

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
This is a well known and not fixable design limitation of the X11 windowing
system. Our Wayland implementation does not have this limitation.

Unfortunately on X11 there is nothing we can do about it.

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

[kwin] [Bug 375369] Decorations crash when change theme

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin  ---
Please provide output of
qdbus org.kde.KWin /KWin supportInformation

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

[kleopatra] [Bug 170915] Certificate details doesn't show correct certifications

[shayne coventry]

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

--- Comment #5 from shayne coventry  ---
thank you. how do I import? do i need to install kleo?
(In reply to Emanuel Schütze from comment #0)
> Version:   2.0.0-rc5 (using 4.1)
> Compiler:  gcc
> OS:MS Windows
> 
> 1. import an openpgp key with certifications
> 2. open certificate details -> certifications
> 3. load certifications
> -> name and email address of certifications are missing
> Only self certifications and new (with kleopatra created) certifications are
> shown correctly.

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

[kwin] [Bug 375355] Meta/Modifier only shortcuts don't work when CapsLock is on

[Martin Gräßlin]

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

--- Comment #4 from Martin Gräßlin  ---
I just realized that our unit test verifies a different behavior. That is:
don't trigger shift shortcut on caps lock.

Now trusting meta on caps lock sounds sensible in general. Though I won't
promise that we can fix it for 5.8.

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

[kleopatra] [Bug 170915] Certificate details doesn't show correct certifications

[shayne coventry]

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

shayne coventry  changed:

   What|Removed |Added

 CC||coventry.sha...@gmail.com

--- Comment #4 from shayne coventry  ---
For some reason. Kde does not recognize certs for google, also My internet
provider does not recognize kde as a viable os. My platform is a chromebook.
This was all working fine until I had to re install everything and start over
re installing kde.
 I did so just like the last time I had it but now I am recieving these new
issues.

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

[Spectacle] [Bug 375382] New: Function for copy to clipboard

[Samim Pezeshki]

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

Bug ID: 375382
   Summary: Function for copy to clipboard
   Product: Spectacle
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: psa...@gmail.com
  Target Milestone: ---

Hi,

I want to be able to take a screenshot and copy it to clipboard and assign a
shortcut to it. Can we have a function for that?

Thanks,
Samim

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

[ksnapshot] [Bug 298493] command line option for copy to clipboard

[Samim Pezeshki]

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

Samim Pezeshki  changed:

   What|Removed |Added

 CC||psa...@gmail.com

--- Comment #1 from Samim Pezeshki  ---
Looking forward for this to happen.

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

[kdenlive] [Bug 375381] archiving a project writes duplicate $CURRENTPATH/$CURRENTPATH

[Wegwerf]

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

--- Comment #1 from Wegwerf  ---
Okay, that's an artefact because both the  root attribute is set to
"$CURRENTPATH" as well as the resource properties.

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

[kdenlive] [Bug 375381] New: archiving a project writes duplicate $CURRENTPATH/$CURRENTPATH

[Wegwerf]

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

Bug ID: 375381
   Summary: archiving a project writes duplicate
$CURRENTPATH/$CURRENTPATH
   Product: kdenlive
   Version: git-master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de
  Target Milestone: ---

I'm not exactly sure as to this is a bug or not: when archiving a project using
Kdenlive's "project" > "archive" function, the .kdenlive file references its
producers using a duplicate $CURRENTPATH/$CURRENTPATH/... This looks odd to me;
but maybe it's supposed to be that dup pattern?

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

[kdenlive] [Bug 373972] Press render choose options, no video in file, just audio

[Wegwerf]

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

--- Comment #4 from Wegwerf  ---
This is a last call to DAVE. If we don't see any useful answer within 7 days,
we'll retire this report as INVALID. Thank you very much for your cooperation.

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

[kdenlive] [Bug 373972] Press render choose options, no video in file, just audio

[Wegwerf]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #3 from Wegwerf  ---
Check that a ffmpeg version is installed that actually supports mp4 containers
and the necessary codecs. Thank you for your cooperation.

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

[systemsettings] [Bug 375380] New: Wallpaper keeps reset

[Piotr Kloc]

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

Bug ID: 375380
   Summary: Wallpaper keeps reset
   Product: systemsettings
   Version: 5.8.95
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_sddm
  Assignee: k...@davidedmundson.co.uk
  Reporter: pepk...@gmail.com
  Target Milestone: ---

Wallpaper in SDDM seems to reset. Possibly related to the new logic introduced
in 5.9.

I'm guessing that changing wallpaper should trigger file change in
/usr/share/sddm/themes/breeze/theme.conf.

Probably from:


[General]
type=color
color=#1d99f3

to:

[General]
type=image
#color=#1d99f3
image=file-in-/usr/share/sddm/themes/breeze/name.png


Or something along the lines, there's also theme.conf.user which maybe was the
target. 

I've got around it by setting it manually in theme.conf.

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

[kdenlive] [Bug 373972] Press render choose options, no video in file, just audio

[Wegwerf]

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

Wegwerf  changed:

   What|Removed |Added

   Severity|critical|normal
 CC||wegwerf-1-...@gmx.de

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

[systemsettings] [Bug 375380] SDDM wallpaper keeps resetting, is not actually set.

[Piotr Kloc]

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

Piotr Kloc  changed:

   What|Removed |Added

Summary|Wallpaper keeps reset   |SDDM wallpaper keeps
   ||resetting, is not actually
   ||set.

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