[plasmashell] [Bug 480516] New: During Panel size edit, mouse hovering over the Panel causes Panel edit mode to close
https://bugs.kde.org/show_bug.cgi?id=480516 Bug ID: 480516 Summary: During Panel size edit, mouse hovering over the Panel causes Panel edit mode to close Classification: Plasma Product: plasmashell Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: darinsmil...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Enter Edit Mode 2. Open Panel Settings 3. Select Length -> Custom 4. Hover mouse over resized panel and watch Panel Setting disappear OBSERVED RESULT Panel edit mode suddenly closes EXPECTED RESULT Panel edit mode should remain open until manually closed. SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.92.90 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-15-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: Dell Inc. Product Name: Inspiron 7559 System Version: 1.3.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479326] With Qt 6.6.1 or later, changing the sorting criteria of the process table to another column is very difficult
https://bugs.kde.org/show_bug.cgi?id=479326 --- Comment #11 from Darin Miller --- (In reply to Nate Graham from comment #7) > Thanks. Are all affected people using NVIDIA GPUs? Using a hybrid laptop, video mode was set to "NVidia on Demand". Switched to Intel only via prime-select, rebooted and sort still failed. In fact, I had to click 30 to 40 times on column titles to initiate a single sort... -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 480443] New: Plasma system monitor clicking column header to sort does not always work
https://bugs.kde.org/show_bug.cgi?id=480443 Bug ID: 480443 Summary: Plasma system monitor clicking column header to sort does not always work Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: darinsmil...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. meta-esc to open system monitor 2. Select Process or Applications tab 3. click any column header other than the currently sorted column and note that sort does not change. OBSERVED RESULT Columns are not sorted as expected EXPECTED RESULT Expect column sort to toggle for the respective selected column. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.92.90 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-15-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: Dell Inc. Product Name: Inspiron 7559 System Version: 1.3.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480408] Plasma height customization broken when panel is on left side of screen
https://bugs.kde.org/show_bug.cgi?id=480408 Darin Miller changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Darin Miller --- The panel Alignment setting was Centered. Today I woke the PC and Plamsa had crashed and upon Plasma restart the panel now respects the location of the sizing set the day before. Also, sizing the panel now respond resize events but the response animation is delayed and a bit "stuttery". I also see the Panel crash when mouse cursor touches the Panel and once the custom Length is selected. So, for now the user must customize other panel configs (i.e. widget locations and widget removal) prior to setting the length. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480408] Plasma height customization broken when panel is on left side of screen
https://bugs.kde.org/show_bug.cgi?id=480408 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480408] Plasma height customization broken when panel is on left side of screen
https://bugs.kde.org/show_bug.cgi?id=480408 Darin Miller changed: What|Removed |Added Summary|Plasma height customization |Plasma height customization |broken when is on left side |broken when panel is on |of screen |left side of screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480408] New: Plasma height customization broken when is on left side of screen
https://bugs.kde.org/show_bug.cgi?id=480408 Bug ID: 480408 Summary: Plasma height customization broken when is on left side of screen Classification: Plasma Product: plasmashell Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: darinsmil...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Enter Edit Mode 2. Select Panel Settings 3. Select Length -> Custom OBSERVED RESULT Bottom of Panel can be shortened, but top of panel refuse to move. Also, the Length -> Custom option is now the default action and selecting other panel settings options is nearly impossible without a touchscreen as the panel settings menu auto hides when mouse pointer moves off of the resize bar. Panel icons are also difficult to move without launching their respective function (thus dumping the user out of Edit mode). EXPECTED RESULT Panel should be resizable from top. Panel settings menu should not auto hide until the panel setting icon is clicked or Edit mode is intentionally exited. SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.92.90 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-15-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: Dell Inc. Product Name: Inspiron 7559 System Version: 1.3.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 477925] Kpat Spider crashes after dealing cards then holding down ctrl-z
https://bugs.kde.org/show_bug.cgi?id=477925 --- Comment #2 from Darin Miller --- I can confirm patch https://invent.kde.org/games/kpat/-/merge_requests/59 fixes crl-z (undo) issue. Thanks for the fast fix! -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 477925] New: Kpat Spider crashes after dealing cards then holding down ctrl-z
https://bugs.kde.org/show_bug.cgi?id=477925 Bug ID: 477925 Summary: Kpat Spider crashes after dealing cards then holding down ctrl-z Classification: Applications Product: kpat Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: darinsmil...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Launch a spider game in Kpat 2. Click the card deck a few times to distribute the next set of cards. 3. Hold Ctrl-z to undo the distributions and kpat will crash. OBSERVED RESULT kpat crashes EXPECTED RESULT Retore cards to state of the previous move. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570S AORUS ELITE AX System Version: -CF ADDITIONAL INFORMATION Older versions (23.08.3) of kpat do not crash when holding ctrl-z. gdb output: ASSERT failure in QList::insert: "index out of range", file /usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h, line 868 Thread 1 "kpat" received signal SIGABRT, Aborted. __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737237797568) at ./nptl/pthread_kill.c:44 Download failed: Invalid argument. Continuing without source file ./nptl/./nptl/pthread_kill.c. 44 ./nptl/pthread_kill.c: No such file or directory. (gdb) backtrace #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737237797568) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737237797568) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737237797568, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x75842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x758287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x764d6fb7 in qAbort () at ./src/corelib/global/qglobal.cpp:161 #6 0x764d2465 in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2003 #7 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7fffcff0) at ./src/corelib/global/qlogging.cpp:378 #8 0x764d79e3 in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:901 #9 0x764a5968 in qt_assert_x (where=where@entry=0x77c2a4c0 "QList::insert", what=what@entry=0x77c2a40b "index out of range", file=file@entry=0x77c299f0 "/usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h", line=line@entry=868) at ./src/corelib/global/qassert.cpp:77 #10 0x77c01527 in QList::emplace (this=, i=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h:868 #11 QList::emplace (i=9, this=0x55db29b8) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h:866 #12 QList::insert (t=, i=9, this=0x55db29b8) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h:472 #13 KCardPile::insert (this=, index=9, card=0x55ea14d0) at ./src/libkcardgame/kcardpile.cpp:384 #14 0x55592247 in DealerScene::undoOrRedo (this=, undo=) at ./src/dealer.cpp:1083 #15 0x76426b9e in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #16 doActivate (sender=0x55b074b0, signal_index=7, argv=0x7fffd360) at ./src/corelib/kernel/qobject.cpp:4021 #17 0x76c3b406 in QAction::triggered (this=this@entry=0x55b074b0, _t1=) at ./obj-x86_64-linux-gnu/src/gui/Gui_autogen/include/moc_qaction.cpp:642 #18 0x76c3f164 in QAction::activate (this=0x55b074b0, event=) at ./src/gui/kernel/qaction.cpp:1102 #19 0x76c3f2a8 in QAction::event (e=0x7fffd5a0, this=0x55b074b0) at ./src/gui/kernel/qaction.cpp:1044 #20 QAction::event (this=0x55b074b0, e=0x7fffd5a0) at ./src/gui/kernel/qaction.cpp:1027 #21 0x775f079b in QApplicationPrivate::notify_helper (this=, receiver=0x55b074b0, e=0x7fffd5a0) at ./src/widgets/kernel/qapplication.cpp:3290 #22 0x7645e828 in QCoreApplication::notifyInternal2 (receiver=0x55b074b0, event=event@entry=0x7fffd5a0) at ./src/corelib/kernel/qcoreapplication.cpp:1118 #23 0x7645e86d in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7fffd5a0) at
[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432744] xembedsniproxy produces a square in the top-left corner that may either eat clicks or be filled in with black color
https://bugs.kde.org/show_bug.cgi?id=432744 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #9 from Darin Miller --- *** Bug 433396 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433396] Using Wayland, buttons on far left of window are unusable window is moved to upper left corner.
https://bugs.kde.org/show_bug.cgi?id=433396 Darin Miller changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #4 from Darin Miller --- *** This bug has been marked as a duplicate of bug 432744 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433396] Using Wayland, buttons on far left of window are unusable window is moved to upper left corner.
https://bugs.kde.org/show_bug.cgi?id=433396 --- Comment #3 from Darin Miller --- Good call Nate. This appears to be a duplicate of 432744 since "killall xembedsniproxy" fixes the problem. The killall command also remove Teams from the systemtray, thus a caveat to the killall command. Marking as duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433396] Using Wayland, buttons on far left of window are unusable window is moved to upper left corner.
https://bugs.kde.org/show_bug.cgi?id=433396 --- Comment #1 from Darin Miller --- Ensure to test with a single panel on the bottom, or if panel is on the left, ensure to auto hide or allow windows to cover panel to ensure buttons land in the extreme upper left of the screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433396] New: Using Wayland, buttons on far left of window are unusable window is moved to upper left corner.
https://bugs.kde.org/show_bug.cgi?id=433396 Bug ID: 433396 Summary: Using Wayland, buttons on far left of window are unusable window is moved to upper left corner. Product: kwin Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: darinsmil...@gmail.com Target Milestone: --- SUMMARY Running Wayland window buttons on the far left are "unclickable" when window is moved to the upper left. STEPS TO REPRODUCE 1. Using System Settings -> Appearance -> Window Decorations -> Tiltebar buttons, move any button to the far left and Apply. 2. Using meta++ move window to the upper left screen corner. 3. Attempt to click on the upper left button. The click is "stolen" by some other process. OBSERVED RESULT Window button is "unclickable". EXPECTED RESULT Since I move the "close" button to the left, I expect to close the window with said button. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-14-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 427526] Bluetooth mouse not visible when attempting to pair in FW 5.74
https://bugs.kde.org/show_bug.cgi?id=427526 Darin Miller changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Darin Miller --- Somehow connection issue resolved fixed itself...(possibly intermittent?). I reopen if I can repeat again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 427526] New: Bluetooth mouse not visible when attempting to pair in FW 5.74
https://bugs.kde.org/show_bug.cgi?id=427526 Bug ID: 427526 Summary: Bluetooth mouse not visible when attempting to pair in FW 5.74 Product: frameworks-bluez-qt Version: 5.74.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: darinsmil...@gmail.com Target Milestone: --- SUMMARY Razer Atherus bluetooth mouse does not show up in Blue scanning devices window. STEPS TO REPRODUCE 1. Put mouse in pairing mode. 2. From the PC, scan for new devices with either panel bluetooth "add devices" button and System Setting Bluetooth add devices. OBSERVED RESULT Device scan fails to show Razer mouse. EXPECTED RESULT Mouse should appear in the scan. SOFTWARE/OS VERSIONS Linux/KDE Plasma: yes KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Connecting BT headphones works fine. Kubuntu 20.04 worked fine with same mouse Ubuntu 20.10 (GNome) also works. Neon Dev Unstable with Plasma 5.20.8, FW 5.75, QT 5.15.0. also works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423781] Corruption in systemsettings5 window and logoff pause/cancellation after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=423781 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #8 from Darin Miller --- NVidia driver 455.28 fixes the System Settings "Black Menu" issue on Kubuntu 20.10. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 427329] NVidia Video corruption after wake from sleep
https://bugs.kde.org/show_bug.cgi?id=427329 --- Comment #6 from Darin Miller --- NVidia driver 455.28 fixes the System Settings "Black Menu" issue. If the chrome maintainers would fix their code, we will be back in business... Filed a 2nd bug against chrome as the corruption is still an issue with Chrome 86. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 427329] NVidia Video corruption after wake from sleep
https://bugs.kde.org/show_bug.cgi?id=427329 --- Comment #3 from Darin Miller --- System Settings black menu occurs regardless if System Settings is open or closed and with compositing both on or off. Since System Setting is also affected and remains an issue withh NVidia driver v435, 450 and 455, I would not consider this to be entirely an upstream issue as previous versions of System Settings (Kubnutu 20.04) used to work fine 435 & 450 NVidia drivers. The chromium browser corruption occurs with composting on and off and has been an issue starting with chromium v84+. A bug was filed against chromium when I was using Kubuntu 20.04 as it was the only app that did not gracefully recover from sleep. I tried to file the bug against NVidia, but I could only find a developer bug reporting forums. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 427329] NVidia Video corruption after wake from sleep
https://bugs.kde.org/show_bug.cgi?id=427329 --- Comment #1 from Darin Miller --- Created attachment 132113 --> https://bugs.kde.org/attachment.cgi?id=132113=edit Browser corruption -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 427329] New: NVidia Video corruption after wake from sleep
https://bugs.kde.org/show_bug.cgi?id=427329 Bug ID: 427329 Summary: NVidia Video corruption after wake from sleep Product: frameworks-plasma Version: 5.74.0 Platform: Ubuntu Packages OS: Unspecified Status: REPORTED Severity: major Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: darinsmil...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 132112 --> https://bugs.kde.org/attachment.cgi?id=132112=edit System Setting corruption Picture SUMMARY NVidia driver is not properly initializing after waking from sleep, corrupting System Settings main menu and any chromium based browser. Minimizing/retoring or restarting the browser "fixes" the corrupted browser, but I have not found anything that fixes the black System Setting menu. STEPS TO REPRODUCE 1. Use NVidia system with 435, 450 or 455 proprietary drivers 2. Sleep and wake system with chromium based browser open. 3. Note the corruption of the chromium window. 4. Launch System Settings and note the black System Settings main menu (no work around to fix found yet other than rebooting). This problem is also reproducible in Neon Dev Unstable with plasma 5.20.80, FW: 5.75.0 QT 5.15, kernel 5.4.0-48 OBSERVED RESULT Corrupted chromium based browser windows, black menu drop downs in the browser, and black main menu of System Settings. EXPECTED RESULT Non-corrupted video. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.10 & Neon Dev Unstable (20.04) KDE Plasma Version: 5.19.5 & 5.20.80 KDE Frameworks Version: 5.74.0 & 5.75.0 Qt Version: 5.14.2 & 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #89 from Darin Miller --- This is issue is fixed on Kubuntu 20.04, Plasma 5.18.5. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 420723] partitionmanager does not recognize exfat kernel support
https://bugs.kde.org/show_bug.cgi?id=420723 --- Comment #2 from Darin Miller --- So packagers can eliminate the dependency for exfat-fuse for kernels 5.4 and above since partitionmanager works fine without it on 5.4. Good to know. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 420723] New: partitionmanager does not recognize exfat kernel support
https://bugs.kde.org/show_bug.cgi?id=420723 Bug ID: 420723 Summary: partitionmanager does not recognize exfat kernel support Product: partitionmanager Version: 4.1.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: darinsmil...@gmail.com Target Milestone: --- SUMMARY On Kubuntu 20.04, partitionmanager does not allow formatting partitions as exfat unless exfat-utils is installed, thus failing to recognize that as of kernel 5.4 and above, exfat is intrinsically supported by the kernel. In addition, exfat-utils recommends exfat-fuse as a dependency. Should partitionmanager be able to format as exfat without the exfat-* packages? STEPS TO REPRODUCE 1. In kubuntu 20.04, sudo apt remove exfat-* 2. Open partitionmanager 3. Select a partition to format and note that exfat is not an option. OBSERVED RESULT no exfat on the drop down EXPECTED RESULT exfat on the dropdown SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: yes (available in About System) KDE Plasma Version: 5,18.4 KDE Frameworks Version: 5.68 Qt Version: 5.12.8 kernel: 5.4.0-26-generic ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 Darin Miller changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #10 from Darin Miller --- This appears to be NVidia-settings issue now that I have experience the issue in other circumstance. Closing the bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #9 from Darin Miller --- I never manually mirrored the screens. Kscreen seems to be working fine when all resolution and monitor position adjustments are made via kscreen. However, kscreen does not detect the current monitor states. So changes made via nvidia-setting are never captured. I upscale my 2k screen to 4K via nvidia setting as that is not possible with kscreen under xorg. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #7 from Darin Miller --- The files in $HOME/.local/share/kscreen were the problem. However, after manually sync'ing kscreen with NVidia settings by manually updating System setting -> Display and Monitor, the screen layout failed to save to the corresponding config file after hitting Apply. To force save, I had to delete the bad file (file with monitors mirrored) and then run: plasmashell --replace A new file with the same name was regenerated, this time with correct display settings. See above attached files. Should kscreen "adopt" the resolution changes made via Nvidia settings? Kscreen does not allow scaling of a 2k screen to 4K resolution on X (at least not on NVidia) and thus I have to use nvidia-settings to accomplish the scaling. Regardless, the Display and Monitor is failing to save on my system. I will attempt to replicate on another NVidia system tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #6 from Darin Miller --- Created attachment 125293 --> https://bugs.kde.org/attachment.cgi?id=125293=edit Mirrored File Display and Monitor failed to save new settings to this file. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #5 from Darin Miller --- Created attachment 125292 --> https://bugs.kde.org/attachment.cgi?id=125292=edit correct config file -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430
--- Comment #3 from Darin Miller ---
I have assigned the following script to a shortcut to deal with the issue.
Note, I also restart plasma as weather widgets fail to initialize and location
of other widgets are randomly scattered across the desktop (needs another bug
report or search for existing...)
#!/bin/sh
nvidia-settings --assign CurrentMetaMode="DP-0:nvidia-auto-select+0+0"
sleep 1
nvidia-settings --assign CurrentMetaMode="DP-0:nvidia-auto-select+0+0,
DP-2:2560x1440+3840+0 {viewportin=3840x2160}"
plasmashell --replace &
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #2 from Darin Miller --- 5th reboot produced the mirrored screens: https://imgur.com/tJnA69w -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #1 from Darin Miller --- Strange... 3 consecutive reboots produced mirrored screens. On the 4th reboot, where I attempted to grab a screenshot of mirrored displays, screens were no longer mirrored but my Font forced dpi was unchecked and defaulted to 96 (was 144 and checked). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] New: Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 Bug ID: 416430 Summary: Plasma 5.18 beta does not save screen layout after reboot Product: KScreen Version: 5.17.90 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: kscreen-bugs-n...@kde.org Reporter: darinsmil...@gmail.com Target Milestone: --- SUMMARY Screens are mirrored on reboot with 5.18 beta. STEPS TO REPRODUCE 1. Using Kubuntu 19.10 with plasma beta ppa: sudo add-apt-repository ppa:kubuntu-ppa/beta && sudo apt update && sudo apt full-upgrade -y 2. Set 4K screen as primary left left screen. Using NVidia Settings, scale 2K screen to 4K to right of 4K screen. 3. Reboot OBSERVED RESULT Before reboot: https://imgur.com/lpbWdRz After reboot: coming soon EXPECTED RESULT Save screen layout. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-26-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #109 from Darin Miller --- This is still broken on Eoan (which has 5.12.4) when the NVidia driver is enabled. Thus, I recommend changing status to reopened. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-13-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #106 from Darin Miller --- The Cover and Flip switch task switcher options seem to be the only switchers not affected by the bug... and neither of these switchers allow mouse interaction... maybe the lack of mouse interaction is a clue to the root cause? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Darin Miller changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #105 from Darin Miller --- Testing Neon, the first and 2nd "back to back" Alt-tab work but subsequent alt-tabs are delayed. The Large Icon task switcher fails to appear after the 2nd or 3rd atl-tab. The alt-tab'ing is hit and miss and is mostly useless after multiple Alt-tabs and the Large Icon task switcher eventually dies completely. NVidia driver: 435.17 Prime Profile: NVidia Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.4 Kernel Version: 5.2.0-15-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #104 from Darin Miller --- Disregard my comment. I did not verify the qt 5.12.4 requirement. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #103 from Darin Miller --- This bug has returned in Neon Dev unstable, not sure when... current versions: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-15-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #81 from Darin Miller --- I too am affected by this bug and am hoping it will also fix the stutter/pause for auto-sizing/maximizing windows dragged to the screen edge. The stutter feels very similar between the alt-tab and window drag/resize pause. On my optimus system, the Intel video card is affected to a much lesser degree but is still noticeable, but NVidia with proprietary driver causes a 5 to 15 second system freeze. I will attempt the patch as outlined below... -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 Darin Miller changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 --- Comment #4 from Darin Miller --- KDEConnect crashing fixed with the latest release. The new version also eliminates the dual pop-up replay boxes actually it eliminates all pop up messages/notification even though kdeconnect is configured to notify, but that will be another bug report Changing status to resolved. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407785] New: KDEConnect crashes on plasma 5.16 beta
https://bugs.kde.org/show_bug.cgi?id=407785 Bug ID: 407785 Summary: KDEConnect crashes on plasma 5.16 beta Product: kdeconnect Version: 1.3.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: darinsmil...@gmail.com Target Milestone: --- SUMMARY KDEConnect crashes on plasma 5.16 beta when attempting to post notifications of incoming texts from phone. STEPS TO REPRODUCE 1. Install plasma 5.16 beta 2. Pair your phone via KDEConnect 3. Ask someone to send you a text. OBSERVED RESULT KDEconnect crashes immediately EXPECTED RESULT Expecting pop notification to allow response to text. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.04 KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-15-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 15.5 GiB of RAM ADDITIONAL INFORMATION crash report: https://paste.ubuntu.com/p/xPYXXPf3jf/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407783] New: Touchpad crashes System Settings on desktop without touchpad
https://bugs.kde.org/show_bug.cgi?id=407783 Bug ID: 407783 Summary: Touchpad crashes System Settings on desktop without touchpad Product: plasmashell Version: 5.15.90 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: darinsmil...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Touchpad crashes when selected System Setting -> Input -> touchpad or launching touchpad directly via krunner on a desktop system that does not have a touchpad STEPS TO REPRODUCE 1. On a desktop that does not have a touchpad, select System Setting -> Input -> Touchpad OBSERVED RESULT System settings crashes immediately. EXPECTED RESULT "Greyed out" Touchpad options and system settings not crashing. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.04 KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-15-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 15.5 GiB of RAM ADDITIONAL INFORMATION: Crash report: https://paste.ubuntu.com/p/tZCXq6HhBH/ -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 407614] kded_touchpad crashes at startup
https://bugs.kde.org/show_bug.cgi?id=407614 --- Comment #28 from Darin Miller --- On Kubuntu 19.10: System Settings -> Input -> Touchpad configuration menu now matches the standalone Touchpad menu and is no longer greyed out. Also, shortcut keys are now working! However, on the desktop (which does not have a touchpad), the System Settings -> Input -> Touchpad selection crashes System Settings. File a separate bug? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 407614] kded_touchpad crashes at startup
https://bugs.kde.org/show_bug.cgi?id=407614 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #18 from Darin Miller --- This also affects desktops that have no touchpad (crashes immediately on startup). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406048] Kicker menu and notifications do not align with primary monitor dimensions.
https://bugs.kde.org/show_bug.cgi?id=406048 Darin Miller changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Darin Miller --- Requested info added (but I forgot to change the status). I assume "REPORTED" is correct? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406048] Kicker menu and notifications do not align with primary monitor dimensions.
https://bugs.kde.org/show_bug.cgi?id=406048 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #3 from Darin Miller --- Created attachment 119161 --> https://bugs.kde.org/attachment.cgi?id=119161=edit Screenshot of shifted kicker menu Also note the weather and temp plasmoids "centered" on the 4k display... they were on the right side of the primary monitor prior to the reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406048] Kicker menu and notifications do not align with primary monitor dimensions.
https://bugs.kde.org/show_bug.cgi?id=406048 --- Comment #2 from Darin Miller --- $ xrandr -q Screen 0: minimum 8 x 8, current 5440 x 2160, maximum 32767 x 32767 DVI-D-0 connected 1600x1200+3840+0 (normal left inverted right x axis y axis) 367mm x 275mm 1600x1200 60.00*+ 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 609mm x 349mm 3840x2160 60.00*+ 29.98 2560x1440 59.95 2048x1280 59.96 2048x1080 24.00 1920x1200 59.88 1920x1080 60.0060.0059.9450.0023.98 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 59.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406048] New: Kicker menu and notifications do not align with primary monitor dimensions.
https://bugs.kde.org/show_bug.cgi?id=406048 Bug ID: 406048 Summary: Kicker menu and notifications do not align with primary monitor dimensions. Product: plasmashell Version: 5.15.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: darinsmil...@gmail.com Target Milestone: 1.0 SUMMARY Kicker menu aligns with the bottom of secondary monitor if BIOS uses the Secondary monitor for POST display. STEPS TO REPRODUCE 1. In System Settings, set 4K monitor as primary display and a set lower resolution monitor as secondary display. Align the displays at the top. 2. Set panel to left side of primary display and move kicker icon to bottom of vertical panel. 4. Reboot machine, click on kicker, observe kicker menu appears on primary monitor but aligns with bottom lower resolution secondary display. OBSERVED RESULT Kicker Menu does not align with kicker icon. EXPECTED RESULT Kicker Menu does should align with kicker icon. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.04 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.11.3 Kernel Version: 5.0.0-8-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION Restarting plasma fixes the issue. I suspect on boot, kicker menu position is set prior to setting the primary monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #29 from Darin Miller --- Created attachment 118734 --> https://bugs.kde.org/attachment.cgi?id=118734=edit with Splash and auto login disabled Boots quickly to desktop when auto login is not enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #28 from Darin Miller --- Kubuntu 18.10/19.04 are also suffering from splash screen delaying desktop display. Attached boot chart with and without splash enabled. BTW, charts captured on a single screen laptop (Dell 7559 booting with Intel video). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #26 from Darin Miller --- Created attachment 118732 --> https://bugs.kde.org/attachment.cgi?id=118732=edit With Splash Slow boot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #27 from Darin Miller --- Created attachment 118733 --> https://bugs.kde.org/attachment.cgi?id=118733=edit Without Splash fast boot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402843] Holdiays on digital clock crash plasmashell
https://bugs.kde.org/show_bug.cgi?id=402843 Darin Miller changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402843] Holdiays on digital clock crash plasmashell
https://bugs.kde.org/show_bug.cgi?id=402843 --- Comment #2 from Darin Miller --- Holidays are now working again in Plasma 5.15.80. Closing bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 402843] New: Holdiays on digital clock crash plasmashell
https://bugs.kde.org/show_bug.cgi?id=402843 Bug ID: 402843 Summary: Holdiays on digital clock crash plasmashell Product: kdeplasma-addons Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: fuzzy-clock Assignee: plasma-b...@kde.org Reporter: darinsmil...@gmail.com Target Milestone: --- Neon Dev Unstable Plasma 5.14.8: Enabling holidays on digital clock causes plasma crash upon Apply. STEPS TO REPRODUCE 1. Right click on clock 2. Select Digital Clock settings | Calendar 3. Check the Holidays box and click Apply Plasma crashes immediately and will not restart. To recover, comment this line in ~/.config/plasma-org.kde.plasma.desktop-appletsrc: # enabledCalendarPlugins=/usr/lib/x86_64-linux-gnu/qt5/plugins/plasmacalendarplugins/holidaysevents.so OBSERVED RESULT Plasmashell crashes and will not restart. Error thrown: $ plasmashell & [1] 4046 darin@imagineNU:~$ org.kde.plasmaquick: Applet preload policy set to 1 file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:61:28: Unable to assign [undefined] to int file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:52:27: Unable to assign [undefined] to int trying to show an empty dialog KActivities: Database connection: "kactivities_db_resources_139651008317504_readonly" query_only: QVariant(qlonglong, 1) journal_mode:QVariant(QString, "wal") wal_autocheckpoint: QVariant(qlonglong, 100) synchronous: QVariant(qlonglong, 0) Closing SQL connection: "kactivities_db_resources_139651008317504_readonly" KActivities: Database connection: "kactivities_db_resources_139651008317504_readonly" query_only: QVariant(qlonglong, 1) journal_mode:QVariant(QString, "wal") wal_autocheckpoint: QVariant(qlonglong, 100) synchronous: QVariant(qlonglong, 0) Nothing to load - the client id is empty Nothing to load - the client id is empty Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion r [1]+ Exit 2 plasmashell EXPECTED RESULT no crashing and holidays on calendar SOFTWARE/OS VERSIONS Linux/KDE Plasma: Yes (available in About System) KDE Plasma Version: 5.14.8 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 381894] Volume feedback and testing don't work
https://bugs.kde.org/show_bug.cgi?id=381894 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Darin Miller --- Problem also noted on Neon Dev unstable Bionic (p 5.13.80, fw 5.50.0, qt 5.11.1). Installing libcanberra-pulse enables sound on my system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget with QSG_RENDER_LOOP=basic
https://bugs.kde.org/show_bug.cgi?id=368838 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #124 from Darin Miller <darinsmil...@gmail.com> --- Memory leak still present with Kubuntu 18.04 updated as follows: Plasma 5.12.5 FW 5.44.0 QT 5.9.5 HW: Toshiba Satellite laptop, Intel graphics Both the media frame widget and desktop background are affected. Setting the update interval to 10s (or less) and parking a memory widget on the desktop was the method used for monitoring. Note: pkill plasmashell; QSG_RENDER_LOOP=threaded kstart plasmashell also stopped the leak. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 392541] New: Unable to active KDE Provider and Git plugins if git is not installed.
https://bugs.kde.org/show_bug.cgi?id=392541 Bug ID: 392541 Summary: Unable to active KDE Provider and Git plugins if git is not installed. Product: kdevelop Version: 5.2.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Project provider: Github Assignee: kdevelop-bugs-n...@kde.org Reporter: darinsmil...@gmail.com Target Milestone: --- The initial issue started out as missing KDE packages in the "Select source" drop down of the Fetch Project menu. Since git was not installed KDevelop would not allow the activation of the KDE provider plugin. Same is true for the "Git Support" plugin. This issue was discovered on a fresh OS install with little or no developer packages installed. A column in the plugin menu that specifies unmet dependencies would have been helpful (or at least message either via pop-up or command line). This issue seems painfully obvious NOW that I know the solution. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 384997] Enabling Auto switching streams on new active output causes pulseaudio to crash
https://bugs.kde.org/show_bug.cgi?id=384997 --- Comment #3 from Darin Miller <darinsmil...@gmail.com> --- I filed the bug here but received no response: https://bugs.launchpad.net/ubuntu/+source/plasma-pa/+bug/1716092. I can report elsewhere or re-file if needed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 367688] Audio Volume Settings of Notification Sounds reset to zero
https://bugs.kde.org/show_bug.cgi?id=367688 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #13 from Darin Miller <darinsmil...@gmail.com> --- This problem is still present in Kubuntu 17.10 with plasma 5.10.3 and 5.10.95. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 384997] New: Enabling Auto switching streams on new active output causes pulseaudio to crash
https://bugs.kde.org/show_bug.cgi?id=384997 Bug ID: 384997 Summary: Enabling Auto switching streams on new active output causes pulseaudio to crash Product: plasma-pa Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: darinsmil...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Not sure if this is a plasma-pa bug or a pulseaudio bug. In plasma-pa -> Audio Volumue -> Advanced tab checking the "Automatically switch all running streams when a new output becomes available" causes PA to crash on startup. If the /etc/pulse/default.pa file is modified by commenting out following line: load-module module-switch-on-connect PA will start as expected. Auto switching works great even when the above line in default.pa line is commented out. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368974] System Settings | App. Style | Window Decorations -> Breeze button size settings are incorrect
https://bugs.kde.org/show_bug.cgi?id=368974 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 381087] Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu.
https://bugs.kde.org/show_bug.cgi?id=381087 --- Comment #1 from Darin Miller <darinsmil...@gmail.com> --- Forgot to mention, version 1.4 is not available in the Version drop-down. But this bug applies to said version. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 381087] New: Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu.
https://bugs.kde.org/show_bug.cgi?id=381087 Bug ID: 381087 Summary: Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu. Product: ksudoku Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: darinsmil...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- The org.kde.ksudoku.desktop file need to be updated to exclude the -caption option as I have been told this function has been deprecated in plasma5. The app fails to launch via the menu/icon in its current state. The following line in src/gui/org.kde.ksudoku.desktop need fixed: Exec=ksudoku %i -caption %c Removing the "%i -caption %c" allows the app to launch without issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379022] Update Task Switcher screenshots
https://bugs.kde.org/show_bug.cgi?id=379022 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #2 from Darin Miller <darinsmil...@gmail.com> --- Breeze and Grid preview button shows the same KDE4 style screenshots on my 17.04 system. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 374687] Allow per display Screen Scalinng (individually)
https://bugs.kde.org/show_bug.cgi?id=374687 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 222428] Wish for KDE recognize/compute DPI settings by different plugged screens
https://bugs.kde.org/show_bug.cgi?id=222428 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps
https://bugs.kde.org/show_bug.cgi?id=371877 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #16 from Darin Miller <darinsmil...@gmail.com> --- Adding a note from a remmina perspective: Meta keys are used frequently when remoting into a Windows box: by itself on windows provides same functionality as Kicker (user text search for applications and files) +D minimizes all windows +e file manager (Explorer) + splits window half screen in corresponding arrow direction. + windows settings etc. Options: 1. Disable kicker meta shortcut entirely 2. Disable meta key with script when launching key capturing applications, re-enable when application is closed. This is a pseudo solution, as kicker would not work while app is running. I switch to local desktop frequently when remoted to a windows box. Though I use krunner to launch most of apps, I would have used the meta key long ago if it worked. Thus, new users will expect it to work if switching from windows. 3. Provide a list of apps in a config file or possibly a "window rules" setting that will disable the kicker meta key when they have focus. However, this requires the user to maintain the key grab setting in the app and in the config file. 4. Honor the key capture state of the application that has focus. Can the key capture state of an app be determined when the app obtains focus? If so, auto disable meta-kicker relationship when respective apps are set to capture the keyboard and re-enable when non-key capturing apps or local desktop has focus. Option 4 is preferred as it requires the least amount of configuration. Options 1, 2 and 3 keep KDE in the tinkerer's realm and discourages users who do not like to fiddle with their system. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 372611] New: plasma-discover 5.8.90 crashes when using the text filter box
https://bugs.kde.org/show_bug.cgi?id=372611 Bug ID: 372611 Summary: plasma-discover 5.8.90 crashes when using the text filter box Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: darinsmil...@gmail.com Target Milestone: --- 1. Launch plasma-discover 5.8.90 (Neon unstable) 2. Type something in the search box, i.e. gimp 3. Delete text and type another search. Crash usually happens by the 2nd or 3rd search. Autobug report says not enough info to file a report, so report filed manually. However, plasma-discover produced a core dump which I can attach if needed. /var/lib/systemd/coredump: -rw-r-+ 1 root root 22504776 Nov 16 21:11 core.plasma-discover.1000.0677b29c8fff42d3bc0469c55d37556c.14239.1479355810.xz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #6 from Darin Miller <darinsmil...@gmail.com> --- This issue also frustrates me. In fact I just removed all widgets from the desktop as I am tired of fighting them. Solution: Widgets should be anchored from their closest screen edges as a percentage of the current screen resolution. Auto resizing should also be handled as resolution ratio. That way widget would gracefully resize and move to predictable locations as the screen changes resolution. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368974] System Settings | App. Style | Window Decorations -> Breeze button size settings are incorrect
https://bugs.kde.org/show_bug.cgi?id=368974 --- Comment #7 from Darin Miller <darinsmil...@gmail.com> --- Verified fixed now. YGAA (You guys are awesome!) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368974] System Settings | App. Style | Window Decorations -> Breeze button size settings are incorrect
https://bugs.kde.org/show_bug.cgi?id=368974 --- Comment #6 from Darin Miller <darinsmil...@gmail.com> --- Problem also persists in Plasma 5.8.9, but I suspect the update has not yet hit the repos... will check again in few days. (Current Breeze package version is +git20161002.1318-0). Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368974] System Settings | App. Style | Window Decorations -> Breeze button size settings are incorrect
https://bugs.kde.org/show_bug.cgi?id=368974 --- Comment #5 from Darin Miller <darinsmil...@gmail.com> --- This problem still persists with the 5.8 updates on neon user edition. I will check the dev-unstable shortly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368974] New: System Settings | App. Style | Window Decorations -> Breeze button size settings are incorrect
https://bugs.kde.org/show_bug.cgi?id=368974 Bug ID: 368974 Summary: System Settings | App. Style | Window Decorations -> Breeze button size settings are incorrect Product: kwin Version: 5.7.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: darinsmil...@gmail.com When Using System Settings | App. Style | Window Decorations -> Breeze button, the window decoration button resizing drop down used change all button sizes immediately upon Apply.Currently in 5.7.95, the height of the decoration bar changes, but the buttons themselves remain unchanged. ' In a similar note, the Window Title font is not immediately updated either. Restarting kwin_x11 applies the newly set button size and Window title font. Reproducible: Always Steps to Reproduce: 1. Settings | App. Style | Window Decorations -> Breeze button 2. Change the Button Size drop down to something different. 3. Notice the title bar height changes slightly but button remain same size. Note: Using 4K (hdpi) display. Actual Results: No changes in font size or button height until kwin_x11 is restarted. Expected Results: Change should be immediate as it was before. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368974] System Settings | App. Style | Window Decorations -> Breeze button size settings are incorrect
https://bugs.kde.org/show_bug.cgi?id=368974 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348393] Style -> Win Deco: No option to add 'Spacer' to Title Bar
https://bugs.kde.org/show_bug.cgi?id=348393 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362105] Taskbar options 'autohide'/'windows can cover' not functional
https://bugs.kde.org/show_bug.cgi?id=362105 --- Comment #16 from Darin Miller <darinsmil...@gmail.com> --- Status Update: Kubuntu 16.10 Yackety NVidia Gefore8 video, NVidia340.96 driver Plasma 5.6.4 - autohide problem Arch NVidia Gefore8 video, NVidia340.96 driver Plasma 5.6.4 - autohide problem The intel 4200 Xenail Plasma 5.6.3 "fixed" itself after an update.?! So now the only common issues among my systems is the legacy NVidia 340.96 drivers. This seems to be a NVidia and/or QT issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362105] Taskbar options 'autohide'/'windows can cover' not functional
https://bugs.kde.org/show_bug.cgi?id=362105 --- Comment #14 from Darin Miller <darinsmil...@gmail.com> --- More clues: Kubuntu 16.04 Xenial Intel 4200 video, Plasma 5.6.3 - autohide problem Kubuntu 16.10 Yackety NVidia Gefore8 video, nouveau driver Plasma 5.6.4 WORKS FINE! Kubuntu 16.10 Yackety NVidia Gefore8 video, NVidia340 driver Plasma 5.6.4 autohide problem Kubuntu 16.10 Yackety NVidia 960m video, NVidia 364.19 driver Plasma 5.6.4 WORKS FINE! As side note, on my Intel 16.04 box, I removed the panel entirely and put the all the widgets from the panel on the bottom of the screen. The I just use show desktop (set to super+D on my box) to access the widgets. OK workaround until the panel is fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362105] Taskbar options 'autohide'/'windows can cover' not functional
https://bugs.kde.org/show_bug.cgi?id=362105 --- Comment #10 from Darin Miller <darinsmil...@gmail.com> --- Also autohide/window can cover fails in Arch with Plasma 5.6.4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362105] Taskbar options 'autohide'/'windows can cover' not functional
https://bugs.kde.org/show_bug.cgi?id=362105 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #7 from Darin Miller <darinsmil...@gmail.com> --- My 5.6.3 in Kubuntu (plasma staging ppa) also suffers from autohide/window can cover issue. Removing/re-adding fresh panel has same behvior. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 354473] Cannot login to Google account
https://bugs.kde.org/show_bug.cgi?id=354473 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore
https://bugs.kde.org/show_bug.cgi?id=354130 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 358000] New: The landings PPA killed muon. Appears dependency related.
https://bugs.kde.org/show_bug.cgi?id=358000 Bug ID: 358000 Summary: The landings PPA killed muon. Appears dependency related. Product: muon Version: 5.5.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: darinsmil...@gmail.com CC: aleix...@kde.org, sit...@kde.org Testing the ppa:kubuntu-ppa/backports-landing. Muon broke after the update. I suspected it was related to the issue discover notifier issue, but now that the notifier issue is fixed, the Muon install issue remains. Confirmed on 2 different machines upgraded from 15.10. Message from sudo apt install muon: muon : Depends: libmuon (= 4:5.4.3-0ubuntu1~ubuntu15.10~ppa1) but it is not going to be installed. E: Unable to correct problems, you have held broken packages. However, sudo dpkg --configure -a, along with autoremove and clean did not fix the issue. Current active sources from /etc/apt/sources.list: deb http://us.archive.ubuntu.com/ubuntu/ wily main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ wily main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ wily-updates main restricted deb http://us.archive.ubuntu.com/ubuntu/ wily-updates main restricted deb http://us.archive.ubuntu.com/ubuntu/ wily multiverse deb-src http://us.archive.ubuntu.com/ubuntu/ wily multiverse deb http://us.archive.ubuntu.com/ubuntu/ wily-updates multiverse deb-src http://us.archive.ubuntu.com/ubuntu/ wily-updates multiverse deb http://us.archive.ubuntu.com/ubuntu/ wily-backports main restricted universe multiverse deb-src http://us.archive.ubuntu.com/ubuntu/ wily-backports main restricted universe multiverse deb http://security.ubuntu.com/ubuntu wily-security main restricted deb-src http://security.ubuntu.com/ubuntu wily-security main restricted deb http://security.ubuntu.com/ubuntu wily-security universe deb-src http://security.ubuntu.com/ubuntu wily-security universe deb http://security.ubuntu.com/ubuntu wily-security multiverse deb-src http://security.ubuntu.com/ubuntu wily-security multiverse -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357835] Hard to resize panel when in vertical mode
https://bugs.kde.org/show_bug.cgi?id=357835 Darin Miller <darinsmil...@gmail.com> changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #2 from Darin Miller <darinsmil...@gmail.com> --- Confirmed with Frameworks 5.18. I do not have 5.17 to try... -- You are receiving this mail because: You are watching all bug changes.
