[valgrind] [Bug 371668] New: ppc64 clobbering of R2 is invalid.

[Will Schmidt via KDE Bugzilla]

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

Bug ID: 371668
   Summary: ppc64 clobbering of R2 is invalid.
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: will_schm...@vnet.ibm.com

This was recently noticed and reported via GCC bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78095

"
>  (Powerpc)
>   GCC now diagnoses inline assembly that clobbers register r2.
> This has always been invalid code, and is no longer quietly   
> tolerated.
"


Reproducible: Always


Actual Results:  
Errors reported in several spots, including: 
m_debuglog.c: In function 'vgPlain_debugLog':
m_debuglog.c:228:4: error: PIC register clobbered by 'r2' in 'asm'
__asm__ volatile (
^~~
### and 
In file included from ../include/pub_tool_clreq.h:34:0,
 from pub_core_clreq.h:38,
 from vg_preloaded.c:46:
vg_preloaded.c: In function '_vgnU_ifunc_wrapper':
../include/valgrind.h:3292:7: error: PIC register clobbered by 'r2' in 'asm'
   __asm__ volatile(   \
   ^
vg_preloaded.c:104:5: note: in expansion of macro 'CALL_FN_W_v'
 CALL_FN_W_v(result, fn);
 ^~~

-- 
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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #2 from Herr Schmidt  ---
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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #1 from Herr Schmidt  ---
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

[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

[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.

[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 /\/\ /\ >< `/ 

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

--- Comment #19 from Will Schmidt  ---
Chased this one around under gdb for a while, looking for where the R2 or the
stack frame are getting messed up.Something seems to be going horribly
wrong here, but it's possible valgrind just always does this and I'm totally
misunderstanding what I am seeing.

With that said:

It looks like something is going badly in  m_dispatch/dispatch-ppc64be-linux.S,
line 225, in or around the vspltisw instruction.   Noting the changes between
the backtrace before and the backtrace after the step over that instruction.

(gdb) 
223beq .LafterVMX2
=> 0x38092e88 <.vgPlain_disp_run_translations+320>:41 82 00 0c   
beq 0x38092e94 <.vgPlain_disp_run_translations+332>
(gdb) bt
#0  .vgPlain_disp_run_translations () at
m_dispatch/dispatch-ppc64be-linux.S:223
#1  0x380a3114 in run_thread_for_a_while
(two_words=two_words@entry=0x802b3fe20,
dispatchCtrP=dispatchCtrP@entry=0x802b3fe34, tid=tid@entry=1, 
alt_host_addr=alt_host_addr@entry=0,
use_alt_host_addr=use_alt_host_addr@entry=0 '\000') at
m_scheduler/scheduler.c:947
#2  0x380a5a18 in vgPlain_scheduler (tid=) at
m_scheduler/scheduler.c:1336
#3  0x380bf3c8 in thread_wrapper (tidW=) at
m_syswrap/syswrap-linux.c:103
#4  run_a_thread_NORETURN (tidW=) at
m_syswrap/syswrap-linux.c:156
#5  0x in ?? ()
(gdb) stepi
.vgPlain_disp_run_translations () at m_dispatch/dispatch-ppc64be-linux.S:225
225vspltisw 3,0x0  /* generate zero */
=> 0x38092e8c <.vgPlain_disp_run_translations+324>:10 60 03 8c   
vspltisw v3,0
(gdb) bt
#0  .vgPlain_disp_run_translations () at
m_dispatch/dispatch-ppc64be-linux.S:225
#1  0x380a3114 in run_thread_for_a_while (two_words=0x0,
dispatchCtrP=0x0, tid=, alt_host_addr=0,
use_alt_host_addr=)
at m_scheduler/scheduler.c:947
#2  0x in ?? ()

(gdb) stepi
226mtvscr  3
=> 0x38092e90 <.vgPlain_disp_run_translations+328>:10 00 1e 44   
mtvscr  v3
(gdb) 
230stdu1,-48(1)
=> 0x38092e94 <.vgPlain_disp_run_translations+332>:f8 21 ff d1   
stdur1,-48(r1)
(gdb) 
.vgPlain_disp_run_translations () at m_dispatch/dispatch-ppc64be-linux.S:233
233mr  31,4  /* r31 (generated code gsp) = r4 */
=> 0x38092e98 <.vgPlain_disp_run_translations+336>:7c 9f 23 78   
mr  r31,r4
(gdb) 
240mtctr   5
=> 0x38092e9c <.vgPlain_disp_run_translations+340>:7c a9 03 a6   
mtctr   r5
(gdb) 
241bctr
=> 0x38092ea0 <.vgPlain_disp_run_translations+344>:4e 80 04 20   
bctr
(gdb) 
0x00080324 in ?? ()
=> 0x00080324:83 df 00 08lwz r30,8(r31)
(gdb) 

... at which point I suspect we're off in the weeds with our IP/SP.Did a
bit more single-stepping after that,..   Neither I nor gdb are able to map
whatever we are executing to anything..  

0x00080324 in ?? ()
=> 0x00080324:83 df 00 08lwz r30,8(r31)
(gdb) 
0x000803240004 in ?? ()
=> 0x000803240004:37 de ff ffaddic.  r30,r30,-1
(gdb) 
0x000803240008 in ?? ()
=> 0x000803240008:93 df 00 08stw r30,8(r31)
(gdb) 
0x00080324000c in ?? ()
=> 0x00080324000c:40 80 00 10bge 0x80324001c
(gdb) 

eventually we stumble across ppc32g_dirtyhelper_MFSPR_
(gdb) 
0x0008032401ec in ?? ()
=> 0x0008032401ec:4e 80 04 21bctrl
(gdb) 
ppc32g_dirtyhelper_MFSPR_268_269 (r269=0) at priv/guest_ppc_helpers.c:98
98   if (r269) {
=> 0x3817ce80 :2f a3 00 00   
cmpdi   cr7,r3,0
   0x3817ce84 :40 9e 00 1c   
bne cr7,0x3817cea0 

a bctrl in that takes us back into dispatch-ppc64be-linux.S
(gdb) 
0x00080324026c in ?? ()
=> 0x00080324026c:4e 80 04 21bctrl
(gdb) 
.vgPlain_disp_cp_chain_me_to_fastEP () at
m_dispatch/dispatch-ppc64be-linux.S:435
435li   6, VG_TRC_CHAIN_ME_TO_FAST_EP
=> 0x38093034 <.vgPlain_disp_cp_chain_me_to_fastEP+0>:38 c0 00 33  
 li  r6,51
(gdb) 
436mflr 7

eventually we branch into postamble/vgPlain_disp_run_translations...

(gdb) 
442b.postamble
=> 0x38093040 <.vgPlain_disp_cp_chain_me_to_fastEP+12>:4b ff fe 64 
  b   0x38092ea4 <.vgPlain_disp_run_translations+348>
(gdb) 
.vgPlain_disp_run_translations () at m_dispatch/dispatch-ppc64be-linux.S:256
256addi1,1,48

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

--- Comment #16 from Will Schmidt  ---
A bit of an info dump from the IRC discussions occurring on this bug:

A gdb session revealed:

Program received signal SIGSEGV, Segmentation fault.
 0x3824b2b0 in is_BCDstring128_helper ()
 (gdb) disas 0x3824b2b0
 Dump of assembler code for function is_BCDstring128_helper:
 => 0x3824b2b0 <+0>: .long 0x0
0x3824b2b4 <+4>: addir0,r23,-11904

Disassembly of the function by name shows a different address.
 (gdb) disas is_BCDstring128_helper
 Dump of assembler code for function is_BCDstring128_helper:
0x3817d180 <+0>: cmpdi   cr7,r3,1
0x3817d184 <+4>: li  r3,1

per some disassembly, I believe we have confirmed we just tried to execute the
OPD...

3824b2b0 g F .opd   0080 is_BCDstring128_helper

> objdump -h none/none-ppc64be-linux 

none/none-ppc64be-linux: file format elf64-powerpc

Sections:
Idx Name  Size  VMA   LMA   File off  Algn
  0 .note.gnu.build-id 0024  38000158  38000158  0158 
2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  1 .text 001c6ed0  38000180  38000180  0180  2**5
  CONTENTS, ALLOC, LOAD, READONLY, CODE
  2 .rodata   00059198  381c7050  381c7050  001c7050  2**3
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  3 .eh_frame 0030  382201e8  382201e8  002201e8  2**3
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  4 .data.rel.ro  0030  3823ffd0  3823ffd0  0022ffd0  2**3
  CONTENTS, ALLOC, LOAD, DATA
  5 .data 25f0  3824  3824  0023  2**3
  CONTENTS, ALLOC, LOAD, DATA
  6 .opd  ad98  382425f0  382425f0  002325f0  2**3
  CONTENTS, ALLOC, LOAD, DATA
  7 .got  0030  3824d388  3824d388  0023d388  2**3
  CONTENTS, ALLOC, LOAD, DATA
  8 .bss  009da2a0  3824d3c0  3824d3c0  0023d3b8  2**4
  ALLOC
  9 .comment  002c      0023d3b8  2**0
  CONTENTS, READONLY
 10 .debug_aranges 1c20      0023d3f0  2**4
  CONTENTS, READONLY, DEBUGGING
 11 .debug_info   0030b9a3      0023f010  2**0
  CONTENTS, READONLY, DEBUGGING
 12 .debug_abbrev 000156fa      0054a9b3  2**0
  CONTENTS, READONLY, DEBUGGING
 13 .debug_line   00055a2f      005600ad  2**0
  CONTENTS, READONLY, DEBUGGING
 14 .debug_frame  00023b30      005b5ae0  2**3
  CONTENTS, READONLY, DEBUGGING
 15 .debug_str0002e1c5      005d9610  2**0
  CONTENTS, READONLY, DEBUGGING
 16 .debug_loc002b2e89      006077d5  2**0
  CONTENTS, READONLY, DEBUGGING
 17 .debug_ranges 00051bb0      008ba65e  2**0
  CONTENTS, READONLY, DEBUGGING

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 Attachment #101244|0   |1
is obsolete||

--- Comment #15 from Will Schmidt  ---
Created attachment 101246
  --> https://bugs.kde.org/attachment.cgi?id=101246=edit
comment 3 step 3 output respin

comment 3 step 3 respin with --trace-notbelow=2092

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

--- Comment #13 from Will Schmidt  ---
Created attachment 101244
  --> https://bugs.kde.org/attachment.cgi?id=101244=edit
comment 3 step 3 output

results from comment3 step 3

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

--- Comment #12 from Will Schmidt  ---
Created attachment 101243
  --> https://bugs.kde.org/attachment.cgi?id=101243=edit
output from monitor v.translate on segfaulting instruction

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

--- Comment #11 from Will Schmidt  ---
(In reply to Mark Wielaard from comment #9)
> Assuming that is with remote vgdb attached then you should be able to get
> the generated IR and assembly with:
>  monitor v.translate 0x100016dc 0b0011
> 
> (See the manual or valgrind --help-debug for the explanation of the
> --trace-flags)

Ok.   So given this: 
Program received signal SIGSEGV, Segmentation fault.
0x100016d8 in test_bcdadd () at test_isa_2_07_part1.c:710
710  __asm__ __volatile__ ("bcdadd. %0, %1, %2, 0" : "=v" (vec_out):
"v" (vec_inA),"v" (vec_inB));
I did the monitor command against the ... 16d8 addr.
(gdb) monitor v.translate 0x100016d8 0b0011

The output is larger than I had expected...attaching it momentarily.

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

--- Comment #10 from Will Schmidt  ---
Created attachment 101242
  --> https://bugs.kde.org/attachment.cgi?id=101242=edit
trace flags output

last portion of output from a run in attachment.

$ ./vg-in-place --tool=none  --trace-flags=10001110 --trace-notbelow=2000
none/tests/ppc64/test_isa_2_07_part1 -a

very last bit of output also inline:
377   std %r14,1296(%r31)
378   ld %r14,1304(%r31)
379   li_word %r15,0xFFFC
380   and %r16,%r14,%r15
381   (xIndir) if (always) { std %r16,1296(%r31); imm64 r30,$disp_cp_xindir;
mtctr r30; bctr }

VexExpansionRatio 36 1872   520 :10

==4341== 
==4341== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==4341==  Bad permissions for mapped region at address 0x3824B2B0
==4341==at 0x100016D8: test_bcdadd (test_isa_2_07_part1.c:710)
==4341==by 0x10001A2F: test_av_bcd (test_isa_2_07_part1.c:1419)
==4341==by 0x41E4D87: generic_start_main.isra.0 (libc-start.c:289)
==4341==by 0x41E4FB7: (below main) (libc-start.c:80)
==4341==

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

--- Comment #8 from Will Schmidt  ---
off-by-one on my disassembly "==>" pointer, the SIGSEGV is actually on the
bcdadd instruction.   (showed up differently while single-stepping).

   0x100016d4 <+64>:lxvd2x  vs32,r10,r9
   0x100016d8 <+68>:lxvd2x  vs33,0,r9
=> 0x100016dc <+72>:bcdadd. v0,v1,v0,0
   0x100016e0 <+76>:li  r10,16

 still poking..

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Will Schmidt via KDE Bugzilla]

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

--- Comment #7 from Will Schmidt  ---
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x100016d8 in test_bcdadd () at test_isa_2_07_part1.c:710
710  __asm__ __volatile__ ("bcdadd. %0, %1, %2, 0" : "=v" (vec_out):
"v" (vec_inA),"v" (vec_inB));

(gdb) disas
Dump of assembler code for function test_bcdadd:
   0x10001694 <+0>:nop
   0x10001698 <+4>:lwz r9,-32228(r2)
   0x1000169c <+8>:cmpwi   cr7,r9,0
   0x100016a0 <+12>:beq cr7,0x100016c8 
   0x100016a4 <+16>:nop
   0x100016a8 <+20>:addir9,r2,-32328
   0x100016ac <+24>:li  r10,32
   0x100016b0 <+28>:lxvd2x  vs32,r10,r9
   0x100016b4 <+32>:lxvd2x  vs33,0,r9
   0x100016b8 <+36>:bcdadd. v0,v1,v0,1
   0x100016bc <+40>:li  r10,16
   0x100016c0 <+44>:stxvd2x vs32,r9,r10
   0x100016c4 <+48>:b   0x100016e8 
   0x100016c8 <+52>:nop
   0x100016cc <+56>:addir9,r2,-32328
   0x100016d0 <+60>:li  r10,32
   0x100016d4 <+64>:lxvd2x  vs32,r10,r9
=> 0x100016d8 <+68>:lxvd2x  vs33,0,r9
   0x100016dc <+72>:bcdadd. v0,v1,v0,0
   0x100016e0 <+76>:li  r10,16
   0x100016e4 <+80>:stxvd2x vs32,r9,r10
   0x100016e8 <+84>:blr
   0x100016ec <+88>:.long 0x0
   0x100016f0 <+92>:.long 0x0
   0x100016f4 <+96>:.long 0x0
End of assembler dump.

(gdb) info reg r10
r100x10001958268441944
(gdb) info reg r9
r9 0x10020f40268570432
(gdb) info reg vs32
vs32   {uint128 = 0x6090180378642006002244669113354d, v2_double =
{0x, 0x0}, v4_float = {
0x, 0x, 0x0, 0x0}, v4_int32 = {0x60901803, 0x78642006,
0x224466, 0x9113354d}, v8_int16 = {
0x6090, 0x1803, 0x7864, 0x2006, 0x22, 0x4466, 0x9113, 0x354d}, v16_int8 =
{0x60, 0x90, 0x18, 0x3, 0x78, 
0x64, 0x20, 0x6, 0x0, 0x22, 0x44, 0x66, 0x91, 0x13, 0x35, 0x4d}}
(gdb) info reg vs33
vs33   {uint128 = 0x8045090189321003001122334556677d, v2_double = {0x0,
0x0}, v4_float = {0x0, 0x0, 0x0, 
0xd66}, v4_int32 = {0x80450901, 0x89321003, 0x112233, 0x4556677d}, v8_int16
= {0x8045, 0x901, 0x8932, 
0x1003, 0x11, 0x2233, 0x4556, 0x677d}, v16_int8 = {0x80, 0x45, 0x9, 0x1,
0x89, 0x32, 0x10, 0x3, 0x0, 0x11, 
0x22, 0x33, 0x45, 0x56, 0x67, 0x7d}}
(gdb)

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

[valgrind] [Bug 368416] Add tc06_two_races_xml.exp output for ppc64.

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

--- Comment #3 from Will Schmidt  ---
Created attachment 101061
  --> https://bugs.kde.org/attachment.cgi?id=101061=edit
updated and refactored patch

Per feedback and commentary, this is a different approach to solving the
problem...

Update and modify the filter_xml filter to strip out the troublesome frame. 
And a tweak to the same to suppress the blurb that typically indicates a frame
has been skipped.
Appears to work OK across the systems I have access to.  (a mix of ppc64 and a
couple x86 boxes).

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

[valgrind] [Bug 368412] False positive result for altivec capability check

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

--- Comment #4 from Will Schmidt  ---
Created attachment 101056
  --> https://bugs.kde.org/attachment.cgi?id=101056=edit
updated patch

Refreshed the patch per comments and feedback.

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

[valgrind] [Bug 368412] False positive result for altivec capability check

[Will Schmidt via KDE Bugzilla]

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

--- Comment #5 from Will Schmidt  ---
(In reply to Mark Wielaard from comment #3)
> You are changing the AC_DEFINE from HAS_ALTIVEC to COMPILER_SUPPORTS_ALTIVEC.
> But COMPILER_SUPPORTS_ALTIVEC is never used as C preprocessor symbol, so I
> think you should just remove it.

Yup, agreed, done.Thanks for the review.

> HAS_ALTIVEC is used as an C preprocessor symbol in
> none/tests/ppc32/jm-insns.c but there it is defined in the Makefile
> depending on the AM_CONDITIONAL HAS_ALTIVEC. So that should be fine

Yup, ..  I had added the AM_CONDITIONAL way back in 15424, but I obviously
missed removing the old definition, which caused the problem..

> (although the comment in the code implies it comes from config.h, which
> isn't true anymore).

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

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

[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

[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

[valgrind] [Bug 365912] ppc64BE segfault during jm-insns test (RELRO)

[Will Schmidt via KDE Bugzilla]

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

--- Comment #1 from Will Schmidt  ---
Created attachment 100217
  --> https://bugs.kde.org/attachment.cgi?id=100217=edit
proposed patch

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

[valgrind] [Bug 365912] ppc64BE segfault during jm-insns test (RELRO)

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||c...@us.ibm.com,
   ||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 365912] New: ppc64BE segfault during jm-insns test (RELRO)

[Will Schmidt via KDE Bugzilla]

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

Bug ID: 365912
   Summary: ppc64BE segfault during jm-insns test (RELRO)
   Product: valgrind
   Version: 3.12 SVN
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: will_schm...@vnet.ibm.com

When running the valgrind tests, the jm-insns test is segfaulting when it
attempts to patch instructions as it deals with the ppc64 (BE) function
descriptor.  
This is actually due to the RELRO option being enabled by default for the ppc64
(BE) platform, per an upstream binutils change. 
Patch to follow.




Reproducible: Always

Steps to Reproduce:
1.  Build and run valgrind regression test on ppc64 platform with new binutils
installed
2.  specifically run the test  " none/tests/ppc64/jm-insns -f "
3.  see it segfault.

Actual Results:  
...
PPC float load insns
with one register + one 16 bits immediate args with flags update:

Program received signal SIGSEGV, Segmentation fault.
...


Expected Results:  
...
All done. Tested 77 different instructions


Patch to disable the relro option for the jm-insns test to follow momentarily.

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

[valgrind] [Bug 361405] disInstr(ppc): unhandled instruction: 0xFF81010C

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 352364] ppc64: --expensive-definedness-checks=yes is not quite working here

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 345121] helgrind/tests/hg05_race2 fails intermittently

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 330617] ppc false positive conditional jump depends on uninitialised value

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||c...@us.ibm.com,
   ||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 322593] Power 8 code to implement Transactional support

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 276224] VEX implementation for PowerPC fp round instructions is incorrect for SNAN argument

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 243483] ppc: callgrind triggers VEX assertion failure

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 201530] Valgrind does not display debug information about stack variables on powerpc-linux

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 145480] [PATCH] POWER5+/POWER6 instructions: frip, frin, friz, frim, cmpb, mftgpr, mffgpr

[Will Schmidt via KDE Bugzilla]

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

--- Comment #4 from Will Schmidt  ---
Looks like the associated patches for this bug went into valgrind as 
"r11338 | sewardj | 2010-09-03 18:49:33 -0500 (Fri, 03 Sep 2010) | 4 lines"..  
should be able to mark this one out as "resolved".

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

[valgrind] [Bug 145480] [PATCH] POWER5+/POWER6 instructions: frip, frin, friz, frim, cmpb, mftgpr, mffgpr

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 109426] ppc: false positive in rt_sigaction

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 362894] missing (broken) support for wbit field on mtfsfi instruction (ppc64)

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 Status|VERIFIED|CLOSED

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

[valgrind] [Bug 362894] missing (broken) support for wbit field on mtfsfi instruction (ppc64)

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #4 from Will Schmidt  ---
tested with a clean upstream valgrind/vex tree, looks good. 
Thanks, 
-Will

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

[valgrind] [Bug 362894] missing (broken) support for wbit field on mtfsfi instruction (ppc64)

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||c...@us.ibm.com

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

[kdelibs] [Bug 363431] kontact crashes when closing

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #4 from Herr Schmidt  ---
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  ---
> 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

[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

[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.

[valgrind] [Bug 362894] missing (broken) support for wbit field on mtfsfi instruction (ppc64)

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

--- Comment #1 from Will Schmidt  ---
Created attachment 98878
  --> https://bugs.kde.org/attachment.cgi?id=98878=edit
proposed patch

Proposed patch.  tested locally with success.

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

[valgrind] [Bug 362894] New: missing (broken) support for wbit field on mtfsfi instruction (ppc64)

[Will Schmidt via KDE Bugzilla]

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

Bug ID: 362894
   Summary: missing (broken) support for wbit field on mtfsfi
instruction (ppc64)
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: will_schm...@vnet.ibm.com

(ppc64)
Support for the mtfsfi instruction when the Wbit is non-zero is failing.

Test -
int main()
{
asm ("mtfsfi 7,0,1");
return 0;
}

$ valgrind ./test
<...>
==64881== 
dis_fp_scr(ppc)(instr,mtfsfi)
disInstr(ppc): unhandled instruction: 0xFF81010C
 primary 63(0x3F), secondary 268(0x10C)
dis_fp_scr(ppc)(instr,mtfsfi)
disInstr(ppc): unhandled instruction: 0xFF81010C
 primary 63(0x3F), secondary 268(0x10C)
dis_fp_scr(ppc)(instr,mtfsfi)
disInstr(ppc): unhandled instruction: 0xFF81010C
 primary 63(0x3F), secondary 268(0x10C)



Reproducible: Always

Steps to Reproduce:
1.  Compile simple test containing "mtfsfi   7,0,1 ".
2.  Run under valgrind.
3.

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

[valgrind] [Bug 362329] Valgrind does not support the IBM POWER ISA 3.0 instructions, part 3

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

-- 
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

[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)

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #1 from Herr Schmidt  ---
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)

[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

[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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #6 from Herr Schmidt  ---
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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #1 from Herr Schmidt  ---
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

[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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #5 from Herr Schmidt  ---
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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #4 from Herr Schmidt  ---
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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #3 from Herr Schmidt  ---
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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #2 from Herr Schmidt  ---
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

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #1 from Herr Schmidt  ---
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

[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

[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 ?? () 

[systemsettings] [Bug 362601] New: Information about your System

[Roland Schmidt via KDE Bugzilla]

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

Bug ID: 362601
   Summary: Information about your System
   Product: systemsettings
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: roland-schmid...@gmx.de

If i try to install or choose a display driver, there are no drivers list and i
cant use open gl because my display driver is not set properly.
I Use a Aspire V5-552g with Radeon Dual graphics hd 8750m.

Please Help

Reproducible: Always

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

[paste.kde.org] [Bug 362188] resize

[Mathias Schmidt via KDE Bugzilla]

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

--- Comment #1 from Mathias Schmidt  ---
It is regarding the sticky notes from widgets that you can add to the desktop.

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

[paste.kde.org] [Bug 362188] resize

[Mathias Schmidt via KDE Bugzilla]

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

Mathias Schmidt  changed:

   What|Removed |Added

Product|knotes  |paste.kde.org
  Component|general |general

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

[knotes] [Bug 362188] resize

[Mathias Schmidt via KDE Bugzilla]

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

Mathias Schmidt  changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages

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

[knotes] [Bug 362188] New: resize

[Mathias Schmidt via KDE Bugzilla]

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

Bug ID: 362188
   Summary: resize
   Product: knotes
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdebugu...@gmail.com
CC: myr...@kde.org

It would be nice if you could resize them.

Reproducible: Always

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

[Discover] [Bug 362087] Will send you one step back

[Mathias Schmidt via KDE Bugzilla]

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

Mathias Schmidt  changed:

   What|Removed |Added

   Severity|normal  |minor

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

[Discover] [Bug 362087] New: Will send you one step back

[Mathias Schmidt via KDE Bugzilla]

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

Bug ID: 362087
   Summary: Will send you one step back
   Product: Discover
   Version: 5.6.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: kdebugu...@gmail.com

If you go in to a category and uses the search field type in 1 charter then
delete it with back space or the delete button it will send you one step back
ex. if you are in the comics category you will be sent back to the start
window, the same will happen in you are clicking on configure shortcuts, about
discover or report bug.

Reproducible: Always

Steps to Reproduce:
1. go into a category 
2a. click the search field enter 1 charter 
2b. then press backspace to delete it 
3a. click on the menu in the right top conner 
3b. click on ether configure shortcuts, about discover or report bug

Actual Results:  
it will send you one step back

Expected Results:  
should have stayed in the category.

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

[Discover] [Bug 362059] Text not contained

[Mathias Schmidt via KDE Bugzilla]

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

Mathias Schmidt  changed:

   What|Removed |Added

Summary|Text not contain|Text not contained

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

[systemsettings] [Bug 361974] New: Power saving settings for monitor have no effect

[Guido Schmidt via KDE Bugzilla]

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

Bug ID: 361974
   Summary: Power saving settings for monitor have no effect
   Product: systemsettings
   Version: 5.6.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: gu...@sanguepreto.de

This is a desktop PC with OpenSUSE 13.2 (x86_64).

Since KDE 5.6 my monitor turns off (I guess an energy saving mode) after a
couple of minutes even though I have this setting disabled in systemsettings5
like I always had. (I would give you the exact name of this setting but even
though I set System Settings to run in english it shows most words in my german
- maybe another bug. The german name is: Energiesparmodus - Bildschirm
abdunkeln)

This does not happen when I am logged into an XFCE session.
BTW this is the only session on this machine.

I tried changing the setting by enabling it and setting the time-out to 1
minute. This also does not have any effect.

So it looks like KDE is not reading/finding the setting and using a default?

Reproducible: Always

Steps to Reproduce:
1. Login to a KDE 5 session.
2. Make sure the energy/power setting for turning off the moniter after a
configurable time is turned off.
3. Wait a little, i.e. watch a movie in full screen mode.

Actual Results:  
Screen turns black and monitor LED indicates a power saving mode.

Expected Results:  
Screens stays on.

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

[valgrind] [Bug 361207] Valgrind does not support the IBM POWER ISA 3.0 instructions, part 2

[Will Schmidt via KDE Bugzilla]

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

Will Schmidt  changed:

   What|Removed |Added

 CC||will_schm...@vnet.ibm.com

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

[valgrind] [Bug 358569] New: Unhandled instructions cause creation of "orphan" stack traces in XML output

[Adriaan Schmidt via KDE Bugzilla]

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

Bug ID: 358569
   Summary: Unhandled instructions cause creation of "orphan"
stack traces in XML output
   Product: valgrind
   Version: 3.11.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: adriaan.schmidt.siem...@gmail.com

When encountering unhandled instructions, Valgrind will provide a warning/error
message and a stack trace.
When running with --xml=yes, the warning will still appear in the console
output, but the stack trace will go to the XML.



Reproducible: Always

Steps to Reproduce:
Run:
valgrind --tool= --xml=yes --xml-file=out.xml /program/with/unhandled/insn

In my case, I run Helgrind on ARM, on a binary that uses libcrypto and thus
runs into bug 331178.

Actual Results:  
Running:
valgrind --tool=helgrind --xml=yes --xml-file=out.xml /my/program

I see on my console:
disInstr(arm): unhandled instruction: 0xEE190F1D
 cond=14(0xE) 27:20=225(0xE1) 4:4=1 3:0=13(0xD)
==909== valgrind: Unrecognised instruction at address 0x4d1cbf68.
==909== Your program just tried to execute an instruction that Valgrind
==909== did not recognise.  There are two possible reasons for this.
==909== 1. Your program has a bug and erroneously jumped to a non-code
==909==location.  If you are running Memcheck and you just saw a
==909==warning about a bad jump, it's probably your program's fault.
==909== 2. The instruction is legitimate but Valgrind doesn't handle it,
==909==i.e. it's Valgrind's fault.  If you think this is the case or
==909==you are not sure, please let us know and we'll try to fix it.
==909== Either way, Valgrind will now raise a SIGILL signal which will
==909== probably kill your program.

My XML output starts with:




4
helgrind


  Helgrind, a thread error detector
  Copyright (C) 2007-2015, and GNU GPL'd, by OpenWorks LLP et al.
  Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright
info
  Command: /my/program


909
907
helgrind


  
/usr/local/bin/valgrind
--tool=helgrind
--xml=yes
--xml-file=out.xml
  
  
/my/program
  



  RUNNING
  00:00:01:35.229 


  

  0x4D1CBF68
  /lib/libcrypto.so.1.0.0

  

  1
  



Expected Results:  
I would suggest that the stack trace be sent to console in this case.

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