[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-11-22 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405609

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #14 from Nate Graham  ---


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

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-11-20 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=405609

--- Comment #13 from Matt Fagnani  ---
Created attachment 124037
  --> https://bugs.kde.org/attachment.cgi?id=124037&action=edit
valgrind log file for system settings segmentation fault

I ran valgrind --log-file=valgrind-systemsettings5-2.txt systemsettings5 &
I reproduced the crash in the same way as in my previous comment. The valgrind
log showed an invalid read in wl_proxy_unref at wayland-client.c:229 and an
invalid write in wl_proxy_unref at wayland-client.c:230 in libwayland-client.
They appeared to be use-after-free errors like those I've previously reported
for kwin_wayland, plasmashell, konsole, powerdevil, etc. (
https://bugs.kde.org/show_bug.cgi?id=409688 ) Several Conditional jump or move
depends on uninitialised value(s) messages were shown. An invalid read at in
load at atomic_base.h:740 of the address 0xb was shown which had a similar
trace similar to that of the crashing threads.

==4968== Invalid read of size 8
==4968==at 0x5D136AA: load (atomic_base.h:740)
==4968==by 0x5D136AA: load (atomic:519)
==4968==by 0x5D136AA: load
(qatomic_cxx11.h:227)
==4968==by 0x5D136AA: load (qbasicatomic.h:239)
==4968==by 0x5D136AA:
QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*)
(qsharedpointer.cpp:1358)
==4968==by 0x6ECFCF7: QWeakPointer (qsharedpointer_impl.h:688)
==4968==by 0x6ECFCF7: assign (qsharedpointer_impl.h:684)
==4968==by 0x6ECFCF7: operator= (qpointer.h:83)
==4968==by 0x6ECFCF7:
QQmlListReferencePrivate::init(QQmlListProperty const&, int,
QQmlEngine*) (qqmllist.cpp:64)
==4968==by 0x6EDE064: QV4::QmlListWrapper::toVariant() const
(qqmllistwrapper.cpp:101)
==4968==by 0x6E20603: toVariant(QV4::ExecutionEngine*, QV4::Value const&,
int, bool, QSet*) (qv4engine.cpp:1306)
==4968==by 0x6E20A68: QV4::ExecutionEngine::toVariant(QV4::Value const&,
int, bool) (qv4engine.cpp:1271)
==4968==by 0x6ED8B24: QQmlBinding::slowWrite(QQmlPropertyData const&,
QQmlPropertyData const&, QV4::Value const&, bool,
QFlags) (qqmlbinding.cpp:415)
==4968==by 0x6EDA8F2: GenericBinding<2>::write(QV4::Value const&, bool,
QFlags) (qqmlbinding.cpp:325)
==4968==by 0x6EDB53F:
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) (qqmlbinding.cpp:249)
==4968==by 0x6ED7C93:
QQmlBinding::update(QFlags) (qqmlbinding.cpp:185)
==4968==by 0x6EE6825:
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&)
(qqmlobjectcreator.cpp:1352)
==4968==by 0x6E65F80: complete (qqmlcomponent.cpp:935)
==4968==by 0x6E65F80: QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) (qqmlcomponent.cpp:931)
==4968==by 0x6E66091: completeCreate (qqmlcomponent.cpp:971)
==4968==by 0x6E66091: QQmlComponentPrivate::completeCreate()
(qqmlcomponent.cpp:966)
==4968==  Address 0xb is not stack'd, malloc'd or (recently) free'd
==4968== 

This crash might be due to an invalid pointer from the earlier use-after-free
errors and use of uninitialized variables. Two further invalid reads were shown
in socketNotifierSourceCheck at qeventdispatcher_glib.cpp:88 which look like
use-after-free errors. Those errors might be side-effects of the segmentation
fault. I've seen this crash 9 times which is about half the times I've tried to
reproduce it. I'm attaching the full valgrind log.

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-11-17 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=405609

Matt Fagnani  changed:

   What|Removed |Added

 CC||matthew.fagn...@utoronto.ca

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-11-05 Thread DSZ
https://bugs.kde.org/show_bug.cgi?id=405609

DSZ  changed:

   What|Removed |Added

 CC||oz.jam@gmail.com

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-11-05 Thread DSZ
https://bugs.kde.org/show_bug.cgi?id=405609

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

systemsettings5 (5.12.8) using Qt 5.9.7

- What I was doing when the application crashed:

After a fresh install of opensuse leap 15.1, I was quickly going through
settings, when clicking application style the system settings crashed.

-- Backtrace (Reduced):
#6  std::__atomic_base::load
(__m=std::memory_order_relaxed, this=) at
/usr/include/c++/7/bits/atomic_base.h:713
#7  std::atomic::load
(__m=std::memory_order_relaxed, this=) at
/usr/include/c++/7/atomic:452
#8 
QAtomicOps::load
(_q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:227
#9  QBasicAtomicPointer::load
(this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:238
#10 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x3) at
tools/qsharedpointer.cpp:1445

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-11-02 Thread Abner Carvalho
https://bugs.kde.org/show_bug.cgi?id=405609

Abner Carvalho  changed:

   What|Removed |Added

 CC||abnercarvalhocosta@hotmail.
   ||com

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-11-02 Thread Abner Carvalho
https://bugs.kde.org/show_bug.cgi?id=405609

--- Comment #10 from Abner Carvalho  ---
Created attachment 123675
  --> https://bugs.kde.org/attachment.cgi?id=123675&action=edit
New crash information added by DrKonqi

systemsettings5 (5.17.2) using Qt 5.13.1

When I was changing on window management the settings application closed.

-- Backtrace (Reduced):
#6  std::__atomic_base::load
(__m=std::memory_order_relaxed, this=) at
/usr/include/c++/7/bits/atomic_base.h:713
#7  std::atomic::load
(__m=std::memory_order_relaxed, this=) at
/usr/include/c++/7/atomic:452
#8 
QAtomicOps::load
(_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
#9  QBasicAtomicPointer::load
(this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:239
#10 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x3) at
tools/qsharedpointer.cpp:1347

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-10-20 Thread Carla Pérez
https://bugs.kde.org/show_bug.cgi?id=405609

Carla Pérez  changed:

   What|Removed |Added

 CC||carla.pm...@gmail.com

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-09-21 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=405609

--- Comment #8 from Patrick Silva  ---
Sometimes I can reproduce this crash on Plasma 5.17 beta (on Wayland session),
but the backtrace looks different.

Operating System: Arch Linux 
KDE Plasma Version: 5.16.90
KDE Frameworks Version: 5.62.0
Qt Version: 5.13.1
Kernel Version: 5.3.0-arch1-1-ARCH

open system settings > desktop behavior > desktop effects
click on "All settings" on top left corner
open "Application style"

if system settings did not crash, close it and repeat the steps above.
At some point probably it will crash.

Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3847625800 (LWP 8230))]

Thread 5 (Thread 0x7f38277bf700 (LWP 8257)):
#0  0x7f384c2fd686 in __libc_disable_asynccancel () at /usr/lib/libc.so.6
#1  0x7f384c2e567b in poll () at /usr/lib/libc.so.6
#2  0x7f3848690130 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f381c00a080, timeout=, context=0x7f381c002540)
at ../glib/glib/gmain.c:4216
#3  0x7f3848690130 in g_main_context_iterate
(context=context@entry=0x7f381c002540, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3912
#4  0x7f3848690201 in g_main_context_iteration (context=0x7f381c002540,
may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978
#5  0x7f384c889a1c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f381c005070, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f384c8304ec in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f38277bed80, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7f384c662385 in QThread::exec() (this=this@entry=0x55613cfb9d10) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7f384b96d849 in QQmlThreadPrivate::run() (this=0x55613cfb9d10) at
/tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.13.1/src/qml/qml/ftw/qqmlthread.cpp:152
#9  0x7f384c6635b0 in QThreadPrivate::start(void*) (arg=0x55613cfb9d10) at
thread/qthread_unix.cpp:360
#10 0x7f384aec457f in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f384c2f00e3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f38369dc700 (LWP 8234)):
#0  0x7f384c2e118c in read () at /usr/lib/libc.so.6
#1  0x7f38486409f0 in read (__nbytes=16, __buf=0x7f38369dbb60,
__fd=, __fd=, __buf=,
__nbytes=) at /usr/include/bits/unistd.h:44
#2  0x7f38486409f0 in g_wakeup_acknowledge (wakeup=0x7f3840003db0) at
../glib/glib/gwakeup.c:210
#3  0x7f384868e9f1 in g_main_context_check
(context=context@entry=0x7f383bf0, max_priority=2147483647,
fds=fds@entry=0x7f3830004e30, n_fds=n_fds@entry=1) at ../glib/glib/gmain.c:3695
#4  0x7f38486900d8 in g_main_context_iterate
(context=context@entry=0x7f383bf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3914
#5  0x7f3848690201 in g_main_context_iteration (context=0x7f383bf0,
may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978
#6  0x7f384c889a1c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f383b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f384c8304ec in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f38369dbd80, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#8  0x7f384c662385 in QThread::exec() (this=this@entry=0x55613738a1b0) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#9  0x7f384b96d849 in QQmlThreadPrivate::run() (this=0x55613738a1b0) at
/tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.13.1/src/qml/qml/ftw/qqmlthread.cpp:152
#10 0x7f384c6635b0 in QThreadPrivate::start(void*) (arg=0x55613738a1b0) at
thread/qthread_unix.cpp:360
#11 0x7f384aec457f in start_thread () at /usr/lib/libpthread.so.0
#12 0x7f384c2f00e3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f3844913700 (LWP 8233)):
#0  0x7f384aeca415 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f383f57bf5c in  () at /usr/lib/dri/i965_dri.so
#2  0x7f383f57bb58 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f384aec457f in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f384c2f00e3 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f384639e700 (LWP 8232)):
#0  0x7f384c2e5667 in poll () at /usr/lib/libc.so.6
#1  0x7f3848690130 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f3840005260, timeout=, context=0x7f384bf0)
at ../glib/glib/gmain.c:4216
#2  0x7f3848690130 in g_main_context_iterate
(context=context@entry=0x7f384bf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3912
#3  0x7f3848690201 in g_main_context_iteration (context=0x7f384bf0,
may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978
#4  0x7f384c889a1c in
QEventDispatcherGlib::processEvents(QFlags)
(th

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-09-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=405609

Christoph Feck  changed:

   What|Removed |Added

 CC||makrat...@gmail.com

--- Comment #7 from Christoph Feck  ---
*** Bug 411499 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-09-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=405609

--- Comment #6 from Christoph Feck  ---
Patrick, now it happened (at least) twice. Maybe you can see a pattern, but it
always involves the window decorations page.

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-09-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=405609

--- Comment #5 from Christoph Feck  ---
*** Bug 411434 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-09-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=405609

Christoph Feck  changed:

   What|Removed |Added

 CC||sts33n...@gmail.com

--- Comment #4 from Christoph Feck  ---
*** Bug 411376 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-04-22 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=405609

--- Comment #3 from Patrick Silva  ---
The crash is not reproducible, it happened just once.
I only have the default themes breeze, oxygen and plastik.

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-04-21 Thread Vlad Zagorodniy
https://bugs.kde.org/show_bug.cgi?id=405609

--- Comment #2 from Vlad Zagorodniy  ---
Cannot reproduce. What themes do you have installed?

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

[kwin] [Bug 405609] System settings crashed when I opened "Application style"

2019-03-31 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=405609

Christoph Feck  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
Product|systemsettings  |kwin
Version|unspecified |git master
  Component|general |aurorae

--- Comment #1 from Christoph Feck  ---
Crash is caused by Aurorae decoration engine, which uses QtQuick.

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