[kmail2] [Bug 396327] column settings not remembered in folder pane
https://bugs.kde.org/show_bug.cgi?id=396327 --- Comment #4 from Jonathan M Davis --- I also have qt 5.10.1 on FreeBSD. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394157] Wallpaper slideshow: background color unsaved
https://bugs.kde.org/show_bug.cgi?id=394157 Jonathan M Davis changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394157] Wallpaper slideshow: background color unsaved
https://bugs.kde.org/show_bug.cgi?id=394157 Jonathan M Davis changed: What|Removed |Added CC||bugs.kde@jmdavisprog.co ||m --- Comment #6 from Jonathan M Davis --- I'm seeing this on FreeBSD. KDE is broken up into so many pieces these days that I don't even know which package installs the wallpaper stuff , but plasma5-plasma-desktop is version 5.12.5. So, if this ends up being fixed with 5.13, then great, but it's trivially reproducible on my system. Basically, it looks like every time I log into KDE, it ignores the wallpaper setting for the background color and just uses blur instead of the solid color that was selected. The setting itself does not change, but it's clearly ignored, as any images that do not match the screen's aspect ratio end up with the blur effect rather than the solid color until I go into the wallpaper settings dialog and reapply the correct settings. To reproduce, obviously, a setting that does not necessarily cover the entire background (e.g. "Scaled, Keep Proportions") must be used, and the background image must be of a different aspect ratio than the screen so that the background actually shows. And if it matters, I have it set to "slideshow," though I expect that other settings such as "image" would exhibit the same problem. Honestly, I find it a bit disturbing that "blur" is even a thing given how hideous it is, but regardless, the settings should be adhered to, not ignored. Hopefully, 5.13 does fix this though. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 396322] An option for the screenlocker to show the screensaver without actually locking the computer
https://bugs.kde.org/show_bug.cgi?id=396322 --- Comment #4 from Jonathan M Davis --- (In reply to David Edmundson from comment #3) > This is not a job for the screenlocker. > > You can do a slideshow with gwenview. Well, if you guys won't fix it so that kscreenlocker can act like a screensaver, then you're not going to fix it, but running a slideshow with a screensaver and running one with with gwenview are two completely different things even if they both involve running a slideshow. One kicks in when the computer has had no input for a certain period of time, and the other is something you run manually when you're specifically trying to show a slideshow. Honestly, I find it pretty amazing that there's anything controversial here. The way that most OSes and DEs handle this is that you have a screensaver, and you can optionally choose to have it require a password to turn it off, whereas it seems like the current approach to KDE is to try and just have it lock the screen and act like it's not a screensaver at all even though that's precisely what it does - it's just made the locking functionality mandatory for some reason. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 396322] An option for the screenlocker to show the screensaver without actually locking the computer
https://bugs.kde.org/show_bug.cgi?id=396322 --- Comment #2 from Jonathan M Davis --- (In reply to Kai Uwe Broulik from comment #1) > Why not just let the screen automatically turn off instead of wasting power > showing a screensaver? For all of the normal reasons that you use a screensaver rather than just shutting the screen off. I'd like to be able to have images showing when I'm not using the computer but am still in the room. Certainly, if that goes on long enough, I want the screen shutting off, but it's not particularly interesting to have the screen just shut off. You could ask the same question as to why the screenlocker has a slideshow in the first place. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396327] New: column settings not remembered in folder pane
https://bugs.kde.org/show_bug.cgi?id=396327 Bug ID: 396327 Summary: column settings not remembered in folder pane Product: kmail2 Version: 5.8.2 Platform: FreeBSD Ports OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: bugs.kde@jmdavisprog.com Target Milestone: --- I set the folder pane to have the "Name," "Unread," and "Total" columns, but when I open kmail after closing it, the "Size" column is also shown, and all of the columns are smashed to the left instead of spaced out the way they were before I closed kmail (though I don't know whether the spacing isn't being saved properly or whether it's just getting messed up, because the "Size" column is being added). In case it matters, the other settings I have for the folder pane are "16x16," "Always," and "Automatically, by Current Column." -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 396322] New: An option for the screenlocker to show the screensaver without actually locking the computer
https://bugs.kde.org/show_bug.cgi?id=396322 Bug ID: 396322 Summary: An option for the screenlocker to show the screensaver without actually locking the computer Product: kscreenlocker Version: unspecified Platform: FreeBSD Ports OS: FreeBSD Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugs.kde@jmdavisprog.com CC: bhus...@gmail.com Target Milestone: --- As far as I can tell, kscreenlocker is KDE's current screensaver solution. It gives pretty much the same control over what it shows as the desktop wallpaper does, and I'd like to use it. However, for whatever reason, it gives no options for not locking the screen when it turns on. So, if I want a screensaver, I'm stuck with the screen locking. For a computer like my laptop which gets used in places outside my home, locking the screen makes perfect sense, but for my desktop at home, it makes no sense at all. It's just annoying. So, I'd really appreciate it if the "Require password after locking" control had an option for "never" so that I'm not required to have my screen lock just to get the screensaver. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396300] New: account assistant creates pgp key without asking when gpg-agent is running
https://bugs.kde.org/show_bug.cgi?id=396300 Bug ID: 396300 Summary: account assistant creates pgp key without asking when gpg-agent is running Product: kmail2 Version: 5.8.2 Platform: FreeBSD Ports OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bugs.kde@jmdavisprog.com Target Milestone: --- When creating a new account in kmail, on the "Secure your Communication" page of the wizard, it not only defaults to "Secure outgoing emails, if possible," but it outright creates a PGP key and adds it to my wallet. It's one thing for it to want to do gpg by default (which I disagree with), but it's another thing entirely to create a key without even asking me first. This means that when I add an account, I have go and delete unwanted PGP keys from my wallet. >From what I can tell after some experimenting, kmail only creates the key if gpg-agent is running. I guess that kmail assumes that I want to use gpg for e-mail just because I have gpg-agent running, but regardless, I really don't think that it's appropriate for kmail to be creating PGP keys without even asking first. Even if I did want to use gpg with kmail right now, I wouldn't want it to create keys without asking first. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 388333] How to create new konqueror processes?
https://bugs.kde.org/show_bug.cgi?id=388333 Jonathan M Davis changed: What|Removed |Added CC||bugs.kde@jmdavisprog.co ||m --- Comment #2 from Jonathan M Davis --- This is _incredibly_ annoying. Previously, I could have a button on the taskbar that opened a new konqueror instance, and now, that doesn't work. Konqueror _does_ open a new instance if you provide a URL, so if I make the button provide a URL, then a new window does open. However, it doesn't give the URL bar focus, so I can't just start typing the URL I want like I could before, and of course, I'm stuck with it always opening a default URL when it starts, and I don't usually want a default URL. FreeBSD finally got KDE 5 recently, and this is one of the problems that has made switching from KDE 4 to KDE 5 to be a downgrade rather than an upgrade. I really hope that this gets fixed sooner rather than later. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 205552] Make each konqueror window use a separate process
https://bugs.kde.org/show_bug.cgi?id=205552 --- Comment #2 from Jonathan M Davis <jmdavisp...@gmx.com> --- Yes, if you open a new window externally, then you get a new process, but you don't if you use "New Window" within Konqueror, and when KDE first starts up and reopens all of the Konqueror windows that were open when you logged out, I'm not sure that all of those are separate either. The current behavior is inconsistent, and I'd very much like it if every Konqueror window were in its own process. It would be more consistent and more resilient. It's not as big an issue as it once was, since KDE and Konqueror are more stable than they were in the early days of KDE 4, but it would still be a definite improvement IMHO. -- You are receiving this mail because: You are watching all bug changes.
