[plasmashell] [Bug 449981] Plasmashell crash in QQuickItemPrivate::setEffectiveVisibleRecur after screen change
https://bugs.kde.org/show_bug.cgi?id=449981 Victoria changed: What|Removed |Added CC|vi...@pm.me | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #9 from Victoria --- Can this also be the reason why Plasma can sometimes completely freeze during heavy IO (like downloading a big game on Steam)? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470372] rpm-ostree updates stopped working
https://bugs.kde.org/show_bug.cgi?id=470372 --- Comment #4 from Victoria --- Created attachment 159436 --> https://bugs.kde.org/attachment.cgi?id=159436&action=edit "rpm-ostree status" output -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470372] rpm-ostree updates stopped working
https://bugs.kde.org/show_bug.cgi?id=470372 --- Comment #3 from Victoria --- Created attachment 159435 --> https://bugs.kde.org/attachment.cgi?id=159435&action=edit Discover stdout showing rpm-ostree update available. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470372] rpm-ostree updates stopped working
https://bugs.kde.org/show_bug.cgi?id=470372 --- Comment #2 from Victoria --- The same thing now started happening on my Laptop -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470372] rpm-ostree updates stopped working
https://bugs.kde.org/show_bug.cgi?id=470372 --- Comment #1 from Victoria --- ~/.config/discoverrc [FlatpakSources] Sources=flathub,fedora-testing,fedora,flathub-beta [Window] geometry=3440,0,863,732 visibility=2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470372] New: rpm-ostree updates stopped working
https://bugs.kde.org/show_bug.cgi?id=470372 Bug ID: 470372 Summary: rpm-ostree updates stopped working Classification: Applications Product: Discover Version: 5.27.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rpm-ostree Backend Assignee: plasma-b...@kde.org Reporter: vi...@pm.me CC: aleix...@kde.org, mariamfahm...@gmail.com, trav...@redhat.com Target Milestone: --- Created attachment 159297 --> https://bugs.kde.org/attachment.cgi?id=159297&action=edit Discover claiming system is up-to-date despite knowing there are updates. Some time ago, Discover stopped showing rpm-ostree updates in GUI. It does see that the update is there, as shown by the update indicator on the sidebar but the main window shows the system is up-to-date and does not show "update" button. CLI logs also show that rpm-ostree is ran correctly and sees the update. Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X470 AORUS ULTRA GAMING -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #78 from Victoria --- Panels might move for another reason than screen IDs changing. For me regularly one panel goes missing after screens turn off. In `.config/plasma-org.kde.plasma.desktop-appletsrc` its 'lastScreen' attribute gets set to '-1' . This seems like an error and unrelated to screens getting different IDs. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442782] KDE Connect is draining battery
https://bugs.kde.org/show_bug.cgi?id=442782 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #5 from Victoria --- I am also affected by the high battery usage since a couple of days. Just a guess, but it seems to be correlated with me binge-watching a series using Haruna. Is it possible that media plugin / MPRIS is spamming communication with the phone? Version 1.19.1 from F-Droid Operating System: Arch Linux KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 460219] Kalendar crashes when adding events to default calendar; shows no future events.
https://bugs.kde.org/show_bug.cgi?id=460219 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #1 from Victoria --- Happens also with Korganizer. Bug must be with Akonadi itself. Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.1-zen2-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408507] notification does not allow copying via shortcut
https://bugs.kde.org/show_bug.cgi?id=408507 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #13 from Victoria --- This still does not work if you try copying from a full-size applet on a panel. Should I open another bug for it or reopen this one, since it seems to be the same issue but applet vs. pop-up? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456186] Add `right click` to pin window to all virtual desktops in the overview and present windows effect
https://bugs.kde.org/show_bug.cgi?id=456186 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #1 from Victoria --- Actually, the functionality of using right-click to pin window and ctrl+pull to show window also on the target desktop seems to be missing since the changes were introduced with Overview effect. Please add that functionality back to Desktop Grid. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449930] xwayland crashing randomly
https://bugs.kde.org/show_bug.cgi?id=449930 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #2 from Victoria --- *** Bug 451401 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451401] Random but related crashes
https://bugs.kde.org/show_bug.cgi?id=451401 Victoria changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #9 from Victoria --- (In reply to Victoria from comment #8) > If this was just an Xwayland bug, then why would systemmonitor stop crashing > the moment this crash happened? And why doesn't it happen on other Wayland compositors? *** This bug has been marked as a duplicate of bug 449930 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451401] Random but related crashes
https://bugs.kde.org/show_bug.cgi?id=451401 Victoria changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #8 from Victoria --- If this was just an Xwayland bug, then why would systemmonitor stop crashing the moment this crash happened? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451401] Random but related crashes
https://bugs.kde.org/show_bug.cgi?id=451401 --- Comment #6 from Victoria --- I have also managed to reproduce the issue on a laptop with Fedora 35 and AMD iGPU. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451401] Random but related crashes
https://bugs.kde.org/show_bug.cgi?id=451401
--- Comment #5 from Victoria ---
When the crash occured, system journal was spammed with the following line 10k
times in one second:
mar 25 19:26:20 morbidPC kwin_wayland_wrapper[1247]: failed to accept: Too many
open file
Rest of the journal log was:
mar 25 19:26:21 morbidPC kernel: sched: RT throttling activated
mar 25 19:26:22 morbidPC xembedsniproxy[1396]: The X11 connection broke (error
1). Did the X11 server die?
mar 25 19:26:22 morbidPC gmenudbusmenuproxy[1393]: The X11 connection broke
(error 1). Did the X11 server die?
mar 25 19:26:22 morbidPC ksmserver[1337]: The X11 connection broke (error 1).
Did the X11 server die?
mar 25 19:26:22 morbidPC kded5[1339]: Service ":1.123" unregistered
mar 25 19:26:22 morbidPC systemd[1146]: plasma-xembedsniproxy.service: Failed
with result 'exit-code'.
mar 25 19:26:22 morbidPC systemd[1146]: plasma-ksmserver.service: Failed with
result 'exit-code'.
mar 25 19:26:22 morbidPC systemd[1146]: plasma-gmenudbusmenuproxy.service:
Failed with result 'exit-code'.
mar 25 19:26:22 morbidPC rtkit-daemon[1165]: Supervising 7 threads of 4
processes of 1 users.
mar 25 19:26:22 morbidPC rtkit-daemon[1165]: Supervising 7 threads of 4
processes of 1 users.
mar 25 19:26:25 morbidPC xdg-desktop-portal-kde[1714]: xdp-kde-settings:
ReadAll called with parameters:
mar 25 19:26:25 morbidPC xdg-desktop-portal-kde[1714]: xdp-kde-settings:
groups: ("org.gnome.*")
mar 25 19:26:25 morbidPC xdg-desktop-portal-kde[1714]: xdp-kde-settings:
ReadAll called with parameters:
mar 25 19:26:25 morbidPC xdg-desktop-portal-kde[1714]: xdp-kde-settings:
groups: ("org.gnome.*")
mar 25 19:26:25 morbidPC rtkit-daemon[1165]: Supervising 7 threads of 4
processes of 1 users.
mar 25 19:26:25 morbidPC rtkit-daemon[1165]: Supervising 7 threads of 4
processes of 1 users.
mar 25 19:26:25 morbidPC rtkit-daemon[1165]: Supervising 7 threads of 4
processes of 1 users.
mar 25 19:26:25 morbidPC rtkit-daemon[1165]: Supervising 7 threads of 4
processes of 1 users.
mar 25 19:26:26 morbidPC plasmashell[1355]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/InhibitionHint.qml:26:5:
QML Label: Binding loop detected for property "verticalAlignment"
mar 25 19:26:26 morbidPC plasmashell[1355]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/InhibitionHint.qml:26:5:
QML Label: Binding loop detected for property "verticalAlignment"
mar 25 19:26:26 morbidPC plasmashell[1355]: QObject::disconnect: Unexpected
nullptr parameter
mar 25 19:26:26 morbidPC kwin_wayland[1247]: QMetaProperty::read: Unable to
handle unregistered datatype 'KWin::SessionState' for property
'KWin::EffectsHandlerImpl::sessionState'
mar 25 19:26:26 morbidPC kwin_wayland[1247]: QMetaProperty::read: Unable to
handle unregistered datatype 'KWin::SessionState' for property
'KWin::EffectsHandlerImpl::sessionState'
mar 25 19:26:26 morbidPC kded5[1339]: Service
"org.kde.StatusNotifierHost-1355" unregistered
mar 25 19:26:28 morbidPC kded5[1339]: Registering
"org.kde.StatusNotifierHost-42366" as system tray
mar 25 19:26:35 morbidPC audit[1355]: ANOM_ABEND auid=1000 uid=1000 gid=1000
ses=3 pid=1355 comm="plasmashell" exe="/usr/bin/plasmashell" sig=11 res=1
mar 25 19:26:35 morbidPC kernel: audit: type=1701 audit(1648232795.703:236):
auid=1000 uid=1000 gid=1000 ses=3 pid=1355 comm="plasmashell"
exe="/usr/bin/plasmashell" sig=11 res=1
mar 25 19:26:35 morbidPC systemd[1]: Created slice Slice
/system/systemd-coredump.
mar 25 19:26:35 morbidPC audit: BPF prog-id=43 op=LOAD
mar 25 19:26:35 morbidPC audit: BPF prog-id=44 op=LOAD
mar 25 19:26:35 morbidPC audit: BPF prog-id=45 op=LOAD
mar 25 19:26:35 morbidPC kernel: audit: type=1334 audit(1648232795.710:237):
prog-id=43 op=LOAD
mar 25 19:26:35 morbidPC kernel: audit: type=1334 audit(1648232795.710:238):
prog-id=44 op=LOAD
mar 25 19:26:35 morbidPC kernel: audit: type=1334 audit(1648232795.710:239):
prog-id=45 op=LOAD
mar 25 19:26:35 morbidPC systemd[1]: Started Process Core Dump (PID 42507/UID
0).
mar 25 19:26:35 morbidPC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-coredump@0-42507-0 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mar 25 19:26:35 morbidPC kernel: audit: type=1130 audit(1648232795.711:240):
pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-42507-0
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
mar 25 19:26:44 morbidPC kwin_wayland[1247]: This plugin does not support
raise()
mar 25 19:26:44 morbidPC kwin_wayland[1247]: This plugin does not support
grabbing the keyboard
mar 25 19:26:50 morbidPC xdg-desktop-portal-kde[1714]: xdp-kde-setting
[plasmashell] [Bug 449981] Plasmashell crashes randomly in PrimaryOutputWatcher::primaryOutputNameChanged()
https://bugs.kde.org/show_bug.cgi?id=449981 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #18 from Victoria --- The crash when monitors wake up from sleep still happens on two monitors connected via DP. Operating System: Arch Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.16.16-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451401] Random but related crashes
https://bugs.kde.org/show_bug.cgi?id=451401 Victoria changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #4 from Victoria --- I tried testing it extensively for last couple of days on Gnome and this issue did not occur. Today, it again did on Plasma. It must be something related to the compositor. There's also the case of some non-X-based applications (systemmonitor) crashing until the Xwayland apps crash, when they start working again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451401] Random but related crashes
https://bugs.kde.org/show_bug.cgi?id=451401 --- Comment #3 from Victoria --- I think it is Xwayland, because that's what most of the crashing applications are. Is KDE logout screen run through Xwayland as well? It doesn't appear after the crash and I have to reboot through CLI. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451401] Random but related crashes
https://bugs.kde.org/show_bug.cgi?id=451401 Victoria changed: What|Removed |Added Keywords||wayland Assignee|kdepim-b...@kde.org |kwin-bugs-n...@kde.org Component|server |wayland-generic Product|Akonadi |kwin --- Comment #1 from Victoria --- Report landed in Akonadi due to being reported using DrKonqui, but it is a general crash affecting all Xwayland applications and sometimes more. Could you please reassign it under Kwin? And any tips on how else I can debug it would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 451401] New: Random but related crashes
https://bugs.kde.org/show_bug.cgi?id=451401
Bug ID: 451401
Summary: Random but related crashes
Product: Akonadi
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: vi...@pm.me
Target Milestone: ---
Application: akonadiserver (5.19.3 (21.12.3))
Qt Version: 5.15.3
Frameworks Version: 5.91.0
Operating System: Linux 5.16.13-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.24.3 [KCrashBackend]
-- Information about the crash:
If I play a game long enough (Xwayland), suddenly all Xwayland applications
crash and cannot be restarted. When trying to restart it, there is no output in
commandline, it just hangs.
Yesterday, I had systemmonitor (ctrl+esc) crash every time when trying to
resize or right click in it. It started working normally after the xwayland
applications crashed.
It was crashing with the following output:
kde wl_display@1: error 1: invalid arguments for wl_shm@61.create_pool
The Wayland connection experienced a fatal error: Invalid argument
Today, that weird crash was preceeded after some minute of Plasmashell
constantly crashing and restarting after I got a notification.
These issues seem to be completely random, happen since 5.23 at least and it is
the first time DrKonqui launched and it is the first debugging information I
managed to get out of these crashes.
Removing all Plasma .config files did not stop the issue from occuring.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#6 std::default_delete::operator() (__ptr=0x110,
this=) at /usr/include/c++/11.2.0/bits/unique_ptr.h:79
#7 std::unique_ptr >::~unique_ptr
(this=, this=) at
/usr/include/c++/11.2.0/bits/unique_ptr.h:361
#8 __gnu_cxx::new_allocator >
>::destroy > > (__p=,
this=) at /usr/include/c++/11.2.0/ext/new_allocator.h:168
#9
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at /usr/include/c++/11.2.0/bits/alloc_traits.h:531
#10 std::vector >,
std::allocator > > >::_M_erase
(__position=Python Exception : Request for member
'_M_head_impl' is ambiguous in type 'std::tuple >'. Candidates are:
'std::default_delete std::_Head_base<1,
std::default_delete, true>::_M_head_impl'
(std::tuple > -> std::_Tuple_impl<0,
Akonadi::Server::Connection*, std::default_delete
> -> std::_Tuple_impl<1, std::default_delete > ->
std::_Head_base<1, std::default_delete, true>)
' std::_Head_base<0, Akonadi::Server::Connection*,
false>::_M_head_impl' (std::tuple > -> std::_Tuple_impl<0,
Akonadi::Server::Connection*, std::default_delete
> -> std::_Head_base<0, Akonadi::Server::Connection*, false>)
{_M_t = { >> = {_M_t = std::tuple
containing = {[1] = 0x557332c6acc0, [2] = {}}}, }}, this=) at /usr/include/c++/11.2.0/bits/vector.tcc:177
#11 std::vector >,
std::allocator > > >::erase
(__position=Python Exception : Request for member
'_M_head_impl' is ambiguous in type 'std::tuple >'. Candidates are:
'std::default_delete std::_Head_base<1,
std::default_delete, true>::_M_head_impl'
(std::tuple > -> std::_Tuple_impl<0,
Akonadi::Server::Connection*, std::default_delete
> -> std::_Tuple_impl<1, std::default_delete > ->
std::_Head_base<1, std::default_delete, true>)
' std::_Head_base<0, Akonadi::Server::Connection*,
false>::_M_head_impl' (std::tuple > -> std::_Tuple_impl<0,
Akonadi::Server::Connection*, std::default_delete
> -> std::_Head_base<0, Akonadi::Server::Connection*, false>)
{_M_t = { >> = {_M_t = std::tuple
containing = {[1] = 0x557332c6acc0, [2] = {}}}, }}, this=) at
/usr/include/c++/11.2.0/bits/stl_vector.h:1431
#12 Akonadi::Server::AkonadiServer::connectionDisconnected (this=) at /usr/src/debug/akonadi-21.12.3/src/server/akonadi.cpp:234
#13 0x7fc86d3072d6 in QObject::event (this=,
e=0x7fc8350b1870) at kernel/qobject.cpp:1314
#14 0x7fc86d2e308e in doNotify (event=0x7fc8350b1870,
receiver=0x7ffd8eafbee0) at kernel/qcoreapplication.cpp:1154
#15 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1140
#16 QCoreApplication::notifyInternal2 (receiver=0x7ffd8eafbee0,
event=0x7fc8350b1870) at kernel/qcoreapplication.cpp:1064
#17 0x7fc86d2e3ba9 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x557332c27190) at
kernel/qcoreapplication.cpp:1821
#18 0x7fc86d32b188 in postEventSourceDispatch (s=0x557332c28650) at
kernel/qeventdispatcher_glib.cpp:277
#19 0x7fc86b67bee3 in g_main_dispatch (context=0x557332c28520) at
../glib/glib/gmain.c:3381
#20 g_main_context_dispatch (context=0x557332c28520) at
../glib/glib/gmain.c:4099
#21 0x7fc86b6d20f9 in g_main_context_iterate
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #390 from Victoria --- I am sorry for a double post. It is not just an empty desktop. That screen behaves as if plasma crashed there. It does not react to right click on the desktop at all. Though pulling a panel over there works, so maybe its only a folder view that is crashed. Also, a widget on my main screen is repositioned. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #389 from Victoria --- Right now on Arch with beta of 5.24, the main screen keeps its panels. but secondary screen is left with a new, empty desktop (black screen, no panels). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439342] File system expose does not allow primary exposure
https://bugs.kde.org/show_bug.cgi?id=439342 --- Comment #2 from Victoria --- Created attachment 144812 --> https://bugs.kde.org/attachment.cgi?id=144812&action=edit Android refusing to share primary storage -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439342] File system expose does not allow primary exposure
https://bugs.kde.org/show_bug.cgi?id=439342 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #1 from Victoria --- I also have this problem. I think Android's filesystem handling changed. When selecting a folder, a popup is showed that says that I cannot share that folder "to protect my privacy". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 --- Comment #44 from Victoria --- I'm sorry for comment spam, but it might be relevant. It happens when I turn on my secondary monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 --- Comment #43 from Victoria --- Created attachment 143416 --> https://bugs.kde.org/attachment.cgi?id=143416&action=edit Plasmashell crash log 5.23.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #42 from Victoria --- Created attachment 143415 --> https://bugs.kde.org/attachment.cgi?id=143415&action=edit Screen crash logs from 5.23.3 This bug still occurs for me on Plasma 5.23.3. Logs attached. Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439096] kscreenlocker broken with error message on wayland
https://bugs.kde.org/show_bug.cgi?id=439096 --- Comment #12 from Victoria --- Created attachment 139965 --> https://bugs.kde.org/attachment.cgi?id=139965&action=edit Journalctl output Crash around 10:10 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439096] kscreenlocker broken with error message on wayland
https://bugs.kde.org/show_bug.cgi?id=439096 Victoria changed: What|Removed |Added Platform|openSUSE RPMs |unspecified Version|5.10.3 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437989] Plasma Wayland with PipeWire crashes when changing audio device profile
https://bugs.kde.org/show_bug.cgi?id=437989 --- Comment #3 from Victoria --- I can't replicate it currently due to being affected by other bugs, like https://bugs.kde.org/show_bug.cgi?id=439096 I tried turning off screen locking to work around it, but then after waking up, Plasma restarted/crashed 3 times before getting back into usable state. Should I cancel this and report again once other bugs are fixed and I am able to reproduce it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365775] When back from a monitor sleep panels and widget migrated between monitors
https://bugs.kde.org/show_bug.cgi?id=365775 Victoria changed: What|Removed |Added Version|5.6.5 |5.22.2 Platform|Fedora RPMs |unspecified CC||vi...@pm.me --- Comment #1 from Victoria --- I have the same situation on Arch with Plasma Wayland. Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439096] kscreenlocker broken with error message on wayland
https://bugs.kde.org/show_bug.cgi?id=439096 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #1 from Victoria --- I have the same situation on Arch. Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437989] New: Plasma Wayland with PipeWire crashes when changing audio device profile
https://bugs.kde.org/show_bug.cgi?id=437989 Bug ID: 437989 Summary: Plasma Wayland with PipeWire crashes when changing audio device profile Product: plasmashell Version: 5.21.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: vi...@pm.me Target Milestone: 1.0 Plasma Wayland with pipewire-pulse crashes after changing audio device. I have two screens and have audio playing through one of them. When the second screen gets turned off and on again, audio "device profile" changes to playing through it. After I switch the device profile back to my main monitor AND turn off the settings window, plasmashell crashes. Operating System: Arch Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.8-zen1-1-zen OS Type: 64-bit Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: Radeon RX 580 Series LOG [12:59] morbidPC | plasmashell kf.plasma.quick: Applet preload policy set to 1 trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" qt.qpa.wayland: Wayland does not support QWindow::requestActivate() trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Loading Calendar plugin HolidaysEventsPlugin(0x5582320aa8e0) Loading Calendar plugin PimEventsPlugin(0x5582320a1a00) file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:501:21: Unable to assign [undefined] to double file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:528:17: Unable to assign [undefined] to double file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:547:13: Unable to assign [undefined] to double trying to show an empty dialog qt.gui.icc: fromIccProfile: failed minimal tag size sanity file:///usr/share/plasma/plasmoids/org.kde.plasma.panelspacer/contents/ui/main.qml:53:5: Unable to assign [undefined] to QQuickGridLayout* file:///home/morbid/.local/share/plasma/plasmoids/com.pajuelo.plasmaConfSaver/contents/ui/FullRepresentation.qml:32:33: Invalid property assignment: string expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt. file:///home/morbid/.local/share/plasma/plasmoids/com.pajuelo.plasmaConfSaver/contents/ui/FullRepresentation.qml:31:33: Invalid property assignment: string expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt. file:///home/morbid/.local/share/plasma/plasmoids/com.pajuelo.plasmaConfSaver/contents/ui/FullRepresentation.qml:30:31: Invalid property assignment: string expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt. file:///home/morbid/.local/share/plasma/plasmoids/com.pajuelo.plasmaConfSaver/contents/ui/main.qml:23: TypeError: Cannot call method 'substr' of undefined file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:30:1: QML DropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" trying to show an empty dialog trying to show an empty dialog qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() file:///usr/share/plasma/plasmoids/org.kde.plasma.panelspacer/contents/ui/main.qml:53:5: Unable to assign [undefined] to QQuickGridLayout* Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasm
[Elisa] [Bug 437730] Playlist is visually cluttered
https://bugs.kde.org/show_bug.cgi?id=437730 --- Comment #1 from Victoria --- Created attachment 138820 --> https://bugs.kde.org/attachment.cgi?id=138820&action=edit General view -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 437730] New: Playlist is visually cluttered
https://bugs.kde.org/show_bug.cgi?id=437730 Bug ID: 437730 Summary: Playlist is visually cluttered Product: Elisa Version: 21.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: vi...@pm.me Target Milestone: --- Created attachment 138819 --> https://bugs.kde.org/attachment.cgi?id=138819&action=edit Minimized view Playlist displays songs with their album covers. If playing in shuffle mode, this becomes very cluttered. It looks especially bad on the "minimized" view. See attached. Please do not show covers in playlist. It looks good in "Tracks" list when it is more concise and everything is in one line. But in my opinion the cover arts still shouldn't be shown in the minimized player view. Also, the playlists always show a horizontal scroll-bar, even if the playlist is empty. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #353 from Victoria --- It still happens on latest Plasma on Wayland. Especially after one of the screens going to sleep, then another one. After waking up, screen layouts switch places (both relative placement of the screens and the panels). Disabling the 2nd screen makes my primary screen "primary" again, but sometimes the panels from second screen disappear completely (as if they were on an imaginary 3rd screen) and I can't get them back other than removing config files and recreating them. Operating System: Arch Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.6-zen1-1-zen OS Type: 64-bit Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 418433] It doesn't allow the monitor to be turned off
https://bugs.kde.org/show_bug.cgi?id=418433 --- Comment #7 from Victoria --- Yes, it was based on the description from the battery monitor applet. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 418433] It doesn't allow the monitor to be turned off
https://bugs.kde.org/show_bug.cgi?id=418433 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #3 from Victoria --- In my opinion at the very least, an audio player should not be inhibiting screen locking. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409841] New: I saved my work but after i was trying to open so i can finish it and it tells me "no valid krita file" and i tryied to open it with other aplications but the file is empty
https://bugs.kde.org/show_bug.cgi?id=409841 Bug ID: 409841 Summary: I saved my work but after i was trying to open so i can finish it and it tells me "no valid krita file" and i tryied to open it with other aplications but the file is empty Product: krita Version: 4.2.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: victorialva...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1.clic on the file 2. wait for it to open 3. it opens (it did not) OBSERVED RESULT the file did not open EXPECTED RESULT the file opened SOFTWARE/OS VERSIONS Windows: 7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 14 Jul 2019 00:19:09 -0300: Converting from application/x-krita to application/x-krita. Location: C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra. Real location: C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra. Batchmode: 0. Configuration: none 14 Jul 2019 00:19:10 -0300: Completed saving C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra (mime: application/x-krita). Result: OK 14 Jul 2019 00:34:41 -0300: Converting from application/x-krita to application/x-krita. Location: C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra. Real location: C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra. Batchmode: 0. Configuration: none 14 Jul 2019 00:34:42 -0300: Completed saving C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra (mime: application/x-krita). Result: OK 14 Jul 2019 00:49:42 -0300: Converting from application/x-krita to application/x-krita. Location: C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra. Real location: C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra. Batchmode: 0. Configuration: none 14 Jul 2019 00:49:43 -0300: Completed saving C:/Users/Jacqueline Ramirez/Downloads/vito\kakita.kra-autosave.kra (mime: application/x-krita). Result: OK 14 Jul 2019 01:01:32 -0300: Saving Document C:/Users/Jacqueline Ramirez/Downloads/vito/kakita.kra as C:/Users/Jacqueline Ramirez/Downloads/vito/kakita.kra (mime: application/x-krita). 500 * 500 pixels, 12 layers. 101 frames, 24 framerate. Export configuration: No configuration 14 Jul 2019 01:01:33 -0300: Converting from application/x-krita to application/x-krita. Location: C:/Users/Jacqueline Ramirez/Downloads/vito/kakita.kra. Real location: C:/Users/Jacqueline Ramirez/Downloads/vito/kakita.kra. Batchmode: 0. Configuration: none 14 Jul 2019 01:01:34 -0300: Completed saving C:/Users/Jacqueline Ramirez/Downloads/vito/kakita.kra (mime: application/x-krita). Result: OK OpenGL Info -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 408930] New: Political map doesnt work
https://bugs.kde.org/show_bug.cgi?id=408930 Bug ID: 408930 Summary: Political map doesnt work Product: marble Version: 2.5 (KDE Applications 18.04) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: viccd...@gmail.com Target Milestone: --- Created attachment 121018 --> https://bugs.kde.org/attachment.cgi?id=121018&action=edit Screenshot from grey atlas when i click the political map botton, the atlas is turned grey and doesn't show any geo-political division STEPS TO REPRODUCE 1. Open Marble 2. Click option: Political Map OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 408870] New: krdc does not connect to rdp client
https://bugs.kde.org/show_bug.cgi?id=408870 Bug ID: 408870 Summary: krdc does not connect to rdp client Product: krdc Version: 18.12 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: batcav...@gmail.com Target Milestone: --- krdc does not connect to rdp client. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE 15.1 / KDE Plasma KDE Plasma Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407465] KMail 5.9.3 doesn't seem to set active sieve script
https://bugs.kde.org/show_bug.cgi?id=407465 Hazel Victoria Campbell changed: What|Removed |Added CC||w...@wza.us -- You are receiving this mail because: You are watching all bug changes.
