[dolphin] [Bug 484018] KDE Plasma in Wayland does not support Drag and Drop operations from Dolphin to Chromium (and Firefox).
https://bugs.kde.org/show_bug.cgi?id=484018 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #10 from Felix Ernst --- This bug might be related to https://bugs.kde.org/show_bug.cgi?id=469644 which has just been fixed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 490620] Missing can't find the information panel
https://bugs.kde.org/show_bug.cgi?id=490620 --- Comment #3 from Felix Ernst --- (In reply to quanticcpu2100 from comment #2) > (In reply to Felix Ernst from comment #1) > > If that doesn't work, I assume this is a packaging issue. Dolphin does allow > > building itself without the information panel, in which case it will look > > like in the screenshot. It is up to the people providing the software to you > > to decide whether the information panel should be available for you or not. > > I installed the baloo and baloo-widget and reboot then the information panel > still not showing up. Okay, yeah. Very weird. Fedora is such a common distribution that I bet I would have heard before if everyone on Fedora was unable to use the information panel. You also specified that you installed from RPM packages which is also the most common way to install Dolphin on Fedora. I wonder what the issue might be. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 490620] Missing can't find the information panel
https://bugs.kde.org/show_bug.cgi?id=490620 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- Would you try installing the Baloo search provider, restart Dolphin, and see if the information panel is available then? If that doesn't work, I assume this is a packaging issue. Dolphin does allow building itself without the information panel, in which case it will look like in the screenshot. It is up to the people providing the software to you to decide whether the information panel should be available for you or not. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 490486] Option to always create a new tab and focus on an already existing Dolphin window if the user clicks on Dolphin's shortcut.
https://bugs.kde.org/show_bug.cgi?id=490486 --- Comment #3 from Felix Ernst --- Ah, sorry for the misunderstanding. We regularly get reports similar to this one but yours is slightly different. You open Dolphin without specifying a folder to open. If you, for example, right-click the Dolphin entry on your panel and choose your home folder there, it will open as a new tab when that setting is enabled. You might be able to edit the desktop entry (which specifies the command that is executed when you press Dolphin in the launcher) to always open the home folder. This would then allow the setting I mentioned to kick in and open a new tab in home instead of launching a new instance of Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 490486] Option to always create a new tab and focus on an already existing Dolphin window if the user clicks on Dolphin's shortcut.
https://bugs.kde.org/show_bug.cgi?id=490486 Felix Ernst changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 490486] Option to always create a new tab and focus on an already existing Dolphin window if the user clicks on Dolphin's shortcut.
https://bugs.kde.org/show_bug.cgi?id=490486 Felix Ernst changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- In the "Configure Dolphin" dialog there is an option "Open new folders in tabs" which should solve this issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 490366] Drag and drop of multiple files in Firefox 128/130, only one file show up
https://bugs.kde.org/show_bug.cgi?id=490366 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- We did have quite a bit of trouble with drag and drop to sandboxed applications (in Kubuntu Firefox is sandboxed because it is provided as a snap by default) in the past. Your Dolphin 22.04 falls into the time frame in which this was an issue. There is a good chance everything would work fine with newer versions of Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488626] Please make Dolphin hide 'lost+found' dirs by default, just like Thunar does
https://bugs.kde.org/show_bug.cgi?id=488626 --- Comment #8 from Felix Ernst --- Good to hear that we have come to a mutual understanding and you are welcome! :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443438] dolphin not usable keyboard-only / without mouse
https://bugs.kde.org/show_bug.cgi?id=443438 --- Comment #4 from Felix Ernst --- >- missing highlighting where the active input is >- if the filelist-panel is active (barly noticeable by the color change in the >surrounding box) >- then, no file is selected by default (another indicator necessary to 'see' >where we are). >Using the cursor keys will select a file (blue background) and will stay >highlighted >- zoom activation (with shift-tab's) is also nearly impossible to see, just >the single pixel line around the zoom-knob changes I agree that these aren't always all that obvious. >- just pressing tab-key does not go 'forward', you remain in the left places >selection. Shift-tab works, by the way I think I fixed this one with https://invent.kde.org/system/dolphin/-/commit/a4efbfbfa69f04ed21fe703a11bb59416ef8a821. >- how do i access the back/forward or icons-view buttons? I fixed this with https://invent.kde.org/frameworks/kxmlgui/-/commit/cf0a2f7c6ca8e426da37abd6a09186c74a88b73f. >1. Start Dolphin, at this stage, pressing Tab navigates between the two panes >I have in the middle (I have the view split) At least this part is most likely caused by the off-by-default "Switch between panes with Tab" setting. >2. Press Shift Tab repeatedly. Notice other elements in the window get focus >in turn, but the Folders panel never gets focus. This seems to work on my end with current master. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 489943] New: Trying to connect to an SSH Entry results in "Error issuing SSH Command"
https://bugs.kde.org/show_bug.cgi?id=489943 Bug ID: 489943 Summary: Trying to connect to an SSH Entry results in "Error issuing SSH Command" Classification: Applications Product: konsole Version: 24.05.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: plugins Assignee: konsole-de...@kde.org Reporter: felix.l...@outlook.com Target Milestone: --- SUMMARY Trying to connect to an SSH Entry results in "Error issuing SSH Command" SELinux on permissisve did not change the behaviour. The issue is not present when installing Konsole using yum, therefor I suspect the issue is due to bwrap sandboxing. STEPS TO REPRODUCE 1. Go to https://flathub.org/apps/org.kde.konsole 2. Install Konsole using "flatpak install flathub org.kde.konsole" 3. Start Konsole via the Fedora Desktop Environment (gnome) 4. Enable the SSH Manager plugin under Plugins 5. Add an Entry to the SSH Manager 6. Doubleclick to connect to the Entry OBSERVED RESULT The following error appears in a small window: Title: "Error issuing SSH Command" Body"Can't issue SSH command outside the shell application (eg, bash, zsh, sh)" EXPECTED RESULT SSH Connection to the specified SSH Manager entry. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.0-427.18.1.el9_4.x86_64, Fedora 9.4 qt6 gnome 46.3.1 ssh -V: OpenSSH_9.6p1, OpenSSL 3.2.1 30 Jan 2024 Flatpak 1.15.8 ADDITIONAL INFORMATION Konsole was installed on a pretty much freshly installed Fedora instance using flatpak. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477739] Free space dropdown shows empty menu if Filelight is not installed
https://bugs.kde.org/show_bug.cgi?id=477739 --- Comment #4 from Felix Ernst --- Git commit 0d981e7b7df266c867004e23a169ba8cc13c8683 by Felix Ernst. Committed on 08/07/2024 at 11:41. Pushed by felixernst into branch 'master'. Improve Filelight installation UX Before this commit pressing the free space button when Filelight is not installed would show a singular action called "Install Filelight to View Disk Usage Statistics…". Pressing this button would open the store page for Filelight. This is an okay user experience, but we can do better. This commit makes it so pressing the free space button when Filelight is not installed shows an attractive UI that makes clear that freeing up disk space can be accomplished nicely by installing Filelight. The "Install Filelight…" button on this UI is connected to PackageKit directly, so we do not need to show a separate store like Discover and instead trigger an installation right then and there. For this, the recently introduced DolphinPackageInstaller KJob is used. Installation progress is reported through the status bar similar to the progress reporting of slowly loading directories or searches. Installation failure or success is ultimately shown within Dolphin as a passive notification above the view. On Microsoft Windows or when PackageKit is not available, the install button will only open a store page for Filelight. M +1-0src/CMakeLists.txt M +3-0src/config-dolphin.h.cmake M +1-0src/dolphinviewcontainer.cpp M +2-2src/global.h M +7-0src/statusbar/dolphinstatusbar.cpp M +7-0src/statusbar/dolphinstatusbar.h M +98 -11 src/statusbar/statusbarspaceinfo.cpp M +32 -0src/statusbar/statusbarspaceinfo.h https://invent.kde.org/system/dolphin/-/commit/0d981e7b7df266c867004e23a169ba8cc13c8683 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 489165] Selecting multiple files behaves unintuitively when View - Details - "Open files and folders" is set to "By clicking on an icon or name"
https://bugs.kde.org/show_bug.cgi?id=489165 Felix Ernst changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Felix Ernst --- (In reply to i from comment #2) > Could it make more sense to have the *visible* selection box keep to what > the mouse was dragged for, but have the box still select everything on that > horizontal line? I think so, yes. That's actually what I suggested we do in https://invent.kde.org/system/dolphin/-/merge_requests/585#note_736366 and which was eventually implemented. It wasn't implemented for the non-default "Open files and Folders: By clicking on an icon or name" though, which is what this bug report is about. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479695] In icons view mode, file name moves left during rename
https://bugs.kde.org/show_bug.cgi?id=479695 Felix Ernst changed: What|Removed |Added CC||smi...@abv.bg --- Comment #13 from Felix Ernst --- *** Bug 487005 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487005] When renaming in icon view, the cursor and the text is not centered but goes to the very left
https://bugs.kde.org/show_bug.cgi?id=487005 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 479695 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 489165] Selecting multiple files behaves unintuitively when View - Details - "Open files and folders" is set to "By clicking on an icon or name"
https://bugs.kde.org/show_bug.cgi?id=489165 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- The selection rectangle used to cover the full width of the view which would solve this bug, but this was changed. IIRC this was done for consistency and because some users thought it was confusing that the selection rectangle was bigger than the area that the mouse was dragged for. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488626] Please make Dolphin hide 'lost+found' dirs by default, just like Thunar does
https://bugs.kde.org/show_bug.cgi?id=488626 --- Comment #5 from Felix Ernst --- (In reply to Eduard from comment #4) >Thanks for the detailed reply! You are welcome! >Now that's solved too with .hidden. I am glad to hear that! > However, that gives a lot of specific control per directory, but it wouldn't > be great if Dolphin had a general configuration option for this too? But > lower priority wish, I get it. It's a bit too niche I think. Creating such a .hidden file is quite easy and one only has to do it once per file system. As a general option for hiding we have already recently added a setting in Dolphin's settings dialog to hide application/x-trash mime types. Users can already modify that any file extension belongs to that mime type and hide them this way. And I don't want to be too eager to hide that folder either because it can be very important for recovering data. Actually, it might make more sense to bother the developers of the fsck utility to not create such folders in the first place. That's on them after all (https://www.baeldung.com/linux/lost-found-directory) and conceptually it seems easier to me to not create a random empty folder when it isn't needed rather than have every application that shows folders to hide it. Dolphin provides various ways of hiding already and we do inform about them in the extended help text of the Dolphin hiding feature. I think we should have most workflows covered this way. There are unfortuantely sometimes aspects which are so custom and specific to users that adding a general setting for them is too much trouble and therefore leads to more issues in the long term than it helps. > And then I am going to have that same wish for Thunar as well. :P Well, don't get your hopes up! I am not sure the Thunar devs are keen on implementing such a feature either. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488626] Please make Dolphin hide 'lost+found' dirs by default, just like Thunar does
https://bugs.kde.org/show_bug.cgi?id=488626 Felix Ernst changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Felix Ernst --- >Are there defined standards beyond dot files and dot folders >which describe these as that they should be hidden? Actually as far as I know even the standard of dot files being hidden is mostly "a standard" because everyone does this. Dolphin could simply show dot files like normal files and we wouldn't break any compatibility or any official standard. We would only break user expectations. (https://unix.stackexchange.com/questions/88875/why-are-filenames-that-start-with-a-dot-hidden-can-i-hide-files-without-using-a) So no, there is no agreed on convention that lost+found directories should be displayed as anything other than a normal folder as far as I am aware. >Otherwise maybe some custom and user configurable filter list could also do >the job? Indeed we have something like this already! See: https://superuser.com/questions/826194/how-to-tell-dolphin-which-files-to-hide Basically you would need to create a text file called ".hidden" next to the "lost+found" folder and then write "lost+found" into the ".hidden" file. Dolphin will read the contents of the ".hidden" file and make sure the "lost+found" folder will be treated like it was hidden. Does that work for you? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487590] Ambiguous shortcut on F3 (split view) after update
https://bugs.kde.org/show_bug.cgi?id=487590 Felix Ernst changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #6 from Felix Ernst --- (In reply to 1r8l864u from comment #5) > I ended up "solving" it by deleting the default shortcuts entirely as well > as dolphinrc and reapplying everything myself... Not sure if that was > overkill, but there were no more ambiguous shortcuts (partially because > there were no shortcuts at all anymore). Okay, great! I mean, it would be even better if we knew that this was just a weirdness that somehow affected only you and not something we need to fix within KDE somehwere, but it is at least neat that you are no longer affected by this issue. We can probably no longer reproduce the issue now, and there is also no immediate need for it anymore. I guess this means that I should mark this bug as resolved instead of keeping it open indefinitely. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485599] dolphin crash when using select file shorcuts (shortcut space)
https://bugs.kde.org/show_bug.cgi?id=485599 Felix Ernst changed: What|Removed |Added CC||arjun...@gmail.com --- Comment #10 from Felix Ernst --- *** Bug 488052 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488052] Hitting space with Dolphin in focus crashes it
https://bugs.kde.org/show_bug.cgi?id=488052 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||felixer...@kde.org --- Comment #2 from Felix Ernst --- (In reply to Arjun42M from comment #0) > Hi there, > > This is my first ever bug report on KDE. Hi, thanks for reaching out! > I had opened Dolphin file browser, and hit space (habit from Microsoft > Windows to select the first time), and it crashed. I have now replicated > this a few times. > > This is a nearly stock Fedora Workstation 40 install that I had just > completed a few hours ago. KDE Plasma 6. No custom tweaks. Have barely had a > chance to play with standard settings, and haven't modified anything related > to the Dolphin file browser. Indeed it is a bit unfortunate that setups like yours are still affected by this crash. The problem is that this crash wasn't introduced by a change in Dolphin, but by a change in the software Dolphin depends on. Qt 6.7 to be exact. So we released a Dolphin version that didn't crash originally and later Qt was updated on distributions that still used the same Dolphin version. We have promptly changed Dolphin so it no longer crashes, but we couldn't update the previously shipped Dolphin version anymore. This crash will no longer happen once the Dolphin 24.05 version arrives on your system. I'll mark this bug report as a duplicate of the already solved bug report which first reported this crash. *** This bug has been marked as a duplicate of bug 485599 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488086] The UX for enabling plugins is very unintuitive
https://bugs.kde.org/show_bug.cgi?id=488086 Felix Ernst changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- I agree with the basic issue raised in this bug report. We did have a discussion about this in https://invent.kde.org/system/dolphin/-/merge_requests/422 before but didn't find a solution that everyone was happy with. >I would suggest either renaming "Context Menu" to "Plugins" >(or revert it to "Services" as it used to be known, or think of a >better name than either suggestion), or splitting it into two headers >- one specifically handling plugins, and one for handling the context menu >entries. It's IMO difficult to find a good solution here. "Context menu" as a title has the advantage that it can be understood by many users. "Services" or "Plugins" is a bit abstract perhaps. It is also difficult to split it into two disparate groups because – as you pointed out – some plugins provide both changes to the general view as well as adding context menu actions. My idea before was to name it "Extensions" perhaps, though this doesn't really make it clear that users should navigate here if they want to hide some action from their context menu. I haven't seen a solution to this yet which seems great. I'll mark this as confirmed for now. It is definitely not ideal as it is. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488094] Separate terminal assigned to tabs
https://bugs.kde.org/show_bug.cgi?id=488094 Felix Ernst changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- Yes, I have been wondering in the past if it wouldn't make more sense to have a terminal per view (not only per tab) instead of only having one terminal per Dolphin window. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488540] Emptying trash has no feedback and can be runned twice by accident causing error
https://bugs.kde.org/show_bug.cgi?id=488540 Felix Ernst changed: What|Removed |Added Ever confirmed|0 |1 CC||felixer...@kde.org Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488495] Messing up desktop icons
https://bugs.kde.org/show_bug.cgi?id=488495 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org, ||h...@kde.org Product|dolphin |plasmashell Version|24.05.0 |6.0.5 Component|general |Folder Target Milestone|--- |1.0 Assignee|dolphin-bugs-n...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488626] Please make Dolphin hide 'lost+found' dirs by default, just like Thunar does
https://bugs.kde.org/show_bug.cgi?id=488626 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- >These folders are generated by fsck on Linux, and they are inaccessible >for non root users. Hiding these folders is great thing. Would you please clarify why you think lost+found directories should be hidden? Your reasoning makes it sound like you want every folder that is only accessible for the root user to be hidden. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488295] Blurry graphic artifact visible behind floating panel in plasmashell
https://bugs.kde.org/show_bug.cgi?id=488295 --- Comment #21 from Felix Zhu --- I'd also like a backport -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488772] User .desktop not work when using keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=488772 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- >When launching Dolphin by click the icon in the application menu, >the sort order respect "~/.local/share/applications/org.kde.dolphin.desktop", >which gets LC_COLLATE="zh_CN.UTF-8", so that it sorts in Chinese Pinyin as >expected. >But when launching Dolphin with keyboard shortcuts, it doesn't. So the global keyboard shortcut for Dolphin as defined in system settings does not seem to care about the extra environment variables defined in the Dolphin .desktop file. Yes, I guess that might be unexpected. If that is the issue you should be able to work around this by binding a custom command that includes the environment variable to a keyboard shortcut in system settings. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476670] Dolphin doesn't focus on the new pasted file if it's beyond screen border
https://bugs.kde.org/show_bug.cgi?id=476670 --- Comment #19 from Felix Ernst --- (In reply to mozo from comment #18) > Could someone tell me when the fix is supposed to lend for us? There were 2 > versions after the fix and it isn't here yet. Seems to me like the commit by Anthony Fieroni above didn't make it into the Dolphin 24.05 release. So as it stands it will only be available from the August release 24.08 onward. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488295] Graphic artifact visible behind floating panel in plasmashell
https://bugs.kde.org/show_bug.cgi?id=488295 --- Comment #9 from Felix Zhu --- I can also reproduce. It only happens sometimes but not always. SOFTWARE/OS VERSIONS Linux: Latest arch Linux (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.3.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION Intel iGPU -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488295] Graphic artifact visible behind floating panel in plasmashell
https://bugs.kde.org/show_bug.cgi?id=488295 Felix Zhu changed: What|Removed |Added CC||ferlax...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488568] CPU and Memory load monitors now showing up in both widgets and the application
https://bugs.kde.org/show_bug.cgi?id=488568 Felix Zhu changed: What|Removed |Added CC||ferlax...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488568] New: CPU and Memory load monitors now showing up in both widgets and the application
https://bugs.kde.org/show_bug.cgi?id=488568 Bug ID: 488568 Summary: CPU and Memory load monitors now showing up in both widgets and the application Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ferlax...@gmail.com Target Milestone: --- Created attachment 170546 --> https://bugs.kde.org/attachment.cgi?id=170546=edit CPU and Memory load monitors now showing up in both widgets and the application *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY System monitor's charts and graphs not showing up at all in the app and in widgets. STEPS TO REPRODUCE 1. Install the kde-unstable repository to get latest kde software 2. sudo pacman -Syu 3. observe that all the system monitor charts just isn't visible anymore(including but not limited to bar graphs, line charts, etc.) OBSERVED RESULT The system monitor charts have no value and lines and bars in the bars and line charts are not showing up. EXPECTED RESULT Function as in 6.0 where the lines are showing up SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.90 (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.3.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION am using the 6.9.4 zen kernel with intel igpu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487718] dolphin crashing on double tapping the spacebar.
https://bugs.kde.org/show_bug.cgi?id=487718 --- Comment #4 from Felix Ernst --- @Shebab, your crash is unrelated to the crash reported in this bug. It has a completely different stack trace and therefore wasn't fixed when this bug report was. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487770] Feature Request: Option to bind arbitrary command lines to shortcut keys and/or custom toolbar buttons
https://bugs.kde.org/show_bug.cgi?id=487770 Felix Ernst changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Felix Ernst --- > Heh, yeah -- that's pretty much exactly what I was asking for. Great! > Since that feature already gets it 90% of the way there, maybe > buttons/shortcuts for that could be implemented later? Well, that feature is specifically about what to do when double-clicking the view. For the other custom service menus I linked a guide to there is indeed a long-standing bug report with many duplicates to allow users to bind those custom commands to keyboard shortcuts. I hope some contributor will find the time to work on this but it might be tricky to implement, so it might take a while for this to happen. > At any rate, I'd be > fine with closing this feature request now if you want to, since that > feature is already so close to it. Yes, let's close this then. It would be confusing to keep a bug report around that is already 90% done, instead of having new bug reports that are very specific about what still doesn't work as expected. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487590] Ambiguous shortcut on F3 (split view) after update
https://bugs.kde.org/show_bug.cgi?id=487590 --- Comment #4 from Felix Ernst --- (In reply to 1r8l864u from comment #3) > (In reply to Felix Ernst from comment #2) > > Considering that you can't find the conflicting shortcut in Dolphin, I > > wonder if this could either be a shortcut that is only available while the > > Konsole panel is active in Dolphin (to check this, first activate Dolphin's > > terminal panel, then open the Dolphin keyboard shortcuts configuration), or > > if some global keyboard shortcut might cause a conflict. This is just a stab > > in the dark on my part though, I don't actually know that much about how > > such a keyboard conflict could suddenly appear during an update. > > Opening the Konsole panel did not bring up any extra options associated with > just F3 in the keyboard config menu. I have reset all the shortcuts to their > default settings but this also did not resolve the ambiguous shortcut. Ah, that's unfortunate. I am mostly guessing here as well. I don't really know what could be the issue for you. > I would like to delete the config files for Dolphin, but I'm not sure which > files to delete within ~/.config/. For hotkey settings see this answer: https://www.reddit.com/r/kde/comments/cmkwae/where_can_i_find_the_config_file_for_keyboard/ Dolphin settings can be reset by deleting /home/userName/.config/dolphinrc . Not sure if that would help at all though, so maybe only move it out of the way for a moment to test and move it back there if you want to keep some settings. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487770] Feature Request: Option to bind arbitrary command lines to shortcut keys and/or custom toolbar buttons
https://bugs.kde.org/show_bug.cgi?id=487770 --- Comment #3 from Felix Ernst --- (In reply to ocalhoun from comment #2) > Hmm... The only way I can find for doing so is: > > […] > > While it may technically be possible to do things this way ... this process > seems a bit unnecessarily convoluted if you're just trying to do something > simple. And it seems to require making your new addon publicly available, > which could be just cluttering the store with things so specific they're > only relevant to you personally, or it could possibly even have privacy > concerns, if the command you need to run includes private information. > > That seems far from ideal to me. It's a reasonable process for adding a new > Plasma widget or desktop theme, sure ... but far too complicated to just get > Dolphin to execute a console command. It is way easier than that and you don't need to upload anything. Here is the guide: https://develop.kde.org/docs/apps/dolphin/service-menus/ One only needs to create a file with a specific format in a local folder and then one can execute custom commands from the Dolphin context menu. > It would be much nicer and simpler to have one of those list items in the > Context Menu settings be "Run Command:" with a text box or popup or > something to enter your command into. (And a new blank "Run Command:" entry > added afterward.) This is not exactly what you are asking for, but the upcoming release (I think in August?) will have a feature so one can set a custom command for double-clicking the view (https://invent.kde.org/system/dolphin/-/merge_requests/764). Generally speaking though, the way of creating service menus as described in the guide I linked is the better way currently. However, there is actually a service menu for creating service menus in the store page: https://store.kde.org/p/1952905/ I haven't tested it, but it seems to allow creating service menus for custom scripts very easily. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487590] Ambiguous shortcut on F3 (split view) after update
https://bugs.kde.org/show_bug.cgi?id=487590 --- Comment #2 from Felix Ernst --- Considering that you can't find the conflicting shortcut in Dolphin, I wonder if this could either be a shortcut that is only available while the Konsole panel is active in Dolphin (to check this, first activate Dolphin's terminal panel, then open the Dolphin keyboard shortcuts configuration), or if some global keyboard shortcut might cause a conflict. This is just a stab in the dark on my part though, I don't actually know that much about how such a keyboard conflict could suddenly appear during an update. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487590] Ambiguous shortcut on F3 (split view) after update
https://bugs.kde.org/show_bug.cgi?id=487590 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- Very weird. By your description this is very annoying and can't really be resolved as a user, so we usually should get a bunch of bug reports about this. This doesn't seem to be the case yet, so either people haven't updated to the latest Dolphin 24.05 version as fast as you have, or the bug is somewhat specific to your setup in some way. It might be worth looking into deleting your Dolphin configuration files and resetting Dolphin if we don't see a bunch of similar bug reports coming in soon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407486] dolphin, extended toolbar disappear. It does not allow me to click hidden buttons.
https://bugs.kde.org/show_bug.cgi?id=407486 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #4 from Felix Ernst --- AFAIK the issue is that the location bar is implemented to have a fixed size. I did that because it was the only way to position it nicely while it actually tries to take up as much space as it can get itself. I assume the fix for this is making sure that location bars/KUrlNavigators in general don't expand to take up all the space and then move away from a fixed width approach in Dolphin, which in programming terms means: 1. In the KIO framework, calculate sizeHint() for KUrlNavigators in a way that they only want as much space as they need to show the path. 2. In the KIO framework, set the default size policy of KUrlNavigators away from QSizePolicy::MinimumExpanding. 3. In Dolphin, avoid setting a fixed size for DolphinNavigatorsWidgetAction and instead set a QSizePolicy::MinimumExpanding there so it takes up the remaining space dynamically without ever expecting more space than the toolbar has. This is a bit of an untested assumption and I assume it might be a bit fiddly to get this right. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485599] dolphin crash when using select file shorcuts (shortcut space)
https://bugs.kde.org/show_bug.cgi?id=485599 Felix Ernst changed: What|Removed |Added CC||saurabh2...@glbajajgroup.or ||g --- Comment #9 from Felix Ernst --- *** Bug 487718 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487718] dolphin crashing on double tapping the spacebar.
https://bugs.kde.org/show_bug.cgi?id=487718 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED CC||felixer...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 485599 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487770] Feature Request: Option to bind arbitrary command lines to shortcut keys and/or custom toolbar buttons
https://bugs.kde.org/show_bug.cgi?id=487770 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Felix Ernst --- In the Dolphin settings there is a "Context Menu" category. There one can download new plugins and services which will then be available from the context menu and will act on the currently selected files or will act on the currently open folder. These actions can be user-defined and downloaded. There are tutorials for this online if you need anything specific. >Some other examples of what a user could create: Some of these indeed are already available for download there! About binding these to keyboard shortcuts: This is indeed not possible currently. There is a long-standing bug report with many duplicates for this. I don't have it at hand at the moment but it shouldn't be too hard to find it. It might make sense to mark this bug report here as a duplicate of that bug report if this is the only aspect missing to resolve this bug report. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448865] [Request] Dark Mode for Windows 10/11
https://bugs.kde.org/show_bug.cgi?id=448865 Felix Ernst changed: What|Removed |Added Resolution|--- |FIXED CC||felixer...@kde.org Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/aeb7048 ||51d3b33f88eb601d597c2b0743d ||4e08df Version Fixed In||24.05 Status|CONFIRMED |RESOLVED --- Comment #4 from Felix Ernst --- This should now be fixed by the combination of https://invent.kde.org/system/dolphin/-/commit/aeb704851d3b33f88eb601d597c2b0743d4e08df and https://invent.kde.org/system/dolphin/-/commit/b30eabbee26b1a2189170571e49bc86c0a49d334 . The latter also changes the styling on Windows to be closer to the Linux version which wasn't really a goal but the easiest way to accomplish dark mode working. These fixes are available in Dolphin 24.05 and later which is the version that was just released a few days ago, however I haven't looked into how long it takes for it to then become available as a Windows download. Glad you are enjoying Dolphin on Windows! It unfortunately doesn't get as much testing as the Linux version, so sorry for any issues you encounter. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477739] Free space dropdown shows empty menu if Filelight is not installed
https://bugs.kde.org/show_bug.cgi?id=477739 Felix Ernst changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/0a8f84a ||52dcd246550b5ea0e795dd7b309 ||f2ece1 --- Comment #2 from Felix Ernst --- Git commit 0a8f84a52dcd246550b5ea0e795dd7b309f2ece1 by Felix Ernst, on behalf of Nicolas Fella. Committed on 30/05/2024 at 15:21. Pushed by felixernst into branch 'master'. Offer installing Filelight if no disk usage analyzer was found This avoids an empty menu and points the user towards a useful tool M +12 -1src/statusbar/statusbarspaceinfo.cpp https://invent.kde.org/system/dolphin/-/commit/0a8f84a52dcd246550b5ea0e795dd7b309f2ece1 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 487237] Creating compressed archives in read-only directory
https://bugs.kde.org/show_bug.cgi?id=487237 Felix Ernst changed: What|Removed |Added Product|dolphin |ark Component|general |plugins Assignee|dolphin-bugs-n...@kde.org |elvis.angelac...@kde.org CC||felixer...@kde.org, ||rthoms...@gmail.com --- Comment #2 from Felix Ernst --- Moving this bug report to Ark because the Compress action (and when it is enable or available) is implemented there AFAIK. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 385008] Make inverse search (aka source reference or backward search) discoverable from the UI
https://bugs.kde.org/show_bug.cgi?id=385008 Felix Ernst changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 385008] Make inverse search (aka source reference or backward search) discoverable from the UI
https://bugs.kde.org/show_bug.cgi?id=385008 Felix Ernst changed: What|Removed |Added Summary|[wish] mouse action or |Make inverse search (aka |shortcut or automatic move |source reference or |to position in source code |backward search) |(latex) if scolling live|discoverable from the UI |preview window | -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 385008] [wish] mouse action or shortcut or automatic move to position in source code (latex) if scolling live preview window
https://bugs.kde.org/show_bug.cgi?id=385008 --- Comment #4 from Felix Ernst --- Created attachment 169773 --> https://bugs.kde.org/attachment.cgi?id=169773=edit Suggestion where an inverse search button could be placed for disoverability I hope something like this can be implemented. I tried myself, by sending a Shift+Mouse Left-Click Event from Kile to the viewer but this somehow didn't have any effect. I think it would be a huge improvement to usability to have something like this. As it stands, I assume that most users (just like the original bug reporter) will not find this feature and always have to manually search through their editor to find the same line they just read in the preview. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484555] [Dolphin] Enhance with “Create folder from selected files”
https://bugs.kde.org/show_bug.cgi?id=484555 Felix Ernst changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/d448f4f ||35d286cae45a62f5a9c1a3be812 ||02f92b Status|ASSIGNED|RESOLVED --- Comment #8 from Felix Ernst --- Git commit d448f4f35d286cae45a62f5a9c1a3be81202f92b by Felix Ernst, on behalf of Ahmet Hakan Çelik. Committed on 23/05/2024 at 13:25. Pushed by felixernst into branch 'master'. Add "Move to New Folder…" action This commit introduces an action which creates a new folder with a name specified by the user and moves all the currently selected items there in one go. This action is implemented as a KFileItemActionPlugin which means users can disable it on Dolphin's context menu settings page. M +12 -0src/CMakeLists.txt A +54 -0src/itemactions/movetonewfolderitemaction.cpp [License: GPL(v2.0+)] A +28 -0src/itemactions/movetonewfolderitemaction.h [License: GPL(v2.0+)] A +14 -0src/itemactions/movetonewfolderitemaction.json https://invent.kde.org/system/dolphin/-/commit/d448f4f35d286cae45a62f5a9c1a3be81202f92b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425997] Pressing 'Shift' to change 'Move to trash' to 'delete' does not work when a sub-context-menu is open
https://bugs.kde.org/show_bug.cgi?id=425997 --- Comment #16 from Felix Ernst --- Git commit 3f4b4bc60fe2bce4d2b6ba81e2d4e341d8092b1a by Felix Ernst, on behalf of Felix Ernst. Committed on 23/05/2024 at 11:12. Pushed by felixernst into branch 'master'. KAbstractFileItemActionPlugin: Remove wrong sentence in documentation The removed line says to have the KAbstractFileItemActionPlugin as the parent of the returned actions. Contrarily, a few lines further down the documentation says to have the parentWidget as the parent of the returned actions. The latter is the more recent addition to the documentation which was added because the former did not work out in some contexts. The bug mentioned below contains a list of changes that made the parentWidget the parent of actions from KAbstractFileItemActionPlugins, which seems to have worked out because from what I can tell they were not reverted in the years since then. M +0-3src/widgets/kabstractfileitemactionplugin.h https://invent.kde.org/frameworks/kio/-/commit/3f4b4bc60fe2bce4d2b6ba81e2d4e341d8092b1a -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443882] popup menu of highlighted text does not appear on right click in text selection mode
https://bugs.kde.org/show_bug.cgi?id=443882 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443882] popup menu of highlighted text does not appear on right click in text selection mode
https://bugs.kde.org/show_bug.cgi?id=443882 Felix Ernst changed: What|Removed |Added CC||m.lince...@gmail.com --- Comment #17 from Felix Ernst --- *** Bug 435918 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435918] Double click on "highlight with comment" annotation selects text instead of opening annotation
https://bugs.kde.org/show_bug.cgi?id=435918
Felix Ernst changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |DUPLICATE
CC||felixer...@kde.org
--- Comment #5 from Felix Ernst ---
The original request of this bug report ("Double click on 'highlight with
comment' annotation with text selection tool should open the annotation") has
been denied because while in "text selection" mode it is expected that clicking
would select text rather than open annotations. I agree with this.
As a solution, Albert suggested to open the annotation while in "text
selection" mode using right-click instead. I also agree with this and the bug
reporter Massimiliano L also seems to be fine with this.
I will therefore mark this bug as a duplicate of
https://bugs.kde.org/show_bug.cgi?id=443882 which is about right-clicking to
open annotations.
*** This bug has been marked as a duplicate of bug 443882 ***
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 484330] PDF editing tools unusable
https://bugs.kde.org/show_bug.cgi?id=484330 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Felix Ernst --- (In reply to dE from comment #0) > For e.g. use the 'insert text' annotation. > 2) You cannot select existing insert text boxes. ctrl+click does not work. > Since this feature does not work, you cannot edit, move or delete the text > box that you inserted. This is possible, however it only works while using the "Browse" tool i.e. when your mouse cursor is a grabby hand. I agree that this is confusing. I wonder if this should be marked as a duplicate of https://bugs.kde.org/show_bug.cgi?id=443882 because the core issue that users are unable to edit annotations with the wrong tool are the same. Maybe no matter the tool, right-clicking an annotation should have an "Edit…" action that opens a popup with all the necessary fields to change the annotation in any way. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 236683] notes usage, usability, interface, user experience
https://bugs.kde.org/show_bug.cgi?id=236683 Felix Ernst changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||felixer...@kde.org Status|REPORTED|NEEDSINFO --- Comment #2 from Felix Ernst --- I think sometime in the last 14 years this has been resolved. >The [notes] feature is however quite hidden. It is now available from the toolbar. IMO one cannot consider it hidden anymore. >make notes show with doubleclick This also seems to be implemented. I will mark this bug reports as NEEDSINFO so you have time to confirm or deny if this bug is fixed for you with the most recent version. If nobody reacts (e.g. because you are no longer here or changed eMail address in the meantime) this bug will automatically be closed after a while. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424723] When going back or up, underline the folder you just came from instead of selecting it
https://bugs.kde.org/show_bug.cgi?id=424723 Felix Ernst changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/122fee5 ||625f0285ec4ebda79162c723909 ||89eb2a Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #13 from Felix Ernst --- Git commit 122fee5625f0285ec4ebda79162c72390989eb2a by Felix Ernst. Committed on 18/05/2024 at 22:18. Pushed by felixernst into branch 'master'. Avoid implicitly selecting items Items should only be selected if the user wants to act on them. However, previous to this commit we sometimes selected items even when there is no reason to assume that the user would like to act on them. Such selections are dangerous because they make it more likely that the user manipulates items by accident which they never even explicitly selected. Example: The "Up" action is used to navigate to the parent folder. This will implicitly select the folder one emerged from after opening the parent folder, so just one accidental press of the Delete key will lead to data loss if the press goes unnoticed. This scenario would have been avoided if no folder had been selected automatically. The above example becomes even more dangerous if the user is acting with elevated privileges. The following implicit selections of items are being removed: - Selecting items that are being activated - Selecting folders one emerges from Even though these items will no longer be selected after these actions, they will still be marked as current. The only downside I see is that our indication of which item is "current" is a lot weaker than the selection highlight, so it might be more difficult to spot which folder one has emerged from. However, this could be counter-acted with some other temporary indication if this really turns out to be a problem. The only downside I see is that our indication of which item is "current" is a lot weaker than the selection highlight, so it might be more difficult to spot which folder one has emerged from. However, this could be counter-acted with some other temporary indication if this really turns out to be a problem. M +2-1src/dolphinviewcontainer.cpp M +17 -4src/kitemviews/kitemlistcontroller.cpp M +43 -4src/tests/dolphinmainwindowtest.cpp M +7-0src/tests/kitemlistcontrollertest.cpp https://invent.kde.org/system/dolphin/-/commit/122fee5625f0285ec4ebda79162c72390989eb2a -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485599] dolphin crash when using select file shorcuts (shortcut space)
https://bugs.kde.org/show_bug.cgi?id=485599 Felix Ernst changed: What|Removed |Added CC||bugs_kde_org.5.kuru@spamgou ||rmet.com --- Comment #7 from Felix Ernst --- *** Bug 487012 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487012] Dolphin crashes when spacebar is pressen
https://bugs.kde.org/show_bug.cgi?id=487012 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 485599 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449537] Enabling show full path checkbox in Dolphin location bar is not preserved between invocations, '>' interface is hard to use
https://bugs.kde.org/show_bug.cgi?id=449537 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #2 from Felix Ernst --- There is a setting in the Dolphin settings dialog that does the same thing and is saved between Dolphin restarts. However, I do agree that the full path checkbox in the context menu should also be saved between sessions. To implement this, we probably need a new signal in the KIO::UrlNavigator class that let's everyone know that this checkbox was changed. In Dolphin code, this signal can then be listened to and the change can be saved to the same place where it already saves to when this is changed from the Dolphin settings. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487080] Files can't be dragged & dropped between Dolphin windows if let go over another file
https://bugs.kde.org/show_bug.cgi?id=487080 Felix Ernst changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- >Issue introduced in Plasma 6. I have a Dolphin 23.08.1 here which shows the exact behaviour your are describing here. I can not drop onto another file here either. So from what I can tell this is not a regression. >EXPECTED RESULT >Previous intended behavior was that only directories detect >dropping over their icon; When dropping over another file, >the dragged file should be moved or copied near it. I guess this would make sense. Dropping one file into another never makes sense in Dolphin, so if we interpret it as dropping into the folder that contains the file being dropped on users won't have to aim as precisely anymore when drag and dropping files. At least I don't see a downside to this proposal. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430300] New requirement to remove Location Bar before toolbar can be made vertical is confusing
https://bugs.kde.org/show_bug.cgi?id=430300 --- Comment #3 from Felix Ernst --- Thanks for confirming that the behaviour hasn't changed! This is indeed still an issue, mostly because while it is absolutely possible to implement this, the only ways to implement this that I am aware of lead to somewhat ugly complex code. (In reply to TraceyC from comment #2) > The problem is mitigated since the default layout of Dolphin has changed. > The location bar is shown in an area below the toolbar. This is not correct. The Url Navigator is still on the toolbar by default. Source: https://invent.kde.org/system/dolphin/-/blob/6c60655ce246a91758f4b9035edf318cb1197a2c/src/dolphinui.rc#L114 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481401] On a slow network location, Dolphin allows two "new folder" modals then crashes
https://bugs.kde.org/show_bug.cgi?id=481401 Felix Ernst changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/742566e ||b69e6bf46e7abb74e9ce9293c4b ||3ed7e8 Resolution|--- |FIXED --- Comment #13 from Felix Ernst --- Git commit 742566eb69e6bf46e7abb74e9ce9293c4b3ed7e8 by Felix Ernst, on behalf of Akseli Lahtinen. Committed on 11/05/2024 at 15:59. Pushed by felixernst into branch 'master'. Check if namejob is already being run before opening new createDirectory dialog This is a fix for a bug where in network views (or otherwise slow systems), pressing `Ctrl+Shift+N` multiple times opens multiple popup windows and thus causes a crash when any of the popups is interacted with after closing the topmost one. The problem is not the crash with popups themselves, but that we're opening multiple popups in the first place. In regular views this works fine, since the `nameJob` does not take long time at all and only one popup opens, immediately blocking the shortcut. In network views, the `nameJob` seems to take a while to run, since it is loading info from network. If user spams `Ctrl+Shift+N` shortcut in frustration, it starts more `nameJob`s and eventually when those jobs are done, it opens multiple popups. This code checks that if we're already running a `namejob`, we're very likely waiting for the `createDir` popup to appear, so we don't do anything until there is no more `nameJob` running. I've tested that it works in both network and regular Dolphin views. M +1-1CMakeLists.txt M +8-2src/dolphinmainwindow.cpp https://invent.kde.org/system/dolphin/-/commit/742566eb69e6bf46e7abb74e9ce9293c4b3ed7e8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486749] Actions in other programs that open folder in Dolphin run a new instance of Dolphin instead of using an existing one
https://bugs.kde.org/show_bug.cgi?id=486749 Felix Ernst changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||felixer...@kde.org --- Comment #2 from Felix Ernst --- That's probably it, so I'll set the status of this to NEEDSINFO. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465334] [Arabic] Dolphin shows file operation progress in the wrong order
https://bugs.kde.org/show_bug.cgi?id=465334 Felix Ernst changed: What|Removed |Added CC||damjan.r...@ozs.si --- Comment #1 from Felix Ernst --- *** Bug 486774 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486774] Dolphin copy progress of bytes copied has reversed values
https://bugs.kde.org/show_bug.cgi?id=486774 Felix Ernst changed: What|Removed |Added Resolution|--- |DUPLICATE CC||felixer...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 465334 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485599] dolphin crash when using select file shorcuts (shortcut space)
https://bugs.kde.org/show_bug.cgi?id=485599 Felix Ernst changed: What|Removed |Added CC||usegenera...@gmail.com --- Comment #6 from Felix Ernst --- *** Bug 486830 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486830] I pressed "space" for 'select files and folders' option.
https://bugs.kde.org/show_bug.cgi?id=486830 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 485599 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486579] Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=486579 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- We fixed a couple of crashes related to QObject::deleteLater for the upcoming Dolphin 24.05 release. I wonder if this specific crash is already fixed there. If you are looking to get rid of this crash in your system immediately, I want to mention that there is a good chance that the crash doesn't happen with the previous Qt version Qt 6.6. You might be able to downgrade. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486226] Custom Columns as plugin or script in details view
https://bugs.kde.org/show_bug.cgi?id=486226 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- >Basically, this is an advanced col Your comment is cut off there. Maybe you would have put a nice summary there. As it stands it is really difficult to follow what exactly you want to see changed. It reads more like a huge list of features and behaviour changes that would be necessary to fulfill a very specific workflow. Please also be aware that Dolphin does explicitly not have the design goal to have features for niche and advanced use cases. One thing you mention is regex filtering. That is indeed a feature that has been requested in the past and is supposed to be added to Dolphin's "Filter" feature as soon as any contributor shows up to implement it. There is also some work underway that would allow end users to use command line tools for the search. I am not sure how exactly that feature will materialise (it is quite complicated and currently in review) but there is a chance that it might allow you to create a command that serves your use case. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486069] With no files selected, activating Selection Mode crash Dolphin
https://bugs.kde.org/show_bug.cgi?id=486069 Felix Ernst changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 485599 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485599] dolphin crash when using select file shorcuts (shortcut space)
https://bugs.kde.org/show_bug.cgi?id=485599 Felix Ernst changed: What|Removed |Added CC||lts20050...@gmail.com --- Comment #4 from Felix Ernst --- *** Bug 486069 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483172] Free Disk Space button margin too wide and cuts off fonts
https://bugs.kde.org/show_bug.cgi?id=483172 --- Comment #5 from Felix Ernst --- (In reply to ndrwkotov from comment #4) > No, not only non-default themes have this problem. Fusion and Windows are > broken too. They are default, aren't they? No, they are not. Fusion is Qt's theme. On Windows we have also switched to Breeze recently because dark mode didn't work there previously. > I suggest to revert these changes. They have no sense, this UI element is not > essential, Please don't ignore my arguments. The change is essential because previously e.g. visually- or motorically-impaired users were unable to open this menu. For them this change was way more important than the custom theming of Dolphin you are interested in. > this changes ruin a lot of custom themes. > Extensive customization is not the least reason for choosing KDE Plasma. Be aware that Dolphin allows you to hide the space information or even the status bar completely if you prefer a clean look (without the bug reported here) over the functionality these components provide. To actually fix this bug report a different solution is needed that doesn't cause problems for some people. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484982] Show close button on split view
https://bugs.kde.org/show_bug.cgi?id=484982 --- Comment #5 from Felix Ernst --- (In reply to Felix Ernst from comment #4) > Hmm, actually now that I think about it, it probably wouldn't be too > difficult to add such bars only while in split view mode Actually, better than an extra bar would probably be if we added them at the end of the location bar (in dolphinnavigatorswidgetaction.cpp). Still not sure though if there would be many users who would like this. Considering that it might be better to have this disabled by default, even people who might like this might not think about enabling it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484982] Show close button on split view
https://bugs.kde.org/show_bug.cgi?id=484982 --- Comment #4 from Felix Ernst --- Hmm, actually now that I think about it, it probably wouldn't be too difficult to add such bars only while in split view mode and only when panels are "unlocked". I wonder if there are many users who would prefer that (aside from Michi ). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484982] Show close button on split view
https://bugs.kde.org/show_bug.cgi?id=484982 --- Comment #3 from Felix Ernst --- (In reply to Michi from comment #2) > First of all thx for your time. You are welcome! >And honestly, the places panel, the console panel, all have a close button. >I don't understand what's different about the split view? Well, actually by default none of them have a close button. There is the action "Un/Lock Panels" which decides whether those panels have an extra bar with a close button. By default, all of these bars are hidden and there is no visible close button for any of those panels. You can find the "Lock Panels" action in the menu bar in View->Show Panels or if you don't have a menu bar enabled in Open Menu->Show Panels. So we actually don't want to introduce extra bars by default only to have close buttons there. >In my opinion I do not like the idea. It > only shows more prominently that I am trying to do the wrong thing. So in > the end I still have to "refocus" - literally. > Hope this makes sense ... It does make sense. This is a bit of a question whether one values this specific issue more highly than the lost screen space by having an extra bar. I wouldn't want to add an extra bar that takes away from the main view, so that's why I came up with the idea of only showing what will happen on hover. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484961] Navigation through components using the TAB key does not work properly
https://bugs.kde.org/show_bug.cgi?id=484961 Felix Ernst changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/a4efbfb ||fa69f04ed21fe703a11bb59416e ||f8a821 Status|REPORTED|RESOLVED Version Fixed In||24.05 Resolution|--- |FIXED CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- Hello! I have already fixed the most basic problem of using Tab for the upcoming Dolphin release with https://invent.kde.org/system/dolphin/-/commit/a4efbfbfa69f04ed21fe703a11bb59416ef8a821. Now, one can just keep pressing Tab which will cycle through most components in Dolphin. I at least assume that this is what this bug report is about. Shift+Tab to move through components probably already works on your end. The order in which the Tab cycling happens can be a bit weird at times, especially when using the Split View feature, however I think it is at least usable now and I will consider this bug resolved. If you are unhappy about the way the Tab order works specifically even after upgrading the yet-to-be-released Dolphin 24.05 version, please open a new bug report which details which behaviour exactly is not working as expected. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484982] Show close button on split view
https://bugs.kde.org/show_bug.cgi?id=484982 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- Hi, we are aware of this problem. However, the solution I currently favour is that we would show a big red "X" spanning the whole view whenever the user hovers the mouse cursor over the "Close [Split View]" button. This way we wouldn't need extra space by default only to show a close button. Would an indicator on hover in your opinion also fix your problem? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484881] Right clicking on empty space in dolphin and scrolling creates selection box
https://bugs.kde.org/show_bug.cgi?id=484881 Felix Ernst changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/24268a4 ||df5d4fe0a856d17ca878d793527 ||a1188e --- Comment #3 from Felix Ernst --- Git commit 24268a4df5d4fe0a856d17ca878d793527a1188e by Felix Ernst, on behalf of Amol Godbole. Committed on 05/04/2024 at 13:47. Pushed by felixernst into branch 'master'. KItemListController: don't create rubber band for a right click in an empty region Rubber band was being incorrectly created for a right click in an empty region. Handle this case in KItemListController::onPress(). M +5-0src/kitemviews/kitemlistcontroller.cpp https://invent.kde.org/system/dolphin/-/commit/24268a4df5d4fe0a856d17ca878d793527a1188e -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482122] In split view the location bar of right side adds a drag-able separator in toolbar
https://bugs.kde.org/show_bug.cgi?id=482122 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #5 from Felix Ernst --- (In reply to Tammes Burghard from comment #4) > I honestly don't really care about it. Its not really discoverable, so I > never noticed it exists until this bug report. Now that I know about it, it > seems useful in very specific situations, so not removing it for these makes > sense I guess. But it also does not really matter, so if it adds maintenance > burden, it can be removed in my opinion. I think that's a fair assessment. It's not all that discoverable, so its usefulness is limited. If it ever becomes difficult to keep it, we shouldn't put too much work into keeping it. As it stands though, it would require more code to disable it than to simply keep it as is. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484414] highlight split panel borders when split view actived
https://bugs.kde.org/show_bug.cgi?id=484414 --- Comment #12 from Felix Ernst --- (In reply to Cherkah from comment #11) > Ok the debate is close, if indeed there was one ! > i was giving the " choice " to find a distinctive solution which takes into > consideration your internal rules / graphic charter and others. > > For example a small distinctive sign (point, dash, line, etc.) could have > been considered without coming into conflict with the color frame policy > already managed by the active theme. Yea, well I unfortunately don't see a way for us to improve this which wouldn't in turn lead to more problems elsewhere. > Or anything else ... It's up to you Maybe others have a different view on this or better ideas that wouldn't lead to problems elsewhere. > As kde plasma user, my duty was only to report relevant free software > bugs/weak points whose perfection is still in progress. Thanks for that! >regards regards -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484414] highlight split panel borders when split view actived
https://bugs.kde.org/show_bug.cgi?id=484414 --- Comment #10 from Felix Ernst --- A colour frame is typically also drawn by the theme. For example the colour frame that was used in Dolphin previously was also drawn by the Breeze theme. If we were to draw a colour frame regardless of the theme we might be working against the artistic goals the theme author tried to accomplish. I really think we shouldn't put it on ourselves to overwrite the visuals a theme provides. The theme itself should play by common rules, so it works nicely with our software. Of course this doesn't mean that it is always the theme author's fault if an application looks wrong. Maybe we wrote software in a way that themes can't really be expected to adapt to. I have no reason to think this is the reason in this case though. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455645] Tooltip frequently covers filenames when it appears
https://bugs.kde.org/show_bug.cgi?id=455645 --- Comment #13 from Felix Ernst --- (In reply to goo from comment #11) > Tooltips should […] appear only when hovering over > the filename and not on the whole row if that is feasable. I agree that this is the behaviour that should be implemented, and it is definitely feasible. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484414] highlight split panel borders when split view actived
https://bugs.kde.org/show_bug.cgi?id=484414 --- Comment #8 from Felix Ernst --- (In reply to Cherkah from comment #7) > But may i use on KDE plasma6 "ANY theme/third-party theme" that i want/need > and in same time do not lost some graphical features ? No, that is literally impossible. You are allowed to use any theme, including themes which use the same colour for everything. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484414] highlight split panel borders when split view actived
https://bugs.kde.org/show_bug.cgi?id=484414 Felix Ernst changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #6 from Felix Ernst --- (In reply to Cherkah from comment #5) > > Are you sure? ... If there really is no difference for you between the two > > see the pictures Indeed no difference. However, from the picture it is clear that Dolphin is definitely not using the default Breeze style. For example: In actual default Breeze the separator between the two views is only a 1 pixel thick line. See this picture for comparison: https://invent.kde.org/system/dolphin/uploads/2e616d5cfbf5297fa4d42781dc6df2c7/Screenshot_2024-03-26_002239.png Be aware that there is a difference between the Global Theme, the application style and the Plasma style, so even though your pictures show that you are using a Breeze global theme and a Breeze Plasma style, the application still seems to use a non-Breeze style for some reason. Since this bug seems to only happen with a third-party theme that is not part of KDE, it is somewhat likely that we can't fix this on our side. Please file a bug report for the third-party theme that you are using. They might be able to resolve this when we can't. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484411] increase tab width to window width
https://bugs.kde.org/show_bug.cgi?id=484411 --- Comment #3 from Felix Ernst --- >>there is a general discontent with the tab width we have not only >>in Dolphin but in KDE in general. AFAIK the consensus so far is that >>we generally want wider tabs, but we don't want them to span the >>whole width of the window because this has usability disadvantages >>(e.g. requires a lot of mouse movement to close multiple tabs in a row). >As far as I know, when the user/programmer community is split >over the usability of a feature, what's better than setting an option >to achieve "consensus" in the free software world (especially since >it is technically possible)? >Isn't that one of the distinctive elements between KDE with GNOME? > >so KDE programmers will have plenty of time to "THINK" about how >to bring users together around a new experience with the tab bar >"recurent issue". As I said: AFAIK there is a consensus that needs to be implemented. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #19 from Felix Ernst --- The situation of this bug has now been somewhat improved. We do no longer automatically put the vaults in Baloo's index as per commits.kde.org/baloo/373cf1e567e2580145f137176d440da27c319f06. However, as pointed out in other places in this bug report already, there are other less obvious ways how the content of the vault can still be available even after closing it. At least simply searching for the content using Baloo should no longer bring them up. However, even Baloo itself might still make contents of the vault available after it is closed. I'll quote Stefan Brüns' comment from https://invent.kde.org/frameworks/baloo/-/merge_requests/96#note_897708: > baloo_file gets information from various sources, inotify for file events, > process signals, events on file descriptors via Solid (e.g. mtab), events via > DBus from UDisks, etc. So it is quite common to e.g. get a "directory > changed" event for a mounted Vault, and some time later the > corresponding "Device/Filesystem added" added from Solid. > > This will then add data from the Vault to the index, and short time later > "discard" the information again, as it becomes excluded. Unfortunately, > the discard only invalidates the data from the index, but the data is still > there, in plain text (somewhat unstructured, but nevertheless). The user > may think everything is fine (no confidential data returned when > searching), but actually it is not. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 --- Comment #18 from Felix Ernst --- Git commit 373cf1e567e2580145f137176d440da27c319f06 by Felix Ernst, on behalf of Adam Fontenot. Committed on 29/03/2024 at 10:32. Pushed by felixernst into branch 'master'. Skip indexing KDE FS volumes unless user included In 69411a, we changed the indexer behavior so that removable media is not indexed by default. This commit tries to extend this behavior to any temporarily mounted file system. For instance, fuse.sshfs and overlay mounted file systems are managed in Solid under the /org/kde/fstab parent. Most likely, users will not want to index these file systems by default. This commit also changes the initialization procedure for StorageDevices. We now attempt to create a cached entry for *all* Solid devices when initializing. It makes sense to do this because `createCacheEntry` is already called whenever a device is added or removed, without any further filtering. Trying to precisely specify which devices to include at the initialization stage risks leaving out devices like the /org/kde/fstab devices that are the subject of this PR. Related: bug 460509 M +3-3src/file/storagedevices.cpp https://invent.kde.org/frameworks/baloo/-/commit/373cf1e567e2580145f137176d440da27c319f06 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 460509] Baloo indexes files temporarily mounted from other file systems
https://bugs.kde.org/show_bug.cgi?id=460509 Felix Ernst changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/baloo/-/commit/373cf ||1e567e2580145f137176d440da2 ||7c319f06 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #10 from Felix Ernst --- Git commit 373cf1e567e2580145f137176d440da27c319f06 by Felix Ernst, on behalf of Adam Fontenot. Committed on 29/03/2024 at 10:32. Pushed by felixernst into branch 'master'. Skip indexing KDE FS volumes unless user included In 69411a, we changed the indexer behavior so that removable media is not indexed by default. This commit tries to extend this behavior to any temporarily mounted file system. For instance, fuse.sshfs and overlay mounted file systems are managed in Solid under the /org/kde/fstab parent. Most likely, users will not want to index these file systems by default. This commit also changes the initialization procedure for StorageDevices. We now attempt to create a cached entry for *all* Solid devices when initializing. It makes sense to do this because `createCacheEntry` is already called whenever a device is added or removed, without any further filtering. Trying to precisely specify which devices to include at the initialization stage risks leaving out devices like the /org/kde/fstab devices that are the subject of this PR. Related: bug 390830 M +3-3src/file/storagedevices.cpp https://invent.kde.org/frameworks/baloo/-/commit/373cf1e567e2580145f137176d440da27c319f06 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482899] Dolphin can't write to folder with group write access
https://bugs.kde.org/show_bug.cgi?id=482899 Felix Ernst changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #9 from Felix Ernst --- Let's consider this fixed then. S. Christian Collins, Benjamin Xiao, Paul Worrall, if this bug still persists while using KDE frameworks 6.1 (which will be released by us on Fri April 13, 2024 and then arrive at your door step at a point in time controlled by your distribution), we would be interested in hearing from you. Good job everyone! :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482899] Dolphin can't write to folder with group write access
https://bugs.kde.org/show_bug.cgi?id=482899 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #7 from Felix Ernst --- I am not sure if this was now fixed by https://invent.kde.org/frameworks/kio/-/commit/8e622280d070df7824baffd684e866c085b56f64. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483797] Selected folders are black
https://bugs.kde.org/show_bug.cgi?id=483797 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #3 from Felix Ernst --- As the two attachments in this bug report show: The folders have the exact same colour as the selection rectangle, so if the folder didn't change colour the folders would become somewhat invisible. Would this be preferred? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483172] Free Disk Space button margin too wide and cuts off fonts
https://bugs.kde.org/show_bug.cgi?id=483172 Felix Ernst changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||felixer...@kde.org --- Comment #3 from Felix Ernst --- I changed this from a label to a button so it would become keyboard-accessible e.g. for visually- or motorically-impaired users. A button needs more space than a label unfortunately and especially themes which have very round buttons and further use margins within the buttons will need even more space. Making this menu accessible is prioritised over non-default theming, and I am not really familiar with the intricacies of button theming, so I personally currently don't know a good way to resolve this unfortunately. We most likely don't want to remove internal status bar margins (Is it possible to ignore internal margins just for the flat button perhaps?) or increase the status bar height. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484411] increase tab width to window width
https://bugs.kde.org/show_bug.cgi?id=484411 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- It is technically possible, but there is a general discontent with the tab width we have not only in Dolphin but in KDE in general. AFAIK the consensus so far is that we generally want wider tabs, but we don't want them to span the whole width of the window because this has usability disadvantages (e.g. requires a lot of mouse movement to close multiple tabs in a row). It would be better to generally improve the tab bar experience in KDE instead of adding more options. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484414] highlight split panel borders when split view actived
https://bugs.kde.org/show_bug.cgi?id=484414 Felix Ernst changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- >OBSERVED RESULT >impossible to identify the active one Are you sure? While it is true that we no longer show a bright blue border around the active view, we made sure that the background colour between the active and inactive view are wildly different. I actually find it way easier to identify which side is active because of this change. Previously the blue border was also shown for whichever view I hovered the mouse cursor over so both of the views had blue border which actually made it very difficult for me to guess which one is active. If there really is no difference for you between the two, there might be a bug elsewhere. Perhaps you are using a theme that doesn't has the same colour set for two roles which really should have distinct colours. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475805] Files with ending .bak are treated as if they were hidden.
https://bugs.kde.org/show_bug.cgi?id=475805 Felix Ernst changed: What|Removed |Added CC||junk.skun...@gmail.com --- Comment #18 from Felix Ernst --- *** Bug 484449 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484449] A file not visible (although not hidden)
https://bugs.kde.org/show_bug.cgi?id=484449 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Felix Ernst --- Thanks for the bug report! The file ending in .OLD is considered an application/x-trash backup file. For a while we thought it would be a good idea to hide this by default. A short while later this decision was reverted with https://invent.kde.org/system/dolphin/-/commit/9691afbc507ee480d4d129a6fff90b6b926aed62. I'll mark this as a duplicate of the other already resolved/fixed bug report. *** This bug has been marked as a duplicate of bug 475805 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461450] Get rid of italic text for links
https://bugs.kde.org/show_bug.cgi?id=461450 --- Comment #14 from Felix Ernst --- (In reply to Holmes from comment #12) > If youre not going to get rid of italic link fonts by default, then at least > give the user a plasma setting to do it themselves. > > I hate nano-ing or vim-ing plasma config files just to get rid of italic > fonts on both the desktop and dolphin! (In reply to mdcclxv from comment #13) > +1 here If I understand correctly, you two dislike italic text in general and want a general option to get rid of it. I am not sure how many users want this and if such an option is likely to be implemented. However, this is also not for me to decide. You might want to create another bug report for getting rid of italic text in general. Not sure if it would be filed against Plasma or against the font config. Either is probably fine. Comments on this resolved Dolphin bug report are somewhat unlikely to reach many Plasma contributors. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480243] Better UI for configuring information panel
https://bugs.kde.org/show_bug.cgi?id=480243 Felix Ernst changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/1d4355f ||619ca8098d12f330741017e417a ||756083 Version Fixed In||24.05 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Felix Ernst --- Git commit 1d4355f619ca8098d12f330741017e417a756083 by Felix Ernst, on behalf of Benedikt Thiemer. Committed on 15/03/2024 at 16:28. Pushed by felixernst into branch 'master'. Add settings page for Panels For now this just includes the settings for the information panel. Prior to this commit the options for configuring the information panel were only exposed via right clicking the information panel. This was not discoverable enough. Our guidelines also state that much. See: https://community.kde.org/Get_Involved/Design/Frequently_Discussed_Topics#Context_menus_are_not_enough The settings page is missing the "Configure" button for the entries in the information panel, which can only be found in the context menu. This is because I thought it would be weird to move it to the settings page. (The "configure" button is used to select the entries for the information panel) FIXED-IN: 24.05 M +7-1src/CMakeLists.txt M +1-0src/dolphinmainwindow.cpp M +8-0src/panels/information/informationpanel.cpp M +6-0src/panels/information/informationpanel.h M +16 -0src/settings/interface/interfacesettingspage.cpp A +105 -0src/settings/interface/panelsettingspage.cpp [License: GPL(v2.0+)] A +44 -0src/settings/interface/panelsettingspage.h [License: GPL(v2.0+)] https://invent.kde.org/system/dolphin/-/commit/1d4355f619ca8098d12f330741017e417a756083 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467752] Dolphin uses black text over black background when using the BreezeDark theme
https://bugs.kde.org/show_bug.cgi?id=467752 --- Comment #9 from Felix Ernst --- Dolphin doesn't read any theme itself. I haven't looked at how any of this works exactly, which is why I pointed you to the forums. AFAIK Qt itself uses the system platform and system styles. So this would be handled in Qt code and the Plasma platform code AFAIK. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 Felix Ernst changed: What|Removed |Added Assignee|matt...@mjdsystems.ca |konsole-de...@kde.org Product|frameworks-kconfig |konsole Version|5.249.0 |24.02.0 Component|general |keyboard --- Comment #11 from Felix Ernst --- I'll move this bug report from frameworks to Konsole because the keyboard shortcut should be changed for Konsole and not in frameworks. -- You are receiving this mail because: You are watching all bug changes.
