[Breeze] [Bug 371908] New: Rainbow Folders in Breeze
https://bugs.kde.org/show_bug.cgi?id=371908 Bug ID: 371908 Summary: Rainbow Folders in Breeze Product: Breeze Version: 5.8.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: johnmaveric...@mail.com CC: kain...@gmail.com Target Milestone: --- I don't know if this is the right place to put it, but i still can't see the feature mentioned in the post about Rainbow Folders ( https://kdeonlinux.wordpress.com/2016/08/08/rainbow-folders/ ) Using OpenSUSE Tumbleweed + KDE Plasma 5.8.2 + Breeze Icons 5.27 -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 372139] New: Debian 8.6.0 - System will not shut down , can only exit by switching off machine
https://bugs.kde.org/show_bug.cgi?id=372139 Bug ID: 372139 Summary: Debian 8.6.0 - System will not shut down , can only exit by switching off machine Product: khelpcenter Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: jbrycr...@gmail.com Target Milestone: --- System will not shut down , can only exit system by switching off machine -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 372139] Debian 8.6.0 - System will not shut down , can only exit by switching off machine
https://bugs.kde.org/show_bug.cgi?id=372139 --- Comment #3 from John --- My knowledge of Linux is very limited , I have installed Debian 8.6.0 from a bought disc , & log in with a password as usual . It is the shut down function as used from the menu that does not work . At the moment I have taken the hard drive with Debian on it out of the machine & have gone back to using Linux Mint . On Sun, Nov 6, 2016 at 11:17 PM, Luigi Toscano wrote: > https://bugs.kde.org/show_bug.cgi?id=372139 > > Luigi Toscano changed: > >What|Removed |Added > > > Status|UNCONFIRMED |RESOLVED > CC||luigi.tosc...@tiscali.it > Resolution|--- |INVALID > > --- Comment #2 from Luigi Toscano --- > I understand the pain, but this is not the proper channel for this issue. > This > bug was opened against khelpcenter, an browser for help guides, which is > for > sure not the right component. But this is not even about software by the > KDE > community, or at least not directly. If the desktop environment used is KDE > Plasma, this may be relevant here, but I would first check on the proper > support channel for Debian, providing more details. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372672] New: File Renaming Options sidebar is missing
https://bugs.kde.org/show_bug.cgi?id=372672 Bug ID: 372672 Summary: File Renaming Options sidebar is missing Product: digikam Version: 5.1.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import-Rename Assignee: digikam-de...@kde.org Reporter: jrussell...@yahoo.com.sg Target Milestone: --- The File Renaming Options sidebar is missing on Digikam5. Build 4:5.1.0-wily~ppa1 on Ubuntu 15.10 x64 I've installed and re-installed this version several times on two machines with the same results. Digikam 4.14.0 has the sidebar. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372672] File Renaming Options sidebar is missing
https://bugs.kde.org/show_bug.cgi?id=372672 --- Comment #4 from John --- The Digikam (5.3) AppImage bundle works, and after upgrading to Ubuntu 16.10 x64 - as I couldn't install v5.3 in Ubuntu 15.10 due to dependency problems - 4:5.3.0-yakkety~ppa2 is also fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged after I've switched from main laptop to external m
https://bugs.kde.org/show_bug.cgi?id=421700 John changed: What|Removed |Added CC||slackma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged after I've switched from main laptop to external m
https://bugs.kde.org/show_bug.cgi?id=421700 --- Comment #66 from John --- Created attachment 146648 --> https://bugs.kde.org/attachment.cgi?id=146648&action=edit New crash information added by DrKonqi plasmashell (5.24.0) using Qt 5.15.3 - What I was doing when the application crashed: Login to wayland session - Unusual behavior I noticed: This is from dmesg: [ 2713.233599] usb 5-2.1.5: Product: USB Billboard Device [ 2713.233601] usb 5-2.1.5: Manufacturer: VIA Labs, Inc. [ 2713.233603] usb 5-2.1.5: SerialNumber: 0001 [ 2713.351129] keepassxc[3952]: segfault at 20 ip 7f17528cdcde sp 7ffed1c73888 error 4 in libQt5WaylandClient.so.5.15.3[7f1752885000+c4000] [ 2713.351144] Code: d0 75 09 c3 0f 1f 84 00 00 00 00 00 ff e0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 48 8d 15 42 f3 ff ff <48> 8b 40 20 48 39 d0 75 09 c3 0f 1f 84 00 00 00 00 00 ff e0 66 66 [ 2713.356585] kscreenlocker_g[14536]: segfault at 20 ip 7f5935f9ccde sp 7ffec2d21168 error 4 in libQt5WaylandClient.so.5.15.3[7f5935f54000+c4000] [ 2713.356597] Code: d0 75 09 c3 0f 1f 84 00 00 00 00 00 ff e0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 48 8d 15 42 f3 ff ff <48> 8b 40 20 48 39 d0 75 09 c3 0f 1f 84 00 00 00 00 00 ff e0 66 66 [ 2713.373084] kwin_wayland[3410]: segfault at 0 ip 7f53dc156115 sp 7ffc85e89cc0 error 4 in KWinWaylandDrmBackend.so[7f53dc11c000+48000] [ 2713.373093] Code: 48 63 55 04 48 8b 45 10 0f 29 04 24 48 8d 14 92 48 8d 5c 05 00 48 8d 04 90 48 01 c5 48 39 eb 74 6a 0f 1f 40 00 49 8b 3e 8b 33 <48> 8b 07 ff 90 28 01 00 00 84 c0 74 4b 8b 43 08 8b 53 0c 48 8d 4b [ 2713.443808] r8152 6-2.1.2:1.0 enx98fa9b46c7bd: renamed from eth0 [ 2714.584783] usbcore: registered new interface driver snd-usb-audio [ 2714.821232] input: Lenovo ThinkPad Thunderbolt 3 Dock USB Audio as /devices/pci:00/:00:1c.4/:02:00.0/:03:01.0/:05:00.0/:06:02.0/:07:00.0/usb5/5-2/5-2.1/5-2.1.1/5-2.1.1.2/5-2.1.1.2:1.3/0003:17EF:3083.0007/input/input29 [ 2714.881018] hid-generic 0003:17EF:3083.0007: input,hidraw1: USB HID v1.11 Device [Lenovo ThinkPad Thunderbolt 3 Dock USB Audio] on usb-:07:00.0-2.1.1.2/input3 [ 2715.215142] IPv6: ADDRCONF(NETDEV_CHANGE): enx98fa9b46c7bd: link becomes ready [ 2715.215506] r8152 6-2.1.2:1.0 enx98fa9b46c7bd: carrier on [ 2716.079488] r8152 6-2.1.2:1.0 enx98fa9b46c7bd: carrier off [ 2718.543110] r8152 6-2.1.2:1.0 enx98fa9b46c7bd: carrier on [ 2725.515851] i915 :00:02.0: [drm] *ERROR* mstb 15dd9b1a port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed seattle ~ ❯ -- Backtrace (Reduced): #4 QScreen::geometry (this=0x0) at kernel/qscreen.cpp:413 #5 0x5594379de6c5 in DesktopView::screenGeometryChanged (this=0x5594393a7f80) at /usr/include/c++/9/bits/atomic_base.h:413 #6 0x7fa16ff3c1be in QtPrivate::QSlotObjectBase::call (a=0x7ffcb6e9b950, r=0x5594393a7f80, this=0x559439383b90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x559438947aa0, signal_index=3, argv=0x7ffcb6e9b950) at kernel/qobject.cpp:3886 [...] #9 0x7fa17074e636 in QScreen::geometryChanged (this=this@entry=0x559438947aa0, _t1=...) at .moc/moc_qscreen.cpp:372 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 450553] New: Edit Applications menu crashes when save button is clicked
https://bugs.kde.org/show_bug.cgi?id=450553 Bug ID: 450553 Summary: Edit Applications menu crashes when save button is clicked Product: kmenuedit Version: 5.23.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: philbyj...@yahoo.com Target Milestone: --- Application: kmenuedit (5.23.5) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.16.9-200.fc35.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 35 (KDE Plasma) DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Created a New Item, Moved several existing Applications into the New Item menu (drag and dropped). Clicked Save. Edit Application segfaults. - Unusual behavior I noticed: None - Custom settings of the application: None The crash can be reproduced every time. -- Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault [KCrash Handler] #4 0x7fb7423da704 in KService::desktopEntryName() const () from /lib64/libKF5Service.so.5 #5 0x55e29dc50689 in GlobalAccel::changeMenuEntryShortcut(QExplicitlySharedDataPointer const&, QKeySequence const&) () #6 0x55e29dc50bfe in MenuFolderInfo::save(MenuFile*) () #7 0x55e29dc469a6 in TreeView::save() () #8 0x7fb740e2b430 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7fb741a02916 in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5 #10 0x7fb741a0562c in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5 #11 0x7fb741b005aa in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 #12 0x7fb741b00707 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7fb741bfd31e in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7fb741a4be7e in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7fb741a09443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7fb741a11074 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7fb740df77d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7fb741a0fb57 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #19 0x7fb741a65450 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7fb741a686e5 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7fb741a09443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7fb740df77d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #23 0x7fb741385b98 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #24 0x7fb741365c9c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #25 0x7fb72f38f11e in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5 #26 0x7fb73f69905f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #27 0x7fb73f6ee2a8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #28 0x7fb73f696853 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #29 0x7fb740e48bb8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #30 0x7fb740df61e2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #31 0x7fb740dfe724 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #32 0x55e29dc377ef in main () [Inferior 1 (process 51324) detached] The reporter indicates this bug may be a duplicate of or related to bug 426822. Possible duplicates by query: bug 426822, bug 423726, bug 419386, bug 417097, bug 416486. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454397] Excessive shortcut to lock screen
https://bugs.kde.org/show_bug.cgi?id=454397 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454397] Excessive shortcut to lock screen
https://bugs.kde.org/show_bug.cgi?id=454397 --- Comment #1 from John --- I agree! I have always used just the Meta+L as that's the key combination that I'm used to coming from Windows 7. Also I didn't know about the CTRL+ALT+L (until now), but even if I did, I would probably never used it as it requires more keys. As a phpStorm user this affects me too: https://www.jetbrains.com/help/phpstorm/mastering-keyboard-shortcuts.html?q=Ctrl%2BAlt%2BL&s=full -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 454398] Search engine selection is uneffective
https://bugs.kde.org/show_bug.cgi?id=454398 John changed: What|Removed |Added CC||ilikef...@waterisgone.com --- Comment #1 from John --- Seems to work for me if I write "g:test" to search "test on Google Tested in latest KDE Neon testing with: KDE Plasma version : 5.24.90 KDE Frameworks version: 5.95 Qt version: 5.15.4 Kernel version 5.13.0-44-generic -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 454398] Search engine selection is uneffective
https://bugs.kde.org/show_bug.cgi?id=454398 John changed: What|Removed |Added CC|ilikef...@waterisgone.com | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454422] RFE: Improve the way updates are downloaded, applied and the user is notified
https://bugs.kde.org/show_bug.cgi?id=454422 John changed: What|Removed |Added CC||ilikef...@waterisgone.com --- Comment #1 from John --- In my opinion Flatpaks should be updated as the user prefers for other updates, automatic or manual. Or some options could be added for each type of packages, system, Flatpak, Snap and AppImage in the future. I normally prefer to update them manually as I don't work to have anything broken during the work days and also I don't want to do it over mobile connections with limited traffic data. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454432] [RFE] Add viewer for windows binaries metadata
https://bugs.kde.org/show_bug.cgi?id=454432 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454077] Translucency effect: Menu transparency settings not working on Wayland
https://bugs.kde.org/show_bug.cgi?id=454077 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454379] plasmashell starts lagging after any file is copied from dolphin and dolphin is closed
https://bugs.kde.org/show_bug.cgi?id=454379 John changed: What|Removed |Added CC||ilikef...@waterisgone.com --- Comment #2 from John --- For me, using Kubuntu 21.10 on a BTRFS+Zstd partition and latest KDE Plasma from Kubuntu's backports PPA, I've seen KDE Plasma many times becoming very slow and even unresponsive to the point that everything freezes with heavy IO operations like copying many folders and files or extracting archives. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454303] Not show videoinfo on information panel
https://bugs.kde.org/show_bug.cgi?id=454303 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 454302] [Feature Request] Do Not Disturb times (configured via KCM)
https://bugs.kde.org/show_bug.cgi?id=454302 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 454296] Present windows broken with 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454296 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454434] New: Space gap in Dolphin between Details view mode and the location field
https://bugs.kde.org/show_bug.cgi?id=454434 Bug ID: 454434 Summary: Space gap in Dolphin between Details view mode and the location field Product: dolphin Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: ilikef...@waterisgone.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** A gap between the details view mode icon and the location bar *** STEPS TO REPRODUCE 1. Open Dolphin 2. Look at the horizontal bar below the title bar that has the navigation buttons (back, forward) and the 3 view modes (Icons, Compact, Details) and the location field showing the current directory location OBSERVED RESULT Between the 3rd detail mode (the Details one) and location section that starts with either ">" or "/" there's now a gap (just the background), which was not there before, at least in the versions of KDE Plasma that I've used in Kubuntu until Kubuntu 21.10 EXPECTED RESULT To be no space game and the Details view mode icon to be close to the location field Like you can have if you grab the vertical line that separates the left navigation panel and the right content panel and drag it left until the location field is right next to the Details view mode icon If this was changed intentionally to make the texts not be trimmed in the left navigation panel, maybe it would be better to detach the vertical line separating the two panels from the location field. It seems that grabbing it moving it to the right it moves also the location field to the right increasing that gap SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454434] Space gap in Dolphin between Details view mode and the location field
https://bugs.kde.org/show_bug.cgi?id=454434 --- Comment #1 from John --- Also I see that if I drag that vertical line to the left and make the navigation panel narrow enough for the item to be trimmed (to show with ... at the end) hovering over them doesn't display a tooltip with their full name. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454436] New: Tooltips are not appearing in Dolphin
https://bugs.kde.org/show_bug.cgi?id=454436 Bug ID: 454436 Summary: Tooltips are not appearing in Dolphin Product: dolphin Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: view-engine: tooltip Assignee: dolphin-bugs-n...@kde.org Reporter: ilikef...@waterisgone.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** Tooltips are not appearing in Dolphin *** STEPS TO REPRODUCE 1. Open Dolphin 2. Hover over the toolbar (the one below title bar) buttons and see how the tooltips are appearing with explanations of what those buttons do 3. Make the left and right panel width narrow enough by dragging the vertical separator to the left until those locations are truncated (showing ... at then end of the names) and the right edge until the content (folder and files) names are trucated ADDITIONAL STEPS 1. Open another program, for example Kate, so that the new program is focused, but Dolphin still visible 2. Open Dolphin's configuration window OBSERVED RESULT The title bar and toolbar tooltips seem to show up as expected In the left and right panel, there are no tooltips, even if the names are truncated and you need to see their full names With the additional step 1 of having Kate open too and focused, hovering on Dolphin toolbar icons shows them highlighted with the blue edges, but the tooltips don't appear anymore With the additional step 2 of viewing Dolphin's configuration window, many options don't have tooltips with explanations. For example in General -> Behavior Show selection marker" EXPECTED RESULT Show tooltitps everywhere, especially when folder and file names are truncated, even if the "Show tooltips" option is not enabled in the configuration window With another program opened and focused, like Kate, I still want to see the tooltips while I hover over stuff in Dolphin For example in this case I was writing in Kate a list of bugs to report later and at this step I had just to hover on Dolphin without having to click anything. And the same with working with side by side windows, I want to see the tooltips on the non-fucused window too. Currently in side by side view it's working on the non-focused windows only on title bar buttons and content if the "Show tooltips" is enabled, but not on the toolbar or for the items that are truncated. Show tooltips in Dolphin's configuration window, at least for some option that are not so easy to understand like ""Show selection marker" SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover Tested on Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454436] Tooltips are not appearing in Dolphin
https://bugs.kde.org/show_bug.cgi?id=454436 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454434] Space gap in Dolphin between Details view mode and the location field
https://bugs.kde.org/show_bug.cgi?id=454434 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454438] New: No option to turn off the default full row selection
https://bugs.kde.org/show_bug.cgi?id=454438 Bug ID: 454438 Summary: No option to turn off the default full row selection Product: dolphin Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: ilikef...@waterisgone.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** No option to turn off the default full row selection in Details view mode *** STEPS TO REPRODUCE 1. Open Dolphin 2. Click anywhere, but not directly on a folder or file OBSERVED RESULT With the default Clicking files or folders set to open them, the folder on that row will be open and we'll move inside or the file will be open. This is really annoying as it leads to too many mistakes! Plus I can never switch family and friends to Linux with KDE Plasma if it comes with these kind of defaults with no options to turn them off. EXPECTED RESULT Don't do anything if I haven't clicked directly on that folder or file so it would be better if it weren't enabled by default. Another think that I expect is for such a feature to have an option in Dolphin's configuration window to enable it when we are ready for it or if we already have similar experience At the moment I have switched "Clicking files or folders" to just select them as that was annoying on its own, but now combined with this feature too makes every unusable as there's no place where I can click safely without something unexpectedly open It mitigates the problem, but still want this to be off by default or at least have an option to turn it off myself. Also an intermediate option for the selection to have the same width as the name column instead of spanning over all the columns would be nice. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454438] No option to turn off the default full row selection
https://bugs.kde.org/show_bug.cgi?id=454438 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454440] New: he "Most Used Pages:" show "Energy Saving" on first run
https://bugs.kde.org/show_bug.cgi?id=454440 Bug ID: 454440 Summary: he "Most Used Pages:" show "Energy Saving" on first run Product: systemsettings Version: 5.24.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Quick Settings Assignee: plasma-b...@kde.org Reporter: ilikef...@waterisgone.com Target Milestone: --- SUMMARY *** The "Most Used Pages:" show "Energy Saving" on first run *** STEPS TO REPRODUCE 1. Open System Settings 2. Don't click on anything and just look at the "Most Use Pages" on the first page OBSERVED RESULT The "Most Used Pages:" show "Energy Saving" EXPECTED RESULT To show "None" or nothing. Maybe even to not display the "Most Used Pages:" itself as it's pointless if it's the first time I'm opening it SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover Tested on Wayland -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454442] New: Opening Discover without having an network connection makes it freeze
https://bugs.kde.org/show_bug.cgi?id=454442 Bug ID: 454442 Summary: Opening Discover without having an network connection makes it freeze Product: Discover Version: 5.24.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ilikef...@waterisgone.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** Opening Discover without having an internet connection makes it freeze *** STEPS TO REPRODUCE 1. Boot KDE Neon and open Discover without having a wired or wireless connection active OBSERVED RESULT The loading progress bar under the "Loading..." text is freezing (nothing is moving) If we try to maximize the window at that time, Discover will freeze (showing the unresponsive text and whitening) The same if it opens in fullscreen mode and we try to restore it to windowed mode And the same if try to close it, it will freeze for a while and when it comes back it will finally close. EXPECTED RESULT I expect Discover to open without freezing and becoming unresponsive in the cases where there's no wired, wireless connection, the computer is in Airplane mode, hotspot mode or there is some kind of network connection, but there's isn't internet accessiblity. I want it to be fast and let me do whatever I want as soon as I open it, for example clicking on the "Installed" tab to look at the installed software. Since all the installed software is locally installed, it makes no sense for me to not be able to do that or to be delayed by some network connection. Also in the case I opened Discover by mistake I want to be able to close it as soon as possible without any delay. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso Tested on Wayland -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454442] Opening Discover without having an network connection makes it freeze
https://bugs.kde.org/show_bug.cgi?id=454442 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454445] New: It would be nice if RGB range: Automatic would also display the currently chosen value
https://bugs.kde.org/show_bug.cgi?id=454445 Bug ID: 454445 Summary: It would be nice if RGB range: Automatic would also display the currently chosen value Product: systemsettings Version: 5.24.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: ilikef...@waterisgone.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** It would be nice if RGB range: Automatic would also display the currently chosen value *** STEPS TO REPRODUCE 1. Open systems Settings 2. Go to Display and Monitor 3. Look at RGB range value (I'm not sure if this is available for all GPU vendors), it might be an Intel only thing. OBSERVED RESULT The RGB range value by default is Automatic. But it's not clear which one of the two values (Full, Limited) has been automatically choosen for the current GPU / computer EXPECTED RESULT To display if possible which option has been choosen automatically so we know if the best value for our GPU / monitor is being used or we need to check the cables, upgrade the Linux kernel, Mesa drivers, etc. Something like: Automatic (current: Full) Or Automatic (current: Limited) Right now since it's not clear which one has been selected automatically I always go there change it manually to Full just to be sure, but I would like to avoid doing that if I see that the Automatic chooses the right thing for my computer. If this depends on the driver and the drivers doesn't report back what it has chosen, then tthat's it, it's ok leaving as it is. Maybe explain why this is not possible in that tooltip next to it and hopefully one day the driver developers seeing it, will add that information too to their drivers in a way that KDE can read it and display it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover Tested on Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454445] It would be nice if RGB range: Automatic would also display the currently chosen value
https://bugs.kde.org/show_bug.cgi?id=454445 --- Comment #2 from John --- (In reply to Zamundaaa from comment #1) > It would indeed be nice, sadly the driver doesn't currently expose that sort > of information to us. It's a known problem and will hopefully be tackled > soon™ with all the other color management stuff being worked on. However, I > fully expect it to still take a long while to be done. > Other than just waiting for that kernel fix, we could also > 1. roll our own automatic detection. Something basic should be pretty quick > to set up, although it may depend on us parsing more edid info (which I'd > like to avoid diving into until we can use libedid to take care of that for > us). Or > 2. remove the automatic option completely and always default to full rgb > range. Something like 98% of monitors and TVs out there have that and new > ones should all be full rgb range, so it likely wouldn't be that bad. > > Both have the problem that they can cause unexpected regressions for some > users with limited rgb TVs though... I would go with option number 2 as long as the users that have monitors and TVs that do not support the full range can still navigate to that control panel page and change it to limited. >From what I understand they should still be able to do that. As for the other option I understand and I would wait for the libedid too. If nothing could be done now, I completely understand. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454438] No option to turn off the default full row selection
https://bugs.kde.org/show_bug.cgi?id=454438 --- Comment #2 from John --- (In reply to Nate Graham from comment #1) > The change is intentional, so let's focus on the problems you're having with > it so we can try to address them without reverting the change or making it > optional. We would like to only do one of those as a last resort. > > > there's no place where I can click safely without something unexpectedly > > open > There is empty space on the left side of the file view that you can click > in. You can also de-select everything by hitting the Esc key. > > Is that okay? Would simply saying that I don't like it or that I like the old behavior more be a valid answer? I'm a long time Windows 7 user and a KDE Plasma user for about 4 years and I like the old behavior. I never felt that that something need to be improved there or that I need a whole row selection. Maybe also because it's more careless and fast, I can drop folder or files pretty much anywhere in the main folder as long as I don't drop the on other folders, which is easy as they are all on the left side, instead of having to care to drop them exactly at the narrow space at the edges. Sometimes I want to select some folders or files that happen to have longer names than the others so I use the trick of dragging the mouse and making the normal multi-selection rectangle, but I drag it left so that it just touches the folders or files that have the longer names and stop immediately to not go further and select also the others. I see that this is still possible in the compact view mode, but my favorite view mode is the Details one which I use almost all the time and it's exactly the one that is affected Another thing that I want is to move in the future my family and friends to Linux and KDE Plasma of course, but I bet some of them will be annoyed by the behavior that it's not like in Windows with which they are used to and will ask me to change it, to which of course I will have to say that I can't making me wonder if I did the right thing of moving them to Linux or moving them to KDE Plasma instead of Cinnamon or other DE that might be more Windows-like. Depending on how many little things like this they don't like I will be forced to move them or an older version of KDE Plasma in case I want them to still benefit from Wayland but don't have the things they don't like, are used to or willing to learn. Why is it exactly such a big deal to make it optional? Shouldn't Windows or KDE Plasma have had it from the beginning or way more in the past if it was so clear that majority of users wanted it? I don't know, but I don't want to bring frustration to my family members and friends I cannot customize KDE to behave like Windows in case they prefer that behavior and that will mean that I will not introduce KDE to them, but another one that is more adaptable. It's not what I want, but also I'm not used to KDE to bring features without an option to turn them off or change them in any way. As for the empty space, I am seeing it now, I have a bit of tunnel vision and it's easier for me to miss some things on the sides. I see that there is some space on the right too, when the window is in fullscreen mode. When it's tiled to the right half screen there's no empty space left on the right And another problem that I can notice even in fullscreen mode, is that if you resize for whatever reason the "Modified" column or whatever column is last until it touches the right edge, then the empty space on the right side disappears. On the left that seems to not be a problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454518] New: Fall Apart effect flashes at the end
https://bugs.kde.org/show_bug.cgi?id=454518 Bug ID: 454518 Summary: Fall Apart effect flashes at the end Product: kwin Version: 5.24.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: ilikef...@waterisgone.com Target Milestone: --- SUMMARY Fall Apart effect flashes at the end of animation STEPS TO REPRODUCE 1. Switch to the Wayland session 2. Enable the "Fall Apart" effect 3. Open and close some windows OBSERVED RESULT After the animation finishes with the window being broken into pieces, it flashes one more time allowing you to see the exact window that you closed for a very short period of time EXPECTED RESULT The Fall Apart effect works normally with the window breaking into pieces without flashing it again SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + all updates from Discover Tested on Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #479 from John --- This is definitely the main reason why I don't use multiple workspaces as usability definitely sucks without having a quick way to identify which workspace is which and the different wallpapers would've been the best thing for that. I could've even used a wallpaper with a house or my favorite picture for the home one or I could've used an image editing program to add even numbers on them or other texts. I can't believe that I had this possibility 12 years ago in Gnome 2 with Compiz, which made the cube even better, and now we still can't have that in modern desktop environments. I know about activities, but honestly I never got into them as they seem to complicated for what I want compared to having a few workspaces that you switch between. I hope some day somebody solves this huge usability problem for me so I can finally use workspaces again as I used to. If I were to design this, I would've just linked each workspace with a set of wallpapers, a set of panels, a set of widgets, a set of icon shortcuts to applications and a set of folders and files that belong to it with an option for each set of things to span on multiple workspaces (to be the same one), like in the case the user wants the same panel or widgets in all or multiple workspaces. I assume this is pretty hard to do, but I think it should solve all the problems and wishes for everybody. and in case of using the cube this would be great. Imagine wanting to play a game and just having to switch to the "gaming" side of the cube where I have a gaming wallpaper, widgets with temperatures for when I alt-tab out of a game, shortcuts on the desktop for all my games or launchers like Steam and Lutris I would find that pretty intuitive and easy to use. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454518] Fall Apart effect flashes at the end
https://bugs.kde.org/show_bug.cgi?id=454518 --- Comment #1 from John --- I think I found a way to make it even worse. If the window that you close was in fullscreen mode it will just flash for a moment at the end of the animation as I said above. But if you keep the window as it was when it opened first time or restore it from fullscreen one to the windowed mode, then close it and immediately move the mouse left right or in a circle where the window was positioned, you can see it flicker again. In my case I can see it flicker again as soon as I move the mouse. If I stop it disappears and if I move it again it starts flickering gain. If flickers frequent enough that I even tried to click on its close button, but it doesn't work or click and drag the title bar. Clicking also doesn't stops it to flicker, but if I drag a selection rectangle on the desktop, the it stops and disappears completely. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454518] Fall Apart effect flashes at the end
https://bugs.kde.org/show_bug.cgi?id=454518 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 454519] New: The help center doesn't open on its index page
https://bugs.kde.org/show_bug.cgi?id=454519 Bug ID: 454519 Summary: The help center doesn't open on its index page Product: khelpcenter Version: 5.8.22041 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: ilikef...@waterisgone.com Target Milestone: --- SUMMARY The help center doesn't open on its index page (first page, contents) STEPS TO REPRODUCE 1. Use KDE Neon 2. Open start menu 3. Click on Help OBSERVED RESULT The Help center opens in windowed mode with a left panel opened by default and the right panel / content blank (white) Making it fullscreen seems to make the left panel unnecessary wide None of the texts lengths in it it seem to require that much space in fullscreen mode Clicking on the first item in the "Contents" tab, which is "Fundamentals" seems to bring the index page on the right panel If the user has changed the setting "Clicking files or folders" in the control panel to "Selects them" before opening the Help center, the just simply clicking on the "Fundamentals" or "Introduction" doesn't work anymore like before EXPECTED RESULT The Help center should open with its first page with its first page, contents already visible in the right / content panel instead of just a blank white page. If the the user makes the program fullscreen from the "Maximize" button or dragging it to the top edge, the left panel width should not be proportional to how it was in the windowed mode as the text has not increased proportionally to require that and it uses too much space that it's better used in the other, the content panel. The help center should not follow the "Clicking files or folders" setting from the control panel and should always work with single clicks in the left panel, it's easier that way and probably better for usability. Also the "Clicking files or folders" option clearly says it's for files or folders, not for links / anchors like in that panel. BTW, one more thing, the top level items in that panel, like the "Fundamentals", "Plasma Manual" doesn't have that right pointing arrow to signal that they have other subsections. Maybe it is intentional because of the already existing icons made it harder to add it too, but I though to mentioned it too, maybe having a complete tree-view it's better to understand where you are and how sections are organized, which are single pages and which have subsections SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover Tested on Wayland -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 454519] The help center doesn't open on its index page
https://bugs.kde.org/show_bug.cgi?id=454519 John changed: What|Removed |Added Platform|Other |Neon Packages CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 454523] New: Password input loses focus too easy
https://bugs.kde.org/show_bug.cgi?id=454523 Bug ID: 454523 Summary: Password input loses focus too easy Product: plasma-nm Version: 5.24.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ilikef...@waterisgone.com Target Milestone: --- SUMMARY The password input for wireless networks loses focus too easy if mouse is moved STEPS TO REPRODUCE 1. Click on the wireless icon in systray (near the clock / date) 2. Click on the "Connect" button for a network 3. Move the mouse in pretty much any direction you want before typing the password or after you typed a few characters 4. Try to type the password now or the remaining part of it 5. In case it doesn't work, try to hover back the the network and its password input field OBSERVED RESULT After clicking on the "Connect" button for a network as soon as the mouse leaves the rectangle with the selection of network and its password input the password input field loses focus and you cannot enter the password or continue to enter it anymore if you already typed some of it. Moving back over that big rectangle or even over the password input doesn't make it regain focus. The only thing that does is clicking directly into that password input field. One case where you can move the mouse after clicking the "Connect" button and not have the password input field lose focus is if the network you want to connect is the first one in the list and you move the mouse upwards. Another case is if you don't move the mouse after clicking that button, but you scroll down so the network and its password input moves up, but the focus is not lost EXPECTED RESULT The password input field keeps its focus for as long as possible no matter in which direction I move the mouse after I click the "Connect" button, as long as I don't click the "connect" button for other network for which its password input field should have focus In the worst case moving back the the rectangle containing the network name and its password input field should focus automatically the password input field to be able to type the password. I'm using many times my laptop in bed with a mouse so after I click the Connect button I leave my mouse to put both hands on the keyboard to type the password. Being in bed, means that the mouse sometimes moves alone by itself as soon as I let it go which I think it's one of the reasons that I'm seeing this I guess the mouse was also moving in other cases, but as Windows 7 and other Linux DEs use a pop-up window that is always focused no matter where and how much the mouse moves, I never saw this problems somewhere else. I'm not saying I want a pop-up window to type the password as I like the current design more, but the focus should try harder to stay on password input field the last network where I clicked the "Connect" button. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover Tested on Wayland BTW, for this bug I really didn't know which is the right product where to report it as for others I use the system monitor to see the name of the process that I opened. Please move it to the right place if you can or let me know to recreate it in another place so this can be deleted. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454526] New: The alternatives menu doesn't close if you click somewhere else
https://bugs.kde.org/show_bug.cgi?id=454526 Bug ID: 454526 Summary: The alternatives menu doesn't close if you click somewhere else Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ilikef...@waterisgone.com Target Milestone: --- SUMMARY The alternatives menu doesn't close if you click somewhere else STEPS TO REPRODUCE 1. Right-click on the start menu or on the hour / date or on the panel 2. Click on the "Show Alternatives" item 3. Don't click on anything there 4. Click on the desktop OBSERVED RESULT In case you change your mind and don't want to switch to an alternative or you want to do it later and not just open something from the desktop, that menu remains open as if it was set to keep open like other windows have. EXPECTED RESULT The menu should close itself as you have changed your mind and you want to do do something else or a call call came in and you had to click the answer button or you had to stop the music, etc. I don't think this is such an important change that it cannot close until the users chooses something. BTW, if you have Firefox open for example, then click on the "Show Alternatives" for the start menu or hour /date and then click on Firefox, it will look like it worked because Firefox comes in front. I noticed only after I minimized Firefox and saw that the alternatives menu is still open, even though I thought id disappeared, which made me open it again multiple times so in the end I had to click on its "Cancel" button 2-3 times this is how I discovered that you can actually open it multiple time and I don't know what could be useful in that. Maybe if you have installed an alternative in the meantime, but probably the one that it's already open should be refreshed to show also the newly installed alternative instead of open it again in front of the other one SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover Tested on Wayland Not sure if this is really a bug or it works as intended, but to seemed more of a bug or at least a bit strange. BTW I didn't know in which product should I report this, please move it the the right place if you can or let me know to recreate it somewhere else. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454528] New: The "Apply" button doesn't wok properly on Login Screen (SDDM) page
https://bugs.kde.org/show_bug.cgi?id=454528 Bug ID: 454528 Summary: The "Apply" button doesn't wok properly on Login Screen (SDDM) page Product: systemsettings Version: 5.24.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: ilikef...@waterisgone.com CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- SUMMARY The "Apply" button doesn't wok properly on Login Screen (SDDM) page STEPS TO REPRODUCE 1. Go to System Setting -> Startup and Shutdown -> Login Screen (SDDM) -> Behavior... 2. Uncheck the "Log in again immediately after logging off" 3. Hit the "Apply" button to save changes OBSERVED RESULT The "Apply" button is still clickable and you have to click it again. If try to close the window after you have clicked it once, it will ask you to apply the changes so clicking once was definitely not enough, but if you choose "Discard" and reopen the same location again you will see that the changes were actually applied as that checkbox is not ticked anymore. Now, if you reopen the same location and want to do the reverse, to tick that checkbox, you can't as it's disabled To make it enabled again you have to tick also the checkbox next to (on the right of) the "Automatically log in" and choose a user, but that drop-down box seems to not show any options. EXPECTED RESULT After ticking that checkbox hitting the "Apply" button once should be enough with the button showing pressed and not letting you to click it again and also closing the window should not ask you to apply the changes. Opening the same page to do the reverse, should be just as easy and the checkbox should be tickable without needing to configure the other stuff as the other stuff was not configured when it was ticked and enabled last time. If the user unticked a single checkob to disable somehting, then it should be able to tick that single checkbox to enable it again Also that drop-down with the users should display some values, at least the current user SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION From: neon-testing-20220524-1822.iso + updates from Discover Tested on Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450786] Privacy problem: deleted annotations are not deleted
https://bugs.kde.org/show_bug.cgi?id=450786 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452243] Programs running on Xwayland randomly crash and Xwayland stops working
https://bugs.kde.org/show_bug.cgi?id=452243 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454590] wayland amd memleak
https://bugs.kde.org/show_bug.cgi?id=454590 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434379] 10bit HDR video render not supported
https://bugs.kde.org/show_bug.cgi?id=434379 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389568] Feature to reset all settings to default values
https://bugs.kde.org/show_bug.cgi?id=389568 --- Comment #35 from John --- (In reply to phrxmd from comment #34) > I would really appreciate this. > ... > Plasma has come some way thanks to indicating changed settings in System > Settings - but this only highlights that Plasma clearly knows what the > defaults are, so it should be possible to reset to them with one click of a > button, instead of setting each of them individually, no? Meh... not everything supports this highlight yet!!! :( And that's the problem that keeps us waiting... Would be a great step in the right direction :) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 394672] Please add AppImage support to KDE Neon
https://bugs.kde.org/show_bug.cgi?id=394672 John changed: What|Removed |Added CC||johnmaveric...@mail.com --- Comment #3 from John --- Please, let's not forget about the update/auto-update of appimages! That's a very important point too!!! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436928] Option to apply updates on shutdown, not startup
https://bugs.kde.org/show_bug.cgi?id=436928 --- Comment #8 from John --- Harald Sitter's *User B* is definitely the desired mode around here. (i prefer to get updates as soon as possible - even if it causes some system instability - but for all other workers here, User B is perfect) Is there any PackageKit bug report on the issue Aleix Pol describes about applying updates on shutdown? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465792] New: 5.27: Panel shows white border instead of transparency/shadow. Flickers occasionally
https://bugs.kde.org/show_bug.cgi?id=465792 Bug ID: 465792 Summary: 5.27: Panel shows white border instead of transparency/shadow. Flickers occasionally Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jd.prim...@proton.me CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 156283 --> https://bugs.kde.org/attachment.cgi?id=156283&action=edit Screenshot of plasma panel with white border 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 *** This is my first bug report so hopefully it isn't too bad. STEPS TO REPRODUCE 1. Load plasma, Scaled display 150% 2. Panel has white border that sometimes flickers OBSERVED RESULT White border around plasma panel. It sometimes flickers. Also effects the sides of tooltips and the top of the plasma application menu. EXPECTED RESULT A plasma panel with no border, plasma panel draws shadow. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel: 6.1.10-1 GPU: 12th gen Intel iGPU - i915 drivers Display: 2256x1504 @ 150%, 60Hz ADDITIONAL INFORMATION I have attached a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465792] 5.27: Panel shows white border instead of transparency/shadow. Flickers occasionally
https://bugs.kde.org/show_bug.cgi?id=465792 John changed: What|Removed |Added Keywords||wayland --- Comment #1 from John --- Forgot to mention this is on wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465822] New: 5.27: Desktop context menu flickers, disappears, and other graphical glitches
https://bugs.kde.org/show_bug.cgi?id=465822 Bug ID: 465822 Summary: 5.27: Desktop context menu flickers, disappears, and other graphical glitches Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: jd.prim...@proton.me CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 Created attachment 156290 --> https://bugs.kde.org/attachment.cgi?id=156290&action=edit Display setup screenshot 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 *** Only my second bug report please let me know if I am missing any info. STEPS TO REPRODUCE 1. Have 2 monitors, external monitor is 1920x1080 no scaling native monitor is 2256x1504 @ 150% scaling 2. Right click on background 3. Navigate to submenu OBSERVED RESULT After navigating to sub-menu the main context menu disappears and starts experiencing flickering and other graphical issues (video attached). I had a similar issue on 5.26 where parts of the menu would disappear but the flickering is new. EXPECTED RESULT A stable context menu with no graphical glitches. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed 20230213 / Plasma 5.27.0 (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel: 6.1.10-1 Graphics Platform: Wayland Display Information: 1920x1080 no scaling 120Hz & 2256x1504 @ 150% scaling 60Hz (will attach picture) GPU: Intel 12th gen iGPU - i915 drivers. ADDITIONAL INFORMATION Glitching only happens on scaled monitor. Link to video w/ glitching https://youtu.be/ijreBrRzkyA -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465822] 5.27: Desktop context menu flickers, disappears, and other graphical glitches
https://bugs.kde.org/show_bug.cgi?id=465822 John changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465822] 5.27: Desktop context menu flickers, disappears, and other graphical glitches
https://bugs.kde.org/show_bug.cgi?id=465822 --- Comment #2 from John --- (In reply to David Edmundson from comment #1) > Please see https://bugreports.qt.io/browse/QTBUG-93380 > > Hopefully should all be resolved by Plasma 6. Sounds good. Out of curiosity, do you know why it's flashing/strobing more on 5.27 than on 5.26? Is there something that's refreshing the desktop or menu? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466248] New: Discover's Notifier Tray Icon does not show
https://bugs.kde.org/show_bug.cgi?id=466248 Bug ID: 466248 Summary: Discover's Notifier Tray Icon does not show Classification: Applications Product: Discover Version: 5.27.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: plasma-b...@kde.org Reporter: johnmaveric...@mail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 156606 --> https://bugs.kde.org/attachment.cgi?id=156606&action=edit Tray Elements config SUMMARY Discover's Notifier Tray Icon - sometimes - does not show (even when it's configured to be always visible on taskbar) I actually don't have steps to reproduce it, because it's apparently random. With the default configuration it sometimes shows up, sometimes it doesn't. I original though it depended on whether there was updates or not (even with it completely invisible from the tray popup), but then - when it showed up - i configured it to be always visible and still sometimes it shows and then sometimes it doesn't. EXPECTED RESULT: Should be visible SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This is not a new problem. It happened on 5.26, on 5.102 and on x.org (if it helps...) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466248] Discover's Notifier Tray Icon does not show
https://bugs.kde.org/show_bug.cgi?id=466248 John changed: What|Removed |Added CC||johnmaveric...@mail.com --- Comment #1 from John --- Created attachment 156607 --> https://bugs.kde.org/attachment.cgi?id=156607&action=edit Tray Sometimes it shows here as well -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466248] Discover's Notifier Tray Icon does not show
https://bugs.kde.org/show_bug.cgi?id=466248 John changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=413053 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413053] Can't remove Discover Update Notifier from System Tray
https://bugs.kde.org/show_bug.cgi?id=413053 John changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466248 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466248] Discover's Notifier Tray Icon does not show
https://bugs.kde.org/show_bug.cgi?id=466248 John changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=434241 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434241] Discover Notifier no longer appears in System Tray when using systemd startup
https://bugs.kde.org/show_bug.cgi?id=434241 John changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466248 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465001] Multi monitor: Third monitor can not be used until after a seep / wake cycle
https://bugs.kde.org/show_bug.cgi?id=465001 John changed: What|Removed |Added Component|general |multi-screen Version|unspecified |5.26.90 Assignee|neon-b...@kde.org |kwin-bugs-n...@kde.org Product|neon|kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465001] Multi monitor: Third monitor can not be used until after a seep / wake cycle
https://bugs.kde.org/show_bug.cgi?id=465001 --- Comment #2 from John --- Modified to be reported under kwin / multimonitor as per blog post by Marco Martin. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 466470] New: Web Tools Are Unusable - Regression
https://bugs.kde.org/show_bug.cgi?id=466470 Bug ID: 466470 Summary: Web Tools Are Unusable - Regression Classification: Applications Product: Falkon Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kdelo...@mozej.com Target Milestone: --- SUMMARY 1. "Inspect Element" has no close button. How do you close it? There's absolutely no way to close it. 2. "ctrl+u" all lines go beyond the screen, which renders ctrl+F unusable. Someone removed "wrap long lines" EXPECTED RESULT 1. Add close button to "inspect element" 2. Make "wrap long lines" the default behavior in "ctrl+u" (or at least revert the regression). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (not Manjaro) (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459778] Screen occasionally freezes "EGL_BAD_SURFACE" errors when launching application while using the Klassy window decoration
https://bugs.kde.org/show_bug.cgi?id=459778 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 255831] I cannot edit the label of a fat32 or ext4 partition, label text field not typable
https://bugs.kde.org/show_bug.cgi?id=255831 John changed: What|Removed |Added CC||ilikef...@waterisgone.com --- Comment #3 from John --- I can confirm this problem still exists on KDE Partition 22.12.3! On Debian 12 (unstable repository). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 466992] New: KDE Partition Manager shows the partition name as label and doesn't allow you to change one
https://bugs.kde.org/show_bug.cgi?id=466992 Bug ID: 466992 Summary: KDE Partition Manager shows the partition name as label and doesn't allow you to change one Classification: Applications Product: partitionmanager Version: 22.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: ilikef...@waterisgone.com Target Milestone: --- Created attachment 157075 --> https://bugs.kde.org/attachment.cgi?id=157075&action=edit Partitions with names and labels set and a partition properties window opened SUMMARY KDE Partition Manager shows the partition name as label in its UI (both in column headers and properties window) And it doesn't allow you the create / edit / delete a partition name. STEPS TO REPRODUCE 1. Use GParted 2. Create or use a GPT partition table on some disk 3. Create a BTRFS partition and fill both the name an label fields with something unique that helps you differentiate later which is which. OBSERVED RESULT My root partition has: Name: Linux-name Label: Linux-label My home partition has: Name: Home-name Label: Home-label And GParted, with which I created the partition table and partitions, giving them names and labels before installing the OS, shows them in the proper columns similar to the fields where they were created. 1. All the partition names under a column named "Name" 2. All the partition labels under a column named "Label" 3. Both the name and the label can be added or edited later from the context menu. For mounted partitions only after version 1.4.0 There was a bug that didn't allow to to this on mounted file systems before this version: https://gparted.org/news.php?item=243 While KDE Partition Manager shows them in a confusing manner, not similar to the fields where they were created 1. All the partition names under a column named "Partition Label" 2. All the partition labels under a column named "Label" 3. Only the label can be added or edited later from the properties window EXPECTED RESULT 1. I expect that all partition names are shown under a column named "Name", instead of "Partition label" how it is now. 2. I expect that when I open the context menu on a partition and click on "Properties" item, I see a row there named "Name" instead of "Partition label" how it is now. This is confusing since we already have label, which of course it's a partition label since we're talking about partitions, same as with the columns. 3. I expected that the name can be added or edited if it's already there, similar to how you can do with the label Optional but nice if possible: 4. I expect to have in the Properties window, the Name field immediately after the Label field to quickly be able to see them both and add or edit them and because to me they are logically related by being a type of a user-friendly description of that partition. 5. If Label remains the first field of this description and Name immediately after it, I expect a "Copy label" button next to name field, if possible, to be able to quickly use the same name if I want to do that. If 4. it's not possible, because they are grouped like in Gparted properties window (File system and Partition), then I would like to see groups labels too, as those horizontal lines are not clear not me at all on what sections they want to separate. Maybe you can do something like the fieldset / legend in HTML: https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_fieldset To me that would be more clear which are part of which, even though it would not help much to understand if the name or label is more useful or supported or I should just continue to add them both. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 ADDITIONAL INFORMATION For my installation I named and labeled the partitions and used the "-name" and "-label" suffixes to be more clear to me which ones are displayed in Dolphin and used anywhere else and as a good way to learn how Linux works. Leaving them empty or typing the same thing in both would've made my learning process harder. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 466992] KDE Partition Manager shows the partition name as label and doesn't allow you to change one
https://bugs.kde.org/show_bug.cgi?id=466992 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 466994] New: KDE Partition Manager cannot change the label on a FAT32 partition
https://bugs.kde.org/show_bug.cgi?id=466994 Bug ID: 466994 Summary: KDE Partition Manager cannot change the label on a FAT32 partition Classification: Applications Product: partitionmanager Version: 22.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: ilikef...@waterisgone.com Target Milestone: --- Created attachment 157077 --> https://bugs.kde.org/attachment.cgi?id=157077&action=edit The label not being editable in the Properties window on a FAT32 partition and how the label looked like before being edited from the terminal with the fatlabel command SUMMARY KDE Partition Manager cannot change the label on a FAT32 partition STEPS TO REPRODUCE 1. Open KDE Partition Manager 2. Create or use a GPT partition table on some disk 3. Create or use a FAT32 partition with a label 4. Open from the the context menu, on that partition, the Properties window OBSERVED RESULT While the text in the label field is selectable and copyable, which is great, there's no cursor there to allow you to edit that text and change it to something else or leave it empty, which should be similar to the state where no label exists, like before one was added. EXPECTED RESULT 1. I expect to be able to edit the label on a FAT32 partition like I can do for other partition types. 2. I expect also that if I delete whatever text was there, so leave it empty, to be like I deleted it, in a similar state as if I never added it, if there's such a difference 3. I expect to be able to edit the name of a FAT32 partition too, but a text field should be added for that first, which maybe will be done when another bug will be fixed: https://bugs.kde.org/show_bug.cgi?id=466992 SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 ADDITIONAL INFORMATION I discovered this bug because I created a few partitions with GParted before installing my OS, including a small FAT32 one for EFI files. Since I like to be a bit organized and I wanted to better understand where all partitions are mounted and used, I filled in the names and labels for them, including this small one, where I've put: Name: EFI-name Label: EFI-label To my surprise, the only label that wasn't exactly like I typed was on this small FAT32 partion, which ended up as "EFI-LABEL" for some reason. I thought that maybe the FAT32 is too old and didn't support lowercase or mixedcase in labels, but today I searched and found out that this is actually not the case as FAT32 supports lowercase or mixed case in labels. It's just Gparted and Windows that doesn't support them. Since I don't dual-boot and have Windows on my computer anymore, I decided to edit it and make it as I wanted, which I couldn't, hence this bug report. Then I decided to try this answer, from where I found out that it should work, on my FAT32 EFI partition: https://superuser.com/a/1575427 With this command: sudo fatlabel /dev/nvme0n1p1 "EFI-label" And its output was: fatlabel: warning - lowercase labels might not work properly on some systems There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) 65:01/00 Not automatically fixing this. I then did a "Refresh devices" in both KDE Partition manager and Gparted, that I had opened before running the command and in both of them the FAT32 EFI partition shows now a label of "EFI-label", exactly how I wanted from the beginning and in a similar patter with the labels of the other partitions So, it's definitely possible to: 1. Set / edit the label of a FAT32 partition. 2. Set / edit the label of a FAT32 partition even if that partition is currently mounted (on /boot/efi, in my case). 3. Lowercase or mixedcase for the label of a FAT32 partition is allowed. 4. The fatlabel command is already installed, at least on my Debian 12 (unstable repository) that I used. BTW, can anyone please check if this bug is related: https://bugs.kde.org/show_bug.cgi?id=255831 I find the the second comment a bit confusing or outdated because: 1. "View -> File System Support" is now "Tools -> File System Support". 2. "so the behaviour you describe is expected" is not expected anymore, as the file system support shows now for FAT32, that both read and write label are supported, provided by dosfstools package, which at least on my Debian 12 is installed by default. 3. "Note that you cannot change the label as long as the file system is mounted." I just did change the label the the FAT32 EFI partition being mounted on /boot/efi. I also seen that a bug not allowing to set the label on a FAT32 partition was once fixed: https://bugs.kde.org/show_bug.cgi?id=254212 If you can add a label, it doesn't make much sense to not b
[partitionmanager] [Bug 466994] KDE Partition Manager cannot change the label on a FAT32 partition
https://bugs.kde.org/show_bug.cgi?id=466994 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 464214] Some of the Wireless network details are wrong
https://bugs.kde.org/show_bug.cgi?id=464214 --- Comment #7 from John --- I had the chance to recently test this on another laptop with a Realtek firmware and there it was the speeds reported were higher. So I guess this depends on the firmware reporting the right thing. I think this bug report can be closed. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 467319] New: KDE Partition Manager is using the same icon as Gparted and it's confusing
https://bugs.kde.org/show_bug.cgi?id=467319 Bug ID: 467319 Summary: KDE Partition Manager is using the same icon as Gparted and it's confusing Classification: Applications Product: partitionmanager Version: 22.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: ilikef...@waterisgone.com Target Milestone: --- Created attachment 157262 --> https://bugs.kde.org/attachment.cgi?id=157262&action=edit Both KDE Partition Manager and Gparted opened SUMMARY KDE Partition Manager is using the same icon as Gparted and it's confusing when you use both STEPS TO REPRODUCE 1. Assuming that KDE Partition Manager is already installed, install Gparted too. 2. Pin them to the task bar or open both of them 3. Try to figure out which is which without hovering them and waiting to see the tooltips OBSERVED RESULT Both KDE Partition Manager and Gparted use the same icon an you cannot differentiate between them just by looking at them. EXPECTED RESULT When they are both installed, I expect to see a visual difference between their icons so I don't waste my time to hover and wait to see which is which. I think Gparted should be displayed with its own icon, like in other desktop environments and not the same that KDE Partition Manager uses. Or at least, if they need o use the same icon, a K and a G letter should be ovelayed on the icon to see which is for which. I don't remember if I opened KDE Partition first and then Gparted so KDE Partition Manager's icon is on the left and Gparted's icon is on the right. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Seen on Debian 12 with the unstable repository and fully updated I don't know if this is a KDE Partition Manager problem or a Gparted one, but I didn't know where it was better to open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 467321] New: KDE Partition Manager's authentication window is left behind
https://bugs.kde.org/show_bug.cgi?id=467321 Bug ID: 467321 Summary: KDE Partition Manager's authentication window is left behind Classification: Applications Product: partitionmanager Version: 22.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: ilikef...@waterisgone.com Target Milestone: --- Created attachment 157263 --> https://bugs.kde.org/attachment.cgi?id=157263&action=edit KDE Partition Manager' authentication window behind SUMMARY KDE Partition Manager's authentication window is left behind STEPS TO REPRODUCE 1. Open KDE Partition Manager 2. If it opened as expected, close it and open it again. 3. If again it opened as expected, close it and try to open it in another way, like from a desktop shortcut or from it being pinned to the task bar OBSERVED RESULT Sometimes the authentication windows is left behind its window so you have to either minimize KDE Partition Manager's window to see it and input the password and press ok or click on the authentication window's icon in the task bar to bring it to front and then input password and press ok to see afterwards the KDE Partition Manager loads its window content in both its panels. It looks like after KDE Partition Manager is started, the authentication window appears first and then the KDE Partition Manager's windows is quickly opened too on top of it, even though it cannot display any content without the authentication window being dealt with first. EXPECTED RESULT One of these solutions: 1. Keep KDE Partition Manager's authentication window On top / front of it, even if it appeared first, so that the password can still be typed and then Ok or Enter pressed, as KDE Partition manager's window is useless without a successful authentication. 2. Do what Gparted is doing, show the authentication window first, as it is right now, but then don't open KDE's partition Manager's window until a proper authentication is made. I prefer solution 1, but I would be ok with 2 also if 1 is too hard to do. Having to always minimize or click on the authentication window's icon every time I open KDE Partition manager is too time consuming and annoying. First time it happened I didn't even understand why KDE Partition was not working. Only later I noticed the authentication window's icon. SOFTWARE/OS VERSIONS Linux/KDE Plasma on Wayland: KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 Linux kernel 6.2.4 (from Ubuntu's archive) ADDITIONAL INFORMATION I could not always reproduce this successfully. Sometimes it opens with the authentication window on top as I prefer it and sometimes it doesn't. And I could not figure out why or how to always trigger the same behavior, either one of them. BTW, can you please check if this bug report is related to this one? https://bugs.kde.org/show_bug.cgi?id=434668 -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 467358] New: Removing a global theme doesn't remove its dependencies too
https://bugs.kde.org/show_bug.cgi?id=467358 Bug ID: 467358 Summary: Removing a global theme doesn't remove its dependencies too Classification: Plasma Product: plasma-integration Version: 5.27.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ilikef...@waterisgone.com Target Milestone: --- Created attachment 157281 --> https://bugs.kde.org/attachment.cgi?id=157281&action=edit Desktop and task bar icons in green and many plasma styles in System Settings SUMMARY Removing a global theme doesn't remove its dependencies too STEPS TO REPRODUCE 1. Install one or more global themes 2. Then remove the newly installed global themes. 3. In case the default global theme (Breeze or Breeze dark) is not chosen automatically choose it and apply it OBSERVED RESULT In my case after installing a few global themes to see which of them have some blur effects, nice window decorations and other cool things, I removed them all, but I remained with a strange green color for the folders on the desktop and for Dolphin's icon in the task bar. Looking at the Plasma styles page, there are a lot of styles there, which were not removed when the global themes they belong to were removed. A specific style called "GruvboxPlasma" is also automatically selected. Please see the attached printscreen Switching to another style, like "Breeze dark" seem to fix the green color problem. But if I click on the "Breeze dark" global them and apply it again the, the green color comes back again. If I go to the styles page, I see that "GruvboxPlasma" is also automatically selected again, even though it should not be for this default global theme. EXPECTED RESULT I expect that, if I test a global theme, see that I don't like it and remove it, all the installed dependencies like: - Plasma styles - Colors - Widow decorations - Icons - Cursors - Fonts (not sure if i my case these were installed too) - Splash screens (not sure if i my case these were installed too) - Login screens - Wallpapers Are uninstalled too. Or at lest ask me if I still want to keep them or not. I might want to keep some of them. As for choosing the default global themes, Breeze or Breeze dark and apply them, I expect that everything reverts to the default no have weird colors, styles and other things that are remnants from other themes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 kernel: 6.2.4 (from Ubuntu's archive) ADDITIONAL INFORMATION Tested on Debian 12 with the Wayland session. BTW, this bug might be similar or have the same cause: https://bugs.kde.org/show_bug.cgi?id=439653 Sorry that I didn't know where was the right place to open this bug report! -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 467358] Removing a global theme doesn't remove its dependencies too
https://bugs.kde.org/show_bug.cgi?id=467358 --- Comment #1 from John --- One more problem that I forgot to mention: Even though that the global themes have been removed, these dependencies left behind make Discover search and send notifications about updates for these dependencies ad shows them under the "Addons" section. So, while apt says that there are no more updates, Discover says that there are still updates to install, which are for these. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467471] New: PWA's Do Not Have Their Own Icon in Icons-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=467471 Bug ID: 467471 Summary: PWA's Do Not Have Their Own Icon in Icons-Only Task Manager Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: jpierce.co...@gmail.com Target Milestone: 1.0 Created attachment 157345 --> https://bugs.kde.org/attachment.cgi?id=157345&action=edit Showing PWA icons on desktop, youtube pwa grouped with brave icon SUMMARY *** Hello, I'm not having a crash, but I install and use PWA's on a regular day to day basis, so I figured I would bring this up. Whenever a PWA is installed, and launched (whether from desktop or application launcher), and with an existing browser window open, instead of having it's own respective icon in the task manager, the icon of the PWA flashes briefly on the task manager before getting grouped with the browser it was installed from, thus taking the icon of the browser itself, instead of using it's own icon, though I saw it's own icon flash briefly, so I know it's there. If the browser is not open when opening a PWA, the PWA icon will take show in place of the browser icon. *** STEPS TO REPRODUCE 1. Navigate to any website 2. Either click the "Install" button in URL window (if official PWA site), or 3. Click three dots in top right corner of browser window 4. Click "More Tools", then "Add Shortcut", then ensure "Open as New Window" is selected, and click "Create" 5. Open the newly installed PWA either from desktop icon or application launcher 6. Observe icon placement/behavior in task manager OBSERVED RESULT - PWA does not hold it's own place in the task manager; instead it is grouped as another browser window - PWA icon does not show in task manager if browser window is open prior to opening PWA - PWA icon replaces browser icon if browser window isn't open prior to opening the PWA EXPECTED RESULT - When launched, PWA icon appears at the end of the task manager as a new program registered - PWA has it's own icon in task manager, rather than appear as another browser window with browser icon SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Fedora 37 KDE Plasma on Wayland (have recreated in X11 in the past before I migrated completely to Wayland) (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Kernel Version: 6.1.18-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 x 11th Gen Intel Core i7-11370H @3.30GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel Xe Graphics Manufacturer: ASUSTeK Computer Inc. Product Name: ASUS TUF Dash F15 FX516PM_FX516PM System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467471] PWA's Do Not Have Their Own Icon in Icons-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=467471 --- Comment #1 from John --- Created attachment 157346 --> https://bugs.kde.org/attachment.cgi?id=157346&action=edit Showing the PWA icons on desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467471] PWA's Do Not Have Their Own Icon in Icons-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=467471 --- Comment #2 from John --- Created attachment 157347 --> https://bugs.kde.org/attachment.cgi?id=157347&action=edit Showing Youtube being grouped with Brave (Chromium browser) icon instead of having it's own icon -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467513] New: Spectacle Does Not Copy Image to Clipboard When Clicking 'Copy to Clipboard' After Screenshot Annotation
https://bugs.kde.org/show_bug.cgi?id=467513 Bug ID: 467513 Summary: Spectacle Does Not Copy Image to Clipboard When Clicking 'Copy to Clipboard' After Screenshot Annotation Classification: Applications Product: Spectacle Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: jpierce.co...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** Like the title states, when I take a Spectacle screenshot (via shortcut keys, have it set to copy on capture), and then click Annotation to edit the screenshot, whenever I click Annotation Done, and click Copy to Clipboard, Spectacle does not copy the image to Clipboard unless there is something existing already in the Clipboard history. If the Clipboard is empty (which I empty it every so often so it doesn't get cluttered up), and the existing copy of the screenshot (before I annotated) is in there, when I click to copy the annotated version of the screenshot, it clears the Clipboard, and doesn't copy the annotated screenshot to the Clipboard. I would think this would be a serious issue since it clears the clipboard without the clipboard being explicitly asked to be cleared. I can try to get a screen recording of this happening soon to help. *** STEPS TO REPRODUCE 1. Take rectangular region screenshot via Spectacle via shortcut keys (Super + Shift + S) 2. Select Annotate, and make edits (usually bordered empty box is what I add), click Annotation Done 3. Click Copy to Clipboard 4. Check Clipboard to see empty Clipboard, attempt to paste annotated image into application (tested on several applications, such as Element, Telegram, LibreWriter, OpenOffice) OBSERVED RESULT Annotated screenshot is not copied to clipboard when Copy to Clipboard button is clicked in Spectacle, instead clears the clipboard EXPECTED RESULT Annotated image is copied to clipboard, and able to successfully be pasted in supported applications. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Fedora 37 KDE Plasma on Wayland (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Kernel Version: 6.1.18-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-11370H @ 3.30GHz System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467513] Spectacle Does Not Copy Image to Clipboard When Clicking 'Copy to Clipboard' After Screenshot Annotation
https://bugs.kde.org/show_bug.cgi?id=467513 --- Comment #1 from John --- The file was too big to attach the screen recording, so I have uploaded it to my Google Drive, and am giving the link to the video here. https://drive.google.com/file/d/1pCJmysx1FFsEozxUeslDKQjPQHbSDPu7/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467572] New: Kate Markdown Module Fully Broken [Regresson]
https://bugs.kde.org/show_bug.cgi?id=467572 Bug ID: 467572 Summary: Kate Markdown Module Fully Broken [Regresson] Classification: Applications Product: kate Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: encoding Assignee: kwrite-bugs-n...@kde.org Reporter: kdelo...@mozej.com Target Milestone: --- SUMMARY If you try to preview your markdown text you see absolutely nothing, so you don't know if anything is OK. The markdown module is broken. STEPS TO REPRODUCE 1. ctrl+shift+, > Plugins ---> Document Preview > ON 2. Tools ---> Mode ---> Markup > Markdown ON 3. View ---> Tool Views ---> Show Preview 4. Empty preview with text "No preview available". Not possible to examine output. Fix regression (maybe other previews don't work either?) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (not Manjaro) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466248] Discover's Notifier Tray Icon does not show
https://bugs.kde.org/show_bug.cgi?id=466248 --- Comment #3 from John --- (In reply to Nate Graham from comment #2) > On a login when it's failed to appear in either the active area of the tray > (on the panel) or the popup, can you paste the output of running `systemctl > status --user app-org.kde.discover.notifier@autostart.service` in a terminal > window? Hi Nate This gets realy long... So, i'll post the last two chunks (because they look 'sort of' the same)... But... if you want the whole thing... i can post it :) ~ lines 1-15/15 (END)...skipping... ● app-org.kde.discover.notifier@autostart.service - Discover ● app-org.kde.discover.notifier@autostart.service - Discover ● app-org.kde.discover.notifier@autostart.service - Discover ● app-org.kde.discover.notifier@autostart.service - Discover Loaded: loaded (/etc/xdg/autostart/org.kde.discover.notifier.desktop; generated) ● app-org.kde.discover.notifier@autostart.service - Discover ● app-org.kde.discover.notifier@autostart.service - Discover ● app-org.kde.discover.notifier@autostart.service - Discover ● app-org.kde.discover.notifier@autostart.service - Discover ● app-org.kde.discover.notifier@autostart.service - Discover ● app-org.kde.discover.notifier@autostart.service - Discover Loaded: loaded (/etc/xdg/autostart/org.kde.discover.notifier.desktop; generated) Active: active (running) since Mon 2023-03-20 12:25:48 WET; 3min 26s ago Docs: man:systemd-xdg-autostart-generator(8) Process: 1365 ExecCondition=/lib/systemd/systemd-xdg-autostart-condition KDE (code=exited, status=0/SUCCESS) Main PID: 1382 (DiscoverNotifie) Tasks: 10 (limit: 9384) Memory: 42.2M CPU: 1.108s CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover.notifier@autostart.service └─1382 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier mar 20 12:25:48 escritorio systemd[1135]: Starting Discover... mar 20 12:25:48 escritorio systemd[1135]: Started Discover. mar 20 12:26:14 escritorio DiscoverNotifier[1382]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION a> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-15/15 (END)...skipping... ● app-org.kde.discover.notifier@autostart.service - Discover Loaded: loaded (/etc/xdg/autostart/org.kde.discover.notifier.desktop; generated) Active: active (running) since Mon 2023-03-20 12:25:48 WET; 3min 26s ago Docs: man:systemd-xdg-autostart-generator(8) Process: 1365 ExecCondition=/lib/systemd/systemd-xdg-autostart-condition KDE (code=exited, status=0/SUCCESS) Main PID: 1382 (DiscoverNotifie) Tasks: 10 (limit: 9384) Memory: 42.2M CPU: 1.108s CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover.notifier@autostart.service └─1382 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier mar 20 12:25:48 escritorio systemd[1135]: Starting Discover... mar 20 12:25:48 escritorio systemd[1135]: Started Discover. mar 20 12:26:14 escritorio DiscoverNotifier[1382]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466248] Discover's Notifier Tray Icon does not show
https://bugs.kde.org/show_bug.cgi?id=466248 John changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Mangonel] [Bug 467686] New: Application Launcher is Only Mouse. No Keybaord Navigation in Menu [Regression]
https://bugs.kde.org/show_bug.cgi?id=467686 Bug ID: 467686 Summary: Application Launcher is Only Mouse. No Keybaord Navigation in Menu [Regression] Classification: Plasma Product: Mangonel Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: mangonel Assignee: martin.sandsm...@kde.org Reporter: kdelo...@mozej.com Target Milestone: --- Created attachment 157514 --> https://bugs.kde.org/attachment.cgi?id=157514&action=edit Screenshot with text what is going on in "Application Launcher" SUMMARY: ---> A screenshot is attached (a picture is worth thousand words, just look at it).<--- Navigating to "Application Launcher" [described as "launcher to start application"] is only mouse compatible. Keyboard navigation fails. STEPS TO REPRODUCE 1. open "application launcher" 2. navigate with arrow keys/tab to "slepp, hibernate, restart, shutdown" and chose "shutdown" 3. Press Enter [to shutdown the system] OBSERVED RESULT Fail to execute Enter while "shutdown" is highlighted. Navigating with keyboard is a major thing on a desktop. So, I put it in "major" EXPECTED RESULT: Fully reinstate keyboard navigation in KDE, SOFTWARE/OS VERSIONS: Linux/KDE Plasma: 5.27.3 (available in About System) KDE Plasma Version: 5.104.0 KDE Frameworks Version: 5.15.8 Qt Version: X11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467572] Kate Markdown Module Fully Broken [Regresson]
https://bugs.kde.org/show_bug.cgi?id=467572 --- Comment #2 from John --- (In reply to Paul Worrall from comment #1) > Is the Markdown Viewer KPart installed? (pacman -Q markdownpart) Kate will not recognize (no preview) markdown .txt file, no matter what you set in Kate. One has to change the extension of the file from .txt to .markdown. Only then the options in Kate to treat the file as mardown will work. Otherwise kate will fail to regognize what file it is no matter what you tell it to do with the text file. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467572] Kate Markdown Module Fully Broken [Regresson]
https://bugs.kde.org/show_bug.cgi?id=467572 --- Comment #3 from John --- Kate will not recognize (no preview) markdown .txt file, no matter what you set in Kate. One has to change the extension of the file from .txt to .markdown. Only then the options in Kate to treat the file as mardown will work. Otherwise kate will fail to regognize what file it is no matter what you tell it to do with the text file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467687] New: Copy of pictures from one album to another doesn't keep its manual ordering
https://bugs.kde.org/show_bug.cgi?id=467687 Bug ID: 467687 Summary: Copy of pictures from one album to another doesn't keep its manual ordering Classification: Applications Product: digikam Version: 7.10.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: py.ha...@gmail.com Target Milestone: --- SUMMARY Copy of pictures from one album to another doesn't keep its manual ordering (but when moving the pictures, instead, it works) I use the value "By Manual and Name" for the menu entry "View"-->"Sort Items". STEPS TO REPRODUCE Copy pictures from one album to another (I doesn't matter how you copy them). OBSERVED RESULT The (manual) ordering set for the first album is not kept in the new album. I mean, pictures are not ordered the same way. The new pictures seems to be ordered by name only. EXPECTED RESULT The pictures should be ordered in the manual order as well. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION none -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467687] Copy of pictures from one album to another doesn't keep its manual ordering
https://bugs.kde.org/show_bug.cgi?id=467687 john changed: What|Removed |Added Platform|Other |Microsoft Windows OS|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467688] New: Missing clone album feature
https://bugs.kde.org/show_bug.cgi?id=467688 Bug ID: 467688 Summary: Missing clone album feature Classification: Applications Product: digikam Version: 7.10.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: py.ha...@gmail.com Target Milestone: --- SUMMARY I am missing a way to clone an album. The clone should keep all meaningful album settings. For example the manual sortering order. My concrete use case is the following. I have an album with all pictures and I want to create another album containing only a sub-selection with the best pictures. SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467687] Copy of pictures from one album to another doesn't keep its manual ordering
https://bugs.kde.org/show_bug.cgi?id=467687 --- Comment #2 from john --- Congratulations! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446924] Support distribution upgrades on Fedora
https://bugs.kde.org/show_bug.cgi?id=446924 --- Comment #8 from John --- Fedora update: https://pagure.io/fedora-kde/SIG/issue/3#comment-848145 (let's hope this gets backported to 5.27...) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466248] Discover's Notifier Tray Icon does not show
https://bugs.kde.org/show_bug.cgi?id=466248 --- Comment #6 from John --- Well, whatever the reason, in the last few days I've been starting Discover manually every day to check for updates, because it simply hasn't been starting. It shows up on the notifications, but not the icon on the taskbar. (maybe it went on a holiday break or something... lucky one... i know i surely needed one!) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458914] New: After installing Gwenview thru snap (not apt) I cannot view images outside ~
https://bugs.kde.org/show_bug.cgi?id=458914 Bug ID: 458914 Summary: After installing Gwenview thru snap (not apt) I cannot view images outside ~ Product: gwenview Version: 22.08.0 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: johnzon...@gmail.com Target Milestone: --- SUMMARY *** After installing Gwenview thru snap (not apt) I cannot view images outside ~. *** STEPS TO REPRODUCE 1a. double-click on an image outside /home/john OR 1b. in Gwenview, navigate to /media OBSERVED RESULT 1a. : Window popup Error - Gwenview with message "Could not enter folder /media/john/data/foto.". In the background in Gwenview: Loading '896796.jpg' failed (in a red rectangle with a red outline) 1b.: Window popup Error - Gwenview with message "Could not enter folder /media." In the background Gwenview is white, no message. EXPECTED RESULT The image is shown SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04 (with kernel 5.13.0.52) (available in About System) KDE Plasma Version: - KDE Frameworks Version: - Qt Version: - Gnome: 3.36.8 ADDITIONAL INFORMATION When using apt to install Gwenview, it worked like expected. But I can't do that anymore because of unmet dependencies. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 458914] After installing Gwenview thru snap (not apt) I cannot view images outside ~
https://bugs.kde.org/show_bug.cgi?id=458914 John changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from John --- (In reply to Nate Graham from comment #1) > This is a snap packaging issue. It limits the locations that an app has > access to. Thanks Nate! No snaps for me anymore. With the latest updates I could install it via apt again, so I've got it working. Love this program! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 402028] Setting shortcut keys to Ctrl+< or Ctrl+> breaks shortcuts for Ctrl+Z & Ctrl+X
https://bugs.kde.org/show_bug.cgi?id=402028 John changed: What|Removed |Added CC||johnmaveric...@mail.com --- Comment #22 from John --- I was about to go crazy about this one. I was searching all over the internet of a way to fix my CTRL+Z shortcut and i just couldn't... tried everything. I just stumble on this bug by chance and give it a try and it turns out it was my calculator shortcut - CTRL+< - that was causing the trouble. Please fix this! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374996] Global menu should not take up space when no menu are shown
https://bugs.kde.org/show_bug.cgi?id=374996 John changed: What|Removed |Added Blocks||435928 CC||johnmaveric...@mail.com --- Comment #4 from John --- I would pretty much like the opposite ( see https://bugs.kde.org/show_bug.cgi?id=435928 ). Because having it hiding and showing constantly has some awful side effects and a spacer does not fix it in any way! Can you make this optional? Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=435928 [Bug 435928] Switching between apps that do and don't support global menus triggers layout resize for other panel applets -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435928] Switching between apps that do and don't support global menus triggers layout resize for other panel applets
https://bugs.kde.org/show_bug.cgi?id=435928 John changed: What|Removed |Added Depends on||374996 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=374996 [Bug 374996] Global menu should not take up space when no menu are shown -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459800] New: Krita Crashes When Attempting to Create a New Image From Empty Clipboard
https://bugs.kde.org/show_bug.cgi?id=459800 Bug ID: 459800 Summary: Krita Crashes When Attempting to Create a New Image From Empty Clipboard Classification: Applications Product: krita Version: 5.1.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: crazyjer...@gmail.com Target Milestone: --- Krita crashes when attempting to create a new image from clipboard and there is no available image data in the clipboard. Situation could be accidental (ie. User unaware the Create from Clipboard option is active because of interface similarity. If Create from Clipboard is used in the previous session, the new image window starts with Create from Clipboard active) or somehow copying an image to the clipboard was not successful. STEPS TO REPRODUCE 1. No image in the clipboard (fresh OS session, etc) 2. Set desired image options (my case: 12.7inx9in, 300dpi, 1 layer with gray canvas color) 3. Click 'Create' button OBSERVED RESULT Krita crashes without any error messages. EXPECTED RESULT 'Create' button grayed out or some error message warning me of impossibility of creating an image without Clipboard data. SOFTWARE/OS VERSIONS Linux: Linux Mint Qt Version: 5.12.12 ADDITIONAL INFORMATION KRITA DID NOT CLOSE CORRECTLY SESSION: 28 Sep 2022 14:05:34 -0500. Executing /tmp/.mount_krita-TD2tRH/usr/bin/krita Krita Version: 5.1.1, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 259537 -- -- -- -- -- -- -- -- - qt5ct: using qt5ct plugin Replacing libstdc++.so.6 with the fallback version: libstdc++.so.6.0.28 -> libstdc++.so.6.0.29 WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! krita.general: ERROR: unable to decode abr format version 9 (subver 0 ) QObject::startTimer: Timers cannot have negative intervals WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! /tmp/.mount_krita-LUOYUK/usr/lib/krita-python-libs/krita added to PYTHONPATH WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by the 'amdDisableVectorWorkaround' option! ASSERT (krita): "!qimage.isNull()" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/kis_clipboard.cc, line 460 -- You are receiving this mail because:
[kwin] [Bug 468071] New: "Peek At Desktop" Conflicts with "Minimize All Windows" as well as Home Folder Concept in Unixes (KDE is not MS Windows, is it?)
https://bugs.kde.org/show_bug.cgi?id=468071 Bug ID: 468071 Summary: "Peek At Desktop" Conflicts with "Minimize All Windows" as well as Home Folder Concept in Unixes (KDE is not MS Windows, is it?) Classification: Plasma Product: kwin Version: master Platform: Archlinux OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: kdelo...@mozej.com Target Milestone: --- SUMMARY I put it into GRAVE in Sevirity. I dare anyone involved in KDE to try minimize all windows using both: shortcut and a button in system tray (bottom right corner next to clock). STEPS TO REPRODUCE 1. Change Icons-only Task Manager to Task Manager 2. Open Kate and Dolphin 3. Try setting/using/figuring out how to minimize ALL WINDOWS. Minimizing all windows is not possible. 4. Uniminimize ONLY ONE WINDOW DOES NOT WORK. Its not possible. Windows are not minimized but "only disappear". Clicking on one program to "show/unminimize" only this program puts ALL PROGRAMS BACK UP. OBSERVED RESULT 1. Remove Peek at desktop- Linux Distro/Unix don't use desktop to put files and folders, we have HOME FOLDER 2. Reinstate "Minimize all windows" so we can minimize all (keyboard shortcut and pannel/systray button) and then UNMINIZE ONLY ONE WINDOW. EXPECTED RESULT 1. Delete uselss "peek at destop". We do not have anything "on desktop" we have HOME FOLDER (KDE has even predefined folders fro Documents, Music, Photos, etc) that personally I have on different block device. This is not windows. No junk on "desktop" 2. Allow us to minimize all windows (both shortcut and panel/systray icon) and bring back only one window/app with one click. Sorry, but who the hell came with this %$# idea? Why KDE hates so much normal and sane behaviour of the desktop? Are you nuts?! SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (not Manjaro) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.15.8 Qt Version: 6.2.6 ADDITIONAL INFORMATION Are you nuts? Or is it some kind of sabotage or a joke? Who allows this decisions? Microsoft Employees? Is KDE now Microsoft dividision? -- You are receiving this mail because: You are watching all bug changes.
