I currently use t-bird with an nntp account pointing to gmane to read
this list and sereral others. Does kde have an nntp client program of
any sort? I don't see it as a possible new account type in kmail. Also,
search with kpackagekit yields nothing with "usenet" or "nntp" that is
That's something we (fedora) patched in to kde4 (from kde3 times), but we have not yet implemented the same for plasma5.
Maybe if there is sufficient demand.
From: kde-bounces(a)lists.fedoraproject.org <kde-bounces(a)lists.fedoraproject.org> on behalf of Gerald B. Cox <gbcox(a)bzb.us>
Sent: Thursday, April 30, 2015 12:10 PM
To: Fedora KDE List
Subject: Plasma 5 - Right Click Desktop - Konsole?
Under KDE 4 you could right click on the desktop which would bring up a menu that allowed
you to open konsole. I've looked under Plasma 5 but apparently not hard enough because I
can't figure out how to add it. Am I missing something or is this no longer available?
When trying to update Yakuake from updates-testing it fails with this error:
Error: Package: yakuake-2.9.9-8.fc21.x86_64 (updates-testing)
Requires: konsole-part >= 4.14.6
Installed: konsole-part-4.14.3-4.fc21.x86_64 (installed)
I'm guessing konsole* missed getting updated to 4.14.7 as I cant see it in the
Running F21 - 4.14.7
Fedora 21 - (Twenty One)
Registered Linux user number #342953
Under KDE 4 you could right click on the desktop which would bring up a
menu that allowed
you to open konsole. I've looked under Plasma 5 but apparently not hard
enough because I
can't figure out how to add it. Am I missing something or is this no
I would like to talk about screen lock in KDE Plasma 5.
KDE Plasma 5 locks the screen with user password after 5 minutes of
system being in idle.
I think that we should disable screenlock as default behaviour for KDE
Plasma, because it will annoy many users. If anybody needs it, it can be
wondering if this is a bug or my own stupidity: whenever I reboot
I have to open KDE Mixer/Settings/Audio Setup/Audio Hardware Setup
and change "Device Configuration/Connector" to "Headphones" in order
to have working headphones.
Why doesn't it remember this setting? After each reboot it is back
to "Line Out"
[ 22.212808] sound hdaudioC0D0: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[ 22.212814] sound hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 22.212817] sound hdaudioC0D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[ 22.212818] sound hdaudioC0D0: mono: mono_out=0x0
[ 22.212820] sound hdaudioC0D0: inputs:
[ 22.212823] sound hdaudioC0D0: Front Mic=0x19
[ 22.212825] sound hdaudioC0D0: Rear Mic=0x18
[ 22.212827] sound hdaudioC0D0: Line=0x1a
[ 22.230225] input: HDA Intel Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
[ 22.230656] input: HDA Intel Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
[ 22.231051] input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 22.231443] input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 22.231835] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
Name and OpenPGP keys available from pgp key servers
First off, thanks for the discussion. However, one thing I've learned when dealing with setting defaults is this: best practice is to never use yourself as anecdotal evidence. :)
Now, instead of disabling screenlock timeouts altogether, perhaps we could find a compromise...
I agree that the default screenlock timeout of 5 minutes does seem a bit short, would anyone be averse to considering increasing this ammount to say 10 or 15 minutes? Would that help satisfy concerns that prompted this thread?