[systemsettings] [Bug 482409] Unclear how to add printer / button disabled
https://bugs.kde.org/show_bug.cgi?id=482409 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485331] New: plasmashell crashed when opening akonadiconsole
https://bugs.kde.org/show_bug.cgi?id=485331
Bug ID: 485331
Summary: plasmashell crashed when opening akonadiconsole
Classification: Plasma
Product: plasmashell
Version: 6.0.3
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: dcalv...@gmail.com
Target Milestone: 1.0
Application: plasmashell (6.0.3)
Qt Version: 6.6.3
Frameworks Version: 6.0.0
Operating System: Linux 6.8.4-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.3 [CoredumpBackend]
-- Information about the crash:
Upon opening akonadiconsole for the purposes of troubleshooting an issue
(https://discuss.kde.org/t/kontact-freezes-upon-starting/13789/8)
akonadiconsole froze and plasmashell crashed and restarted
The reporter is unsure if this crash is reproducible.
-- Backtrace (Reduced):
#5 0x721c16ec5ae6 in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x57257b85ad20) at
/usr/src/debug/plasma-workspace/plasma-workspace-6.0.3/applets/kicker/plugin/kastatsfavoritesmodel.cpp:189
#6 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (arg=, f=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7
QtPrivate::Functor::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (arg=, f=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:339
#8
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=0x57257b85ad10, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522
#9 0x721c38f91599 in QtPrivate::QSlotObjectBase::call (a=0x7ffd53babb78,
r=0x57257bd41500, this=0x57257b85ad10, this=, r=,
a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.3/src/corelib/kernel/qobjectdefs_impl.h:433
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 485331] plasmashell crashed when opening akonadiconsole
https://bugs.kde.org/show_bug.cgi?id=485331 --- Comment #1 from Damian C --- Created attachment 168347 --> https://bugs.kde.org/attachment.cgi?id=168347=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 484775] Kontact Does Not Start After Upgrade to Plasma 6.0.3
https://bugs.kde.org/show_bug.cgi?id=484775 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484430] Discover crashes when searching for something
https://bugs.kde.org/show_bug.cgi?id=484430 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484430] New: Discover crashes when searching for something
https://bugs.kde.org/show_bug.cgi?id=484430 Bug ID: 484430 Summary: Discover crashes when searching for something Classification: Applications Product: Discover Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 167722 --> https://bugs.kde.org/attachment.cgi?id=167722=edit gdb plasma-discover SUMMARY Discover crashes when attempting to search for something, or trying to explore categories. STEPS TO REPRODUCE 1. Open Discover 2. Search for something 3. Crashes OBSERVED RESULT App crashes EXPECTED RESULT Returns the search, or shows the clicked category. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION attached gdb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484366] Using Wayland changes panels and desktops to the wrong monitors
https://bugs.kde.org/show_bug.cgi?id=484366 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484366] New: Using Wayland changes panels and desktops to the wrong monitors
https://bugs.kde.org/show_bug.cgi?id=484366 Bug ID: 484366 Summary: Using Wayland changes panels and desktops to the wrong monitors Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When logging in selecting Wayland, panels and desktops are attached to the wrong monitors/displays. STEPS TO REPRODUCE 1. Boot ArchLinux, select Wayland. 2. Observe the panels and desktops disrupted. OBSERVED RESULT Desktops and panels are attached to the wrong monitor. EXPECTED RESULT Panels and desktops remain attached to the monitors I have set up for them regardless of desktop compositor. As it used to be prior to the Plasma 6 upgrade. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION Using 3 monitors. This started happening after upgrading to Plasma 6. Something similar to this had happened in the past but it had been solved, it was possible to change between x11 and Wayland while keeping the same desktops and panels on the right monitors. If I logoff Wayland and go back to X11 the panels and desktops are attached to the correct monitors. If I correct the panels and desktops for Wayland and attach them the way they should go, then going back to x11 will have the panels all wrong. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 484364] Crash launching kontact
https://bugs.kde.org/show_bug.cgi?id=484364 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 484364] New: Crash launching kontact
https://bugs.kde.org/show_bug.cgi?id=484364 Bug ID: 484364 Summary: Crash launching kontact Classification: Applications Product: kontact Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dcalv...@gmail.com Target Milestone: --- Created attachment 167685 --> https://bugs.kde.org/attachment.cgi?id=167685=edit coredumpctl info for this crash SUMMARY When attempting to launch Kontact, it crashes. STEPS TO REPRODUCE 1. Boot Arch Linux with Plasma 6, select Wayland. 2. Attempt to launch kontact 3. Crash. OBSERVED RESULT Kontact crashes and dumps core. EXPECTED RESULT Open Kontact normally. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION Only happens with Wayland, using X11 results in Kontact launching successfully. Attempting to launch Kmail instead of Kontact results in the same crash. Started happening only after upgrading to Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 472370] Selecting a different audio output device sometimes won't change the output device for active applications
https://bugs.kde.org/show_bug.cgi?id=472370 Damian C changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 472370] Selecting a different audio output device sometimes won't change the output device for active applications
https://bugs.kde.org/show_bug.cgi?id=472370 --- Comment #2 from Damian C --- (In reply to Nate Graham from comment #1) > Can you install the "PulseAudio Volume Control" app and do the same thing > there, and see if the same problem happens? Thanks! After some days of testing I can say it tends to happen less frequently, but still does happen even using pavucontrol. Basically after selecting a device as default from the output devices tab, sometimes an app continues to send audio through the previously default device and needs to be set through the playback tab, changing the specific stream. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460687] "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 --- Comment #3 from Damian C --- (In reply to Laurent Montel from comment #2) > We have "redirect" action. > so what is missing ? I don't think Redirect is the same as Forward. If you look at the options presented here: https://docs.kde.org/stable5/en/kmail/kmail2/filters.html Forward and Redirect are two distinct options. Redirect: "This will redirect the message as-is to another email address.". I think it attempts to re route the message without re sending it as a message sent by you, but I'm not sure. While forward is the same as right clicking the message and re send it from your account as if right clicking and selecting forward - inline. Sending the messag efrom your account, adding the "Fwd:" prefix to the subject. So yeah, Forward To is literally missing. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460687] "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 Damian C changed: What|Removed |Added Version|5.21.2 |5.23.3 --- Comment #1 from Damian C --- Still an issue with: Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.3-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 472370] Selecting a different audio output device sometimes won't change the output device for active applications
https://bugs.kde.org/show_bug.cgi?id=472370 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 472370] New: Selecting a different audio output device sometimes won't change the output device for active applications
https://bugs.kde.org/show_bug.cgi?id=472370 Bug ID: 472370 Summary: Selecting a different audio output device sometimes won't change the output device for active applications Classification: Plasma Product: pulseaudio-qt Version: 1.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.fe...@gmx.de Reporter: dcalv...@gmail.com Target Milestone: --- SUMMARY *** Selecting a different audio output device sometimes won't change the output device for active applications such as a game or a player, or a browser. You need to change the application's output device individually by using the "applications" tab in the volume control. *** STEPS TO REPRODUCE 1. Be playing some audio on an application, youtube over brave browser for instance. 2. Use the panel's volume control to select a different output device, such as a headset. 3. Audio continues to play over the previously selected output device. OBSERVED RESULT Audio continues to play over the previously selected output device I then correct this by going over to the applications tab in the aforementioned volume control and select a different output device for the specific application. EXPECTED RESULT Applications play over the device selected on the devices volume control tab. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.3-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION This does not happen always, can't find a pattern to it. Unsure if related, sounds like it could be: Using the mouse scroll wheel to change the volume by having the mouse cursor placed above the panel's volume icon also changes the volume of the previously used device (and the associated system sound for each step of volume change also plays over the previously active device) unless I open the panel and manually slide the volume over the desired currently active device, only then the mouse scroll wheel acts as expected. Same result happens with my keyboard's dedicated volume keys. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 --- Comment #5 from Damian C --- (In reply to Zamundaaa from comment #3) > There's still no GAMMA_LUT property, so I'm not sure how night color would > be related. Can you attach your full KWin log? So > > journalctl --user-unit plasma-kwin_wayland --boot 0 > after causing the issue again Attached! I don't expect Night Color to work since the property is not there, but it seems to cause the issue when it attempts to kick in. And the only way to stop it from happening so far is to disable Night Color. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 --- Comment #4 from Damian C --- Created attachment 158675 --> https://bugs.kde.org/attachment.cgi?id=158675=edit journalctl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469175] Panel with taskbar freezes visually but remains operational
https://bugs.kde.org/show_bug.cgi?id=469175 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469175] New: Panel with taskbar freezes visually but remains operational
https://bugs.kde.org/show_bug.cgi?id=469175 Bug ID: 469175 Summary: Panel with taskbar freezes visually but remains operational Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Default panel with taskbar and clock freezes visually at some point during operation. The panel can still be interacted with but it won't update any information, the time on the digital clock remains as it was when it stopped working, and taskbar icons that would update some information (such as the new email counter within the kmail icon) will not update. STEPS TO REPRODUCE 1. Boot and login normally. 2. Use the system normally and at some point some panel will stop responding, normally the main display one, but not exclusively. OBSERVED RESULT Panel stops visually updating, and becomes "frozen", but interaction is still possible, so I'd call it "functional". EXPECTED RESULT Panel doesn't freeze visually at all. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.13-zen-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION It can be brought back to a working state by right clicking the panel, entering edit mode and changing some visual aspect of it, such as the height. It does not happen on all panels simultaneously, it seems to affect a single display, though not necessarily the same one every time. It may have happened around the time I opened a game running with Proton, but unsure at this point. Even more strange, during the "frozen" period, if one clicks on the pinned taskbar icon for "System Settings" it opens some windows that existed at some point on a different activity. Even stranger is the fact that this activity no longer exists as I deleted it from the activities menu, but during this issue, clicking on this icon brings back the apps that I had open back then, which were a browser and a konsole window. This strange behavior ceases when the workaround of changing the panels height is applied. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 --- Comment #2 from Damian C --- Created attachment 158525 --> https://bugs.kde.org/attachment.cgi?id=158525=edit drm_info1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 --- Comment #7 from Damian C --- (In reply to Zamundaaa from comment #6) > Please create a separate bug report for the freeze Done, https://bugs.kde.org/show_bug.cgi?id=468895 Thank you, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] New: Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 Bug ID: 468895 Summary: Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers. Classification: Plasma Product: kwin Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: dcalv...@gmail.com Target Milestone: --- SUMMARY *** With the Night Color feature enabled, running Wayland with NVIDIA proprietary drivers, one or more monitors freezes momentarily. If left unattended the whole kwin session freezes on all monitors. On the logs, the message : "kwin_wayland_drm: Failed to create gamma blob! Invalid argument" can be seen at each time the desktop freezes. After a few seconds it will unfreeze and let you continue for maybe a minute more before going at it again, I'm guessing it is the Night Color feature attempting to start again. *** STEPS TO REPRODUCE 1. Be running a Kwin Wayland session using Nvidia proprietary drivers. 2. Have the Night Color feature enabled. 3. At the time the Night Color feature is supposed to kick in, the issue is observed. OBSERVED RESULT One or more monitors freezes momentarily. If left unattended the whole kwin session freezes on all monitors. EXPECTED RESULT Night Color works as expected. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Nvidia Drivers: 530.41.03-1 ADDITIONAL INFORMATION 3 monitors: One Display Port, one HDMI and one DVI. It seems to favor freezing the DVI monitor first, but the rest will follow soon. To avoid this issue and continue to have a working system through the night hours, the workaround has been to disable Night Color completely. Seems related to #450327. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 --- Comment #5 from Damian C --- I want to add that with the Night Color feature enabled, each time the "kwin_wayland_drm: Failed to create gamma blob! Invalid argument" message shows on the logs, the screen freezes (one of them, the other two won't), and it can completely freeze the kwin session. 3 monitors: One Display Port, one HDMI and one DVI. Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Nvidia Drivers: 530.41.03-1 Workaround has been to disable this feature completely. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460687] "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 --- Comment #10 from Damian C --- (In reply to Adam Borsos from comment #9) > QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu-compositing" works me as a > workaround, so the issue seems to be HW accel related > > (Operating System: Gentoo Linux 2.13 > KDE Plasma Version: 5.27.4 > KDE Frameworks Version: 5.104.0 > Qt Version: 5.15.8 > Kernel Version: 6.1.19-gentoo-x86_64 (64-bit) > Graphics Platform: Wayland > Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics > Memory: 31.2 GiB of RAM > Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2) This works for me as well! Also works for the news feed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login after panel appears
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #21 from Damian C --- Confirmed, the issue is no longer happening. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #14 from Damian C --- (In reply to Damian C from comment #13) > (In reply to Nate Graham from comment #11) > > (waiting for confirmation that it's still an issue in the X11 session for > > Plasma 5.26.2, for the people who were experiencing it in 5.26.0) > > I regret to report that this is still happening running 5.26.2, no change in > behavior whatsoever. Oh and now it seems, plasmashell --replace doesn't put them back to their proper place. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #13 from Damian C --- (In reply to Nate Graham from comment #11) > (waiting for confirmation that it's still an issue in the X11 session for > Plasma 5.26.2, for the people who were experiencing it in 5.26.0) I regret to report that this is still happening running 5.26.2, no change in behavior whatsoever. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455538] Option to keep floating panels -floating- when windows are maximized and using "Maximized Window Gap" Kwin Script
https://bugs.kde.org/show_bug.cgi?id=455538 --- Comment #5 from Damian C --- (In reply to Nate Graham from comment #4) > Git commit ed0214057e7ae78bedc4486a6344db9459ce5570 by Nate Graham, on > behalf of Niccolò Venerandi. > Committed on 25/10/2022 at 14:52. > Pushed by ngraham into branch 'master'. > > Panel: when floating, de-float when window touches it > > A floating Panel now de-floats and becomes opaque whenever a window touches > it. > This also allows for a thinner Panel when a window is maximized (a normal > Panel > is 44 px; before this patch a de-floated one was 60, now it's 52px) and that > should > allay complaints about excessive margins). > Related: bug 455483, bug 455323 > FIXED-IN: 5.27 > > M +29 -6desktoppackage/contents/views/Panel.qml > > https://invent.kde.org/plasma/plasma-desktop/commit/ > ed0214057e7ae78bedc4486a6344db9459ce5570 Thank you! looking forward to 5.27 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #6 from Damian C --- (In reply to Nate Graham from comment #4) > We're getting reports that this remains broken but only for X11. Which makes > sense for why I can't reproduce it, because I'm on Wayland. And probably the > developers who worked on the fix are on Wayland too. > > For anyone able to reproduce on X11, can you try the following: > > 1. Log out of your X11 session > 2. Log into a wayland session > 3. Arrange widgets how yo want > 3. Log out of the wayland session > 4. Log into it again > > Thanks! I've done this and it seems to be less messy overall. Almost all widgets retain their proper positioning, except for 2 of the digital clock ones. This can be observed in the screenshot I've uploaded (comment 5 I think). And the webslice widget is now displaying a dark grey color instead of the contents of the website. (can also be seen on screenshot) This of course also brings other problems with using wayland, such as the webslice widget issue, Kmail's blank emails on the reading pane, etc. But it seems to not misalign most of the widgets as opposed to X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #5 from Damian C --- Created attachment 153030 --> https://bugs.kde.org/attachment.cgi?id=153030=edit Widgets after rebooting using wayland. Digital clock widgets showing wrong size, but better overall. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460687] New: "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 Bug ID: 460687 Summary: "Forward To" option missing from Filter Actions Classification: Applications Product: kmail2 Version: 5.21.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: dcalv...@gmail.com Target Milestone: --- Created attachment 153013 --> https://bugs.kde.org/attachment.cgi?id=153013=edit Missing Forward To option within Filter Actions menu SUMMARY *** When configuring either a new or existing filter, the Filter Actions drop down menu is missing the Forward-To option. *** STEPS TO REPRODUCE 1. Go to settings. Configure Filters 2. Click on Filter Actions. OBSERVED RESULT Observe the lack of a "Forward To" option. EXPECTED RESULT Forward To option within the Filter Actions menu as described here: https://docs.kde.org/stable5/en/kmail/kmail2/filters.html SOFTWARE/OS VERSIONS 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.2-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION See Attached image. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 446580] Contact synchronization with google doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446580 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460618] Can't remember desktop widget positions after relogin
https://bugs.kde.org/show_bug.cgi?id=460618 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 Damian C changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #2 from Damian C --- (In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 413645 *** Hello, I've seen that in bug 413645 this has been marked as fixed with 5.26. I am now running 5.26 and I'm afraid this behavior as described in this bug report persist. Issuing plasmashell --replace restores the widgets to their intended position (previous to reboot). Thank you, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] New: Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 Bug ID: 458038 Summary: Widgets become slightly misplaced (misaligned) after login Product: plasmashell Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 151411 --> https://bugs.kde.org/attachment.cgi?id=151411=edit The yellow line shows the alignment position the widgets should have stayed aligned to SUMMARY When logging in, right before the task manager panel appears at the bottom, all the widgets shown on the screenshot are loaded first and they appear in their right positions, as set previously before rebooting/relogin. However right after the bottom task manager panel appears, they become misplaced or misaligned, almost as if they would seem to "jump" out of position. This is on the third screen/display. All three displays are one next to the other in an horizontal fashion, the widgets are placed in the one to my right side. STEPS TO REPRODUCE 1. Place widget to their desired positions. 2. Log off and login, or reboot and login. OBSERVED RESULT Observe the widgets become misplaced right after the bottom task manager is loaded. EXPECTED RESULT The widgets remain in their specified position as they were placed before rebooting. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.1-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION See screenshot. The yellow line shows the alignment position the widgets should have stayed aligned to. Also running 2 instances of conky for 2 information "panels". The widgets that become misplaced are mainly "System Monitor" widgets, but I also had this issue with an assortment of "Digital Clock" widgets that I had previously placed on that same screen showing the time on different cities, and the constant repositioning after a reboot required to make them useful was too frustrating so I just removed them. The widget's size is also slightly altered. Could be related to "425368", though there's very little information on that one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455323] Ugly margins around de-floated floating panel with any maximized windows
https://bugs.kde.org/show_bug.cgi?id=455323 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 --- Comment #7 from Damian C --- (In reply to Damian C from comment #5) > Same, but with white screen instead of black. Presumably due to theming. > > Operating System: Arch Linux > KDE Plasma Version: 5.25.1 > KDE Frameworks Version: 5.95.0 > Qt Version: 5.15.5 > Kernel Version: 5.18.6-zen1-1-zen (64-bit) > Graphics Platform: Wayland > Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz > Memory: 15.5 GiB of RAM > Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 I must clarify, that unlike the bug reporter, I do not get the same blank screen with the Feeds (Akregator), and the messages do load if I double click to open them in a new window. But I did not see them loading even after a while. The button in the middle of the panes, to switch from HTML to Plain Text, is also unresponsive using wayland, it simply does nothing. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com --- Comment #5 from Damian C --- Same, but with white screen instead of black. Presumably due to theming. Operating System: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.6-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455538] New: Option to keep floating panels -floating- when windows are maximized
https://bugs.kde.org/show_bug.cgi?id=455538 Bug ID: 455538 Summary: Option to keep floating panels -floating- when windows are maximized Product: plasmashell Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 149885 --> https://bugs.kde.org/attachment.cgi?id=149885=edit example of the "desired" result but with a non maximized window SUMMARY *** Normally when using a floating panel, maximizing a window and having the floating panel become a "normal" (ie, non floating) panel makes sense as it would look ugly and incoherent with the maximized window. However I'm using the "Maximized Window Gap" Kwin Script, and with it my maximized windows have a gap around them, and when these windows are not maximized (but taking the same space as the maximized window) it looks like both the window and the panel are floating over the background and to me it looks quite cool. However when I maximize any window while using the kwin script and the floating panel, the panel acts as it was designed to and becomes "non floating", thus breaking the look of both elements (the window, and the panel) floating. I know this is probably quite a niche scenario, but I'd love to have such option. Something similar but not quite the same has been requested under bug #454950. It will make more sense with the screenshot, which shows more or less an example of the "desired" result but with a non maximized window, which doesn't look quite exactly right as I basically had to set the window size manually to more or less match what it looks like when maximized with the kwin script enable, but it will surely illustrate the point. *** STEPS TO REPRODUCE 1. Enable Floating Panel. 2. Be using Kwin Script "Maximized Window Gap" 3. Maximize a window. OBSERVED RESULT The floating panel becomes a "normal" panel and docks to the bottom of the screen. EXPECTED RESULT That the floating panel remains floating the same as if there was no maximized window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 --- Comment #9 from Damian C --- Experiencing the same issue. Running korganizer within kontact. The frequency of the issue has increased after getting the latest version of the app: korganizer-21.08.3-1 When it does happen I get hundreds of pop ups and the system stops responding. I can only close the app by switching to a tty (Ctrl + Alt + F2) and killing it. The massive amount of pop ups causes the k11 process to use 100% of CPU. Perhaps I'm seeing more messages than most as my google calendar has got subscriptions from a few other calendars from other people. The very last time it happened today I was not interacting with korzganizer at all, rather browsing the internet. Also, the very last time it happened I had no choice but to issue sudo reboot from the tty as the system would not come back from the freeze/stuck. Since it happened twice today I have removed the calendar for now. Operating System: Manjaro Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15,5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 Damian C changed: What|Removed |Added Version|5.18.1 |GIT (master) CC||dcalv...@gmail.com Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342873] After removing a second panel with taskbar, windows still animate minimization into it
https://bugs.kde.org/show_bug.cgi?id=342873 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com --- Comment #9 from Damian C --- Still the case in 5.22.5. The only way to get it to grab the minimization "focus" again on the main panel is to make some re-arrangement or change to it. It seems the focus goes to whatever panel got modified/changed last. Acceptable workaround, but I'd propose to have the panels clearly identified in some form on a setting and perhaps using window rules be able to force them to minimize to a specific panel. That would also allow specific apps to minimize to specific panels. No idea how hard that'd be though, maybe it's not possible. Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.15-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426412] Kwin laggy after pausing and un-pausing compositing
https://bugs.kde.org/show_bug.cgi?id=426412 Damian C changed: What|Removed |Added Platform|Other |Manjaro CC||dcalv...@gmail.com Version|5.19.5 |5.22.4 --- Comment #8 from Damian C --- Confirm the same bug. kwin_x11 --replace Removes the lag. Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.15-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
