[kmail2] [Bug 368136] email only renders to a quarter of its designated space

[Lukas Schneiderbauer via KDE Bugzilla]

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

--- Comment #1 from Lukas Schneiderbauer  ---
Created attachment 100892
  --> https://bugs.kde.org/attachment.cgi?id=100892=edit
screenshot of kmail

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

[kmail2] [Bug 368136] New: email only renders to a quarter of its designated space

[Lukas Schneiderbauer via KDE Bugzilla]

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

Bug ID: 368136
   Summary: email only renders to a quarter of its designated
space
   Product: kmail2
   Version: 5.2.1
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: lukas.schneiderba...@gmail.com

Kmail version: 5.3.0 /16.08.0 (was not pickable above)
Qt: 5.6.1

Email on my hidpi screen only renders to a quarter of its designated space,
see screenshot soon to be attached.
This also happens when "opening" the email into a new window.

Let me know if you need additional info.

Reproducible: Always

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

[frameworks-kwindowsystem] [Bug 368023] Window system freezes temporarily on application switch

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Martin Gräßlin  ---
> KWin version: 5.5.5
> Qt Version: 5.5.1

Please upgrade to newer version of both Plasma an Qt. Especially Qt is rather
old and known to have had issues. There is a fair amount of chance that the
problem is fixed with newer versions. Also it's close to impossible for us to
investigate for such old software.

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

[kmail2] [Bug 368135] New: Kmail crashes every time when I try to preview certain emails

[Kilavagora via KDE Bugzilla]

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

Bug ID: 368135
   Summary: Kmail crashes every time when I try to preview certain
emails
   Product: kmail2
   Version: 5.1.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kilavag...@hotmail.com

Application: kmail (5.1.3)

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

-- Information about the crash:
- What I was doing when the application crashed: Certain emails crash kmail.
E.g. this time I was just trying to preview email from Bestbuy.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Floating point exception
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fad65210800 (LWP 2166))]

Thread 21 (Thread 0x7facb8b16700 (LWP 2545)):
#0  0x7fad6221dbfd in poll () at /lib64/libc.so.6
#1  0x7fad58495e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fad58495f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fad62d61d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fad62d08d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fad62b2a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fad62b2f32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fad589b20a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fad6222602d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7facb9ffb700 (LWP 2494)):
#0  0x7fad584d7cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fad584958fc in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fad58495df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fad58495f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fad62d61d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fad62d08d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fad62b2a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fad62b2f32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fad589b20a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fad6222602d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7facba7fc700 (LWP 2477)):
#0  0x7fad584d7cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fad58495e4a in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fad58495f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fad62d61d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fad62d08d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fad62b2a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fad62b2f32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fad589b20a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fad6222602d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7facbaffd700 (LWP 2475)):
#0  0x7fad6221dbfd in poll () at /lib64/libc.so.6
#1  0x7fad58495e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fad58495f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fad62d61d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fad62d08d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fad62b2a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fad62b2f32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fad589b20a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fad6222602d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7facbb7fe700 (LWP 2471)):
#0  0x7fad584d7cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fad58495e4a in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fad58495f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fad62d61d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fad62d08d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fad62b2a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fad62b2f32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fad589b20a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fad6222602d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7facbbfff700 (LWP 2469)):
#0  0x7fad6221dbfd in poll () at /lib64/libc.so.6
#1  0x7fad58495e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fad58495f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fad62d61d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at 

[kde] [Bug 368133] New: Plasma Crash modifying panel widgets

[Katie Roberts via KDE Bugzilla]

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

Bug ID: 368133
   Summary: Plasma Crash modifying panel widgets
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: noc...@psychohalflife.com

Application: plasma-desktop (4.11.11)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 4.4.0-34-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed: Attempting to modify panel
widgets, add system tray widget. Using 2 displays both with similar panels

- Unusual behavior I noticed: started stuttering hard, wouldn't respond, acted
as if it added wdiget but saw no widget

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

Thread 5 (Thread 0x7fb929e1e700 (LWP 2522)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb94c526ffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7fb94c527039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7fb94709d184 in start_thread (arg=0x7fb929e1e700) at
pthread_create.c:312
#4  0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fb8a46a4700 (LWP 2523)):
#0  0x7fffe1d9bd7f in clock_gettime ()
#1  0x7fb95317685d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fb94fc61ad7 in do_gettime (frac=0x7fb8a46a3b70, sec=0x7fb8a46a3b68)
at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fb94fd3df05 in updateCurrentTime (this=0x7fb89c003130) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fb89c003130, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fb94fd3c67c in timerSourcePrepareHelper (src=,
timeout=0x7fb8a46a3c24) at kernel/qeventdispatcher_glib.cpp:143
#7  0x7fb94fd3c725 in timerSourcePrepare (source=,
timeout=) at kernel/qeventdispatcher_glib.cpp:176
#8  0x7fb94698b68d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fb94698bf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fb94698c0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fb94fd3c7be in QEventDispatcherGlib::processEvents
(this=0x7fb89c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#12 0x7fb94fd0e0af in QEventLoop::processEvents
(this=this@entry=0x7fb8a46a3de0, flags=...) at kernel/qeventloop.cpp:149
#13 0x7fb94fd0e3a5 in QEventLoop::exec (this=this@entry=0x7fb8a46a3de0,
flags=...) at kernel/qeventloop.cpp:204
#14 0x7fb94fc0ac5f in QThread::exec (this=this@entry=0x2045f50) at
thread/qthread.cpp:537
#15 0x7fb94fcef823 in QInotifyFileSystemWatcherEngine::run (this=0x2045f50)
at io/qfilesystemwatcher_inotify.cpp:265
#16 0x7fb94fc0d32f in QThreadPrivate::start (arg=0x2045f50) at
thread/qthread_unix.cpp:349
#17 0x7fb94709d184 in start_thread (arg=0x7fb8a46a4700) at
pthread_create.c:312
#18 0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fb8a21b2700 (LWP 2525)):
#0  0x7fb9469cd9b1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb94698bbda in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb94698c048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb94698c30a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb8a2cae336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7fb9469b0f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fb94709d184 in start_thread (arg=0x7fb8a21b2700) at
pthread_create.c:312
#7  0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fb8a1339700 (LWP 2526)):
#0  0x7fffe1d9bd7f in clock_gettime ()
#1  0x7fb95317685d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fb94fc61ad7 in do_gettime (frac=0x7fb8a1338b70, sec=0x7fb8a1338b68)
at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fb94fd3df05 in updateCurrentTime (this=0x7fb88c002930) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fb88c002930, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fb94fd3c67c in timerSourcePrepareHelper (src=,
timeout=0x7fb8a1338c24) at kernel/qeventdispatcher_glib.cpp:143
#7  0x7fb94fd3c725 

[kde] [Bug 368134] New: Plasma Crash modifying panel widgets

[Katie Roberts via KDE Bugzilla]

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

Bug ID: 368134
   Summary: Plasma Crash modifying panel widgets
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: noc...@psychohalflife.com

Application: plasma-desktop (4.11.11)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 4.4.0-34-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed: Attempting to modify panel
widgets, add system tray widget. Using 2 displays both with similar panels

- Unusual behavior I noticed: started stuttering hard, wouldn't respond, acted
as if it added wdiget but saw no widget

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

Thread 5 (Thread 0x7fb929e1e700 (LWP 2522)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb94c526ffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7fb94c527039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7fb94709d184 in start_thread (arg=0x7fb929e1e700) at
pthread_create.c:312
#4  0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fb8a46a4700 (LWP 2523)):
#0  0x7fffe1d9bd7f in clock_gettime ()
#1  0x7fb95317685d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fb94fc61ad7 in do_gettime (frac=0x7fb8a46a3b70, sec=0x7fb8a46a3b68)
at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fb94fd3df05 in updateCurrentTime (this=0x7fb89c003130) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fb89c003130, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fb94fd3c67c in timerSourcePrepareHelper (src=,
timeout=0x7fb8a46a3c24) at kernel/qeventdispatcher_glib.cpp:143
#7  0x7fb94fd3c725 in timerSourcePrepare (source=,
timeout=) at kernel/qeventdispatcher_glib.cpp:176
#8  0x7fb94698b68d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fb94698bf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fb94698c0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fb94fd3c7be in QEventDispatcherGlib::processEvents
(this=0x7fb89c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#12 0x7fb94fd0e0af in QEventLoop::processEvents
(this=this@entry=0x7fb8a46a3de0, flags=...) at kernel/qeventloop.cpp:149
#13 0x7fb94fd0e3a5 in QEventLoop::exec (this=this@entry=0x7fb8a46a3de0,
flags=...) at kernel/qeventloop.cpp:204
#14 0x7fb94fc0ac5f in QThread::exec (this=this@entry=0x2045f50) at
thread/qthread.cpp:537
#15 0x7fb94fcef823 in QInotifyFileSystemWatcherEngine::run (this=0x2045f50)
at io/qfilesystemwatcher_inotify.cpp:265
#16 0x7fb94fc0d32f in QThreadPrivate::start (arg=0x2045f50) at
thread/qthread_unix.cpp:349
#17 0x7fb94709d184 in start_thread (arg=0x7fb8a46a4700) at
pthread_create.c:312
#18 0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fb8a21b2700 (LWP 2525)):
#0  0x7fb9469cd9b1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb94698bbda in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb94698c048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb94698c30a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb8a2cae336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7fb9469b0f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fb94709d184 in start_thread (arg=0x7fb8a21b2700) at
pthread_create.c:312
#7  0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fb8a1339700 (LWP 2526)):
#0  0x7fffe1d9bd7f in clock_gettime ()
#1  0x7fb95317685d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fb94fc61ad7 in do_gettime (frac=0x7fb8a1338b70, sec=0x7fb8a1338b68)
at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fb94fd3df05 in updateCurrentTime (this=0x7fb88c002930) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fb88c002930, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fb94fd3c67c in timerSourcePrepareHelper (src=,
timeout=0x7fb8a1338c24) at kernel/qeventdispatcher_glib.cpp:143
#7  0x7fb94fd3c725 

[kde] [Bug 368132] New: Plasma Crash modifying panel widgets

[Katie Roberts via KDE Bugzilla]

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

Bug ID: 368132
   Summary: Plasma Crash modifying panel widgets
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: noc...@psychohalflife.com

Application: plasma-desktop (4.11.11)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 4.4.0-34-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed: Attempting to modify panel
widgets, add system tray widget. Using 2 displays both with similar panels

- Unusual behavior I noticed: started stuttering hard, wouldn't respond, acted
as if it added wdiget but saw no widget

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

Thread 5 (Thread 0x7fb929e1e700 (LWP 2522)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb94c526ffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7fb94c527039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7fb94709d184 in start_thread (arg=0x7fb929e1e700) at
pthread_create.c:312
#4  0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fb8a46a4700 (LWP 2523)):
#0  0x7fffe1d9bd7f in clock_gettime ()
#1  0x7fb95317685d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fb94fc61ad7 in do_gettime (frac=0x7fb8a46a3b70, sec=0x7fb8a46a3b68)
at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fb94fd3df05 in updateCurrentTime (this=0x7fb89c003130) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fb89c003130, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fb94fd3c67c in timerSourcePrepareHelper (src=,
timeout=0x7fb8a46a3c24) at kernel/qeventdispatcher_glib.cpp:143
#7  0x7fb94fd3c725 in timerSourcePrepare (source=,
timeout=) at kernel/qeventdispatcher_glib.cpp:176
#8  0x7fb94698b68d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fb94698bf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fb94698c0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fb94fd3c7be in QEventDispatcherGlib::processEvents
(this=0x7fb89c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#12 0x7fb94fd0e0af in QEventLoop::processEvents
(this=this@entry=0x7fb8a46a3de0, flags=...) at kernel/qeventloop.cpp:149
#13 0x7fb94fd0e3a5 in QEventLoop::exec (this=this@entry=0x7fb8a46a3de0,
flags=...) at kernel/qeventloop.cpp:204
#14 0x7fb94fc0ac5f in QThread::exec (this=this@entry=0x2045f50) at
thread/qthread.cpp:537
#15 0x7fb94fcef823 in QInotifyFileSystemWatcherEngine::run (this=0x2045f50)
at io/qfilesystemwatcher_inotify.cpp:265
#16 0x7fb94fc0d32f in QThreadPrivate::start (arg=0x2045f50) at
thread/qthread_unix.cpp:349
#17 0x7fb94709d184 in start_thread (arg=0x7fb8a46a4700) at
pthread_create.c:312
#18 0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fb8a21b2700 (LWP 2525)):
#0  0x7fb9469cd9b1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb94698bbda in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb94698c048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb94698c30a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb8a2cae336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7fb9469b0f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fb94709d184 in start_thread (arg=0x7fb8a21b2700) at
pthread_create.c:312
#7  0x7fb95316837d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fb8a1339700 (LWP 2526)):
#0  0x7fffe1d9bd7f in clock_gettime ()
#1  0x7fb95317685d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fb94fc61ad7 in do_gettime (frac=0x7fb8a1338b70, sec=0x7fb8a1338b68)
at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fb94fd3df05 in updateCurrentTime (this=0x7fb88c002930) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fb88c002930, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fb94fd3c67c in timerSourcePrepareHelper (src=,
timeout=0x7fb8a1338c24) at kernel/qeventdispatcher_glib.cpp:143
#7  0x7fb94fd3c725 

[kolourpaint] [Bug 368131] New: KolourPaint 16.08.0 ignores relative paths on the command line

[David Korth via KDE Bugzilla]

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

Bug ID: 368131
   Summary: KolourPaint 16.08.0 ignores relative paths on the
command line
   Product: kolourpaint
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kolourpaint-supp...@lists.sourceforge.net
  Reporter: gerbils...@gerbilsoft.com

KolourPaint 16.08.0 ignores relative paths on the command line. This seems to
be caused by QUrl::fromUserInput not handling relative pathnames.

Reproducible: Always

Steps to Reproduce:
1. In a terminal, cd to a directory containing an image file.
2. kolourpaint ./imagefile.png

Actual Results:  
KolourPaint opens a blank, untitled image.

Expected Results:  
KolourPaint opens imagefile.png.

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

[kmail2] [Bug 65760] Multiple signature selector would be nice

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #8 from Laurent Montel  ---
Signature depends against identity.
So I don't have idea how to add it without complexify interface.

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

[krita] [Bug 368119] Line Tool - strange line to corner

[via KDE Bugzilla]

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

--- Comment #3 from elk...@yahoo.com ---
Created attachment 100891
  --> https://bugs.kde.org/attachment.cgi?id=100891=edit
Video showing that issue also effects brush tool when using mouse

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

[KScreen] [Bug 351025] When external monitor is disconnected, the laptop monitor doesn't become active again

[zanetti357 via KDE Bugzilla]

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

zanetti357  changed:

   What|Removed |Added

 CC||zanetti_...@hotmail.com

--- Comment #35 from zanetti357  ---
(In reply to Sebastian Kügler from comment #34)
> A couple of causes for this bug have been fixed in the Plasma/5.8 branch.
> 
> If problems persists with the latest code, please file a separate report to
> keep the debugging history clean (this bug-report mixes different causes and
> effects).

Sorry Sebastian, would you please explain me how to install the latest
Plasma5.8? This problem is driving me crazy and I've just started using
Kubuntu.
Thanks in advance!

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

[krita] [Bug 368119] Line Tool - strange line to corner

[via KDE Bugzilla]

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

elk...@yahoo.com changed:

   What|Removed |Added

 CC||elk...@yahoo.com

--- Comment #2 from elk...@yahoo.com ---
This is another symptom of the issue I detailed in Comment 1 of the "finish
line" bug[364183]
https://bugs.kde.org/show_bug.cgi?id=364183

Since the resolution of 364183 didn't fix Comment 1, I figured it was a
separate problem and 
was going to create a new bug, but you beat me to it.

Some additional info. The issue from 364183, Comment 1,  does affect both Win &
Linux, but only happens when using a mouse for drawing. 

I've also added a video showing the issue with the brush tool.

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

[kmail2] [Bug 65760] Multiple signature selector would be nice

[Steeven Hudon via KDE Bugzilla]

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

Steeven Hudon  changed:

   What|Removed |Added

 CC||st...@hotmail.com

--- Comment #7 from Steeven Hudon  ---
I would also like to have that feature in Kmail2 : 

At work, I use Microsoft Outlook, and the multiple signatures feature  gives me
the opportunity to change every mail's signature to taste (depending on what I
included in my mail) - without having to have template-e-mails or anything like
it.  For example, for a standard mail, I could select any of theses three
signatures I would have created :
1. Thank you and have a nice day !  (default)
2. See file(s) attached.  Thank you and have a nice day !
3. Should you have any questions, do not hesitate to write us back. Thank you
and have a nice day !

It could be possible to create list of signatures and assign any of those
signatures as default for each Identity in Kmail, and then, when writing a
mail, to have the choice to select any of the other signatures available, when
required.

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

[krita] [Bug 368128] Stops working after switching tag/workspace in dwm

[via KDE Bugzilla]

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

--- Comment #1 from acc...@openmailbox.org ---
## Quick tutorial to setup and use dwm ##

On a shell:
$ git clone http://git.suckless.org/dwm
$ cd dwm
$ sudo make clean install
It's installed.

* You'll also need dmenu, which is probably packaged in your distro. Install it
with your package manager.
* Create a ~/.xinitrc file, put the line 'exec dwm' in it and save it.
* Switch to a TTY and run 'startx'.
You should be running dwm now.

* To launch Krita, press Alt+p, type krita, and press Return.
* To switch tags, use Alt+n, where n is the tag number.

This is all that's required to reproduce the bug. You can read the man page for
more information on getting around dwm.

## Reproducing the bug once Krita is running ##

1. Create a new file of any size
2. Scribble on it to verify that it's working (optional)
3. Switch to a different wm tag with Alt+n or by clicking on it in the status
bar.
4. Switch back to the Krita tag
5. Try to scribble on the canvas again.

At this point the bug will have already been triggered. You can change tools
and generally interact with the rest of the Krita UI, but nothing will work on
the canvas (except newly created ones) and other weird behavior will arise.
Saving won't work by any means. Closing the tab will hang Krita.

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #18 from Leslie Zhai  ---
Git commit f3f4602e30c67bf622b5a52ea39c78817b1dd020 by Leslie Zhai.
Committed on 02/09/2016 at 02:15.
Pushed by lesliezhai into branch 'master'.

Use growisofs for burning DVD/Blu-ray by default.

M  +3-2libk3b/jobs/k3bdvdcopyjob.cpp

http://commits.kde.org/k3b/f3f4602e30c67bf622b5a52ea39c78817b1dd020

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

[kate] [Bug 368130] New: Vi-mode search box disappears if used again while the search box is still open

[Simon Yuan via KDE Bugzilla]

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

Bug ID: 368130
   Summary: Vi-mode search box disappears if used again while the
search box is still open
   Product: kate
   Version: 16.04.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Vi Input Mode
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: siyuan...@gmail.com

In Vi-mode, if you search by, say using the shortcut ctrl + f, while the search
box is open, pressing ctrl + f again while the search box is still opened
causes the search box to disappear. Once the editor goes into this state, you
can never get the search box back until you reopen the editor.

I selected Version=16.04.1, but I'm actually using 16.08.

Reproducible: Always

Steps to Reproduce:
1. Search by using the menu or ctrl + f.
2. Search again without closing the search box by repeating step 1 once.
3. Any further attempts to search fails to bring up the search box.

Actual Results:  
You can never get the search box back once you trigger the bug.

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #17 from Leslie Zhai  ---
Hi Thomas,

Thanks for your detailed DVD background information, I will deep into it ;-)

> which i believe prevents the automatic use of growisofs

I will double check it!

> That will be a problem when you work on the DVD/BD code

yes! people often use clound or usb disk right now, so I have to borrow some
empty DVD/Blu-ray...

> So K3B did not properly determine the Next Writable Address (NWA)

yes, wrong 0,0 alleged_next_session, and I will also deep into it, very
interesting and it is able to learn some thing ;-)

Regards,
Leslie Zhai

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

[kdenlive] [Bug 367593] Kdenlive crashes immediately on opening

[via KDE Bugzilla]

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

rgl...@gmail.com changed:

   What|Removed |Added

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

--- Comment #4 from rgl...@gmail.com ---
Gentoo stable version of frei0r-plugins and opencv were using Qt4.
No crash with unstable versions.
Sorry, I should have searched the forums first...
https://forums.gentoo.org/viewtopic-t-881523-start-25.html

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

[kdevelop] [Bug 368129] New: Crash when switch between input modes

[Simon Yuan via KDE Bugzilla]

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

Bug ID: 368129
   Summary: Crash when switch between input modes
   Product: kdevelop
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: all editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: siyuan...@gmail.com

KDevelop crashes when switch from vi-mode to Normal after a search and/or
replace is performed. I'm unsure if it's a Kate bug or KDevelop, but the crash
cannot be reproduced with the same steps for KDevelop on Kate.

Reproducible: Always

Steps to Reproduce:
1. Open any file.
2. Search and/or replace.
3. Switch between Normal/vi-mode, although my observation is that it crashes
when switching from vi-mode to Normal.

Actual Results:  
KDevelop crashes


Stack trace from coredumpctl:
Stack trace of thread 15931:
#0  0x7fe9a94b723a _ZN6KateVi18EmulatedCommandBar6closedEv
(libKF5TextEditor.so.5)
#1  0x7fe9a93f2035 n/a (libKF5TextEditor.so.5)
#2  0x7fe9acfa74e9 _ZN11QMetaObject8activateEP7QObjectiiPPv
(libQt5Core.so.5)
#3  0x7fe9a9479f50 _ZN15KateViInputMode8activateEv
(libKF5TextEditor.so.5)
#4  0x7fe9a93d0310
_ZN11KTextEditor11ViewPrivate12setInputModeENS_4View9InputModeE
(libKF5TextEditor.so.5)
#5  0x7fe9a94e432a n/a (libKF5TextEditor.so.5)
#6  0x7fe9acfa74e9 _ZN11QMetaObject8activateEP7QObjectiiPPv
(libQt5Core.so.5)
#7  0x7fe9adc55472 _ZN7QAction9triggeredEb
(libQt5Widgets.so.5)
#8  0x7fe9adc57e60 _ZN7QAction8activateENS_11ActionEventE
(libQt5Widgets.so.5)
#9  0x7fe9adc587dc _ZN7QAction5eventEP6QEvent
(libQt5Widgets.so.5)
#10 0x7fe9adc5be3c
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
#11 0x7fe9adc635b1
_ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
#12 0x7fe9acf7bc80
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)

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

[krita] [Bug 368128] New: Stops working after switching tag/workspace in dwm

[via KDE Bugzilla]

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

Bug ID: 368128
   Summary: Stops working after switching tag/workspace in dwm
   Product: krita
   Version: 3.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: acc...@openmailbox.org

Every time I switch tags in dwm (http://dwm.suckless.org) Krita will stop
drawing on canvas. If I try to save the work it will display the message
"Waiting for image operation to complete..."
Everything else will still work, and I can even open a new canvas and draw on
it.
However if I close the non-working tab it will hang the entire application.

I tried reproducing this on i3 and awesome. Neither triggered this bug.

Reproducible: Always

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

[kwin] [Bug 362955] (Auto)Suspending compositing sometimes results in stale non-composited picture

[J . Daffodil via KDE Bugzilla]

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

--- Comment #6 from J. Daffodil  ---
I have this issue, and have had it for quite some time. I can trigger it
(almost) 100% of the time by turning off compositing using any method.

I've grabbed some screenshots in case it's useful. This:
http://i.imgur.com/9NfHLAw.png is the desktop before I disable compositing and
close the window. This: http://i.imgur.com/RXXL7qp.png is immediately after I
disable compositing.

I'm using openSUSE 42.1, kernel 4.1.27, Plasma 5.5.5, and an Nvidia 970 with
their driver (367.35). I've seen the issue consistently through at least a few
versions of openSUSE, KDE 4 and 5, and three different GPUs (all Nvidia, all
proprietary driver), though. I think I've also pretty much always used two or
more monitors with that computer.

kwin_x11 --replace does fix the issue for me, for a little while. I can then
disable compositing and everything functions like it should, for a while.
Disabling and re-enabling compositing afterwards will bring the issue back, but
not consistently. The issue might resurface the first time I disable
compositing again, or it might be ten "cycles" before it happens again.

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

[krita] [Bug 368127] "RESTORE DEFAULTS" in preferences button does not work with general settings,i tested with other settings it worked with all settings except general settings.Help button in prefe

[Rafael via KDE Bugzilla]

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

Rafael  changed:

   What|Removed |Added

URL||https://www.dropbox.com/s/v
   ||iz9pqwyyzgvsht/Screencast%2
   ||02016-09-02%2003%3A41%3A50.
   ||mp4?dl=0

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

[krita] [Bug 368127] New: "RESTORE DEFAULTS" in preferences button does not work with general settings,i tested with other settings it worked with all settings except general settings.Help button in

[Rafael via KDE Bugzilla]

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

Bug ID: 368127
   Summary: "RESTORE DEFAULTS" in preferences button does not work
 with general settings,i tested with other settings it
worked with all settings except general settings.Help
button in preferences doesnot work at all.Thanks for
attention
   Product: krita
   Version: 2.9.7
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: blackbloo...@mail.ru

"RESTORE DEFAULTS" in preferences button does not work  with general settings,i
tested with other settings it worked with all settings except general
settings.Help button in preferences doesnot work at all.Thanks for attention

Reproducible: Always

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

[dolphin] [Bug 362834] F4 doesn't open terminal in the current directory at least on MTP and SMB

[Viorel-Cătălin Răpițeanu via KDE Bugzilla]

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

--- Comment #1 from Viorel-Cătălin Răpițeanu  ---
This feature would be great if it would get implemented.
The same behaviour is seen for sftp as well.

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

[dolphin] [Bug 188794] Embedded Konsole follows fish path through ssh

[Viorel-Cătălin Răpițeanu via KDE Bugzilla]

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

Viorel-Cătălin Răpițeanu  changed:

   What|Removed |Added

 CC||rapiteanu.cata...@gmail.com

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

[dolphin] [Bug 362834] F4 doesn't open terminal in the current directory at least on MTP and SMB

[Viorel-Cătălin Răpițeanu via KDE Bugzilla]

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

Viorel-Cătălin Răpițeanu  changed:

   What|Removed |Added

 CC||rapiteanu.cata...@gmail.com

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

[kio] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway

[Viorel-Cătălin Răpițeanu via KDE Bugzilla]

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

Viorel-Cătălin Răpițeanu  changed:

   What|Removed |Added

 CC||rapiteanu.cata...@gmail.com

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

[frameworks-kwallet] [Bug 368126] KWallet can't open a gpg-encrypted wallet

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 100890
  --> https://bugs.kde.org/attachment.cgi?id=100890=edit
KWallet error message

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

[frameworks-kwallet] [Bug 368126] New: KWallet can't open a gpg-encrypted wallet

[Lastique via KDE Bugzilla]

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

Bug ID: 368126
   Summary: KWallet can't open a gpg-encrypted wallet
   Product: frameworks-kwallet
   Version: 5.18.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: andy...@mail.ru
CC: kdelibs-b...@kde.org

A newly created wallet with GPG backend cannot be opened.

Reproducible: Always

Steps to Reproduce:
1. Start Wallet Manager.
2. Create a new wallet (File->New), select GPG backend and an RSA-4096 GPG key.
3. When you select the key, an error appears (see the attach). No matter how
many times you press Retry, the same error appears.
4. When you press Cancel, the error disappears, the new wallet is in the list
in the Manager.
5. When you try to open the wallet, the same error appears. Occasionally the
error does not appear and the wallet opens, but that is a rare case.
6. The same error appears when you execute `kwallet-query -l ` in
the command line.


Actual Results:  
An error appears, the wallet is inaccessible.

Expected Results:  
The wallet should work.

The GPG key uses RSA 4096-bit key with no passphrase.

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

[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

[Dennis Schridde via KDE Bugzilla]

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

--- Comment #10 from Dennis Schridde  ---
(In reply to Denis Kurz from comment #9)
> Isn't this just a linking error? Last time I checked, there was no call to
> QtWebEngine in the PIMContactsRunner, but it is linked against it somehow.
> So when the plugin is loaded by Qt, so is the QtWebEngine, which
> automatically triggers its initialize function.

On my system, /usr/lib/qt5/plugins/krunner_pimcontacts.so was built with
-Wl,--as-needed. Thus if no part of the code uses a library, that library will
not be linked against.

The full tree of linked libraries (omitting duplications) is given here -
QtWebEngine is not among them:
/usr/lib/qt5/plugins/krunner_pimcontacts.so
| /usr/lib64/libKF5Runner.so.5
| | /usr/lib64/libKF5Plasma.so.5
| | | /usr/lib64/libQt5Sql.so.5
| | | | /usr/lib64/libQt5Core.so.5
| | | | | /lib64/libz.so.1
| | | | | /usr/lib64/libicui18n.so.57
| | | | | | /usr/lib64/libicuuc.so.57
| | | | | | | /usr/lib64/libicudata.so.57
| | | | | /usr/lib64/libicuuc.so.57
| | | | | /usr/lib64/libpcre16.so.0
| | | | | /usr/lib64/libglib-2.0.so.0
| | | | | | /lib64/libpcre.so.1
| | | | | /usr/lib64/libsystemd.so.0
| | | | | | /lib64/libcap.so.2
| | | | | | /lib64/liblzma.so.5
| | | | | | /usr/lib64/liblz4.so.1
| | | | | | /usr/lib64/libgcrypt.so.20
| | | | | | | /usr/lib64/libgpg-error.so.0
| | | | | | /lib64/ld-linux-x86-64.so.2
| | | | | | | /lib64/ld-linux-x86-64.so.2
| | | | | /lib64/ld-linux-x86-64.so.2
| | | /usr/lib64/libKF5XmlGui.so.5
| | | | /usr/lib64/libQt5Network.so.5
| | | | | /usr/lib64/libQt5Core.so.5
| | | | | /lib64/libz.so.1
| | | | | /usr/lib64/libproxy.so.1
| | | | | /usr/lib64/libssl.so.1.0.0
| | | | | | /usr/lib64/libcrypto.so.1.0.0
| | | | | | | /lib64/libz.so.1
| | | | | /usr/lib64/libcrypto.so.1.0.0
| | | | /usr/lib64/libQt5PrintSupport.so.5
| | | | | /usr/lib64/libQt5Widgets.so.5
| | | | | | /usr/lib64/libQt5Gui.so.5
| | | | | | | /usr/lib64/libQt5Core.so.5
| | | | | | | /usr/lib64/libpng16.so.16
| | | | | | | | /lib64/libz.so.1
| | | | | | | /usr/lib64/libharfbuzz.so.0
| | | | | | | | /usr/lib64/libglib-2.0.so.0
| | | | | | | | /usr/lib64/libfreetype.so.6
| | | | | | | | | /lib64/libz.so.1
| | | | | | | | | /lib64/libbz2.so.1
| | | | | | | | | /usr/lib64/libpng16.so.16
| | | | | | | | | /usr/lib64/libharfbuzz.so.0
| | | | | | | | /usr/lib64/libgraphite2.so.3
| | | | | | | /lib64/libz.so.1
| | | | | | | /usr/lib64/libGL.so.1
| | | | | | | | /usr/lib64/libexpat.so.1
| | | | | | | | /usr/lib64/libxcb-dri3.so.0
| | | | | | | | | /usr/lib64/libxcb.so.1
| | | | | | | | | | /usr/lib64/libXau.so.6
| | | | | | | | | | /usr/lib64/libXdmcp.so.6
| | | | | | | | | | | /usr/lib64/libbsd.so.0
| | | | | | | | /usr/lib64/libxcb-present.so.0
| | | | | | | | | /usr/lib64/libxcb.so.1
| | | | | | | | /usr/lib64/libxcb-sync.so.1
| | | | | | | | | /usr/lib64/libxcb.so.1
| | | | | | | | /usr/lib64/libxshmfence.so.1
| | | | | | | | /usr/lib64/libglapi.so.0
| | | | | | | | /usr/lib64/libXext.so.6
| | | | | | | | | /usr/lib64/libX11.so.6
| | | | | | | | | | /usr/lib64/libxcb.so.1
| | | | | | | | /usr/lib64/libXdamage.so.1
| | | | | | | | | /usr/lib64/libX11.so.6
| | | | | | | | /usr/lib64/libXfixes.so.3
| | | | | | | | | /usr/lib64/libX11.so.6
| | | | | | | | /usr/lib64/libX11-xcb.so.1
| | | | | | | | | /usr/lib64/libX11.so.6
| | | | | | | | | /usr/lib64/libxcb.so.1
| | | | | | | | /usr/lib64/libX11.so.6
| | | | | | | | /usr/lib64/libxcb.so.1
| | | | | | | | /usr/lib64/libxcb-glx.so.0
| | | | | | | | | /usr/lib64/libxcb.so.1
| | | | | | | | /usr/lib64/libxcb-dri2.so.0
| | | | | | | | | /usr/lib64/libxcb.so.1
| | | | | | | | /usr/lib64/libXxf86vm.so.1
| | | | | | | | | /usr/lib64/libX11.so.6
| | | | | | | | | /usr/lib64/libXext.so.6
| | | | | | | | /usr/lib64/libdrm.so.2
| | | | | | /usr/lib64/libQt5Core.so.5
| | | | | | /usr/lib64/libgobject-2.0.so.0
| | | | | | | /usr/lib64/libglib-2.0.so.0
| | | | | | | /usr/lib64/libffi.so.6
| | | | | | /usr/lib64/libglib-2.0.so.0
| | | | | | /usr/lib64/libX11.so.6
| | | | | /usr/lib64/libQt5Gui.so.5
| | | | | /usr/lib64/libQt5Core.so.5
| | | | /usr/lib64/libKF5TextWidgets.so.5
| | | | | /usr/lib64/libKF5SonnetUi.so.5
| | | | | | /usr/lib64/libQt5Widgets.so.5
| | | | | | /usr/lib64/libKF5SonnetCore.so.5
| | | | | | | /usr/lib64/libQt5Core.so.5
| | | | | | /usr/lib64/libQt5Gui.so.5
| | | | | | /usr/lib64/libQt5Core.so.5
| | | | | /usr/lib64/libKF5SonnetCore.so.5
| | | | | /usr/lib64/libKF5Service.so.5
| | | | | | /usr/lib64/libKF5ConfigCore.so.5
| | | | | | | /usr/lib64/libQt5Core.so.5
| | | | | | /usr/lib64/libKF5CoreAddons.so.5
| | | | | | | /usr/lib64/libQt5Core.so.5
| | | | | | /usr/lib64/libKF5I18n.so.5
| | | | | | | /usr/lib64/libQt5Core.so.5
| | | | | | /usr/lib64/libKF5DBusAddons.so.5
| | | | | | | /usr/lib64/libQt5DBus.so.5
| | | | | | | | /usr/lib64/libQt5Core.so.5
| | | | | | | | /usr/lib64/libdbus-1.so.3
| | | | | | | | | /usr/lib64/libsystemd.so.0
| | | | | | | 

[kmymoney4] [Bug 367869] Wishlist item - Update stock prices via crond

[Jack via KDE Bugzilla]

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

--- Comment #1 from Jack  ---
A variant on this would be to allow command line switches for all appropriate
menu items.  Having the program not need to open any windows at all for these
non-interactive sessions would also be useful.

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

[kdenlive] [Bug 365839] Unable to open or save a project

[via KDE Bugzilla]

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

porj...@yahoo.com.au changed:

   What|Removed |Added

 CC||porj...@yahoo.com.au

--- Comment #3 from porj...@yahoo.com.au ---
I'm having the same issue on kdenlive distributed with Fedora 24 -
kdenlive-16.04.3-1.fc24.x86_64

I've found that the issue occurs when the main kdenlive window is maximised.
When the window is minimised, the save/open dialog is not blank.

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

[kmail2] [Bug 360194] Archiving takes current date, not date of messages

[via KDE Bugzilla]

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

sascha.zengl...@yahoo.de changed:

   What|Removed |Added

 CC||sascha.zengl...@yahoo.de

--- Comment #1 from sascha.zengl...@yahoo.de ---
There should be a way to choose whether to archive by current or mail date. I
personally think it makes more sense your way, but it should be configurable.

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

[clazy] [Bug 368072] -Werror has no effect with Clazy

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Assignee|unassigned-b...@kde.org |smart...@kde.org
 Status|UNCONFIRMED |CONFIRMED

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

[digikam] [Bug 368125] New: No hint when adding face within album view

[Stefano via KDE Bugzilla]

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

Bug ID: 368125
   Summary: No hint when adding face within album view
   Product: digikam
   Version: 5.1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: AlbumsView
  Assignee: digikam-de...@kde.org
  Reporter: rs4...@gmail.com

When you add a face tag in album view, typing a name does not show the list of
similar tags, like it does in face detection pane: this forces you to type the
whole name instead of clicking on the suggestion list.

Instead, it shows the full list of tags: first, the combo is too little, and
anyway the full list of tags (with tree view) is pretty useless in that
context.

Reproducible: Always

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

[digikam] [Bug 368124] New: Face tag inside album view is case sensitive

[Stefano via KDE Bugzilla]

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

Bug ID: 368124
   Summary: Face tag inside album view is case sensitive
   Product: digikam
   Version: 5.1.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Management
  Assignee: digikam-de...@kde.org
  Reporter: rs4...@gmail.com

When you add a tace tag inside album view the input box is case sensitive, it
should better be case insensitive as it is in the batch face detection view.

Reproducible: Always

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

[okular] [Bug 344599] Thumbnails sidebar always open when okular starts

[via KDE Bugzilla]

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

j...@antonello.org changed:

   What|Removed |Added

 CC||j...@antonello.org

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

[gwenview] [Bug 368123] New: gwenview-16.04.3 crashes when closing, happens at random

[Jón Frímann via KDE Bugzilla]

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

Bug ID: 368123
   Summary: gwenview-16.04.3 crashes when closing, happens at
random
   Product: gwenview
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: jonfr1...@jonfr.com
CC: myr...@kde.org

When closing gwenview-16.04.3 it crashed without reason. This does seem to be
random crash and is hard to make it happen again.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. Open up a image.
2. Change to an other image.
3. Close gwenview.

Actual Results:  
On closing the gwenview crashes, this crash is difficult to make happen and
might only happen once in a while without clear reason.

Expected Results:  
The program should close normally.

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

Thread 2 (Thread 0x7f5c3282e700 (LWP 19797)):
#0  0x7f5c48600dcd in read () from /lib64/libc.so.6
#1  0x7f5c42171090 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f5c4212fcd4 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f5c421301b0 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f5c4213031c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f5c48eaefdc in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f5c48e63192 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f5c48cc2aa4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f5c4d5541dd in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x7f5c48cc717b in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x7f5c437e642c in start_thread () from /lib64/libpthread.so.0
#11 0x7f5c4860db9d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5c4d1c3800 (LWP 19795)):
[KCrash Handler]
#6  0x7f5c491f3842 in ?? () from /usr/lib64/libQt5Gui.so.5
#7  0x7f5c491f3911 in QImageReader::~QImageReader() () from
/usr/lib64/libQt5Gui.so.5
#8  0x7f5c49209a4c in QMovie::~QMovie() () from /usr/lib64/libQt5Gui.so.5
#9  0x7f5c4cca85d1 in ?? () from /usr/lib64/libgwenviewlib.so.5
#10 0x7f5c4cca8629 in ?? () from /usr/lib64/libgwenviewlib.so.5
#11 0x7f5c4ccab589 in Gwenview::Document::~Document() () from
/usr/lib64/libgwenviewlib.so.5
#12 0x7f5c4ccabba1 in Gwenview::Document::~Document() () from
/usr/lib64/libgwenviewlib.so.5
#13 0x7f5c4ccb1850 in ?? () from /usr/lib64/libgwenviewlib.so.5
#14 0x7f5c4ccb117d in Gwenview::DocumentFactory::~DocumentFactory() () from
/usr/lib64/libgwenviewlib.so.5
#15 0x7f5c4855c4b8 in ?? () from /lib64/libc.so.6
#16 0x7f5c4855c505 in exit () from /lib64/libc.so.6
#17 0x7f5c48547617 in __libc_start_main () from /lib64/libc.so.6
#18 0x0042b6b9 in _start ()

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

[umbrello] [Bug 202436] Umbrello crashes on undo after deleting [UMLWidgetController::insertSaveValues, Uml::CmdMoveWidget::undo, QUndoStack::undo]

[ghislain via KDE Bugzilla]

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

ghislain  changed:

   What|Removed |Added

 CC||jffra...@gmail.com

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

[kdenlive] [Bug 368057] segfault in timeline on many transitions

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

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

[krita] [Bug 368119] Line Tool - strange line to corner

[eliotJ via KDE Bugzilla]

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

eliotJ  changed:

   What|Removed |Added

   Keywords||regression

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

[krita] [Bug 368119] Line Tool - strange line to corner

[eliotJ via KDE Bugzilla]

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

--- Comment #1 from eliotJ  ---
Created attachment 100889
  --> https://bugs.kde.org/attachment.cgi?id=100889=edit
video with bug appearing

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

[konsole] [Bug 368122] URLs get concatenated with first word after newline

[Nemo via KDE Bugzilla]

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

--- Comment #1 from Nemo  ---
Created attachment 100888
  --> https://bugs.kde.org/attachment.cgi?id=100888=edit
Example from IRC on irssi

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

[konsole] [Bug 368122] New: URLs get concatenated with first word after newline

[Nemo via KDE Bugzilla]

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

Bug ID: 368122
   Summary: URLs get concatenated with first word after newline
   Product: konsole
   Version: 15.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: federicol...@tiscali.it

I'm often unable to click or right click URLs in Konsole because they get
garbled with extraneous text just because they come at the end of a line, which
happens frequently e.g. in IRC messages containing a link as last thing.

Reproducible: Sometimes

Steps to Reproduce:
1. Open a CLI program which sometimes outputs URLs at the end of a line, like
irssi
2. Get an URL + newline + non-space characters sequence printed, with the URL
long enough but not so much as to be wrapped
3. Hover/select/click/copy the URL

Actual Results:  
The first word after the newline is selected together with the URL as if it
were part of the URL. The URL most likely becomes invalid.

Expected Results:  
The URL is terminated by the newline.

The bug has appeared in the last few days for me on fedora 23 stable. I'm not
aware of any other involved software having changed.

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

[kdenlive] [Bug 368057] segfault in timeline on many transitions

[via KDE Bugzilla]

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

--- Comment #3 from asla...@vsechno-atd.cz ---
Interestingly, I've enabled the testing Kdenlive ppa and upgraded everything
and rebooted, and the crash does not occur now. I might have had a different
build installed, although I thought it was the stable ppa version.

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

[dolphin] [Bug 368121] New: Sort setting change does effect only after restart Dolphin

[Dr . Chapatin via KDE Bugzilla]

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

Bug ID: 368121
   Summary: Sort setting change does effect only after restart
Dolphin
   Product: dolphin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: yy...@gmx.com

Sort setting change does effect only after restart Dolphin


Reproducible: Always

Steps to Reproduce:
1. Open Dolphin and open its settings dialog
2. On left site select "General", change "Sorter mode" and apply the change


Actual Results:  
Previous setting is still working until Dolphin is restarted

Expected Results:  
New setting works immediately

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

[frameworks-ki18n] [Bug 368007] Krita 3.0.1 RC doesn't load a system language of OS

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 CC||kosse...@kde.org

--- Comment #7 from Friedrich W. H. Kossebau  ---
I tried to reproduce the issue on linux (opensuse tumbleweed) with ki18n 5.24.
But everything works as intended for me, even with exactly the setup you gave
(using zh_TW ).

Looking at the code I could not see anything suspicious, also any added qdebug
statements always had values expected.

There are some windows specific codepath though, which also changed since ki18n
5.17 (which I understood did not show this bug) . On my recent commits to ki18n
I did not touch those parts, so no idea what influence they have. There is one
commit which might be especially suspective, perhaps you would talk to the
author:
https://quickgit.kde.org/?p=ki18n.git=commit=26750a15fba059d3a703131e9cd400893aa596a6
(see also https://git.reviewboard.kde.org/r/127275/ where I commented about
some issue with this patch)

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

[valgrind] [Bug 368120] x86_linux asm _start functions do not keep 16-byte aligned stack pointer

[dimitry via KDE Bugzilla]

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

dimitry  changed:

   What|Removed |Added

 CC||dimi...@google.com

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

[valgrind] [Bug 368120] New: x86_linux asm _start functions do not keep 16-byte aligned stack pointer

[via KDE Bugzilla]

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

Bug ID: 368120
   Summary: x86_linux asm _start functions do not keep 16-byte
aligned stack pointer
   Product: valgrind
   Version: 3.11.0
  Platform: Android
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: c...@google.com

When valgrind is optimized by clang/llvm for x86 targets, clang/llvm requires
16-byte aligned stack pointers from the caller. The valgrind assembly functions
_start,  vgModuleLocal_call_on_new_stack_0_1, and do_syscall_clone_x86_linux do
not keep stack pointer aligned before calling other functions.

This is working with gcc because it does not require such stack pointer
alignment.
When compiled with clang/llvm, memcheck aborted with segmentation fault.

The following diff should fixed the problem for Android x86 target:

@@ -2925,12 +2925,13 @@ asm("\n"
 "\tmovl  $vgPlain_interim_stack, %eax\n"
 "\taddl  $"VG_STRINGIFY(VG_STACK_GUARD_SZB)", %eax\n"
 "\taddl  $"VG_STRINGIFY(VG_DEFAULT_STACK_ACTIVE_SZB)", %eax\n"
+/* allocate at least 16 bytes on the new stack, and aligned */
 "\tsubl  $16, %eax\n"
 "\tandl  $~15, %eax\n"
 /* install it, and collect the original one */
 "\txchgl %eax, %esp\n"
 /* call _start_in_C_linux, passing it the startup %esp */
-"\tpushl %eax\n"
+"\tmovl  %eax, (%esp)\n"
 "\tcall  _start_in_C_linux\n"
 "\thlt\n"
 ".previous\n"
diff --git a/coregrind/m_syswrap/syswrap-x86-linux.c
b/coregrind/m_syswrap/syswrap-x86-linux.c
index 24d7dc1..233886d 100644
--- a/coregrind/m_syswrap/syswrap-x86-linux.c
+++ b/coregrind/m_syswrap/syswrap-x86-linux.c
@@ -83,8 +83,9 @@ asm(
 ".globl vgModuleLocal_call_on_new_stack_0_1\n"
 "vgModuleLocal_call_on_new_stack_0_1:\n"
 "   movl %esp, %esi\n" // remember old stack pointer
-"   movl 4(%esi), %esp\n"  // set stack
-"   pushl 16(%esi)\n"  // arg1 to stack
+"   movl 4(%esi), %esp\n"  // set stack, assume %esp is now 16-byte aligned
+"   subl $12, %esp\n"  // skip 12 bytes
+"   pushl 16(%esi)\n"  // arg1 to stack, %esp is 16-byte aligned
 "   pushl  8(%esi)\n"  // retaddr to stack
 "   pushl 12(%esi)\n"  // f to stack
 "   movl $0, %eax\n"   // zero all GP regs
@@ -150,7 +151,8 @@ asm(
 "movl 4+"FSZ"(%esp), %ecx\n"/* syscall arg2: child stack */
 "movl12+"FSZ"(%esp), %ebx\n"/* fn arg */
 "movl 0+"FSZ"(%esp), %eax\n"/* fn */
-"lea -8(%ecx), %ecx\n"  /* make space on stack */
+"andl$-16, %ecx\n"  /* align to 16-byte */
+"lea -20(%ecx), %ecx\n" /* allocate 16*n+4 bytes on stack
*/
 "movl%ebx, 4(%ecx)\n"   /*   fn arg */
 "movl%eax, 0(%ecx)\n"   /*   fn */

@@ -165,7 +167,7 @@ asm(
 "jnz 1f\n"

  /* CHILD - call thread function */
-"popl%eax\n"
+"popl%eax\n"/* child %esp is 16-byte aligned
*/
 "call*%eax\n"   /* call fn */

  /* exit with result */




Reproducible: Always

Steps to Reproduce:
1. Build valgrind with clang/llvm for x86 linux
2. Run valgrind to debug a 32-bit x86 program 


Actual Results:  
Segmentation fault in x86 32-bit memcheck.



See Android patch in https://android-review.googlesource.com/#/c/264837

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

[krita] [Bug 368119] New: Line Tool - strange line to corner

[eliotJ via KDE Bugzilla]

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

Bug ID: 368119
   Summary: Line Tool - strange line to corner
   Product: krita
   Version: 3.0.1 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: os...@jadamspam.pl

I showing this bug on the video which I will attach in comment.  I affraid this
bug started to appear after dmitry's fix for "Finish line" (option from
Stabilizer), which was commited lately... This bug makes "Line Tool"
unusable...

This bug appear for me often, but sadly I don't know how exactly reproduce
it... I hope this will be fixed for v3.0.1 stable.

Windows 7 64 bit, Nvidia GeForce G 103M, Intel dual Core 2,2 Ghz, 4 GB Ram.

Reproducible: Always

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

[Akonadi] [Bug 352249] kmail ... gmail Syncing folder 'linux-arm-kernel' hangs at 98%

[Michael Chalvatzis via KDE Bugzilla]

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

Michael Chalvatzis  changed:

   What|Removed |Added

 CC||gly...@gmx.net

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

[valgrind] [Bug 339596] vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||m...@redhat.com

--- Comment #17 from Mark Wielaard  ---
About the testcase. The __builtin_ia32_xxx are really just internal compiler
details. They might or might not be there between versions of the same compiler
or between different compilers. They might not even implement the same thing or
take different arguments. For example the testcase uses __builtin_ia32_vpcomew
with an extra argument that says which kind of operation/memonic is really
meant, while gcc provides 8 separate __builtin_ia32_vpcom[xxx] to provide the
same functionality. The testcase uses separate __builtin_ia32_vfnmaddxx and
__builtin_ia32_vfnmsubxx functions, while gcc just provides one which takes a
positive or negative argument. There is also no guarantee that these functions
translate to some exact instruction (sequence).

So it would be better to rewrite the testcase to use explicit inline assembly
using the exact instructions that we want to test.

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

[Bluedevil] [Bug 368118] New: Bluetooth headset doesn't output voice after disconnected and reconnected

[Bora Semiz via KDE Bugzilla]

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

Bug ID: 368118
   Summary: Bluetooth headset doesn't output voice after
disconnected and reconnected
   Product: Bluedevil
   Version: 5.6.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: daemon
  Assignee: now...@gmail.com
  Reporter: borasemi...@gmail.com

I have a bluetooth headset. It's brand is Bluedio. I can connect the headset to
my computer with no issue. However, when I disconnect my device and reconnect
it again, it doesn't work as expected. Here is what is happening after
reconnection;

I use Kubuntu 16.04,
1) Between the first connection and disconnection of the device, I have to
change the volume setting to High Fidelity Playback (A2DP Sink) (System
Settings > Multimedia > Audio Volume > Configuration Tab), otherwise voice
quality is suck.
2) After disconnecting and reconnecting the headset, my configuration above
disappears. After reconnecting the configuration switches to Headset Head Unit
(HSP/HFP), which is in the same dropdown menu with the High Fidelity Playback
(A2DP Sink). However this voice quality is suck. From the same dropdown menu,
if I change to the High Fidelity Playback (A2DP Sink), it doesn't change and it
doesn't produce output anymore. I tried rebooting and repairring, first
repairing after rebooting, first rebooting after repairing... Non.

The workaround I found to this problem is deleting the associated bluetooth
configuration folder with the headset. In my case, it is in the
/var/lib/bluetooth. After, I repaired the headset.

Reproducible: Always

Steps to Reproduce:
1. Disconnect the bluetooth headset.
2. Reconnect.

Actual Results:  
I couldn't get voice output from my headset. To be specific, I couldn't get
voice output when the volume configuration is High Fidelity Playback (A2DP
Sink).

Expected Results:  
It should give me voice output in High Fidelity Playback (A2DP Sink) mode,
after any kind of reconnection.

I use Kubuntu 16.04.

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

[kdevelop] [Bug 367825] KDevelop 5 freezes while parsing Javascript code

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Sven Brauch  ---
I think this is the reason: https://git.reviewboard.kde.org/r/128762/
Need to fix it up though.

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

[kdenlive] [Bug 361966] Seeking frame-by-frame from the left and from the right displays different contents in the project monitor

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 357991] Unable to rotate video negative amount when not using standard locale for numbers

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #5 from Wegwerf  ---
Jean-Baptiste, I can reproduce this now, by temporarily switching the locale in
a terminal session as follows:
$export LANGUAGE=nb_NO.UTF-8
$export LANG=nb_NO.UTF-8
$export LC_NUMERIC=nb_NO.UTF-8

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

[kdenlive] [Bug 357991] Unable to rotate video negative amount when not using standard locale for numbers

[Wegwerf via KDE Bugzilla]

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

--- Comment #4 from Wegwerf  ---
Can you please run the "locale" command in a terminal and report back its
output?

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

[trojita] [Bug 367601] fake-dev-random should not be used unconditionally

[Jan Kundrát via KDE Bugzilla]

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

Jan Kundrát  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/troj
   ||ita/1311c5afd1f4b5a17c946c2
   ||45d7ec30d39a22eb4

--- Comment #2 from Jan Kundrát  ---
Git commit 1311c5afd1f4b5a17c946c245d7ec30d39a22eb4 by Jan Kundrát.
Committed on 29/08/2016 at 11:06.
Pushed by gerrit into branch 'master'.

tests: Remove Linux-specific includes for dlsym

The dlsym(RTLD_NEXT) appears to be reasonably portable (it's POSIX,
except the minor RTLD_NEXT and _GNU_SOURCE on glibc), so let's use this
thing to fix a build failure on OpenBSD.

We are doing this because GnuPG 2.1+ is still not really that
mainstream and because faking the random generator just for the tests at
all platforms simplifies the test matrix. Alternatives such as GnuPG
version detection are IMHO too fancy.
Change-Id: Icf0001a20c6e2901a88b65a705059d687951b1fb

M  +1-4tests/Utils/fake-dev-random.c

http://commits.kde.org/trojita/1311c5afd1f4b5a17c946c245d7ec30d39a22eb4

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

[trojita] [Bug 367607] Compiled trojita asserts on startup when trojita has been installed with package manager

[Jan Kundrát via KDE Bugzilla]

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

Jan Kundrát  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/troj
   ||ita/fa23cf7f49abf2b3116cfb0
   ||286d744d688752bb8

--- Comment #2 from Jan Kundrát  ---
Git commit fa23cf7f49abf2b3116cfb0286d744d688752bb8 by Jan Kundrát.
Committed on 30/08/2016 at 09:08.
Pushed by gerrit into branch 'master'.

Plugins: do not assert on plugins duplicated to several directories

As Caspar points out, the code asserts when a same-named plugin is found
both in the systemwide directory and in our current build directory.

This change makes sure that only one "instance" of a same-named file is
attempted for loading. This check happens early in the path and because
appdir-local plugins are actually attempted to load earlier than the
rest, it Should Work™.
Change-Id: Id0bb508a03708c1cbe8d43b8685c236a3292

M  +12   -1src/Plugins/PluginManager.cpp

http://commits.kde.org/trojita/fa23cf7f49abf2b3116cfb0286d744d688752bb8

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

[kdenlive] [Bug 367748] System tray indicator for insync stopped working after installation of KDEnlive from the testing repo

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 367748] System tray indicator for insync stopped working after installation of KDEnlive from the testing repo

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||wegwerf-1-...@gmx.de
 Resolution|--- |FIXED

--- Comment #1 from Wegwerf  ---
Fixed since a few days in master and testing ppas.

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

[kdenlive] [Bug 367593] Kdenlive crashes immediately on opening

[Wegwerf via KDE Bugzilla]

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

--- Comment #3 from Wegwerf  ---
Why are there Qt calls involved from version 4.8.7 instead of at least 5.0?
Your setup seems to be severly broken. Please head over to the Kdenlive forum
and ask for help from Gentoo users. Thank you very much for your cooperation.

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

[kdenlive] [Bug 368057] segfault in timeline on many transitions

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||wegwerf-1-...@gmx.de
 Ever confirmed|0   |1

--- Comment #2 from Wegwerf  ---
Do these crashes happen all the time in ::update method of various frei0r
shared libs?

Looks suspiciously like the random crashes I experience with self-compiled
Kdenlive since I updated from the Kdenlive ppa's. However, when I use Kdenlive
from the Kdenlive ppa, then it is stable.

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

[kmail2] [Bug 308968] certificate is not remembered

[via KDE Bugzilla]

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

--- Comment #15 from nik.knatter...@web.de ---
What is the correct path where kde stores the user added certificates? Can the
root ca cert simply be placed in that directory?

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

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

[benjamin scott via KDE Bugzilla]

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

benjamin scott  changed:

   What|Removed |Added

 CC||bensc...@nwlink.com

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

[Kubuntu Notifications Helper] [Bug 368117] New: newby: was cleaning duplicate files

[André via KDE Bugzilla]

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

Bug ID: 368117
   Summary: newby: was cleaning duplicate files
   Product: Kubuntu Notifications Helper
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: pominvi...@libero.it

i am total ignorant face at linux stuff.
Here is what i copied:





Reproducible: Always


Actual Results:  
Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-34-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:


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

Thread 5 (Thread 0x7f1420d74700 (LWP 18065)):
[KCrash Handler]
#6  0x7f159c0839a5 in QMutex::lock() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f159c08a9ab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f159c08b86f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f15988396fa in start_thread (arg=0x7f1420d74700) at
pthread_create.c:333
#10 0x7f15a14c5b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f157dffe700 (LWP 17936)):
#0  0x7f15a14b59cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1597cf1740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1597cade84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1597cae340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1597cae4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f159c2c2a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f159c269dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f159c0868a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f159c08b84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f15988396fa in start_thread (arg=0x7f157dffe700) at
pthread_create.c:333
#10 0x7f15a14c5b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f158162c700 (LWP 17935)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1589995213 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f1589994937 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f15988396fa in start_thread (arg=0x7f158162c700) at
pthread_create.c:333
#4  0x7f15a14c5b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f158bf93700 (LWP 17933)):
#0  0x7f15a14b9e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1595c45c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f1595c478d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f158e2e5629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f159c08b84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f15988396fa in start_thread (arg=0x7f158bf93700) at
pthread_create.c:333
#6  0x7f15a14c5b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f158e69d8c0 (LWP 17932)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1595c45eb9 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f1595c47617 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f1595c47721 in xcb_wait_for_reply () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x7f158e3073c6 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#5  0x7f158e307478 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x7f159c7c8fe8 in QCursor::pos(QScreen const*) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x7f159c7c90c1 in QCursor::pos() () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#8  0x7f159ceed971 in QMenu::popup(QPoint const&, QAction*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f159ceef9b1 in QMenu::internalDelayedPopup() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7f159c29be53 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f159cdb1cdb in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f159cef4a83 in QMenu::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f159cd6f05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from 

[kmail2] [Bug 368116] New: Passphrase for S/MIME key is not saved in kwallet

[Johannes Maier via KDE Bugzilla]

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

Bug ID: 368116
   Summary: Passphrase for S/MIME key is not saved in kwallet
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: maier...@gmx.de

The passphrase for the S/MIME key to sign a e-mail is not saved in password
manager (kwallet) if selected to do so.

Reproducible: Always

Steps to Reproduce:
1. boot computer
2. send e-mail with option sign always
3. you are promted for the key password and not for the kwallet password

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

[Baloo] [Bug 368115] New: GParted crashed

[via KDE Bugzilla]

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

Bug ID: 368115
   Summary: GParted crashed
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: pinak.ah...@gmail.com
  Reporter: pedron.alexan...@gmail.com

Application: baloo_file (5.18.0)

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

-- Information about the crash:
- What I was doing when the application crashed:
GParted crashed when I was trying to create a new partition on an usb stick.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f535920e418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f535921001a in __GI_abort () at abort.c:89
#8  0x7f5359cbfff1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=this@entry=0x7ffc70cfc0b0,
msg=msg@entry=0x7f535b32dd28 "Cannot construct placeholder type QDBusRawType")
at global/qlogging.cpp:781
#10 0x7f535b30a552 in QDBusRawTypeHandler::construct () at
qdbusmetaobject.cpp:133
#11 0x7f5359ef39c0 in QMetaType::construct (copy=0x0, where=0x7ffc70cfc1d0,
this=0x7ffc70cfc110) at
../../include/QtCore/../../src/corelib/kernel/qmetatype.h:2141
#12 (anonymous namespace)::customConstruct (d=0x7ffc70cfc1d0, copy=0x0) at
kernel/qvariant.cpp:1019
#13 0x7f5359ef48bf in QVariant::QVariant (this=0x7ffc70cfc1d0,
typeId=, copy=) at kernel/qvariant.cpp:1660
#14 0x7f5359ec0cf2 in QMetaProperty::read (this=this@entry=0x7ffc70cfc270,
object=object@entry=0x1135800) at kernel/qmetaobject.cpp:3010
#15 0x7f5359ee0b0f in QObject::property (this=0x1135800, name=0x1170798
"MountPoints") at kernel/qobject.cpp:3893
#16 0x7f535aef7664 in Solid::Backends::UDisks2::DeviceBackend::checkCache
(this=0xf19190, key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:185
#17 0x7f535aef7883 in
Solid::Backends::UDisks2::DeviceBackend::propertyExists (this=0xf19190,
key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:132
#18 0x7f535aeef5be in Solid::Backends::UDisks2::Device::propertyExists
(this=this@entry=0x11707d0, key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:126
#19 0x7f535aef137f in Solid::Backends::UDisks2::Device::isMounted
(this=0x11707d0) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:818
#20 0x7f535af0a711 in Solid::Backends::UDisks2::StorageAccess::isAccessible
(this=0x1177e10) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:75
#21 0x7f535af0a944 in Solid::Backends::UDisks2::StorageAccess::updateCache
(this=0x1177e10) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:138
#22 Solid::Backends::UDisks2::StorageAccess::StorageAccess (this=0x1177e10,
device=0x11707d0, __in_chrg=, __vtt_parm=) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:36
#23 0x7f535aeef780 in
Solid::Backends::UDisks2::Device::createDeviceInterface (this=0x11707d0,
type=) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:174
#24 0x7f535aeb968f in Solid::Device::asDeviceInterface
(this=this@entry=0x7ffc70cfc5e0, type=@0x7ffc70cfc570:
Solid::DeviceInterface::StorageAccess) at
../../../src/solid/devices/frontend/device.cpp:154
#25 0x00423116 in Solid::Device::as
(this=0x7ffc70cfc5e0) at /usr/include/KF5/Solid/solid/device.h:247
#26 Baloo::StorageDevices::createCacheEntry (this=this@entry=0xea9390, dev=...)
at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/storagedevices.cpp:79
#27 0x004233a8 in Baloo::StorageDevices::slotSolidDeviceAdded
(this=0xea9390, udi=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/storagedevices.cpp:96
#28 0x7f5359ee1e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffc70cfc740,
r=0xea9390, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#29 QMetaObject::activate (sender=0xea9c70, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc70cfc740)
at kernel/qobject.cpp:3698
#30 0x7f5359ee27d7 in QMetaObject::activate (sender=,
m=m@entry=0x7f535b146e60 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc70cfc740)
at kernel/qobject.cpp:3578
#31 0x7f535aeb9bb2 in Solid::DeviceNotifier::deviceAdded (this=, _t1=...) at ./moc_devicenotifier.cpp:136
#32 0x7f5359ee1fca in QMetaObject::activate (sender=sender@entry=0xeaa5d0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffc70cfc870) at kernel/qobject.cpp:3713
#33 0x7f5359ee27d7 in QMetaObject::activate 

[kmail2] [Bug 308968] certificate is not remembered

[Christian Heller via KDE Bugzilla]

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

--- Comment #14 from Christian Heller  ---
Thanks for the hint. For me, importing the certificate worked.
It appears properly under "User-added certificates".
Debian Stable.
However, I will have to see over the next couple of days,
if the message dialogue indeed does not appear anymore.

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

[ktorrent] [Bug 368114] New: KTorrent fills up .xsession-errors with connection logs

[Knut Andre Tidemann via KDE Bugzilla]

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

Bug ID: 368114
   Summary: KTorrent fills up .xsession-errors with connection
logs
   Product: ktorrent
   Version: 5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: knut.tidem...@gmail.com

It seems that KTorrent is filling up the .xsession-errors log with every
connection it makes.

Here's an example of the of the output:
tor. sep. 1 20:06:56 2016: Accepted connection from 50.65.xx.xx
tor. sep. 1 20:06:56 2016: Accepted connection from 81.224.xx.xx
tor. sep. 1 20:06:57 2016: Authentication(S) to 50.65.xx.xx : ok
tor. sep. 1 20:06:57 2016: Authentication(S) to 81.224.xx.xx : ok
tor. sep. 1 20:06:57 2016: Accepted connection from 188.142.xx.xx
tor. sep. 1 20:06:57 2016: Accepted connection from 222.97.xx.xx
tor. sep. 1 20:06:57 2016: Authentication(S) to 188.142.219.54 : ok
tor. sep. 1 20:06:57 2016: Authentication(S) to 222.97.167.160 : failure
tor. sep. 1 20:06:58 2016: Accepted connection from 185.148.xx.xx
tor. sep. 1 20:06:58 2016: Authentication(S) to 185.148.xx.xx : failure

As you can see, they come quite frequently and after 2 and half days of uptime
the log is now 230 MB.

The client is running with 32 torrents seeding.

When I quite ktorrent the messages stop, and they begin again when ktorrent is
restarted.


Reproducible: Always

Steps to Reproduce:
1. Start ktorrent with some torrents running
2. tail -f .xsession-errors

Actual Results:  
KTorrent logs every connection (it seems)

Expected Results:  
Ktorrent should not fill up the .xsession-errors that fast.

I'm running the arch linux package of ktorrent, version 5.0.1-2. kio version
5.25.0-1.

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

[dolphin] [Bug 368056] dolphin: symbol lookup error: /usr/lib/libkdeinit5_dolphin.so: undefined symbol: _ZN23KStandardItemListWidget5eventEP6QEvent

[Christoph Feck via KDE Bugzilla]

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

--- Comment #3 from Christoph Feck  ---
That's odd. Are you sure you are not mixing different dolphin installations?

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

[kmail2] [Bug 368113] New: invalid signature when using vcard

[Johannes Maier via KDE Bugzilla]

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

Bug ID: 368113
   Summary: invalid signature when using vcard
   Product: kmail2
   Version: 5.1.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: maier...@gmx.de

I'm using S/MIME Encryption in Kmail. That works.
But when using S/MIME Signature with a vcard Attachment, this does not work
anymore. Seems that vcard is added to the already signed mail. Therefore the
signature is wrong then?

Reproducible: Always

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

[dolphin] [Bug 368056] dolphin: symbol lookup error: /usr/lib/libkdeinit5_dolphin.so: undefined symbol: _ZN23KStandardItemListWidget5eventEP6QEvent

[Ingo Siegert via KDE Bugzilla]

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

--- Comment #2 from Ingo Siegert  ---
I restarted the KDE session, I also reinstalled dolphin. 
Both did not help.

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

[kdepim] [Bug 364994] Kmail crash when deleting message in thread view

[Heiko Becker via KDE Bugzilla]

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

Heiko Becker  changed:

   What|Removed |Added

 CC||heire...@exherbo.org

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

[kmail2] [Bug 308968] certificate is not remembered

[via KDE Bugzilla]

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

--- Comment #13 from nik.knatter...@web.de ---
Hi Christian,

thank you for the hint. In fact, I've tried that. Which leads to another bug
(in my eyes):
I click on "add", select the cert. It appears in the list as a "user
certificate" (Benutzerzertifikate). Then I click on "apply". Once the window is
closed and reopened, the cert has vanished again. :(

Cheers
Nik

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

[kdepim] [Bug 364994] Kmail crash when deleting message in thread view

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||martin+...@serafean.cz

--- Comment #5 from Denis Kurz  ---
*** Bug 366862 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 366862] kmail crash while syncing

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||denis.kurz+kdebugs@posteo.d
   ||e
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Denis Kurz  ---


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

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

[Planet KDE] [Bug 368098] Please add me in PlanetKDE

[Michail Vourlakos via KDE Bugzilla]

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

--- Comment #2 from Michail Vourlakos  ---
Thank u Christoph, I cleaned it from very old posts...
When you activate me I am going to make the first post in that list...

Do you need anything else from me to proceed?

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

[plasmashell] [Bug 366283] Non KDE plasma system tray icons are missing

[Janos Zsitvai via KDE Bugzilla]

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

--- Comment #4 from Janos Zsitvai  ---
I haven't experienced the problem since applying the patch on the 28th. This is
with version 5.7.4.

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

[kontact] [Bug 367031] Deleting message in a threaded message causes a crash

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||denis.kurz+kdebugs@posteo.d
   ||e
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Denis Kurz  ---


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

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

[kdepim] [Bug 364994] Kmail crash when deleting message in thread view

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kirichenk...@gmail.com

--- Comment #4 from Denis Kurz  ---
*** Bug 368092 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 368092] kmail crashed when deleting many of messages

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||denis.kurz+kdebugs@posteo.d
   ||e
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Denis Kurz  ---


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

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

[kdepim] [Bug 364994] Kmail crash when deleting message in thread view

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||freekdekru...@kde.nl

--- Comment #3 from Denis Kurz  ---
*** Bug 367031 has been marked as a duplicate of this bug. ***

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

[libksane] [Bug 312514] Bad area selection on Skanlite in preview mode

[Arnaud via KDE Bugzilla]

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

--- Comment #18 from Arnaud  ---
(In reply to Arnaud from comment #16)
> Hi, I know this is an old bug, but was wondering whether it ever got
> resolved. Status shows "resolved fixed", but I am still experiencing the
> same problem with my HP Scanjet 8250, a scanner using avision drivers. It
> would be great to find a solution. A preview scans only roughly an A5 area
> on this A4 flatbed scanner.
> $ skanlite -v
> Qt: 4.8.7
> KDE Development Platform: 4.14.16
> Skanlite: 1.1
> 
> Doing a scan instead of prescan does scan the whole surface, but defeats the
> purpose of the program, because I want to use it the scan and split multiple
> hpotos on one page.
> My HP Officejet 5610 (All in One) works without any problems.  How can I
> implement the fix?
> Thanks,
> Arnaud

I just tired Skanlite 2.0.0 under yakkety - problem is present in that version
too.

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

[Planet KDE] [Bug 368098] Please add me in PlanetKDE

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||cf...@kde.org

--- Comment #1 from Christoph Feck  ---
The Planet aggregator will only "import" feeds that are listed at
https://psifidotos.blogspot.com/feeds/posts/default/-/kde

Simply open it in Konqueror/KHTML to see them.

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

[umbrello] [Bug 158739] Python Import Classes does not import Attributes

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||2.20.1 (KDE Applications
   ||16.08.1)
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/umbr
   ||ello/2d452ec81ad95e4788505f
   ||21cb4e0de50fed8505

--- Comment #2 from Ralf Habacker  ---
Git commit 2d452ec81ad95e4788505f21cb4e0de50fed8505 by Ralf Habacker.
Committed on 01/09/2016 at 17:29.
Pushed by habacker into branch 'Applications/16.08'.

Fix 'Python Import Classes does not import Attributes'.

This commit adds support for parsing class attributes and
includes related test cases. Attribute types are estimated
from the initialisation value.
For supported types see test/import/python/types.py, for
supported visibilities test/import/python/visibility.py
FIXED-IN:2.20.1 (KDE Applications 16.08.1)

A  +10   -0test/import/python/types.py
A  +19   -0test/import/python/visibility.py
M  +11   -0umbrello/codeimport/nativeimportbase.cpp
M  +1-0umbrello/codeimport/nativeimportbase.h
M  +44   -0umbrello/codeimport/pythonimport.cpp

http://commits.kde.org/umbrello/2d452ec81ad95e4788505f21cb4e0de50fed8505

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

[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

[Denis Kurz via KDE Bugzilla]

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

--- Comment #9 from Denis Kurz  ---
Isn't this just a linking error? Last time I checked, there was no call to
QtWebEngine in the PIMContactsRunner, but it is linked against it somehow. So
when the plugin is loaded by Qt, so is the QtWebEngine, which automatically
triggers its initialize function.

Fixing the CMakeLists.txt might be enough to fix this.

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

[plasmashell] [Bug 368112] New: Plasma crashed after creating new partition

[via KDE Bugzilla]

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

Bug ID: 368112
   Summary: Plasma crashed after creating new partition
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pedron.alexan...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Plasma crashed after creating a new partition on an USB stick with the KDE
Partition Editor.

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

Thread 15 (Thread 0x7fa0ae7fc700 (LWP 5706)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa191a22aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3f270a0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=this@entry=0x2ba5438,
mutex=mutex@entry=0x2ba5430, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7fa194cc092e in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x2ba5428) at scenegraph/qsgthreadedrenderloop.cpp:224
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x2ba53b0) at
scenegraph/qsgthreadedrenderloop.cpp:657
#5  0x7fa194cc11b3 in QSGRenderThread::run (this=0x2ba53b0) at
scenegraph/qsgthreadedrenderloop.cpp:686
#6  0x7fa191a2184e in QThreadPrivate::start (arg=0x2ba53b0) at
thread/qthread_unix.cpp:331
#7  0x7fa190b0e6fa in start_thread (arg=0x7fa0ae7fc700) at
pthread_create.c:333
#8  0x7fa191337b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fa0aeffd700 (LWP 5090)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa191a22aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3857150) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=this@entry=0x394b6e8,
mutex=mutex@entry=0x394b6e0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7fa194cc092e in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x394b6d8) at scenegraph/qsgthreadedrenderloop.cpp:224
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x394b660) at
scenegraph/qsgthreadedrenderloop.cpp:657
#5  0x7fa194cc11b3 in QSGRenderThread::run (this=0x394b660) at
scenegraph/qsgthreadedrenderloop.cpp:686
#6  0x7fa191a2184e in QThreadPrivate::start (arg=0x394b660) at
thread/qthread_unix.cpp:331
#7  0x7fa190b0e6fa in start_thread (arg=0x7fa0aeffd700) at
pthread_create.c:333
#8  0x7fa191337b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fa0afdfe700 (LWP 5052)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa191a22aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3950d30) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=this@entry=0x321fb88,
mutex=mutex@entry=0x321fb80, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7fa194cc092e in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x321fb78) at scenegraph/qsgthreadedrenderloop.cpp:224
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x321fb00) at
scenegraph/qsgthreadedrenderloop.cpp:657
#5  0x7fa194cc11b3 in QSGRenderThread::run (this=0x321fb00) at
scenegraph/qsgthreadedrenderloop.cpp:686
#6  0x7fa191a2184e in QThreadPrivate::start (arg=0x321fb00) at
thread/qthread_unix.cpp:331
#7  0x7fa190b0e6fa in start_thread (arg=0x7fa0afdfe700) at
pthread_create.c:333
#8  0x7fa191337b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fa0b8926700 (LWP 5048)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa191a22aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3590ef0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=this@entry=0x35e9758,
mutex=mutex@entry=0x35e9750, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7fa194cc092e in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x35e9748) at scenegraph/qsgthreadedrenderloop.cpp:224
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x35e96d0) at
scenegraph/qsgthreadedrenderloop.cpp:657
#5  0x7fa194cc11b3 in QSGRenderThread::run 

[konsole] [Bug 368042] 2 konsole windows with different data - konsole use obsolete file meta data and file content

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||cf...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Christoph Feck  ---
There is no cache in Konsole, and Konsole does not change the output of the
'cat' commands, so the issue is elsewhere.

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

[konsole] [Bug 368086] KDE 5

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |konsole
  Component|general |general
   Assignee|unassigned-b...@kde.org |konsole-de...@kde.org
Version|unspecified |15.12.3

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

[dolphin] [Bug 368056] dolphin: symbol lookup error: /usr/lib/libkdeinit5_dolphin.so: undefined symbol: _ZN23KStandardItemListWidget5eventEP6QEvent

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||cf...@kde.org
 Resolution|--- |INVALID

--- Comment #1 from Christoph Feck  ---
kdeinit still refers to the old libkdeinit5_dolphin.so. Please restart the
session after KDE updates. If this does not solve the issue, please add a
comment.

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

[rekonq] [Bug 328181] Crash on http://www.idg.se/2.1085/1.535700/sa-livsfarlig-ar-din-billiga-piratladdare/sida/4/vi-letar-efter-fusk

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||gabr...@rueeck.de

--- Comment #16 from Denis Kurz  ---
*** Bug 364000 has been marked as a duplicate of this bug. ***

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

[kcharselect] [Bug 242333] bookmarks for character sets

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kcha
   ||rselect/c25c21fa4415ff25db4
   ||9b674ec3003bdcf4c565e
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Christoph Feck  ---
Git commit c25c21fa4415ff25db49b674ec3003bdcf4c565e by Christoph Feck.
Committed on 01/09/2016 at 16:32.
Pushed by cfeck into branch 'master'.

Add bookmarks support

REVIEW: 128522

M  +2-1CMakeLists.txt
M  +66   -2kcharselectdia.cc
M  +2-0kcharselectdia.h
M  +2-1kcharselectui.rc

http://commits.kde.org/kcharselect/c25c21fa4415ff25db49b674ec3003bdcf4c565e

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

[kio] [Bug 238309] folder in recycle bin makes dolphin fill up /tmp dir

[Götz via KDE Bugzilla]

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

--- Comment #7 from Götz  ---
The same with Dolphin 16.08 and KIO 5.25.

When /tmp fill up, many problems arise. I understand this doesn't occur always,
and is not easy to debug, and considering the consequences of a full /tmp,
could you give this bug more priority? There seems to be more affected users
and not tracked duplicates, some of them:

Hard spamming in /tmp when browsing the trash directory.
https://bugs.kde.org/show_bug.cgi?id=272249

Dolphins temporary files aren't deleted
https://bugs.kde.org/show_bug.cgi?id=208625

dolphin from git master pollutes /tmp/ with dolphin.* files
https://bugs.kde.org/show_bug.cgi?id=352975

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

[korganizer] [Bug 360065] crash when exit programs that use pim

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||denis.kurz+kdebugs@posteo.d
   ||e

--- Comment #3 from Denis Kurz  ---
Reporter in bug 368037 seems to suggest that this only happens "if I have
imported my google calendar".

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

[korganizer] [Bug 360065] crash when exit programs that use pim

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||miriam.r.garcia.mail@gmail.
   ||com

--- Comment #2 from Denis Kurz  ---
*** Bug 368037 has been marked as a duplicate of this bug. ***

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

[korganizer] [Bug 368037] Korganizer crashes when closing

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||denis.kurz+kdebugs@posteo.d
   ||e
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Denis Kurz  ---


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

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

[krita] [Bug 368111] New: [appimage] first run *.desktop shortcut creation. Not working and obligatory

[David REVOY via KDE Bugzilla]

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

Bug ID: 368111
   Summary: [appimage] first run *.desktop shortcut creation. Not
working and obligatory
   Product: krita
   Version: 3.0.1 Beta
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com

Created attachment 100887
  --> https://bugs.kde.org/attachment.cgi?id=100887=edit
[screenshot of the *.appimage file created instead of *.desktop]

Hi, recent Appimages ask for the creation of a shortcut *.desktop in a dialog
at start-up. 

Problems:

- If user choose 'No' the Appimage keep asking for creating the *.desktop file
at every start-up. ( something probably in all Appimage,  read comment of
HidariRyoushin here about Rambox doing the same behavior
https://www.reddit.com/r/LinuxActionShow/comments/50iefe/an_illustrated_guide_to_the_krita_appimage/
) 
- If user choose 'Yes' the Appimage create something in the
/home//.local/share/applications folder. It's a broken *.desktop
file, the extension is *.appimage. You can find a visual in attachement. (note:
If this file exist, the question dialog at start-up stops. )

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

[rekonq] [Bug 328181] Crash on http://www.idg.se/2.1085/1.535700/sa-livsfarlig-ar-din-billiga-piratladdare/sida/4/vi-letar-efter-fusk

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||denis.kurz+kdebugs@posteo.d
   ||e
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #17 from Denis Kurz  ---
This has been reported many times for various applications (akregator,
konqueror, kontact, rekonq, storageservicemanager), but only for 4.x versions
of KDE, which is based on Qt4. Looking at the backtraces of these reports, it
is quite obvious that this is a bug in QtWebkit4, which we do not control.
Support for Qt4 by the Qt Company has been dropped in late 2015.

I close this bug as resolved unmaintained, but you'd be advised not to hope for
a fix in Qt4, since the Qt Company dropped support for that in late 2015. I'd
be really surprised to see this bug pop up again in any recent,
Frameworks-based version of the afflicted applications. Of course, I gladly
reopen here if someone proves me wrong.

I'm sorry for the bad news, because I know that many of you are still bound to
use Qt4-based KDE applications. You might want to try the workaround proposed
in bug 361385, comment 1.

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

[akregator] [Bug 361816] Akregator crashes at the begining

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 CC||denis.kurz+kdebugs@posteo.d
   ||e
 Resolution|WAITINGFORINFO  |DUPLICATE

--- Comment #2 from Denis Kurz  ---


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

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