[kwin] [Bug 487409] LG monitor hotplug on DPMS power on causes several applications to resize their windows
https://bugs.kde.org/show_bug.cgi?id=487409 Christopher Snowhill changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #4 from Christopher Snowhill --- Fine, since you didn't accept my submitted info, I'll just close this and cease using Plasma. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487409] LG monitor hotplug on DPMS power on causes several applications to resize their windows
https://bugs.kde.org/show_bug.cgi?id=487409 --- Comment #2 from Christopher Snowhill --- (In reply to Zamundaaa from comment #1) > Are the misbehaving windows tiled in any way before the screens turn off? > There's a whole bunch of fixes related to that + hotplugs in 6.0.5 They are not tiled, they are merely scattered around my primary display. > > > Desktop should make an attempt to absorb the DRM event and seed a new DRM > > surface handle to the compositor. > Delaying drm events by multiple seconds is not an option, and wouldn't > reliably fix this either. No, the compositor needs to handle hotplug events > properly, and KWin does have a bunch of code in place to do so. You're right. But there's probably no adequate solution to this that also won't have some form of jank. If I'd known what I know about this monitor now, I probably wouldn't have bought it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487409] New: LG monitor hotplug on DPMS power on causes several applications to resize their windows
https://bugs.kde.org/show_bug.cgi?id=487409 Bug ID: 487409 Summary: LG monitor hotplug on DPMS power on causes several applications to resize their windows Classification: Plasma Product: kwin Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: kod...@gmail.com Target Milestone: --- SUMMARY I have an LG 24UD58-B monitor (3840x2160@60Hz) and a Dell P2414H (1920x1080@60Hz), and when the two monitors DPMS cycle off, everything is fine. When the LG monitor powers back on, due to a bug in its deep sleep state, it causes a DRM hotplug event, which causes only that monitor to bounce out of the desktop layout. This causes all my windows to pop over to a desktop that's one quarter of the size and half the scale of the primary display. The only applications I have right now which are affected oddly by this are Steam (XWayland) and WezTerm (Wayland). Steam shrinks so its window now fits into the top left quarter of the screen, while WezTerm shrinks itself to the minimum allowed window size and becomes unusable until I resize it again. STEPS TO REPRODUCE 1. Acquire the listed monitors, any video card to drive them, but AMDGPU in this case. 2. Allow DPMS to cycle the displays off completely. 3. Move the mouse to cycle them on. OBSERVED RESULT Windows move around, some of them shrink, others shrink unusably. EXPECTED RESULT Desktop should make an attempt to absorb the DRM event and seed a new DRM surface handle to the compositor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, kernel 6.9.1-2-cachyos (64-bit) (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Bug is a minor nuisance, but at least better than whole apps crashing on monitor hotplug like some other desktops on the machine do. It would be nice if a slight delay could be added to actual hotplug events to coalesce a monitor disappearing for just a moment into a DRM handle refresh. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478838] Plasmashell sometimes crashes in QPlatformWindow::hasPendingUpdateRequest() after or during screen being turned off
https://bugs.kde.org/show_bug.cgi?id=478838 Christopher Snowhill changed: What|Removed |Added CC||kod...@gmail.com --- Comment #14 from Christopher Snowhill --- Confirmed crash on Arch packaged Plasma Wayland. Two monitors: LG 24UD58-B, which disconnects itself momentarily when it's resumed from DPMS off, whether HDMI or DisplayPort; and a Dell P2414H, which maintains a steady connection regardless of DPMS state, connected by DisplayPort, as it has no HDMI inputs. Backtrace, resolved with debuginfod as best I could: ``` #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f17380ab393 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f173805a6c8 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f173aed943f in KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kcrash/kcrash-6.0.0/src/kcrash.cpp:586 #4 0x7f173805a770 in () at /usr/lib/libc.so.6 #5 0x7f1738db4245 in QPlatformWindow::hasPendingUpdateRequest (this=0x56c294528500) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/gui/kernel/qplatformwindow.cpp:765 #6 0x7f173abf1acb in operator() (__closure=0x56c295ede0f0) at /usr/src/debug/qt6-wayland/qtwayland-everywhere-src-6.7.0/src/client/qwaylandwindow.cpp:1648 #7 QtPrivate::FunctorCall, QtPrivate::List<>, void, QtWaylandClient::QWaylandWindow::requestUpdate():: >::call (arg=, f=...) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137 #8 QtPrivate::FunctorCallable >::call, void> (arg=, f=...) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:345 #9 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x56c295ede0e0, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555 #10 0x7f17387883e4 in QObject::event (this=0x56c2945284f0, e=0x56c294020930) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:1446 #11 0x7f173a4fbfcb in QApplicationPrivate::notify_helper (this=, receiver=0x56c2945284f0, e=0x56c294020930) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287 #12 0x7f173873dae8 in QCoreApplication::notifyInternal2 (receiver=0x56c2945284f0, event=event@entry=0x56c294020930) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1134 #13 0x7f173873de74 in QCoreApplication::sendEvent (event=0x56c294020930, receiver=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1575 #14 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x56c28fd34ba0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1932 #15 0x7f17389860e4 in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1789 #16 postEventSourceDispatch (s=0x56c28fd62a90) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qeventdispatcher_glib.cpp:244 #17 0x7f17372cf199 in g_main_dispatch (context=0x7f172c000f00) at ../glib/glib/gmain.c:3344 #18 0x7f173732e3bf in g_main_context_dispatch_unlocked (context=0x7f172c000f00) at ../glib/glib/gmain.c:4152 #19 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x7f172c000f00, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4217 #20 0x7f17372ce712 in g_main_context_iteration (context=0x7f172c000f00, may_block=1) at ../glib/glib/gmain.c:4282 #21 0x7f1738983df4 in QEventDispatcherGlib::processEvents (this=0x56c28ffb8620, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qeventdispatcher_glib.cpp:394 #22 0x7f1738745c7e in QEventLoop::processEvents (flags=..., this=0x7fff594a6750) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qeventloop.cpp:100 #23 QEventLoop::exec (this=0x7fff594a6750, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qeventloop.cpp:182 #24 0x7f17387416e8 in QCoreApplication::exec () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/global/qflags.h:74 #25 0x7f173a4f851a in QApplication::exec () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:2555 #26 0x56c28e3e7476 in main (argc=, argv=) at /usr/src/debug/plasma-workspace/plasma-workspace-6.0.3/shell/main.cpp:214 ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480991] Windows resize oddly when 200% scaled monitor hot-replugs itself
https://bugs.kde.org/show_bug.cgi?id=480991 --- Comment #2 from Christopher Snowhill --- Created attachment 165654 --> https://bugs.kde.org/attachment.cgi?id=165654=edit Wezterm Wayland debug log Here's a log from the terminal being launched from Konsole with WAYLAND_DEBUG=1, locking my displays, letting them power off, then waking and unlocking them, then resizing the window back to a usable size again, then closing it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480991] New: Windows resize oddly when 200% scaled monitor hot-replugs itself
https://bugs.kde.org/show_bug.cgi?id=480991 Bug ID: 480991 Summary: Windows resize oddly when 200% scaled monitor hot-replugs itself Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kod...@gmail.com Target Milestone: --- SUMMARY *** I have my desktop configured with an LG 24UD58-B 3840x2160@60Hz monitor, set to 200% scaling, either on HDMI or DisplayPort, it will do this on either one. And a Dell P2414H at 1920x1080@60Hz at 100% scaling, over DisplayPort. When my primary monitor is put into DPMS power off state, and successfully turns itself off after displaying the "power save" notice, it does something odd when powering back on. At the instant the operating system powers it back on with DPMS controls, it hot detaches itself from DRM, then needs to be re-attached. This causes a video mode change, possibly causing scaling to temporarily reset to 100% and back to 200% again. This has the effect of causing several of my desktop windows to resize themselves. Wezterm in Wayland mode shrinks to a tiny box. Firefox, in its Wayland mode, maintains its size for the most part. Discord, an Electron app running in Xwayland mode, grows its window frame to 200% of its original size, but the content remains its original size in the top left corner of the window frame, while the rest of the window frame becomes transparent to what's underneath of it, and also becomes transparent to clicking in those empty regions. When resizing this Electron window's frame, or using the Super+Right button resize on a non-transparent region of the window contents, the window contents suddenly grow to the full size of the 200% scaled window frame. I have to shrink this Electron app every time I log back into my desktop, and grow the size of Wezterm to a usable size as well. STEPS TO REPRODUCE 1. Have a 200% scaled monitor that does the above indicated DPMS dance every time it's powered back on, and a 100% scaled monitor to the right of it, which does not do any sort of port resetting when restored to powered on state. 2. Start some of the above mentioned apps, and arrange their windows in a semblance of normalcy. 3. Lock the screen. 4. Press the Escape key to DPMS power off. 5. Wait for the display to fully power off. 6. Move the mouse or press a key to power back on. 7. Unlock the desktop. OBSERVED RESULT Several different apps, depending on GTK+, Qt, Electron, either Xwayland or Wayland native, will be resized oddly, in somewhat consistent ways depending on what type of app it is. EXPECTED RESULT Windows should maintain their original size as they had prior to the video mode change, considering the mode change was same mode to same mode, but maybe had an inconsistent mode in between due to the DPMS power cycling and subsequent DRM mode reset. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux rolling, testing repositories enabled KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION None that I can think of. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472795] Miscellaneous problems with Edit Duration
https://bugs.kde.org/show_bug.cgi?id=472795 Christopher Snowhill changed: What|Removed |Added CC||kod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472795] New: Miscellaneous problems with Edit Duration
https://bugs.kde.org/show_bug.cgi?id=472795 Bug ID: 472795 Summary: Miscellaneous problems with Edit Duration Classification: Applications Product: kdenlive Version: 23.04.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kod...@gmail.com Target Milestone: --- SUMMARY The video clip Edit Duration dialog is somewhat broken. While the Crop Start, Duration, and Crop End fully allow editing by typing in numbers, the Start Position field appears to only accept numbers in the hours field, and automatically reverts the minutes, seconds, and frames fields to whatever they were before typing. Scrolling the fields is similarly broken, as it seems to only allow scrollwheel response to the seconds and frames fields, stopping at 00,00. The Start Position field also seems to have a completely arbitrary idea of what the minimum start position for a video clip should be, and it's usually at least 10 minutes into an otherwise empty video, or sometimes 90+ minutes in, in the case of the audio for this clip I'm trying to crop. STEPS TO REPRODUCE 1. Open a 2+ hour long webm as a clip 2. Attempt to crop it down using the Edit Duration dialog OBSERVED RESULT Be baffled as the dialog appears to enforce arbitrary limits on the Start Position. EXPECTED RESULT The start position should have no such limits placed on it, especially when the video timeline is otherwise empty. SOFTWARE/OS VERSIONS Linux/KDE Plasma: I am running this under GNOME, I guess that's not a supported configuration? I have all of Plasma installed. KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I guess I should just use a video player to find the timestamps I want and use ffmpeg to crop the video instead. I'm basically shooting myself in the foot by expecting a non-linear editor to do simple tasks like crop a two hour video down to one minute or less. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470400] New: Panel, deleted, then restored, gets stuck halfway up the screen until panel is restarted
https://bugs.kde.org/show_bug.cgi?id=470400 Bug ID: 470400 Summary: Panel, deleted, then restored, gets stuck halfway up the screen until panel is restarted Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kod...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY On my system, where it may be relevant that the screen is 3840x2160 with a scale factor of 200%, and a second screen, which is 1920x1080, scaled to 100%, on Wayland, experiences an issue when accidentally deleting and then undoing deletion of the bottom panel. STEPS TO REPRODUCE 1. Enter edit mode on the default bottom panel 2. Right click the panel, remove it. 3. Click the undo button on the balloon that pops up. OBSERVED RESULT Panel restores itself vertically centered on the screen, just above the center. Possibly with some of its widgets rearranged. Panel cannot be moved to the bottom of the screen, and the editor thinks it is already on the bottom of the screen. EXPECTED RESULT Panel should restore to the bottom of the screen. Panel should restore its original arrangement of widgets. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, KDE Plasma 5.27.5 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION This may or may not be related to screen scale factor, or Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470399] New: Plasmoid tooltip opens under cursor and moves away from cursor, closing itself
https://bugs.kde.org/show_bug.cgi?id=470399 Bug ID: 470399 Summary: Plasmoid tooltip opens under cursor and moves away from cursor, closing itself Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kod...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY A plasmoid, [Event Calendar](https://store.kde.org/p/998901/), opens tooltips to show holidays on the visible calendar. These tooltips can be made to spawn and animate through the cursor, repeatedly opening and closing themselves. STEPS TO REPRODUCE 1. Install the Plasmoid. 2. Add it to the Panel. 3. Add a calendar with holidays in the current month. (US calendar with Memorial Day, for instance.) 4. Open the Plasmoid by clicking it. 5. Move the cursor up and to the left, over a cell with a holiday or event. 6. Hover over the cell. OBSERVED RESULT Tooltip spawns from the bottom right of the Plasmoid, causing it to animate directly under the cursor and away from it again, which causes the tooltip to self-terminate. The cursor focus being interrupted from the cell by the tooltip passing under it also causes the hover action to activate another tooltip, repeatedly, until the cursor is moved off the calendar cell. EXPECTED RESULT Tooltip should not check for cursor focus until it has come to rest after animating itself open. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, KDE Plasma 5.27.5 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Mentioned plasmoid may or may not be to blame for the issue, but animating open a window which hides itself when a cursor moves over or off it, should not test for cursor hover until its animation cycle completes. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443745] Discover crashes in FlatpakBackend::findSource() when going to the Installed page
https://bugs.kde.org/show_bug.cgi?id=443745 --- Comment #53 from Christopher Snowhill --- Created attachment 151750 --> https://bugs.kde.org/attachment.cgi?id=151750=edit discover backtrace from coredumpctl gdb Sorry about that, I should have attached this in the first place. Not sure if it's the same crash, and if it's not, I'll open a new report. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443745] Discover crashes in FlatpakBackend::findSource() when going to the Installed page
https://bugs.kde.org/show_bug.cgi?id=443745 Christopher Snowhill changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||kod...@gmail.com --- Comment #51 from Christopher Snowhill --- Still happening with 5.25.4, with the only Flatpak source added being flathub, on Arch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433139] KWin_wayland crashes on monitor disconnect
https://bugs.kde.org/show_bug.cgi?id=433139 Christopher Snowhill changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433139] KWin_wayland crashes on monitor disconnect
https://bugs.kde.org/show_bug.cgi?id=433139 --- Comment #5 from Christopher Snowhill --- I may as well close this, then. My distribution doesn't provide debugging symbols, so the entire backtrace is a single function call address and nothing else. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433486] Set multi-monitor mode to "Unify outputs", disconnect external monitor, turn it off and reconnect it: Plasma crashes.
https://bugs.kde.org/show_bug.cgi?id=433486 Christopher Snowhill changed: What|Removed |Added CC||kod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
https://bugs.kde.org/show_bug.cgi?id=419728 Christopher Snowhill changed: What|Removed |Added CC||kod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419759] Set multi-monitor mode to "Unify outputs", disconnect external monitor, turn it off and reconnect it: kwin_wayland crashes.
https://bugs.kde.org/show_bug.cgi?id=419759 Christopher Snowhill changed: What|Removed |Added CC||kod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433139] New: KWin_wayland crashes on monitor disconnect
https://bugs.kde.org/show_bug.cgi?id=433139 Bug ID: 433139 Summary: KWin_wayland crashes on monitor disconnect Product: kwin Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kod...@gmail.com Target Milestone: --- SUMMARY KWin_wayland segfaults when any monitor is disconnected, such as when my LG 24UD58-B goes into DPMS power save mode when the screen saver activates. It reconnects itself when DPMS re-powered. STEPS TO REPRODUCE 1. Log into Plasma Wayland session. 2. Lock the screen and wait for the screen saver to power the monitors off. 3. Wake the desktop and unlock the screen. OBSERVED RESULT Kwin crashes, and the session is restored from scratch. EXPECTED RESULT The session continues unabated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.11.0-122 (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION kwin_wayland produced an absolutely useless backtrace log. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397834] Native Firefox/Wayland port works poorly on Wayland Plasma
https://bugs.kde.org/show_bug.cgi?id=397834 Christopher Snowhill changed: What|Removed |Added CC||kod...@gmail.com --- Comment #27 from Christopher Snowhill --- Two more months, any additional news? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389990] Some icons are badly rendered on system tray
https://bugs.kde.org/show_bug.cgi?id=389990 Christopher Snowhill changed: What|Removed |Added CC||kod...@gmail.com --- Comment #7 from Christopher Snowhill --- I'm experiencing a similar issue with tray icons, only killing xembedsniproxy had no effect, as all icons remained. The issue appears as icons that were added minutes after login instead of by auto started applications on login, the icons render as twice as large as they should be, and the tray only shows the center quarter of the actual icon. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 393181] Baloo uses 100% CPU. Never ending indexing while it is only one file left.
https://bugs.kde.org/show_bug.cgi?id=393181 Christopher Snowhill changed: What|Removed |Added CC||kod...@gmail.com --- Comment #5 from Christopher Snowhill --- If I have this issue, where should I find this database, and where can I send it for debugging? I had to disable indexing on Kubuntu 18.04.1 because they apparently never applied this patch. Maybe it’s applied in 18.10, which I recently installed. I’d still like to know if it’s a corrupt database. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 399582] New: I18N_EXCESS_ARGUMENTS_SUPPLIED message
https://bugs.kde.org/show_bug.cgi?id=399582 Bug ID: 399582 Summary: I18N_EXCESS_ARGUMENTS_SUPPLIED message Product: ksysguard Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: kod...@gmail.com Target Milestone: --- SUMMARY The CPU usage tooltip displays a (I18N_EXCESS_ARGUMENTS_SUPPLIED) message below both of the CPU time spent running as... messages. STEPS TO REPRODUCE 1. Open KSysGuard 2. Switch to the Process Table tab. 3. Hover the pointer over the CPU % column value for any process. OBSERVED RESULT Tooltip displays spurious warning. EXPECTED RESULT Unknown, not sure if it's appending that message to the CPU time, or if it's replacing another message which should be there. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Using the current Kubuntu 18.04.1 packages. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 398005] KDE session fails to restart ssh-agent on log out -> log in cycle
https://bugs.kde.org/show_bug.cgi?id=398005 --- Comment #2 from Christopher Snowhill --- Created attachment 114669 --> https://bugs.kde.org/attachment.cgi?id=114669=edit Patched Xsession.d script that fixes the issue -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 398005] KDE session fails to restart ssh-agent on log out -> log in cycle
https://bugs.kde.org/show_bug.cgi?id=398005 --- Comment #1 from Christopher Snowhill --- This is probably not a KDE bug, but instead an Xsession script bug. Ah, yeah, the script in question is provided by x11-common. I'll see if I can report it to them. Here's the workaround anyway, if anyone finds this incorrect bug report before I launch one against x11-common on Ubuntu. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 398005] KDE session fails to restart ssh-agent on log out -> log in cycle
https://bugs.kde.org/show_bug.cgi?id=398005 Christopher Snowhill changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 398005] New: KDE session fails to restart ssh-agent on log out -> log in cycle
https://bugs.kde.org/show_bug.cgi?id=398005 Bug ID: 398005 Summary: KDE session fails to restart ssh-agent on log out -> log in cycle Product: kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kod...@gmail.com Target Milestone: --- On Kubuntu Desktop, KDE Plasma session fails to re-launch ssh-agent upon logging out and logging back in again. The SSH Agent environment variables for the previous session persist. Package: plasma-desktop Version: 4:5.12.6-0ubuntu0.1 -- You are receiving this mail because: You are watching all bug changes.
