[kontact] [Bug 358153] New: Crash on exit kontact (no crash when exiting standalone apps)

2016-01-17 Thread Martin Tlustos via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358153

Bug ID: 358153
   Summary: Crash on exit kontact (no crash when exiting
standalone apps)
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com

Application: kontact ()

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

-- Information about the crash:
- What I was doing when the application crashed:
I tried to close the program. It doesn't matter whether I close it by clicking
on the top-right corner or via "file - exit".

Strange behaviour I have observed:
kontact always complains about kwallet not opening correctly ("several failed
attempts to open a wallet"). This does not happen if I use a standalone program
either.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f3d4beb6700 (LWP 6121)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3d7104f48b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f3d7104f4c9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f3d6c7ce6aa in start_thread (arg=0x7f3d4beb6700) at
pthread_create.c:333
#4  0x7f3d71f41eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f3d0b113700 (LWP 6122)):
#0  0x7f3d71f368dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f3d6bb511ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3d6bb512fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3d72a7729b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3d72a1d75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3d7283b3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3d728402be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3d6c7ce6aa in start_thread (arg=0x7f3d0b113700) at
pthread_create.c:333
#8  0x7f3d71f41eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f3d0961e700 (LWP 6123)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3d70d5d5b4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f3d7107f341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f3d6c7ce6aa in start_thread (arg=0x7f3d0961e700) at
pthread_create.c:333
#4  0x7f3d71f41eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f3d08dfe700 (LWP 6124)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3d70d5e5e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f3d7107f341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f3d6c7ce6aa in start_thread (arg=0x7f3d08dfe700) at
pthread_create.c:333
#4  0x7f3d71f41eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f3d03fff700 (LWP 6125)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3d70d5e5e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f3d7107f341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f3d6c7ce6aa in start_thread (arg=0x7f3d03fff700) at
pthread_create.c:333
#4  0x7f3d71f41eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f3d037fe700 (LWP 6126)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3d70d5e5e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f3d7107f341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f3d6c7ce6aa in start_thread (arg=0x7f3d037fe700) at
pthread_create.c:333
#4  0x7f3d71f41eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f3ce7042700 (LWP 6222)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3d008eb114 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f3d008eb159 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f3d6c7ce6aa in start_thread (arg=0x7f3ce7042700) at
pthread_create.c:333
#4  0x7f3d71f41eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

[plasmashell] [Bug 354386] System tray panel changes to secondary monitor that is on top/above on dual-monitor config

2016-01-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354386

--- Comment #9 from cher...@aip.de ---
A potential important info, that I forgot - I use the panel in auto-hide mode.

Another erratic behaviour that I observe is, that sometimes - when I logged out
with the second screen connected, the panel won't reappear on the laptop screen
on the next login when I detached the monitor in between sessions.

If this happens, I cannot just connect the second monitor and move the panel -
because of this bug: https://bugs.kde.org/show_bug.cgi?id=356727 - The only
solution then is to log out, connect to a monitor, log in again and then drag
the panel to laptop screen, log out - disconnect the 2nd monitor and then
finally I can log in to a working session.

If the bug is not fixed, any help from  for a possible workaround in this case
is highly desired, since I use my laptop for presentations - and at conferences
I cannot just connect to a second monitor after my presentation is over.

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


[kdelibs] [Bug 328571] autostart never finishes, ksmserver ignores logout/shutdown

2016-01-17 Thread paul6245 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=328571

--- Comment #63 from paul6245  ---
(In reply to Rex Dieter from comment #62)
> See comment #53 for when and where the fix was committed

Thanks Rex, but what does comment 53 actually mean. How do I use it to fix this
shutdown problem?

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


[korgac] [Bug 358152] New: korganizer reminder tool crashes at akonadi/kontact start

2016-01-17 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358152

Bug ID: 358152
   Summary: korganizer reminder tool crashes at akonadi/kontact
start
   Product: korgac
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: christiande...@web.de

Application: korgac (5.1.1)

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

-- Information about the crash:
Starting a new session for my user and then starting kontact often causes a
crash in the korganizer reminder tool, which makes DrKonqi appear.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KOrganizer-Erinnerungsmodul (korgac), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ffbc35e5800 (LWP 1447))]

Thread 5 (Thread 0x7ffba7bf0700 (LWP 1455)):
#0  0x7ffbbd29cc1d in poll () from /lib64/libc.so.6
#1  0x7ffbb6bbd422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7ffbb6bbf00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7ffba991b3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ffbbdbab32f in QThreadPrivate::start (arg=0xfab140) at
thread/qthread_unix.cpp:331
#5  0x7ffbb62ea0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7ffbbd2a504d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7ffb9d331700 (LWP 1464)):
#0  0x7ffbb5e0fcf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7ffbb5dcde4a in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ffbb5dcdf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ffbbd8b in QEventDispatcherGlib::processEvents
(this=0x7ffb980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ffbbdd84d53 in QEventLoop::exec (this=this@entry=0x7ffb9d330dd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ffbbdba661a in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7ffbbdbab32f in QThreadPrivate::start (arg=0x103afe0) at
thread/qthread_unix.cpp:331
#7  0x7ffbb62ea0a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7ffbbd2a504d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7ffb9cb30700 (LWP 1465)):
#0  0x7ffbbd2b161f in __libc_enable_asynccancel () from /lib64/libc.so.6
#1  0x7ffbbd298ce2 in read () from /lib64/libc.so.6
#2  0x7ffbb5e0eb60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7ffbb5dcd999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7ffbb5dcddf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7ffbb5dcdf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7ffbbd8b in QEventDispatcherGlib::processEvents
(this=0x7ffb98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7ffbbdd84d53 in QEventLoop::exec (this=this@entry=0x7ffb9cb2fdd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7ffbbdba661a in QThread::exec (this=) at
thread/qthread.cpp:503
#9  0x7ffbbdbab32f in QThreadPrivate::start (arg=0x1026590) at
thread/qthread_unix.cpp:331
#10 0x7ffbb62ea0a4 in start_thread () from /lib64/libpthread.so.0
#11 0x7ffbbd2a504d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ffb97fff700 (LWP 2210)):
#0  0x7ffbbd29cc1d in poll () from /lib64/libc.so.6
#1  0x7ffbb5dcde64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ffbb5dcdf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ffbbd8b in QEventDispatcherGlib::processEvents
(this=0x7ffb8c004130, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ffbbdd84d53 in QEventLoop::exec (this=this@entry=0x7ffb97ffedd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ffbbdba661a in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7ffbbdbab32f in QThreadPrivate::start (arg=0xfb35b0) at
thread/qthread_unix.cpp:331
#7  0x7ffbb62ea0a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7ffbbd2a504d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ffbc35e5800 (LWP 1447)):
[KCrash Handler]
#6  QVector::reserve (this=0x13e1980,
asize=asize@entry=0) at /usr/include/qt5/QtCore/qvector.h:366
#7  0x7ffbc21b9d54 in KCalCore::Calendar::setupRelations (this=0x10da230,
forincidence=...) at /usr/src/debug/kcalcore-15.12.1/src/calendar.cpp:1032
#8  0x7ffbc21f88ac in KCalCore::MemoryCalendar::addIncidence
(this=0x10da230, incidence=...) at
/usr/src/debug/kcalcore-15.12.1/src/memorycalendar.cpp:305
#9  0x7ffbc2b9ce9d in Akonadi::CalendarBasePrivate::internalInsert
(this=this@entry=0x1083860, item=...) at
/usr/src/debug/akonadi-calendar-15.12.1/src/calendarbase.cpp:158
#10 0x7ffbc2baac53 in 

[kdenlive] [Bug 357386] Git master 2016-01-01 - Saved custom filter stack has fixed keyframes

2016-01-17 Thread Evert Vorster via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357386

Evert Vorster  changed:

   What|Removed |Added

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

--- Comment #4 from Evert Vorster  ---
Fixed... 

Thanks for the fix, but. I would still like to be able to add keyframes to
some effects that don't have them now.

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


[frameworks-modemmanager-qt] [Bug 349478] Qualcomm 4G modem not recognised - Works under Gnome

2016-01-17 Thread Paul Konecny via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=349478

--- Comment #24 from Paul Konecny  ---
Hi Lamarque, 
it seems that this issue indeed was originating from the driver
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=59536da34513c594af2a6fd35ba65ea45b6960a1

According to this link it should be fixed in Kernel 4.4
As soon as I get my hands on this Kernel I'll retest. 
Thanks!

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


[korganizer] [Bug 358154] New: Second event modification reset date and time to nonsense

2016-01-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358154

Bug ID: 358154
   Summary: Second event modification reset date and time to
nonsense
   Product: korganizer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: michael.wey...@uni-bayreuth.de

If I change/modify an event a second time, the date is sett to the actual date
and the time will be set to 00:00 for start and 01:00 for end of the event.

Reproducible: Always

Steps to Reproduce:
1. Modify and event in calendar
2. After finishing the first changes, click on the event at the new date and
repeat to change.

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


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

2016-01-17 Thread Martin Tlustos via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354400

Martin Tlustos  changed:

   What|Removed |Added

 CC||martin.tlus...@gmail.com

--- Comment #9 from Martin Tlustos  ---
You need to add "ppa:kubuntu-ppa" (and maybe "ppa:kubuntu-backports") to your
repository. The version there is still 5.0.3, though, but 5.1 should make it
there eventually.

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


[plasmashell] [Bug 356994] Task manager shows windows from wrong screen or not at all in dual monitor setup

2016-01-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356994

--- Comment #7 from a.skemb...@gmail.com ---
Same here, today the problem is still here.

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


[kmix] [Bug 358150] New: kmix master channel crash

2016-01-17 Thread Damo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358150

Bug ID: 358150
   Summary: kmix master channel crash
   Product: kmix
   Version: 4.5
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: d.aitke...@gmail.com

Application: kmix (4.5)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.19.0-32-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed:
i was trying to select the master channel settings in kmix to change from
bluetooth to digital output

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

Thread 5 (Thread 0x7f1fea1e4700 (LWP 2523)):
#0  0x7f200f9096c4 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#1  0x7f200727768d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2007277f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f20072780ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f200f9097be in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f200f8db0af in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f200f8db3a5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f200f7d7c5f in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f200f8bc823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f200f7da32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x7f2007dfe182 in start_thread (arg=0x7f1fea1e4700) at
pthread_create.c:312
#11 0x7f2011e4547d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f1fe99e3700 (LWP 2538)):
#0  0x7f20072b961a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f20072b99a9 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2007277680 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2007277f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f20072780ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f200f9097be in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f200f8db0af in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f200f8db3a5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f200f7d7c5f in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f200f8bc823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x7f200f7da32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x7f2007dfe182 in start_thread (arg=0x7f1fe99e3700) at
pthread_create.c:312
#12 0x7f2011e4547d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f1feb6cd700 (LWP 11340)):
#0  0x7f2011e3812d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f20107c5031 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f20107b683c in pa_mainloop_poll () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f20107b6ece in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f20107b6f80 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f20107c4fe3 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f20077c1f08 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
#7  0x7f2007dfe182 in start_thread (arg=0x7f1feb6cd700) at
pthread_create.c:312
#8  0x7f2011e4547d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f1fdd625700 (LWP 32263)):
#0  0x7f2011e3812d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f2007277fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f20072780ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2007278129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f200729cf05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f2007dfe182 in start_thread (arg=0x7f1fdd625700) at
pthread_create.c:312
#6  0x7f2011e4547d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f2012582800 (LWP 2443)):
[KCrash Handler]
#5  0x7f1fe85e58bb in gtk_widget_set_direction () from
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#6  0x7f200efe146e in 

[kdelibs] [Bug 328571] autostart never finishes, ksmserver ignores logout/shutdown

2016-01-17 Thread Rex Dieter via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=328571

--- Comment #65 from Rex Dieter  ---
http://commits.kde.org/kinit/40c2bf7a551e379cbb61bd9491618031d7a6f8a6

was the patch committed to kinit framework, which was included in time for kde
frameworks 5.15 release.  Easiest thing to do would be to upgrade to kf5-5.15
https://www.kde.org/announcements/kde-frameworks-5.15.0.php
or newer, and see if that helps.

If your distro doesn't provide kf5-5.15 or newer, ask them to include the
patch/fix referenced here in their kinit builds.  (Sorry, I cannot give
detailed instructions on how to do your own patched builds, that's more
complicated and often specific to each distro).

If kinit-5.15 or newer doesn't fix things, you're likely hitting some different
issue than is documented here.

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


[kdenlive] [Bug 357780] git master 2016-01-10 - project fps change does not updatekeyframes on timeline

2016-01-17 Thread Evert Vorster via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357780

Evert Vorster  changed:

   What|Removed |Added

 Resolution|--- |REMIND
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Evert Vorster  ---
This is still an issue in most recent git.

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


[kdenlive] [Bug 350948] git master 2015-08-04 - changing project framerate does not update number of frames in source clips

2016-01-17 Thread Evert Vorster via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=350948

Evert Vorster  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|REMIND  |FIXED

--- Comment #13 from Evert Vorster  ---
It's fixed now...

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


[digikam] [Bug 358053] drag and drop across local collections does not do anything

2016-01-17 Thread Thomas Eschenbacher via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358053

--- Comment #6 from Thomas Eschenbacher  ---
Sorry, my mistake! You are right, that test was indeed across different
partitions, even different disks (both using btrfs). But with your latest patch
it is no longer reproducible here.

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


[kdelibs] [Bug 328571] autostart never finishes, ksmserver ignores logout/shutdown

2016-01-17 Thread paul6245 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=328571

--- Comment #64 from paul6245  ---
(In reply to Rex Dieter from comment #62)
> See comment #53 for when and where the fix was committed

Thanks Rex, but what does comment 53 actually mean. How do I use it to fix this
shutdown problem?

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


[plasma-nm] [Bug 358151] New: Ошибка при попытке редактирования OpenVPN соединения

2016-01-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358151

Bug ID: 358151
   Summary: Ошибка при попытке редактирования OpenVPN соединения
   Product: plasma-nm
   Version: 0.9.3.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: editor
  Assignee: lu...@kde.org
  Reporter: slava.blinni...@gmail.com
CC: jgrul...@redhat.com

Application: kde-nm-connection-editor (0.9.3.5)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-29-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
Каждый раз при попытке редактирования OpenVPN соединения возникает эта ошибка.
Соединения других типов нормально редактируются.

The crash can be reproduced every time.

-- Backtrace:
Application: Редактор соединений (kde-nm-connection-editor), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x7f50b18df3d9 in
SettingWidget::SettingWidget(QSharedPointer const&,
QWidget*, QFlags) () at
/usr/lib64/libplasmanetworkmanagement-editor.so
#6  0x7f50b18c347a in
IPv6Widget::IPv6Widget(QSharedPointer const&,
QWidget*, QFlags) () at
/usr/lib64/libplasmanetworkmanagement-editor.so
#7  0x7f50b18e3ab9 in ConnectionDetailEditor::initTabs() () at
/usr/lib64/libplasmanetworkmanagement-editor.so
#8  0x7f50b18ea6b2 in ConnectionDetailEditor::gotSecrets(QString const&,
bool, QMap > const&, QString const&) () at
/usr/lib64/libplasmanetworkmanagement-editor.so
#9  0x7f50b11af1fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#10 0x7f50b1559fad in NetworkManager::Connection::gotSecrets(QString
const&, bool, QMap > const&, QString const&)
() at /usr/lib64/libNetworkManagerQt.so.1
#11 0x7f50b155aa52 in
NetworkManager::Connection::onSecretsArrived(QDBusPendingCallWatcher*) () at
/usr/lib64/libNetworkManagerQt.so.1
#12 0x7f50b11af1fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#13 0x7f50aeab1b5f in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () at
/usr/lib64/libQtDBus.so.4
#14 0x7f50b11b359e in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#15 0x7f50afa2776c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#16 0x7f50afa2dcad in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#17 0x7f50b0bf2e0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#18 0x7f50b119b2ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#19 0x7f50b119e57d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#20 0x7f50b11c88fe in  () at /usr/lib64/libQtCore.so.4
#21 0x7f50ad446a04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#22 0x7f50ad446c48 in  () at /usr/lib64/libglib-2.0.so.0
#23 0x7f50ad446cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#24 0x7f50b11c80be in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#25 0x7f50afac4676 in  () at /usr/lib64/libQtGui.so.4
#26 0x7f50b1199e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#27 0x7f50b119a165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#28 0x7f50b119f5b9 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#29 0x0040a975 in  ()
#30 0x7f50aecf3b05 in __libc_start_main () at /lib64/libc.so.6
#31 0x0040aa82 in _start ()

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

Possible duplicates by query: bug 358031, bug 357459, bug 357219, bug 351732.

Reported using DrKonqi

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

[korgac] [Bug 358152] korganizer reminder tool crashes at akonadi/kontact start

2016-01-17 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358152

--- Comment #1 from Christian Trippe  ---
This is with korganizer 15.12.1 but if I remember correctly this happened also
with previous releases. This version is unfortunately not available in
bugzilla.

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


[digikam] [Bug 358149] Duplicate entry in JPEG2000 image extensions

2016-01-17 Thread Maik Qualmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358149

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.0.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/digi
   ||kam/d883d903bf46e9ec3d645fe
   ||5b12db81be75ef39a

--- Comment #1 from Maik Qualmann  ---
Git commit d883d903bf46e9ec3d645fe5b12db81be75ef39a by Maik Qualmann.
Committed on 18/01/2016 at 07:04.
Pushed by mqualmann into branch 'master'.

removes duplicate JPEG2000 image extension
FIXED-IN: 5.0.0

M  +2-1NEWS
M  +2-2app/utils/digikam_globals.cpp

http://commits.kde.org/digikam/d883d903bf46e9ec3d645fe5b12db81be75ef39a

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


[plasma-nm] [Bug 358151] Ошибка при попытке редактирования OpenVPN соединения

2016-01-17 Thread Jan Grulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358151

Jan Grulich  changed:

   What|Removed |Added

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

--- Comment #1 from Jan Grulich  ---


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

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


[plasma-nm] [Bug 341650] Connection manager crashes when editing/adding openVPN connection

2016-01-17 Thread Jan Grulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341650

Jan Grulich  changed:

   What|Removed |Added

 CC||slava.blinni...@gmail.com

--- Comment #15 from Jan Grulich  ---
*** Bug 358151 has been marked as a duplicate of this bug. ***

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


[digikam] [Bug 358053] drag and drop across local collections does not do anything

2016-01-17 Thread Maik Qualmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358053

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/digi
   ||kam/2065450d991966c46e9a96d
   ||be87d7a28b7d13ee0

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


[plasmashell] [Bug 355592] Thumbnail icons in folder view layout desktop have wrong fixed 1:1 aspect ratio

2016-01-17 Thread garwol via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355592

garwol  changed:

   What|Removed |Added

 CC||bikemac...@wp.pl

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


[Phonon] [Bug 358111] Kphotoalbum (KPA) crashed, on trying to view a mpeg file

2016-01-17 Thread Johannes Zarl-Zierl via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358111

Johannes Zarl-Zierl  changed:

   What|Removed |Added

Product|kphotoalbum |Phonon
  Component|general |general
Version|4.6.2   |unspecified
   Assignee|kpab...@willden.org |sit...@kde.org
 CC||johan...@zarl.at,
   ||myr...@kde.org,
   ||romain.per...@gmail.com

--- Comment #1 from Johannes Zarl-Zierl  ---
Thanks for the bug report!

Judging from the backtrace, it seems like the crash happened in either phonon
or libvlccore. I'm therefore moving this bug to Phonon...

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


[plasmashell] [Bug 347268] thumb on the desktop are streched

2016-01-17 Thread garwol via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=347268

garwol  changed:

   What|Removed |Added

 CC||bikemac...@wp.pl

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


[kdenlive] [Bug 357921] returns "not a valid project file" for all previous projects after update

2016-01-17 Thread joaorlazaro via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357921

joaorlazaro  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

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


[digikam] [Bug 358053] drag and drop across local collections does not do anything

2016-01-17 Thread Thomas Eschenbacher via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358053

--- Comment #4 from Thomas Eschenbacher  ---
No, the collections were on the same partition.
I tried the latest git commit and now it works!
Thanks for fixing it :-)

(unfortunately I found out that moving files with special characters does not
work too, I will file a new bug report for that...)

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


[digikam] [Bug 358144] New: moving images with special characters in the file name does not work

2016-01-17 Thread Thomas Eschenbacher via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358144

Bug ID: 358144
   Summary: moving images with special characters in the file name
does not work
   Product: digikam
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Albums View
  Assignee: digikam-de...@kde.org
  Reporter: thomas.eschenbac...@gmx.de

image files that contain special characters in the file name cannot be moved

Reproducible: Always

Steps to Reproduce:
1. within one album, store an image with a special character (or rename on the
shell), for example "Picture(1).jpg"
2. try to drag it into another location

Actual Results:  
nothing happens, the file is not moved, the drag operation just does
nothing, no debug or error message visible on the console.


This sounds related to bug #355256, but I guess it is a different cause, in my
case I have file names with only "(number)" at the end and only ASCII
characters, so it does not look like an UTF-8 encoding issue. When I rename the
files manually on the console, so that they contain no brackets anymore, I can
move them as expected, so there is not problem with permissions or so. I also
cross-checked and renamed a file back, to "Picture(1).jpg" and it was no longer
movable. AFAIR it is not drag specific, also cut does not work.

BTW: the thumbnail engine seems to have no problem with these files, thumbnails
are shown

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


[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT

2016-01-17 Thread AnAkkk via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356992

AnAkkk  changed:

   What|Removed |Added

 CC||anakin...@gmail.com

--- Comment #28 from AnAkkk  ---
There seem to be a mistake in the patch:

EGLDisplay dpy = eglGetDisplay(EGL_DEFAULT_DISPLAY);
if (dpy == EGL_NO_DISPLAY)
dpy = eglGetDisplay(EGL_DEFAULT_DISPLAY);

I guess the first line was not supposed to be changed, as this is now calling
the same function again with the same parameters in case it fails.

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


[krita] [Bug 346165] OSX: No pen pressure when OpenGL is turned off

2016-01-17 Thread wolthera via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=346165

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #12 from wolthera  ---
Hi Anton, we literally released a 3.0 pre-alpha today. You might want to check
if the bug is fixed on there. Check krita.org news posts for this. Also take
the survey linked at the end of the post.

It may be that it doesn't even work at all, but it does contain a few months of
effort to try and fix this problem, and while we know that we're still not
done, it might be a much bigger improvement.

Solutions like hotkeying openGL is something we would very much like to avoid,
because the experience should be seamless.

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


[kphotoalbum] [Bug 340211] KPA should invalidate/update metadata when a changed image is detected.

2016-01-17 Thread Andreas Schleth via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=340211

Andreas Schleth  changed:

   What|Removed |Added

 CC||schleth...@web.de

--- Comment #3 from Andreas Schleth  ---
I do not think, this is a completely good idea.

I often do some minor repairs to images after tagging.  I even have a tag:
"Nacharbeit" = "repair something".  So, I would not want my image data to
change because of this.

Updating the thumbnail would be very OK.
Changing tags, time and such much less.

I do not understand: why should the GPS-Info be changed?  
I guess it is a rare case that an image would be replaced by a completely
different image from another location.  In this case you could easily import
the image as new and delete the old one.

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


[krita] [Bug 358137] New: Krita crashes after splash window is displayed

2016-01-17 Thread Ron via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358137

Bug ID: 358137
   Summary: Krita crashes after splash window is displayed
   Product: krita
   Version: 2.9.10
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: r...@first-rate.info

Application: krita (2.9.10)
KDE Platform Version: 4.14.13 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 3.13.0-74-generic i686
Distribution: Ubuntu 14.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Trying to start Krita, it crashes immediately after splash window is displayed.
- My setup:
Two monitors plus Wacom Intuos 4 tablet

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0xb779f428 in __kernel_vsyscall ()
#7  0xb5b28607 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#8  0xb5b2ba33 in __GI_abort () at abort.c:89
#9  0xb5e08d73 in qt_message_output(QtMsgType, char const*) () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#10 0xb5e09127 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#11 0xb5e09658 in qFatal(char const*, ...) () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#12 0xb5e0971d in qt_assert_x(char const*, char const*, char const*, int) ()
from /usr/lib/i386-linux-gnu/libQtCore.so.4
#13 0xb70c77af in operator[] (i=-1, this=0xbfa36da4) at
/usr/include/qt4/QtCore/qlist.h:477
#14 KisConfig::getScreenProfile (screen=screen@entry=-1) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/kis_config.cc:409
#15 0xb70c7aab in KisConfig::displayProfile (this=this@entry=0xbfa36ef8,
screen=-1) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/kis_config.cc:441
#16 0xb7342ba3 in KisScratchPad::setupScratchPad (this=0x9bd24b8,
resourceProvider=resourceProvider@entry=0x9a39110, defaultColor=...) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/widgets/kis_scratch_pad.cpp:340
#17 0xb732c4cb in KisPaintOpPresetsPopup::KisPaintOpPresetsPopup
(this=0x9bceeb0, resourceProvider=0x9a39110, parent=0x0) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/widgets/kis_paintop_presets_popup.cpp:88
#18 0xb7187f5d in KisPaintopBox::KisPaintopBox (this=0x9b51f18, view=0x99936c0,
parent=0x95b3f50, name=0xb75c4c6e "paintopbox") at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/kis_paintop_box.cc:359
#19 0xb70ca3dc in KisControlFrame::KisControlFrame (this=0x9ae2d48,
view=0x99936c0, parent=0x95b3f50, name=0x0) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/kis_control_frame.cpp:119
#20 0xb7476139 in KisViewManager::KisViewManager (this=0x99936c0,
parent=0x95b3f50, _actionCollection=0x9a61c88) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/KisViewManager.cpp:328
#21 0xb74316eb in KisMainWindow::KisMainWindow (this=0x95b3f50,
__in_chrg=, __vtt_parm=) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/KisMainWindow.cpp:286
#22 0xb743d277 in KisPart::createMainWindow (this=0x9a07800) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/KisPart.cpp:259
#23 0xb73d6383 in KisApplication::start (this=this@entry=0xbfa378f4) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/ui/KisApplication.cpp:418
#24 0x08049f83 in main (argc=1, argv=0xbfa379e4) at
/build/krita-2.9-PhCyNx/krita-2.9-2+git20151209+r43/krita/main.cc:192

Possible duplicates by query: bug 321758.

Reported using DrKonqi

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


[plasmashell] [Bug 358138] New: Plasma shell crashes when trying to delete a desktop icon

2016-01-17 Thread Heinrich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358138

Bug ID: 358138
   Summary: Plasma shell crashes when trying to delete a desktop
icon
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: heinr...@quantentunnel.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

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

-- Information about the crash:
select desktop icon with right mouseklick ->  select "move to trash" from
context menu -> crash
Plasma shell is terminated (error message shown) and restarts after I agree to
terminate it automatically . I can then repeat these steps (tried three times).

The crash can be reproduced every time.

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

Thread 12 (Thread 0x7fc985528700 (LWP 5069)):
#0  0x7fc996a55c1d in poll () at /lib64/libc.so.6
#1  0x7fc99b981422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fc99b98300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fc987cab3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc99714d32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc99625f0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fc996a5e04d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fc97e42e700 (LWP 5071)):
#0  0x7fc993179cf5 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc993137e16 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc993137f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc99737fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc997326d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc99714861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc99a433df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc99714d32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc99625f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc996a5e04d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fc97246d700 (LWP 5086)):
#0  0x7fc997145cc5 in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5
#1  0x7fc997380895 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7fc9931378f1 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc993137df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fc993137f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fc99737fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fc997326d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fc99714861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fc99a433df8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7fc99714d32f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fc99625f0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fc996a5e04d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fc970935700 (LWP 5089)):
#0  0x7fc9931374a0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7fc993137d80 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc993137f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc99737fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc997326d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc99714861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc99a433df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc99714d32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc99625f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc996a5e04d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fc96af84700 (LWP 5090)):
#0  0x7fc99626305f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc99cbe886b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fc99cbe8899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fc99625f0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc996a5e04d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fc8e3927700 (LWP 5095)):
#0  0x7fff9f7a2b26 in clock_gettime ()
#1  0x7fc996a6ac9d in clock_gettime () at /lib64/libc.so.6
#2  0x7fc9971fe7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fc99737e3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fc99737e945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc99737fb5e in  () at 

[kdenlive] [Bug 358044] Lumakey Effect listed but does not work

2016-01-17 Thread Jean-Baptiste Mardelle via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358044

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||j...@kdenlive.org

--- Comment #1 from Jean-Baptiste Mardelle  ---
Created attachment 96701
  --> https://bugs.kde.org/attachment.cgi?id=96701=edit
Luma key effect

The Lumakey effect changes the clip's alpha channel. So the see it's effect,
you need a transition (like composite transition that is available in tracks)
and another clip beneath.

Works in my tests (see attached screenshot)

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


[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT

2016-01-17 Thread Uriy Zhuravlev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356992

--- Comment #27 from Uriy Zhuravlev  ---
>Let's get this off the list

Good! Patch works well.

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


[Phonon] [Bug 357229] amarok: skips track, jumps to middle of next track, when switching to next song in playlist

2016-01-17 Thread Florian Lindner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357229

--- Comment #8 from Florian Lindner  ---
I have listened to a couple of songs until Amarok skipped one song. After
playing 5 seconds of the next song I stopped and quit Amarok.

Backend is

gstreamer 1.6.2-1
gstreamer0.10 0.10.36-4

Whatever KDE uses for backend.

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


[kwin] [Bug 357032] KWin crashes after RubyMine sync window close

2016-01-17 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357032

--- Comment #11 from Thomas Lübking  ---
Sorry for the delay.

Does this fix it?

diff --git a/scene.cpp b/scene.cpp
index e673853..ad5ca6d 100644
--- a/scene.cpp
+++ b/scene.cpp
@@ -825,9 +825,8 @@ WindowQuadList Scene::Window::buildQuads(bool force) const
 AbstractClient *client = dynamic_cast(toplevel);
 QRegion contents = clientShape();
 QRegion center = toplevel->transparentRect();
-QRegion decoration = (client && true ?
-  QRegion(client->decorationRect()) : shape()) -
center;
-ret = makeQuads(WindowQuadContents, contents,
client->clientContentPos());
+QRegion decoration = (client ? QRegion(client->decorationRect()) :
shape()) - center;
+ret = makeQuads(WindowQuadContents, contents,
toplevel->clientContentPos());

 QRect rects[4];
 bool isShadedClient = false;

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

[kdenlive] [Bug 356963] "Check if first added clip matches project profile" no longer activates

2016-01-17 Thread Jean-Baptiste Mardelle via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356963

--- Comment #12 from Jean-Baptiste Mardelle  ---
Git commit dcd2511b64855e191a877788693298762cb144db by Jean-Baptiste Mardelle.
Committed on 17/01/2016 at 19:05.
Pushed by mardelle into branch 'master'.

Rephrase message on unknown profile.
Make sure profile created from clip has width multiple of 8 (required in some
parts of MLT)

M  +8-8src/bin/bin.cpp
M  +1-1src/definitions.cpp
M  +6-2src/doc/kdenlivedoc.cpp

http://commits.kde.org/kdenlive/dcd2511b64855e191a877788693298762cb144db

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


[okular] [Bug 358066] [Wishlist] Improved popup note

2016-01-17 Thread Simone Gaiarin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358066

Simone Gaiarin  changed:

   What|Removed |Added

 CC||visual-des...@kde.org

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


[okular] [Bug 358057] [Usability] Permanent/sticky annotation feature is hard to discover

2016-01-17 Thread Simone Gaiarin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358057

Simone Gaiarin  changed:

   What|Removed |Added

 CC||visual-des...@kde.org

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


[kmail2] [Bug 358116] messageviewer leaks temporary files with mail parts in it

2016-01-17 Thread Laurent Montel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358116

--- Comment #4 from Laurent Montel  ---
For me it's when kmail crash.
I will look at how to clean up it during crash.

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


[systemsettings] [Bug 345743] The multimedia key 'toggle touchpad' does nothing, and setting it as a shortcut for kcm_touchpad behaves weird

2016-01-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345743

frederick...@gmail.com changed:

   What|Removed |Added

 CC||frederick...@gmail.com

--- Comment #5 from frederick...@gmail.com ---
I'm running Kubuntu 15.10 with Plasma 5.4.2 and confirmed the problem.

The problem is quite easy to solve. Open ~/.config/kglobalshortcutsrc by any
editor and replace all ,ៀ? with ,ៀ (delete the question mark in other words).

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

[kdenlive] [Bug 357710] wipe transition uses incorrect shape size when using a png lumas file

2016-01-17 Thread Jean-Baptiste Mardelle via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357710

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||j...@kdenlive.org

--- Comment #2 from Jean-Baptiste Mardelle  ---
Thanks for your report and feedback.
We are going to switch back to ppm files for the next 15.12.2 release.

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


[kdenlive] [Bug 357710] wipe transition uses incorrect shape size when using a png lumas file

2016-01-17 Thread Jean-Baptiste Mardelle via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357710

--- Comment #3 from Jean-Baptiste Mardelle  ---
err.. I mean pgm files.

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


[kdenlive] [Bug 357710] wipe transition uses incorrect shape size when using a png lumas file

2016-01-17 Thread Jean-Baptiste Mardelle via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357710

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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


[Phonon] [Bug 357229] amarok: skips track, jumps to middle of next track, when switching to next song in playlist

2016-01-17 Thread Florian Lindner via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357229

--- Comment #7 from Florian Lindner  ---
Created attachment 96703
  --> https://bugs.kde.org/attachment.cgi?id=96703=edit
Output of amarok --debug-audio 2>&1

I have listened to a couple of songs until Amarok skipped one song. After
playing 5 seconds of the next song I stopped and quit Amarok.

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


[kcalc] [Bug 353644] Constants buttons do not work

2016-01-17 Thread ralph via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353644

ralph  changed:

   What|Removed |Added

 CC||rams...@virgilio.it

--- Comment #3 from ralph  ---
Same problem on openSUSE Leap 42.1
KCalc 15.12.0 - KDE Frameworks 5.18.0 - Qt 5.5.1 (built against 5.5.1)

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


[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT

2016-01-17 Thread AnAkkk via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356992

--- Comment #30 from AnAkkk  ---
No problem :)

I don't know anything about EGL, but shouldn't the call be
eglGetCurrentDisplay() instead of eglGetDisplay() like it is in the updated
patched version? Seems like eglGetDisplay always take a parameter.

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


[krita] [Bug 358137] Krita crashes after splash window is displayed

2016-01-17 Thread Ron via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358137

--- Comment #1 from Ron  ---
When I switch off my Intuos tablet and try to start Krita, it still crashes
immediately after splash.
When I go to Settings > System Settings > Display Config > disable the 2nd
monitor, with Intuos tablet switched on, Krita opens normally.
So, the problem appears to be related to using two monitors.

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


[okular] [Bug 341914] Allow Annotation Tools in Toolbar

2016-01-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341914

kde...@2hh.at changed:

   What|Removed |Added

 CC||kde...@2hh.at

--- Comment #3 from kde...@2hh.at ---
I do think it is common sense that all kind of tools can be placed indiviually
in toolbars which each user can hide or show as desired. To my opnion it is
more than strange that this one toolbar can only be displayed by switching it
to visible every time it is neede. It should be a decision of the user and not
of the developers if and when a toolbar shall be visible or not.

Kind regards

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


[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT

2016-01-17 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356992

Thomas Lübking  changed:

   What|Removed |Added

  Flags||ReviewRequest+
URL||https://git.reviewboard.kde
   ||.org/r/126783/

--- Comment #26 from Thomas Lübking  ---
Let's get this off the list
https://git.reviewboard.kde.org/r/126783/

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

[digikam] [Bug 358053] drag and drop across local collections does not do anything

2016-01-17 Thread Maik Qualmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358053

--- Comment #5 from Maik Qualmann  ---
(In reply to Thomas Eschenbacher from comment #4)
> No, the collections were on the same partition.

Strange, I can confirm the problem only for different partitions. What a file
system do you use?

Maik

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


[kdeplasma-addons] [Bug 351827] No way to see elided application names in Application Dashboard in full

2016-01-17 Thread Bob Wya via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351827

Bob Wya  changed:

   What|Removed |Added

 CC||bob.mt@gmail.com

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


[krunner] [Bug 358140] New: krunner crashed sometimes

2016-01-17 Thread Rafis Kamaliev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358140

Bug ID: 358140
   Summary: krunner crashed sometimes
   Product: krunner
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: ra...@pisem.net

-- Information about the crash:
- What I was doing when the application crashed:
1. Launched krunner using Alt+F2
2. entered application name in krunner

Reproducible: Sometimes

Steps to Reproduce:
1. Launched krunner using Alt+F2
2. entered application name in krunner

Actual Results:  
crash

Expected Results:  
run an application

Application: krunner

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

-- Information about the crash:
- What I was doing when the application crashed:
1. Launched krunner using Alt+F2
2. entered application name in krunner

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

Thread 12 (Thread 0x7f3d8d768700 (LWP 1919)):
#0  0x7f3da01c0c1d in poll () at /lib64/libc.so.6
#1  0x7f3d9f6ce422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f3d9f6d000f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f3d8feeb3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f3da08b832f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f3d9e02e0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f3da01c904d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f3d81f30700 (LWP 1940)):
#0  0x7f3da09697c0 in  () at /usr/lib64/libQt5Core.so.5
#1  0x7f3da0ae93b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#2  0x7f3da0ae9945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f3da0aeab5e in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f3d9d6c74ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f3d9d6c7d80 in  () at /usr/lib64/libglib-2.0.so.0
#6  0x7f3d9d6c7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f3da0aead8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#8  0x7f3da0a91d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#9  0x7f3da08b361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#10 0x7f3da2f66df8 in  () at /usr/lib64/libQt5Qml.so.5
#11 0x7f3da08b832f in  () at /usr/lib64/libQt5Core.so.5
#12 0x7f3d9e02e0a4 in start_thread () at /lib64/libpthread.so.0
#13 0x7f3da01c904d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f3d78f3f700 (LWP 4826)):
#0  0x7f3d9e03205f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3da08b934b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f3da365725b in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f3da36576f3 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f3da08b832f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f3d9e02e0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f3da01c904d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f3d68252700 (LWP 4827)):
#0  0x7f3d9e03205f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3da08b934b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f3d7a77b65f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f3d7a77f43a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f3d7a7796cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f3d7a77f481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f3d7a7796cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f3d7a77d005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f3da08b832f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f3d9e02e0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f3da01c904d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f3d67a51700 (LWP 4828)):
[KCrash Handler]
#6  0x7f3da091bd30 in QHashData::rehash(int) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f3d9f013dbc in KIconLoader::hasIcon(QString const&) const () at
/usr/lib64/libKF5IconThemes.so.5
#8  0x7f3d9f00bcf1 in KIconEngine::availableSizes(QIcon::Mode,
QIcon::State) const () at /usr/lib64/libKF5IconThemes.so.5
#9  0x7f3da1065e23 in QIcon::availableSizes(QIcon::Mode, QIcon::State)
const () at /usr/lib64/libQt5Gui.so.5
#10 0x7f3da1066792 in QIcon::fromTheme(QString const&, QIcon const&) () at

[krita] [Bug 352499] Crashed when I started using the brush

2016-01-17 Thread Markus L via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352499

--- Comment #10 from Markus L  ---
(In reply to Markus L from comment #9)
> No crashing, when I test new 3.0 pre-alpha version. Windows 10 64 Pro , same
> Trust tablet as no my earlier comments.

...ON my earlier comments.

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


[plasmashell] [Bug 358143] New: Segmentation fault during normal usage (both autostart and manual start)

2016-01-17 Thread Rémi Verschelde via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358143

Bug ID: 358143
   Summary: Segmentation fault during normal usage (both autostart
and manual start)
   Product: plasmashell
   Version: 5.5.3
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: XembedSNIProxy
  Assignee: plasma-b...@kde.org
  Reporter: rversche...@gmail.com

Created attachment 96702
  --> https://bugs.kde.org/attachment.cgi?id=96702=edit
Console output and gdb backtrace around a segfault

Using Plasma 5.5.3 on Mageia Cauldron 64-bit with Qt 5.6.0-beta.

XembedSNIProxy seems to segfault relatively often with (so far) no reliable
pattern that I could identify. I've opened a bug report on Mageia's bugzilla
about this issue, where I started to do some investigation:
https://bugs.mageia.org/show_bug.cgi?id=17516

The utility is properly started with plasmashell, but apparently crashes after
a short while. Running it again from a terminal seem to show that it's a
segmentation fault, though it can happen after quite a long time of normal
usage (including legacy icons for hexchat, clementine, Mageia's net_applet and
mgaapplet).

I ran it through gdb and just got this crash:

---
kde.xembedsniproxy: trying to dock window  75497483
kde.xembedsniproxy: adding damage watch for  75497483

Program received signal SIGSEGV, Segmentation fault.
0x0040e697 in SNIProxy::SNIProxy (this=0x709d30, wid=75497483,
parent=) at
/usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/sniproxy.cpp:165
165 if (clientGeom->width > s_embedSize || clientGeom->height >
s_embedSize )
---

And the backtrace:
---
(gdb) bt
#0  0x0040e697 in SNIProxy::SNIProxy(unsigned int, QObject*)
(this=0x709d30, wid=75497483, parent=)
at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/sniproxy.cpp:165
#1  0x0040c3f3 in FdoSelectionManager::dock(unsigned int)
(this=this@entry=0x7fffd970, winId=75497483)
at
/usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/fdoselectionmanager.cpp:157
#2  0x0040c55c in FdoSelectionManager::nativeEventFilter(QByteArray
const&, void*, long*) (this=0x7fffd970, eventType=...,
message=0x7fffe4004ee0, result=)
at
/usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/fdoselectionmanager.cpp:124
#3  0x76958237 in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(this=, eventType=..., message=message@entry=0x7fffe4004ee0,
result=result@entry=0x7fffd478) at kernel/qabstracteventdispatcher.cpp:460
#4  0x7fffee33a0c5 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(this=this@entry=0x641be0, event=event@entry=0x7fffe4004ee0) at
qxcbconnection.cpp:1062
#5  0x7fffee33afb6 in QXcbConnection::processXcbEvents() (this=0x641be0) at
qxcbconnection.cpp:1672
#6  0x7698706a in QObject::event(QEvent*) (this=0x641be0, e=) at kernel/qobject.cpp:1256
#7  0x7695b1ea in QCoreApplication::notify(QObject*, QEvent*)
(event=, receiver=) at
kernel/qcoreapplication.cpp:1088
#8  0x7695b1ea in QCoreApplication::notify(QObject*, QEvent*)
(this=, receiver=, event=) at
kernel/qcoreapplication.cpp:1074
#9  0x7695b348 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x641be0, event=event@entry=0x7fffe4006d40) at
kernel/qcoreapplication.cpp:1013
#10 0x7695d16b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (event=0x7fffe4006d40, receiver=) at
kernel/qcoreapplication.h:227
#11 0x7695d16b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x635710)
at kernel/qcoreapplication.cpp:1648
#12 0x7695d638 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1506
#13 0x769ad1d3 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x6910c0) at kernel/qeventdispatcher_glib.cpp:270
#14 0x72e70267 in g_main_context_dispatch (context=0x7fffe40016f0) at
gmain.c:3154
#15 0x72e70267 in g_main_context_dispatch
(context=context@entry=0x7fffe40016f0) at gmain.c:3769
#16 0x72e70498 in g_main_context_iterate
(context=context@entry=0x7fffe40016f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3840
#17 0x72e7053c in g_main_context_iteration (context=0x7fffe40016f0,
may_block=may_block@entry=1) at gmain.c:3901
#18 0x769ad5e6 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x68edf0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#19 0x7695903a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fffd8d0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#20 0x76961541 in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1283
#21 

[KBibTeX] [Bug 357883] Can't save .bib file to a remote file system mounted with SSHFS

2016-01-17 Thread Thomas Fischer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357883

Thomas Fischer  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Thomas Fischer  ---
Just tested myself, mounting a remote SSH folder via sshfs. Started KBibTeX,
created a new file, added an entry, saved it in mounted directory. Then exited
KBibTeX, restarted, opened test file, added another entry, saved again. No
problems, file and its backup (...~) were correctly written on remote
filesystem.

KBibTeX is performing only basic I/O operations, nothing special like locks or
permissions. From experience, I know that remote filesystems are all very shaky
and all kinds of things can go wrong. Just look at the many options sshfs
allows you to work around particular issues.
BTW, is the directory you are mounting via sshfs maybe mounted from somewhere
else via e.g. NFS to the machine you are ssh'ing to? Just look for "nfs
identity mapping" for starters ...

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


[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT

2016-01-17 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356992

--- Comment #29 from Thomas Lübking  ---
Hehe - many thanks for covering my ass =)

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

[kwin] [Bug 337355] plasma 5 panel gets too transparent in desktop cube

2016-01-17 Thread Bob Wya via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=337355

Bob Wya  changed:

   What|Removed |Added

 CC||bob.mt@gmail.com

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


[kphotoalbum] [Bug 340211] KPA should invalidate/update metadata when a changed image is detected.

2016-01-17 Thread Johannes Zarl-Zierl via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=340211

--- Comment #2 from Johannes Zarl-Zierl  ---
No. This has not yet been implemented.

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


[krita] [Bug 346165] OSX: No pen pressure when OpenGL is turned off

2016-01-17 Thread Anton via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=346165

Anton  changed:

   What|Removed |Added

 CC||kad...@gmail.com

--- Comment #11 from Anton  ---
I use 2.9.9 (git b4ac381) using mac os. I have the same bug and "ceremony"
works as mentioned by guruguru...@outlook.jp 

My suggestion is to make possible to create shortcut for "Enable/Disabled
OpenGL" that we do not spend much time to switch on/off. (it's not possible
right now)

Another bug I leave it here: Krita freezes when you paint by stylus or even
mouse. Workaround is to use "Show canvas only" mode then it works great!

_
MacBook Pro (Retina, 15-inch, Mid 2014)
2,5 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 750M 2048 MB

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


[plasmashell] [Bug 358141] New: Spotify app for Linux crashing after start

2016-01-17 Thread Spectro via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358141

Bug ID: 358141
   Summary: Spotify app for Linux crashing after start
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: imanen...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

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

-- Information about the crash:
Manually added repository for Spotify, got it installed. From then on, every
time I start the app, it crashes.

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

Thread 10 (Thread 0x7f769a190700 (LWP 1282)):
#0  0x7f76a92df8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f76ad326bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f76ad32874f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f769c4daa39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7f76a99d22be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f76a8ac16aa in start_thread (arg=0x7f769a190700) at
pthread_create.c:333
#6  0x7f76a92eaeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f76939da700 (LWP 1296)):
#0  0x7f76a92df8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f76a608c1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f76a608c2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f76a9c0929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f76a9baf75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f76a99cd3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f76ac1f5f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f76a99d22be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f76a8ac16aa in start_thread (arg=0x7f76939da700) at
pthread_create.c:333
#9  0x7f76a92eaeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f7688617700 (LWP 1300)):
#0  0x7f76a6089278 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f76a608b71b in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f76a608c11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f76a608c2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f76a9c0929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f76a9baf75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f76a99cd3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f76ac1f5f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f76a99d22be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f76a8ac16aa in start_thread (arg=0x7f7688617700) at
pthread_create.c:333
#10 0x7f76a92eaeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f7685e74700 (LWP 1307)):
#0  0x7f76a608b7c1 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f76a608c11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f76a608c2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f76a9c0929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f76a9baf75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f76a99cd3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f76ac1f5f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f76a99d22be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f76a8ac16aa in start_thread (arg=0x7f7685e74700) at
pthread_create.c:333
#9  0x7f76a92eaeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f7677fff700 (LWP 1312)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f76ae581114 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f76ae581159 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f76a8ac16aa in start_thread (arg=0x7f7677fff700) at
pthread_create.c:333
#4  0x7f76a92eaeed in clone () at

[plasmashell] [Bug 358142] New: Plasma crashes with nouveau driver

2016-01-17 Thread Cesko Voeten via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358142

Bug ID: 358142
   Summary: Plasma crashes with nouveau driver
   Product: plasmashell
   Version: 5.5.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: cvoe...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

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

Logging into the system.

- Unusual behavior I noticed:

If I use openbox as window manager as opposed to kwin, I can at least make it
to the desktop (although with a few small kernel complaints; no stacktraces
though) and the shell does not crash until I click the lower-left K launcher
icon (replacing it with the 'Application menu' launcher allows me to launch
applications without crashing the shell).

It is of extreme importance to note that there are massive complaints from the
kernel during my failed attempt to log in. I'm unsure if these are the result
of my issues (KDE supplying incorrect commands to the driver?) or the cause
(driver itself broken)? It should be noted that other GL apps work completely
fine with zero issues - e.g. GNOME 3, really any 3D game, KDE 4, etc.; this is
why I did not immediately discount this issue as an upstream problem, but
wanted to ask you guys first (and the stacktrace also says 'your kernel is
fine' ;) ). See below:

[   88.010981] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 0020024b08 put 0020028a50 ib_get 0022 ib_put 0023 state 4004
(err: INVALID_MTHD) push 00406040
[   88.011148] nouveau :01:00.0: gr: DATA_ERROR 000c [INVALID_BITFIELD] 
[   88.011157] nouveau :01:00.0: gr: 0010 [] ch 4 [001f935000
ksplashqml[538]] subc 3 class 8297 mthd 0da0 data 0004721c  
[   88.012372] nouveau :01:00.0: fifo: CACHE_ERROR - ch 4 [ksplashqml[538]]
subc 0 mthd  data 0438  
[   88.027726] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 00200298b8 put 002002d42c ib_get 0028 ib_put 0029 state 8000
(err: INVALID_CMD) push 00406040
[   88.027887] nouveau :01:00.0: gr: DATA_ERROR 0004 [INVALID_VALUE]
[   88.027901] nouveau :01:00.0: gr: 0010 [] ch 4 [001f935000
ksplashqml[538]] subc 3 class 8297 mthd 0e58 data 00146200  
[   88.044326] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 002002d8c8 put 0020031308 ib_get 002e ib_put 002f state 80006e2c
(err: INVALID_CMD) push 00406040
[   88.044499] nouveau :01:00.0: gr: DATA_ERROR 0004 [INVALID_VALUE]
[   88.044507] nouveau :01:00.0: gr: 0010 [] ch 4 [001f935000
ksplashqml[538]] subc 3 class 8297 mthd 0e28 data 0004721c  
[   88.146068] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 002003976c put 0020039864 ib_get 003c ib_put 003d state 8000a314
(err: INVALID_CMD) push 00406040
[   88.177723] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 002003ab6c put 002003c034 ib_get 0040 ib_put 0041 state 80008861
(err: INVALID_CMD) push 00406040
[   88.211021] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 002003d9d4 put 0020041de8 ib_get 0046 ib_put 0047 state 80007780
(err: INVALID_CMD) push 00406040
[   88.211192] nouveau :01:00.0: gr: DATA_ERROR 000c [INVALID_BITFIELD] 
[   88.211203] nouveau :01:00.0: gr: 0010 [] ch 4 [001f935000
ksplashqml[538]] subc 3 class 8297 mthd 153c data 00106d80  
[   88.227714] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 0020042844 put 0020046c80 ib_get 004e ib_put 004f state 80007220
(err: INVALID_CMD) push 00406040
[   88.244313] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 0020047960 put 002004c170 ib_get 0054 ib_put 0055 state 80007780
(err: INVALID_CMD) push 00406040
[   88.294545] nouveau :01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[538]]
get 0020053f0c put 0020056ed8 ib_get 0065 ib_put 0066 state 80006c08
(err: INVALID_CMD) push 00406040
[   88.294721] nouveau :01:00.0: gr: DATA_ERROR 0005 

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

2016-01-17 Thread Dainius Masiliūnas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=346608

--- Comment #44 from Dainius Masiliūnas  ---
Yes, thanks. That's good to know and good to hear.
I'm not too concerned with a few specialised icons being mismatched; after all,
it's the common ones that you end up pressing the most.

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

[Touchpad-KCM] [Bug 357907] Crash eventual crash, often on load

2016-01-17 Thread Weng Xuetian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357907

--- Comment #9 from Weng Xuetian  ---
(In reply to Hrvoje Senjan from comment #8)
> The crash happens with plasma desktop master

Can you print out m_connection value with gdb? Can you make sure when it
crashes it run with newly installed instead of old one?

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


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

2016-01-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356035

--- Comment #3 from emp...@adslgr.com ---
Anyone can do something about this highly annoying bug? the whole panel and
it's icons are now *useless* as they never refresh/redraw.

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


[akregator] [Bug 358127] Incorrect Hungarian and Spanish feeds address

2016-01-17 Thread Laurent Montel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358127

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdep
   ||im/de8c3fd37945df8866f2edf3
   ||f85da719c2e8a9c6
 Resolution|--- |FIXED
   Version Fixed In||5.1.2
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Laurent Montel  ---
Git commit de8c3fd37945df8866f2edf3f85da719c2e8a9c6 by Montel Laurent.
Committed on 17/01/2016 at 20:02.
Pushed by mlaurent into branch 'Applications/15.12'.

Fix Bug 358127 - Incorrect Hungarian and Spanish feeds address

Thanks for  André Marcelo Alvarenga to give me info about theses defaults rss.

I commented Hungarian rss feed as there is not a good url.

FIXED-IN: 5.1.2

M  +3-2akregator/src/akregator_part.cpp

http://commits.kde.org/kdepim/de8c3fd37945df8866f2edf3f85da719c2e8a9c6

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

[krita] [Bug 352499] Crashed when I started using the brush

2016-01-17 Thread Markus L via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352499

--- Comment #9 from Markus L  ---
No crashing, when I test new 3.0 pre-alpha version. Windows 10 64 Pro , same
Trust tablet as no my earlier comments.

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


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

2016-01-17 Thread Jean-Baptiste Mardelle via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=346608

--- Comment #43 from Jean-Baptiste Mardelle  ---
I am currently not satisfied with the icon situation, here are some details:
Due to a Qt bug, setting an icon theme per application was not possible. This
is problematic when user has a light color theme on Desktop but wants to use
Kdenlive with a dark theme, because the icons were using not visible against a
dark background. So I used a hack, embedding all icons inside Kdenlive, and
allowing us to use our own icons.

In Qt 5.5, the problem was fixed and it is possible to define an icon theme per
application. But Qt 5.5. is still not widely used. When it becomes more
mainstream, I will change the way we handle icons to use the system icons, and
switching dark / light themes with color themes. When this will be implemented,
this should allow more flexibility with icon themes. However you need to be
aware that several icons we use are not in the oxygen theme, so you might end
up with a mix of breeze/oxygen, unless you contribute the missing icons in
oxygen theme...

Hope this clarifies a bit the icon situation.

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


[Touchpad-KCM] [Bug 357907] Crash eventual crash, often on load

2016-01-17 Thread Rajeesh K V via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357907

--- Comment #10 from Rajeesh K V  ---
Uninstalled xorg-x11-drv-libinput, running on synaptics driver; still no crash
for me. So, yes - it would be great to get some debug output.

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


[KBibTeX] [Bug 357883] Can't save .bib file to a remote file system mounted with SSHFS

2016-01-17 Thread Thomas Fischer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357883

--- Comment #2 from Thomas Fischer  ---
One more thing: I just noticed you are providing version 0.4.1. This version is
no longer supported. Please try at least 0.6 to see if the problem still
persists.

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


[KBibTeX] [Bug 357883] Can't save .bib file to a remote file system mounted with SSHFS

2016-01-17 Thread Thomas Fischer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357883

Thomas Fischer  changed:

   What|Removed |Added

  Component|Network/online search   |Loading/saving files

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


[kwin] [Bug 357032] KWin crashes after RubyMine sync window close

2016-01-17 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357032

Thomas Lübking  changed:

   What|Removed |Added

URL||https://git.reviewboard.kde
   ||.org/r/126787/
  Flags||ReviewRequest+

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

[krita] [Bug 358147] Crash when trying to open or create a file

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358147

zottg  changed:

   What|Removed |Added

   Severity|grave   |crash

--- Comment #3 from zottg  ---
Degraded severity. Read the release notes more. It's related to the Intel
graphics chip/disable OpenGL work around.

If I disable OpenGL in settings and restart, everything's OK.

But this makes animation playback really choppy and unreliable.

Keeping this open because Krita crashes. The release notes just said the screen
might go black.

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


[kexi] [Bug 346839] Switching off the visibility of query fields hides data in the last field

2016-01-17 Thread Jarosław Staniek via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=346839

--- Comment #23 from Jarosław Staniek  ---
Query Designer fixed for SQLite/MySQL/PostreSQL/Sybase. In review now.

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

[kwin] [Bug 358004] Kwin crash on closing matlab figures / closing matlab

2016-01-17 Thread Christian Butcher via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358004

--- Comment #2 from Christian Butcher  ---
Fixed by diff in comment 11 of the bug of which this is marked a duplicate -
see https://git.reviewboard.kde.org/r/126787

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


[krita] [Bug 358147] Crash when trying to open a file from 2.9.10 animation beta

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358147

zottg  changed:

   What|Removed |Added

  Component|Animation   |general

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


[kdeconnect] [Bug 357982] I confirm the bug.

2016-01-17 Thread woodsmoke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357982

--- Comment #3 from woodsmoke  ---
The Samsung SIII android phone had an update for KDE Connect as of 5:51 pm
Central Time U.S. 18 Jan 2016.

The phone and computer still did not pair.

The app in the Kubuntu Wiley computer was reinstalled.

The phone and computer still did not pair.

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


[digikam] [Bug 358149] New: Duplicate entry in JPEG2000 image extensions

2016-01-17 Thread André Marcelo Alvarenga via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358149

Bug ID: 358149
   Summary: Duplicate entry in JPEG2000 image extensions
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: alvare...@kde.org

String to translate in digikam.pot file:

#: app/utils/digikam_globals.cpp:130
msgid "JPEG2000 Image (*.jp2 *.j2k *.jpx *.jpx *.pgx)"
msgstr ""

See two *.jpx entries.

Reproducible: Always

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


[kmymoney4] [Bug 358129] Changing dividend transaction to reinvested dividend transaction after import of QIF/QFX file on online banking update.

2016-01-17 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358129

allan  changed:

   What|Removed |Added

 CC||agande...@gmail.com
 Ever confirmed|0   |1
   Version Fixed In||4.8.x?
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from allan  ---
> As suggested by AGA, I entered a manual test dividend transaction. I then 
> edited to a reinvested dividend > transaction, updating the required fields. 
> This worked as expected with no errors like the one mentioned 
> above. To close the test, I edited the transaction back to a dividend 
> transactions. This also completed with > no issues.

Oh, that is not what I was expecting.  I had just tested with 4.7.2, and, as I
recollect, manual entry resulted in the same problem.  I'll have to go back,
later, and check.  Meanwhile, testing with the development branch, and my patch
for this problem, all seems OK, so far.

After some more testing, I'll publish this patch and, hopefully, go via
Reviewboard to commit.

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


[krita] [Bug 358146] Window size and position are not saved

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358146

--- Comment #1 from zottg  ---
May be related to
https://bugs.kde.org/show_bug.cgi?id=335923
https://bugs.kde.org/show_bug.cgi?id=331819

Both were fixed but I don't know if they've been included in the 3.0 pre alpha.

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


[krita] [Bug 358146] New: Window size and position are not saved

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358146

Bug ID: 358146
   Summary: Window size and position are not saved
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: zottgram...@gmail.com

1. Launch Krita
2. Resize and reposition window
3. Close Krita
4. Open Krita
5. Previous size and position settings are not saved

Windows 10 64bit

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


[krita] [Bug 358147] Crash when trying to open or create a file

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358147

zottg  changed:

   What|Removed |Added

Summary|Crash when trying to open a |Crash when trying to open
   |file from 2.9.10 animation  |or create a file
   |beta|

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


[krita] [Bug 358147] Crash when trying to open or create a file

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358147

zottg  changed:

   What|Removed |Added

   Severity|crash   |grave

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


[krita] [Bug 358147] Crash when trying to open or create a file

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358147

--- Comment #1 from zottg  ---
It turns out that Krita will crash from just creating a file as well.

1. Open Krita
2. Create a new file
3. Crash

Right before the crash, a warning box appears and says, "You have an Intel(R)
HD Graphics".
Immediately after the program crashes.

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


[krita] [Bug 357460] Copy/pasted content shifts when a keyframe is created on a new layer

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357460

zottg  changed:

   What|Removed |Added

Version|2.9.10  |3.0 Alpha

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


[krita] [Bug 358148] New: Export/import settings/keymap or automatically do it when upgrading from previous versions

2016-01-17 Thread zottg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358148

Bug ID: 358148
   Summary: Export/import settings/keymap or automatically do it
when upgrading from previous versions
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: zottgram...@gmail.com

I upgraded from the 2.9.10 animation beta to 3.0 pre alpha. None of the keymaps
or settings were persisted/imported from the previous version.

The most ideal solution would be to prompt the user to import the settings or
not.

Another solution would be to provide an import/export settings & keymap option
so the user can do so manually.

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


[akregator] [Bug 319815] embedded video not playable, must open article in new tab to play

2016-01-17 Thread André Marcelo Alvarenga via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=319815

André Marcelo Alvarenga  changed:

   What|Removed |Added

 CC||alvare...@kde.org

--- Comment #2 from André Marcelo Alvarenga  ---
Created attachment 96705
  --> https://bugs.kde.org/attachment.cgi?id=96705=edit
Screenshot

I can reproduce using Akregator 5.1.1 (See screenshot with error message box)

You can test using http://www.noticiasautomotivas.com.br/feed and any article
with "VÍDEO" in Title.

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

[ark] [Bug 211669] Add LZO support to Ark

2016-01-17 Thread David Hallas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=211669

David Hallas  changed:

   What|Removed |Added

 CC||da...@davidhallas.dk

--- Comment #8 from David Hallas  ---
I am currently working on adding support for this using lzop - I will post
patches to reviewboard when ready. Currently I only have listing done.

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


[plasmashell] [Bug 357926] Screen/elements blink when moving mouse is some area

2016-01-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357926

hkz85825...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from hkz85825...@gmail.com ---
Got fixed after upgrading Qt. So it's a bug of Qt, not KDE. Sorry for
interfering.

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


[kmail2] [Bug 353876] KMail crashes on start

2016-01-17 Thread Aitor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353876

Aitor  changed:

   What|Removed |Added

 CC||m...@aitorpazos.es

--- Comment #1 from Aitor  ---
I'm unable to start Kmail since a couple of versions with a similar crash on
Kleo::CryptoBackendFactory::scanForBackends

Running it in a clean environment works well, but I'm not willing to drop my
data.

Kmail: 5.1.1
Kleopatra: 2.2.0
Qt: 5.5.1
Distro: Archlinux
Kernel: 4.3.3.2 x86_64

Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1a79b94840 (LWP 16240))]

Thread 11 (Thread 0x7f1a781c7700 (LWP 16241)):
#0  0x7f1a91a8018d in poll () from /usr/lib/libc.so.6
#1  0x7f1a8bf93ae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f1a8bf95757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f1a798ed379 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f1a92381b8e in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f1a8b9694a4 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f1a91a8913d in clone () from /usr/lib/libc.so.6

Thread 10 (Thread 0x7f1a755e6700 (LWP 16242)):
#0  0x7f1a8b96f07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f1a8fc7048b in ?? () from /usr/lib/libQt5WebKit.so.5
#2  0x7f1a8fc704c9 in ?? () from /usr/lib/libQt5WebKit.so.5
#3  0x7f1a8b9694a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f1a91a8913d in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7f1a2e1d8700 (LWP 16243)):
#0  0x7f1a8b191270 in ?? () from /usr/lib/libglib-2.0.so.0
#1  0x7f1a8b14daa4 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#2  0x7f1a8b14df60 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7f1a8b14e0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f1a925b956b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7f1a9256057a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7f1a9237cbe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7f1a92381b8e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f1a8b9694a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f1a91a8913d in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7f1a27df7700 (LWP 16246)):
#0  0x7f1a8b96f07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f1a8f96f644 in ?? () from /usr/lib/libQt5WebKit.so.5
#2  0x7f1a8fca0101 in ?? () from /usr/lib/libQt5WebKit.so.5
#3  0x7f1a8b9694a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f1a91a8913d in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f1a275f6700 (LWP 16247)):
#0  0x7f1a8b96f07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f1a8f9706b3 in ?? () from /usr/lib/libQt5WebKit.so.5
#2  0x7f1a8fca0101 in ?? () from /usr/lib/libQt5WebKit.so.5
#3  0x7f1a8b9694a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f1a91a8913d in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f1a152d8700 (LWP 16248)):
#0  0x7f1a91a8018d in poll () from /usr/lib/libc.so.6
#1  0x7f1a8b14dfbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f1a8b14e0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f1a925b956b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f1a9256057a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f1a9237cbe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f1a92381b8e in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f1a8b9694a4 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f1a91a8913d in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f1a14ad7700 (LWP 16249)):
#0  0x7f1a8b192614 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0
#1  0x7f1a8b14df76 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f1a8b14e0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f1a925b956b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f1a9256057a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f1a9237cbe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f1a92381b8e in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f1a8b9694a4 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f1a91a8913d in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f1a0700 (LWP 16250)):
#0  0x7ffe363e3c8f in clock_gettime ()
#1  0x7f1a91a95d36 in clock_gettime () from /usr/lib/libc.so.6
#2  0x7f1a92432256 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f1a925b6fe9 in QTimerInfoList::updateCurrentTime() () from

[digikam] [Bug 358081] Tags Manager - selecting tags from tree-view do not focus tags title field in right sidebar

2016-01-17 Thread Maik Qualmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358081

--- Comment #2 from Maik Qualmann  ---
Git commit 130ff08145ab51cf157d45eede04c7f3e3e5a019 by Maik Qualmann.
Committed on 17/01/2016 at 08:43.
Pushed by mqualmann into branch 'master'.

fix TAlbum icon update

M  +0-1libs/album/albummanager.cpp

http://commits.kde.org/digikam/130ff08145ab51cf157d45eede04c7f3e3e5a019

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


[digikam] [Bug 358081] Tags Manager - selecting tags from tree-view do not focus tags title field in right sidebar

2016-01-17 Thread Maik Qualmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358081

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #3 from Maik Qualmann  ---
1) is resolved with the commit from Comment 2
2) is here also not to reproduce with digiKam-5.0.0-beta3

I think we can close this bug.

Maik

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


[marble] [Bug 358094] Regression; Scroll-zoom with touchpads broken in Marble v15.12

2016-01-17 Thread Dennis Nienhüser via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358094

Dennis Nienhüser  changed:

   What|Removed |Added

 CC||nienhue...@kde.org

--- Comment #1 from Dennis Nienhüser  ---
Can you please check if
https://quickgit.kde.org/?p=marble.git=commit=1b4da07 causes the problem?

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

[Akonadi] [Bug 325224] CalDav doesn't read server items

2016-01-17 Thread Moritz Ulmer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=325224

Moritz Ulmer  changed:

   What|Removed |Added

 CC|moritz.ul...@posteo.de  |

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


[kphotoalbum] [Bug 342457] Documentation improvements

2016-01-17 Thread Tobias Leupold via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=342457
Bug 342457 depends on bug 342253, which changed state.

Bug 342253 Summary: How to enable face recognition is hard to detect in 
settings dialogue
https://bugs.kde.org/show_bug.cgi?id=342253

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

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


[kphotoalbum] [Bug 342253] How to enable face recognition is hard to detect in settings dialogue

2016-01-17 Thread Tobias Leupold via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=342253

Tobias Leupold  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #7 from Tobias Leupold  ---
Well, nobody ever complained again about this, so I'll close it now ;-)

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


[kphotoalbum] [Bug 210330] adding database folder under "My Pictures" is signaled falsely as read-only

2016-01-17 Thread Tobias Leupold via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=210330

Tobias Leupold  changed:

   What|Removed |Added

 CC||tobias.leup...@web.de

--- Comment #1 from Tobias Leupold  ---
Does this problem still exist? And are you sure you used KPA on MS Windows? ;-)

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


[kphotoalbum] [Bug 220446] Select images graphically by GeoPosition

2016-01-17 Thread Tobias Leupold via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=220446

Tobias Leupold  changed:

   What|Removed |Added

 CC||tobias.leup...@web.de
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Tobias Leupold  ---
This functionality has been added in the meantime and will be released with KPA
4.7.

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


[plasma-nm] [Bug 357938] offer to create openconnect-VPN without required packages installed

2016-01-17 Thread Jan Grulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357938

--- Comment #11 from Jan Grulich  ---
I mean the problem with missing notification is solved in newer versions, but
you should still be able to create all VPN connections even with missing NM
plugins, which I don't consider as a problem.

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


[marble] [Bug 358094] Regression; Scroll-zoom with touchpads broken in Marble v15.12

2016-01-17 Thread Stefan Bauer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358094

--- Comment #2 from Stefan Bauer  ---
(In reply to Dennis Nienhüser from comment #1)
> Can you please check if
> https://quickgit.kde.org/?p=marble.git=commit=1b4da07 causes the problem?

You nailed it, this commit introduces the problem.

While testing I identified some prerequisites that have to be met in order to
trigger the issue:
- Touchpad is used (X.org synaptics in my case). Using a mouse with indexed
scroll wheel does not trigger the problem.
- Only certain maps trigger the issue: OpenCycleMap, Plain Map, Satellite View
and some more work, OSM Hike Map and OpenStreetMap don't. I guess this is
related to whether these maps are "discrete" or not.

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

  1   2   3   >