[k3b] [Bug 381460] no UTF-8 support in "folder is not empty dialogue" while readout of VCD

2017-06-29 Thread Herr Schmidt 
https://bugs.kde.org/show_bug.cgi?id=381460

--- Comment #4 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Dear Leslie,

unluckily I won't have VCDs around until next week and I can't test it
using DVDs as this requires transcode which is not in the sources / not
installable right now. I am really apologizing, but I never built
myself and it looks awfully complicated and time consuming - sorry!

But here is a translation:

Front Window

Title - "There are already files - K3b"
Main Part - "The folder is not empty, still continue?"
Files - "Persian/Arabic - مسالزاده (4,0 KiB)"
"Mutated Vowls - äöüß (4,0 KiB)"


Small Back Window

Title - "ReadOut Video-CD - K3b"
Main Part - "ReadOut Video-CD"
"Destination Folder"
"ReadOut to:"
"Settings"

I hope this helps - if you still need the english screenshot pleas tell
me, then I will send it to you as soon as I have a VCD around again next
week.

Kindly yours
Maria


Leslie Zhai:
> https://bugs.kde.org/show_bug.cgi?id=381460
> 
> --- Comment #3 from Leslie Zhai <lesliez...@llvm.org.cn> ---
> Hi Herr,
> 
>> unluckily even in Debian-Sid there is only k3b 2.0.3a-2+b2 available.
> 
> yes, only ArchLinux and Ubuntu packaged the latest k3b, do you know how to
> build by yourself? http://www.leetcode.cn/2016/08/k3b.html
> 
>> But I added a screenshot.
> 
> please kindly LANG=en_US.UTF-8 k3b to switch English UI, then re-attach the
> screenshot reproduce the issue, thanks!
> 
> Regards,
> Leslie Zhai

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

[k3b] [Bug 381460] no UTF-8 support in "folder is not empty dialogue" while readout of VCD

2017-06-26 Thread Herr Schmidt 
https://bugs.kde.org/show_bug.cgi?id=381460

--- Comment #2 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Hey Leslie,

unluckily even in Debian-Sid there is only k3b 2.0.3a-2+b2 available.
But I added a screenshot. The first entry is supposed to be "مسالزاده"
and the second entry is supposed to be "äöüß"

Thanks!
Maria


Leslie Zhai:
> https://bugs.kde.org/show_bug.cgi?id=381460
> 
> Leslie Zhai <lesliez...@llvm.org.cn> changed:
> 
>What|Removed |Added
> 
>  CC||lesliez...@llvm.org.cn
> 
> --- Comment #1 from Leslie Zhai <lesliez...@llvm.org.cn> ---
> Hi Herr,
> 
> Please try K3b Applications/17.07 https://github.com/KDE/k3b v2.0.x was not
> maintained any more, and please kindly attach some screenshots for me, thanks!
> 
> Regards,
> Leslie Zhai

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

[k3b] [Bug 381460] New: no UTF-8 support in "folder is not empty dialogue" while readout of VCD

2017-06-20 Thread Herr Schmidt 
https://bugs.kde.org/show_bug.cgi?id=381460

Bug ID: 381460
   Summary: no UTF-8 support in "folder is not empty dialogue"
while readout of VCD
   Product: k3b
   Version: 2.0.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: GUI/Usability
  Assignee: k...@kde.org
  Reporter: wettererschein...@bb-goettingen.de
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

When I start a readout of a VCD (VCD auslesen) and try to save it in a folder
which is not empty I am showed a dialogue containing the filenames inside that
folder. If these files contain either German Umlaute (äöü) or Persian/Arabic
characters, these are only shown as unreadable hieroglyphics.

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

[tellico] [Bug 380815] Improving file catalog import for video-files: Video-only option + folder structure detection + Cover/srt detection

2017-06-04 Thread Herr Schmidt 
https://bugs.kde.org/show_bug.cgi?id=380815

Herr Schmidt <wettererschein...@bb-goettingen.de> changed:

   What|Removed |Added

Summary|Improving file catalog  |Improving file catalog
   |import for video-files: |import for video-files:
   |Video-only option + folder  |Video-only option + folder
   |structure detection + Cover |structure detection +
   |detection   |Cover/srt detection

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

[tellico] [Bug 380815] New: Improving file catalog import for video-files: Video-only option + folder structure detection + Cover detection

2017-06-04 Thread Herr Schmidt 
https://bugs.kde.org/show_bug.cgi?id=380815

Bug ID: 380815
   Summary: Improving file catalog import for video-files:
Video-only option + folder structure detection + Cover
detection
   Product: tellico
   Version: 3.0.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ro...@periapsis.org
  Reporter: wettererschein...@bb-goettingen.de
  Target Milestone: ---

Dear People,

thanks for your great useful work!
I would like to humbly propose a possible improvement to the file catalog
import regarding folders containing a video-collection. I have put the
suggestions in the order of most important first:

* Adding an Video-only-Option: Only add videos (ignore other files)

* Detection of information in filenames or folder structure: If the names of
folders are set in certain way like
"collection/director/title-year/filename.iso" or "title-year-director.mp4" it
would be helpful to detect that information (or tell tellico to interpret them
in a certain way, like in amarok)

* Cover detection: Often the Covers are inside the same folder of the
video-file, so automatically integrating them in the collection when doing a
file catalog import would be really helpful!

* detection of subtitle-files in the same folder / with the same filename

Thanks alot!
Maria

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

[amarok] [Bug 375026] New: Session crashes after reactivation of locked screen

2017-01-13 Thread Herr Schmidt 
https://bugs.kde.org/show_bug.cgi?id=375026

Bug ID: 375026
   Summary: Session crashes after reactivation of locked screen
   Product: amarok
   Version: 2.8.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: wettererschein...@bb-goettingen.de
  Target Milestone: 2.9

Application: amarok (2.8.0)
KDE Platform Version: 4.14.26
Qt Version: 4.8.7
Operating System: Linux 4.8.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- Unusual behavior I noticed:

After I locked my screen and returned typing in my password instead of
unlocking I get to the login screen. After login and automatic start of Amarok
I get an error message:

Die Amarok-Datenbank berichtet die folgenden Fehler:
GREPME MySQLe query failed! (2000) mysql_embedded: Shutdown complete
 on init
In den meisten Fällen müssen diese Fehler behoben sein, bevor Amarok
vollständig funktioniert.

And after trying to close I get this bug dialogue.


Additionally I get the following segmentation fault:
korgac PID: 9713 Signal: Segmentation fault (11) Datum: 14.01.17 03:38:56

The crash can be reproduced sometimes.

-- Backtrace:
Application: Amarok (amarok), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9069e8a080 (LWP 9693))]

Thread 13 (Thread 0x7f9001035700 (LWP 10024)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f905ce6d739 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f905d184ccb in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f906568c464 in start_thread (arg=0x7f9001035700) at
pthread_create.c:333
#4  0x7f9066aea9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 12 (Thread 0x7f901a1bd700 (LWP )):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9065c7b61a in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f9065f80ec0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f9065c7b649 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f906568c464 in start_thread (arg=0x7f901a1bd700) at
pthread_create.c:333
#4  0x7f9066aea9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 11 (Thread 0x7f901bffe700 (LWP 9996)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f905d15395f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f905d1539b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f906568c464 in start_thread (arg=0x7f901bffe700) at
pthread_create.c:333
#4  0x7f9066aea9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 10 (Thread 0x7f9024ff8700 (LWP 9995)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f906719c316 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x55fb38775740) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=, mutex=0x55fb386d89e0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7f9062820b30 in ?? () from /usr/lib/libthreadweaver.so.4
#4  0x7f9062823393 in ?? () from /usr/lib/libthreadweaver.so.4
#5  0x7f90628233ac in ?? () from /usr/lib/libthreadweaver.so.4
#6  0x7f90628233ac in ?? () from /usr/lib/libthreadweaver.so.4
#7  0x7f9062821e8d in ThreadWeaver::Thread::run() () from
/usr/lib/libthreadweaver.so.4
#8  0x7f906719bdaa in QThreadPrivate::start (arg=0x7f900c082170) at
thread/qthread_unix.cpp:352
#9  0x7f906568c464 in start_thread (arg=0x7f9024ff8700) at
pthread_create.c:333
#10 0x7f9066aea9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 9 (Thread 0x7f90257f9700 (LWP 9994)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f906719c316 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x55fb39fd3260) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=,
mutex=mutex@entry=0x55fb39fd3240, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f9067198003 in QSemaphore::acquire (this=this@entry=0x55fb39fd2e20,
n=n@entry=1) at thread/qsemaphore.cpp:144
#4  0x7f90697a1e10 in Playlists::PlaylistFileLoaderJob::run
(this=0x55fb39fd2de0) at
./src/core-impl/playlists/types/file/PlaylistFileLoaderJob.cpp:92
#5  0x7f9062822670 in ?? () from /usr/lib/libthreadweaver.so.4
#6  0x7f9062822880 in

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

2016-11-18 Thread Herr Schmidt 
https://bugs.kde.org/show_bug.cgi?id=342763

Herr Schmidt <wettererschein...@bb-goettingen.de> changed:

   What|Removed |Added

 CC|wettererscheinung@bb-goetti |
   |ngen.de |

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

[kontact] [Bug 371277] Kontact, KOrganizer-Reminder-Module and Akonadi-ical-Ressource crashing after deleting "only this" task with subtasks and undo/redo them

2016-10-20 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371277

--- Comment #2 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 101658
  --> https://bugs.kde.org/attachment.cgi?id=101658=edit
korgac-20161020-130116.kcrash.txt

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

[kontact] [Bug 371277] Kontact, KOrganizer-Reminder-Module and Akonadi-ical-Ressource crashing after deleting "only this" task with subtasks and undo/redo them

2016-10-20 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371277

--- Comment #1 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 101657
  --> https://bugs.kde.org/attachment.cgi?id=101657=edit
akonadi_ical_resource-20161020-125848.kcrash.txt

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

[kontact] [Bug 371277] New: Kontact, KOrganizer-Reminder-Module and Akonadi-ical-Ressource crashing after deleting "only this" task with subtasks and undo/redo them

2016-10-20 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371277

Bug ID: 371277
   Summary: Kontact, KOrganizer-Reminder-Module and
Akonadi-ical-Ressource crashing after deleting "only
this" task with subtasks and undo/redo them
   Product: kontact
   Version: 5.2.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Application: kontact (5.2.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

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

Step 1: create toplevel task
Step 2: create sublevel 1 task under the toplevel task
Step 3+4: create 2 sublevel 2 tasks (2a, 2b) under sublevel 1 task
Step 5: delete sublevel 1 task and confirm "Delete only this" --> result is
only toplevel task shown
Step 6: Undo and Redo a few times --> crash (sometimes after first redo,
sometimes after a circle of a few undos and redos)

Also works with deleting toplevel task in the same way and following Step 6.

- Unusual behavior I noticed:
1) Step 5: deletes sublevel 1 AND all sublevel 2 although "Delete only this"
was selected
2) Bug 371242

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 0x7f79d542af00 (LWP 2683))]

Thread 33 (Thread 0x7f78e0dd9700 (LWP 2809)):
#0  g_mutex_unlock (mutex=0x7f78fc00c2f0) at ././glib/gthread-posix.c:1348
#1  0x7f79e552492e in g_main_context_acquire (context=0x7f78fc00c2f0) at
././glib/gmain.c:3283
#2  0x7f79e5525885 in g_main_context_iterate
(context=context@entry=0x7f78fc00c2f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3879
#3  0x7f79e5525aec in g_main_context_iteration (context=0x7f78fc00c2f0,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f79ec92551b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f79ec8cd19a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f79ec6f2e53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f79ec6f7d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f79e5d4d464 in start_thread (arg=0x7f78e0dd9700) at
pthread_create.c:333
#9  0x7f79ebdfc97f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 32 (Thread 0x7f78e2194700 (LWP 2801)):
#0  0x7f79e556b029 in g_mutex_lock (mutex=mutex@entry=0x7f78e8002300) at
././glib/gthread-posix.c:1336
#1  0x7f79e5524ee5 in g_main_context_prepare
(context=context@entry=0x7f78e8002300, priority=priority@entry=0x7f78e2193b80)
at ././glib/gmain.c:3504
#2  0x7f79e55258fb in g_main_context_iterate
(context=context@entry=0x7f78e8002300, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#3  0x7f79e5525aec in g_main_context_iteration (context=0x7f78e8002300,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f79ec92551b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f79ec8cd19a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f79ec6f2e53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f79ec6f7d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f79e5d4d464 in start_thread (arg=0x7f78e2194700) at
pthread_create.c:333
#9  0x7f79ebdfc97f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 31 (Thread 0x7f7902a67700 (LWP 2771)):
#0  0x7f79e556b025 in g_mutex_lock (mutex=mutex@entry=0x7f78f8000990) at
././glib/gthread-posix.c:1336
#1  0x7f79e5525556 in g_main_context_dispatch
(context=context@entry=0x7f78f8000990) at ././glib/gmain.c:3850
#2  0x7f79e5525a40 in g_main_context_iterate
(context=context@entry=0x7f78f8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3929
#3  0x7f79e5525aec in g_main_context_iteration (context=0x7f78f8000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f79ec92551b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f79ec8cd19a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f79ec6f2e53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f79ec6f7d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f79e5d4d464 in start_thread (arg=0x7f7902a67700) at
pthread_create.c:333
#9  0x7f79ebdfc97f in clone () at

[kontact] [Bug 371242] New: kontact crashes sporadical after closing

2016-10-19 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=371242

Bug ID: 371242
   Summary: kontact crashes sporadical after closing
   Product: kontact
   Version: 5.2.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Application: kontact (5.2.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
I closed kontact using either Ctrl-Q or the x of the window frame.

This happens sporadical with no visible relation to the actions before.
Although I mainly use korganizer with ToDos and recently for dates / holidays.
This might possibly be related to bug 363431 although I upgraded recently to
Plasma 5.8 and Kernel 4.7 and Kontact is a higher version now. so I'm no sure.
It is much less now, than it was before and usually it closes normally.

The crash can be reproduced sometimes.

-- 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 0x7f77b5f93f00 (LWP 4704))]

Thread 46 (Thread 0x7f772a2f4700 (LWP 5266)):
#0  0x7f77cc95857d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f77c60d2c80 in read (__nbytes=16, __buf=0x7f772a2f3aa0,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7f7718002510) at ././glib/gwakeup.c:210
#3  0x7f77c608e485 in g_main_context_check
(context=context@entry=0x7f7718004380, max_priority=2147483647,
fds=fds@entry=0x7f77180030e0, n_fds=n_fds@entry=1) at ././glib/gmain.c:3707
#4  0x7f77c608e974 in g_main_context_iterate
(context=context@entry=0x7f7718004380, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3926
#5  0x7f77c608eaec in g_main_context_iteration (context=0x7f7718004380,
may_block=1) at ././glib/gmain.c:3990
#6  0x7f77cd48e51b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f77cd43619a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f77cd25be53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f77cd260d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f77c68b6464 in start_thread (arg=0x7f772a2f4700) at
pthread_create.c:333
#11 0x7f77cc96597f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 45 (Thread 0x7f76447f0700 (LWP 5188)):
#0  0x7f77cc95c50d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f77c608e9d6 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f7710004560, timeout=, context=0x7f7710004d30)
at ././glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f7710004d30,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
././glib/gmain.c:3924
#3  0x7f77c608eaec in g_main_context_iteration (context=0x7f7710004d30,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f77cd48e51b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f77cd43619a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f77cd25be53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f77cd260d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f77c68b6464 in start_thread (arg=0x7f76447f0700) at
pthread_create.c:333
#9  0x7f77cc96597f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 44 (Thread 0x7f76c97fa700 (LWP 5186)):
#0  0x7f77c60d4029 in g_mutex_lock (mutex=mutex@entry=0x7f770c005530) at
././glib/gthread-posix.c:1336
#1  0x7f77c608e9bb in g_main_context_poll (priority=,
n_fds=1, fds=0x7f770c004d60, timeout=, context=0x7f770c005530)
at ././glib/gmain.c:4223
#2  g_main_context_iterate (context=context@entry=0x7f770c005530,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
././glib/gmain.c:3924
#3  0x7f77c608eaec in g_main_context_iteration (context=0x7f770c005530,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f77cd48e51b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f77cd43619a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f77cd25be53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f77cd260d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f77c68b6464 in start_thread (arg=0x7f76c97fa700) at
pthread_create.c:333
#9  0x7f77cc96597f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 43

[plasmashell] [Bug 370195] New: Bug#839716: plasma-widgets: For easier bug reports widgets should have an "About" Section containing the package they belong to.

2016-10-06 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370195

Bug ID: 370195
   Summary: Bug#839716: plasma-widgets: For easier bug reports
widgets should have an "About" Section containing the
package they belong to.
   Product: plasmashell
   Version: master
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: wettererschein...@bb-goettingen.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Link to Debian Wishlist-Bug which I hereby send upstream: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839716
Thanks, Maria!

Package: plasma-widgets-workspace
Version: 4:4.11.13-2
Severity: wishlist
File: plasma-widgets

Dear Maintainer,

writing bug reports about bugs in Plasma widgets or addons is sometimes quite
difficult as it is not clear to which package they belong to.

Especially if you use a non-english language, you don't even know the official
name of the widget/addon, so it is really hard work to find out where to write
the bug report to. Even in the forums people sometimes can't help you,
especially if your used language is much different than english therefore using
completely different names.

Fazit: Widgets should have an "About" Section containing at least information
about the package they belong to. This would make reporting of bug alot easier.

Thanks for your work and time!
Maria



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plasma-widgets-workspace depends on:
ii  libc6 2.24-3
ii  libkdecore5   4:4.14.23-1
ii  libkdeui5 4:4.14.23-1
ii  libkdewebkit5 4:4.14.23-1
ii  libkio5   4:4.14.23-1
ii  libkunitconversion4   4:4.14.23-1
ii  libplasma34:4.14.23-1
ii  libplasmaclock4abi4   4:4.11.13-2
ii  libqt4-declarative4:4.8.7+dfsg-9
ii  libqt4-network4:4.8.7+dfsg-9
ii  libqt4-xml4:4.8.7+dfsg-9
ii  libqtcore44:4.8.7+dfsg-9
ii  libqtgui4 4:4.8.7+dfsg-9
ii  libqtwebkit4  2.3.4.dfsg-8.1
ii  libstdc++66.1.1-11
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxfixes31:5.0.2-1
ii  libxrender1   1:0.9.9-2
ii  plasma-dataengines-workspace  4:4.11.13-2

plasma-widgets-workspace recommends no packages.

plasma-widgets-workspace suggests no packages.

-- no debconf information

Maximiliano Curia wrote:

¡Hola Maria!

El 2016-10-04 a las 11:24 +0200, Maria escribió:
> Package: plasma-widgets-workspace Version: 4:4.11.13-2 Severity: wishlist 
> File: plasma-widgets

> Dear Maintainer,

> writing bug reports about bugs in Plasma widgets or addons is sometimes quite 
> difficult as it is not clear to which package they belong to.

> Especially if you use a non-english language, you don't even know the 
> official name of the widget/addon, so it is really hard work to find out 
> where to write the bug report to. Even in the forums people sometimes can't 
> help you, especially if your used language is much different than english 
> therefore using completely different names.

> Fazit: Widgets should have an "About" Section containing at least information 
> about the package they belong to. This would make reporting of bug alot 
> easier.

I don't see how this could be feasible under the Debian scope, but it shouldn't
be too hard to do this on the upstream side of things, reporting the
corresponding group (plasma, apps, extragear) and component (kdeplasma-addons,
etc) a particular plasmoid belongs to. The relation between the upstream
component names and the Debian source package names should be similar enough,
and are probably easy to find, although you'll need to know how to report to
the source package directly.

On the other hand, most kde applications have a Report Bug menu entry, that
reports the issue upstream, which is the preferred report method for the not
Debian specific issues, so it would make sense to add this "report bug" option
to the plasmoids.

Could you please send the feature request upstream?

Happy hacking,
-- 
"Fighting patents one by one will never eliminate the danger of software
patents, any more than swatting mosquitoes will eliminate malaria."
-- Richard M. Stallman
Saludos /\/\ /\ >< `/

[partitionmanager] [Bug 368211] New: crashes after start

2016-09-03 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368211

Bug ID: 368211
   Summary: crashes after start
   Product: partitionmanager
   Version: 1.0.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: wettererschein...@bb-goettingen.de

Application: partitionmanager-bin (1.0.3)
KDE Platform Version: 4.14.23
Qt Version: 4.8.7
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

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

I started it as root from the console and it crashed immediately. (Starting as
another user graphically with kdesu doesn't work as well but thats a different
bug report.)

Thanks!

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager
(partitionmanager-bin), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f418605e1c8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f418605f64a in __GI_abort () at abort.c:89
#8  0x7f41876c2f15 in qt_message_output (msgType=,
buf=0x120c8e8 "partitionmanager(9691)/kdeui (kdelibs): Session bus not found
\nTo circumvent this problem try the following command (with Linux and bash)
\nexport $(dbus-launch) ") at global/qglobal.cpp:2447
#9  0x7f4187d4264c in QDebug::~QDebug (this=0x7ffe0267dc10,
__in_chrg=) at /usr/include/qt4/QtCore/qdebug.h:85
#10 0x7f4187d9b2ba in KApplicationPrivate::init (this=0x1169e80,
GUIenabled=GUIenabled@entry=true) at ./kdeui/kernel/kapplication.cpp:516
#11 0x7f4187d9bc92 in KApplication::KApplication (this=0x7ffe0267de70,
GUIenabled=true) at ./kdeui/kernel/kapplication.cpp:352
#12 0x004010e2 in ?? ()
#13 0x7f418604b730 in __libc_start_main (main=0x400fb0, argc=1,
argv=0x7ffe0267df88, init=, fini=,
rtld_fini=, stack_end=0x7ffe0267df78) at ../csu/libc-start.c:291
#14 0x004011fd in _start ()

Possible duplicates by query: bug 363463, bug 357541.

Reported using DrKonqi

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

[plasmashell] [Bug 367768] New: Plasma crashed when changing into a new created activity

2016-08-24 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=367768

Bug ID: 367768
   Summary: Plasma crashed when changing into a new created
activity
   Product: plasmashell
   Version: 5.6.5
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: wettererschein...@bb-goettingen.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.5)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
After creating a new activity with custom energy saving settings I changed into
my other main activity using a shortcut. At first in the info bar
(Kontrolleiste) containing the active activities the new one wasn't shown and
the shortcut changed into the third activity. After hitting the shortcut
several times it crashed.

I am only posting this, because the Fehleranalyse said it is usefull with three
of three stars. Maybe it is of use.

Greetings!

-- 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 0x7fd63d1ca940 (LWP 3325))]

Thread 20 (Thread 0x7fd3f3596700 (LWP 4264)):
#0  0x7fd6345c5ac9 in g_mutex_lock (mutex=mutex@entry=0x7fd3ec000990) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gthread-posix.c:1335
#1  0x7fd634580ddc in g_main_context_check
(context=context@entry=0x7fd3ec000990, max_priority=2147483647,
fds=fds@entry=0x7fd3ec004f80, n_fds=n_fds@entry=1) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3683
#2  0x7fd634581340 in g_main_context_iterate
(context=context@entry=0x7fd3ec000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3837
#3  0x7fd6345814ac in g_main_context_iteration (context=0x7fd3ec000990,
may_block=1) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7fd63813b51b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd6380e319a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd637f08e53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fd637f0dd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fd63701f464 in start_thread (arg=0x7fd3f3596700) at
pthread_create.c:333
#9  0x7fd63782530d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7fd541ded700 (LWP 4263)):
#0  0x7fd63781c19d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd63458139c in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7fd3f8002f70, timeout=, context=0x7fd3f80040b0) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7fd3f80040b0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7fd6345814ac in g_main_context_iteration (context=0x7fd3f80040b0,
may_block=1) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7fd63813b51b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd6380e319a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd637f08e53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fd637f0dd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fd63701f464 in start_thread (arg=0x7fd541ded700) at
pthread_create.c:333
#9  0x7fd63782530d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fd543fff700 (LWP 4029)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fd637f0ec3b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fd57c5d3bbf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7fd57c5d7bb8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fd57c5d2dad in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fd57c5d7c12 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fd57c5d2dad in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fd57c5d7c12 in ?? () from

[kdelibs] [Bug 363431] kontact crashes when closing

2016-05-24 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363431

--- Comment #4 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Dear Allan Winter,

thanks for the patch and your help! Unluckily I don't know how to use
it. What will it do?

And I wanted to link to the other problems in this installation as they
might be connected(?).

* akonadi-backend-mysql: errors in selftest 5,16,17; maybe connection to
severe unstability of my system? Debian Bug#825224
* dolphin 15.08.3: Crashes randomly and frequently Debian Bug#808244
* Search emails in Kmail/Kontact gives no results although it should.
* kdeinit5 sometimes crashes before log out.
* Krunner crashes regularly (segmentation fault) with no visible reason
as well. I have to restart it manually. Sometimes even the starter and
the control bar crash leaving me unoperable. No Bug report yet as there
are no debug symbols available.
* VLC does'nt start related somehow to the Qt Interface plus purge VLC
wants to uninstall essential KDE stuff. Debian Bug#825140

Thanks alot again! I am a little bit in a despair by now.
Maria

Allen Winter via KDE Bugzilla:
> https://bugs.kde.org/show_bug.cgi?id=363431
> 
> --- Comment #3 from Allen Winter <win...@kde.org> ---
> I just attached a patch that might fix this crash.  I am unable to reproduce
> the crash, however.
> 
> Herr Schmidt, maybe you can test it ?
>

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

[kontact] [Bug 363431] New: kontact crashes when closing

2016-05-23 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363431

Bug ID: 363431
   Summary: kontact crashes when closing
   Product: kontact
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Application: kontact (4.14.10)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
Dear maintainers,
kontact was opened automatically after login because it was open when I shutted
down my computer last time. I just looked at the task planner and clicked on
akregator (it said this is a different instance or sth like that and the window
has to brought up to foreground, but that never happened it just showed the
window from the planner before) then I switched to calendar and planner back
and forth. I decided to quit and hitted the window quit button at the upper
right window corner. Then this dialogue about crashing came up. This happened
just a few minutes ago as well in a similar situation.

Things I noticed:
First time this happened I quitted because I did not see my mouse cursor
anymore, although it was obviously there as several buttons where highlited
when the invisible mouse passed them. This just happend again and might be
correlated to using the console with Ctrl-Alt-F1 and installing the debug
symbols. (It happened when I switched back (Ctrl-Alt-F7) while the install was
going. Switching back to the console and after the install back to KDE made the
mouse visible again.

Thanks for your work!

The crash can be reproduced sometimes.

-- 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 0x7f40b8927940 (LWP 24599))]

Thread 4 (Thread 0x7f4098ab8700 (LWP 24608)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f40b5047f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f40b5047fb9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f40afb4f454 in start_thread (arg=0x7f4098ab8700) at
pthread_create.c:334
#4  0x7f40b5df6e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f40581ad700 (LWP 24609)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f40b4d6bef1 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f40b5078536 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f40afb4f454 in start_thread (arg=0x7f40581ad700) at
pthread_create.c:334
#4  0x7f40b5df6e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f40428be700 (LWP 24667)):
#0  0x7f40b5deddcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f40af66739c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f40af6674ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f40b65ed266 in QEventDispatcherGlib::processEvents
(this=0x7f403c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x7f40b65bb18f in QEventLoop::processEvents
(this=this@entry=0x7f40428bdc90, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f40b65bb4f5 in QEventLoop::exec (this=this@entry=0x7f40428bdc90,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f40b64aa549 in QThread::exec (this=) at
thread/qthread.cpp:538
#7  0x7f40b64ace3c in QThreadPrivate::start (arg=0x244ca10) at
thread/qthread_unix.cpp:352
#8  0x7f40afb4f454 in start_thread (arg=0x7f40428be700) at
pthread_create.c:334
#9  0x7f40b5df6e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f40b8927940 (LWP 24599)):
[KCrash Handler]
#6  QAbstractSlider::maximum (this=0x20) at widgets/qabstractslider.cpp:366
#7  0x7f40b7d30584 in KViewStateSaverPrivate::restoreScrollBarState
(this=0x22ca1a0) at
/build/kde4libs-3hgzgp/kde4libs-4.14.14/kdeui/itemviews/kviewstatesaver.cpp:67
#8  KViewStateSaver::qt_static_metacall (_o=, _id=, _a=, _c=) at
/build/kde4libs-3hgzgp/kde4libs-4.14.14/obj-x86_64-linux-gnu/kdeui/kviewstatesaver.moc:52
#9  0x7f40b65d6db1 in QObject::event (this=0x4a5e900, e=) at
kernel/qobject.cpp:1222
#10 0x7f40b6fe190c in QApplicationPrivate::notify_helper
(this=this@entry=0x22cf300, receiver=receiver@entry=0x4a5e900,
e=e@entry=0x4fc7120) at kernel/qapplication.cpp:4570
#11 0x7f40b6fe8846 in QApplication::notify (this=this@entry=0x7fffda223c40,
receiver=receiver@entry=0x4a5e900, e=e@entry=0x4fc7120) at
kernel/qapplication.cpp:4356
#12 0x7f40b7d623ca in KApplication::notify (this=0x7fffda223c40,

[systemsettings] [Bug 363413] New: although setting "switching control"=Desktop, remembers layout through different activities

2016-05-22 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363413

Bug ID: 363413
   Summary: although setting "switching control"=Desktop,
remembers layout through different activities
   Product: systemsettings
   Version: 5.4.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

I want to have two activities A and B. A has with several Desktops / virtual
workspaces (Arbeitsflächen), each one using a certain keyboard layout.
Activity B should only have one workspace/Desktop containing a certain set of
Plasma widgets+Software and should have a certain fixed keyboard layout.

First Problem:
Workspaces and activities seem both to be global: Whenever I change the amount
and settings of Workspaces while in A, after switching to B I will find the
changed number and settings as well. Result is, that I will always keep the
last keyboard layout from the workspace I used last in A.

Second problem:
This is confusing especially as it is possible to make the workspaces in B look
different than those in A (like wallpaper) without changing something in A.
This provokes the assumption, that the activities are autonomous regarding  the
workspaces as well. But in truth it seems to be a mixup of
B-workspaces-settings and global/A-workspaces settings. This is not intuitive.
Especially as there are different ways of changing something about the
workspaces which is not selfexplaining.
I don't understand, wether the workspaces in A are the same instances like
those in B or not. 

Reproducible: Always



Expected Results:  
I would expect the activities to be autonomous regarding workspaces and
keyboard layouts as well (unless I choose the option: global).

Regarding the system settings I would expect the setting to be visually devided
by activity. E.g. in KSystemsettings>Workspaces a switch on top where you can
switch to which activity the settings should apply.

And I would expect to keep the last used keyboard layout inside a specific
workspace in B when I switch from A to B.

Thanks for your great work!

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

[plasmashell] [Bug 362798] New: Plasma crashes from time to time with no obvious reason

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

Bug ID: 362798
   Summary: Plasma crashes from time to time with no obvious
reason
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: wettererschein...@bb-goettingen.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
This happens from time to time - but every day. I couldn't find a relation to
my actions.

- Unusual behavior I noticed:
I have several problems regarding graphics, probably kwin or ksystemsettings.
See my bugreports #362720 #362726 and #362728.

I've got quite new Hardware (Thinkpad T560) don't know wether it could be
related to that. I hope you can find something in the technical details. The
program said it's useful...

Thanks for your work - by the way!

The crash can be reproduced sometimes.

-- 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 0x7f20a20348c0 (LWP 2640))]

Thread 8 (Thread 0x7f208d1f3700 (LWP 2643)):
#0  0x7f209c73ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f20a07ffc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f20a08018d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f208f341629 in QXcbEventReader::run (this=0x2440860) at
qxcbconnection.cpp:1253
#4  0x7f209ce3084e in QThreadPrivate::start (arg=0x2440860) at
thread/qthread_unix.cpp:331
#5  0x7f209bf1d6fa in start_thread (arg=0x7f208d1f3700) at
pthread_create.c:333
#6  0x7f209c746b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f20868fe700 (LWP 2645)):
#0  0x7f2099514a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f20994d0311 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f20994d042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f209d067a9b in QEventDispatcherGlib::processEvents
(this=0x7f2088c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f209d00edea in QEventLoop::exec (this=this@entry=0x7f20868fdce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f209ce2b8a4 in QThread::exec (this=this@entry=0x251d980) at
thread/qthread.cpp:503
#6  0x7f209f6d33c5 in QQmlThreadPrivate::run (this=0x251d980) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f209ce3084e in QThreadPrivate::start (arg=0x251d980) at
thread/qthread_unix.cpp:331
#8  0x7f209bf1d6fa in start_thread (arg=0x7f20868fe700) at
pthread_create.c:333
#9  0x7f209c746b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f207b34d700 (LWP 2646)):
#0  0x7f209c73ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f20994d031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f20994d042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f209d067a9b in QEventDispatcherGlib::processEvents
(this=0x7f20740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f209d00edea in QEventLoop::exec (this=this@entry=0x7f207b34cce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f209ce2b8a4 in QThread::exec (this=this@entry=0x2891420) at
thread/qthread.cpp:503
#6  0x7f209f6d33c5 in QQmlThreadPrivate::run (this=0x2891420) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f209ce3084e in QThreadPrivate::start (arg=0x2891420) at
thread/qthread_unix.cpp:331
#8  0x7f209bf1d6fa in start_thread (arg=0x7f207b34d700) at
pthread_create.c:333
#9  0x7f209c746b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f2079479700 (LWP 2647)):
#0  update_get_addr (ti=0x7f209d25b788) at dl-tls.c:807
#1  0x7f209ce2f792 in get_thread_data () at thread/qthread_unix.cpp:181
#2  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at
thread/qthread_unix.cpp:212
#3  0x7f209d0672e1 in postEventSourcePrepare (timeout=0x0,
s=0x7f206c0012d0) at kernel/qeventdispatcher_glib.cpp:247
#4  postEventSourceCheck (source=0x7f206c0012d0) at
kernel/qeventdispatcher_glib.cpp:264
#5  0x7f20994cfd51 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f20994d02c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f20994d042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f209d067a9b in QEventDispatcherGlib::processEvents
(this=0x7f206c0008c0,

[kmail2] [Bug 362728] list of Mails in a folder not readable (white on white)

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362728

--- Comment #1 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 98800
  --> https://bugs.kde.org/attachment.cgi?id=98800=edit
Here you can see clearly that the titles of all mails in that folder are not
shown.

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

[kmail2] [Bug 362728] New: list of Mails in a folder not readable (white on white)

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362728

Bug ID: 362728
   Summary: list of Mails in a folder not readable (white on
white)
   Product: kmail2
   Version: 5.1.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Dear maintainers,

I can't use the program, as in the folderview (right from the treeview and
above the actual mail) the titles etc. are shown white on white. I will add a
picture on which you can see what I mean. 

These are mails from a Icedove import. But I suggest that this has something to
do with kwin or system settings due to strange behaviour regardings graphics
throughout the whole distro. Please have a look at my bug reports #362723,
#362720.

Thanks for your work, by the way!

Reproducible: Always




Thinkpad T560

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

[kontact] [Bug 362726] New: KOrganizer crashed after trying to make a task from inside the KMail tab

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362726

Bug ID: 362726
   Summary: KOrganizer crashed after trying to make a task from
inside the KMail tab
   Product: kontact
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Application: kontact (5.1.3)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I tried to make a task inside kmail (there is a bar below to do this) after I
applied it crashed.



Before that I tried to make a new task in the task part of Korganizer and this
task did never show up there. It only was shown as a link in the overview tab.
But the link lead me into the nothingness of tasks...

-- 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 0x7fc2256b1940 (LWP 14322))]

Thread 49 (Thread 0x7fc21bfff700 (LWP 14324)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23cbb788b in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fc23d45483c ) at wtf/FastMalloc.cpp:2825
#2  0x7fc23cbb78c9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0x7fc23d45483c ) at
wtf/FastMalloc.cpp:1993
#3  0x7fc23897a6fa in start_thread (arg=0x7fc21bfff700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 48 (Thread 0x7fc1d9079700 (LWP 14325)):
#0  0x7fc23814d340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc23814f84b in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc23815024b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc23815042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc23f477a9b in QEventDispatcherGlib::processEvents
(this=0x7fc1d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fc23f41edea in QEventLoop::exec (this=this@entry=0x7fc1d9078c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fc23f23b8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fc23f24084e in QThreadPrivate::start (arg=0x1ed49e0) at
thread/qthread_unix.cpp:331
#8  0x7fc23897a6fa in start_thread (arg=0x7fc1d9079700) at
pthread_create.c:333
#9  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 47 (Thread 0x7fc1d2b24700 (LWP 14326)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23c8c5a74 in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x7fc2205ba058) at heap/BlockAllocator.cpp:139
#2  0x7fc23cbe7541 in WTF::wtfThreadEntryPoint(void*) () at
wtf/ThreadingPthreads.cpp:195
#3  0x7fc23897a6fa in start_thread (arg=0x7fc1d2b24700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 46 (Thread 0x7fc1d2323700 (LWP 14327)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23c8c6aa3 in JSC::GCThread::gcThreadMain (this=0x1ed1690) at
heap/GCThread.cpp:81
#2  0x7fc23cbe7541 in WTF::wtfThreadEntryPoint(void*) () at
wtf/ThreadingPthreads.cpp:195
#3  0x7fc23897a6fa in start_thread (arg=0x7fc1d2323700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 45 (Thread 0x7fc1d1b22700 (LWP 14328)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23c8c6aa3 in JSC::GCThread::gcThreadMain (this=0x1ed36d0) at
heap/GCThread.cpp:81
#2  0x7fc23cbe7541 in WTF::wtfThreadEntryPoint(void*) () at
wtf/ThreadingPthreads.cpp:195
#3  0x7fc23897a6fa in start_thread (arg=0x7fc1d1b22700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 44 (Thread 0x7fc1d1321700 (LWP 14329)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23c8c6aa3 in JSC::GCThread::gcThreadMain (this=0x20c8c20) at
heap/GCThread.cpp:81
#2  0x7fc23cbe7541 in WTF::wtfThreadEntryPoint(void*) () at
wtf/ThreadingPthreads.cpp:195
#3  0x7fc23897a6fa in start_thread (arg=0x7fc1d1321700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 43 (Thread 0x7fc1b7381700 (LWP 14330)):
#0

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362720

--- Comment #6 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 98799
  --> https://bugs.kde.org/attachment.cgi?id=98799=edit
Due to this bug some boxes are almost unreadable. This is on ixquick.de

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

[Discover] [Bug 362723] text overlaps and is not readable

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362723

--- Comment #1 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 98798
  --> https://bugs.kde.org/attachment.cgi?id=98798=edit
Muon Discover graphical/text failure

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

[Discover] [Bug 362723] New: text overlaps and is not readable

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362723

Bug ID: 362723
   Summary: text overlaps and is not readable
   Product: Discover
   Version: 5.6.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

The texts of the main examples are overlapping and therefore not readable. See
Picture. 

Reproducible: Always

Steps to Reproduce:
1. Start the program. ;)

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362720

--- Comment #5 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 98797
  --> https://bugs.kde.org/attachment.cgi?id=98797=edit
firefox and textboxes are still dark

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362720

--- Comment #4 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 98796
  --> https://bugs.kde.org/attachment.cgi?id=98796=edit
back

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362720

--- Comment #3 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 98795
  --> https://bugs.kde.org/attachment.cgi?id=98795=edit
switching back

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362720

--- Comment #2 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 98794
  --> https://bugs.kde.org/attachment.cgi?id=98794=edit
after first switch

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362720

--- Comment #1 from Herr Schmidt <wettererschein...@bb-goettingen.de> ---
Created attachment 98793
  --> https://bugs.kde.org/attachment.cgi?id=98793=edit
starting point

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

[systemsettings] [Bug 362720] New: desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362720

Bug ID: 362720
   Summary: desktop appearance: switching between theme Breeze and
~ dark mixes up in Dada-style
   Product: systemsettings
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_desktopthemedetails
  Assignee: jamboar...@gmail.com
  Reporter: wettererschein...@bb-goettingen.de
CC: plasma-b...@kde.org

If I switch the desktop appearance theme (Erscheinungsbild; first entry) from
Breeze to Breeze dark, apply it only some things like the control bar
(Kontrollleiste; below of the screen with start button etc.) get dark. When I
switch back to Breeze again it results in a mixed theme with a somewhat lighter
grey control bar but dark windows. Only if after this step I just click on
Breeze dark (without applying) and click back to Breeze and apply (which then
is possible although it is supposed to be the actual theme) the colors change
to the light theme again. But the Boxes (text input) inside a Website like this
are still black. And Firefox stays dark (although only standard theme is
installed).

Reproducible: Always

Steps to Reproduce:
Systemsettings - Desktop Design (Arbeitsbereich Design; first entry) -
Appearance (Erscheinungsbild; first entry)
1. Switch from Breeze to Breeze dark and apply
2. Switch back to Breeze and apply.
3. Click on Breeze dark, click back on Breeze and then apply



Thinkpad T560

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

[systemsettings] [Bug 362718] New: Systemsettings 5.5.5 crashes when Switching between two menu items

2016-05-05 Thread Herr Schmidt via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362718

Bug ID: 362718
   Summary: Systemsettings 5.5.5 crashes when Switching between
two menu items
   Product: systemsettings
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Application: systemsettings5 (5.5.5)

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

-- Information about the crash:
Bug #354164 sounds similar, but there it stated that the error is solved in
Version 4.x (I don't remember exactly). So as I am using Version 5.5.5 it can't
be the same bug, no?

Every time I go to the desktop settings and switch several times (not only
twice as in the other bug) between some entries after 6-12 changes it crashes.

- Unusual behavior I noticed:
* Switching between Breeze and Breeze-dark doesn't work properly. This results
in a mixup between the two and the layout changes every time I click on the
other theme, click back to the active theme and apply the "change".
* Plasma crashed two or three times without me being able to tell why or in
which situation.
* Grafics are disturbed (Some texts inside a button are longer than the button,
in Discover the descriptions of the top presented items above are not readable
because the overlap outside of the boxes, Ubuntu Software Center shows white
text on white background which makes it unusable)
* Theres a cracking noise out of the speakers after login, when initialising
KDE.

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7ff107abc700 (LWP 11272)):
#0  0x7ff115af0e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff1137d8c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7ff1137da8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7ff109e0e629 in QXcbEventReader::run (this=0x1f054f0) at
qxcbconnection.cpp:1253
#4  0x7ff1161e684e in QThreadPrivate::start (arg=0x1f054f0) at
thread/qthread_unix.cpp:331
#5  0x7ff112f626fa in start_thread (arg=0x7ff107abc700) at
pthread_create.c:333
#6  0x7ff115afcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7ff0ed2e8700 (LWP 11281)):
#0  0x7ff112a4093f in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff112a4124b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff112a4142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff11641da9b in QEventDispatcherGlib::processEvents
(this=0x7ff0e01619d0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ff1163c4dea in QEventLoop::exec (this=this@entry=0x7ff0ed2e7ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ff1161e18a4 in QThread::exec (this=this@entry=0x49f4670) at
thread/qthread.cpp:503
#6  0x7ff114b603c5 in QQmlThreadPrivate::run (this=0x49f4670) at
qml/ftw/qqmlthread.cpp:141
#7  0x7ff1161e684e in QThreadPrivate::start (arg=0x49f4670) at
thread/qthread_unix.cpp:331
#8  0x7ff112f626fa in start_thread (arg=0x7ff0ed2e8700) at
pthread_create.c:333
#9  0x7ff115afcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7ff0e7009700 (LWP 11282)):
#0  0x7ff112a40d38 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff112a412c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff112a4142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff11641da9b in QEventDispatcherGlib::processEvents
(this=0x7ff0dc038220, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ff1163c4dea in QEventLoop::exec (this=this@entry=0x7ff0e7008ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ff1161e18a4 in QThread::exec (this=this@entry=0x2618cd0) at
thread/qthread.cpp:503
#6  0x7ff114b603c5 in QQmlThreadPrivate::run (this=0x2618cd0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7ff1161e684e in QThreadPrivate::start (arg=0x2618cd0) at
thread/qthread_unix.cpp:331
#8  0x7ff112f626fa in start_thread (arg=0x7ff0e7009700) at
pthread_create.c:333
#9  0x7ff115afcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7ff0eefe6700 (LWP 11285)):
#0  0x7ff112a85a49 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff112a403f4 in g_main_context_release () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff112a412d6 in ?? ()