[kwin] [Bug 457822] client.frameGeometry.width doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=457822 Marcos Gutiérrez Alonso changed: What|Removed |Added OS|Other |Linux CC||margua...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454691] New: On a 4K monitor, the context menus load incorrectly on Wayland
https://bugs.kde.org/show_bug.cgi?id=454691 Bug ID: 454691 Summary: On a 4K monitor, the context menus load incorrectly on Wayland Product: kwin Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: margua...@gmail.com Target Milestone: --- SUMMARY In a 4K monitor, the resolution of the context menus is not correct. When I hover over an item, all other items "crash" (dissappear) and the one I hovered renders at the correct resolution. It's hard to explain so here's a video demonstration: https://youtu.be/drwGeXqMgFA This happens to EVERY right-click context menu on Wayland: in the plasma panel, in the desktop, in the application launcher... everywhere. This does NOT happen on my secondary 1080p monitor. STEPS TO REPRODUCE 1. Enable 4K resolution in wayland 2. Right-click anywhere to bring up a context menu 3. Hover over an element and watch the elements become invisible OBSERVED RESULT 1080p resolution on context menus when they load. EXPECTED RESULT They appear with the appropriate resolution. SOFTWARE/OS VERSIONS OS: Arch Linux x86_64 Kernel: 5.18.1-zen1-1-zen Resolution: 3840x2160 DE: Plasma 5.24.5 WM: kwin Theme: [Plasma], Breeze [GTK2/3] Icons: [Plasma], breeze-dark [GTK2/3] (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION - I'm using the amd gpu drivers. - This text rendering issue (without transparencies) happens in other places too, such as the "About this system" in the system settings. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 453730] Plasma crashed in KIconLoader::setCustomPalette()
https://bugs.kde.org/show_bug.cgi?id=453730 --- Comment #6 from Marcos Gutiérrez Alonso --- (In reply to Nate Graham from comment #4) > If it's not "Breeze Icons", does the crash happen if you switch to "Breeze > Icons"? I have tried it and it does not crash... In fact it does not crash anymore(?) It's hard to say because I don't know *what* made it crash, so I just used it normally and after 3 days it has not crashed once (with "Breeze Icons" nor with the custom ones). I do update my computer regularly, so it might have fixed itself I guess? Anyhow, sorry for making you lose your time. Will add more info to this thread if I happen to find out what crashed plasma or it crashes even with "Breeze Icons". Thank you again! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 453730] Plasma crashed in KIconLoader::setCustomPalette()
https://bugs.kde.org/show_bug.cgi?id=453730 --- Comment #5 from Marcos Gutiérrez Alonso --- (In reply to Nate Graham from comment #4) > Thanks! Looks samey. > > What icon theme are you using? If it's not "Breeze Icons", does the crash > happen if you switch to "Breeze Icons"? Indeed I'm using Relax-Dark-Icons (https://store.kde.org/p/1687609), I will switch to Breeze Dark and comment if/when a crash occurs Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453730] Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=453730
--- Comment #3 from Marcos Gutiérrez Alonso ---
(In reply to Nate Graham from comment #2)
> Unfortunately the backtrace is incomplete and missing debug symbols for the
> following lines that we need to figure out exactly what's going wrong:
>
> > #4 0x7ff30404bbef in () at
> > /usr/lib/qt/plugins/plasma/applets/org.kde.plasma.private.systemtray.so
>
> Could you please install debug symbols for Plasma and the kiconthemes
> framework, reproduce the crash, and attach a new symbolicated backtrace? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
>
> Thanks!
(This is my first time reporting a bug with a backtrace, please be patient)
After installing `debuginfod`, I restarted and got another crash. This time is
not the same error I think.
This is the backtrace (from gdb I run `bt full`):
```
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f110f49534c in __pthread_kill_implementation () from
/usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7f110abb7540 (LWP 46271))]
(gdb)
(gdb) c
The program is not being run.
(gdb) bt full
#0 0x7f110f49534c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#1 0x7f110f4484b8 in raise () at /usr/lib/libc.so.6
#2 0x7f7aa384 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-5.93.0/src/kcrash.cpp:609
data =
{ = {_vptr.MetadataWriter = 0x7f7ad8b8
}, argv = {_M_elems = {0x0, 0x7f7ab0c1
"--platform", 0x55d477e95b98 "wayland", 0x7f7ab0de "--appname",
0x55d475b896f0 "plasmashell", 0x7f7ab0f7 "--apppath", 0x55d475b89630
"/usr/bin", 0x7f7ab104 "--signal", 0x7fffdb1715e6 "11", 0x7f7ab112
"--pid", 0x7fffdb1715f0 "46271", 0x7f7ab118 "--appversion", 0x55d4760df478
"5.24.5", 0x7f7ab125 "--programname", 0x55d4760a76e8 "Plasma",
0x7f7ab133 "--bugaddress", 0x55d4760a81b8 "sub...@bugs.kde.org",
0x7f7ab14e "--startupid", 0x55d4796a4798 "0", 0x7f7ab162 "--restarted",
0x0 }}, argc = 20, m_writer = 0x7fffdb171720}
platformName = {d = 0x55d477e95b80}
about =
argv = 0x7fffdb171618
ini =
{ = {_vptr.MetadataWriter = 0x7f7ad8e8
}, writable = false, fd = 95, iniLine
= {_M_elems = "restarted=true\n\0...@bugs.kde.org\n", '\000' }}
sigtxt = "11\000\000\000\000\000\000\000"
pidtxt = "46271\000\000\000\000\000\000\000\000\000\360?\000\000\000"
startupId = {d = 0x55d4796a4780}
argc =
crashRecursionCounter = 2
#3 0x7f110f448560 in () at /usr/lib/libc.so.6
#4 0x7f11100484d4 in QColor::operator=(QColor const&) () at
/usr/lib/libQt5Gui.so.5
#5 0x7f110f3d9b74 in KIconColors::KIconColors(QPalette const&)
(this=, palette=..., this=, palette=) at /usr/src/debug/kiconthemes-5.93.0/src/kiconcolors.cpp:101
d = 0x55d47984d9c0
#6 0x7f110f3e954b in KIconLoader::setCustomPalette(QPalette const&)
(this=0x7f110f3ff0d0 <(anonymous
namespace)::Q_QGS_globalIconLoader::innerFunction()::holder>, palette=...)
at /usr/src/debug/kiconthemes-5.93.0/src/kiconloader.cpp:1834
#7 0x7f10cc6da27e in QIconSource::pixmap(QSize const&)
(this=0x55d477be87c0, size=...) at
/usr/src/debug/plasma-framework-5.93.0/src/declarativeimports/core/iconitem.cpp:96
result =
#8 0x7f10cc6dff5e in IconItem::loadPixmap() (this=0x55d47700dd50) at
/usr/src/debug/plasma-framework-5.93.0/src/declarativeimports/core/iconitem.cpp:713
size = -619240880
result =
animated =
#9 0x7f3c606d in QQuickWindowPrivate::polishItems()
(this=0x7f10fc001d20) at
/usr/src/debug/qtdeclarative/src/quick/items/qquickwindow.cpp:393
item = 0x55d47700dd50
itemPrivate =
itemsRemaining = 1
polishLoopDetector = {itemsToPolish = ,
numPolishLoopsInSequence = 0}
#10 0x7f37f463 in
QSGThreadedRenderLoop::polishAndSync(QSGThreadedRenderLoop::Window*, bool)
(this=0x55d476866ab0, w=0x55d477118360, inExpose=)
at
/usr/src/debug/qtdeclarative/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1577
window = 0x55d476d77ca0
timer = {t1 = -9223372036854775808, t2 = -9223372036854775808}
polishTime = 0
waitTime = 0
syncTime = 0
profileFrames = false
d =
#11 0x7f3d1784 in QQuickWindow::event(QEvent*) (this=0x55d476d77ca0,
e=0x7fffdb1725c0) at
/usr/src/debug/qtdeclarative/src/quick/items/qquickwindow.cpp:1857
d = 0x7f10fc001d20
#12 0x7f11107182c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#13 0x7f110fac25aa in Q
[plasmashell] [Bug 453730] Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=453730 Marcos Gutiérrez Alonso changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453730] Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=453730 Marcos Gutiérrez Alonso changed: What|Removed |Added CC||margua...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453730] New: Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=453730 Bug ID: 453730 Summary: Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault Product: plasmashell Version: 5.24.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: margua...@gmail.com Target Milestone: 1.0 Created attachment 148788 --> https://bugs.kde.org/attachment.cgi?id=148788=edit Segmentation fault backtrace with GDB SUMMARY I attach a backtrace. This segmentation fault crashes the entire plasma shell. It happens seemingly randomly and multiple times per session. STEPS TO REPRODUCE It seems to happen randomly. However, the crash usually takes place when switching between screens, alt+tabbing, drag-and-dropping something or when a notification pops up. OBSERVED RESULT The entire plasma shell crashes (and then restarts). SOFTWARE/OS VERSIONS I'm using Wayland OS: Manjaro Linux x86_64 Kernel: 5.17.6-1-MANJARO Resolution: 1920x1080 DE: Plasma 5.24.5 WM: kwin WM Theme: Relax-Blur-Aurorae Theme: Breath2 2021 Dark [Plasma], Breeze [GTK3] Icons: [Plasma], Relax-Dark-Icons [GTK2/3] CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz GPU: AMD ATI Radeon RX 6600/6600 XT/6600M Memory: 6280MiB / 16001MiB (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
