[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 Michael Mikowski changed: What|Removed |Added CC||z_mikow...@yahoo.com --- Comment #40 from Michael Mikowski --- This looks promising Harald. Kfocus will test with 5.27.8 across multiple installations and report back. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466689] System Settings Crash After Applying Global Theme
https://bugs.kde.org/show_bug.cgi?id=466689 --- Comment #2 from Michael Mikowski --- Thank you Nate! > I recommend upgrading to 5.15.8 + the KDE patches. Agreed. Please point me to a document on how to do this if you know one exists. I looked around for a few minutes, and didn't easily find anything. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466689] New: System Settings Crash After Applying Global Theme
https://bugs.kde.org/show_bug.cgi?id=466689 Bug ID: 466689 Summary: System Settings Crash After Applying Global Theme Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: z_mikow...@yahoo.com Target Milestone: --- Application: systemsettings (5.27.2) Qt Version: 5.15.3 Frameworks Version: 5.102.0 Operating System: Linux 5.19.0-32-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.2 LTS DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: Steps to Reproduce: 1. Open System Settings > Appearance > Global Theme 2. Select a different theme than the current (for this crash, I selected Breeze Dark IIRC) 3. In the "Apply Breeze Dark" dialog, check [x] Appearance settings and [x] Desktop and window layout 4. Click [ Apply ] button Expected Results: 1. Theme should be applied as selected. 2. System settings should not crash. Actual Results: 1. Theme is applied as selected (Good!) 2. System settings crashes (BAD) This behamatches closed bug 458405 which is marked as a duplicate of bug 446111. However, I have been able to reproduce, and the failure mode may vbe different. This is also on Plasma 5.27.2. Frequency: Estimated below 5%. While this crash occured once, I tried 20 additional times using the same system settings instance each time, and it occurred again on the 20th attempt. The detail listed is: Executable: systemsettings PID 50,622 Signal: Segmentation fault (11) Time 3/1/23 5:27 PM The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fc7c2e7df00 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fc7c2e7de19 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fc7c2e7de19 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fc7c2e7de19 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fc7c2e7ebde in QQuickWindowPrivate::deliverToPassiveGrabbers(QVector > const&, QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fc7c2e84ed5 in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fc7c2e8665f in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fc7c4f4d5a5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fc7c576c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fc7c4ab9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fc7c39470ab in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #15 0x7fc7c57af4ee in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fc7c576c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fc7c5774364 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fc7c4ab9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fc7c5772e47 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fc7c57c8d40 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fc7c57cbfd5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fc7c576c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fc7c4ab9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fc7c4f41307 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7fc7c4f16a2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #26 0x7fc7bf0f8d6e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #27 0x7fc7c3320d3b in g_main_context_dispatch () from
[dolphin] [Bug 464460] Support environmental variables in Places
https://bugs.kde.org/show_bug.cgi?id=464460 --- Comment #4 from Michael Mikowski --- Hi Felix: > Excuse me if I have missed a detail here: Config files for what? I should have read the initial bug a little more closely. I incorrectly assumed that places were read from a config file dropped in ~/.config. However, on closer examination, I see this is found in `~/.local/share/user-places.xbel`. My interest was in seeing variable expansion generally supported for YAML-like KDE config files using a single shared read-write library. I agree that the additional abstraction for this specific file is almost certainly not worth it. Sorry for the misunderstanding. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464460] Support environmental variables in Places
https://bugs.kde.org/show_bug.cgi?id=464460 Michael Mikowski changed: What|Removed |Added CC||z_mikow...@yahoo.com --- Comment #2 from Michael Mikowski --- Felix, I generally agree with your sentiment. However, I do think there is some value here for your consideration. Honestly, just support for a small subset like HOME and USER might be a good first step. I did this with qwe bash bookmarks app (https://github.com/olafurw/qwe), and now users can share a config file, which is very handy. I would suggest only support of UPPER_CASE variable names using brace expansion and a YAML escape back slash like so: ... 1. Conflicts with literal labels issue: Probably mitigated by escaped bash-style brace expansion. 2. Use Cases: 1. Users create config files that can be shared without modifications; 2. Developers can rely on static configs that do not need to be rewritten for every user; 3. Apps can abstract a greater number of default settings through a central default config expressed in $XDG_CONFIG_DIRS. 3. Bookmarks can be changed via scripts : yes, but this hard-codes configs and does not capture intent like environment variable expansion can. Rewriting is pretty much a hack to get around that intent isn't captured. 4. Cost vs. benefit: I defer to you on that. I did want to illustrate, however, that I do certainly see some benefit. Using the escape character might mitigate much of the risk. Admittedly, environment variable are often not set in various contexts, so perhaps just a very limited subset as discussed above would be a good start. I hope that is useful. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 451018] Slack users on KDE Plasma unable to open workspace in desktop app via Chromium based browsers
https://bugs.kde.org/show_bug.cgi?id=451018
Michael Mikowski changed:
What|Removed |Added
CC||z_mikow...@yahoo.com
--- Comment #3 from Michael Mikowski ---
(In reply to Nate Graham from comment #2)
> I agree with Nicolas (amazing investigation, BTW!). Slack itself should be
> fixed here. If not, trying a Qt fix would be the better option that changing
> openUrlJob and everything that uses it.
Here is a work-around. Drop it in /usr/local/bin/xdg-open so it gets opened
first. You will need to make it executable.
#!/bin/bash
# Wrapper for xdg-open which fixes auth for Slack URLs
#
if [[ "${1:-}" =~ ^slack:// ]]; then
exec /usr/lib/slack/slack "$@";
fi
exec /usr/bin/xdg-open "$@";
--
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 --- Comment #8 from Michael Mikowski --- Created attachment 152980 --> https://bugs.kde.org/attachment.cgi?id=152980=edit 6. Compare Position, Horizontal -- 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 --- Comment #7 from Michael Mikowski --- Created attachment 152979 --> https://bugs.kde.org/attachment.cgi?id=152979=edit 5. Horizontal Layout after Relogin -- 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 --- Comment #6 from Michael Mikowski --- Created attachment 152978 --> https://bugs.kde.org/attachment.cgi?id=152978=edit 4. Horizontal Layout in 4k -- 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 --- Comment #5 from Michael Mikowski --- 1. Per bug 458038, I tried running `plasma-shell --replace` and it did indeed fix the problem, but it took forever - somewhere around 30s. I have not confirmed if this always works. 2. I tried with a horizontal layout too, with similar results. New screen screenshots incoming. 3. Out of 12 tests: 3a. 2 times: Widgets immediately appeared in their correct positions (screenshots 1 + 4) on relogin 3b. 8 times: Widgets immediately appeared "broken" positions (screenshots 2 + 5) on relogin and stayed there 3c. 2 times: Widgets immediately appeared "broken" as above, but around 30s later, the layout abruptly reset to the correct layout. The behavior appears identical to point 1, above. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #68 from Michael Mikowski --- During testing of 5.24.7 on Kubuntu 22.04 LTS, this has remained in place. Aaron Rainbolt, Riccardo Robecchi, Nate Graham: I have created a new bug 460618 to track and added you to the CC list. -- 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 Michael Mikowski changed: What|Removed |Added CC||sephiroth...@hotmail.it -- 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 Michael Mikowski changed: What|Removed |Added CC||arraybo...@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 Michael Mikowski changed: What|Removed |Added CC||n...@kde.org, ||z_mikow...@yahoo.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 --- Comment #2 from Michael Mikowski --- Created attachment 152960 --> https://bugs.kde.org/attachment.cgi?id=152960=edit 3. Compare Positions -- 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 --- Comment #1 from Michael Mikowski --- Created attachment 152959 --> https://bugs.kde.org/attachment.cgi?id=152959=edit 2. Layout after relogin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460618] New: Can't remember desktop widget positions after relogin
https://bugs.kde.org/show_bug.cgi?id=460618 Bug ID: 460618 Summary: Can't remember desktop widget positions after relogin Classification: Plasma Product: plasmashell Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: z_mikow...@yahoo.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 152958 --> https://bugs.kde.org/attachment.cgi?id=152958=edit 1. Original Layout in 4K SUMMARY STEPS TO REPRODUCE 1. Place widgets on the desktop 2. Log out 3. Log in OBSERVED RESULT Widgets move, even with no change in screen or resolution. EXPECTED RESULT Widgets should be restored to exact prior location. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98 Qt Version: 5.15.3 ADDITIONAL INFORMATION This is a continuation of bug 413645. I was hoping this was fixed in 5.24.7, but it was trivial to recreate. This problem seems more likely to occur with HDPI panels, however, some have noted that this is also a problem at 1080p (bug 413645 comment 66). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #41 from Michael Mikowski --- (In reply to Nate Graham from comment #40) > The issue only affected Plasma 5.25+Frameworks 5.98. The combination of > Plasma 5.24+Frameworks 5.98 isn't affected. > > Regardless, patching this fix into your 5.98 and then later shipping the > re-spun 5.98 is highly recommended! Thanks Nate! I'll pass that along! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #39 from Michael Mikowski --- (In reply to Nate Graham from comment #38) > ^^ That should fix it for people with Plasma 5.25 > > The fix will officially land in Frameworks 5.99 and we're coordinating to > have a re-spin of Frameworks 5.98 released. Even if that doesn't end up > happening (but I think it will), distros will be patching this in directly > ASAP. Nate, can you or another confirm if this is or is not recommended for Frameworks 5.98 + Plasma 5.24 LTS? As posted in comment 24, I didn't see any problems with this combination. I tried to copy Rik Mills for Kubuntu, but can't find him on the CC list. He certainly would be interested as that is the current state of Kubuntu + backports. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 Michael Mikowski changed: What|Removed |Added CC||z_mikow...@yahoo.com --- Comment #24 from Michael Mikowski --- Could not reproduce pop-up placement issue on 5.24.6 with Frameworks 5.98. Details below: 1. Left and Right-click Kickoff. Pop-up is aligned as expected. 2. alt-space to launch krunner. Placement is top center as expected. 3. Right-click on other icons in panel. Placement is as expected. 4. System Tray: Left-click on plasma-optimus, ibus panel, volume, wifi, klipper, bluetooth, and solaar widgets. All pop-ups are placed as expected. KDE Plasma 5.24.6 KDE Frameworks 5.98.0 QT Version 5.15.3 Kernel: 5.17.0-1016-oem Graphics Platform: Wayland Hardware: i7-1165G7 Memory: 32GB GPU: Mesa Intel Xe Graphics (96 EU) Additional system details at https://invent.kde.org/-/snippets/2348 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 --- Comment #6 from Michael Mikowski --- Hi Bug Triage: I know this is very similar to other bugs, however, we tried to be as precise as possible and eliminate unknowns to help sort our what could be the issue. For example, we were sure to note our DPI settings (default, not set) and global scale (default, 100%). We also used a very common theme (Breeze Dark) to avoid any interference from any custom layouts. We also reproduced this with manually placed widgets to avoid any possibility that this could be layout-induced. We filed specifically against 5.24.5 LTS, and we added annotated screen shots as well. I hope you find this useful. Sincerely, Mike -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 --- Comment #5 from Michael Mikowski --- Created attachment 150497 --> https://bugs.kde.org/attachment.cgi?id=150497=edit 05-layout-widgets-post.jpg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 --- Comment #4 from Michael Mikowski --- Created attachment 150496 --> https://bugs.kde.org/attachment.cgi?id=150496=edit 04-layout-widgets-pre.jpg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 --- Comment #3 from Michael Mikowski --- Created attachment 150495 --> https://bugs.kde.org/attachment.cgi?id=150495=edit 03-manual-widgets.jpg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 Michael Mikowski changed: What|Removed |Added Attachment #150494|Screen Configuration|02-screens.jpg description|| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 Michael Mikowski changed: What|Removed |Added Attachment #150492|System Snapshot |00-system.jpg description|| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 Michael Mikowski changed: What|Removed |Added Attachment #150493|Fonts DPI |01-fonts-dpi.jpg description|| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 --- Comment #2 from Michael Mikowski --- Created attachment 150494 --> https://bugs.kde.org/attachment.cgi?id=150494=edit Screen Configuration -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 --- Comment #1 from Michael Mikowski --- Created attachment 150493 --> https://bugs.kde.org/attachment.cgi?id=150493=edit Fonts DPI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] New: Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 Bug ID: 456497 Summary: Icons and Widgets Move on Second Monitor Product: plasmashell Version: 5.24.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: z_mikow...@yahoo.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 150492 --> https://bugs.kde.org/attachment.cgi?id=150492=edit System Snapshot SUMMARY: Icons and Widgets Move After Logout DESCRIPTION: When using a 4K monitor as the primary display, logging in and back out moves widgets and icons on the desktop file. STEPS TO REPRODUCE 1. Attach a 4K display to the system and boot up. - DO NOT change DPI or global scaling See 01-fonts-dpi.jpg and 02-screens.jpg 2. Set 4K display as primary, see 02-screens.jpg 3. Place widgets on the desktop 4. Logout and back in. OBSERVED RESULT 1. Notice widgets have moved substantially, see 03-manual-widgets.jpg 2. Themed layouts show the same behavior as shown in 04-layout-widgets-pre.jpg and 05-layout-widgets-post.jpg EXPECTED RESULT Widgets should NOT move from their placements. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 See 00-system.jpg for more details. ADDITIONAL INFORMATION Running Plasma over X: xserver-xorg/jammy,now 1:7.7+23ubuntu2 This is reproducible over all 5 laptop hardware platforms running this software load. The laptop panel show here is QHD, but we have seen similar behavior with FHD. We have also observed similar behavior on a single panel QHD laptop. Related tickets: 456049 marked duplicate of 425368 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize
https://bugs.kde.org/show_bug.cgi?id=456049 Michael Mikowski changed: What|Removed |Added CC||z_mikow...@yahoo.com --- Comment #5 from Michael Mikowski --- A few additional observations: 1. This occurs with the official Breeze Dark theme. 2. This occurs with themed layouts OR when widgets are added manually to the desktop. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]
https://bugs.kde.org/show_bug.cgi?id=453752 Michael Mikowski changed: What|Removed |Added Summary|Effects Settings from |Effects Settings from |XDG_CONFIG_DIRS are discard |XDG_CONFIG_DIRS are |when user clicks on |discarded when user clicks |[Defaults] |on [Defaults] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discard when user clicks on [Defaults]
https://bugs.kde.org/show_bug.cgi?id=453752 Michael Mikowski changed: What|Removed |Added Summary|Effects Settings do |Effects Settings from ||XDG_CONFIG_DIRS are discard ||when user clicks on ||[Defaults] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453752] New: Effects Settings do
https://bugs.kde.org/show_bug.cgi?id=453752 Bug ID: 453752 Summary: Effects Settings do Product: systemsettings Version: 5.24.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_effects Assignee: kwin-bugs-n...@kde.org Reporter: z_mikow...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** Click on Defaults in `kcmshell5 kcm_kwin_effects` results in apparently hard-coded defaults, not those defined in the `kf5-config --path config` hierarchy. *** STEPS TO REPRODUCE 1. Install Kubuntu 22.04 2. Edit `/usr/share/kubuntu-default-settings/kf5-settings` to include the following: [Plugins] wobblywindowsEnabled=true 3. Log out and back in. Open `kcmshell5 kcm_kwin_effects` and notice that wobbly windows are indeed enabled (this is not default on stock KDE). 4. Click on the [Defaults] button in the GUI. OBSERVED RESULT The wobbly window option erased and there is no simple or easy way for the user to recover the intent from the config path. EXPECTED RESULT I think that clicking on [Defaults] should honor the `kf5-config --path config` so that, for example, Kubuntu defaults can be recovered. Alternately, there may be a system-default vs. KDE defaults option, maybe with a pulldown button so as to not further clutter the interface. The preferred default should be the config path so as to retain the distribution or vendor intent IMO. SOFTWARE/OS VERSIONS Windows: no macOS: no Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION We see similar behavior with kglobalshortcutsrc. However, in this case, these don't even get APPLIED during run. KDE apparently inserts a .config/kdedefaults directory in the config path after changes to the settings, which is also inserted into the xdg-config path before any system paths. There may be some overlap there. I am at your service to provide additional testing and assistance. Just let me know if there is any way I can help to get this resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451056] Kwin-X11 Windows Resize, Position, and Move Erratically
https://bugs.kde.org/show_bug.cgi?id=451056 Michael Mikowski changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451056] Kwin-X11 Windows Resize, Position, and Move Erratically
https://bugs.kde.org/show_bug.cgi?id=451056 --- Comment #2 from Michael Mikowski --- At present, the windows appear to behaving well with the latest point update (5.24.2 => 5.24.3). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451056] Kwin-X11 Windows Resize, Position, and Move Erratically
https://bugs.kde.org/show_bug.cgi?id=451056 Michael Mikowski changed: What|Removed |Added CC||z_mikow...@yahoo.com --- Comment #1 from Michael Mikowski --- 1. NO IMPROVEMENT: Turned off fractional scaling + no forced DPI. 2. IMPROVED: Turned off fractional scaling + FORCED DPI to 96. This appears to FIX issues A-D. In addition, turning off the compositor no longer results in a large black border where the window shadow used to be. I recognize this may be related to a recent software upgrade as well. I will try this with 96 DPI and fractional scaling and report back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451056] New: Kwin-X11 Windows Resize, Position, and Move Erratically
https://bugs.kde.org/show_bug.cgi?id=451056 Bug ID: 451056 Summary: Kwin-X11 Windows Resize, Position, and Move Erratically Product: kwin Version: 5.24.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: z_mikow...@yahoo.com Target Milestone: --- SUMMARY Kwin is showing the following anomalies. These are not constant, but occur frequently (10-20 times) per day. They all appear to be associated with a scaling issue, so I have grouped them here. I will work to provide a better guide to reproduce as I find out more. Driver package is nvidia-driver-470. STEPS TO REPRODUCE 1. Run Jammy with multiple 4K monitors attached. I've tried this with a high font DPI setting (System Settings > Fonts > Force DPI = 144) and fractional scaling (System Settings > Displays > Global Scale = 150%). These symptoms occur in either setting. I have not confirmed if this works without either. 2. Launch an app such as konsole or google-chrome (the latter seems highly susceptible). 3. Tile and drag windows. This results in issues (1), (2), and (3), above. 4. Drag a tab from konsole or firefox into an empty space. The window will be placed incorrectly even if the area dragged to is completely open. 5. Turning off compositing (alt+shift+f12) results in window being sized to include a large black border (around 50px) which presumably is the shadow size. This border is ignored when tiling or using the maximize button. But it is included in window size when using vertical maximize and horizontal maximize. OBSERVED RESULT A. When moving windows, the window will not move with the cursor but will continue to move the window further downwards on the screen even as the cursor is pushed further up. In fact, the speed at which a window moves down appears proportional to the upward movement of the cursor. B. Windows that are moved as in (1) will often "slide off screen" and are inaccessible using the cursor although they still exist in the panel. Windows include IntelliJ Pro, Google Chrome, Konsole. C. Windows that have been tiled (e.g. press meta + arrow key) when moved by dragging the title bar, will vertically collapse to only the height of the title bar. After dropping this title bar, one cannot select or move it again from the screen. Windows include IntelliJ Pro, Google Chrome, Konsole D. Windows spawned by dragging a tab from one window onto an empty space (e.g. dragging a tab from a firefox browser or konsole session onto an empty space on the desktop) are placed badly - usually far away from the intended location, and sometimes off-screen as in (2). EXPECTED RESULT A and B. Moving windows should follow the cursor and not 'slide off screen' where they are inaccessible. C. Windows show maintain their size or pre-tiling size when moving, and should not collapse to title-bar height. D. Windows spawned from another window tab like konsole or firefox, should be created in the area of the cursor, not off screen. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.15.0-18-lowlatency (64-bit) Graphics Platform: X11 Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 ADDITIONAL INFORMATION Downstream Kubuntu bug: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1962621 All kwin settings are defaults. No kwin scripts are installed or used. SPECULATION Scaling is not applied correctly to window moving or sizing? Font DPI is not applied correctly to window moving or sizing? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393596] Discover crash
https://bugs.kde.org/show_bug.cgi?id=393596 Michael Mikowski changed: What|Removed |Added CC||z_mikow...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account
https://bugs.kde.org/show_bug.cgi?id=364802 Michael Mikowski <z_mikow...@yahoo.com> changed: What|Removed |Added CC||z_mikow...@yahoo.com --- Comment #3 from Michael Mikowski <z_mikow...@yahoo.com> --- I also ran into this problem today, but it might just be a problem with Google Imap because now works. Can you try auto-detecting the server under Settings -> Configure Kmail -> Accounts -> Receiving -> Modify (selected account) -> Advanced -> Auto Detect (under Connection Settings)? Does it now work? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 340540] Folder Archive does not archive on Archive selection
https://bugs.kde.org/show_bug.cgi?id=340540 Michael Mikowski <z_mikow...@yahoo.com> changed: What|Removed |Added CC||z_mikow...@yahoo.com --- Comment #4 from Michael Mikowski <z_mikow...@yahoo.com> --- Confirmed here as well. Archiving a folder fails for every folder I try on both active and disabled IMAP accounts. It doesn't work for Local folders either. I too am trying to archive an imap account (Exchange 2008 server - not my choice :P ) that did NOT have "download messages for offline use" set but is now defunct. I want to store whatever information I currently have into an archive. Is there any way to do this? Interestingly, I was able to copy a second account (Gmail server) with the exact same settings to a backup folder without difficulty by selecting the account "folder", e.g. "Gmail", right-clicking, and then selecting -> Copy folder to and then selecting a local backup folder. When I try that with the (Exchange) IMAP account, it silently fails. v5.02 Using: KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
