[frameworks-kio] [Bug 178678] Navigating mounted network locations is extremely slow in Dolphin compared to command line
https://bugs.kde.org/show_bug.cgi?id=178678 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445065] Dolphin freezes on "disk sleep" when browsing samba mount
https://bugs.kde.org/show_bug.cgi?id=445065 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 449814] Directory properties show empty volume information for btrfs file system
https://bugs.kde.org/show_bug.cgi?id=449814 Massimiliano L changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Massimiliano L --- This seems to be fixed, not sure since when. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492815] New: KDE panel freezes when a mounted NFS share becomes unavailable
https://bugs.kde.org/show_bug.cgi?id=492815 Bug ID: 492815 Summary: KDE panel freezes when a mounted NFS share becomes unavailable Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: m.lince...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When a NFS share is mounted, and Dolphin is open on that NFS share, if the NFS share suddenly becomes unavailable this results in the panel freezing. Also Dolphin freezes but that would be another (less serious) bug, unless the bug can be traced to an underlying component. STEPS TO REPRODUCE 1. Mount a NFS share (I have my NFS shares specified in fstab, but I use Dolphin to mount them) 2. Shutdown the NFS server 3. Try to interact with Dolphin / the panel, like clicking on the Dolphin icon in the panel. OBSERVED RESULT The panel freezes. EXPECTED RESULT The panel continues to work unaffected. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 490999] New: Improve usability of Export PDF dialog
https://bugs.kde.org/show_bug.cgi?id=490999 Bug ID: 490999 Summary: Improve usability of Export PDF dialog Classification: Applications Product: Skanpage Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: m.lince...@gmail.com Target Milestone: --- First let me mention that I appreciate quite a lot the design and overall usability of Skanpage. I would like however to make a couple (or maybe more) suggestions on how to improve the "Export PDF" dialog. The current issues are: 1. right now, one is expected to edit both the title and the filename to make the document unique; 2. directory path and filename are edited using a single box, while in general one saves multiple documents on the same directory (i.e. the directory mostly changes once per session, the filename changes always); 3. the `file://` prefix is redundant and confusing. Possible solutions / proposals: 1. by default, derive the filename from the title, so that editing the title is sufficient to create a custom filename; 1a. yet, allow to edit the filename manually, maybe there could be an "auto" mode where the filename is derived from the title and "greyed out", plus an option to make it editable. 2. make directory and filename two separate boxes (I guess this could go well together with 1a); 3. either (i) use a drop down menu with the supported protocols, defaulting to `file://`, or (ii) hide the protocol when, and only when, it's `file://`. I hope these suggestions can be helpful and thank you in advance for taking them (potentially) in consideration. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 464503] Have an option to select image compression
https://bugs.kde.org/show_bug.cgi?id=464503 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com --- Comment #3 from Massimiliano L --- (In reply to Alexander Stippich from comment #2) > Unfortunately, Qt does currently not offer support for selecting the image > compression when writing to PDFs. So it is not easy to implement as far as I > know. Would it be possible to call some ghostscript command after writing the PDF to file, immediately overwriting it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489296] Application Launcher breaks and shows as empty panel
https://bugs.kde.org/show_bug.cgi?id=489296 --- Comment #7 from Massimiliano L --- (In reply to Nate Graham from comment #6) > Darn. Can you attach journal logs from around the time it happened? > > If you can reproduce it at will, then do the following: run `plasmashell > --replace` in a terminal window, reproduce the issue, and then copy-paste > all the text in the terminal window into a comment here. > > Thanks! Hi Nate, thanks for the follow up. The occurrence is rare enough, so it's hard for it to appear within the same boot session. Also I haven't experienced it since I stopped using the external dock and started using the HDMI out of my laptop (see also #489367 for problems I had with the dock and external displays). If the issue does not reappear in my current setup I think we can archive this for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications.
https://bugs.kde.org/show_bug.cgi?id=487780 Massimiliano Torromeo changed: What|Removed |Added CC||massimiliano.torromeo@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489367] Connecting USB-C dock with external displays fails to activate them and gives a black screen
https://bugs.kde.org/show_bug.cgi?id=489367 --- Comment #4 from Massimiliano L --- (In reply to Zamundaaa from comment #2) > Please attach the kwin log > > journalctl --user-unit plasma-kwin_wayland --boot 0 > and the output of drm_info > - without the dock connected > - with it connected and working > - with it connected and not working Hi and thanks for the feedback. Unfortunately, the USB-C port of my laptop is failing so I need to wait for a new one in order to properly test this. If the bug gets closed, I can reopen it whenever I have new information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489296] Application Launcher breaks and shows as empty panel
https://bugs.kde.org/show_bug.cgi?id=489296 Massimiliano L changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489296] Application Launcher breaks and shows as empty panel
https://bugs.kde.org/show_bug.cgi?id=489296 --- Comment #4 from Massimiliano L --- (In reply to Massimiliano L from comment #3) > (In reply to Nate Graham from comment #2) > > I had that thought as well. > > > > If you move aside (don't delete) ~/.cache/plasmashell/qmlcache/ and then > > restart the system, does the issue stop happening? No, the issue reproduces even after moving aside the qmlcache. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489362] After resuming from suspend (close/open lid) sometimes the touchpad requires two fingers to work
https://bugs.kde.org/show_bug.cgi?id=489362 --- Comment #2 from Massimiliano L --- (In reply to Zamundaaa from comment #1) > Please report this at > https://gitlab.freedesktop.org/libinput/libinput/-/issues Thank you for the pointer. It seems it is indeed a known libinput issue, but apparently hard to debug for devs: https://gitlab.freedesktop.org/libinput/libinput/-/issues/712 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489296] Application Launcher breaks and shows as empty panel
https://bugs.kde.org/show_bug.cgi?id=489296 --- Comment #3 from Massimiliano L --- (In reply to Nate Graham from comment #2) > I had that thought as well. > > If you move aside (don't delete) ~/.cache/plasmashell/qmlcache/ and then > restart the system, does the issue stop happening? I will try and report back! Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489367] Connecting USB-C dock with external displays fails to activate them and gives a black screen
https://bugs.kde.org/show_bug.cgi?id=489367 --- Comment #1 from Massimiliano L --- P.S.: about the attached logs I should mention that, upon reconnecting the dock, the external displays reactivated but one of the two displays started at low resolution (640x480) and was not reachable with the mouse pointer (Display Configuration would show it as "detached" from the main display). Usually when the disconnect-reconnect iteration succeeds in activating the displays, those respect the configuration I had previously set. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489367] New: Connecting USB-C dock with external displays fails to activate them and gives a black screen
https://bugs.kde.org/show_bug.cgi?id=489367 Bug ID: 489367 Summary: Connecting USB-C dock with external displays fails to activate them and gives a black screen Classification: Plasma Product: kwin Version: 6.1.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m.lince...@gmail.com Target Milestone: --- Created attachment 171125 --> https://bugs.kde.org/attachment.cgi?id=171125&action=edit Log from the crash SUMMARY Sometimes (more often than not) when connecting a USB-C dock with two external displays, the two displays fail to activate. Whether the issue occurs seems totally random. Sometimes disconnecting and reconnecting the dock fixes the issue, sometimes multiple iterations are required. Sometimes restarting the system and/or plasmashell seems to help (but this is anectodal could still be random). STEPS TO REPRODUCE 1. Connect USB-C dock with external displays 2. Configure display setup in "Display Configuration". In my case, the laptop screen is set to deactivated when the external displays are connected. 3. Work normally. 4. Disconnect dock and move on with your life. 5. Get back to work and connect the USB-C dock. OBSERVED RESULT Laptop display deactivates, but external display do not activate and stay black. EXPECTED RESULT External displays activate regularly upon connection. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Latitude 7490 ADDITIONAL INFORMATION A system log is attached. This was taken on a fresh boot. At the first connection of the USB-C dock, the displays failed to activate. Disconnecting and reconnecting the dock fixed the issue at the first try. All this is captured in the log. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489362] New: After resuming from suspend (close/open lid) sometimes the touchpad requires two fingers to work
https://bugs.kde.org/show_bug.cgi?id=489362 Bug ID: 489362 Summary: After resuming from suspend (close/open lid) sometimes the touchpad requires two fingers to work Classification: Plasma Product: kwin Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: m.lince...@gmail.com Target Milestone: --- SUMMARY When resuming work on my laptop after sleep / closing the lid, sometimes the touchpad is unrensponsive and requires two fingers to move the pointer. STEPS TO REPRODUCE 1. Work with your laptop normally 2. Close the lid 3. Open the lid 4. Go through 1-2-3 a few times until the problem appears. OBSERVED RESULT The touchpad does not respond to the usual one-finger operation, while using two fingers can move the cursor. EXPECTED RESULT The touchpad works normally. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Latitude 7490 ADDITIONAL INFORMATION I observed this behaviour on the GNOME Session as well, but I never experienced on Plasma X11. This could point to an upstream issue (Wayland). Switching to a virtual terminal and then back to the desktop fixes the issue. Similar issues have been reported in the past 2+ years across several platforms: https://askubuntu.com/questions/1387034/touchpad-starts-requiring-2-fingers-way-to-fix -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489296] New: Application Launcher breaks and shows as empty panel
https://bugs.kde.org/show_bug.cgi?id=489296 Bug ID: 489296 Summary: Application Launcher breaks and shows as empty panel Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: m.lince...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY The Application Launcher randomly breaks and start showing an empty pane upon opening, however no crash is reported by Plasma. Restarting plasmashell (`plasmashell --replace`) fixes the issue. I am using a multi-monitor setup, but I am not sure if this is a requirement for the bug to appear. STEPS TO REPRODUCE 1. Use Plasma for a while 2. Click on the launcher button 3. Observe the Application Launcher OBSERVED RESULT Application Launcher shows a totally empty panel (no menu, no search, no power buttons). EXPECTED RESULT Application Launcher works normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 with KDE Plasma on Wayland KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 488199] Discover app search stuck on "Still looking..."
https://bugs.kde.org/show_bug.cgi?id=488199 --- Comment #2 from Massimiliano L --- (In reply to Nate Graham from comment #1) > The issue of the busy indicator being misplaced is Bug 488267. As for the > functional issue, does it *ever* find anything? Like, after, say, 30 > minutes? Or is it still stuck at that point? > > If so, does the issue reproduce in a new clean user account on the same > machine? > > If so, does the issue reproduce in a live session of Fedora 40, like from > the same USB flash drive you used to install it? I can reproduce the issue on both my installations, a desktop and a laptop. A newly created user is equally affected. I will try with a live session over the weekend. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 --- Comment #10 from Massimiliano L --- (In reply to Mike from comment #9) > Yeah, please do. I see in the log where the crash happened and that code > has changed, though I'm not really sure if that's the cause. Either way, I > am unable to reproduce the crash on 6.0.5, 6.1 or master. Fedora 40 KDE VM > is hosed too so I'll have a look in a few days. > > Meantime, any way you can test with 6.1 with Fedora? I need to wait for Fedora to ship 6.1, it should not take long. As soon as that happens, I will try to reproduce the bug and follow up with a new report. Thank you again! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 --- Comment #8 from Massimiliano L --- (In reply to Mike from comment #7) > Git commit 90f3daa4fb814bbc9222b6b68d6ee3e896da94ae by Mike Noe. > Committed on 11/06/2024 at 19:42. > Pushed by noee into branch 'master'. > > kcm/[core,qml]: Cleanup Manual Config/Remote printer search > > qml: Add contextual help for the manual config options. For printer host > search, don't populate list with "local" printers. Also, handle CUPS > results and errors for remote printer search. > > core: Don't emit remotePrintersLoaded if there is a CUPS error > FIXED-IN: 6.2 > > M +1-2src/kcm/printermanager.cpp > M +20 -13 src/kcm/ui/components/ManualUri.qml > > https://invent.kde.org/plasma/print-manager/-/commit/ > 90f3daa4fb814bbc9222b6b68d6ee3e896da94ae Thank you for following-up so quickly, this kind of UI improvements is very much appreciated! Should I open a new bug for the crashing issues or was this addressed in the further commits? -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 488354] New: "Enable" and "Turn Off" buttons should act on selected entries only
https://bugs.kde.org/show_bug.cgi?id=488354 Bug ID: 488354 Summary: "Enable" and "Turn Off" buttons should act on selected entries only Classification: Applications Product: kdebugsettings Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: mon...@kde.org Reporter: m.lince...@gmail.com Target Milestone: --- SUMMARY When selecting one of multiple entries in the KDebugSettings / KDE Application tab, the enable and turn off buttons always act on all the entries returned by the search field, regardless of which entries have been selected. This behaviour goes against what I think is be a normal user's expectation (in case it's intentional, I can elaborate more on why I think is a questionable UI choice). STEPS TO REPRODUCE 1. Open KDebugSettings 2. Select one or more entries 3. Click on "Enable All Debug" or "Turn Off All Messages" OBSERVED RESULT All the entries matching the search are toggled. Selection is irrelevant. EXPECTED RESULT Only the selected entries are toggled. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 --- Comment #6 from Massimiliano L --- Created attachment 170369 --> https://bugs.kde.org/attachment.cgi?id=170369&action=edit Systemsettings crash seen from journalctl Thank you for the help! Here is a log of the crash, actually two in a sequence (triggered by the same sequence of operations). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 488199] New: Discover app search stuck on "Still looking..."
https://bugs.kde.org/show_bug.cgi?id=488199 Bug ID: 488199 Summary: Discover app search stuck on "Still looking..." Classification: Applications Product: Discover Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: m.lince...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When searching for an app, Discover is stuck at "Still looking..." with the spinning gear. STEPS TO REPRODUCE 1. Open Discover; 2. Search for an app (i.e. "KleverNotes") using the text field up on the left; 3. Observe Discover behaviour. OBSERVED RESULT Discover search is stuck at "Still looking..." with the spinning gear for an apparently indefinite amount of time. EXPECTED RESULT Discover search returns something, or at least tells you what it is currently doing / waiting on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 Linux/KDE: Fedora 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 488198] "Still looking..." message and spinning gear overlap when searching for an app
https://bugs.kde.org/show_bug.cgi?id=488198 Massimiliano L changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 488198] New: "Still looking..." message and spinning gear overlap when searching for an app
https://bugs.kde.org/show_bug.cgi?id=488198 Bug ID: 488198 Summary: "Still looking..." message and spinning gear overlap when searching for an app Classification: Applications Product: Discover Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: m.lince...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 170263 --> https://bugs.kde.org/attachment.cgi?id=170263&action=edit Overlapping text and graphics in Discover SUMMARY When searching for an app in Discover, the "Still looking..." message overlaps with the spinning gear and is partially obscured by it. STEPS TO REPRODUCE 1. Open Discover 2. Search for an application using the top left text field 3. Observe Discover's behaviour OBSERVED RESULT The "Still looking..." message appears and overlaps with a spinning wheel. EXPECTED RESULT Message and graphics do not overlap. SOFTWARE/OS VERSIONS Linux/KDE: Fedora 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION - I am using 150% fractional scaling. - Similar to bug 485379 but that was filed against Plasma 5.x and is probably superseded. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 --- Comment #4 from Massimiliano L --- (In reply to Mike from comment #3) > What is strange, however, is that you are not forced to authenticate when > you choose "Add Printer". Are you running as root or some other elevated > user? This could also explain crashes in System Settings. No, it's a pretty standard Fedora 40 installation. I observe the same behaviour on my other machine, same OS. I wonder if there is some magic (polkit?) going on behind the curtains. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 --- Comment #2 from Massimiliano L --- Thank you for the quick feedback! (In reply to Mike from comment #1) > When you select Add Printer, are you prompted to authenticate? No, I am not prompted for authentication. > Also, do you > have the package system-config-printer installed? I did not, now I have. But it seems to only provide an additional GUI for the same CUPS backend? > Can you post the output from the command: `lpinfo -v` (You may have to > elevate privileges) I get the following list: - file cups-brf:/ network beh network ipp network https network ipps network http direct hp network socket network lpd network smb direct hpfax - With or without sudo (only the order is different). > Note: The search button on "Manual Config" asks CUPS for printers at the > host address. If you know the printer address, you just type it in and > choose "Continue". If the address is just a scheme, CUPS returns local > printers by default, which we should probably ignore as it is bit confusing. OK, now I better understand how this works. I think part of the confusion arises from the fact that the "address" for CUPS can either be an individual networked printer o a CUPS host. The scroll menu with the search result appears only if something is returned, giving the impression that otherwise the "search button" is doing nothing. I think right now I can only add printers through another CUPS server and not directly as network printers, though. Note: I find a bit confusing to have "select printer" and "continue with address" above the address field / printer list, instead of below. > As far as the crashing, this is something unusual. You can turn on > debugging for the printer manager in KDebugSettings. Search "print" and > enable Full Debug for kcm and libkcups. You can than watch the log in a > terminal with `journalctl --user -f` to help narrow down what is crashing. I will as soon as I have the time to look again into this! In the meantime (now that I figured out how this window is supposed to work) I would classify this as UI/UX improvement rather than a bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488097] New: Search button of "Set up a Printer Connection" wizard misbehaves
https://bugs.kde.org/show_bug.cgi?id=488097 Bug ID: 488097 Summary: Search button of "Set up a Printer Connection" wizard misbehaves Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: plasma-b...@kde.org Reporter: m.lince...@gmail.com CC: noeero...@gmail.com Target Milestone: --- SUMMARY When using the "Add Printer" wizard from the system settings "Printers", the user is prompted to insert a printer's address. Near the "Address" field, there is a search button. Pressing such button seems not to produce any action in most cases. STEPS TO REPRODUCE 1. Open system settings -> Printer 2. Click on Add Printer 3. Wait for the "Unable to automatically discover any printing devices" 3. Insert a printer address (or not) and press the search button. OBSERVED RESULT Nothing happens. But if the address is set to "ipp://" or some other "prefix://" the search returns the existing configured printers, even if they don't appear to match the search criterion. EXPECTED RESULT Pressing the search button returns some kind of answer if nothing is found. Likewise, it should not return printers that do not match the search button. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION - oddly, the "Add Printer" feature opens a pop-up window, while the "Add Group" and "Configure Print Server" features just "slide" the current system settings panel to the wizard; - the wizard crashes very frequently, I will issue another bug if I can get useful crash reports. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 383366] Do not display first run download manager integration with Konqueror if it's not installed
https://bugs.kde.org/show_bug.cgi?id=383366 Massimiliano L changed: What|Removed |Added Version|unspecified |24.02.2 CC||m.lince...@gmail.com Platform|Netrunner |unspecified -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 482733] yakuake remembers last screen resolution, have to open twice to get correct size
https://bugs.kde.org/show_bug.cgi?id=482733 --- Comment #2 from Massimiliano Torromeo --- The same problem happens vertically on a second monitor that has the same resolution but rotated so that 1920px is the height of one monitor and the other is 1080px -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 482733] yakuake remembers last screen resolution, have to open twice to get correct size
https://bugs.kde.org/show_bug.cgi?id=482733 Massimiliano Torromeo changed: What|Removed |Added CC||massimiliano.torromeo@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 483324] Splitting views doesn't put focus on the new view
https://bugs.kde.org/show_bug.cgi?id=483324 --- Comment #2 from Massimiliano Torromeo --- I noticed something else in regard to the keybindings workaround that I mentioned earlier. Only if the focus is on the first split view I can access the "konsolepart" keybindings in the shortcut settings, otherwise I can only see the "Yakuake" bindings. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 483324] Splitting views doesn't put focus on the new view
https://bugs.kde.org/show_bug.cgi?id=483324 --- Comment #1 from Massimiliano Torromeo --- I just noticed that in the shortcut settings, there are duplicate actions for split view. There are 2 actions (vertical/horizontal) for the konsolepart component with no keybinds by default, and 2 similar actions (the ones this report is about) in the yakuake section. If I bind keys to the konsolepart actions I can work around this issue and the focus is moved properly to the new views, but the split behaves a little differently and creates a new header/toolbar on top of the views (which I don't mind much). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 483324] New: Splitting views doesn't put focus on the new view
https://bugs.kde.org/show_bug.cgi?id=483324
Bug ID: 483324
Summary: Splitting views doesn't put focus on the new view
Classification: Applications
Product: yakuake
Version: 24.02.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: h...@kde.org
Reporter: massimiliano.torro...@gmail.com
Target Milestone: ---
When using the split view top/bottom or left/right the cursor does not focus
the new view anymore like it used to do in previous versions.
The behavior is also inconsistent based on where the focus is when the split
view action is invoked:
- if the focus is on the first view, the focus does not change and is still on
the first view after the split
- if the focus is on any other view, yakuake loses focus entirely
STEPS TO REPRODUCE
1. open yakuake
2. split view with "CTRL+(" or "CTRL+)"
OBSERVED RESULT
The focus remains on the first view.
EXPECTED RESULT
The focus should change to the new view on the right or bottom of the first
one.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.1 (yakuake reports 6.0.0, but every KDE package is
at version 6.0.1)
Qt Version: 6.6.2
--
You are receiving this mail because:
You are watching all bug changes.
[kontact] [Bug 481618] New: KMail crashes when adding HTML signature
https://bugs.kde.org/show_bug.cgi?id=481618 Bug ID: 481618 Summary: KMail crashes when adding HTML signature Classification: Applications Product: kontact Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: leoni.massimilia...@gmail.com Target Milestone: --- Application: kontact (5.24.4 (23.08.4)) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-18-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: When adding a signature in the identity manager, Signature -> Enable signature -> Input Field -> Use HTML -> Insert HTML -> pasting the text Insert -> OK causes KMail to segfault. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f4797265899 in richtextBorderStyleToHtmlBorderStyle (style=4294967295) at text/qtextdocument.cpp:2642 #5 0x7f47972736d7 in QTextHtmlExporter::emitTable (this=this@entry=0x7ffe8f83a010, table=0x55e3735eee20) at text/qtextdocument.cpp:3273 #6 0x7f4797272887 in QTextHtmlExporter::emitFrame (this=this@entry=0x7ffe8f83a010, frameIt=...) at text/qtextdocument.cpp:3315 #7 0x7f479727462f in QTextHtmlExporter::toHtml (this=this@entry=0x7ffe8f83a010, encoding=..., mode=mode@entry=QTextHtmlExporter::ExportEntireDocument) at text/qtextdocument.cpp:2401 #8 0x7f4797274ac2 in QTextDocument::toHtml (this=0x55e372b2ab60, encoding=...) at text/qtextdocument.cpp:3413 #9 0x7f4797b6e68e in QWidgetTextControl::toHtml() const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f4797b434db in QTextEdit::toHtml() const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f474d620155 in KIdentityManagement::SignatureConfigurator::signature() const () from /lib/x86_64-linux-gnu/libKPim5IdentityManagementWidgets.so.5 #12 0x7f4704b4f02e in ?? () from /lib/x86_64-linux-gnu/libkmailprivate.so.5 #13 0x7f4704b56ebd in KMail::IdentityPage::slotModifyIdentity() () from /lib/x86_64-linux-gnu/libkmailprivate.so.5 #14 0x7f4796cf4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f4797c69d34 in QTreeWidget::itemDoubleClicked(QTreeWidgetItem*, int) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f4796cf4de8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f4797be5d29 in QAbstractItemView::doubleClicked(QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f4797c6439b in QTreeView::mouseDoubleClickEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f47979b0309 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f4797a5ddc2 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f4796cbd06a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f479796c772 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f47979743c4 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f4796cbd30a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f4797972ea7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f47979c91fb in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f47979cc555 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f479796c783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f4796cbd30a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f4797143368 in QGuiApplicationPrivate::processMouseEvent (e=0x55e370a79d50) at kernel/qguiapplication.cpp:2322 #31 0x7f4797116dbc in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #32 0x7f47876f4f5e in xcbSourceDispatch (source=) at ./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105 #33 0x7f478ce51d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7f478cea7258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7f478ce4f3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f4796d167f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib
[konsole] [Bug 480884] Konsole terminates when a program launched by it runs out of memory (oom-kill)
https://bugs.kde.org/show_bug.cgi?id=480884 --- Comment #5 from Massimiliano L --- (In reply to fanzhuyifan from comment #4) > In general, the advice is to *not* operate your system in settings that > frequently trigger the OOM killer. > There are several ways to do that: > - limiting the ram of memory-hungry processes (e.g., using systemd, or > options to jvm) > - use swap (zram offers a way to put swap inside ram, and you could always > configure swap on harddrives) > - upgrade your hardware The use case here is Konsole being used for development and debug. The large memory consumption would then be unintentional, either because the amount of required memory was miscalculated or because there is a memory leak in the program. But if the terminal gets killed, the stdout is lost and debugging gets more complicated. Of course logging to a file or limiting the memory available to the python interpreter would be valid alternatives. > If you must operate near regimes that saturate the memory, my suggestion is > to custom configure an OOM killer, so you get more control over what is > killed in OOM situations. > > The systemd and kernel OOM killers both use some sort of heuristics to > decide which application to kill first. It is very hard for us to guarantee > that konsole is not killed first -- in some cases, it might even be > desirable to kill konsole first if more critical applications can continue. It might be desirable to kill Konsole if Konsole was responsible for the memory consumption by itself and not because of a child process, but I get the point. Your comment clarifies the situation enough for me. Thank you again for the support. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480884] Konsole terminates when a program launched by it runs out of memory (oom-kill)
https://bugs.kde.org/show_bug.cgi?id=480884 --- Comment #2 from Massimiliano L --- (In reply to fanzhuyifan from comment #1) > Unfortunately KDE software is not responsible for deciding which process to > kill during out of memory events. Usually it is either the kernel OOM > killer, and the systemd OOM killer, and we have no control over how these > behave. If you find the current OOM killer unsatisfactory, you could try > customizing those or using alternate OOM killers like > https://github.com/rfjakob/earlyoom. Thank you for the answer. But this occurs systematically and does not occur with GNOME Terminal. So there should be something in the design or behavior of Konsole that triggers the OOM killer to terminate it together with the child process. Any ideas on why this may be? If this is "not a bug" can we turn this into a wishlist item? I believe it can significantly impact the user experience in some cases, putting Konsole (and KDE software) behind competitors. It could be also interesting to understand whether this is distro-related. If people not using Fedora are not experiencing the same issue, I may file a bug report with Fedora as well. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 480904] New: Import and export of annotations settings
https://bugs.kde.org/show_bug.cgi?id=480904
Bug ID: 480904
Summary: Import and export of annotations settings
Classification: Applications
Product: okular
Version: 23.08.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: m.lince...@gmail.com
Target Milestone: ---
Okular allows to customise annotation settings ("Configure Annotations"), but
there seems to be no easy way to share these to another installation.
Typically, one would like to keep their annotation style consistent across
multiple devices and doing this manually requires some work (especially
fine-tuning the colors).
It could be nice to have a feature to import and export annotation settings
from Okular.
As a partial replacement for this feature, the Okular manual could include
information about where these settings are stored.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 480901] New: "Configure Okular" window under "Settings" menu is slow to open
https://bugs.kde.org/show_bug.cgi?id=480901 Bug ID: 480901 Summary: "Configure Okular" window under "Settings" menu is slow to open Classification: Applications Product: okular Version: 23.08.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: m.lince...@gmail.com Target Milestone: --- SUMMARY The "Configure Okular..." window accessible from the "Settings" menu takes in the order of seconds to open. Same happens when accessing it through other buttons, such as "Configure Annotations". This is observed on a fairly well-powered desktop PC with loads of free RAM. STEPS TO REPRODUCE 1. open Okular 2. click on Settings -> "Configure Okular..." OBSERVED RESULT About 3+ seconds of Okular not doing anything before the configuration window shows. EXPECTED RESULT Opening of configuration window should be almost instantaneous. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 39 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480884] New: Konsole terminates when a program launched by it runs out of memory (oom-kill)
https://bugs.kde.org/show_bug.cgi?id=480884 Bug ID: 480884 Summary: Konsole terminates when a program launched by it runs out of memory (oom-kill) Classification: Applications Product: konsole Version: 23.08.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: m.lince...@gmail.com Target Milestone: --- SUMMARY When launching a program from Konsole and the program runs out of memory, Konsole terminates as well. Here is an extract from kernel logs: [ 4798.852688] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-0b1078c44601481893367fffe01d53f3.scope,task=python,pid=33408,uid=1000 [ 4798.852755] Out of memory: Killed process 33408 (python) total-vm:40125280kB, anon-rss:24510464kB, file-rss:4604kB, shmem-rss:0kB, UID:1000 pgtables:60432kB oom_score_adj:200 STEPS TO REPRODUCE 1. launch a memory-eater program; 2. wait until it fills the entire RAM and is killed by the kernel. OBSERVED RESULT The Konsole window disappears. EXPECTED RESULT The Konsole window should stay open, and report that the program has been terminated because of an OOM. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 39 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION The same behaviour is shown by Yakuake. On the other hand GNOME Terminal survives the killing of the process. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476833] folder view in a panel
https://bugs.kde.org/show_bug.cgi?id=476833 --- Comment #6 from Massimiliano Agosti --- I changed the graphic card for other reasons and this solved the problem. 😮 Il 16/11/23 00:17, Massimiliano Agosti Outlook ha scritto: > > Shortcuts are working correctly from Dolphin . I copied the shorcut on > the Desktop; it works. > > It's Folder View widgets that does not work properly anymore since a > recent update (from Backports ppa I presume). I personalized the > default icon of folders; I still see it in Dolphin but no more in > Folder View widget where it's shown like the classic Brezza one. > > Il 15/11/23 23:58, Nate Graham ha scritto: >> https://bugs.kde.org/show_bug.cgi?id=476833 >> >> --- Comment #3 from Nate Graham --- >> Can you try giving them execute permissions and see if that helps? >> >> If you move the shortcuts to the desktop (the actual desktop, as in navigate >> to >> "desktop://" in Dolphin) and then open them, does it work? >> -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476833] folder view in a panel
https://bugs.kde.org/show_bug.cgi?id=476833 --- Comment #4 from Massimiliano Agosti --- Shortcuts are working correctly from Dolphin . I copied the shorcut on the Desktop; it works. It's Folder View widgets that does not work properly anymore since a recent update (from Backports ppa I presume). I personalized the default icon of folders; I still see it in Dolphin but no more in Folder View widget where it's shown like the classic Brezza one. Il 15/11/23 23:58, Nate Graham ha scritto: > https://bugs.kde.org/show_bug.cgi?id=476833 > > --- Comment #3 from Nate Graham --- > Can you try giving them execute permissions and see if that helps? > > If you move the shortcuts to the desktop (the actual desktop, as in navigate > to > "desktop://" in Dolphin) and then open them, does it work? > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476833] folder view in a panel
https://bugs.kde.org/show_bug.cgi?id=476833 --- Comment #2 from Massimiliano Agosti --- You added .desktop file shortcuts to apps and put them in a folder, and added a Folder View widget to your panel and configured it to show that folder*_YES_*, and now when you open the folder and click on the shortcuts, the app doesn't open*_YES_* and instead the file opens in a text editor app?*_NO_. When I click on the shortcuts nothing happens*. *I tried a Folder View widget placed on Desktop pointing to a folder containing .pdf files; clicking on them do not have any effect. I can open the files only by choosing the program (Okular) from the menu that appears doing richt click on the mouse.* *Thank you for your help* Il 15/11/23 21:05, Nate Graham ha scritto: > https://bugs.kde.org/show_bug.cgi?id=476833 > > Nate Graham changed: > > What|Removed |Added > > CC||n...@kde.org > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham --- > Let me see if I understand this. > > You added .desktop file shortcuts to apps and put them in a folder, and added > a > Folder View widget to your panel and configured it to show that folder, and > now > when you open the folder and click on the shortcuts, the app doesn't open and > instead the file opens in a text editor app? > > If I have that right, can you try giving the files execute permissions and see > if that helps? > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476833] New: folder view in a panel
https://bugs.kde.org/show_bug.cgi?id=476833 Bug ID: 476833 Summary: folder view in a panel Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: massimiliano.ago...@outlook.it CC: h...@kde.org Target Milestone: 1.0 Created attachment 163041 --> https://bugs.kde.org/attachment.cgi?id=163041&action=edit Screenshot folder view SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Can't start anymore any application in a folder from folder view in a panel -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 474242] Duplicate item in Places / "Remote" for fstab-mounted NFS drive
https://bugs.kde.org/show_bug.cgi?id=474242 --- Comment #7 from Massimiliano L --- (In reply to Méven Car from comment #5) > I am guessing the issue would be fixed if you updated your fstab line to : > > From > `nas.local:export/foo /media/net-foo nfs defaults,nofail 0 0` > > To > `nas.local:/export/foo /media/net-foo nfs defaults,nofail 0 0` > > (note the added slash) Yes, thank you. I had figured this out when checking the bug report for the trailing `/` case. It makes sense to have a full absolute path after `:` but apparently fstab does not care. Thank you for working on this! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 474242] Duplicate item in Places / "Remote" for fstab-mounted NFS drive
https://bugs.kde.org/show_bug.cgi?id=474242 --- Comment #4 from Massimiliano L --- (In reply to Méven Car from comment #3) > Can you share your fstab file (or at least all the nfs lines) ? The fstab entry is as follows: > nas.local:export/foo /media/net-foo nfs defaults,nofail 0 0 The content of `$HOME/.local/share/user-places.xbel` seems to hold a lot of out-of-date entries (is this a bug as well?). Since I have changed my configuration a few times I am not sure how to find the "corresponding" bookmark, but I guess it is this one: > > > http://www.kde.org";> >/org/kde/fstab/nas.local:export/foo:/media/net-foo >true >true > > > And here is the output from solid-hardware5 list for the concerned mount: > udi = '/org/kde/fstab/nas.local:/export/foo:/media/net-foo' > udi = '/org/kde/fstab/nas.local:export/foo:/media/net-foo' -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 474242] Duplicate item in Places / "Remote" for fstab-mounted NFS drive
https://bugs.kde.org/show_bug.cgi?id=474242 --- Comment #1 from Massimiliano L --- Extending the fix to bug 406242 would be a bit inelegant as one would need to test 4 combinations of (non) leading / (non) trailing slashes. Could we assume that 'mtab' device name will always have the same style (leading slash without trailing slash) and convert the fstab string to that style, before testing with 'contains'? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 474242] New: Duplicate item in Places / "Remote" for fstab-mounted NFS drive
https://bugs.kde.org/show_bug.cgi?id=474242 Bug ID: 474242 Summary: Duplicate item in Places / "Remote" for fstab-mounted NFS drive Classification: Frameworks and Libraries Product: frameworks-solid Version: 5.109.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m.lince...@gmail.com CC: kdelibs-b...@kde.org, lu...@kde.org Target Milestone: --- SUMMARY Having NFS shares mounted via fstab may in duplicate items under "Remote" places. This seems similar to bug 406242 except it occurs when the path on the NFS server does not start with a '/'. STEPS TO REPRODUCE 1. add NFS share mount to fstab in the form `nas.local:export/foo /media/net-foo nfs defaults,nofail 0 0` 2. systemctl daemon-reload && mount -a 3. open Dolphin OBSERVED RESULT The share appears twice with the same name. One with the mounted and one with the unmounted icon. EXPECTED RESULT Share should appear only once. SOFTWARE/OS VERSIONS Linux: Fedora (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files) for local filesystem
https://bugs.kde.org/show_bug.cgi?id=387663 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 428854] Nightcolor fails to activate after KWin or the whole session is restarted; must manually toggle it off and on again
https://bugs.kde.org/show_bug.cgi?id=428854 Massimiliano L changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #22 from Massimiliano L --- It seems this report was automatically closed (?) but the bug is still present in KDE 5.27.6. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 469108] Two sidebar shortcuts, one of which doesn't work
https://bugs.kde.org/show_bug.cgi?id=469108 --- Comment #2 from Massimiliano --- Sorry about the duplicate! I did search but I couldn't find the original. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 469108] New: Two sidebar shortcuts, one of which doesn't work
https://bugs.kde.org/show_bug.cgi?id=469108 Bug ID: 469108 Summary: Two sidebar shortcuts, one of which doesn't work Classification: Applications Product: okular Version: 23.04.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: leoni.massimilia...@gmail.com Target Milestone: --- Created attachment 158518 --> https://bugs.kde.org/attachment.cgi?id=158518&action=edit Visual example SUMMARY The Configure Shortcuts dialogue has two entries for "Show Sidebar", one of which doesn't work STEPS TO REPRODUCE 1. Open Configure Shortcuts dialogue 2. Type "Sidebar" 3. Observe two "Show Sidebar" entries 4. Only one of the two actually works OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon 5.27 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457228] New: Okular is very slow when loading files from sshfs mounts
https://bugs.kde.org/show_bug.cgi?id=457228 Bug ID: 457228 Summary: Okular is very slow when loading files from sshfs mounts Product: okular Version: 21.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: m.lince...@gmail.com Target Milestone: --- SUMMARY When opening a small PDF file (less than 50 KB) on a remote filesystem mounted through sshfs (fuse.sshfs), Okular takes almost 10 seconds to load. The behaviour is the same regardless of the fact Okular is launched from Dolphin or from the command line. Evince for comparison takes less than 2 seconds. STEPS TO REPRODUCE 1. mount a remote filesystem using sshfs (from the shell) 2. open a PDF file with Okular OBSERVED RESULT Okular takes a long time to load (almost 10 seconds). EXPECTED RESULT Okular should take a time compatible with other PDF readers. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 377955] yakuake does no longer accept input
https://bugs.kde.org/show_bug.cgi?id=377955 Massimiliano Torromeo changed: What|Removed |Added CC||massimiliano.torromeo@gmail ||.com --- Comment #4 from Massimiliano Torromeo --- What I'm seeing it's not that yakuake doesn't accept input but that it loses focus. I can see the shell cursor change from ▮ to ▯ after maybe a second when I click on it to give it focus. This started yesterday after upgrading plasma packages to 5.25.3 on Arch Linux. Maybe the issue is in kwin? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 Massimiliano Hofer changed: What|Removed |Added CC||m...@mhofer.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd
https://bugs.kde.org/show_bug.cgi?id=433299 --- Comment #13 from Massimiliano L --- Works now for me with systemd 250 on Fedora 36 (Plasma 5.24.5). -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 315096] Adding an option to launch Filelight
https://bugs.kde.org/show_bug.cgi?id=315096 --- Comment #4 from Massimiliano --- (In reply to e from comment #3) > Sorry I didn't realize this is filed under a different component Yes, this was a bug report for KDiskFree. I suggest you file a separate bug report for Filelight to ask for the functionality you want. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 128434] Preview tooltip for hyperlinks to other pages
https://bugs.kde.org/show_bug.cgi?id=128434 Massimiliano L changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Massimiliano L --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 449814] New: Directory properties show empty volume information for btrfs file system
https://bugs.kde.org/show_bug.cgi?id=449814 Bug ID: 449814 Summary: Directory properties show empty volume information for btrfs file system Product: frameworks-kio Version: 5.90.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Properties dialog Assignee: kio-bugs-n...@kde.org Reporter: m.lince...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 146465 --> https://bugs.kde.org/attachment.cgi?id=146465&action=edit example SUMMARY Directory properties show empty volume information for btrfs file system STEPS TO REPRODUCE 1. Open btrfs volume with Dolphin 2. Right click on directory -> properties OBSERVED RESULT File System / Mounted From are empty Mounted on reads "KSqueezedTextLabel" Directory properties show empty information for btrfs volumes Free Space reads ok. EXPECTED RESULT Volume information should be correctly reported. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora w/zawertun COPR KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419302] Dolphin search/baloo shows a lot of duplicates
https://bugs.kde.org/show_bug.cgi?id=419302 Massimiliano L changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #11 from Massimiliano L --- It could be nice to have confirmation by the OP that this problem occurs with btrfs, but it seems highly likely that this is a duplicate of bug 402154. Since the latter is not very findable (misleading title, long discussion), I guess this could stay open. A few comments / considerations: - I can confirm the file search in the menu is not affected by duplicated results, so at least there should be a way to fix the appearance in Dolphin even if duplicates are present in the index; - I am not up to date w.r.t. about how btrfs adoption is evolving in the wild, but with major distros such as OpenSUSE and Fedora on board the userbase is becoming pretty large. A warning message in the File Search config module about support for btrfs being "experimental" could be welcome, but I am not sure what is the KDE policy about this kind of thing; - is it possible to think of a "sanification" routine for the file index, dedicated to the detection / elimination of duplicate file entries? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 429910] Settings -> File search: Folder specific configuration list: self-reproducing, irremovable items of '/home/' with 'indexed' value
https://bugs.kde.org/show_bug.cgi?id=429910 Massimiliano L changed: What|Removed |Added Version|5.22.5 |5.89.0 Component|filesearch |general Product|krunner |frameworks-baloo -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 429910] Settings -> File search: Folder specific configuration list: self-reproducing, irremovable items of '/home/' with 'indexed' value
https://bugs.kde.org/show_bug.cgi?id=429910 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com --- Comment #15 from Massimiliano L --- *** Bug 439403 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 439403] Folder specific configuration show multiple home directory rules that cannot be deleted
https://bugs.kde.org/show_bug.cgi?id=439403 Massimiliano L changed: What|Removed |Added Platform|Other |Netrunner Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Massimiliano L --- I tried to grep the source code to find the origin of these presets, but I was not successful. My current skills are insufficient to troubleshoot this more in depth. Ultimately I think this is a duplicate of Bug 429910 (the discussion there has been a bit untidy but it is clear the underlying issue is the same or tightly related). I am tentatively closing this report. *** This bug has been marked as a duplicate of bug 429910 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 Massimiliano L changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=419302 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419302] Dolphin search/baloo shows a lot of duplicates
https://bugs.kde.org/show_bug.cgi?id=419302 Massimiliano L changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=404057 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419302] Dolphin search/baloo shows a lot of duplicates
https://bugs.kde.org/show_bug.cgi?id=419302 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=402154 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot
https://bugs.kde.org/show_bug.cgi?id=402154 Massimiliano L changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=419302 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd
https://bugs.kde.org/show_bug.cgi?id=433299 Massimiliano L changed: What|Removed |Added Platform|openSUSE RPMs |Fedora RPMs Version|5.21.0 |5.23.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd
https://bugs.kde.org/show_bug.cgi?id=433299 Massimiliano L changed: What|Removed |Added Ever confirmed|0 |1 Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED CC||m.lince...@gmail.com --- Comment #7 from Massimiliano L --- Testing now on Fedora 35 and systemd 249, Skype and Dropbox still fail to autostart. Is anybody able to confirm that this is actually fixed for them? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444053] New: Plasma crashed after updating 5.23.0
https://bugs.kde.org/show_bug.cgi?id=444053
Bug ID: 444053
Summary: Plasma crashed after updating 5.23.0
Product: plasmashell
Version: 5.23.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: titti...@tiscali.it
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.23.0)
Qt Version: 5.15.3
Frameworks Version: 5.87.0
Operating System: Linux 5.11.0-38-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User - Plasma 25th Anniversary Edition
DrKonqi: 5.23.0 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed: I had just update to 5.23.0,
plasma crash at start up, on the screen appear just "Latte"bar, other is black
- Unusual behavior I noticed:
The crash can be reproduced every time.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
[New LWP 1398]
[New LWP 1445]
[New LWP 1446]
[New LWP 1447]
[New LWP 1448]
[New LWP 1511]
[New LWP 1521]
[New LWP 1532]
[New LWP 1549]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7faf22b97aff in __GI___poll (fds=0x7ffe2a377678, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="expression for
target",file="/usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml",fullname="/usr/share/plasma/plasmoids/org.kde.plasma.kickoff/cont".
-
(beware that frames may have been optimized out)
[Current thread is 1 (Thread 0x7faf1ecec9c0 (LWP 1327))]
Thread 10 (Thread 0x7faef5e80700 (LWP 1549)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55ce0f5627c4) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ce0f562770,
cond=0x55ce0f562798) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55ce0f562798, mutex=0x55ce0f562770) at
pthread_cond_wait.c:647
#3 0x7faf22f2c59b in QWaitConditionPrivate::wait (deadline=...,
this=0x55ce0f562770) at thread/qwaitcondition_unix.cpp:146
#4 QWaitCondition::wait (this=this@entry=0x55ce10361f08,
mutex=mutex@entry=0x55ce10361f00, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5 0x7faf24b95b44 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x55ce10361ef8) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68
#6 QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x55ce10361e60) at scenegraph/qsgthreadedrenderloop.cpp:936
#7 0x7faf24b95fb9 in QSGRenderThread::run (this=0x55ce10361e60) at
scenegraph/qsgthreadedrenderloop.cpp:1053
#8 0x7faf22f2642c in QThreadPrivate::start (arg=0x55ce10361e60) at
thread/qthread_unix.cpp:329
#9 0x7faf21e75609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7faf22ba4293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 9 (Thread 0x7faef760e700 (LWP 1532)):
#0 0x7faf23165e34 in QTimerInfoList::timerWait (this=,
tm=...) at
../../include/QtCore/5.15.3/QtCore/private/../../../../../src/corelib/kernel/qcore_unix_p.h:119
#1 0x7faf23167346 in timerSourcePrepareHelper (timeout=0x7faef760d9d4,
src=) at kernel/qeventdispatcher_glib.cpp:162
#2 timerSourcePrepare (source=, timeout=0x7faef760d9d4) at
kernel/qeventdispatcher_glib.cpp:166
#3 0x7faf214428ef in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7faf2144329b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7faf214434a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x7faf231675eb in QEventDispatcherGlib::processEvents
(this=0x7faee8013300, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7 0x7faf2310b87b in QEventLoop::exec (this=this@entry=0x7faef760dba0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8 0x7faf22f25292 in QThread::exec (this=this@entry=0x55ce10085880) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9 0x7faf24ad03ba in QQuickPixmapReader::run (this=0x55ce10085880) at
util/qquickpixmapcache.cpp:1024
#10 0x7faf22f2642c in QThreadPrivate::start (arg=0x55ce10085880) at
thread/qthread_unix.cpp:329
#11 0x7faf21e75609 in start_thread (arg=) at
pthread_create.c:477
#12 0x7faf22ba4293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 8 (Thread 0x7faef7ff6700 (LWP 1521)):
#0 __GI___libc_read (nbytes=16, buf=0x7faef7ff59d0, fd=19) at
../sysdeps/unix/sysv/linux/read.c:26
#1 __GI___libc_read (fd=19, buf=0x7faef7ff59d0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2 0x00
[systemsettings] [Bug 439403] Folder specific configuration show multiple home directory rules that cannot be deleted
https://bugs.kde.org/show_bug.cgi?id=439403 Massimiliano L changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439403] Folder specific configuration show multiple home directory rules that cannot be deleted
https://bugs.kde.org/show_bug.cgi?id=439403 --- Comment #2 from Massimiliano L --- (In reply to groot from comment #1) > Please take a look at `~/.config/baloofilerc` (the configuration file for > baloo). I can't reproduce this, but that's possibly because I can't get two > entries for the home directory to begin with. > > There are two interesting lines in that file: > > ``` > exclude folders[$e]=$HOME/kde/ > folders[$e]=$HOME/,/mnt/lc/ > ``` > > (look for the line starting with "exclude folders" and the line starting > with "folders"; the text above is **my** configuration). I'm curious if your > home-directory is listed twice, or is listed ander different paths to the > same directory. Thanks for the assistance! At this right moment, I have three immutable rules for the home directory, two set to "indexed" and one set to "non indexed". Plus I have two rules for $HOME/Music and $HOME/Pictures In my config file: > dbVersion=2 > exclude filters= [... bunch of extensions] > exclude filters version=8 > exclude folders[$d] If I change the third entry for $HOME to "Indexed", the line in my config file changes and becomes: > exclude filters version=8 > exclude folders[$d] > folders[$e]=$HOME/,$HOME/,$HOME/,$HOME/Music/,$HOME/Pictures/ So some rules that before were implicit become explicit. If I change the first entry for $HOME to "Not indexed", the duplicate entries disappear and I get in my config file: > exclude filters version=8 > exclude folders[$d] > folders[$e]=$HOME/ Now I reset everything to the defaults again, and I get back the three entries for $HOME + $HOME/Pictures and $HOME/Music. The lines in the config file becomes: > exclude filters version=8 > exclude folders[$e]=$HOME So it seems something is wrong with the default "template". Would you know where that is coded so I may check if something is wrong with my installation? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439275] Inappropriate button text in the System Settings “File Search” page.
https://bugs.kde.org/show_bug.cgi?id=439275 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com --- Comment #6 from Massimiliano L --- I opened bug 439403 about duplicate immutable entries for $HOME. Odd behaviour of the pause indexer button is reported in bug 436352. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439403] New: Folder specific configuration show multiple home directory rules that cannot be deleted
https://bugs.kde.org/show_bug.cgi?id=439403 Bug ID: 439403 Summary: Folder specific configuration show multiple home directory rules that cannot be deleted Product: systemsettings Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_baloo Assignee: baloo-bugs-n...@kde.org Reporter: m.lince...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I realised some folders and files were not indexed. Checking the "File Search" configuration module I notice that there are two identical entries for the same '/home/username' directory, one set to "indexed" and one set to "not indexed". The two rules cannot be deleted as the corresponding button is greyed out. Resetting to default creates a third entry for the home directory that cannot be deleted as well. So now I have three entries for the home directory. STEPS TO REPRODUCE I am not sure, since it is impossible to go back to the default. OBSERVED RESULT Multiple rules for the home directory are created and cannot be deleted. EXPECTED RESULT Only one entry for the same directory should exist (to avoid redundant contradictory rules). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 436118] "Software not from a trusted source" prompt does not tell which package is the suspect one
https://bugs.kde.org/show_bug.cgi?id=436118 Massimiliano L changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #9 from Massimiliano L --- Reopening this since I had provided additional info. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 436118] "Software not from a trusted source" prompt does not tell which package is the suspect one
https://bugs.kde.org/show_bug.cgi?id=436118 --- Comment #6 from Massimiliano L --- I managed to reproduce the bug while trying to update slack. And I can double confirm this is software updates and not Discover. The RPM repo file (/etc/yum.repos.d/slack.repo) reads as follows: [slack] name=slack baseurl=https://packagecloud.io/slacktechnologies/slack/fedora/21/x86_64 enabled=1 gpgcheck=0 gpgkey=https://packagecloud.io/gpg.key sslverify=1 sslcacert=/etc/pki/tls/certs/ca-bundle.crt -- 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 --- Comment #4 from Massimiliano L --- (In reply to Albert Astals Cid from comment #3) > Hmmm, you're right, you can't right click. > > I think adding a right click makes sense in this scenarion, but I don't want > to change "double clicking selects word under cursor", because that's what > anyone expects when double clicking in text selection As long as a more intuitive user experience can be provided, I am happy with whatever option is chosen. Not sure about what "anyone expects" since I believe Okular is the only reader with differentiation between browse and text selection, but I understand the argument for consistency. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 436118] "Software not from a trusted source" prompt does not tell which package is the suspect one
https://bugs.kde.org/show_bug.cgi?id=436118 --- Comment #4 from Massimiliano L --- (In reply to Nate Graham from comment #3) > And you're sure you were using the plasma-pk-updates widget, and not > Discover? I clicked on the "Software Updates" icon in the tray and if I right click on the same item I get "Configure Software Updates" so I guess this does not have to do with Discover. I have been doing it for a while and it has worked flawlessly so far. I would suspect a package from one of my "external" repos (Skype, Zoom, Slack) to be the cause. I am fine in putting this on hold until I can reproduce it again. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 436118] "Software not from a trusted source" prompt does not tell which package is the suspect one
https://bugs.kde.org/show_bug.cgi?id=436118 --- Comment #2 from Massimiliano L --- (In reply to Nate Graham from comment #1) > When do you get this prompt? What are you doing to trigger it? I have not encountered a chance to reproduce it yet. What I did is just launch the upgrade through the "software updates" widget. Unfortunately I do not remember which packages were in the list, and after the upgrade I did not know how to get back the log of what was installed. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 435824] FISH KIO slave hangs and randomly stops working (Dolphin)
https://bugs.kde.org/show_bug.cgi?id=435824 --- Comment #2 from Massimiliano L --- (In reply to Christian Hartmann from comment #1) > Same here with: > > Operating System: openSUSE Tumbleweed 20210422 > KDE Plasma Version: 5.21.4 > KDE Frameworks Version: 5.81.0 > Qt Version: 5.15.2 It seems to me the KIO sftp is more stable, although FISH has been reported to be faster in the past I do not notice performance issues with sftp so far. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 380417] fish doesn't use User from .ssh/config
https://bugs.kde.org/show_bug.cgi?id=380417 --- Comment #5 from Massimiliano L --- (In reply to Méven Car from comment #4) > You checkout this branch > https://invent.kde.org/meven/kio-extras/-/tree/work/fish-bug-380417 and let > me know how it goes. > > I don't know much about fish protocol in particular, so expect the > unexpected. Testing this is on my todo, I apologise but I got busy with work and I do not have the test bench ready yet. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 436118] New: "Software not from a trusted source" prompt does not tell which package is the suspect one
https://bugs.kde.org/show_bug.cgi?id=436118 Bug ID: 436118 Summary: "Software not from a trusted source" prompt does not tell which package is the suspect one Product: plasma-pk-updates Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: m.lince...@gmail.com Target Milestone: --- Created attachment 137862 --> https://bugs.kde.org/attachment.cgi?id=137862&action=edit example prompt SUMMARY In some circumstances, the software update service will prompt for a password because "The software is not from a trusted source." Action is indicated as "Install untrusted local file". In such case, there is no mention about which package is the "suspect" so the user has no choice except accepting blindly the update or aborting. Also it is confusing to have the action described as "Install untrusted local file" while the package is being update from a repository. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 + KDE copr (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- 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 --- Comment #2 from Massimiliano L --- (In reply to Albert Astals Cid from comment #1) > You are in text selection mode, clicking doing selection things is the > expected behaviour. > > Why would it do something else? if you want to open the annotation you can > right click or you can go to browse mode. Hi Albert, thanks for the feedback. Maybe I should have filed it as a feature request rather than a bug. Please note that right click in "text selection" mode does not do anything unless some text is selected, and even in that case the context menu does not have to do with annotations. So it is not possible to open the annotation that way. I honestly think it is counterintuitive and potentially misleading for "text selection" mode to show annotations while allowing to open only some of them. That way there is no visual/functional distinction between a simple highlight and an "highlight with comment". Furthermore, you have a situation where some "highlight with comment" open - if you click in the right place, namely a space between words where applicable - and some other do not. This feels like a lack of UX consistency to me. I truly believed Okular was broken for months until I realised by pure chance the underlying pattern, and I consider myself a fairly "advanced" user. Also please consider the use case where one may want to copy some sentences and the related annotations on a notepad. One would need to keep switching between "text selection" and "browse mode", because in "text selection" you cannot open annotations and in "browse mode" you cannot select the document text. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406725] Allow folders to be excluded for thumbnail generation
https://bugs.kde.org/show_bug.cgi?id=406725 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com --- Comment #10 from Massimiliano L --- A byproduct of this behaviour is that by default network mounts are scanned as well, this may results in possibly undesired network traffic outside of the user's control. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435918] New: Double click on "highlight with comment" annotation selects text instead of opening annotation
https://bugs.kde.org/show_bug.cgi?id=435918 Bug ID: 435918 Summary: Double click on "highlight with comment" annotation selects text instead of opening annotation Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: m.lince...@gmail.com Target Milestone: --- SUMMARY When in "text selection" mode, double clicking on the highlighted text of an "highlight with comment" annotation results in the word being selected instead of the annotation being opened. If the annotation spans across multiple words, clicking on the white space between will open the annotation, providing a confusing user experience (it took a while to me to realise why certain annotations did open and others did not). STEPS TO REPRODUCE 1. Create an "highlight with comment" annotation. 2. Switch to text selection mode. 3. Double click on the highlighted text. OBSERVED RESULT The double-clicked word gets selected. EXPECTED RESULT The annotation is opened. SOFTWARE/OS VERSIONS Okular Version 20.12.3 KDE Frameworks 5.81.0 Qt 5.15.2 (built against 5.15.2) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435536] Location bar lags and becomes unrensponsive using fish on a directory with a large number of items
https://bugs.kde.org/show_bug.cgi?id=435536 --- Comment #1 from Massimiliano L --- According to user 'bivouak' on reddit, this is part of a class of issues related to KIO and the fact that 'listing directories is currently synchronous, which means Dolphin UI will refresh only once all the folder contents have been read'. There should be a corresponding bug for dolphin or KIO so this can be marked as a duplicate? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 434407] Size inconsistency in initials-style avatar (default vs change avatar)
https://bugs.kde.org/show_bug.cgi?id=434407 --- Comment #4 from Massimiliano L --- (In reply to Domenico Panella from comment #3) > In my opinion, the default image and the image which we select via window > dialog should be handled at the same way. > I mean both handled as Image or Text otherwise we will always see the > difference between them. I agree with your view. It is otherwise a bit strange to have a default configuration that can never be reset to default. Harmonising the two would be a good idea. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 434407] Size inconsistency in initials-style avatar (default vs change avatar)
https://bugs.kde.org/show_bug.cgi?id=434407 --- Comment #2 from Massimiliano L --- (In reply to Domenico Panella from comment #1) > Decreasing "font.pixelSize" property > at > https://invent.kde.org/plasma/plasma-desktop/-/blob/master/kcms/users/ > package/contents/ui/UserDetailsPage.qml#L419 > > from > font.pixelSize: Kirigami.Units.gridUnit * 4 > > to > font.pixelSize: Kirigami.Units.gridUnit * 2.5 > > it looks good for me. I understand you propose a change that makes the font smaller but do we understand why the font was changeing size compared to the default? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 380417] fish doesn't use User from .ssh/config
https://bugs.kde.org/show_bug.cgi?id=380417 --- Comment #3 from Massimiliano L --- (In reply to Méven Car from comment #2) > As a workaround, you can pass your username as > fish://serverusern...@somedomain.com > > Currently the code defaults the username when not set in the url to your > username. > line 713 of fish.cpp > > The fish ioslave is quite old code and hard to maintain. I can't test it. > > I could provide a patch but I will need someone to test it. > Do feel you can do it Massimiliano ? > You can follow https://www.youtube.com/watch?v=B4xoc0K5iA4 but just for > kio-extras, i.e kdesrc-build kio-extras Hi Méven. Thanks for the feedback. I am available to test it (I had set up a Neon VM for this kind of stuff), I can also take a look at the source code but I am not sure I am experienced enough to help. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 435824] New: FISH KIO slave hangs and randomly stops working (Dolphin)
https://bugs.kde.org/show_bug.cgi?id=435824 Bug ID: 435824 Summary: FISH KIO slave hangs and randomly stops working (Dolphin) Product: kio-extras Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: FISH Assignee: plasma-b...@kde.org Reporter: m.lince...@gmail.com Target Milestone: --- SUMMARY >From time to time FISH access to a remote server stops working with the dolphin status bar hanging on "Connecting..." / "Loading folder...". When this happens, it becomes impossible to reconnect. There is no timeout and the user is not prompted with any log about the backend. SSH access to the same machine works fine. STEPS TO REPRODUCE Use fish for some time until it stops working (sorry, I do not find a specific trigger). OBSERVED RESULT Unable to connect to servers through FISH. EXPECTED RESULT There should be no situation in which the protocol "hangs" indefinitely. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 380417] fish doesn't use User from .ssh/config
https://bugs.kde.org/show_bug.cgi?id=380417 Massimiliano L changed: What|Removed |Added CC||m.lince...@gmail.com --- Comment #1 from Massimiliano L --- I am also experiencing this, behaviour seems to be unchanged as of today. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434406] Neutral user icon as avatar choice
https://bugs.kde.org/show_bug.cgi?id=434406 --- Comment #15 from Massimiliano L --- (In reply to Domenico Panella from comment #13) > Also the new user management predict the image/icons selection via file > system browsing. You can select whatever you want via "Choose file" button. > Attach a screenshot to remove some doubts I think we are overcomplicating this :) I am aware "Choose file" option but that means the user would have either to find out where the icons are stored or download a custom image from the web. I do not see any problem in expanding the pool of available images by one element. I offer to take care of it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434406] Neutral user icon as avatar choice
https://bugs.kde.org/show_bug.cgi?id=434406 --- Comment #12 from Massimiliano L --- > During user creation is not is possible and i think that it's intentional... > It has not sense to add a profile picture for the user which you are not. > In modify mode, it already provides this functionality and it's right , > therefore, > you only could ask a default behaviour changing which doesn't seem wanted. Yes, my point is that in "edit mode" there is a pool of images that can be chosen from. If I remember correctly, the old user manager had access to the icon set. The new user manager has access to a pre-defined set of images and it is just a matter of adding one more to the repo :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434406] Neutral user icon as avatar choice
https://bugs.kde.org/show_bug.cgi?id=434406 --- Comment #9 from Massimiliano L --- (In reply to Domenico Panella from comment #8) > I had properly interpreted your request therefore you are requiring a > default behaviour changing which should show "user-identity" icon in place > of image with initial letters which you say that is buggy too when we change > its aspect. > > To be honest, for me is indiffeent, but from comment above, it doesn't seem > interested to change it, therefore i'd say to close this bug/request. > I'd leave open this bug 434407 instead I think this was clear from my opening message that my primary aim was to have/provide a neutral-looking option such as the user identity icon among the avatar choices. This can be done pretty easily (I can try to do it by myself and file a merge request). The change of defaults was just a sidenote suggestion given the current state of things but it can be put aside if nobody else supports it (also I guess these matters should be up to the VDG?). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434406] Neutral user icon as avatar choice
https://bugs.kde.org/show_bug.cgi?id=434406 --- Comment #7 from Massimiliano L --- > (Coming back to the previous message I believe the "user-identity" icon > would be a better default and give a more polished look. Initials currently > appear right next to the user's full name and the background color of the > circle makes up a bit of visual clutter. On the other hand this is also a > matter of personal preference and I understand you/we may want to showcase > this feature in the defaults :) P.S.: in favour of changing the default would be the fact that the initials-style avatar is currently buggy (see bug 434407), so as soon as the user tries to change the default appearance (e.g. color) the avatar will look 'bad'. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434406] Neutral user icon as avatar choice
https://bugs.kde.org/show_bug.cgi?id=434406 --- Comment #6 from Massimiliano L --- (In reply to Domenico Panella from comment #5) > A question: > > my system settings show both "Users" and "Users Manager". > "Users manager" already offers this option while we create a new user. You > can choice your preferred image > from window dialog or browsing file system. > > "Users" doesn't offer this option while we create the user (it always sets > the image with initial letters) but only after do it we can change the image. > > Do we want be able to choice our preferred image while create the user too > on "Users"? I do not think this is a very useful feature for two reasons: 1. most systems have single user created during the installation, without access to customisations of the DE user profile; 2. if you are using "Users" to create an user, you are probably creating someone's else user so it does not makes sense to customise the profile picture for them. (Coming back to the previous message I believe the "user-identity" icon would be a better default and give a more polished look. Initials currently appear right next to the user's full name and the background color of the circle makes up a bit of visual clutter. On the other hand this is also a matter of personal preference and I understand you/we may want to showcase this feature in the defaults :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435536] New: Location bar lags and becomes unrensponsive using fish on a directory with a large number of items
https://bugs.kde.org/show_bug.cgi?id=435536 Bug ID: 435536 Summary: Location bar lags and becomes unrensponsive using fish on a directory with a large number of items Product: dolphin Version: 20.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: filter Assignee: dolphin-bugs-n...@kde.org Reporter: m.lince...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When browsing a remote directory with 'fish' and if such directory has a pretty big number of items, the location bar responsiveness becomes inconsistent and lags are experienced. STEPS TO REPRODUCE 1. Connect to a remote filesystem using fish 2. Browse to a directory with a large number of items (~ 2000) 3. Try to scroll the items and then try to use the location bar. OBSERVED RESULT Location bar responsiveness seem to depend on the status of the "scrolling", becomes laggy. EXPECTED RESULT Location bar should always be responsive? SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora / 20.12.3 (zawertun's COPR) (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434406] Neutral user icon as avatar choice
https://bugs.kde.org/show_bug.cgi?id=434406 --- Comment #2 from Massimiliano L --- (In reply to Nate Graham from comment #1) > Seems fair. The `user-identity` icon seems neutral enough. Thanks for the feedback! Should we just copy-paste the icon to the files of the user manager? Does the latter support SVG or a raster format is required? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 340637] Highlighting in a two-column document highlights both columns instead of one
https://bugs.kde.org/show_bug.cgi?id=340637 Massimiliano L changed: What|Removed |Added Version|1.11.3 |20.12.3 CC||m.lince...@gmail.com --- Comment #8 from Massimiliano L --- Problem is still present in 20.12.3, does not happens with all two-column PDFs but it still occurs with the example provided here. Evince on the same document behaves correctly. -- You are receiving this mail because: You are watching all bug changes.
