T.C. Hollingsworth wrote:
> systemd (by default) doesn't put idle systems to sleep, but it does
> put closed laptops to sleep when no desktop power management system
> is active (e.g. when KDM is running).
>
> Just set HandleLidSwitch=ignore in /etc/systemd/logind.conf to turn
> it off. See `man
On Tue, Aug 5, 2014 at 9:46 AM, CLOSE Dave
wrote:
> Thanks for the reply. I interpret your comments to imply that, because
> I'm using KDM, the laptop should never go to sleep while at the login
> screen. Unfortunately, that is not my experience. If the laptop is
> closed, it goes to suspend withi
Allegedly, on or about 05 August 2014, CLOSE Dave sent:
> If the laptop is closed, it goes to suspend within a few minutes.
As a side issue, you need to check that your laptop won't overheat if
the lid is shut. Some of them have ventilation around the keyboard, and
need it.
--
[tim@localhost ~
T.C. Hollingsworth wrote:
> What display manager are you using? `systemctl show
> display-manager.service -pId` will tell you.
# systemctl show display-manager.service -pId
Id=kdm.service
> KDM is the default display manager on the Fedora KDE spin, and KDM is
> ancient and crufty and doesn't ev
On Fri, Aug 1, 2014 at 10:45 AM, CLOSE Dave
wrote:
> I have some laptops running F20/KDE which, among other purposes, are
> acting as gateways to a private network. Most of the time these laptops
> are unattended -- no one is logged into the console -- but the gateway
> function must continue to r
I asked:
> Is there a way to keep the power management function active even
> when no one is logged into the console?
On 08/02/2014 08:19 AM, Tim wrote:
> Perhaps you can configure power management options for the kdm user
> (that which the KDM logon screen runs as)? Assuming that kdm works
> i
Allegedly, on or about 01 August 2014, CLOSE Dave sent:
> Is there a way to keep the power management function active even when
> no one is logged into the console?
Perhaps you can configure power management options for the kdm user
(that which the KDM logon screen runs as)? Assuming that kdm wo
On 4 August 2010 06:00, JB wrote:
> JB yahoo.com> writes:
>
>> ...
>> Hi, I forgot it.
>> ...
> I would do this as well.
> You may lose some custom settings, but it appears it is effective (I removed
> battery widget from my panel unintentionally and could not add it back via
> panel's add widget
On 3 August 2010 13:38, JB wrote:
> JB yahoo.com> writes:
>
>> ...
>> # yum reinstall upower
>> ...
>
> Hi, I forgot it.
> After reinstall (please do it even if it appears unnecessary ...; I recently
> fixed my bluetooth by reinstalling multiple related packages):
Doing that now
>
> note: l
On 3 August 2010 12:21, JB wrote:
> Chris Rouch gmail.com> writes:
>
>> ...
>> > [jb localhost ~]$ ps aux |grep -i power
>> > root 1439 0.0 0.3 6028 2364 ? S Aug01 0:04
>> > /usr/libexec/upowerd
>> > ...
>> Bingo! For whatever reason, upowerd is not running. If I start it b
On 2 August 2010 17:43, JB wrote:
> Chris Rouch gmail.com> writes:
>
>>
>> So I think this is a kde problem.
>>
> Hi,
> have you looked into these in KDE:
> computer-system settings-general-notifications-system
> notifications-applications
> event source selection -> scroll to PowerDevil
> selec
Chris Rouch gmail.com> writes:
>
> So I think this is a kde problem.
>
Hi,
have you looked into these in KDE:
computer-system settings-general-notifications-system notifications-applications
event source selection -> scroll to PowerDevil
select item e.g. AC adaptor plugged in
check off below e.
On 1 August 2010 20:24, JD wrote:
> On 08/01/2010 11:15 AM, Chris Rouch wrote:
>> .snip .
>> I'm going to try it, just to rule out the kde components. But i've
>> used gnome before and was forced to junk it for fvwm when it became
>> too bloated for my (old) laptop. i've never been tempte
On 08/01/2010 11:15 AM, Chris Rouch wrote:
> .snip .
> I'm going to try it, just to rule out the kde components. But i've
> used gnome before and was forced to junk it for fvwm when it became
> too bloated for my (old) laptop. i've never been tempted to try it
> again :-)
>
> Regards,
>
>
On 30 July 2010 00:16, Gordon Messmer wrote:
> On 07/29/2010 01:17 AM, Chris Rouch wrote:
>> I think this was working for f13 too until the last time i applied
>> updates, though it may just be that i didn't test it.
>
> The first thing you should try is probably to boot the oldest F13 kernel
> th
On 29 July 2010 16:32, JB wrote:
> JB yahoo.com> writes:
>
>>
>> Chris Rouch gmail.com> writes:
>>
>> >
>> > I have a duel boot laptop. if i boot it into f12, using kde, and pull
>> > out the power cord, i get a popup message telling me i've done so and
>> > the battery monitor icon changes. If
On Thu, 2010-07-29 at 15:16 -0700, Gordon Messmer wrote:
> On 07/29/2010 01:17 AM, Chris Rouch wrote:
> > I think this was working for f13 too until the last time i applied
> > updates, though it may just be that i didn't test it.
>
> The first thing you should try is probably to boot the oldest F
On 07/29/2010 01:17 AM, Chris Rouch wrote:
> I think this was working for f13 too until the last time i applied
> updates, though it may just be that i didn't test it.
The first thing you should try is probably to boot the oldest F13 kernel
that you've got and see if the system's behavior is any
On Thu, 2010-07-29 at 19:28 +0800, Ed Greshko wrote:
> On 07/29/2010 07:16 PM, Tim wrote:
> > While I think it's fair to ask that Fedora 13 (and its apps) can read
> > the configuration left behind by Fedora 12, and update it where needed.
> > You can't really expect Fedora 12 (when someone is dual
On 07/29/2010 07:41 PM, Chris Rouch wrote:
> Good idea. I created a new user, selected a kde session and logged in
> as that user. I did not change any configuration. The battery charge
> icon had a yellow lightning bolt indication mains power. I pulled the
> power lead, and nothing changed - no p
On 29 July 2010 13:28, Ed Greshko wrote:
> While I do agree with what you've said The one thing that hasn't
> been determined is if indeed the issue is the differences in settings
> between F12 and F13 and jumping between the 2 versions. The OP "thinks"
> it was working before the last upda
On 29 July 2010 12:27, JB wrote:
> Chris Rouch gmail.com> writes:
>
>>
>> The home directory is
>> shared between the two boots, so the configuration is the same.
>>
> Well,
> that may be the problem ...
> Unless you really have a specific reason to have a common home dir,
> I think you are askin
On 07/29/2010 07:16 PM, Tim wrote:
> While I think it's fair to ask that Fedora 13 (and its apps) can read
> the configuration left behind by Fedora 12, and update it where needed.
> You can't really expect Fedora 12 (when someone is dual-booting) to be
> able to handle Fedora 13 configurations.
>
On Thu, 2010-07-29 at 12:47 +0200, Timothy Murphy wrote:
> It is up to Fedora to make sure that any config files
> that it (she?) places in /home are properly updated
> during installation of a new distribution.
While I think it's fair to ask that Fedora 13 (and its apps) can read
the configuratio
JB wrote:
>> The home directory is
>> shared between the two boots, so the configuration is the same.
>>
> Well,
> that may be the problem ...
> Unless you really have a specific reason to have a common home dir,
> I think you are asking for more or less unpredictability with both
> installations
25 matches
Mail list logo
