[digikam] [Bug 367844] In Face Detection Options, if you delect one album, in fact it scan all albums

2016-08-26 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367844

--- Comment #1 from Christian  ---
Sorry, error in the description : Read "If you select one album, in fact it
scans all albums"

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


[digikam] [Bug 367844] New: In Face Detection Options, if you delect one album, in fact it scan all albums

2016-08-26 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367844

Bug ID: 367844
   Summary: In Face Detection Options, if you delect one album, in
fact it scan all albums
   Product: digikam
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Management
  Assignee: digikam-de...@kde.org
  Reporter: christian.carro...@wanadoo.fr

Version 5.1.0 digikam on PC/Windows-64bits, In Face Detection Options, if you
delect one album, in fact it scan all albums

Reproducible: Always

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


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

2016-07-25 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361236

Christian  changed:

   What|Removed |Added

 CC|kr...@free.fr   |

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


[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

2016-07-22 Thread Volker Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362958

--- Comment #33 from Volker Christian  ---
(In reply to Fabian Vogt from comment #32)
> Created attachment 100243 [details]
> Test mail with invitation
> 
> Here is a multipart/alternative mail that fails to display properly.

The patch in comment 24 handles this mail correctly.

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


[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

2016-07-22 Thread Volker Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362958

--- Comment #31 from Volker Christian  ---
(In reply to Sandro Knauß from comment #29)
> @craig: I cant reproduce this problem with korganizer (5.2.2) as sender of
> the mail.
> I see correctly the invitation inside kmail.
> Keep in mind, that you need kdepim-addons installed for displaying the
> invitations. 
> So please upload a wrongly displayed email, so that I am able to reproduce
> the issue.
> 
> Content-Type: multipart/mixed; boundary="nextPart1"
> MIME-Version: 1.0
> 
>  --nextPart1
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
> 
> Some text describing the calendar
> 
> --nextPart1
> Content-Type: text/calendar; charset="utf-8"; method="request";
> name="cal.ics"
> Content-Disposition: attachment
> Content-Transfer-Encoding: quoted-printable
> 
> BEGIN:VCALENDAR
> [...]
> END:VCALENDAR
> 
> --nextPart1--

That you can not reproduce the problem is due do that fact that the
content-type of this mail is multipart/mixed which is handled correctly in
messagelib. The content-type which is not handled correctly is
multipart/alternative.

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

[kwin] [Bug 365896] New: Kwin crashes when wallet pops-up

2016-07-20 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365896

Bug ID: 365896
   Summary: Kwin crashes when wallet pops-up
   Product: kwin
   Version: 5.7.1
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kr...@free.fr

Application: kwin_x11 (5.7.1)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.7.0-desktop-0.rc7.6.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
launching chromium for the first time in the session, a previous tab needs to
restore login informations, so wallet window appears, and Kwin crashes.

It seems that having firefox already running before launching chromium is
needed.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f76898cf700 (LWP 15623)):
#0  0x7f76aa26bd73 in select () at /lib64/libc.so.6
#1  0x7f76a80f7e5f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7f76a80f977b in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7f76a80f9c42 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f76a80a7c9a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f76a7ee137c in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f76a3118805 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f76a7ee5fb9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f76aa53a66d in start_thread () at /lib64/libpthread.so.0
#9  0x7f76aa275d8d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f75eb62e700 (LWP 15020)):
#0  0x7f76aa53fc4f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f75ef3269d3 in thread_function () at /usr/lib64/dri/swrast_dri.so
#2  0x7f75ef326857 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so
#3  0x7f76aa53a66d in start_thread () at /lib64/libpthread.so.0
#4  0x7f76aa275d8d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f75ebe2f700 (LWP 15019)):
#0  0x7f76aa53fc4f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f75ef3269d3 in thread_function () at /usr/lib64/dri/swrast_dri.so
#2  0x7f75ef326857 in impl_thrd_routine () at /usr/lib64/dri/swrast_dri.so
#3  0x7f76aa53a66d in start_thread () at /lib64/libpthread.so.0
#4  0x7f76aa275d8d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f76890c6700 (LWP 14930)):
#0  0x7f76aa53fc4f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f76a728a234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f76a728a279 in  () at /lib64/libQt5Script.so.5
#3  0x7f76aa53a66d in start_thread () at /lib64/libpthread.so.0
#4  0x7f76aa275d8d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f768a930700 (LWP 14928)):
#0  0x7f76aa26bd73 in select () at /lib64/libc.so.6
#1  0x7f76a80f7e5f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7f76a80f977b in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7f76a80f9c42 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f76a80a7c9a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f76a7ee137c in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f76a3118805 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f76a7ee5fb9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f76aa53a66d in start_thread () at /lib64/libpthread.so.0
#9  0x7f76aa275d8d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f7690f0f700 (LWP 14918)):
#0  0x7f76aa26bd73 in select () at /lib64/libc.so.6
#1  0x7f76a80f7e5f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7f76a80f977b in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7f76a80f9c42 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f76a80a7c9a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f76a7ee137c in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f76d615 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f76a7ee5fb9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f76aa53a66d in start_thread () at /lib64/libpthread.so.0
#9  0x7f76aa275d8d in clone () at /lib64

[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

2016-07-16 Thread Volker Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362958

--- Comment #25 from Volker Christian  ---
(In reply to Fabian Vogt from comment #23)
> I investigated a bit more:
> When the mail contains only the text/calendar node, it's shown as expected.
> The issue is that in a multipart/alternative handling, it only cares about
> text/plain and text/html.
> If one of those is present, it's displayed and everything else is ignored.
> I have no idea how a proper fix looks like, for now I changed the "break;"
> in messageviewer/src/viewer/objecttreeparser.cpp:352 to a "continue;", to
> always display all mail nodes, including text/calendar. This works well for
> me as I'm mostly working with plaintext mails and calendar invitations
> anyway.

I found a more proper fix directly in the multipart/alternative handling. This
is sure not the philosopher's stone. Nevertheless, it works for me also for
html-mails. The patch is in comment 24. Be aware, that the patch is not well
formated - it is only for testing.

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


[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

2016-07-16 Thread Volker Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362958

--- Comment #24 from Volker Christian  ---
Created attachment 100130
  --> https://bugs.kde.org/attachment.cgi?id=100130&action=edit
Fix Multipart Handling

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


[amarok] [Bug 365320] after i enable scripts, amarok won't open at all!! :(

2016-07-10 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365320

--- Comment #1 from christian  ---
I am using KaOs as my default os

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


[amarok] [Bug 365320] New: after i enable scripts, amarok won't open at all!! :(

2016-07-10 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365320

Bug ID: 365320
   Summary: after i enable scripts, amarok won't open at all!! :(
   Product: amarok
   Version: kf5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: cpboonzaa...@gmail.com

Amarok crash and won't open after I had enabled scripts

Reproducible: Always

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


[kstars] [Bug 365207] Hours angle negative

2016-07-07 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365207

--- Comment #1 from christian  ---
Created attachment 99930
  --> https://bugs.kde.org/attachment.cgi?id=99930&action=edit
the HA of polaris is negative

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


[kstars] [Bug 365207] New: Hours angle negative

2016-07-07 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365207

Bug ID: 365207
   Summary: Hours angle negative
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

hi,

when the hour angle is more 12h her value is negative.



Reproducible: Always

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


[kstars] [Bug 365129] world map very small

2016-07-05 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365129

--- Comment #1 from christian  ---
Created attachment 99873
  --> https://bugs.kde.org/attachment.cgi?id=99873&action=edit
screenshot

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


[kstars] [Bug 365129] New: world map very small

2016-07-05 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365129

Bug ID: 365129
   Summary: world map very small
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

all is in the screenshot. 

that's since the last (or precedent) update.

Thank you

Reproducible: Always

Steps to Reproduce:
1. click on "geographic emplacement "
2. 
3.

Actual Results:  
a world map very (very) small

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


[kstars] [Bug 364983] loose FOV since last update

2016-07-05 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364983

--- Comment #3 from christian  ---
Hi Jasem,

since the last update, the FOVs are back... A strange behavior.

I think you can close this no bug ;-)

thank you very much

Christian

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


[kstars] [Bug 365022] difference between transit time and wut information

2016-07-03 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365022

--- Comment #1 from christian  ---
Hi,

more, the information about the rise, transit and set time when you do a right
click on the star, differ between object information and the wut. 

And, if possible, display the star information (right click)  in this order : 
rise / transit / set.

Thanks you.

Regards
Christian

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


[kstars] [Bug 365019] improve display locale time

2016-07-03 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365019

--- Comment #3 from christian  ---
improve in the sense of the readable of the local time. When you set time (at
startup, this isn't display! that would be good is the time appears at start
up), this one is displaying at top right with the selected object and the
selected object is above the time. I have attached a screenshot for you see
what i mean.

Thank Jasem.

Christian

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


[kstars] [Bug 365022] New: difference between transit time and wut information

2016-07-02 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365022

Bug ID: 365022
   Summary: difference between transit time and wut information
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

Created attachment 99814
  --> https://bugs.kde.org/attachment.cgi?id=99814&action=edit
screenshot

Hi,

In the WUT tool, the transit and the set time of the object differs of the
object detail. 

Thank you.

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


[kstars] [Bug 365019] improve display locale time

2016-07-02 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365019

--- Comment #1 from christian  ---
Created attachment 99812
  --> https://bugs.kde.org/attachment.cgi?id=99812&action=edit
screenshot

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


[kstars] [Bug 365019] New: improve display locale time

2016-07-02 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365019

Bug ID: 365019
   Summary: improve display locale time
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

Hi, 

is it possible to improve the display of the local time ? 

Thank
Christian

Reproducible: Always

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


[kstars] [Bug 364983] loose FOV since last update

2016-07-02 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364983

--- Comment #2 from christian  ---
Hi Jasem,

thank you for you quick answer. 

There are only my own fov definitions and ekos profile that have disappeared.
That isn't very critic and may be the consequently an other update 

Thank you.

Christian

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


[kstars] [Bug 364983] New: loose FOV since last update

2016-07-01 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364983

Bug ID: 364983
   Summary: loose FOV since last update
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

After the update today (1 july 2016) with a apt-get upgrade the kstars-bleeding
and kstars-bleeding-data and they FOV and the ekos profile have disappeared.

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


[kdesu] [Bug 364898] plasma5 unable to launch kdesu and getting stuck with msg: "KDEInit could not launch '/usr/lib64/libexec/kf5/kdesu'"

2016-06-29 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364898

Christian  changed:

   What|Removed |Added

Summary|kdesu not launching app and |plasma5 unable to launch
   |getting stuck with msg: |kdesu and getting stuck
   |"KDEInit could not launch   |with msg: "KDEInit could
   |'/usr/lib64/libexec/kf5/kde |not launch
   |su'"|'/usr/lib64/libexec/kf5/kde
   ||su'"

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


[kdesu] [Bug 364898] kdesu not launching app and getting stuck with msg: "KDEInit could not launch '/usr/lib64/libexec/kf5/kdesu'"

2016-06-29 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364898

Christian  changed:

   What|Removed |Added

 CC||christian_bur...@yahoo.com

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


[kdesu] [Bug 364898] kdesu not launching app and getting stuck with msg: "KDEInit could not launch '/usr/lib64/libexec/kf5/kdesu'"

2016-06-29 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364898

Christian  changed:

   What|Removed |Added

Summary|plasma5 unable to launch|kdesu not launching app and
   |kdesu and getting stuck |getting stuck with msg:
   |with msg: "KDEInit could|"KDEInit could not launch
   |not launch  |'/usr/lib64/libexec/kf5/kde
   |'/usr/lib64/libexec/kf5/kde |su'"
   |su'"|
  Component|general |kdesu
   Keywords||reproducible

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


[kdesu] [Bug 364898] plasma5 unable to launch kdesu and getting stuck with msg: "KDEInit could not launch '/usr/lib64/libexec/kf5/kdesu'"

2016-06-29 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364898

Christian  changed:

   What|Removed |Added

Summary|plasma5 not able to launch  |plasma5 unable to launch
   |kdesu and getting stuck |kdesu and getting stuck
   |with msg: "KDEInit could|with msg: "KDEInit could
   |not launch  |not launch
   |'/usr/lib64/libexec/kf5/kde |'/usr/lib64/libexec/kf5/kde
   |su'"|su'"

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


[kdesu] [Bug 364898] plasma5 not able to launch kdesu and getting stuck with msg: "KDEInit could not launch '/usr/lib64/libexec/kf5/kdesu'"

2016-06-29 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364898

Christian  changed:

   What|Removed |Added

Summary|kdesu not launching app and |plasma5 not able to launch
   |getting stuck with msg: |kdesu and getting stuck
   |"KDEInit could not launch   |with msg: "KDEInit could
   |'/usr/lib64/libexec/kf5/kde |not launch
   |su'"|'/usr/lib64/libexec/kf5/kde
   ||su'"
  Component|kdesu   |general

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


[kdesu] [Bug 364898] New: kdesu not launching app and getting stuck with msg: "KDEInit could not launch '/usr/lib64/libexec/kf5/kdesu'"

2016-06-29 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364898

Bug ID: 364898
   Summary: kdesu not launching app and getting stuck with msg:
"KDEInit could not launch
'/usr/lib64/libexec/kf5/kdesu'"
   Product: kdesu
   Version: 1.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: kdesu
  Assignee: kdesu-bugs-n...@kde.org
  Reporter: christian_bur...@yahoo.com

There's a related bug opened for suse which shows this isn't an issue related
to the distro:
https://bugzilla.opensuse.org/show_bug.cgi?id=957470 

I'm getting this message when trying to lauch konsole as root:
KDEInit could not launch '/usr/lib64/libexec/kf5/kdesu'
~ $ which kdesu
/usr/bin/kdesu
~ $ ls -latrhs /usr/bin/kdesu
52K -rwxr-xr-x 1 root root 52K Jun 27 08:52 /usr/bin/kdesu
~ $ kdesu --version
Qt: 4.8.7
KDE Development Platform: 4.14.21
KDE su: 1.0


Reproducible: Always

Steps to Reproduce:
1. edit launch parameters from plasma5 to launch konsole as a different user:
root.
2. launch konsole.
3. the error message will appear in the screen: 
"KDEInit could not launch '/usr/lib64/libexec/kf5/kdesu'".

Actual Results:  
No error messages other than the one mentioned above:
no crashes seen in 'dmesg' output or logged messages in '~.xsession-errors'
either, no clear way to debug the issue.

Expected Results:  
The launcher should work as when it's invoked via command line.

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


[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

2016-06-23 Thread Volker Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362958

Volker Christian  changed:

   What|Removed |Added

 CC||volker.christian@fh-hagenbe
   ||rg.at

--- Comment #19 from Volker Christian  ---
Any news about this bug! It is a showstopper for me using kdepim 16.04 as I
need this feature urgently!

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


[kstars] [Bug 363190] bad date format in observer planner

2016-06-22 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363190

--- Comment #2 from christian  ---
this behavior is reproductible with all language

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


[kstars] [Bug 363190] bad date format in observer planner

2016-06-22 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363190

--- Comment #1 from christian  ---
Created attachment 99661
  --> https://bugs.kde.org/attachment.cgi?id=99661&action=edit
capture of observation planner

watch the date format at right of the location

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


[kstars] [Bug 364644] Strange display with specific zoom factor on sagitarius

2016-06-22 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364644

--- Comment #1 from christian  ---
Created attachment 99660
  --> https://bugs.kde.org/attachment.cgi?id=99660&action=edit
capture on sky near sagitarius

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


[kstars] [Bug 364644] New: Strange display with specific zoom factor on sagitarius

2016-06-22 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364644

Bug ID: 364644
   Summary: Strange display with specific zoom factor on
sagitarius
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

with a specific zoom factor, the display show a strange picture like more small
squares. Move the sky is very slow.

When i change zoom factor, this picture disasppear.

It's near to the sagitarius.

Reproducible: Always

Steps to Reproduce:
1. move to near sagitarius
2. use zoom factor to CDV approximatif : 6.4 degrés
3.

Actual Results:  
display strange square and move the sky is very slow

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

[dolphin] [Bug 364540] New: Dolphin-15.12.3-r1

2016-06-20 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364540

Bug ID: 364540
   Summary: Dolphin-15.12.3-r1
   Product: dolphin
   Version: 15.12.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: gen...@moin.fi

Application: dolphin (15.12.3)
 (Compiled from sources)
Qt Version: 5.5.1
Frameworks Version: 5.22.0
Operating System: Linux 4.4.6-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
I had moved files by drag and drop to a sibling folder. When the move was
finished, I clicked on the parent folder, and dolphin crashed.

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

Thread 3 (Thread 0x7f9b30436700 (LWP 27546)):
#0  0x7f9b45f25c8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9b3a36db12 in poll (__timeout=-1, __nfds=1, __fds=0x7f9b30435c80)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0xf98f40, cond=cond@entry=0xf98f80,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7f9b3a36f8d7 in xcb_wait_for_event (c=0xf98f40) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7f9b31943c29 in QXcbEventReader::run (this=0xf97b80) at
qxcbconnection.cpp:1229
#5  0x7f9b40b6a812 in QThreadPrivate::start (arg=0xf97b80) at
thread/qthread_unix.cpp:331
#6  0x7f9b3d0365c6 in start_thread (arg=0x7f9b30436700) at
pthread_create.c:334
#7  0x7f9b45f2f0cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f9b216df700 (LWP 27548)):
#0  0x7f9b45f25c8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9b3aeafdbc in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f9b1c003020, timeout=, context=0x7f9b1c000990) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f9b1c000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3835
#3  0x7f9b3aeafeec in g_main_context_iteration (context=0x7f9b1c000990,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3901
#4  0x7f9b40d6144b in QEventDispatcherGlib::processEvents
(this=0x7f9b1c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f9b40d11fea in QEventLoop::exec (this=this@entry=0x7f9b216ded80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f9b40b66076 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f9b40b6a812 in QThreadPrivate::start (arg=0x13c7fd0) at
thread/qthread_unix.cpp:331
#8  0x7f9b3d0365c6 in start_thread (arg=0x7f9b216df700) at
pthread_create.c:334
#9  0x7f9b45f2f0cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f9b464e4840 (LWP 27545)):
[KCrash Handler]
#6  QCoreApplication::notifyInternal (this=0x7ffcc6d269a0, receiver=0x0,
event=event@entry=0x7ffcc6d26620) at kernel/qcoreapplication.cpp:963
#7  0x7f9b40d60a12 in QCoreApplication::sendEvent (event=0x7ffcc6d26620,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#8  QTimerInfoList::activateTimers (this=0xfd0e30) at
kernel/qtimerinfo_unix.cpp:637
#9  0x7f9b40d60fc1 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:177
#10 0x7f9b3aeafbae in g_main_dispatch (context=0x7f9b280016f0) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3154
#11 g_main_context_dispatch (context=context@entry=0x7f9b280016f0) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3769
#12 0x7f9b3aeafe25 in g_main_context_iterate
(context=context@entry=0x7f9b280016f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3840
#13 0x7f9b3aeafeec in g_main_context_iteration (context=0x7f9b280016f0,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3901
#14 0x7f9b40d6141f in QEventDispatcherGlib::processEvents (this=0xff33f0,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#15 0x7f9b40d11fea in QEventLoop::exec (this=this@entry=0x7ffcc6d26870,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#16 0x7f9b40d1947c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#17 0x7f9b412440fc in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1527
#18 0x7f9b41773205 in QApplica

[kstars] [Bug 363190] New: bad date format in observer planner

2016-05-17 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363190

Bug ID: 363190
   Summary: bad date format in observer planner
   Product: kstars
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

The month of the date shown in the observation planner, at right to location is
incorrect. 

Reproducible: Always

Steps to Reproduce:
1.open observation planner window
2.
3.

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


[kstars] [Bug 362905] New: Crash what's interesting

2016-05-10 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362905

Bug ID: 362905
   Summary: Crash what's interesting
   Product: kstars
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

Application: kstars (2.6.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: nothing special. only firefox
and dolphin run. I'm on ubuntu 16.04

on the screen of "what's interesting" and after click ok, the application crash
!!!

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7ff088f43700 (LWP 7855)):
#0  0x7ff09843ee8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff092a13c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7ff092a158d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7ff08b295629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7ff0993a784e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff09acf06fa in start_thread (arg=0x7ff088f43700) at
pthread_create.c:333
#6  0x7ff09844ab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7ff08b64e8c0 (LWP 7854)):
[KCrash Handler]
#6  0x007bef81 in WIEquipSettings::setAperture (this=0x1ddd8ef0) at
/build/kstars-bleeding-eGyhPQ/kstars-bleeding-16.04+r5727.253~ubuntu16.04.1/kstars/tools/whatsinteresting/wiequipsettings.cpp:158
#7  0x004981b5 in KStars::slotShowWIView (this=0x2a84c90,
status=) at
/build/kstars-bleeding-eGyhPQ/kstars-bleeding-16.04+r5727.253~ubuntu16.04.1/kstars/kstarsactions.cpp:450
#8  0x00499ae5 in KStars::slotShowWIView (this=,
status=) at
/build/kstars-bleeding-eGyhPQ/kstars-bleeding-16.04+r5727.253~ubuntu16.04.1/kstars/kstarsactions.cpp:447
#9  0x0059a128 in KStars::qt_static_metacall (_o=,
_id=, _a=0x7fffe5270770, _c=) at
/build/kstars-bleeding-eGyhPQ/kstars-bleeding-16.04+r5727.253~ubuntu16.04.1/obj-x86_64-linux-gnu/kstars/moc_kstars.cpp:607
#10 0x7ff0995b6fca in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7ff09a55d7fe in QDialog::finished(int) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7ff09a55df78 in QDialog::done(int) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7ff0995b6e4f in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7ff09a48d9f0 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7ff0995b6fca in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7ff09a6fe1b2 in QAbstractButton::clicked(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7ff09a460f04 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7ff09a462519 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7ff09a462694 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7ff09a3a6f88 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7ff09a36405c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7ff09a369c19 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7ff09958862b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7ff09a368b32 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7ff09a3c157b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x7ff09a3c3b3b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x7ff09a36405c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x7ff09a369516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x7ff09958862b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7ff099db3521 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#31 0x7ff099db51e5 in
QGuiApplicationPr

[kate] [Bug 354482] scrolling quickly with the mouse wheel jumps and can even scroll backwards

2016-04-26 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354482

Christian  changed:

   What|Removed |Added

 CC||christian.fr...@gmail.com

--- Comment #7 from Christian  ---
I'm observing a similar behaviour. I have to mention that I'm running Ubuntu in
VirtualBox. However my problem does not appear in any other application like
for example Firefox.

Scrolling with the mouse wheel is very laggy/jumpy and only works at all if the
mouse is not moved at all. No such problem can be observed when using the
touchpad.

Same problem in KWrite by the way and similar but less severe also in gedit but
not at all (everything 100% smooth, no matter how hard you shake the mouse) in
Firefox.

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


[kstars] [Bug 361201] New: Kstars se plante en lancant l'outil "Elévation selon l'heure'

2016-03-30 Thread christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361201

Bug ID: 361201
   Summary: Kstars se plante en lancant l'outil "Elévation selon
l'heure'
   Product: kstars
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

Application: kstars (2.5.0)

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

-- Information about the crash:
plantage immédiat dès appel de l'outil Elévation selon l'heure

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f511e248700 (LWP 3935)):
#0  0x7f512ef7588d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f512989cbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f512989e74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f5121006a39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7f512fe942be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f51318246aa in start_thread (arg=0x7f511e248700) at
pthread_create.c:333
#6  0x7f512ef80e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f5121363800 (LWP 3934)):
[KCrash Handler]
#6  0x0055a05c in GeoLocation::UTtoLT (this=0x10044, ut=...) at
../../kstars/auxiliary/geolocation.cpp:187
#7  0x007d4b7f in AVTPlotWidget::paintEvent (this=0x1cb65450,
e=) at ../../kstars/tools/avtplotwidget.cpp:207
#8  0x7f5130ee5188 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f5130fdf76e in QFrame::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7f5132cd0c8e in KPlotWidget::event (this=0x1cb65450,
e=0x7ffe0caf24a0) at ../../src/kplotwidget.cpp:430
#11 0x7f5130ea2b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f5130ea8230 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f5130073f1b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f5130ede689 in QWidgetPrivate::sendPaintEvent(QRegion const&) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f5130edecd1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7f5130edf95c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7f5130edf849 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f5130ede841 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f5130edf95c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f5130edf849 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f5130ede841 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f5130eafbc2 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7f5130eb0692 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7f5130efe7eb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7f5130ea2b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x7f5130ea8230 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x7f5130073f1b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f51308f8336 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#29 0x7f51308f907d 

[frameworks-kactivities] [Bug 359244] Activities: When I stop my "Music" activity, I want the music player to stop playing music

2016-02-23 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359244

--- Comment #8 from Christian  ---
Great, thanks. Would be great if these hints could be added to the
documentation. I tried to find the "official" documentation for Activities - is
this it?
https://docs.kde.org/stable5/en/kde-workspace/plasma-desktop/zooming-user-interface.html
It hardly explains anything...

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


[frameworks-kactivities] [Bug 359244] Activities: When I stop my "Music" activity, I want the music player to stop playing music

2016-02-22 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359244

--- Comment #6 from Christian  ---
Thank you Ivan! Wow that's a useful script. It would be nice if the properties
window of the program shortcuts would include a setting for that. But good to
know that it's possible to do this manually using a script.

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


[frameworks-kactivities] [Bug 359244] Activities: When I stop my "Music" activity, I want the music player to stop playing music

2016-02-11 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359244

--- Comment #4 from Christian  ---
Hej Ivan!  Thank you, very much appreciated!  I didn't know that the
applications also have to implement the activity framework - I thought it would
work with all windowed applications... Oh well, software is always more
complicated than it seems to the casual user!

Another question that occurred to me - but I'm guessing that this is also
impossible in general, is: When I associate an activity to a window, and
somehow I've closed the window. Can I then make it so that, when I restart the
application, it also restarts that activity? (At least for some activities.)
But I am imagining that this would also have to be implemented by the
application and wouldn't work in general, right?
Is it possible to modify the KDE menu shortcuts (I mean the things I click on
to start programs) so that clicking on it also starts a particular activity?

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


[frameworks-kactivities] [Bug 359244] Activities: When I stop my "Music" activity, I want the music player to stop playing music

2016-02-11 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359244

--- Comment #2 from Christian  ---
I used "gmusicbrowser". It shows as a minimized window in the taskbar, and
there is also a symbol in the status bar.

I'm wondering if this is a good place to suggest additional functionality in
the settings of the Activities.  For me, the following two configuration
options would make it more useful:

1. Option whether stopping an activity should close all the windows associated
with only this activity. (A bit like when you log out and all the windows
close, but for just that activity.)
2. Possibility to associate programs with activities - e.g., when I start the
"Music" activity, the music player window should be opened even if it is not
running.

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


[kwin] [Bug 359244] New: Activities: When I stop my "Music" activity, I want the music player to stop playing music

2016-02-10 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359244

Bug ID: 359244
   Summary: Activities: When I stop my "Music" activity, I want
the music player to stop playing music
   Product: kwin
   Version: 5.5.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: activities
  Assignee: kwin-bugs-n...@kde.org
  Reporter: gen...@moin.fi

Hi KDE - I'm new to activities, but I like the idea. I've defined some
activities now and put some windows to activities. It's neat that all the
windows of one "running" activity are hidden from view when I click on a window
that belongs to a different activity.
But the "stop" button on the activities doesn't work the way I expect it to.
Use case:
1. I select the "Music" activity and my music player is shown. I click on
"Play" so it plays some music.
2. Now I activate the "Email" activity and the email window is shown, I do
stuff there.
3. Suppose my phone rings. I want to stop the music. So I go to the Activities
manager and "stop" the "Music" activity (that shows as "Used a while ago").

Expected result: "Music" activity is stopped and music stops playing.
Actual result: "Music" activity is shown as stopped, but the music continues
playing. (The music player window is still in the task bar, too.)

Maybe I haven't completely understood activities. But what is the "stop" button
on the activity supposed to do, if it doesn't stop the programs that belong to
the activity (and to no other activity)?

Reproducible: Always

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


[dragonplayer] [Bug 357869] Crash after click on Open Disk

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

--- Comment #2 from Christian  ---
Dear Harald,

please be so kind and forward this bug to the libdvdnav developers. I don't see
dragon player out of any responsibility, since its using a library with bugs.
Thanks!

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


[dragonplayer] [Bug 357869] New: Crash after click on Open Disk

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

Bug ID: 357869
   Summary: Crash after click on Open Disk
   Product: dragonplayer
   Version: 2.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: christ...@fitzgerald-forberg.de
CC: myr...@kde.org

Application: dragon (2.0)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-37-generic x86_64
Distribution: Linux Mint 17.1 Rebecca

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

I opened a DVD with the player and clicked on 'Disc'.
DVD: Children's classic CS Lewis The Chronicles of Narnia - The Lion the Witch
and the Wardrobe
BBC Daily Mail

The crash can be reproduced every time.

-- Backtrace:
Application: Dragon Player (dragon), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4778ee07c0 (LWP 23482))]

Thread 4 (Thread 0x7f475feb4700 (LWP 23484)):
#0  0x7f4775af312d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4773900031 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f47738f183c in pa_mainloop_poll () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f47738f1ece in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f47738f1f80 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f47738fffe3 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f477015ef08 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
#7  0x7f4772c59182 in start_thread (arg=0x7f475feb4700) at
pthread_create.c:312
#8  0x7f4775b0047d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f475b308700 (LWP 23485)):
#0  __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7f474c000a60) at
pthread_mutex_unlock.c:57
#1  __GI___pthread_mutex_unlock (mutex=0x7f474c000a60) at
pthread_mutex_unlock.c:310
#2  0x7f4771f1f9b1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4771edde9d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f4771ede0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f477657f7be in QEventDispatcherGlib::processEvents
(this=0x7f474c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f47765510af in QEventLoop::processEvents
(this=this@entry=0x7f475b307de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f47765513a5 in QEventLoop::exec (this=this@entry=0x7f475b307de0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f477644dc5f in QThread::exec (this=this@entry=0xefbdb0) at
thread/qthread.cpp:537
#9  0x7f4776532823 in QInotifyFileSystemWatcherEngine::run (this=0xefbdb0)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f477645032f in QThreadPrivate::start (arg=0xefbdb0) at
thread/qthread_unix.cpp:349
#11 0x7f4772c59182 in start_thread (arg=0x7f475b308700) at
pthread_create.c:312
#12 0x7f4775b0047d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f475ab07700 (LWP 23486)):
[KCrash Handler]
#6  0x7f475a5f2601 in set_VTS_PTT (vm=0x7f47500030a0, vtsN=1, vts_ttn=1,
part=1) at src/vm/getset.c:69
#7  0x7f475a5f174d in vm_jump_title_part (vm=0x7f47500030a0,
title=title@entry=1, part=part@entry=1) at src/vm/vm.c:571
#8  0x7f475a5eba73 in dvdnav_part_play (this=0x7f47500026f0,
title=title@entry=1, part=part@entry=1) at src/navigation.c:238
#9  0x7f475a5ebaaa in dvdnav_title_play (this=,
title=title@entry=1) at src/navigation.c:172
#10 0x7f475a8002bb in CommonOpen (p_this=p_this@entry=0x7f47500010a8,
p_dvdnav=, b_readahead=b_readahead@entry=true) at
access/dvdnav.c:296
#11 0x7f475a800a3a in AccessDemuxOpen (p_this=0x7f47500010a8) at
access/dvdnav.c:395
#12 0x7f4764db0428 in module_load (obj=obj@entry=0x7f47500010a8,
m=m@entry=0xbdebb0, init=init@entry=0x7f4764db0380 ,
args=args@entry=0x7f475ab06ab0) at modules/modules.c:185
#13 0x7f4764db09de in vlc_module_load (obj=obj@entry=0x7f47500010a8,
capability=capability@entry=0x7f4764deed0f "access_demux", name=0x7f4750001143
"", strict=strict@entry=true, probe=probe@entry=0x7f4764db0380 )
at modules/modules.c:277
#14 0x7f4764db0eb4 in module_need (obj=obj@entry=0x7f47500010a8,
cap=cap@entry=0x7f4764deed0f "access_demux", name=,
strict=strict@entry=true) at modules/modules.c:366
#15 0x7f4764d6635f in demux_New (p_obj=p_obj@entry=0xfd08f8,
p_parent_input=p_parent_input@entry=0xfd08f8,
psz_access=psz_access@entry=0x7f475fd0 "dvd",
psz_demux=psz_demux@entry=0x7f475ff0 "any",
psz_location=psz_location@entry=0x7f475fd6 "/dev/sr0", s=s@entry=0x0,
out=0x7f4758e0, b_quick=b_quick@entry=fals

[krita] [Bug 357166] New: two finger zoom gesture stopped functioning, making convenient zooming impossible

2015-12-25 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357166

Bug ID: 357166
   Summary: two finger zoom gesture stopped functioning, making
convenient zooming impossible
   Product: krita
   Version: 2.9.10
  Platform: MS Windows
   URL: https://bugs.kde.org/show_bug.cgi?id=356959
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: christianbcla...@gmail.com

The two finger zoom capability was working until a day ago. I have attempted
restarts and have uninstalled and reinstalled Krita 2.9.10.
The touch screen is still functionable for tools and the two finger function
can pan the canvas sideways, up and down.

Reproducible: Always

Steps to Reproduce:
1.Open Canvas.
2.Try to zoom with gesture
3.

Actual Results:  
Does not zoom in or out of canvas

Expected Results:  
Zoom in and out of canvas to allow for finite movement

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


[konsole] [Bug 350834] Konsole chrash when exiting

2015-12-23 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=350834

Christian  changed:

   What|Removed |Added

 CC||alexandruc...@gmail.com

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


[konsole] [Bug 350834] Konsole chrash when exiting

2015-12-23 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=350834

--- Comment #1 from Christian  ---
Created attachment 96283
  --> https://bugs.kde.org/attachment.cgi?id=96283&action=edit
New crash information added by DrKonqi

konsole (15.08.3) using Qt 5.5.1

As always, I was typing "ctrl + d" and konsole gave me an error. Also,
sometimes it doesn't close giving me and 100% cpu.

-- Backtrace (Reduced):
#11 0x003ab4e872d7 in QCoreApplication::removePostedEvents(QObject*, int)
() from /lib64/libQt5Core.so.5
#12 0x003ab4eb29f2 in QObjectPrivate::~QObjectPrivate() () from
/lib64/libQt5Core.so.5
#13 0x003ab4eb2b19 in QObjectPrivate::~QObjectPrivate() () from
/lib64/libQt5Core.so.5
#14 0x003ab4ebb108 in QObject::~QObject() () from /lib64/libQt5Core.so.5
#15 0x7f0fa556bb69 in QXcbConnection::~QXcbConnection() () from
/lib64/libQt5XcbQpa.so.5

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


[kaffeine] [Bug 357093] New: Kaffeine crashes after Update Fedora 22 on 22nd December 2015

2015-12-23 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357093

Bug ID: 357093
   Summary: Kaffeine crashes after Update Fedora 22 on 22nd
December 2015
   Product: kaffeine
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: christophpfis...@gmail.com
  Reporter: christ...@hauser-pc.de

Application: kaffeine-xbu (1.2.2 1.2.6)
KDE Platform Version: 4.14.14
Qt Version: 4.8.6
Operating System: Linux 4.2.8-200.fc22.i686 i686
Distribution (Platform): Fedora RPMs

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

Fedora installed updates on 22nd of december, rebooted and issue was there.

The crash can be reproduced every time.

-- Backtrace:
Application: Kaffeine (kaffeine-xbu), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb77b67c0 (LWP 3612))]

Thread 4 (Thread 0xb646fb40 (LWP 3621)):
#0  0x in __kernel_vsyscall ()
#1  0x415c9216 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#2  0x4a2737e7 in metronom_sync_loop () at /lib/libxine.so.2
#3  0x415c4370 in start_thread () at /lib/libpthread.so.0
#4  0x414e82be in clone () at /lib/libc.so.6

Thread 3 (Thread 0xb5c67b40 (LWP 3622)):
#0  0x in __kernel_vsyscall ()
#1  0x414db0db in poll () at /lib/libc.so.6
#2  0x4cf439de in poll_func () at /lib/libpulse.so.0
#3  0x4cf3183b in pa_mainloop_poll () at /lib/libpulse.so.0
#4  0x4cf320b1 in pa_mainloop_iterate () at /lib/libpulse.so.0
#5  0x4cf32184 in pa_mainloop_run () at /lib/libpulse.so.0
#6  0x4cf4396c in thread () at /lib/libpulse.so.0
#7  0x4cee248d in internal_thread_func () at
/usr/lib/pulseaudio/libpulsecommon-6.0.so
#8  0x415c4370 in start_thread () at /lib/libpthread.so.0
#9  0x414e82be in clone () at /lib/libc.so.6

Thread 2 (Thread 0xb12ffb40 (LWP 3623)):
#0  0x in __kernel_vsyscall ()
#1  0x415c8e4c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x4a287908 in ao_loop () at /lib/libxine.so.2
#3  0x415c4370 in start_thread () at /lib/libpthread.so.0
#4  0x414e82be in clone () at /lib/libc.so.6

Thread 1 (Thread 0xb77b67c0 (LWP 3612)):
[KCrash Handler]
#7  0x in __kernel_vsyscall ()
#8  0x4141d796 in raise () at /lib/libc.so.6
#9  0x4141f027 in abort () at /lib/libc.so.6
#10 0x41416187 in __assert_fail_base () at /lib/libc.so.6
#11 0x4141620b in  () at /lib/libc.so.6
#12 0x in __x86.get_pc_thunk.ax () at /lib/libva-x11.so.1
#13 0x in va_DisplayContextGetDriverName () at /lib/libva-x11.so.1
#14 0x in vaInitialize () at /lib/libva.so.1
#15 0x in vaapi_init_internal () at
/usr/lib/xine/plugins/2.5/xineplug_vo_out_vaapi.so
#16 0x in vaapi_open_plugin () at
/usr/lib/xine/plugins/2.5/xineplug_vo_out_vaapi.so
#17 0x4a278d3a in _load_video_driver () at /lib/libxine.so.2
#18 0x4a27c29d in _x_load_video_output_plugin () at /lib/libxine.so.2
#19 0x4a27c2e5 in xine_open_video_driver () at /lib/libxine.so.2
#20 0x0804e339 in XineObject::init(unsigned long long) ()
#21 0x0804f306 in XineObject::readyRead() ()
#22 0x0804b248 in XineObject::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) [clone .part.0] ()
#23 0x4ac98bba in QMetaObject::activate(QObject*, QMetaObject const*, int,
void**) () at /lib/libQtCore.so.4
#24 0x4acf20d2 in QSocketNotifier::activated(int) () at /lib/libQtCore.so.4
#25 0x4aca3f6f in QSocketNotifier::event(QEvent*) () at /lib/libQtCore.so.4
#26 0x4ba936d4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at
/lib/libQtGui.so.4
#27 0x4ba9ab20 in QApplication::notify(QObject*, QEvent*) () at
/lib/libQtGui.so.4
#28 0x4c6a7062 in KApplication::notify(QObject*, QEvent*) () at
/lib/libkdeui.so.5
#29 0x4ac830d6 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at
/lib/libQtCore.so.4
#30 0x4acb81e3 in socketNotifierSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib/libQtCore.so.4
#31 0x41731d43 in g_main_context_dispatch () at /lib/libglib-2.0.so.0
#32 0x41732125 in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#33 0x417321f7 in g_main_context_iteration () at /lib/libglib-2.0.so.0
#34 0x4acb7af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#35 0x4bb50fbc in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib/libQtGui.so.4
#36 0x4ac81662 in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#37 0x4ac81a09 in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#38 0x4ac87fdb in QCoreApplication::exec() () at /lib/libQtCore.so.4
#39 0x4ba91a95 in QApplication::exec() () at /lib/libQtGui.so.4
#40 0x0804afce in main ()

Reported using DrKonqi

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


[kde] [Bug 356628] New: Dependences kontact and Plasma

2015-12-13 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356628

Bug ID: 356628
   Summary: Dependences kontact and Plasma
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: cp.pia...@gmail.com

Application: plasma-desktop (4.11.16)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.13-desktop-2.mga5 x86_64
Distribution: "Mageia 5"

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

I delete kontact with Rpmdrake.
I think a problem with dependences

-- Backtrace:
Application: Shell del desktop di Plasma (plasma-desktop), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1a2fd1d780 (LWP 2679))]

Thread 4 (Thread 0x7f1a06496700 (LWP 2681)):
#0  0x7f1a2e5b367f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1a20aed73a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQtScript.so.4
#2  0x7f1a20aed769 in  () at /lib64/libQtScript.so.4
#3  0x7f1a2e5ae5bd in start_thread () at /lib64/libpthread.so.0
#4  0x7f1a2d3275cd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f19810d2700 (LWP 2683)):
#0  0x7f1a2a444fe4 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f1a2a4014d0 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f1a2a401de3 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f1a2a401fbc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f1a2e96be3e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#5  0x7f1a2e93d931 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f1a2e93dc45 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#7  0x7f1a2e83b899 in QThread::exec() () at /lib64/libQtCore.so.4
#8  0x7f1a2e91f3d3 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#9  0x7f1a2e83dfff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#10 0x7f1a2e5ae5bd in start_thread () at /lib64/libpthread.so.0
#11 0x7f1a2d3275cd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f197bbd6700 (LWP 2685)):
#0  0x7f1a2e5b367f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1a2e83e4f4 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQtCore.so.4
#2  0x7f1a1fd41abc in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
() at /lib64/libthreadweaver.so.4
#3  0x7f1a1fd44623 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) () at /lib64/libthreadweaver.so.4
#4  0x7f1a1fd4329f in ThreadWeaver::Thread::run() () at
/lib64/libthreadweaver.so.4
#5  0x7f1a2e83dfff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#6  0x7f1a2e5ae5bd in start_thread () at /lib64/libpthread.so.0
#7  0x7f1a2d3275cd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f1a2fd1d780 (LWP 2679)):
[KCrash Handler]
#5  0x7f1a2e8390e6 in QReadWriteLock::~QReadWriteLock() () at
/lib64/libQtCore.so.4
#6  0x7f1a23484b6d in Plasma::QueryMatch::~QueryMatch() () at
/usr/lib64/libplasma.so.3
#7  0x7f1a23494af0 in
QList::removeAll(Plasma::QueryMatch const&) () at
/usr/lib64/libplasma.so.3
#8  0x7f1a23493708 in Plasma::RunnerContext::removeMatch(QString) () at
/usr/lib64/libplasma.so.3
#9  0x7f1980166674 in SolidRunner::refreshMatch(QString&) () at
/usr/lib64/kde4/krunner_solid.so
#10 0x7f1980166cf9 in SolidRunner::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/kde4/krunner_solid.so
#11 0x7f1a2e95288a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#12 0x7f198016856c in DeviceWrapper::dataUpdated(QString const&,
QHash) [clone .part.21] () at
/usr/lib64/kde4/krunner_solid.so
#13 0x7f1980169035 in DeviceWrapper::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/kde4/krunner_solid.so
#14 0x7f1a2e95288a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#15 0x7f1a234105d7 in Plasma::DataContainer::dataUpdated(QString const&,
QHash const&) () at /usr/lib64/libplasma.so.3
#16 0x7f1a23410f10 in Plasma::DataContainer::checkForUpdate() () at
/usr/lib64/libplasma.so.3
#17 0x7f1a23412e43 in Plasma::DataEngine::timerEvent(QTimerEvent*) () at
/usr/lib64/libplasma.so.3
#18 0x7f1a2e956c2b in QObject::event(QEvent*) () at /lib64/libQtCore.so.4
#19 0x7f1a2dab679c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#20 0x7f1a2dabce40 in QApplication::notify(QObject*, QEvent*) () at
/li