[dolphin] [Bug 482993] New: Dolphin no longer handling group permissions correctly
https://bugs.kde.org/show_bug.cgi?id=482993 Bug ID: 482993 Summary: Dolphin no longer handling group permissions correctly Classification: Applications Product: dolphin Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: stuartksm...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY: Previously, folders not owned by the user were fully accessible via Dolphin if the user had group membership and permissions. This version of Dolphin appears to disregard group permissions when the user is not the owner. STEPS TO REPRODUCE 1. Create a folder not owned by your user but with any group your user belongs to. 2. Set permissions of the folder to drwxrwxr_x. 3. Open Dolphin and right-click on the folder to open the context menu OBSERVED RESULT Notice that these three menu options are grayed out: "Create New", "Duplicate Here", and "Compress". The same results are observed when entering the test folder and right-clicking on the empty space. NOTE: I can drag and drop items into the un-owned folder but the associated mouse cursor shows "not permitted" symbol (red circle with line through it). EXPECTED RESULT If the user has group access to a folder the menu options should all be available as they were in previous versions of Dolphin. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Wayland -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 Stuart K. Smith changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #5 from Stuart K. Smith --- Seeing the same thing here when kscreen is installed. AMD RX580 and KDEneon -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 458566] "Restart Game" opens "Save Game" dialog
https://bugs.kde.org/show_bug.cgi?id=458566 --- Comment #2 from Stuart K. Smith --- (In reply to Albert Astals Cid from comment #1) > I think it makes sense, imagine you're almost done and Press F5 by mistake, > having a dialog that lets you save, not save, cancel, makes sense to me As someone who plays the game almost daily, I find it highly annoying and unnecessary. It's rare to solve a game on the first go so restarting is a common thing to do for 3 or 4 rounds at least. An accidental F5 only means you have to start over with the same tiles - something one does anyway. An intentional F5 now means you have to stop what you are doing and close a dialog. If it was an intentional change, it is not a benefit and has a negative impact on game play. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 458566] New: "Restart Game" opens "Save Game" dialog
https://bugs.kde.org/show_bug.cgi?id=458566 Bug ID: 458566 Summary: "Restart Game" opens "Save Game" dialog Product: kmahjongg Version: 0.9.22080 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: stuartksm...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Since last update, F5 (Reload Game) results in a "Save Game?" dailog instead of just reloading the current game as in the past. STEPS TO REPRODUCE 1. Start a game and take one or more turns. 2. Press F5 to reload. OBSERVED RESULT Save Game dialog window opens. EXPECTED RESULT No dialog, just the game reloading. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434635] Partition Manager's Help files can not be parsed in Help Center
https://bugs.kde.org/show_bug.cgi?id=434635 --- Comment #8 from Stuart K. Smith --- Tested this on Debian Sid with Plasma 5.20.5/ Frameworks 5.78.0 and no error. Still seems to be an (K)Ubuntu problem -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434635] Partition Manager's Help files can not be parsed in Help Center
https://bugs.kde.org/show_bug.cgi?id=434635 --- Comment #6 from Stuart K. Smith --- Just checked on an updated Manjaro KDE running plasma 5.21.3 and OK there. Must be related to Ubuntu. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434635] Partition Manager's Help files can not be parsed in Help Center
https://bugs.kde.org/show_bug.cgi?id=434635 --- Comment #4 from Stuart K. Smith --- Same again on 20.10 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434635] Partition Manager's Help files can not be parsed in Help Center
https://bugs.kde.org/show_bug.cgi?id=434635 Stuart K. Smith changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #3 from Stuart K. Smith --- I am seeing the same results on Kubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #35 from Stuart K. Smith --- Still not resolved. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414906] Dolphin does not allow UNMOUNT of USB thumb drives, only "Safely Remove"
https://bugs.kde.org/show_bug.cgi?id=414906 --- Comment #3 from Stuart K. Smith --- One more possible issue: I have an older USB attached SD card reader. "Safely Remove" powers down the entire device rather than the subject SD card. In my case, the device is internally installed in a desktop machine and internally connected to a USB buss, so unplugging and plugging it back in is not an option. Either rebooting or some device power control magic if you're that familiar with the device is required. Granted, this case is a poorly designed hardware issue, but it is easily managed by a more friendly Dolphin context. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414906] Dolphin does not allow UNMOUNT of USB thumb drives, only "Safely Remove"
https://bugs.kde.org/show_bug.cgi?id=414906 --- Comment #2 from Stuart K. Smith --- Thank you for the quick reply. Yes: You want to reformat or install an ISO to a thumb drive. You plug it in, mount it, view it to be sure it's blank or doesn't contain any data you want to save, then unmount it and format it or whatever. Or you copy a file or two off of it, then hit the "Safely Remove", then realize you wanted one more file. Too bad, you have to pull it and start all over again. Clearly, one can do this from the command line, but using the GUI and a mouse has benefits. Also not all computers have easily reachable USB ports (some of us still have desktop machines). Conversely, why does a thumb drive need to be powered down at all? if it's unmounted, there's no benefit to making it inaccessible, is there? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414906] New: Dolphin does not allow UNMOUNT of USB thumb drives, only "Safely Remove"
https://bugs.kde.org/show_bug.cgi?id=414906 Bug ID: 414906 Summary: Dolphin does not allow UNMOUNT of USB thumb drives, only "Safely Remove" Product: dolphin Version: 19.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: stuartksm...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin Removable Devices context menu needs Unmount just like the Devices context menu. Safely remove powers down and logically ejects a thumb drive requiring one to physically remove and re-insert it before use again. STEPS TO REPRODUCE 1. Right-Click on removable USB device 2. 3. OBSERVED RESULT Context menu contains: - Open in New Window - Open in New Tab - Properties - Safely Remove - - Hide - Hide Section 'Removable Devices' EXPECTED RESULT - Open in New Window - Open in New Tab - Properties - Unmount - Safely Remove - - Hide - Hide Section 'Removable Devices' SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDEneon 5.17 (available in About System) KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Kernel 5.0.0-36-generic -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #11 from Stuart K. Smith --- BTW, agreed on the security issue. I had narrowed it to just the specific PC and it's in a rather controlled environment. I had widened it (ALL ALL etc.) when trying to trouble shoot this issue. My laptop does not have this setup. I haven't ventured into polkit much, but worth a look. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #10 from Stuart K. Smith --- Thank for the detailed info. Always good to be armed with the facts in my world. Funny you should make that recommendation about pkcon as I starting looking into it right after my last post here. My apt use was due to the burgeoning problems with early Discover in conjunction with Muon being without a dev. I just put apt into some aliases and made the suoders entry and went full CLI for updates and installations. That was about 5 years ago I think? pkcon looks good in the CLI and I'm looking at the GUIs also. Thanks again. Beverages on me if we ever meet in the real world :) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #8 from Stuart K. Smith --- So neon-settings redirected bin/apt to sbin/apt ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #7 from Stuart K. Smith --- Seems like an odd way to implement a change like that; /usr/sbin/apt calls /usr/sbin/apt-overly which calls /usr/bin/apt. No wonder sudoers got confused! At least this explains why my sudo apt overrides worked in the 16.04 version. Thanks for running it down, I would have never found this. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #4 from Stuart K. Smith --- Results here are unchanged. Removing neon-settings allows sudoers.d/apt to work but it does not when neon-settings are installed. The issue appears to be specific to apt and apt-get. Echoing Harald commands do indeed work for 'ls' but '/usr/bin/apt' in sudoers.d does NOT work when neon-settings is installed, but does when neon-settings is not installed. Same goes for '/usr/bin/apt'. '/usr/bin/add-apt-repository' works with or without neon-settings installed so it is not related to the '/usr/bin/' folder but appears to be specific to apt and apt-get. All of the above 'apt' related commands and others are in a single file together on a single line and all but apt and apt-get work without a sudo password. I confirmed this on a VM as well as on my bare metal install. To recap: While neon-settings is installed: /bin/ls in /etc/sudoers.d/foo does allow 'sudo ls' to work without a password. Others, like 'sudo pwrstat' and 'sudo btrfs' that are on my system also work. Identically formatted '/etc/sudoers.d/apt' containing '/usr/bin/apt' and '/usr/bin/apt-get' among other commands all work EXCEPT apt and apt-get. Uninstalling neon-settings allows 'sudo apt' and 'sudo apt-get' to work without a password with no other modifications. Could someone specifically test this against /usr/bin/apt and/or /usr/bin/apt-get to confirm? Test procedure requested please: With neon-settings installed, use Harald's series of commands above and substitute '/usr/bin/apt' for '/bin/ls'. Then enter 'sudo -k' and 'sudo apt update'. Assuming the result is a password is requested, do CTRL+C to cancel and then uninstall neon-settings and re-test. Be sure to do 'sudo -k' between commands if package uninstall is done in the same terminal to force a reset of the environment. Please report results here. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #1 from Stuart K. Smith --- I installed all the dependencies for neon-settings and sudoers.d/ files worked normally. Installing the specific neon-settings package breaks the functionality. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] New: neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 Bug ID: 407729 Summary: neon-settings package causes files in /sudoers.d to not be honored Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: stuartksm...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Using a new install of KDEneon I noticed any entries in /etc/sudoers.d/ did not have the desired effect of allowing sudo actions without a password. Replacing the "neon-settings" package with "kubuntu-settings-desktop" results in the files in /etc/sudoers.d to begin working again. STEPS TO REPRODUCE 1. Fresh install of KDEneon. 2. Add file in /etc/sudoers.d/ using "sudo visudo -f ..." 3. Test action and see that sudo password is still required. OBSERVED RESULT Install "kubuntu-settings-desktop" which forces removal of "neon-settings". Test action and see that sudo password is no longer required. EXPECTED RESULT Files in sudoers.d should be parsed by KDEneon as they are when using Kubuntu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDEneon User Edition - latest (5.15.5) (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION I'm not sure yet if it's actually neon-settings or one of is depends or a missing depends. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #32 from Stuart K. Smith --- Mihai Sorin Dobrescu: I totally got what you meant and my comment wasn't pointed at you. Rather, I was try to illustrate a broader point that different devices needs different actions and the terms are important because of that. Using "Safely Eject" obfuscates the actual needed action and is part of the problem in my view. Christoph Feck: Precisely and exactly to the issue. There are many uses for the Notifier when controlling USB storage devices and there is no "one size fits all" solution. Fully ejecting a non-spinning device in unwarranted and in many cases very inconvenient. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #29 from Stuart K. Smith --- That doesn't seem to work here, at least not with a USB stick: sudo hdparm -y /dev/sdi [sudo] password for stuart: /dev/sdi: issuing standby command SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 14 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The drive is still mounted after this and unmounting first has the same results. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #27 from Stuart K. Smith --- Thinking it over, what I would like to see is; If the USB storage device is a CD/DVD/BR, "Eject" is the default action. If the device is a USB attached file system but not a CD/DVD/BR, then set "Unmount all file systems on this device" as default action, and offer "Unmount only this file system" as an action in the list for the device. Then if you want to unmount and grab your thumb drive or USB hard drive, the default is perfect. If you are continuing to work with a multi-file system USB device, then you can select and specify which file system to unmount (or mount). In both cases, the device remains accessible because it has not been powered off by Eject. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #26 from Stuart K. Smith --- Agreed, however in the case of USB thumb drive, unmounting forces commit or it won't unmount until cache is clear. It least that's my belief. IME I can't unmount any file system until it's not being used. Part of the issue might be the understanding of eject vs. unmount. A file system is unmounted, but not ever "ejected". A device may be ejected, but only cleanly if it has been unmounted prior. A device, like a USB thumb drive or USB hard drive is never really in need of "Eject" because once the file system(s) on it are unmounted you can just pull it out. This is where this whole mess started. Someone had multiple file systems on a USB device and failed to unmount one or more of them before pulling the plug. This could cause a file corruption if a write were not complete. This potential outweighed (at least in some persons minds) the inconvenience to the thousands of users just a thumb drive. In my mind, the best possible solution for USB r/w storage devices is an "unmount all" condition where all file systems on the device are unmounted. "Eject" does this conveniently enough but then you end up where we are - pulling a re-inserting the device. Seems like an expansion of the Notifier actions in this regard is in order. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #24 from Stuart K. Smith --- There seems to be a lot of rambling on this bug report about loosely related topics. My issue is that a USB device should not have to be unplugged and re-inserted by design. That is a very poor working practice. You should be able to choose or default to Unmount rather than Eject (aka "Safely Remove") devices that do not require ejection. Is there no way for the programming of the Device Notifier to detect if a plugged in device is a spinning hard drive vs. a USB thumb drive? BTW, my WD USB spinning hard drive does not need to be "parked" to be removed. This effectively make Notifier mostly useless for USB thumb drives. If I have to go to the command line so I don't have to reach behind my monitor or PC case to unplug and reinsert my USB drive, then why have the GUI Notifier? At a minimum, "Unmount" should be in the options available and at best be the default choice when clicking the up arrow in Notifier. I'd bet that there are oodles more thumb drives being used than portable hard drives. Let the lesser sized user group have the extra "Fully Eject" option available in the action list but make Unmount the option. Seems way more logical to me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406362] New: Device Notifier treats USB thumb drives like CDs - "Safely remove" ejects instead of unmounting
https://bugs.kde.org/show_bug.cgi?id=406362 Bug ID: 406362 Summary: Device Notifier treats USB thumb drives like CDs - "Safely remove" ejects instead of unmounting Product: plasmashell Version: 5.12.8 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: stuartksm...@gmail.com Target Milestone: 1.0 SUMMARY The Device Notifier "Ejects" USB thumb drives rendering them unusable until they are pulled from the port and re-inserted. This is both unnecessary and poor work-flow. There is no justification for ejecting a USB thumb drive. A much better action would be for "Unmount" to be the default action instead of "Eject". This would allow multiple actions to be taken on a thumb drive without continuously removing and re-inserting it, such as reformatting or burning and ISO to it. This is especially important if the USB port is difficult to physically access, such as the back-side of a monitor or PC. STEPS TO REPRODUCE 1. Insert thumb drive and observe Device Notifier pop-up indication that a drive has been inserted. 2. Select "Open with File Manager" from access options in Device Notifier. 3. Select the up-arrow button "Click to Safely Remove this device." using Device Notifier. OBSERVED RESULT The USB device is no longer listed in attached devices via "lsusb" although it is still physically present and cannot be accessed until it is removed and re-inserted. EXPECTED RESULT File system should be unmounted but the physical device should still addressable. "Safely Remove" when referring to a USB drive should only unmount the device, not eject it from the bus. Ejecting is only preferred if the physical device requires that for access such as with a CDROM/DVD. Unmounting a USB drive prior to its physical removal is sufficient for file system safety. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDEneon LTS 5.12 (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 388593] Krunner spellcheck plugin does not work (Could not find a dictionary)
https://bugs.kde.org/show_bug.cgi?id=388593 Stuart K. Smith <stuartksm...@gmail.com> changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #2 from Stuart K. Smith <stuartksm...@gmail.com> --- Same here: kf5.karchive: bzDecompress returned -5 The dictionary data engine timed out (word: "app" ) The dictionary data engine timed out (word: "appl" ) The dictionary data engine timed out (word: "apple" ) The dictionary data engine timed out (word: "apple" ) Neon user addition, Plasma 5.12 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379721] neon only dependency bug: phonon4qt5-backend-vlc and -gstreamer.
https://bugs.kde.org/show_bug.cgi?id=379721 --- Comment #4 from Stuart K. Smith <stuartksm...@gmail.com> --- (In reply to Jonathan Riddell from comment #3) > Much KDE software depends on Phonon which needs one of its backends > installed to function. If you remove that it's entirely reasonable that apt > wants to remove the software that needs it. I completely understand and agree, but I don't see this as the central issue. The problem as I see it is the lack of a fail-back to the gstreamer backend in the event the user wants to remove VLC. As it stands, removing VLC is impossible unless the user knows to install the gstreamer backend prior to attempting the removal. This requirement is not obvious to the uninitiated and is not apparent by the error messages created by the attempt. IMO, this situation could be easily resolved in one of these ways: 1) The removal of phonon4qt5-backend-vlc triggers the installation of phonon4qt5-backend-gstreamer - and vice-versa, thus preventing the unintentional breakage of the entire system. 2) Both backends installed by default, thus allowing VLC to be removed without incident. 3) VLC not be installed by default at all, instead having gtreamer be the default backend. Again, IMO #1 would be the most beneficial as it provides protection from "silly user tricks." Interesting points to note: **Removing the gstreamer backend (whilst the VLC backend is not present) automatically installs the VLC backend. It's only when you attempt the reverse as stated above that the removal of KDE is at risk. **Even VLC does not have the VLC backend as a dependency. Removing the VLC backend on it's own does not force the removal of VLC. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379721] New: neon only dependency bug: phonon4qt5-backend-vlc and -gstreamer.
https://bugs.kde.org/show_bug.cgi?id=379721 Bug ID: 379721 Summary: neon only dependency bug: phonon4qt5-backend-vlc and -gstreamer. Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: stuartksm...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Attempting to remove vlc from KDEneon results in removal of entire plasma desktop. I found the problematic package is "phonon4qt5-backend-vlc" which takes everything else with it. If, prior to removing vlc, you first install "phonon4qt5-backend-gtreamer" then you can remove vlc and it's depends successfully. This requirement to have either phonon4qt5-backend-vlc or -gstreamer is not present in Kubuntu 16.04. Either the dependencies are incorrect or at a minimum, the gstreamer package should be installed as fall-back if one wants to remove vlc. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://
https://bugs.kde.org/show_bug.cgi?id=366795 Stuart K. Smith <stuartksm...@gmail.com> changed: What|Removed |Added CC||stuartksm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362241] Rectangular Region option does not preview and does not save an image after 15.12.3-2 -> 16.04.0-1
https://bugs.kde.org/show_bug.cgi?id=362241 --- Comment #15 from Stuart K. Smith <stuartksm...@gmail.com> --- Yeah using nvidia driver here, thanks for the reply Boudhayan. I've had numerous issues with nvidia drivers higher than 340 with the newer 4.4 kernels. I don't have time to validate this right now, but I'll try reverting back to 340 and see if the issue continues. IMO, the latest nvidia drivers are crappy/buggy -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362241] Rectangular Region option does not preview and does not save an image after 15.12.3-2 -> 16.04.0-1
https://bugs.kde.org/show_bug.cgi?id=362241 Stuart K. Smith <stuartksm...@gmail.com> changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #9 from Stuart K. Smith <stuartksm...@gmail.com> --- Rectanglar Region capture does not work below about 400x300 ish Version 16.04.3 on KDEneon Why is this marked "Resolved?" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342716] translucency effect causes zombie when closing a window (likely due to multiple and uncancelled "set" calls)
https://bugs.kde.org/show_bug.cgi?id=342716 Stuart K. Smith <stuartksm...@gmail.com> changed: What|Removed |Added CC||stuartksm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
