https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #28 from JordanL ---
I can't reproduce it (since returning to Plasma Wayland with 5.22.5), however I
did replace my monitors with new ones which have far fewer issues with this
sort of thing than my previous ones.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=374908
JordanL changed:
What|Removed |Added
CC|jordanlepp...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=443545
JordanL changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk
Component|Panel
https://bugs.kde.org/show_bug.cgi?id=443545
--- Comment #1 from JordanL ---
Created attachment 142296
--> https://bugs.kde.org/attachment.cgi?id=142296=edit
When there are only 18 bars
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443545
Bug ID: 443545
Summary: System monitor Sensor can't show more than 18 bars.
Product: plasmashell
Version: 5.22.5
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=370180
JordanL changed:
What|Removed |Added
CC|jordanlepp...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=422426
JordanL changed:
What|Removed |Added
CC|jordanlepp...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=422426
JordanL changed:
What|Removed |Added
CC||jordanlepp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=370180
--- Comment #13 from JordanL ---
I'm not experiencing it on reboot. Only when the screens turn off and back on.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377561
--- Comment #12 from JordanL ---
More relevant info: I have two 4k monitors connected with DisplayPort 1.2.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377561
--- Comment #11 from JordanL ---
For me though, the panels aren't so much switched, but both screens show the
window list for the right hand desktop (I have the window list setup to show
windows on the current screen). Both my panels are identical so I
https://bugs.kde.org/show_bug.cgi?id=377561
--- Comment #10 from JordanL ---
Yes, this is happening with:
Plasma 5.16.5
KDE Frameworks 5.62.0
Qt 5.13.1
I'm using an AMD Vega 64 GPU and running Arch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373907
JordanL changed:
What|Removed |Added
CC||jordanlepp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=404152
--- Comment #10 from JordanL ---
Certainly not enough to provide a competent review of Kwin code unfortunately.
I've checked out the Kwin repo anyway to see if I might familiarise myself with
it enough to offer patches for some issues I can reproduce
https://bugs.kde.org/show_bug.cgi?id=404152
--- Comment #7 from JordanL ---
I understand it's important for problems to be fixed properly rather than
hastily, and I don't want to sound impatient, but is it normal for a fix like
this to be under review for nearly two months? Having buggy
https://bugs.kde.org/show_bug.cgi?id=404152
JordanL changed:
What|Removed |Added
CC||jordanlepp...@gmail.com
--- Comment #5 from JordanL
https://bugs.kde.org/show_bug.cgi?id=402827
JordanL changed:
What|Removed |Added
Version|5.14.4 |5.15.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #20 from JordanL ---
Just retested on Arch with Plasma 5.15.0, KDE frameworks 5.55.0, Qt 5.12.1,
same hardware as before.
Bug is still present, when monitors turn off due to power saving. kwin_wayland
dumps core.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #18 from JordanL ---
Well that's progress at least, I might be able to use the Wayland session full
time if so. Could you get the backtrace from the segfault when you turn the
monitor off? In case it's different?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #14 from JordanL ---
"svn patch" would't play ball, so I manually applied the patch to 5.14.4 and
rebuilt. The issue still occurs. The backtrace is different though, so I think
this is progress. The backtrace differs from #8 onwa
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #13 from JordanL ---
I'll attempt to test this patch, any info you can point me to to help me
rebuild kwin with it? Worst case I could manually apply the changes in the src
and rebuild but I'm sure there's a quicker way!
--
You
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #9 from JordanL ---
Attached a new log, "Log of all threads before raise is called".
This is a backtrace of all kwin threads at the point it called raise(). I
believe thread 1 is the thread that is relevant here:
Thread
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #8 from JordanL ---
Created attachment 117283
--> https://bugs.kde.org/attachment.cgi?id=117283=edit
Log of all threads before raise is called
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #7 from JordanL ---
Debugger log after rebuilding glibc with debug:
Continuing.
[Detaching after fork from child process 1548]
Thread 1 "kwin_wayland" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #6 from JordanL ---
I worked out how to attach the debugger while kwin_wayland is still running. It
throws SIGABRT when calling raise() in /usr/lib/libc.so.6 - so I will now
rebuild glibc with debug symbols and see if that gets me anywhere
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #5 from JordanL ---
Created attachment 117281
--> https://bugs.kde.org/attachment.cgi?id=117281=edit
New log after rebuilding kwin and mesa with debug symbols
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #4 from JordanL ---
Sorry, even after installing kwin and mesa built with debug symbols, I get no
backtrace and have no idea where to go next. I've attached the latest log I get
(log4.txt).
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #3 from JordanL ---
Seems I also need to rebuild kwin with debug symbols (makes sense!). Think I'm
close to having the backtrace now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402827
--- Comment #2 from JordanL ---
Any idea which (if any) packages I need to rebuild with debug symbols? It looks
like I need to rebuild mesa but I'm not 100% sure.
$ pacman -Qo /usr/lib/libgbm.so.1.0.0
/usr/lib/libgbm.so.1.0.0 is owned by mesa 18.3.1-1
https://bugs.kde.org/show_bug.cgi?id=402827
Bug ID: 402827
Summary: kwin_wayland segfault on monitor wakeup
Product: kwin
Version: 5.14.4
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: major
https://bugs.kde.org/show_bug.cgi?id=400058
--- Comment #7 from JordanL ---
I too can confirm the issue is fixed since the second batch of Qt updates.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400058
--- Comment #2 from JordanL ---
My issue also started today, after the update of Qt to 5.11.2. It happens
whether the Plasma or the Plasma Wayland session is selected. I was going to
file a bug for SDDM, but couldn't find it (is it not a KDE project
https://bugs.kde.org/show_bug.cgi?id=400058
JordanL changed:
What|Removed |Added
CC||jordanlepp...@gmail.com
--- Comment #1 from JordanL
https://bugs.kde.org/show_bug.cgi?id=399564
--- Comment #8 from JordanL ---
5.13.* was the first release I tried Wayland in, so this bug might have been
around long before that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399564
--- Comment #7 from JordanL ---
Should have mentioned, this bug was also present in 5.13.*.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399564
--- Comment #3 from JordanL ---
(gdb) continue
Continuing.
[Thread 0x7fc9a17fa700 (LWP 5989) exited]
[Thread 0x7fc9a1ffb700 (LWP 5665) exited]
[Thread 0x7fc9a27fc700 (LWP 5664) exited]
[Thread 0x7fc9a2ffd700 (LWP 5663) exited]
[Thread 0x7fc9a37fe700
https://bugs.kde.org/show_bug.cgi?id=399564
--- Comment #1 from JordanL ---
CORRECTION
The system info I posted above was back in the Xorg session, this is the output
of inxi -Fxz while using Wayland:
System:Host: rupert Kernel: 4.15.0-36-generic x86_64 bits: 64 gcc: 7.3.0
https://bugs.kde.org/show_bug.cgi?id=399564
Bug ID: 399564
Summary: kwin_wayland segfault on monitor wakeup
Product: kwin
Version: 5.14.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=394532
--- Comment #3 from JordanL ---
In Plasma 5.13.5 the central bug of this ticket still occurs: The window list
of one screen will sometimes list the windows for the other screen after the
screens come back on after powersaving. Right now, it's the left
https://bugs.kde.org/show_bug.cgi?id=394532
--- Comment #2 from JordanL <jordanlepp...@gmail.com> ---
I've discovered it's only maximised windows that get moved to the left screen.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377561
--- Comment #7 from JordanL <jordanlepp...@gmail.com> ---
Thanks, NVidia GPUs seem to be a common element (I mean, they're pretty popular
obviously but even so).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374908
--- Comment #6 from JordanL <jordanlepp...@gmail.com> ---
Do you remember if it was an NVidia GPU? That seems to be a very common
element.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=394532
--- Comment #1 from JordanL <jordanlepp...@gmail.com> ---
This seems to be "fixed" if I make the left-hand monitor the primary screen.
The right-hand task manager now lists the correct tasks after screens are
switched back on, and c
43 matches
Mail list logo
