Hi again,

Arch uses a package format called. pkg.tar.gz, and yes I have compiled
kpowersave myself, using --prefix=/opt/kde and as you suggested
--enable-debug-msg

I then tried running kpowersave from the console using: kpowersave
--nofork. Reading from the output it seems that things are working fine,
only nothing ever happens after the given amount of inactivity. I have
tried waiting several minutes more than the 1 minute I chose to be the
trigger. As you suggested, I also tried to enable scheme specific
blacklist both with an without programs, still with no success.
This is the output I have from kpowersave, notice that at 13:14:40 I
choose to explicitly do a "Suspend to Ram" from the kpowersave menu, to
see what kind of output that brings.

Any suggestions how to debug further?

[EMAIL PROTECTED] kpowersave]$ kpowersave --nofork
 12:57:04:424:  kpowersave::kpowersave
 12:57:04:425:  pDaemon::pdaemon
 12:57:04:425:  dbusPowersaveConnection::dbusPowersaveConnection
 12:57:04:426:  dbusPowersaveConnection::initDBUS
 12:57:04:428:  pDaemon::checkDaemon
 12:57:04:429:  pDaemon::switchToDaemonMode
 12:57:04:429:  pDaemon::readDaemonData
 12:57:04:431:  pDaemon::updateSchemeInfo
 12:57:04:449:  pDaemon::updateSchemeInfo
 12:57:04:459:  pDaemon::getMaxBrightnessLevels
 12:57:04:462:  kpowersave::update
 12:57:04:462:  kpowersave::updateCPUFreqMenu
 12:57:04:462:  kpowersave::updateSchemeMenu
 12:57:04:464:  kpowersave::setSchemeSettings()
 12:57:04:467:  kpowersave::setAutoSuspend
 12:57:04:492:  pDaemon::setBrightness
 12:57:04:498:  pDaemon::getBrightness
 12:57:04:499:  kpowersave::redrawPixmap
 12:57:04:499:  kpowersave::loadIcon
 12:57:04:500:  kpowersave::drawIcon
 12:57:04:528:  filter_function::SIGNAL=NameAcquired
 12:57:04:528:  filter_function::VALUE=:1.117
 12:57:23:977:  kpowersave::updateTooltip
 12:57:27:606:  kpowersave::mousePressEvent
 12:57:27:673:  pDaemon::checkDaemon
 12:57:27:676:  pDaemon::updateSchemeInfo
 12:57:32:791:  kpowersave::show_configure_dialog
 12:57:32:839:  pDaemon::getMaxBrightnessLevels
 12:57:32:849:  pDaemon::getBrightness
 12:57:32:860:  pDaemon::setBrightness
 12:57:32:871:  pDaemon::getBrightness
 12:57:32:875:  pDaemon::setBrightness
 12:57:32:884:  pDaemon::getBrightness
 12:58:13:828:  kpowersave::observe_configDlg
 12:58:13:836:  kpowersave::setSchemeSettings()
 12:58:13:843:  kpowersave::setAutoSuspend
 12:58:13:865:  pDaemon::setBrightness
 12:58:13:933:  pDaemon::getBrightness
 13:03:39:620:  kpowersave::updateTooltip
 13:03:42:10:   kpowersave::mousePressEvent
 13:03:42:60:   pDaemon::checkDaemon
 13:03:42:63:   pDaemon::updateSchemeInfo
 13:03:50:618:  kpowersave::show_configure_dialog
 13:03:50:645:  pDaemon::getMaxBrightnessLevels
 13:03:50:665:  pDaemon::getBrightness
 13:03:50:686:  pDaemon::setBrightness
 13:03:50:696:  pDaemon::getBrightness
 13:03:50:699:  pDaemon::setBrightness
 13:03:50:709:  pDaemon::getBrightness
 13:05:10:793:  kpowersave::observe_configDlg
 13:05:10:800:  kpowersave::setSchemeSettings()
 13:05:10:807:  kpowersave::setAutoSuspend
 13:05:10:818:  pDaemon::setBrightness
 13:05:10:863:  pDaemon::getBrightness
 13:14:32:979:  kpowersave::updateTooltip
 13:14:35:780:  kpowersave::mousePressEvent
 13:14:35:829:  pDaemon::checkDaemon
 13:14:35:833:  pDaemon::updateSchemeInfo
 13:14:40:313:  kpowersave::do_suspend2ram
 13:14:40:409:  filter_function::SIGNAL=PowersaveEvent
 13:14:40:410:  filter_function::VALUE=global.suspend2ram
 13:14:40:410:  pDaemon::processClientMessage
 13:14:40:410:  Powersave Event: 'global.suspend2ram'
 13:14:40:410:  kpowersave::set_suspend_type
 13:14:40:410:  kpowersave::update
 13:14:40:416:  filter_function::SIGNAL=Progress
 13:14:40:416:  filter_function::VALUE=0
 13:14:40:416:  pDaemon::processClientMessage
 13:14:40:416:  kpowersave::showProgressDialog
 13:14:40:450:  filter_function::SIGNAL=Progress
 13:14:40:450:  filter_function::VALUE=10|unmounting FAT/NTFS partitions
 13:14:40:450:  pDaemon::processClientMessage
 13:14:40:450:  kpowersave::showProgressDialog
 13:14:40:520:  filter_function::SIGNAL=Progress
 13:14:40:520:  filter_function::VALUE=20|stopping services
 13:14:40:520:  pDaemon::processClientMessage
 13:14:40:520:  kpowersave::showProgressDialog
 13:14:44:128:  filter_function::SIGNAL=Progress
 13:14:44:128:  filter_function::VALUE=30|ejecting PCMCIA cards
 13:14:44:128:  pDaemon::processClientMessage
 13:14:44:128:  kpowersave::showProgressDialog
 13:14:44:272:  filter_function::SIGNAL=Progress
 13:14:44:272:  filter_function::VALUE=40|unloading modules
 13:14:44:272:  pDaemon::processClientMessage
 13:14:44:272:  kpowersave::showProgressDialog
 13:14:44:280:  filter_function::SIGNAL=Progress
 13:14:44:280:  filter_function::VALUE=40|unloading module: ipw2200
 13:14:44:280:  pDaemon::processClientMessage
 13:14:44:280:  kpowersave::showProgressDialog
 13:14:44:632:  filter_function::SIGNAL=Progress
 13:14:44:632:  filter_function::VALUE=40|unloading module: ehci_hcd
 13:14:44:632:  pDaemon::processClientMessage
 13:14:44:632:  kpowersave::showProgressDialog
 13:14:44:675:  filter_function::SIGNAL=Progress
 13:14:44:675:  filter_function::VALUE=40|unloading module: uhci_hcd
 13:14:44:675:  pDaemon::processClientMessage
 13:14:44:675:  kpowersave::showProgressDialog
 13:14:44:910:  filter_function::SIGNAL=Progress
 13:14:44:910:  filter_function::VALUE=40|unloading module: usblp
 13:14:44:910:  pDaemon::processClientMessage
 13:14:44:910:  kpowersave::showProgressDialog
 13:14:44:931:  filter_function::SIGNAL=Progress
 13:14:44:931:  filter_function::VALUE=50
 13:14:44:931:  pDaemon::processClientMessage
 13:14:44:931:  kpowersave::showProgressDialog
 13:14:47:358:  filter_function::SIGNAL=Progress
 13:14:47:358:  filter_function::VALUE=60|syncing file systems
 13:14:47:358:  pDaemon::processClientMessage
 13:14:47:358:  kpowersave::showProgressDialog
 13:14:50:352:  filter_function::SIGNAL=Progress
 13:14:50:352:  filter_function::VALUE=101
 13:14:50:352:  pDaemon::processClientMessage
 13:14:50:352:  kpowersave::showProgressDialog
 13:14:50:365:  kpowersave::closeProgressDialog()
 13:14:50:365:  filter_function::SIGNAL=Screenlock
 13:14:50:365:  filter_function::VALUE=global.suspend2ram
 13:14:50:365:  pDaemon::processClientMessage
 13:14:50:365:  kpowersave::lockscreen_on_lockEvent
 13:15:01:923:  filter_function::SIGNAL=PowersaveEvent
 13:15:01:923:  filter_function::VALUE=global.resume.suspend2ram
 13:15:01:923:  pDaemon::processClientMessage
 13:15:01:923:  Powersave Event: 'global.resume.suspend2ram'
 13:15:01:923:  kpowersave::set_suspend_type
 13:15:01:923:  kpowersave::setAutoSuspend
 13:15:01:924:  kpowersave::update
 13:16:04:657:  kpowersave::updateTooltip



Regards,
Simon



On Mon, 30 Jan 2006, Danny Kukawka wrote:

> Hi,
>
> On Monday 30 January 2006 12:03, Simon Hjorth Bøggild wrote:
> > I'm running powersave version 0.11.6 with kpowersave version 0.5.4 on Arch
> > Linux with Kernel 2.6.15, KDE 3.5.
>
> Fine ... what kind of package format use Arch Linux? RPM or DEP? Did you
> compile KPowersave by your self?
>
> > The Kpowersave seems to be working fine, it reports battery/ac status,
> > cpu frequency policy and current active scheme (performance, powersave
> > etc.). However, when I configure the current active scheme (i.e.
> > performance) to Suspend to Ram after say 1 minute of inactivity, nothing
> > happens, it never Suspends to ram. If I on other other hand, explicitly
> > choose the "Suspend to Ram" option in the Kpowersave menu, my computer
> > does indeed Suspend to Ram immediately and correctly and also comes back
> > up again when I want to.
> > My question is, why does the Actions on inactivity seem to have no effect?
>
> Maybe a program from the blacklist is running. You maybe can try to enable a
> scheme specific blacklist and don't add a program there.
>
> I checked this here at my machine and all worked as espected (Btw. please
> note: there is a difference between set time in configure dialog and the real
> time before suspend (max. +30sec))
>
> > can I enable some debugging somehow to see if Kpowersave actually tries to
> > suspend my computer, but fails (which would be strange, since it works
> > fine when doing it explicity also from Kpowersave), or is it a matter of
> > kpowersave not recognizing inactivity?
>
> You could kpowersave recompile with --enable-debug-msg and start kpowersave
> then from console to see all debug messages.
>
> > I previously used Klaptop with no problems (also on inactivity)
> > Other information: hal version 0.5.6, dbus version 0.50
>
> Cheers,
>
> Danny
> _______________________________________________
> powersave-devel mailing list
> [email protected]
> http://forge.novell.com/mailman/listinfo/powersave-devel
>
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel

Reply via email to