[kwin] [Bug 443723] "Display geometry when moving or resizing" feature is missing
https://bugs.kde.org/show_bug.cgi?id=443723 --- Comment #17 from Michael Tunnell --- Thank you very much for putting in the time to work on this Richard, having this back is much appreciated for my media production workflow! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454230] Cursor Launch Feedback - Add Spinner/Busy Cursor option
https://bugs.kde.org/show_bug.cgi?id=454230 --- Comment #2 from Michael Tunnell --- Yes! Please add this option and also please make it the default. In my opinion, this is more polished approach and feels more modern than the bouncing icon. Plus there is a great icon in the Breeze Icons set that can be for this and I made a video demonstrating it for those who are not aware of it. Here is the demo of the icon I'd like to see be used or maybe a variation of this. https://www.youtube.com/watch?v=uYSNixVdYDE -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443723] "Display geometry when moving or resizing" does not work under wayland
https://bugs.kde.org/show_bug.cgi?id=443723 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #12 from Michael Tunnell --- I am disappointed to see this removed intentionally. I used this feature all the time to resize windows for different usecases. I'll provide one of the critical examples I use it for. I'm a podcaster on Destination Linux and during preparation we have individual windows for each camera. I resize the windows to 1080p so that I can capture them via OBS. This feature made it very easy and simple to make sure I always had it at the right sizing and positioning for capture. The first episode we recorded after I updated to 5.24 actually sent me into a panic because I didnt have time to figure out what happened. Luckily I already knew how to workaround this with wmctrl so I did that and have been doing so ever since. I decided to see if there was a bug report to add my need to today and see that it was intentionally removed without warning. I don't know how I would be able to be warned as I am not sure there is a change advisory thing but that would be very helpful as a side note. I now see that wmctrl does not work on Wayland so this feature being removed in KWin and my workaround only works in X means this will eventually create a bigger problem for me later. Note: this is not the only reason I use this feature, this was also great for a lot of other reasons and was a great way to show people why KWin was awesome because everyone has different reasons to find this helpful. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 437205] New: Suggestion to Change AppStream Data for KDE Connect Website
https://bugs.kde.org/show_bug.cgi?id=437205 Bug ID: 437205 Summary: Suggestion to Change AppStream Data for KDE Connect Website Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: m...@michaeltunnell.com Target Milestone: --- SUMMARY I suggest changing the URL for "visit app website" link in AppStream to https://kdeconnect.kde.org/ as it would make easier for people to get to know what KDE Connect can do when loading in various "app stores". It is currently set to the wiki/docs page of https://community.kde.org/KDEConnect STEPS TO REPRODUCE 1. open this link into Discover: appstream://org.kde.kdeconnect.kcm.desktop - or just search for it in Discover 2. Find the visit app website link to see the current setting -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437147] Meta+V Shortcut Not Existent in Plasma 5.21.90
https://bugs.kde.org/show_bug.cgi?id=437147 --- Comment #7 from Michael Tunnell --- Okay, upon further (sorry for the amount of comments), it seems that the Apply function not engaging in Plasma 5.21 on Fedora 34 is because the changes are being instantly applied as I made a change and close the window without clicking OK or Cancel, the change was still applied. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437147] Meta+V Shortcut Not Existent in Plasma 5.21.90
https://bugs.kde.org/show_bug.cgi?id=437147 --- Comment #6 from Michael Tunnell --- I have used this Klipper popup on my system for years but I do not have any particular preference for the shortcut combo I use so I decided to adopt Meta+V in my current install for Plasma 5.21 on Fedora 34. Due to this change, I noticed that the "Apply" not engaging issue is also existent in Plasma 5.21 as I had to click OK to make the change for Meta+V in my production machine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437147] Meta+V Shortcut Not Existent in Plasma 5.21.90
https://bugs.kde.org/show_bug.cgi?id=437147 --- Comment #4 from Michael Tunnell --- @Nate whenever I make changes in Klipper's shortcut configuration the "Apply" button doesn't engage. This is the case for choosing Default for Meta+V radio or just any other changes I made during my testing on any of the shortcuts. However, if you make the change to Default and the just click OK to apply & close, this does work making Meta+V activate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437147] Meta+V Shortcut Not Existent in Plasma 5.21.90
https://bugs.kde.org/show_bug.cgi?id=437147 --- Comment #2 from Michael Tunnell --- Created attachment 138457 --> https://bugs.kde.org/attachment.cgi?id=138457&action=edit Meta+V is set but not active After further testing, I can confirm that I have the same experience as Rik. The Meta+V is set for Default but for some reason Custom is taking precedence over the default even though Custom is empty. I have provided a screenshot of my experience as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437147] New: Meta+V Shortcut Not Existent in Plasma 5.21.90
https://bugs.kde.org/show_bug.cgi?id=437147 Bug ID: 437147 Summary: Meta+V Shortcut Not Existent in Plasma 5.21.90 Product: plasmashell Version: 5.21.90 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: m...@michaeltunnell.com Target Milestone: 1.0 Created attachment 138452 --> https://bugs.kde.org/attachment.cgi?id=138452&action=edit image displaying Shortcuts for Klipper in 5.21.90 SUMMARY Klipper should be opening with the shortcut of Meta+V (based on Beta blog post) but it's not working. I looked at the configuration options of Klipper and it seems as though no shortcut is set to load Klipper at mouse position which is what I assume is the intended action. STEPS TO REPRODUCE 1. Update Kubuntu 21.04 to use 5.21.90 via Backports PPA 2. Attempt to use Meta+V OBSERVED RESULT No action occurs EXPECTED RESULT I dont know what is meant to happen but I assume Klipper should load at mouse position. SOFTWARE/OS VERSIONS OS: Kubuntu 21.04 Linux: 5.11.0-17 KDE Plasma Version: Plasma 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 430620] Discover shows apps/packages as recommended that I have already installed
https://bugs.kde.org/show_bug.cgi?id=430620 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #4 from Michael Tunnell --- I agree that it can be off-putting a bit to show apps already installed as a suggestion but a Featured section isn't really a recommendation setup. I think Discover should introduce a recommendation option based on what people have installed but a Featured section that is meant for everyone is a good thing to have as well. I think the problem is that Discover is designed in a way that multiple sections are not accessible at the same time like other app stores are built. I think the best tactic here would be to redesign the landing page of Discover so that more sections can be included such as a Featured, Recommended, Top Rated, etc. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343281] Font Selection Error, Creates Whitespace [San Serif instead of Monospace]
https://bugs.kde.org/show_bug.cgi?id=343281 Michael Tunnell changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Michael Tunnell --- Oh I forgot I even submitted this bug report. :D Apparently, the issue has been gone for a very long time, so all good. :) I marked it as resolved. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update
https://bugs.kde.org/show_bug.cgi?id=407058 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #32 from Michael Tunnell --- the auto-resize seems to work when switching to Fullscreen via Host+F (default = Right Ctrl + F) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421851] New: Request: Grid Layout for Run Command Items (Stream Deck-like interface)
https://bugs.kde.org/show_bug.cgi?id=421851 Bug ID: 421851 Summary: Request: Grid Layout for Run Command Items (Stream Deck-like interface) Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: m...@michaeltunnell.com Target Milestone: --- Request: modify the Run Command plugin, or make another one based on it, to display items in a grid rather than in the current list form. The reason is KDE Connect can already run scripts or commands and thats awesome but I often have to scroll through my list to select something. If I could have it in a grid format then I could see more items at once. The current max on my phone is 9 items but with a grid it could be many more. I'd also like for this grid to have multiple pages in a profile form where depending on what I am doing I could have different items in the grid. Finally, I'd like the ability to modify the color of the grid items so they are quickly identifiable at a glance. It would even be cooler if images could be used for say example icons. Essentially, this would allow KDE Connect to turn a phone or a tablet into an alternative to the El Gato Stream Deck. You can already kind of do it now with the command list but if these were done it would pretty much eliminate the need for a stream deck. :D -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409388] Backup and Restore KDE Connect Remote Commands
https://bugs.kde.org/show_bug.cgi?id=409388 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414427] Opacity Shortcuts Suggestion for KWin
https://bugs.kde.org/show_bug.cgi?id=414427 --- Comment #2 from Michael Tunnell --- The need is discoverability and better user experience. Saving it for what "could be" seems very wasteful to me. The vast majority of people have no idea that his feature even exists because the discoverability is 100% exclusive to digging into the shortcuts in System Settings. The window context menu (Alt+F3) does not offer this as an option to use unlike other KWin actions so without it being preset and people telling others to check it out the only way to know it exists or even see a demo of it as a user is to manually go into System Settings -> Shortcuts -> Global Shortcuts -> KWin -> dig through all of these to eventually find the Opacity actions -> Manually set both them. Yes, it is somewhat self-evident for what they are intended to do *but* not everyone knows what opacity means and the manual involvement required is just unnecessary barrier to entry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414427] New: Opacity Shortcuts Suggestion for KWin
https://bugs.kde.org/show_bug.cgi?id=414427 Bug ID: 414427 Summary: Opacity Shortcuts Suggestion for KWin Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@michaeltunnell.com Target Milestone: --- By default, KWin does not have shortcuts for the Increase/Decrease Opacity of windows but it does come in handy often for some people, such as myself so I suggest they be set to the following. Increase Opacity=Meta+Alt+= Decrease Opacity=Meta+Alt+- This is similar to how the Zoom function works with Plasma but adds the extra Alt modifier. This is the setting I use for my workflow and I use it often when podcasting so others might find it useful and it doesn't negatively affect anything as those shortcuts I'm suggesting are not utilized for anything at the moment. I was told to create a bug report for this instead of a Phabricator task so this is that bug report. (reference: https://phabricator.kde.org/T10568) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414142] New: [Request] Please add a GUI option to remove all blank spaces in a track
https://bugs.kde.org/show_bug.cgi?id=414142
Bug ID: 414142
Summary: [Request] Please add a GUI option to remove all blank
spaces in a track
Product: kdenlive
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: m...@michaeltunnell.com
Target Milestone: ---
You can currently remove spaces in a track or you can remove the same space in
the all tracks but it would be a fantastic feature to be able to remove all
spaces of a single track all at once.
I would prefer it to have an option to remove all the spaces in a single track
and then another option that removed all the spaces in every track though I
would need to keep the clips proportional.
Sometimes when I do the remove from all tracks it cuts clips that overlap and
that sort of thing so maybe removing all spaces in all tracks wouldnt work out
that well but if it was possible to remove the spaces and keep the tracks in
the right size and right location, that would be incredible. :D
---
I asked this in the telegram group and Vincent gave me a way to do it in the
XML and I tried it yesterday. It worked perfectly and easily saved me 20
minutes of pointless space removal :D
Here is the method Vincent provided that I used quite happily:
until we implement that, you can open your project in an editor, search &
delete all lines containing
in all file for all tracks, or select the right playlist if you want to apply
only on a single track
in shell:
sed '/ outfile.kdenlive
to limit to a given range:
sed '//,/<\/playlist>/{/
[lattedock] [Bug 411775] New: Added Files to a Dock and Now Can't Remove Entries
https://bugs.kde.org/show_bug.cgi?id=411775 Bug ID: 411775 Summary: Added Files to a Dock and Now Can't Remove Entries Product: lattedock Version: 0.9.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: m...@michaeltunnell.com Target Milestone: --- Created attachment 122573 --> https://bugs.kde.org/attachment.cgi?id=122573&action=edit screenshot of what it looks like and no option to remove So I accidentally added some files to a Dock and now I can't remove them from the dock. I have provided screenshots to demonstrate what I mean and I have not deleted the dock in case there is some of tested desired. Why did I do this? Well I was actually trying to drag and drop the files on another app and somehow I missed and landed in the dock. I am not sure exactly. STEPS TO REPRODUCE 1. Set Dock to Dodge Active 2. Drag files, in my case markdown .md files, from Dolphin to the Dock Files will be added and not removable and since it isnt an applet there is no option to remove it in the context menu. I suppose the thing I would expect is a way to remove it from the dock. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma 5.16.5 KDE Frameworks 5.61.0 Qt 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #100 from Michael Tunnell --- Yes! I have been waiting for this to happen for over 4 years so I am so excited to see it's finally happening! Thank you! When we eventually meet in person, fair warning . . . hug is coming -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407433] New: Visible Area of the Timeline Out of Sync with Keyboard Navigation
https://bugs.kde.org/show_bug.cgi?id=407433 Bug ID: 407433 Summary: Visible Area of the Timeline Out of Sync with Keyboard Navigation Product: kdenlive Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m...@michaeltunnell.com Target Milestone: --- SUMMARY The Timeline of 19.04+ is no longer connected to the keyboard navigation shortcuts. I created a video to demonstrate the issue that I am experiencing: https://youtu.be/rblA9vh-0Lw STEPS TO REPRODUCE 1. Have a large enough Timeline to have something extending either side of the visible area. 2. Use Keyboard navigation like Alt+Left or Alt+Right to navigate through the timeline. OBSERVED RESULT Timeline is in a fixed position and does not follow the playhead when using keyboard navigation. EXPECTED RESULT The visible area of the timeline should follow the playhead, the playhead should always be visible in the timeline. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.10 KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394341] Request: Swap Values for Clip Jumping via Mouse Wheel
https://bugs.kde.org/show_bug.cgi?id=394341 --- Comment #2 from Michael Tunnell --- Great! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394341] New: Request: Swap Values for Clip Jumping via Mouse Wheel
https://bugs.kde.org/show_bug.cgi?id=394341 Bug ID: 394341 Summary: Request: Swap Values for Clip Jumping via Mouse Wheel Product: kdenlive Version: 18.04.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m...@michaeltunnell.com Target Milestone: --- I think the method of scrolling through the timeline should be modified to feel more natural. Zooming and Normal scrolling feels fine but when using the mousewheel to jump to the ends of clips, it's cumbersome and confusing even when doing it for a very long time. I am referring to the function of Alt+Mousewheel (up and down) which works in the opposite configuration of normal timeline scrolling. When moving through the timeline with the mousewheel (no modifier), mousewheel up makes the timeline move to the left and mousewheel down moves to the right. This feels natural. However, when using Alt+Mousewheel to jump to the start and end of clips, the directions are flipped so when you Alt+Mousewheel Up it moves to the right. I have been using Kdenlive for a very long time and I have never been able to get used to this because it breaks the natural flow of what is expected, even when knowing what will happen. My suggestion is to swap the Alt+Mousewheel to use the directions that normal mousewheel uses. - TL:DR Mousewheel Up = moves timeline to the left Mousewheel Down = moves timeline to the right Alt+Mousewheel Up = moves playhead to the right direction Alt+Mousewheel Down = moves playhead to the left direction Please switch the Alt+Mousehweel actions to work in conjunction with the directions that the normal mousewheel action uses. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390527] New: Add Ctrl+H as Alternative Shortcut for Alt+. to Toggle Show Hidden Files
https://bugs.kde.org/show_bug.cgi?id=390527 Bug ID: 390527 Summary: Add Ctrl+H as Alternative Shortcut for Alt+. to Toggle Show Hidden Files Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: m...@michaeltunnell.com CC: elvis.angelac...@kde.org Target Milestone: --- I am not suggesting a replacement but rather adding an alternative option so both Alt+. and Ctrl+H work. This mostly applies to Dolphin but I also suggest it for any dialog popups as well. Ctrl+H is the most common shortcut used in Linux distros so this would make it available for those people switching to Plasma that expect it to be there. File Managers that have Ctrl+H by default: Nautilus, Caja, Nemo, Thunar, PCManFM, Pantheon Files, & Solus Files. There currently is an alternative of "F8" but this is so uncommonly used I forgot this was a thing. So I suggest replacing F8 with Ctrl+H as the alternative. Side Note: I much prefer Alt+. so this is suggestion is to improve on-boarding to Plasma, not related to my preference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390086] Option to move widgets via simple drag-and-drop anywhere on the widget
https://bugs.kde.org/show_bug.cgi?id=390086 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 389374] AppImage Launch Errors for v2.10.5
https://bugs.kde.org/show_bug.cgi?id=389374 --- Comment #5 from Michael Tunnell --- skrooge-2.10.10-x86_64.AppImage successfully launched and is usable. :) -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 389374] AppImage Launch Errors for v2.10.5
https://bugs.kde.org/show_bug.cgi?id=389374 --- Comment #3 from Michael Tunnell --- I just looked at the discourse feed and saw you did contact probono . . . nevermind. :) . . . anyway, I'd be happy to test any future appimage builds for this app. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388612] Ark cannot open AppImage v2 (squashfs)
https://bugs.kde.org/show_bug.cgi?id=388612 --- Comment #5 from Michael Tunnell --- I did set it as executable which created those issue but in order to look into the AppImage I did noticed the Ark issue. This is unrelated, sorry, I made a bug report for Skrooge at #389374 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 389374] AppImage Launch Errors for v2.10.5
https://bugs.kde.org/show_bug.cgi?id=389374 --- Comment #2 from Michael Tunnell --- I did download it from the source url you mentioned. I will be happy to test the new appimage that you are generating so please comment back when you have the new one ready. With that said, have you talked with *probono* (AppImage Dev) about this? He is very attentive and helpful with questions for developing AppImages. -> https://discourse.appimage.org/ -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 389374] New: AppImage Launch Errors for v2.10.5
https://bugs.kde.org/show_bug.cgi?id=389374 Bug ID: 389374 Summary: AppImage Launch Errors for v2.10.5 Product: skrooge Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: m...@michaeltunnell.com CC: steph...@mankowski.fr Target Milestone: --- I tried out the AppImage for Skrooge in KDE Neon. (love the name Skrooge by the way) I couldn't get it to launch, here are the errors I received: >skrooge: /lib/x86_64-linux-gnu/libz.so.1: version `ZLIB_1.2.9' not found >(required by /tmp/.mount_skroogfXowNq/usr/lib/x86_64-linux-gnu/libpng16.so.16) >skrooge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found >(required by /tmp/.mount_skroogfXowNq/lib/x86_64-linux-gnu/libudev.so.1) >skrooge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found >(required by /tmp/.mount_skroogfXowNq/lib/x86_64-linux-gnu/libsystemd.so.0) I am not sure if this relates to #388612 or not but I commented on that bug to see if someone can clarify whether it is or not. cite: https://bugs.kde.org/show_bug.cgi?id=388612 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388612] Ark cannot open AppImage v2 (squashfs)
https://bugs.kde.org/show_bug.cgi?id=388612 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #3 from Michael Tunnell --- I tried to launch this appimage and it failed for me as well but I am not sure the exact cause. Please clarify if this is the same problem based on the following error messages. >skrooge: /lib/x86_64-linux-gnu/libz.so.1: version `ZLIB_1.2.9' not found >(required by /tmp/.mount_skroogfXowNq/usr/lib/x86_64-linux-gnu/libpng16.so.16) >skrooge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found >(required by /tmp/.mount_skroogfXowNq/lib/x86_64-linux-gnu/libudev.so.1) >skrooge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found >(required by /tmp/.mount_skroogfXowNq/lib/x86_64-linux-gnu/libsystemd.so.0) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388301] Discover Crashes when trying to upgrade a package
https://bugs.kde.org/show_bug.cgi?id=388301 --- Comment #4 from Michael Tunnell --- my Neon install says "E: Unable to locate package plasma-discover-private-dbg" Discover hadn't crashed since my last comment but it did just now though when trying to install the debug software, I received that error. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388301] Discover Crashes when trying to upgrade a package
https://bugs.kde.org/show_bug.cgi?id=388301 --- Comment #1 from Michael Tunnell --- I tried it again but this time I utilized more patience. I was clicking the Update All button prior to everything loading in Discover like plugins and such. This time I waited for all of it to load then I clicked the button and the upgrade worked just fine. I will report back the next time I have an upgrade for further testing but it seems like it is caused by clicking the button prior to everything of Discover being loaded. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388301] New: Discover Crashes when trying to upgrade a package
https://bugs.kde.org/show_bug.cgi?id=388301 Bug ID: 388301 Summary: Discover Crashes when trying to upgrade a package Product: Discover Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: m...@michaeltunnell.com Target Milestone: --- Application: plasma-discover (5.11.0) Qt Version: 5.9.3 Frameworks Version: 5.41.0 Operating System: Linux 4.4.0-104-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: I opened Discover from the System Tray plasmoid and then when I clicked Update All packages, it launched a password confirmation and then immediately crashed. It would crash on every attempt to do this and always at the same time. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fee6fdfc900 (LWP 25613))] Thread 11 (Thread 0x7fee21def700 (LWP 26017)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fee6bca165b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x206f270) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x1d53910, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fee6f1adebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fee6f1ae7b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fee6bca0709 in QThreadPrivate::start (arg=0x1d53890) at thread/qthread_unix.cpp:368 #6 0x7fee67e4f6ba in start_thread (arg=0x7fee21def700) at pthread_create.c:333 #7 0x7fee6b2a63dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7fee22df1700 (LWP 25797)): #0 0x7ffebc1aebcd in clock_gettime () #1 0x7fee6b2b4836 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fee22df0a30) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7fee6bec9fd1 in qt_clock_gettime (ts=0x7fee22df0a30, clock=) at kernel/qelapsedtimer_unix.cpp:111 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7fee6bec87c9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fee140022d0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7fee6bec8d35 in QTimerInfoList::timerWait (this=0x7fee140022d0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7fee6becaa6c in timerSourcePrepareHelper (timeout=0x7fee22df0af4, src=) at kernel/qeventdispatcher_glib.cpp:132 #8 idleTimerSourcePrepare (source=, timeout=0x7fee22df0af4) at kernel/qeventdispatcher_glib.cpp:212 #9 0x7fee65ef691d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fee65ef72bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fee65ef749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fee6beca6cb in QEventDispatcherGlib::processEvents (this=0x7fee140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7fee6be72e2a in QEventLoop::exec (this=this@entry=0x7fee22df0cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #14 0x7fee6bc9b8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #15 0x7fee6bca0709 in QThreadPrivate::start (arg=0x21ec080) at thread/qthread_unix.cpp:368 #16 0x7fee67e4f6ba in start_thread (arg=0x7fee22df1700) at pthread_create.c:333 #17 0x7fee6b2a63dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fee237fe700 (LWP 25785)): #0 0x7fee6b29a70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fee65ef738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fee65ef7712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fee314669d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fee65f1dbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fee67e4f6ba in start_thread (arg=0x7fee237fe700) at pthread_create.c:333 #6 0x7fee6b2a63dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fee23fff700 (LWP 25784)): #0 0x7fee6b29a70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fee65ef738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fee65ef749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fee65ef74d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fee65f1dbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fee67e4f6ba in start_thread (arg=0x7fee23fff700) at pthread_
[Plasma Vault] [Bug 385444] Add Ability to Delete a Vault via GUI
https://bugs.kde.org/show_bug.cgi?id=385444 --- Comment #3 from Michael Tunnell --- @Ivan Čukić > I'm leaning towards having 'dismantle' just unregister (your third step) the > vault and force the user to delete the directories manually (with this stated > in the UI so that the user does not have any surprises). I think there should be an offer of Dismantle and Delete. Dismantling doing as you suggest where it just removes the entry but the data is fine. Deleting would be a full delete of entry and files/folders. @Nate Graham > The UI should make it clear that deleting a vault with information in it is a > destructive action, and we should provide an undo for mistakes. This could be approached in the way Dolphin has Delete & Shift+Delete for permanent deletion. > we ought to treat users as adults capable of making their own decision and > whose time is valuable. This *exactly this*. So often I've seen projects insist that something can't be done because of fear that "it is too destructive" which of course is replied by the user with "yes, that is exactly the point of why I want it." -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 385445] Changing Focus to Password Dialog Upon Opening Vault from System Tray
https://bugs.kde.org/show_bug.cgi?id=385445 --- Comment #3 from Michael Tunnell --- @Christoph Feck I tried what you suggested and it worked fine. I used KDE Neon Git Stable in order to do the testing so I would assume it has the latest versions of everything since the beta. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 385445] New: Changing Focus to Password Dialog Upon Opening Vault from System Tray
https://bugs.kde.org/show_bug.cgi?id=385445 Bug ID: 385445 Summary: Changing Focus to Password Dialog Upon Opening Vault from System Tray Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: m...@michaeltunnell.com Target Milestone: --- While working on the Plasma 5.11 Release Video, I noticed that when I selected the option to "Open with File Manager" it would activate the password dialog. I expected that the dialog would be in focus immediately so I could start typing but instead the widget/applet keeps the focus. In most situations in Plasma, I've noticed that when the password dialog is opened it takes focus to allow for immediate interaction so I think this Vault action should also utilize that approach as well. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 385444] New: Add Ability to Delete a Vault via GUI
https://bugs.kde.org/show_bug.cgi?id=385444 Bug ID: 385444 Summary: Add Ability to Delete a Vault via GUI Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: m...@michaeltunnell.com Target Milestone: --- At the moment, it seems the only way to delete a vault is to manually perform the following: 1. Delete the folder ~/Vaults/Vault_NAME 2. Delete the folder ~/.vaults/Vault_NAME.enc 3. Delete the entry for the vault inside of ~/.config/plasmavaultrc There isn't any documentation as to how to do this that I could find and the git log seems to have previously had a "dismantle" option that was removed. I think this is an important feature to have as soon as possible. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 381110] Consistent Crashing in Kdenlive when using Custom Wipe Transition
https://bugs.kde.org/show_bug.cgi?id=381110 --- Comment #3 from Michael Tunnell --- @alcinos, here is the wipe file. Unfortunately, I couldn't attach it because of the silly 4MB max limit for attachments. http://michaeltunnell.com/files/clock-at-3.pgm -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 381110] Consistent Crashing in Kdenlive when using Custom Wipe Transition
https://bugs.kde.org/show_bug.cgi?id=381110 --- Comment #1 from Michael Tunnell --- Anyone interested in addressing this? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382757] kdenlive won't launch "Undefined Symbol: qt_hash_seed"
https://bugs.kde.org/show_bug.cgi?id=382757 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #8 from Michael Tunnell --- I did the same thing as @Paul Figueiredo did. I uninstalled Kdenlive, removed the kdenlive-stable PPA, removed old dependencies, and reinstalled Kdenlive with the neon packages. Kdenlive works fine now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378032] Remember history of notifications like on KDE4
https://bugs.kde.org/show_bug.cgi?id=378032 --- Comment #24 from Michael Tunnell --- (In reply to Tom Hardy from comment #21) > I would like to point out that notification are already configurable on a > per application basis in that you can show a popup message or not, play a > sound or not, etc., or run a script that can presumably use a different > notification system. ;) As David Edmundson said, this is not applicable to all applications and in fact most applications. Only apps that develop specifically to support this level of customization is applicable. I'd say that around 70% of applications that I've tried do not support this. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 381110] New: Consistent Crashing in Kdenlive when using Custom Wipe Transition
https://bugs.kde.org/show_bug.cgi?id=381110 Bug ID: 381110 Summary: Consistent Crashing in Kdenlive when using Custom Wipe Transition Product: kdenlive Version: 17.04.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: m...@michaeltunnell.com Target Milestone: --- Created attachment 106047 --> https://bugs.kde.org/attachment.cgi?id=106047&action=edit backtrace data This bug occurs with Kdenlive 17.04.2 on KDE Neon with Plasma 5.10.1 I created a custom pgm wipe for the clock wipe to be started at 3 (right side) rather that from 12 (top). When selecting the wipe, Kdenlive crashes every time just from the selection of the wipe. I created a video to dmeonstrate the issue: https://youtu.be/G4H5Wy0Spl4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378032] Remember history of notifications like on KDE4
https://bugs.kde.org/show_bug.cgi?id=378032 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #20 from Michael Tunnell --- I'd just like to comment and say that I also want permanent notifications option because I want to use an email notifier tool that sends notifications but not having the ability to check what notifications have happened makes it worthless. I do think it should be an option and there could be a need for a redesign of how it functions. My Suggestion: 1. Leave the notification area the same size it is now. 2. Add option for permanent notifications. 3. Add a "Manage Notifications" (or something) button. 4. Open new window that contains all of the notifications that have been marked as permanent, organized by the application that initiated the notification. I can do a design mockup of this idea, if interested. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 378055] Depends on libmimetic0 but needs libmimetic0v5
https://bugs.kde.org/show_bug.cgi?id=378055 --- Comment #5 from Michael Tunnell --- > and that the OBS actually gets the job done Except when it doesn't like in this case. :) -- > Feel free to setup whatever repos you need, then. You can find Trojita's git > URL on the project's homepage That would result in me maintaining an unofficial PPA for others and that is not something I think any project should want because that could easily end badly. I suppose this is a "WONTFIX' issue and I'll just wait for Stretch to replace Jessie so that I can review this app. -- Have a nice day. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 378055] Depends on libmimetic0 but needs libmimetic0v5
https://bugs.kde.org/show_bug.cgi?id=378055 --- Comment #3 from Michael Tunnell --- @Jan would there be any chance for Trojita to set up a PPA to solve the Ubuntu support? If the packages were automatically built by Launchpad then the Debian vs Ubuntu issues would be solved automatically. If Trojita has git somewhere it's actually possible to mirror git commits to Launchpad so that updates are rather seamless. I have used this git mirroring feature before and it works pretty well. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 378055] New: Depends on libmimetic0 but needs libmimetic0v5
https://bugs.kde.org/show_bug.cgi?id=378055 Bug ID: 378055 Summary: Depends on libmimetic0 but needs libmimetic0v5 Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Core Assignee: trojita-b...@kde.org Reporter: m...@michaeltunnell.com Target Milestone: --- Trojita will not install in Ubuntu 16.04 because it depends on libmimetic0 which is not available from 16.04+ as it was replaced with libmimetic0v5. Here is the error provided when trying to install. > "The following packages have unmet dependencies: trojita : Depends: libmimetic0 but it is not installable E: Unable to correct problems, you have held broken packages." deb file acquired from OBS repo. (trojita_0.7_amd64.deb) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 373967] Android File System not Mounted and Pairing is no longer persistent.
https://bugs.kde.org/show_bug.cgi?id=373967 --- Comment #5 from Michael Tunnell --- > That's likely because you ran dolphin as root and it created files on your > .cache directory I did totally open it as root previously. It wasn't .cache that had weird permissions but rather it was "~/.config/kdeconnect/config". I renamed the folder for regenerating the folder and it seems to have worked. I then deleted the other older folder and will provide updates to whether this solved it or not. (so far it seems fixed) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 373967] Android File System not Mounted and Pairing is no longer persistent.
https://bugs.kde.org/show_bug.cgi?id=373967 Michael Tunnell changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Michael Tunnell --- I solved the problem. This was a permissions issue with ~/.local/share/user-places.xbel having ownership to root somehow instead of my user. I don't know how that happened but once I switched it to my user it started working again. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11
https://bugs.kde.org/show_bug.cgi?id=373291 --- Comment #6 from Michael Tunnell --- Here is the response from Rhythmbox developers on the issue, essentially saying it is a distro level issue. > rhythmbox ( -> ) libtotem-plparser ( -> ) libgmime ( -> ) libgpgme > > So, there is no direct relation between rhythmbox and libgpgme. Also, this > issue should be reported to the distribution maintainer, at best. The > symlinks are already there in my case ( Debian ). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11
https://bugs.kde.org/show_bug.cgi?id=373291 --- Comment #5 from Michael Tunnell --- > No, please leave this open until kmymoney gets updated to not need the > pthreads library. I agree with this point . . . until it is fixed by the application the bug report is still valid. I will also submit this bug report to the other applications I experienced the issue with. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 373967] New: Android File System not Mounted and Pairing is no longer persistent.
https://bugs.kde.org/show_bug.cgi?id=373967 Bug ID: 373967 Summary: Android File System not Mounted and Pairing is no longer persistent. Product: kdeconnect Version: 1.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: m...@michaeltunnell.com Target Milestone: --- My Devices Setup: Motorola Nexus 6 Android: 6.0.1 KDE Neon: with Plasma 5.8.4 KDE Connect (Linux): 1.0.1 KDE Connect (Android): 1.5 -- I have been having many issues with my KDE Connect Android app since the recent update a few days ago. 1. The Android app loses the pairing and everything stops working very quickly, whether I move away from the app in the foreground or not. 2. During the short time period of being paired, I can send files, remote input, and multimedia control. 3. I am unable able mount the Android filesystem at any time. 4. I am unable to sync the clipboard at any time. 5. During the short paired time, the android filesystem is never available in Dolphin. 6. During the short paired time, when attempting to launch the android filesystem from the system tray widget I receive the following error. "A folder named /home/michael/.cache/kioexec/krun/4394_0/ already exists." -- I have been using KDE Connect for well over a year now and I freaking love it but since December 17, it just stopped working. 5. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11
https://bugs.kde.org/show_bug.cgi?id=373291 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #1 from Michael Tunnell --- I had the same issue with missing libgpgme-pthread.so.11 but inside of Rhythmbox rather that KMyMoney. I've also seen reports of other applications being affected by this issue so I think it is a larger problem than just KMyMoney. The solution I used to temporarily solve this problem was to create a symlink of "libgpgme-pthread.so.11" to "libgpgme.so.11" inside of "/usr/lib/x86_64-linux-gnu/". Forum Thread discussing this topic, this thread contains the symlink workaround. https://forum.kde.org/viewtopic.php?f=309&t=137494 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361672] New: Plasma Ignores the KWin Setting of Disabling "Desktop navigation wraps around"
https://bugs.kde.org/show_bug.cgi?id=361672 Bug ID: 361672 Summary: Plasma Ignores the KWin Setting of Disabling "Desktop navigation wraps around" Product: plasmashell Version: 5.5.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: m...@michaeltunnell.com This is not an issue specific to the Pager applet, this applies to pretty much everything related to Plasma. This also seems to have existed since Plasma 4. Previous Bug Reports: 1. https://bugs.kde.org/show_bug.cgi?id=286297 2. https://bugs.kde.org/show_bug.cgi?id=327313 3. https://bugs.kde.org/show_bug.cgi?id=334230 The issue is that when you disable the "Desktop navigation wraps around" option in System Settings -> Desktop Behavior -> Virtual Desktops -> Switching, KWin respects the decision but nothing in Plasma respects it. Unfortunately, I could not find any setting in Plasma that respected this wrap disabling. Reproducible: Always Steps to Reproduce: 1. Disable navigation wrap. 2. Mouse scroll on Pager widget or system desktop. Actual Results: 1. In the Pager widget, do a mouse-scroll on it and the desktop navigation wraps. 2. Using the Mouse-scroll on the desktop itself via the Desktop Settings -> Mouse Actions -> Vertical-Scroll = Switch Desktops the navigation continues to wrap. Expected Results: Stop at the first and last desktops when this setting is disabled. If you have shortcuts defined in KWin for switching desktops then those shortcuts respect the option of disabling the navigation wrap. KWin Shortcuts I've Tested that Work as Expected: Switch to Next Desktop Switch to Previous Desktop Switch One Desktop Up Switch One Desktop Right Switch One Desktop Down Switch One Desktop Left -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356800] Add ability to configure how applications are shown on the desktop mouse actions application launcher
https://bugs.kde.org/show_bug.cgi?id=356800 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #1 from Michael Tunnell --- This is a bug in Plasma 5 I'm affected by as well, the usability is essentially lost entirely for me so I simply don't use it anymore. I just checked it in Plasma 4.14.x and this is not an issue . . . while it is not configurable in 4.14.x either, it defaults to application Name instead of Description. Name being the default is logical functionality so I wouldn't consider it a bug in that scenario. - http://michaeltunnell.com/images/linux/kde/mouse-action-menu-plasma-4.png In Plasma 5, the description is used instead and since there are no options to configure this feature in Desktop Settings > Mouse Actions or System Settings it makes the desktop application launcher difficult to use. http://michaeltunnell.com/images/linux/kde/plasma-5.5-mouse-action-launcher-menu-bug.jpg I'd prefer to have the ability to choose how the items are displayed in the same way that the Plasma Widgets have but I'd be satisfied personally if the default setting was Application Name. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358992] dolphin crashes after running as superuser (kdesudo dolphin)
https://bugs.kde.org/show_bug.cgi?id=358992 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #1 from Michael Tunnell --- This sounds like it could be a duplicate of https://bugs.kde.org/show_bug.cgi?id=353263 Try the workaround mentioned in this comment, https://bugs.kde.org/show_bug.cgi?id=353263#c7 -- You are receiving this mail because: You are watching all bug changes.
[kdesudo] [Bug 353263] No icons show on root session. unable to assign any too.
https://bugs.kde.org/show_bug.cgi?id=353263 Michael Tunnell changed: What|Removed |Added CC||m...@michaeltunnell.com --- Comment #9 from Michael Tunnell --- I too have this problem when using kdesudo combined with dolphin. I also tested elevating to root via "sudo su" and then launching dolphin, the same error happens there as well. I ran the suggested workaround in comment #7 without kdesudo and can confirm that the workaround of "KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true dbus-launch dolphin" running with sudo su works properly with the icons. I'm not sure if this helps narrow it down but perhaps this means that it's not directly related to kdesudo. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #89 from Michael Tunnell --- (In reply to Thomas Lübking from comment #88) > turning "you may misclick because things suddenly move under > the cursor" into "if you cannot control where you click" made me seriously > wonder whether you were not entirely sober when writing this. On comment #71 you said and i quote: "If you cannot control where you click, you've more severe and general problems." So it appears you don't remember your own words nor bothered to Ctrl+F. > your comment #80 is frankly just a collection of bullshit You are dismissive in every comment you make as if to say only your comments are valid such as claiming in multiple comments that others' points are "Wrong" or "Void". Calling my comments bullshit because you disagree with them is most certainly not civil and I'd suspect violates the KDE Community Guidelines. > I'm now really fed up and just deleted the branch fixing my "list of > defects" - you may thank Mr. Tunnell for this. That's petty and absurd. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #87 from Michael Tunnell --- (In reply to Thomas Lübking from comment #86) > Ftr, several issues with closing windows from this effect in general an in > particular w/ the previous MMB feature were stated in comments #68 and #71 Fuchs explained how you were wrong for #68 in #69. I explained how you were wrong with #71 in #80. Just because you do not agree with the feature does not mean your comments are the final say. (In reply to Martin Gräßlin from comment #84) > The discussion is over, I won't implement it and I won't approve any change > which would implement it. If you expect reasoning for that: sorry I don't > feel like I want to. You have now finally admitted what most of us suspected. You removed it because of your own preference, you have no actual reason for removing it, you have no intention to ever put it back and you won't approve any change for it. I'm glad to finally have an answer for a question regarding your comment of asking a "higher-level" that I asked 4 months ago, better late than never. The answer was exactly what I expected so I'm disappointed with your attitude but not surprised. I will go to the "higher-level" now just to get an outsider perspective of the benefits and negatives discussed in this thread. I expect you to ignore them but I will contact them out of principal. Your insistence to dictate what other people should and should not want is just wrong and disappointing whether you ignore the "higher-level" or not won't change the fact that your approach to this subject is poor. -- You are receiving this mail because: You are watching all bug changes.
