[dolphin] [Bug 357359] New: Dolphin's file type Application preference order changes itself

[Sudhir Khanger via KDE Bugzilla]

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

Bug ID: 357359
   Summary: Dolphin's file type Application preference order
changes itself
   Product: dolphin
   Version: 15.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: sud...@sudhirkhanger.com

Text, xml, etc. type of files are being opened in LibreOffice Calc. Changing
App preference order changes itself back to what it was right away. Please see
the attached screencast.

Reproducible: Always

Steps to Reproduce:
1. Right-click a text file > Properties > File Type options > app preference
order.
2. Move the app that you want the file to be opened in and apply
3.

Actual Results:  
Changed order doesn't stick. It reverts back as soon as you apply.


mimeapps.list

[Added Associations]
application/xml=org.kde.kwrite.desktop;firefox.desktop;google-chrome.desktop;libreoffice-calc.desktop;libreoffice-writer.desktop;kde4-okularApplication_txt.desktop;emacs.desktop;calibre-ebook-viewer.desktop;emacsclient.desktop;calibre-gui.desktop;
text/plain=org.kde.kwrite.desktop;libreoffice-calc.desktop;libreoffice-writer.desktop;kde4-okularApplication_txt.desktop;emacs.desktop;calibre-ebook-viewer.desktop;emacsclient.desktop;calibre-gui.desktop;

[Default Applications]
application/xml=org.kde.kwrite.desktop;
text/plain=org.kde.kwrite.desktop;

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

[dolphin] [Bug 357359] Dolphin's file type Application preference order changes itself

[Sudhir Khanger via KDE Bugzilla]

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

--- Comment #1 from Sudhir Khanger  ---
Created attachment 96373
  --> https://bugs.kde.org/attachment.cgi?id=96373=edit
screencast demonstrating the problem

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

[yakuake] [Bug 336228] pressing f12 (or the equivalent closekey) causes respawn of yakuake if mouse is in yakuake

[Nicolás Alvarez via KDE Bugzilla]

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

Nicolás Alvarez  changed:

   What|Removed |Added

 CC||nicolas.alva...@gmail.com

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

[kdenlive] [Bug 357326] 1326x888 resolution/aspect ratio cause faulty display of videos

[via KDE Bugzilla]

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

--- Comment #2 from qubo...@gmail.com ---
If I configure Kdenlive to use the mentioned profile as default, after
restarting Kdenlive, a new project will have the same issues.

To anbody testing this: please report your graphics card driver so we can
hopefully narrow it down.

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

[kdevelop] [Bug 357358] New: Crash while parsing

[Christof Hanke via KDE Bugzilla]

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

Bug ID: 357358
   Summary: Crash while parsing
   Product: kdevelop
   Version: 4.7.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: christof.ha...@induhviduals.de

Application: kdevelop (4.7.2)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.3.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20151227) (x86_64)"

-- Information about the crash:
opened a session with the single project libkeduvocdocument-15.08.3

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4ec59ef900 (LWP 10503))]

Thread 11 (Thread 0x7f4ea7c75700 (LWP 10504)):
#0  0x7f4ebfdca07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4ebfa97fea in  () at /usr/lib64/libQtScript.so.4
#2  0x7f4ebfa98019 in  () at /usr/lib64/libQtScript.so.4
#3  0x7f4ebfdc44a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f4ec20bcbdd in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f4e267dd700 (LWP 10505)):
#0  0x7f4ebfdca428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4ec277c732 in QWaitCondition::wait(QMutex*, unsigned long)
(time=1000, this=0x2f3c7e0) at thread/qwaitcondition_unix.cpp:84
#2  0x7f4ec277c732 in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x2f29ee0, time=1000) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f4ec108e706 in  () at /usr/lib64/libkdevplatformlanguage.so.8
#4  0x7f4ec277c23c in QThreadPrivate::start(void*) (arg=0x2f29ec0) at
thread/qthread_unix.cpp:352
#5  0x7f4ebfdc44a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4ec20bcbdd in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f4e1bfd3700 (LWP 10506)):
#0  0x7f4ebc3a3a85 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f4ebc3a41df in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4ebc3a436c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4ec28b026e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4e140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f4ec28803e1 in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f4e1bfd2ce0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f4ec28806f5 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4e1bfd2ce0, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f4ec2779a59 in QThread::exec() (this=) at
thread/qthread.cpp:538
#7  0x7f4ec277c23c in QThreadPrivate::start(void*) (arg=0x384a4e8) at
thread/qthread_unix.cpp:352
#8  0x7f4ebfdc44a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f4ec20bcbdd in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f4dffc94700 (LWP 10570)):
#0  0x7f4ebc3e74b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4ebc3a4226 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4ebc3a436c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4ec28b026e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4df8015260, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f4ec28803e1 in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f4dffc93ca0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f4ec28806f5 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4dffc93ca0, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f4ec2779a59 in QThread::exec() (this=this@entry=0x4313cf0) at
thread/qthread.cpp:538
#7  0x7f4ec28614c3 in QInotifyFileSystemWatcherEngine::run()
(this=0x4313cf0) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f4ec277c23c in QThreadPrivate::start(void*) (arg=0x4313cf0) at
thread/qthread_unix.cpp:352
#9  0x7f4ebfdc44a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4ec20bcbdd in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f4dff493700 (LWP 10617)):
#0  0x7f4ec20b022d in read () at /lib64/libc.so.6
#1  0x7f4ebc3e6210 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4ebc3a3d94 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4ebc3a4208 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f4ebc3a436c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f4ec28b026e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4df0016420, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f4ec28803e1 in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f4dff492ca0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f4ec28806f5 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4dff492ca0, flags=...) at kernel/qeventloop.cpp:204
#8  0x7f4ec2779a59 in QThread::exec() 

[korganizer] [Bug 148172] Kontact crashes often after update

[Stephen via KDE Bugzilla]

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

Stephen  changed:

   What|Removed |Added

 CC||sder...@gmail.com

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

[konsole] [Bug 356203] Freeze on alt+f4 press

[via KDE Bugzilla]

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

bryan.para...@gmail.com changed:

   What|Removed |Added

 CC||bryan.para...@gmail.com

--- Comment #1 from bryan.para...@gmail.com ---
I am having issues with Konsole sitting there eating up a whole core
deadlocking on:

(gdb) bt
#0  0x7f90b552ce28 in _nv014tls () from /usr/lib/libnvidia-tls.so.340.96
#1  0x7f90b94c3ed4 in ?? () from /usr/lib/libGL.so.1
#2  0x7f90b94c423c in ?? () from /usr/lib/libGL.so.1
#3  0x7f90b94c433a in ?? () from /usr/lib/libGL.so.1
#4  0x7f90b949f105 in ?? () from /usr/lib/libGL.so.1
#5  0x7f90c278c885 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#6  0x7f90c21c3f88 in __run_exit_handlers () from /usr/lib/libc.so.6
#7  0x7f90c21c3fd5 in exit () from /usr/lib/libc.so.6
#8  0x7f90c21ae617 in __libc_start_main () from /usr/lib/libc.so.6
#9  0x00400779 in _start ()
(gdb) 

Unsure if related.

Did you turn off framebuffer? What hardware

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

[krunner] [Bug 357357] New: currency converter dont work

[FabiB via KDE Bugzilla]

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

Bug ID: 357357
   Summary: currency converter dont work
   Product: krunner
   Version: 5.5.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: converter
  Assignee: m...@vhanda.in
  Reporter: plusf...@gmail.com

when you tty to convert "10€" to something else .. its always the same:
1.0001e-98 USD
1.0001e-98 CAN
1.0001e-98 GBP
[...] 
also other currencies are not converted but simply goes 1:1 ...
please fix this, since its a really usefull function

Reproducible: Always

Steps to Reproduce:
1. alt+space (krunner)
2. "10EUR"

Actual Results:  
1.0001e-98 USD
1.0001e-98 CAN
1.0001e-98 GBP
[...]

Expected Results:  
it should work like on plasma4

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

[kdenlive] [Bug 357322] Clip Properties: rounded frame rate, b/s vs kb/s, superfluous digit in audio bitrate

[via KDE Bugzilla]

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

--- Comment #2 from qubo...@gmail.com ---
Thanks!
- As a quick test: 59.94 and 29.97 are the same both in Kdenlive clip
properties and ffprobe.
- 23.98 (ffprobe) is now reported as 23.976 in the properties. Not sure if
there's an issue there.
- I noticed that Audio and Video bitrates are now in kb/s rather than KiB/s but
the "Bitrate" is still in bits/s though without "b/s" (ffmpeg uses "kb/s" for
all three it seems)

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

[kdelibs] [Bug 357345] New: Knotify crashed after system-start

[via KDE Bugzilla]

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

Bug ID: 357345
   Summary: Knotify crashed after system-start
   Product: kdelibs
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: knotify
  Assignee: ogoff...@kde.org
  Reporter: gratisap...@arcor.de

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

-- Information about the crash:
Every start of Knotify lets crash it

The crash can be reproduced every time.

-- Backtrace:
Application: KNotify (knotify4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff4084db800 (LWP 2388))]

Thread 2 (Thread 0x7ff3f4eb1700 (LWP 2389)):
#0  0x7ff405696c5d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff402ccdbe4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff402ccdcec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff405e220de in QEventDispatcherGlib::processEvents
(this=0x7ff3f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7ff405df3e6f in QEventLoop::processEvents
(this=this@entry=0x7ff3f4eb0da0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7ff405df4165 in QEventLoop::exec (this=this@entry=0x7ff3f4eb0da0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7ff405cf10bf in QThread::exec (this=this@entry=0x1e4acc0) at
thread/qthread.cpp:538
#7  0x7ff405dd5783 in QInotifyFileSystemWatcherEngine::run (this=0x1e4acc0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7ff405cf379f in QThreadPrivate::start (arg=0x1e4acc0) at
thread/qthread_unix.cpp:349
#9  0x7ff4036fa0a4 in start_thread (arg=0x7ff3f4eb1700) at
pthread_create.c:309
#10 0x7ff40569f08d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7ff4084db800 (LWP 2388)):
[KCrash Handler]
#5  __strcmp_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:29
#6  0x7ff3e89bffee in qMetaTypeStaticType (length=22, typeName=0x3e7e998
) at kernel/qmetatype.cpp:806
#7  QMetaType::registerNormalizedType (normalizedTypeName=...,
deleter=deleter@entry=0x7ff3e9c8a930
::Delete(void*)>, creator=creator@entry=0x7ff3e9c8aab0
::Create(void const*)>, destructor=destructor@entry=0x7ff3e9c8a890
::Destruct(void*)>, constructor=constructor@entry=0x7ff3e9c8a8a0
::Construct(void*, void const*)>, size=size@entry=16,
flags=flags@entry=..., metaObject=metaObject@entry=0x0) at
kernel/qmetatype.cpp:896
#8  0x7ff3e99d3f57 in qRegisterNormalizedMetaType
(defined=QtPrivate::MetaTypeDefinedHelper::Defined, dummy=0x, normalizedTypeName=...) at
../../src/corelib/kernel/qmetatype.h:1603
#9  qRegisterMetaType
(defined=QtPrivate::MetaTypeDefinedHelper::Defined, dummy=0x, typeName=0x7ff3e9d669de
"QPaintBufferCacheEntry") at ../../src/corelib/kernel/qmetatype.h:1628
#10 qt_metatype_id () at painting/qpaintbuffer.cpp:2081
#11 qt_metatype_id () at ../../src/corelib/kernel/qmetatype.h:1509
#12 qMetaTypeId () at
../../src/corelib/kernel/qmetatype.h:1649
#13 qRegisterMetaTypeStreamOperators () at
../../src/corelib/kernel/qmetatype.h:1698
#14 qRegisterPaintBufferMetaTypes () at painting/qpaintbuffer.cpp:2107
#15 qRegisterPaintBufferMetaTypes_ctor_class_ (this=) at
painting/qpaintbuffer.cpp:2111
#16 __static_initialization_and_destruction_0 (__priority=65535,
__initialize_p=1) at painting/qpaintbuffer.cpp:2111
#17 _GLOBAL__sub_I_qpaintbuffer.cpp(void) () at painting/qpaintbuffer.cpp:2207
#18 0x7ff4083608ea in call_init (l=, argc=argc@entry=1,
argv=argv@entry=0x7fff1dad0488, env=env@entry=0x1dc5180) at dl-init.c:78
#19 0x7ff4083609d3 in call_init (env=0x1dc5180, argv=0x7fff1dad0488,
argc=1, l=) at dl-init.c:36
#20 _dl_init (main_map=main_map@entry=0x1f2be50, argc=1, argv=0x7fff1dad0488,
env=0x1dc5180) at dl-init.c:126
#21 0x7ff408364b08 in dl_open_worker (a=a@entry=0x7fff1dace538) at
dl-open.c:566
#22 0x7ff4083607a4 in _dl_catch_error
(objname=objname@entry=0x7fff1dace528,
errstring=errstring@entry=0x7fff1dace530,
mallocedp=mallocedp@entry=0x7fff1dace527, operate=operate@entry=0x7ff408364830
, args=args@entry=0x7fff1dace538) at dl-error.c:187
#23 0x7ff4083642fb in _dl_open (file=0x1f2bcf0
"/usr/lib64/vlc/plugins/gui/libqt4_plugin.so", mode=-2147483647,
caller_dlopen=, nsid=-2, argc=1, argv=0x7fff1dad0488,
env=0x1dc5180) 

[frameworks-frameworkintegration] [Bug 356583] KWalletManager5 crashes on "Export as encrypted"

[Florian Sievert via KDE Bugzilla]

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

Florian Sievert  changed:

   What|Removed |Added

 CC||ca...@phobeus.de

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

[systemsettings] [Bug 348998] SDDM login manager configuration window can be unresponsive

[Pulfer via KDE Bugzilla]

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

Pulfer  changed:

   What|Removed |Added

 CC||pul...@list.ru

--- Comment #11 from Pulfer  ---
Same with ROSA packages (Plasma 5.5.2).

When run from systemsettings SDDM KCM is always unresponsive in my test
VirtualBox machine. But when run just as "kcmshell5 sddm" it works fine.

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

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Götz via KDE Bugzilla]

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

Götz  changed:

   What|Removed |Added

 CC||goetzchr...@gmail.com

--- Comment #5 from Götz  ---
I experience the same issue GTK+2 and GTK+3 have light on light tooltip.

But additionally I can see in a PyQt4 app (PyQt5 works), that the tooltip is
not like the default Breeze color scheme, it shows dark text on a light
background.

So it seems that only Qt5 apps use the Breeze color scheme style.

Arch Linux
Plasma 5.5.2
KF 5.17
Qt 5.5.1
GTK+ 3.18.6

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

[kdenlive] [Bug 346608] SUGGESTION: Breeze dark theme by default?

[Jesse via KDE Bugzilla]

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

--- Comment #37 from Jesse  ---
j-b-m, can you confirm that this solution works for you as well? If so,
wouldn't that make it possible to have the Breeze dark theme enabled by default
on most current GNU/Linux (non-KDE desktop) distributions while still keeping
the look of Kdenlive as if it was on a KDE-based distro?

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

[plasmashell] [Bug 357344] New: plasma crash + skype

[Rod Sheaff via KDE Bugzilla]

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

Bug ID: 357344
   Summary: plasma crash + skype
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: r...@sheaffbrooks.plus.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-22-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
Trying to re-open skype (sorry) to re-test microphone input to it (usb webcam
with buildt-in microphone).

64-bit Kubuntu 15.10, standard installation.

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

Thread 22 (Thread 0x7fcc3caf6700 (LWP 1807)):
#0  0x7fcc4d8a28dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fcc51948bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fcc5194a74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fcc3f6ffa39 in QXcbEventReader::run (this=0x1d526e0) at
qxcbconnection.cpp:1105
#4  0x7fcc4dfa12be in QThreadPrivate::start (arg=0x1d526e0) at
thread/qthread_unix.cpp:337
#5  0x7fcc4d07e6aa in start_thread (arg=0x7fcc3caf6700) at
pthread_create.c:333
#6  0x7fcc4d8adeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fcc361fe700 (LWP 1886)):
#0  0x7fcc4a63d884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fcc4a5f8770 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcc4a5f911b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcc4a5f92fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fcc4e1d829b in QEventDispatcherGlib::processEvents
(this=0x7fcc38e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fcc4e17e75a in QEventLoop::exec (this=this@entry=0x7fcc361fdda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fcc4df9c3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fcc507f3f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fcc4dfa12be in QThreadPrivate::start (arg=0x1e776c0) at
thread/qthread_unix.cpp:337
#9  0x7fcc4d07e6aa in start_thread (arg=0x7fcc361fe700) at
pthread_create.c:333
#10 0x7fcc4d8adeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7fcc2b4de700 (LWP 1896)):
#0  0x7fcc4a63d869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fcc4a5f90f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcc4a5f92fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcc4e1d829b in QEventDispatcherGlib::processEvents
(this=0x7fcc240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fcc4e17e75a in QEventLoop::exec (this=this@entry=0x7fcc2b4ddda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fcc4df9c3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fcc507f3f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fcc4dfa12be in QThreadPrivate::start (arg=0x2135df0) at
thread/qthread_unix.cpp:337
#8  0x7fcc4d07e6aa in start_thread (arg=0x7fcc2b4de700) at
pthread_create.c:333
#9  0x7fcc4d8adeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7fcc28bfe700 (LWP 1933)):
#0  0x7fcc4d8a28dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fcc4a5f91ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcc4a5f92fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcc4e1d829b in QEventDispatcherGlib::processEvents
(this=0x7fcc28c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fcc4e17e75a in QEventLoop::exec (this=this@entry=0x7fcc28bfdda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fcc4df9c3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fcc507f3f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fcc4dfa12be in QThreadPrivate::start (arg=0x204b800) at
thread/qthread_unix.cpp:337
#8  0x7fcc4d07e6aa in start_thread (arg=0x7fcc28bfe700) at
pthread_create.c:333
#9  0x7fcc4d8adeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fcc1b1b6700 (LWP 1934)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc52bbd114 in ?? () from

[okular] [Bug 356816] When I open certain pdf documents, each entry in table of contents contains weird chracters at the end.

[Albert Astals Cid via KDE Bugzilla]

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

--- Comment #13 from Albert Astals Cid  ---
Are you sure you're using Plasma 4 as a desktop?

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

[plasmashell] [Bug 357343] New: Crash after exiting Skype by its icon on the status bar

[giacof via KDE Bugzilla]

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

Bug ID: 357343
   Summary: Crash after exiting Skype by its icon on the status
bar
   Product: plasmashell
   Version: 5.2.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: gia...@tiscali.it
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.2.2)

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

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

The Skype window got frozen and irresponsive after disconnecting the bluetooth
headset device. So I tried to close Skype by right clicking on its icon on the
status bar and then selecting exit.
Then the Skype window closed, but the crash notification popped up at once.
Some 10 minutes later, the Skype window came back, still unresposive.

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

Thread 39 (Thread 0x7f69330b0700 (LWP 1768)):
#0  0x7f69420e28dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f694464fb72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f694465164f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f69353f7099 in QXcbEventReader::run (this=0x18d98c0) at
qxcbconnection.cpp:1105
#4  0x7f6942763b0e in QThreadPrivate::start (arg=0x18d98c0) at
thread/qthread_unix.cpp:337
#5  0x7f69419696aa in start_thread (arg=0x7f69330b0700) at
pthread_create.c:333
#6  0x7f69420edeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 38 (Thread 0x7f692bfff700 (LWP 1792)):
#0  0x7f693e7ebeb2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f693e7ee7ef in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f693e7eee60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f693e7eefcc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f69429fac6c in QEventDispatcherGlib::processEvents
(this=0x7f6928c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#5  0x7f694299f3e2 in QEventLoop::exec (this=this@entry=0x7f692bffede0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f694275eb44 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f69444ecf65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f6942763b0e in QThreadPrivate::start (arg=0x1996c20) at
thread/qthread_unix.cpp:337
#9  0x7f69419696aa in start_thread (arg=0x7f692bfff700) at
pthread_create.c:333
#10 0x7f69420edeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 37 (Thread 0x7f691cf48700 (LWP 1806)):
#0  0x7f693e833789 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f693e7ee8cc in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f693e7eee60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f693e7eefcc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f69429fac6c in QEventDispatcherGlib::processEvents
(this=0x7f69180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#5  0x7f694299f3e2 in QEventLoop::exec (this=this@entry=0x7f691cf47de0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f694275eb44 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f69444ecf65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f6942763b0e in QThreadPrivate::start (arg=0x2336900) at
thread/qthread_unix.cpp:337
#9  0x7f69419696aa in start_thread (arg=0x7f691cf48700) at
pthread_create.c:333
#10 0x7f69420edeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 36 (Thread 0x7f6916fa9700 (LWP 1809)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7f69420e28d2 in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0x7f693e7eeebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f693e7eefcc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f69429fac6c in QEventDispatcherGlib::processEvents
(this=0x7f6918c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#5  0x7f694299f3e2 in QEventLoop::exec (this=this@entry=0x7f6916fa8de0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f694275eb44 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f69444ecf65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f6942763b0e in QThreadPrivate::start (arg=0x23f0290) 

[kwin] [Bug 356557] Add "Fullscreen window" matching

[via KDE Bugzilla]

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

--- Comment #26 from jeremy9...@gmail.com ---
(In reply to Thomas Lübking from comment #25)

If you don't understand what I meant you can reread the comments. I don't want
to spend more time on this, so can we stop with this and move along please ? I
think we have better things to do and I already say what I want.

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

[digikam] [Bug 350367] Digikam crash when saving edited picture

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||g...@giedke.de

--- Comment #11 from caulier.gil...@gmail.com ---
*** Bug 357340 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 357340] digikam crashes when modifying picture

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
I suspect that you use Exiv2 0.24 with digiKam. Look in Help/Component Info
dialog for details.

Please update to Exiv2 0.25 which include a lots of fixes. digiKam and
libkexiv2 need to be recompiled.

Gilles Caulier

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

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

[plasmashell] [Bug 354137] task bar constantly freezes, when I use systemd automount on an nfs volume in the network

[Rainer Finke via KDE Bugzilla]

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

Rainer Finke  changed:

   What|Removed |Added

 CC||m...@rainer-finke.de

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

[plasmashell] [Bug 354137] task bar constantly freezes, when I use systemd automount on an nfs volume in the network

[Rainer Finke via KDE Bugzilla]

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

Rainer Finke  changed:

   What|Removed |Added

 CC|m...@rainer-finke.de|

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

[plasmashell] [Bug 357343] Crash after exiting Skype by its icon on the status bar

[giacof via KDE Bugzilla]

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

--- Comment #2 from giacof  ---
(In reply to David Edmundson from comment #1)
> Thanks
> 
> This has been fixed for a while.

Thank you, since what version was the issue fixed?

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

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Götz via KDE Bugzilla]

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

--- Comment #6 from Götz  ---
Qt4 and Qt5 tooltips
http://i.imgur.com/xr5bQtX.png

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

[plasmashell] [Bug 357343] Crash after exiting Skype by its icon on the status bar

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Thanks

This has been fixed for a while.

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

[kdelibs] [Bug 357346] New: Knotify keeps crashing (after XFCE desktop installation)

[via KDE Bugzilla]

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

Bug ID: 357346
   Summary: Knotify keeps crashing (after XFCE desktop
installation)
   Product: kdelibs
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: knotify
  Assignee: ogoff...@kde.org
  Reporter: tariqbenam...@gmail.com

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

-- Information about the crash:
- What I was doing when the application crashed: The session just started up.
It crashes everytime I log in. This behaviour started after a XFCE destkop
installation.

The crash can be reproduced every time.

-- Backtrace:
Application: KNotify (knotify4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f72bbd73800 (LWP 15762))]

Thread 3 (Thread 0x7f72a80bd700 (LWP 16017)):
#0  0x7f72b8f59d2d in read () at /lib64/libc.so.6
#1  0x7f72b6608750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f72b65c7714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f72b65c7b7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f72b65c7cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f72b96e00de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#6  0x7f72b96b1e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f72b96b2165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#8  0x7f72b95af0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#9  0x7f72b9693783 in  () at /usr/lib64/libQtCore.so.4
#10 0x7f72b95b179f in  () at /usr/lib64/libQtCore.so.4
#11 0x7f72b6fe40a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f72b8f6608d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f72983f3700 (LWP 16145)):
#0  0x7f72b8f5dc5d in poll () at /lib64/libc.so.6
#1  0x7f72988fe268 in  () at /usr/lib64/libusb-1.0.so.0
#2  0x7f72b6fe40a4 in start_thread () at /lib64/libpthread.so.0
#3  0x7f72b8f6608d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f72bbd73800 (LWP 15762)):
[KCrash Handler]
#5  0x7f72b8fa4fe6 in __strcmp_ssse3 () at /lib64/libc.so.6
#6  0x7f7295c8dfee in QMetaType::registerNormalizedType(QByteArray const&,
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void
const*), int, QFlags, QMetaObject const*) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f729618df57 in  () at /usr/lib64/libQt5Gui.so.5
#8  0x7f72bbbfb8ea in call_init.part () at /lib64/ld-linux-x86-64.so.2
#9  0x7f72bbbfb9d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2
#10 0x7f72bbbffb08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#11 0x7f72bbbfb7a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#12 0x7f72bbbff2fb in _dl_open () at /lib64/ld-linux-x86-64.so.2
#13 0x7f72b473e02b in dlopen_doit () at /lib64/libdl.so.2
#14 0x7f72bbbfb7a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#15 0x7f72b473e5dd in _dlerror_run () at /lib64/libdl.so.2
#16 0x7f72b473e0c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#17 0x7f72a6f3259f in  () at /usr/lib64/libvlccore.so.7
#18 0x7f72a6f1bd5d in  () at /usr/lib64/libvlccore.so.7
#19 0x7f72a6f1c057 in  () at /usr/lib64/libvlccore.so.7
#20 0x7f72a6f1c2c9 in  () at /usr/lib64/libvlccore.so.7
#21 0x7f72a6f1c534 in  () at /usr/lib64/libvlccore.so.7
#22 0x7f72a6f1ca87 in  () at /usr/lib64/libvlccore.so.7
#23 0x7f72a6eb449d in libvlc_InternalInit () at /usr/lib64/libvlccore.so.7
#24 0x7f72a6c85623 in libvlc_new () at /usr/lib64/libvlc.so.5
#25 0x7f72a71b6ec9 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#26 0x7f72a719c728 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#27 0x7f72a719d1eb in qt_plugin_instance () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#28 0x7f72b9697641 in QPluginLoader::instance() () at
/usr/lib64/libQtCore.so.4
#29 0x7f72a76b3f8b in  () at /usr/lib64/kde4/plugins/phonon_platform/kde.so
#30 0x7f72a76b4773 in  () at /usr/lib64/kde4/plugins/phonon_platform/kde.so
#31 0x7f72bb352c76 in  () at /usr/lib64/libphonon.so.4
#32 0x7f72bb353317 in Phonon::Factory::backend(bool) () at
/usr/lib64/libphonon.so.4
#33 0x7f72bb3538e3 in  () at /usr/lib64/libphonon.so.4
#34 0x7f72bb34b9b9 in  () at /usr/lib64/libphonon.so.4
#35 0x7f72bb349896 in  () at /usr/lib64/libphonon.so.4
#36 0x0040e771 in _start ()

Reported using DrKonqi

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

[kmymoney4] [Bug 357290] unwanted transfer transaction created by ofx

[Swj via KDE Bugzilla]

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

--- Comment #5 from Swj  ---
Yes, I suppose it is an investment account- its a money market account and
ofxlog.txt has a  tag in it.
Do you know of a workaround so I can get rid of all the double transactions in
this acct and not have them reoccur every month?

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

[parley] [Bug 356233] File is not writeable when creating a new collection

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/libk
   ||eduvocdocument/0cb9b9aea226
   ||4fc66d25fb6d93adc32c75dfef9
   ||7
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from Andreas Cord-Landwehr  ---
Git commit 0cb9b9aea2264fc66d25fb6d93adc32c75dfef97 by Andreas Cord-Landwehr.
Committed on 30/12/2015 at 18:54.
Pushed by cordlandwehr into branch 'master'.

Fix Save-As functionality.

File system operations like QFile require paths instead of URLs, which
is the difference between the uses of:
* url.toDisplayString -> file:///the/path
* url.toLocalFile -> /the/path
Correctly use toLocalFile for all file system calls.

M  +2-2keduvocdocument/keduvocdocument.cpp

http://commits.kde.org/libkeduvocdocument/0cb9b9aea2264fc66d25fb6d93adc32c75dfef97

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC|k...@davidedmundson.co.uk|

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

[krita] [Bug 357342] doesn't open a new raw file and a saved file, it just was black

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #3 from Boudewijn Rempt  ---
Okay, then I deduce that you're probably using a laptop, or a system with an
integrated Intel graphics processor in any case. Your driver is broken and
cannot handle Krita's demands. Updating a driver is pretty difficult, more
difficult than it should be, and manufacturers are really bad at providing
updates.

You can go to the Settings menu, select Configure Krita, click on the Display
icon and then disable the OpenGL checkbox. That should fix the canvas display
issue, at the expense of some performance and missing features.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[via KDE Bugzilla]

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

--- Comment #139 from abrah...@acm.org ---
As I've said before, I really miss the "different wallpapers" feature -- enough
so that I'll stick with v14.04LTS until its end of life until and unless the
feature is restored.  At the same time, I appreciate all the hard work that
David has put into KDE.  I may disagree with his judgement, but ultimately he
and the other devs are the bosses here.  I never forget that he who pays the
piper calls the tune.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Nathanael Schilling via KDE Bugzilla]

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

--- Comment #135 from Nathanael Schilling  ---
plasma is an open source project. Whilst I think that the decision to
discontinue multiple wallpapers is stupid, I think it's a stretch to
compare plasma to an actual company that produces things people pay for.

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

[kde] [Bug 357348] (Blank) Dialog (any application) freezes randomly due to waiting for open("dev/video0", O_RDWR), unplugging webcam solves the issue

[Vyse007 via KDE Bugzilla]

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

--- Comment #1 from Vyse007  ---
Created attachment 96367
  --> https://bugs.kde.org/attachment.cgi?id=96367=edit
Blank dialog when trying to delete a file using Dolphin

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

[kwin] [Bug 347176] kcm_kwin4_genericscripted.so not found because it's in the wrong location

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #5 from Thomas Lübking  ---
Do you have
/usr/lib/qt/plugins/kwin/effects/configs/kcm_kwin4_genericscripted.so or maybe
"only" /usr/lib/plugins/kwin/effects/configs/kcm_kwin4_genericscripted.so and
how does that correlate with the output of "kf5-config --path qtplugins"?

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

[kmymoney4] [Bug 357290] unwanted transfer transaction created by ofx

[Jack via KDE Bugzilla]

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

--- Comment #6 from Jack  ---
The question is what kind of  account do you have it set up as in KMM?  
In the ofx log, can you find what date KMM is requesting as the start of
downloaded transactions?  That is the first key point.  If it is the date of
your last update, we move on to the second issue.  However, if it is 60 days
ago, even if  you have the account configured to download only since the
previous update, then you can try setting the start date each time  you
download.  That will avoid downloading the same transactions multiple times.

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

[kdevelop] [Bug 357350] New: Custom color scheme in Kdevelop4 Kate

[Jakob Janzen via KDE Bugzilla]

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

Bug ID: 357350
   Summary: Custom color scheme in Kdevelop4 Kate
   Product: kdevelop
   Version: 4.7.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jashk...@googlemail.com

Application: kdevelop (4.7.1)
KDE Platform Version: 4.14.10
Qt Version: 4.8.6
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- opened color settings of Kate in Kdevelop
- imported custom color scheme (wich works normal in Kate without Kdevelop)
- while color scheme was loading, Kdevelop crashed

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8acfc62800 (LWP 68334))]

Thread 9 (Thread 0x7f8ab2634700 (LWP 68335)):
#0  0x7f8aca06105f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ac9d3486b in  () at /usr/lib64/libQtScript.so.4
#2  0x7f8ac9d348a9 in  () at /usr/lib64/libQtScript.so.4
#3  0x7f8aca05d0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f8acc33a04d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f8a3141c700 (LWP 68344)):
#0  0x7f8aca061408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8acca07084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f8acb315c82 in  () at /usr/lib64/libkdevplatformlanguage.so.8
#3  0x7f8acca06bbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7f8aca05d0a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f8acc33a04d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f8a0ff53700 (LWP 68353)):
#0  0x7f8ac6682cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f8ac6640387 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8ac6640d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f8ac6640f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f8accb34fde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7f8accb06d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f8accb07045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f8acca044df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7f8accae8653 in  () at /usr/lib64/libQtCore.so.4
#9  0x7f8acca06bbf in  () at /usr/lib64/libQtCore.so.4
#10 0x7f8aca05d0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f8acc33a04d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f8a10754700 (LWP 68361)):
#0  0x7f8acc331c1d in poll () at /lib64/libc.so.6
#1  0x7f8ac6640e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8ac6640f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8accb34fde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f8accb06d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f8accb07045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f8acca044df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f8accae8653 in  () at /usr/lib64/libQtCore.so.4
#8  0x7f8acca06bbf in  () at /usr/lib64/libQtCore.so.4
#9  0x7f8aca05d0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f8acc33a04d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f8a1b6d4700 (LWP 68362)):
#0  0x7f8aca06105f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8acca070a6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f8ac254f6fc in  () at /usr/lib64/libthreadweaver.so.4
#3  0x7f8ac2552193 in  () at /usr/lib64/libthreadweaver.so.4
#4  0x7f8ac2550eaf in ThreadWeaver::Thread::run() () at
/usr/lib64/libthreadweaver.so.4
#5  0x7f8acca06bbf in  () at /usr/lib64/libQtCore.so.4
#6  0x7f8aca05d0a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7f8acc33a04d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f8a1985c700 (LWP 68501)):
#0  0x7f8ac6682d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f8ac6640759 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8ac6640dcf in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f8ac6640f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f8accb34fde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7f8accb06d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f8accb07045 in
QEventLoop::exec(QFlags) () at

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[via KDE Bugzilla]

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

--- Comment #137 from jeremy9...@gmail.com ---
(In reply to David Edmundson from comment #129)
> It's probably in your interest not to piss me off.

I don't need this feature so I'm not emotionally involved on his disappearing.
I profoundly respect and admire your work but the fact is that is you that
pissed of the users by removing a feature they loved without even asking them
;)

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

[kmail2] [Bug 357351] New: Akonadi crashes when dowloading mail

[Wolfgang via KDE Bugzilla]

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

Bug ID: 357351
   Summary: Akonadi crashes when dowloading mail
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: wof...@woffer.org

Akonadi chrashes when looking for new mails with kmail5.
Mails which have allready been download are retrieved again.
This is happening since three days when I tryed to install Simon which
requested for an older akonadi version

Bug info below:

Application: akonadi_pop3_resource (4.89.0)

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

-- Information about the crash:


-- Backtrace:
Application: Akonadi-Ressource (akonadi_pop3_resource), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7faceb7a6800 (LWP 3121))]

Thread 2 (Thread 0x7facd55fb700 (LWP 3137)):
#0  0x7face66f3c1d in poll () at /lib64/libc.so.6
#1  0x7face155d422 in  () at /usr/lib64/libxcb.so.1
#2  0x7face155f00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7facd73263c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7face700232f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7face177a0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7face66fc04d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7faceb7a6800 (LWP 3121)):
[KCrash Handler]
#6  0x7face674c818 in __memmove_ssse3_back () at /lib64/libc.so.6
#7  0x7face7067649 in QListData::remove(int) () at
/usr/lib64/libQt5Core.so.5
#8  0x7face70678e9 in QListData::erase(void**) () at
/usr/lib64/libQt5Core.so.5
#9  0x0041ff87 in POP3Resource::saveSeenUIDList() ()
#10 0x00420687 in POP3Resource::finish() ()
#11 0x00422b0b in POP3Resource::doStateStep() ()
#12 0x00427b6d in POP3Resource::quitJobResult(KJob*) ()
#13 0x7face720d73f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#14 0x7face8f6dd32 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/usr/lib64/libKF5CoreAddons.so.5
#15 0x7face8f6e59f in KJob::finishJob(bool) () at
/usr/lib64/libKF5CoreAddons.so.5
#16 0x00436dd1 in SlaveBaseJob::slotSlaveResult(KJob*) ()
#17 0x7face720d73f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#18 0x7face8f6dd32 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/usr/lib64/libKF5CoreAddons.so.5
#19 0x7face8f6e59f in KJob::finishJob(bool) () at
/usr/lib64/libKF5CoreAddons.so.5
#20 0x7face9c4dde6 in KIO::SimpleJob::slotFinished() () at
/usr/lib64/libKF5KIOCore.so.5
#21 0x7face9c58c03 in KIO::TransferJob::slotFinished() () at
/usr/lib64/libKF5KIOCore.so.5
#22 0x7face9c58381 in  () at /usr/lib64/libKF5KIOCore.so.5
#23 0x7face720dcc6 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#24 0x7face9c328b1 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() at /usr/lib64/libKF5KIOCore.so.5
#25 0x7face9c2ff98 in KIO::SlaveInterface::dispatch() () at
/usr/lib64/libKF5KIOCore.so.5
#26 0x7face9c343ce in KIO::Slave::gotInput() () at
/usr/lib64/libKF5KIOCore.so.5
#27 0x7face9cae5d5 in  () at /usr/lib64/libKF5KIOCore.so.5
#28 0x7face720dcc6 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#29 0x7face9be444c in  () at /usr/lib64/libKF5KIOCore.so.5
#30 0x7face720eac6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#31 0x7face8141e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#32 0x7face8146cc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#33 0x7face71dde95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#34 0x7face71e0057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#35 0x7face72358f3 in  () at /usr/lib64/libQt5Core.so.5
#36 0x7face0e3ac84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#37 0x7face0e3aed8 in  () at /usr/lib64/libglib-2.0.so.0
#38 0x7face0e3af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#39 0x7face7234d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#40 0x7face71dbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#41 0x7face71e38f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#42 0x7faceb1412aa in Akonadi::ResourceBase::init(Akonadi::ResourceBase*)
() at /usr/lib64/libKF5AkonadiAgentBase.so.5
#43 0x0042a40d in int 

[kdenlive] [Bug 346608] SUGGESTION: Breeze dark theme by default?

[via KDE Bugzilla]

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

--- Comment #38 from qubo...@gmail.com ---
Side note: I would like to suggest that both dark and light themes are included
in Kdenlive, notwithstanding which one is the default one.

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

[kwin] [Bug 356740] Kwin crash if I set brightness while in kodi

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #7 from Thomas Lübking  ---
That's bug #346118 - certainly not related to kwin and unlikely related to
changing the brightness in kodi.

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

[kpat] [Bug 357349] In Spider Solitaire an extra card gets sent to completed piles

[Tim Middleton via KDE Bugzilla]

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

--- Comment #1 from Tim Middleton  ---
Created attachment 96369
  --> https://bugs.kde.org/attachment.cgi?id=96369=edit
screen shot of 2 of clubs in wrong place

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

[kpat] [Bug 357349] New: In Spider Solitaire an extra card gets sent to completed piles

[Tim Middleton via KDE Bugzilla]

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

Bug ID: 357349
   Summary: In Spider Solitaire an extra card gets sent to
completed piles
   Product: kpat
   Version: 3.6
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: x...@vex.net
CC: kde-games-b...@kde.org

In spider solitaire when you complete a full sequence of the same suite the
cards get moved from the playing area to the "completed pile". In one instance,
I got to the end of the game I was about to win and found there was a card
missing in the play area. Looking down on the completed pile, which normally
will show the ace at the top of each pile, one pile shows a 2 of clubs, which
is the missing card from the play area. 

It actually seems like the pile where the 2 of clubs is showing thinks it is
the completed clubs set, because there are two of each suits represented in the
complete piles (I play with "4 suits (hard)" option), despite there being all
the other clubs except the 2 still in the play area. 

I have taken a screen shot to show how the game looks in the current error
state which I will attach to a comment.

Since the completed piles exist in order that they were completed and the 2 of
clubs appears in the 4th pile, it seems the bug happened some turns ago and I
didn't notice.

Thinking back, I did notice one strange behaviour, however. At one point I
completed a suit and it failed to auto-move to the completed piles. I then
moved that completed card sequence to an empty spot and that triggered it to
move itself to the completed piles. Perhaps that is when the weird state
appeared.

I see the game number is 1123469748, but I haven't yet tried to replay this
game and see if I can trigger the problem again. 

Reproducible: Didn't try

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

[kwin] [Bug 347176] kcm_kwin4_genericscripted.so not found because it's in the wrong location

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #7 from Thomas Lübking  ---
See the doubled plugins/plugins ?

That's a distro bug (and I think it was already reported) - basically they
added "plugins" to the plugins path when compiling KF5 (what's likely
undesired), but use the proper path on installing kwin (or similar, but
whatever happened, the lib does not end up in a plugins path and the default
plugins path in KF5 is likely the wrong one)

Check whether you don't have accidentally set "echo $QT_PLUGIN_PATH" and try

  
QT_PLUGIN_PATH=/usr/lib64/plugins/:/usr/lib64/qt5/plugins/plugins/:/usr/lib64/qt5/plugins/
kwin_x11 --replace &

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

[kwin] [Bug 356557] Add "Fullscreen window" matching

[via KDE Bugzilla]

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

--- Comment #29 from jeremy9...@gmail.com ---
There is already too much hate on internet and I hope that we can forget this
and make peace.

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

[kwin] [Bug 347176] kcm_kwin4_genericscripted.so not found because it's in the wrong location

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #9 from Thomas Lübking  ---
Then it the path set at compile time.
As mentioned, I think we had this (fedora? I'm really not sure) but you may
still want to report to your distro.

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

[kwin] [Bug 347176] kcm_kwin4_genericscripted.so not found because it's in the wrong location

[Marc Collin via KDE Bugzilla]

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

Marc Collin  changed:

   What|Removed |Added

 CC||coll...@laboiteaprog.com

--- Comment #4 from Marc Collin  ---
same problem if i set with this value.

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

[kde] [Bug 357348] (Blank) Dialog (any application) freezes randomly due to waiting for open("dev/video0", O_RDWR), unplugging webcam solves the issue

[Vyse007 via KDE Bugzilla]

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

--- Comment #2 from Vyse007  ---
I should add that this only happens the first time I launch the application.
Once I have waited for the first dialog to be populated, all the subsequent
dialogs work as expected. If I restart the application, however, I have to deal
with it again (but only for the first time, as always).

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

[kwin] [Bug 356740] Kwin crash if I set brightness while in kodi

[Côme Chilliet via KDE Bugzilla]

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

--- Comment #6 from Côme Chilliet  ---
Created attachment 96368
  --> https://bugs.kde.org/attachment.cgi?id=96368=edit
Plasmashell backtrace

Got this crash today while using kodi. Was not setting the backlight this time.

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

[kwin] [Bug 347176] kcm_kwin4_genericscripted.so not found because it's in the wrong location

[Marc Collin via KDE Bugzilla]

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

--- Comment #6 from Marc Collin  ---
no mine is in lib64
/usr/lib64/qt5/plugins/kwin/effects/configs/kcm_kwin4_genericscripted.so

kf5-config --path qtplugins return 
/usr/lib64/plugins/:/usr/lib64/qt5/plugins/plugins/

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[via KDE Bugzilla]

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

--- Comment #136 from hum...@yahoo.fr ---
Congratulations guys. You pissed off the only kde dev who was working on that
problem... I think that now we can forget having this feature back anytime
soon...

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

[kdevelop] [Bug 357350] Custom color scheme in Kdevelop4 Kate

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Kevin Funk  ---
You're lacking some debug symbols.

Please install the Kate debug package (kate-dbg or similar), then reproduce the
crash and post the new stacktrace.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[via KDE Bugzilla]

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

--- Comment #138 from jeremy9...@gmail.com ---
It's like giving a candy to a kid and, a little later, take it back !
You will only make it cry :D

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

[ksmserver] [Bug 354934] crash after connecting external screen

[Kelvie Wong via KDE Bugzilla]

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

--- Comment #4 from Kelvie Wong  ---
This is on qt 5.5.1, and kde 5.17 (built on the 27th of dec, from the ubuntu
unstable ci ppa)

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

[kwin] [Bug 347176] kcm_kwin4_genericscripted.so not found because it's in the wrong location

[Marc Collin via KDE Bugzilla]

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

--- Comment #8 from Marc Collin  ---
In console, 

echo $QT_PLUGIN_PATH

return nothing.

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

[ksmserver] [Bug 354934] crash after connecting external screen

[Kelvie Wong via KDE Bugzilla]

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

Kelvie Wong  changed:

   What|Removed |Added

 CC||kel...@ieee.org

--- Comment #3 from Kelvie Wong  ---
Created attachment 96370
  --> https://bugs.kde.org/attachment.cgi?id=96370=edit
Stacktrace with ScreenLocker entry

I have this problem as well -- I use nightly build PPAs; this happens with
almost exactly the same setup

External monitor (I typically set my desktop to only display on the external
display) over displayport.

Trivially reproducable (on a Dell laptop) by locking the screen whilst using
the external display, and turning off the external monitor (which is the
primary desktop).

Attaching a stacktrace as well.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[via KDE Bugzilla]

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

--- Comment #140 from wulf.richa...@gmx.de ---
yes, different wallpapers are cool, but what about the marble globe background
or the search and launch layout? The were cooler!
ok, not really essential, but cool.

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

[kdenlive] [Bug 357326] 1326x888 resolution/aspect ratio cause faulty display of videos

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
I cannot reproduce. However, can you confirm that the problem only happens when
you change the profile of a current document ?

If you start a new project with your adjusted profile (1326x888), and add your
clip, it is displayed correctly in both monitors ?

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

[krita] [Bug 357342] doesn't open a new raw file and a saved file, it just was black

[via KDE Bugzilla]

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

--- Comment #4 from alissaroe...@gmail.com ---
Thank you very much for your help now it works ^~^

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

[kdeconnect] [Bug 355015] SFTP: Can't browse files on phone using kdeconnect-kde5

[Robert G . Siebeck via KDE Bugzilla]

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

Robert G. Siebeck  changed:

   What|Removed |Added

 CC||kde.bugzilla.2...@r123.de

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

[gwenview] [Bug 357353] New: crashed when pressing CONTROL L two times very fast

[Gerd Grass via KDE Bugzilla]

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

Bug ID: 357353
   Summary: crashed when pressing CONTROL L two times very fast
   Product: gwenview
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: gerd.gr...@gmx.de
CC: myr...@kde.org

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

-- Information about the crash:
- What I was doing when the application crashed:
gwenview crashed when pressing CONTROL L (for rotating) two times very fast. 
When pressing CONTROL L slowly several times then it always worked.
Problem only happened when file was loaded and there was no rotation before.

The crash can be reproduced sometimes.

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

Thread 3 (Thread 0x7fd2215d9700 (LWP 2311)):
#0  0x7fd2364e9c5d in poll () at /lib64/libc.so.6
#1  0x7fd239913f20 in  () at /opt/lib/libmediaclient.so
#2  0x7fd239914c62 in poll () at /opt/lib/libmediaclient.so
#3  0x7fd231e23be4 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fd231e23cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fd2389120de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#6  0x7fd2388e3e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7fd2388e4165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#8  0x7fd2387e10bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#9  0x7fd2388c5783 in  () at /usr/lib64/libQtCore.so.4
#10 0x7fd2387e379f in  () at /usr/lib64/libQtCore.so.4
#11 0x7fd235dec0a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7fd2364f208d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fd21bfff700 (LWP 2344)):
#0  0x7fd235df0408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd2387e3c64 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7fd2387d77ba in  () at /usr/lib64/libQtCore.so.4
#3  0x7fd2387e379f in  () at /usr/lib64/libQtCore.so.4
#4  0x7fd235dec0a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7fd2364f208d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fd239c90880 (LWP 2283)):
[KCrash Handler]
#5  0x7fd2388eb83e in QMetaObject::cast(QObject*) const () at
/usr/lib64/libQtCore.so.4
#6  0x7fd2393b913f in  () at /usr/lib64/libgwenviewlib.so.4
#7  0x7fd2393ba7dd in
Gwenview::Document::prepareDownSampledImageForZoom(double) () at
/usr/lib64/libgwenviewlib.so.4
#8  0x7fd2393f33fa in Gwenview::ImageScaler::doScale() () at
/usr/lib64/libgwenviewlib.so.4
#9  0x7fd2393d2e74 in Gwenview::RasterImageView::updateBuffer(QRegion
const&) () at /usr/lib64/libgwenviewlib.so.4
#10 0x7fd2393d2fb1 in Gwenview::RasterImageView::onZoomChanged() () at
/usr/lib64/libgwenviewlib.so.4
#11 0x7fd2393c4ff0 in  () at /usr/lib64/libgwenviewlib.so.4
#12 0x7fd2393d2ba1 in Gwenview::RasterImageView::updateImageRect(QRect
const&) () at /usr/lib64/libgwenviewlib.so.4
#13 0x7fd2393d4839 in  () at /usr/lib64/libgwenviewlib.so.4
#14 0x7fd2388f91fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#15 0x7fd2393b7a95 in Gwenview::Document::imageRectUpdated(QRect const&) ()
at /usr/lib64/libgwenviewlib.so.4
#16 0x7fd2388fd59e in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#17 0x7fd2371dd76c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#18 0x7fd2371e3cad in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#19 0x7fd237ef5e0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#20 0x7fd2388e52ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#21 0x7fd2388e857d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#22 0x7fd2389128fe in  () at /usr/lib64/libQtCore.so.4
#23 0x7fd231e23a04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#24 0x7fd231e23c48 in  () at /usr/lib64/libglib-2.0.so.0
#25 0x7fd231e23cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#26 0x7fd2389120be in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#27 0x7fd23727a676 in  () at /usr/lib64/libQtGui.so.4
#28 0x7fd2388e3e6f in
QEventLoop::processEvents(QFlags) () at

[gwenview] [Bug 357353] crashed when pressing CONTROL L two times very fast

[Gerd Grass via KDE Bugzilla]

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

--- Comment #1 from Gerd Grass  ---
Created attachment 96372
  --> https://bugs.kde.org/attachment.cgi?id=96372=edit
File for which the problem sometines occured.

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

[kdeconnect] [Bug 356528] Dolphin can not access android file system

[Robert G . Siebeck via KDE Bugzilla]

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

Robert G. Siebeck  changed:

   What|Removed |Added

 CC||kde.bugzilla.2...@r123.de

--- Comment #2 from Robert G. Siebeck  ---
Possible duplicate of #355015

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

[kpat] [Bug 357349] In Spider Solitaire an extra card gets sent to completed piles

[Tim Middleton via KDE Bugzilla]

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

--- Comment #2 from Tim Middleton  ---
I hit undo until I reached the place where the 2 of clubs was put down. I can
confirm it was at the same time as the completed sequence which did not
auto-move to the completed piles happened. Hitting redo at that point would
repeat the same error. However, if I completed the sequence again from a save
game I made at that point then it moved to the completed pile properly and the
2 of clubs remained in play

So, I can not repeat the bug.

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

[kdeconnect] [Bug 340612] Android Gallery does not update after filetransfer

[Robert G . Siebeck via KDE Bugzilla]

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

Robert G. Siebeck  changed:

   What|Removed |Added

 CC||kde.bugzilla.2...@r123.de

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

[plasma-nm] [Bug 357354] New: Show BSSID in connection detail

[Daniel Vrátil via KDE Bugzilla]

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

Bug ID: 357354
   Summary: Show BSSID in connection detail
   Product: plasma-nm
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: dvra...@kde.org
CC: lu...@kde.org

It would be very nice to have current BSSID in "Details" of each wireless
access point (or at least active wireless connection).

This is useful when you are connected to a network with multiple APs and want
to know which of the APs you are actually connected to right now.

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

[kdevelop] [Bug 357355] New: Crash on old session remove

[Raúl via KDE Bugzilla]

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

Bug ID: 357355
   Summary: Crash on old session remove
   Product: kdevelop
   Version: 4.7.1
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rasas...@gmail.com

Application: kdevelop (4.7.1)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.3.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

I opened kdevelop after long time without using it. I have session holding only
one old project. I started a new session, after the session was opened, I went
back to the old session and remove it from the session menu. kdevelop crashed.

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

Thread 7 (Thread 0x7f8d70fed700 (LWP 5651)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8d88d18d2a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f8d88d18d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f8d8762c284 in start_thread (arg=0x7f8d70fed700) at
pthread_create.c:333
#4  0x7f8d8b15674d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f8cef258700 (LWP 5654)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f8d8b808394 in QWaitConditionPrivate::wait (time=1000,
this=0x307edc0) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=this@entry=0x2e76468,
mutex=mutex@entry=0x2e76470, time=time@entry=1000) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f8d8a115f16 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x2e76450) at
/build/kdevplatform-Y8NEm6/kdevplatform-1.7.1/language/duchain/duchain.cpp:283
#4  0x7f8d8b807e4c in QThreadPrivate::start (arg=0x2e76450) at
thread/qthread_unix.cpp:352
#5  0x7f8d8762c284 in start_thread (arg=0x7f8cef258700) at
pthread_create.c:333
#6  0x7f8d8b15674d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f8ce1d04700 (LWP 5655)):
#0  0x7ffed2578caf in clock_gettime ()
#1  0x7f8d8b16357d in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f8ce1d03a10) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f8d8b862795 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7f8d8b949215 in QTimerInfoList::updateCurrentTime
(this=0x7f8cdc002ed0) at kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7f8cdc002ed0, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7f8d8b947adc in timerSourcePrepareHelper (src=,
timeout=0x7f8ce1d03ac4) at kernel/qeventdispatcher_glib.cpp:136
#7  0x7f8d84f9a75d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f8d84f9b0fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f8d84f9b2dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f8d8b9483a6 in QEventDispatcherGlib::processEvents
(this=0x7f8cdc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#11 0x7f8d8b9162e1 in QEventLoop::processEvents
(this=this@entry=0x7f8ce1d03c90, flags=...) at kernel/qeventloop.cpp:149
#12 0x7f8d8b916655 in QEventLoop::exec (this=this@entry=0x7f8ce1d03c90,
flags=...) at kernel/qeventloop.cpp:204
#13 0x7f8d8b805559 in QThread::exec (this=) at
thread/qthread.cpp:538
#14 0x7f8d8b807e4c in QThreadPrivate::start (arg=0x317e0e8) at
thread/qthread_unix.cpp:352
#15 0x7f8d8762c284 in start_thread (arg=0x7f8ce1d04700) at
pthread_create.c:333
#16 0x7f8d8b15674d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f8cbebc6700 (LWP 5676)):
#0  0x7f8d84f9ab2c in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f8d84f9b170 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8d84f9b2dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8d8b9483a6 in QEventDispatcherGlib::processEvents
(this=0x7f8cb8003080, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x7f8d8b9162e1 in QEventLoop::processEvents
(this=this@entry=0x7f8cbebc5c40, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f8d8b916655 in QEventLoop::exec (this=this@entry=0x7f8cbebc5c40,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f8d8b805559 in QThread::exec (this=this@entry=0x40ff2b0) at
thread/qthread.cpp:538
#7  0x7f8d8b8f6343 in 

[plasmashell] [Bug 343246] plasma 5 doesn't allow different wallpapers and widgets for each virtual desktop

[via KDE Bugzilla]

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

tuxfus...@gmail.com changed:

   What|Removed |Added

 CC||tuxfus...@gmail.com

--- Comment #38 from tuxfus...@gmail.com ---
The amount of people wanting this feature back is a perfect example of the
state of KDE. Developers ignore the end user. "I'm the developer, I know best".
http://linuxfonts.narod.ru/why.linux.is.not.ready.for.the.desktop.current.html

"Activities were ment to do that better.." People hate activities! You force
something on peoples brains no one gets -> kill THAT. I can easily be convinced
of "feature B does that better, use it". I used activites for 60 seconds found
the first bug ( You can't ORDER them, seriously ?) of this so called "way more
refined way to do things" 

Linux based desktops used to openly boast ( me too!) of the super simple and
cool system of virtual desktops. You could easily "impress" people of a Linux
desktop with that feature. Windows for example neglected that completely. Now,
in the same year that MS finally copies that feature in W10, you wizards of KDE
take the first shot at it. Yes, of course it's still there. But read closely
above, people will not switch to plasma 5 for simple stuff like this. Going
back to 4 again ( this is the third time for me ...) until you guys figure out
an answer to the question "why do we develop software in the first place"

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

[krita] [Bug 357342] doesn't open a new raw file and a saved file, it just was black

[via KDE Bugzilla]

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

--- Comment #2 from alissaroe...@gmail.com ---
Hi,

thanks for your answer. This is everytime when I create a new image. I use the
newest krita update. And about the last thing i don't really know what it is,
i'm sorry.

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

[kwin] [Bug 356557] Add "Fullscreen window" matching

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #27 from Thomas Lübking  ---
ok, sorry i missed that you're just trolling. thanks for wasting my time and
welcome to my sa blacklist.

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

[plasmashell] [Bug 357316] Plasma 5 random crashes openSUSE Leap

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---


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

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

[plasmashell] [Bug 356454] 4k TV Crash On Resume

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---


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

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

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

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||flas...@hotmail.com

--- Comment #6 from David Edmundson  ---
*** Bug 356454 has been marked as a duplicate of this bug. ***

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

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

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||linus.kardell+kdebugs@gmail
   ||.com

--- Comment #7 from David Edmundson  ---
*** Bug 357316 has been marked as a duplicate of this bug. ***

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

[Baloo] [Bug 357300] plasmashell crash - mdb_env_pick_meta (env=0x7f634c178970) at mdb.c:3709

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||pinak.ah...@gmail.com
  Component|general |General
Product|plasmashell |Baloo
   Target Milestone|1.0 |---
   Assignee|k...@davidedmundson.co.uk|m...@vhanda.in
Version|5.5.2   |unspecified

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

[kmail2] [Bug 357269] Can't import custom message list aggregation and theme from older config

[JHF2442 via KDE Bugzilla]

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

--- Comment #4 from JHF2442  ---
Created attachment 96371
  --> https://bugs.kde.org/attachment.cgi?id=96371=edit
theme from older kmail2

This is one of my import trials

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

[kdenlive] [Bug 357324] Project Settings / Video Profile Profile Button no function/icon

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kden
   ||live/7452cedabe8245f5d48f06
   ||e901aa68b343d32988
 Resolution|--- |FIXED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 7452cedabe8245f5d48f06e901aa68b343d32988 by Jean-Baptiste Mardelle.
Committed on 30/12/2015 at 21:58.
Pushed by mardelle into branch 'Applications/15.12'.

Fix manage project profiles broken in project settings

M  +4-0src/project/dialogs/projectsettings.cpp

http://commits.kde.org/kdenlive/7452cedabe8245f5d48f06e901aa68b343d32988

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

[akregator] [Bug 161543] Wrong date format used - system settings ignored

[Tom Chiverton via KDE Bugzilla]

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

Tom Chiverton  changed:

   What|Removed |Added

 CC||bugs.kde@falkensweb.com

--- Comment #2 from Tom Chiverton  ---
This has regressed in Kontact 5.0.2

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

[akregator] [Bug 335748] Information in date columns unclear, no controls to clarify

[Tom Chiverton via KDE Bugzilla]

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

Tom Chiverton  changed:

   What|Removed |Added

 CC||bugs.kde@falkensweb.com

--- Comment #1 from Tom Chiverton  ---
In Kontact 5.0.2 here, the Date's are in back-to-front american (MM/DD/YY)
further back than a week, despite my date and time settings being for the UK
(DD/MM/YY) defaults.

There's no GUI in the Akregator settings to alter this, and it's clearly not
getting it from the main KDE settings either.

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

[kdeconnect] [Bug 340152] Folder "does not exist" error when browsing external SD card folder over SFTP

[Robert G . Siebeck via KDE Bugzilla]

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

Robert G. Siebeck  changed:

   What|Removed |Added

 CC||kde.bugzilla.2...@r123.de

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

[kdenlive] [Bug 357322] Clip Properties: rounded frame rate, b/s vs kb/s, superfluous digit in audio bitrate

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 65f5f6544cff77e2016e8003e9ebe051d19dd1f2 by Jean-Baptiste Mardelle.
Committed on 30/12/2015 at 22:39.
Pushed by mardelle into branch 'Applications/15.12'.

Fix wrong rounding and other small issues in clip properties display

M  +14   -13   src/mltcontroller/clippropertiescontroller.cpp

http://commits.kde.org/kdenlive/65f5f6544cff77e2016e8003e9ebe051d19dd1f2

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

[plasmashell] [Bug 357352] New: Device Notifier appears when clicking a different tray icon after a device is connected

[Dan via KDE Bugzilla]

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

Bug ID: 357352
   Summary: Device Notifier appears when clicking a different tray
icon after a device is connected
   Product: plasmashell
   Version: 5.2.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: gandalfdagr...@gmail.com

After connecting a device (in my case, an Android phone), the Device Notifier
doesn't always appear. However, the next time I click a different tray icon
(reproduced with both Media Player and the Status and Notifications dropdown),
Device Notifier appears instead of the desired applet. If I close Device
Notifier and click the other icon again, the correct applet appears.

Reproducible: Always

Steps to Reproduce:
1. Connect a device such as an Android phone (you may need to then disconnect
it and reconnect it).
2. Click a tray icon other than Device Notifier.

Actual Results:  
Device Notifier appears.

Expected Results:  
The applet corresponding to the clicked icon should appear.

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

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[Matt Hubert via KDE Bugzilla]

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

Matt Hubert  changed:

   What|Removed |Added

 CC||m...@cfxnetworks.com

--- Comment #6 from Matt Hubert  ---
+1. Recent addresses are fine, Google Contacts all show up correctly in
KAddressBook, but no autocomplete anymore in KMail composer.

KMail 5.0.2
KF 5.15.0
Kubuntu 15.10

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

[kdenlive] [Bug 351512] Freeze when importing clips without a clip monitor

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[digikam] [Bug 357356] New: Digikam crash on startup while scanning photos

[Tyler via KDE Bugzilla]

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

Bug ID: 357356
   Summary: Digikam crash on startup while scanning photos
   Product: digikam
   Version: 4.13.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: k...@gden.com

Application: digikam (4.13.0)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.18.8-201.fc21.x86_64 x86_64
Distribution: "Fedora release 21 (Twenty One)"

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

Starting up a new install of digikam.  Every time the app starts up, it crashes
at about 20% into scanning my photos directory.  Debug output, GStreamer
reports bad file descriptor.

I completely un-installed and removed all config files.   Re-installed and
duplicated the same issue.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
18562:movl(%rsp), %edi
[Current thread is 1 (Thread 0x7f3d8694db00 (LWP 31186))]

Thread 3 (Thread 0x7f3d4c5ff700 (LWP 31188)):
[KCrash Handler]
#6  0x7f3d791aa8d7 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7f3d791ac53a in __GI_abort () at abort.c:89
#8  0x7f3d791edda3 in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7f3d792fd2f0 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7f3d791f99f5 in __GI___libc_free (ptr=,
str=0x7f3d792fd338 "free(): invalid next size (fast)", action=)
at malloc.c:4974
#10 0x7f3d791f99f5 in __GI___libc_free (have_lock=0, p=,
av=) at malloc.c:3841
#11 0x7f3d791f99f5 in __GI___libc_free (mem=) at
malloc.c:2951
#12 0x7f3d768696d3 in Exiv2::QuickTimeVideo::userDataDecoder(unsigned long)
() at /lib64/libexiv2.so.13
#13 0x7f3d7686872b in Exiv2::QuickTimeVideo::tagDecoder(Exiv2::DataBuf&,
unsigned long) () at /lib64/libexiv2.so.13
#14 0x7f3d76868ae0 in Exiv2::QuickTimeVideo::decodeBlock() () at
/lib64/libexiv2.so.13
#15 0x7f3d76868d55 in Exiv2::QuickTimeVideo::readMetadata() () at
/lib64/libexiv2.so.13
#16 0x7f3d848c9e7d in KExiv2Iface::KExiv2::load(QString const&) const
(this=this@entry=0x7f3d44421ac0, filePath=...) at
/usr/src/debug/libkexiv2-14.12.3/libkexiv2/kexiv2.cpp:310
#17 0x7f3d83f54e76 in Digikam::DMetadata::load(QString const&) const
(this=this@entry=0x7f3d44421ac0, filePath=...) at
/usr/src/debug/digikam-4.13.0/core/libs/dmetadata/dmetadata.cpp:110
#18 0x7f3d8396f067 in Digikam::ImageScanner::loadFromDisk()
(this=this@entry=0x7f3d4c5fe030) at
/usr/src/debug/digikam-4.13.0/core/libs/database/imagescanner.cpp:1550
#19 0x7f3d8396f250 in Digikam::ImageScanner::newFile(int)
(this=this@entry=0x7f3d4c5fe030, albumId=albumId@entry=337) at
/usr/src/debug/digikam-4.13.0/core/libs/database/imagescanner.cpp:289
#20 0x7f3d838ff7e6 in Digikam::CollectionScanner::scanNewFile(QFileInfo
const&, int) (this=this@entry=0x7f3d4c5fea90, info=..., albumId=337) at
/usr/src/debug/digikam-4.13.0/core/libs/database/collectionscanner.cpp:1255
#21 0x7f3d83902ed2 in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) (this=this@entry=0x7f3d4c5fea90, location=..., album=...) at
/usr/src/debug/digikam-4.13.0/core/libs/database/collectionscanner.cpp:1090
#22 0x7f3d83902d8f in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) (this=this@entry=0x7f3d4c5fea90, location=..., album=...) at
/usr/src/debug/digikam-4.13.0/core/libs/database/collectionscanner.cpp:1113
#23 0x7f3d83902d8f in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) (this=this@entry=0x7f3d4c5fea90, location=..., album=...) at
/usr/src/debug/digikam-4.13.0/core/libs/database/collectionscanner.cpp:1113
#24 0x7f3d83902d8f in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) (this=this@entry=0x7f3d4c5fea90, location=..., album=...) at
/usr/src/debug/digikam-4.13.0/core/libs/database/collectionscanner.cpp:1113
#25 0x7f3d83903723 in
Digikam::CollectionScanner::scanAlbumRoot(Digikam::CollectionLocation const&)
(this=this@entry=0x7f3d4c5fea90, location=...) at
/usr/src/debug/digikam-4.13.0/core/libs/database/collectionscanner.cpp:829
#26 0x7f3d83904f75 in Digikam::CollectionScanner::completeScan()
(this=this@entry=0x7f3d4c5fea90) at
/usr/src/debug/digikam-4.13.0/core/libs/database/collectionscanner.cpp:490
#27 0x005e9840 in Digikam::ScanController::run() (this=0x1a280b0) at
/usr/src/debug/digikam-4.13.0/core/app/database/scancontroller.cpp:756
#28 0x7f3d79f6e41f 

[frameworks-kcoreaddons] [Bug 357306] Build Broken on Windows

[Michael Pyne via KDE Bugzilla]

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

Michael Pyne  changed:

   What|Removed |Added

   Version Fixed In||5.18
  Latest Commit||http://commits.kde.org/kcor
   ||eaddons/caf9e50da1d6ac94bfc
   ||844a4ba688a10aee851c0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Michael Pyne  ---
Git commit caf9e50da1d6ac94bfc844a4ba688a10aee851c0 by Michael Pyne.
Committed on 31/12/2015 at 02:07.
Pushed by mpyne into branch 'master'.

Fix multiline QStringLiteral usage to build on Windows.

Instead of using ::fromLatin1() I just used + to concatenate the string
literals. Both affected autotests still pass. Please reopen if build
still fails on Windows.
FIXED-IN:5.18

M  +4-4autotests/ktexttohtmltest.cpp

http://commits.kde.org/kcoreaddons/caf9e50da1d6ac94bfc844a4ba688a10aee851c0

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

[kdevelop] [Bug 353863] crash parsing a kdev-qmake project (Qt 5.5.0 qtbase.pro)

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

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

--- Comment #4 from Kevin Funk  ---


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

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

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

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||christof.hanke@induhviduals
   ||.de

--- Comment #15 from Kevin Funk  ---
*** Bug 357358 has been marked as a duplicate of this bug. ***

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

[kontact] [Bug 355439] kontact crashed after updating an event

[Dj YB via KDE Bugzilla]

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

--- Comment #3 from Dj YB  ---
Thanks,
It did not happen again yet, when it does I will do as you said.

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

[kde] [Bug 357331] New: Konsole does not work properly when opened on secondary screen

[via KDE Bugzilla]

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

Bug ID: 357331
   Summary: Konsole does not work properly when opened on
secondary screen
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: maldun.finsterschr...@gmail.com

Application: kdeinit5 (15.08.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.8-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
- What I was doing when the application crashed:
Open Konsole on secondary Monitor

- Unusual behavior I noticed:
Within the window one sees everything in the Background (like a screenshot).
When moving the Window this snapshot remains.
When Closing Konsole crashes from time to time.

-My System: Intel i7 with Nvidia GeForce GTX 750 Ti. Driver number 358

-- Backtrace:
Application: Konsole (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc558e008c0 (LWP 3495))]

Thread 2 (Thread 0x7fc536fd4700 (LWP 3496)):
[KCrash Handler]
#5  0x7fc555b32a98 in raise () at /lib64/libc.so.6
#6  0x7fc555b3469a in abort () at /lib64/libc.so.6
#7  0x7fc555b75e3a in  () at /lib64/libc.so.6
#8  0x7fc555b7fe0e in _int_malloc () at /lib64/libc.so.6
#9  0x7fc555b824ca in calloc () at /lib64/libc.so.6
#10 0x7fc5507b33e3 in  () at /lib64/libnvidia-tls.so.358.16
#11 0x7fc55406d531 in g_malloc0 () at /lib64/libglib-2.0.so.0
#12 0x7fc554084fcd in g_slice_free1 () at /lib64/libglib-2.0.so.0
#13 0x7fc5552393b9 in __nptl_deallocate_tsd.part.4 () at
/lib64/libpthread.so.0
#14 0x7fc55523a7a9 in start_thread () at /lib64/libpthread.so.0
#15 0x7fc555c00a9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc558e008c0 (LWP 3495)):
#0  0x7fc5507b1e15 in _nv014tls () at /lib64/libnvidia-tls.so.358.16
#1  0x7fc553d9abad in  () at /usr/lib64/nvidia/libGL.so.1
#2  0x7fc553d9af78 in  () at /usr/lib64/nvidia/libGL.so.1
#3  0x7fc553d9b06a in  () at /usr/lib64/nvidia/libGL.so.1
#4  0x7fc553dde365 in  () at /usr/lib64/nvidia/libGL.so.1
#5  0x7fc558cd3d25 in _dl_fini () at /lib64/ld-linux-x86-64.so.2
#6  0x7fc555b37658 in __run_exit_handlers () at /lib64/libc.so.6
#7  0x7fc555b376a5 in  () at /lib64/libc.so.6
#8  0x557585ba6777 in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) ()
#9  0x557585ba7ffe in handle_launcher_request(int, char const*) [clone
.isra.24] ()
#10 0x557585ba857b in handle_requests(int) ()
#11 0x557585ba314a in main ()

Reported using DrKonqi

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

[kdevelop] [Bug 194403] ability to configure verbosity of compiler output is lost

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||kf...@kde.org
   Target Milestone|--- |5.0.0

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

[kde] [Bug 357331] Konsole does not work properly when opened on secondary screen

[via KDE Bugzilla]

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

maldun.finsterschr...@gmail.com changed:

   What|Removed |Added

   Platform|unspecified |Fedora RPMs

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

[kde] [Bug 357331] Konsole does not work properly when opened on secondary screen

[via KDE Bugzilla]

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

--- Comment #2 from maldun.finsterschr...@gmail.com ---
BtW: It looks like QTerminal works correctly

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

[kde] [Bug 357331] Konsole does not work properly when opened on secondary screen

[via KDE Bugzilla]

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

--- Comment #1 from maldun.finsterschr...@gmail.com ---
Here the output when I open Konsole from another terminal:

[maldun@drachenhorst ~]$ konsole
QCoreApplication::arguments: Please instantiate the QApplication object first
[maldun@drachenhorst ~]$ The font for use in the terminal has not been matched
exactly. Perhaps it has not been found properly.
The font for use in the terminal has not been matched exactly. Perhaps it has
not been found properly.
0x560ac1a3c640 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a3d1c0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a3eb70 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a3e1b0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a3dd10 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a3d8e0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a33740 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a33bc0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a340a0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a34540 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a34a60 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a34f80 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a354a0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a3e690 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a41230 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a41a10 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a42160 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a44190 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a3dd10 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16c76c0) ): Attempt to set a screen on a child window.
0x560ac1a42160 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16c76c0) ): Attempt to set a screen on a child window.
0x560ac1a2b990 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16d0ba0) ): Attempt to set a screen on a child window.
0x560ac1a3d1c0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16c76c0) ): Attempt to set a screen on a child window.
0x560ac1a3eb70 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16c76c0) ): Attempt to set a screen on a child window.
0x560ac1a3e1b0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16c76c0) ): Attempt to set a screen on a child window.
0x560ac1a3dd10 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16c76c0) ): Attempt to set a screen on a child window.
0x560ac1a42160 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16c76c0) ): Attempt to set a screen on a child window.
0x560ac1a3c640 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x560ac16c76c0) ): Attempt to set a screen on a child window.
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2059, resource id:
119537795, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2062, resource id:
119537795, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2065, resource id:
119537795, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2068, resource id:
119537795, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2071, resource id:
119537795, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 

[kwin] [Bug 357311] plastik decorations: Color scheme changes are not applied immediately

[Alexander Schier via KDE Bugzilla]

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

--- Comment #4 from Alexander Schier  ---
It is IN Plastik and not in the default decoration. I can try some other
decorations later on the Fedora live cd i used, when it's needed.

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

[amarok] [Bug 357251] Amarok didn't play any audio, and crashes every time it is started after updating it today

[Geza via KDE Bugzilla]

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

--- Comment #6 from Geza  ---
There are still no line numbers, sorry!

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

[plasmashell] [Bug 357332] New: Not possible to open a new panel on second screen

[via KDE Bugzilla]

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

Bug ID: 357332
   Summary: Not possible to open a new panel on second screen
   Product: plasmashell
   Version: 5.5.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: slartibar...@gmail.com

The setup is as follows:
Laptop t420 with external hdmi monitor, both showing desktop folder

Trying to add a new panel (a second one) to the second/hdmi monitor (idea is to
have the laptop monitor/lid closed and i want a second aplication-kicker and
taskmanager on monitor2)

All new panels (the 'default' or 'empty' panel) always land on the laptop
screen, there is no way of moving it to the second screen
And, playing around with the panel, plasma continuously crashes after removing
the 'unwanted' panel on the laptop screen.

Reproducible: Always

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

[Breeze] [Bug 357334] New: Missing icon for status/mail-*

[Olivier Churlaud via KDE Bugzilla]

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

Bug ID: 357334
   Summary: Missing icon for status/mail-*
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Icons
  Assignee: uri_herr...@nitrux.in
  Reporter: oliv...@churlaud.com
CC: kain...@gmail.com

The icons for status/mail-attachment
mail-queued
mail-read
mail-replied
mail-tagged
mail-unread-new
mail-unread

are missing


Reproducible: Always

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

[telepathy] [Bug 353325] Can't connect to jabber servers which require forward secrecy

[Christoph Erhardt via KDE Bugzilla]

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

Christoph Erhardt  changed:

   What|Removed |Added

 CC||k...@sicherha.de

--- Comment #5 from Christoph Erhardt  ---
I did some testing on Fedora 23.

* Empathy successfully connects to jabber.ccc.de. (Side note: It constantly
complains that the CAcert certificate is untrusted - even after I ticked the
checkbox "Remember this choice for future connections".)
* KDE Telepathy always fails to connect: "There was a network error, check your
connection". There is no warning concerning the certificate.

I'm relatively sure that the issue has nothing to do with forward secrecy. I
have a secondary XMPP account on another server that deploys PFS, and KDE
Telepathy has no problems connecting to that account. Maybe it's an issue with
the untrusted server certificate?

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

[kdeplasma-addons] [Bug 357333] New: comic widget doesn't save the image

[Eugenio via KDE Bugzilla]

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

Bug ID: 357333
   Summary: comic widget doesn't save the image
   Product: kdeplasma-addons
   Version: 5.5.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Comic Applet
  Assignee: notm...@gmail.com
  Reporter: eugeni...@gmail.com

"save image" doesn't work.
The first time I try to save the name of the image is correct but then it's
wrong (it sums all the names used before).
Also it doesn't save the image at all (changing name doesn't work).
It's completely broken.

Reproducible: Always

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

[kdelibs] [Bug 357330] New: Cannot cancel a download from the KNewStuff interface

[Akarsh Simha via KDE Bugzilla]

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

Bug ID: 357330
   Summary: Cannot cancel a download from the KNewStuff interface
   Product: kdelibs
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: knewstuff
  Assignee: jpwhit...@kde.org
  Reporter: akarsh.si...@kdemail.net
CC: gladh...@kde.org

KStars uses the KNewStuff interface to download large data (1.4 GB size). Many
users do not realize the size of the download and may want to cancel it.
However, no such provision exists. Closing the KNS interface or the application
does not terminate the download. (I think a terminal interrupt does, though).

A button to cancel the download process, and also a way to show some of the
download progress would be helpful.

Reproducible: Always

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