[kde] [Bug 427993] Multiple System components/processes crash when unplugging an external monitor

2020-10-19 Thread Tom Magowan
https://bugs.kde.org/show_bug.cgi?id=427993

Tom Magowan  changed:

   What|Removed |Added

 CC||tom.mago...@gmail.com

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-17 Thread Tom Magowan
https://bugs.kde.org/show_bug.cgi?id=424834

--- Comment #8 from Tom Magowan  ---
I get a similar segfault, but after updating my kde neon distribution to focal
20.04:

kwin_wayland[11167]: segfault at 0 ip 7f0bf495d3cb sp 7fff42c83408
error 4 in libwayland-server.so.0.1.0[7f0bf4958000+8000]

Seems to be affecting a few other users:
https://www.reddit.com/r/kdeneon/comments/i480oq/segmentation_fault_at_plasma_wayland_session/

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-17 Thread Tom Magowan
https://bugs.kde.org/show_bug.cgi?id=424834

Tom Magowan  changed:

   What|Removed |Added

 CC||tom.mago...@gmail.com

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

[plasmashell] [Bug 395706] Dual monitor + wayland crash

2018-06-25 Thread Tom Magowan
https://bugs.kde.org/show_bug.cgi?id=395706

--- Comment #3 from Tom Magowan  ---
Apologies for the lack of debug symbols, DrKonqi implied they had been
installed.

Unfortunately I cannot reproduce the exact same crash (the problem manifests
itself slightly differently every time I log in). However I did manage to find
the root cause of the issue, which I believe to be a problematic kscreen
configuration. If I delete the directory ~/.local/share/kscreen I can log in
fine, and the plasma wayland session is created successfully.

I've attached the unstable kscreen config to this bug report, just in case it
helps.

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

[plasmashell] [Bug 395706] Dual monitor + wayland crash

2018-06-25 Thread Tom Magowan
https://bugs.kde.org/show_bug.cgi?id=395706

--- Comment #2 from Tom Magowan  ---
Created attachment 113563
  --> https://bugs.kde.org/attachment.cgi?id=113563&action=edit
unstable config from ~/.local/share/kscreen

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

[plasmashell] [Bug 395706] New: Dual monitor + wayland crash

2018-06-21 Thread Tom Magowan
https://bugs.kde.org/show_bug.cgi?id=395706

Bug ID: 395706
   Summary: Dual monitor + wayland crash
   Product: plasmashell
   Version: 5.13.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: tom.mago...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.13.1)

Qt Version: 5.11.0
Frameworks Version: 5.47.0
Operating System: Linux 4.13.0-45-generic x86_64
Distribution: KDE neon User Edition 5.13

-- Information about the crash:
System: Dell XPS laptop with connected external monitor.

- What I was doing when the application crashed:
Log in to kde using plasma wayland session.
After a few seconds the laptop display freezes, but the external monitor loads
the kde desktop.
The System Compositor dialog is launched.
Crash report icon displayed in system tray (used to generate this bug report).
The system display dialog reports the laptop monitor as disabled, the external
monitor as enabled.

This crash also happens on another Dell XPS laptop of mine. I first noticed the
issue with the release of plasma 5.12 LTS, and it continues to be an issue in
5.13.1

The crash can be reproduced every time.

-- 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 0x7f264a983940 (LWP 24118))]

Thread 6 (Thread 0x7f258bfff700 (LWP 24190)):
#0  0x7f2643b2474d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f263df3c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f263df3c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f264443bbeb in QEventDispatcherGlib::processEvents
(this=0x7f25840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f26443e31ca in QEventLoop::exec (this=this@entry=0x7f258bffec00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f26442185e4 in QThread::exec (this=) at
thread/qthread.cpp:522
#6  0x7f26481dce66 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f2644223727 in QThreadPrivate::start (arg=0x1bfe140) at
thread/qthread_unix.cpp:367
#8  0x7f26430c86ba in start_thread (arg=0x7f258bfff700) at
pthread_create.c:333
#9  0x7f2643b3041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f259a2a3700 (LWP 24188)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f26442245cb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x19d71e0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x19d5440,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f264825cafd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f264825cf81 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f2644223727 in QThreadPrivate::start (arg=0x19d53c0) at
thread/qthread_unix.cpp:367
#6  0x7f26430c86ba in start_thread (arg=0x7f259a2a3700) at
pthread_create.c:333
#7  0x7f2643b3041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f262b7cf700 (LWP 24178)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f264a0f0e04 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f264a0f0e49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f26430c86ba in start_thread (arg=0x7f262b7cf700) at
pthread_create.c:333
#4  0x7f2643b3041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f2631e71700 (LWP 24160)):
#0  0x7f2643b2474d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f263df3c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f263df3c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f264443bbeb in QEventDispatcherGlib::processEvents
(this=0x7f26240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f26443e31ca in QEventLoop::exec (this=this@entry=0x7f2631e70c50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f26442185e4 in QThread::exec (this=) at
thread/qthread.cpp:522
#6  0x7f2647d52cf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f2644223727 in QThreadPrivate::start (arg=0x102e5d0) at
thread/qthread_unix.cpp:367
#8  0x7f26430c86ba in start_thread (arg=0x7f2631e71700) at
pthread_create.c:333
#9  0x7f2643b3041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f26338a7700 (LWP 24147)):
#0  0x7f2643b2474d in poll () at ../sysdeps/unix/syscall-template.S:84
#1

[kwin] [Bug 389551] kwin_wayland crash when monitor is switched off (or input is changed)

2018-02-26 Thread Tom Magowan
https://bugs.kde.org/show_bug.cgi?id=389551

Tom Magowan  changed:

   What|Removed |Added

 CC||tom.mago...@gmail.com

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