Re: [powersave-devel] Re: [PATCH} powersave-0.9.25: powersaved use 100% cpu
Hi,
thanks for the patch.
If you builded powersave for ALT Linux, could you also build a rpm package for
ALT Linux, which we can release on Novellforge/Sourceforge?
Have you also tried to build KPowersave?
Rgds,
Danny Kukawka
On Thursday 21 July 2005 08:38, Anton Farygin wrote:
> On Thu, 21 Jul 2005 10:06:15 +0400, Anton Farygin wrote:
> > Hi !
> >
> > I'm build powersave-0.9.25 for ALT Linux and resolve bug into powersaved
> > polling code (incorrect timespec calclualtion for poll interval).
> >
> > With this patch powersaved works fine.
>
> oops.
>
> corrected patch:
>
> diff -urN powersave-0.9.25.orig/daemon/powersaved.cpp
> powersave-0.9.25/daemon/powersaved.cpp ---
> powersave-0.9.25.orig/daemon/powersaved.cpp 2005-03-19 18:36:52 +0300 +++
> powersave-0.9.25/daemon/powersaved.cpp 2005-07-05 20:10:28 +0400 @@
> -504,12 +504,13 @@
> req.tv_usec = 0;
> }
> else {
> - req.tv_sec = config->current_scheme->POLL_INTERVAL
> / 1000 - - process_time / (1000*1000);
> - req.tv_usec =
> (config->current_scheme->POLL_INTERVAL * 1000 % 100) -
> - process_time % (1000*1000);
> + struct timeval timedec;
> + req.tv_sec = config->current_scheme->POLL_INTERVAL
> / 1000; + req.tv_usec =
> (config->current_scheme->POLL_INTERVAL * 1000 % 100); +
> timersub(&tv_stop,&tv_start,&timedec);
> + timersub(&req, &timedec, &req);
> pDebug (DBG_DEBUG, "Needed %lu sec and %lu usec
> time to process functions after select\n", -
> process_time / (1000*1000), process_time % (1000*1000)); +
> timedec.tv_sec,timedec.tv_usec);
> }
> }
> }
>
>
> ___
> powersave-devel mailing list
> powersave-devel@forge.novell.com
> http://forge.novell.com/mailman/listinfo/powersave-devel
___
powersave-devel mailing list
powersave-devel@forge.novell.com
http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] get no button.* from powersave via D-BUS
Hi, now the events and notifications from powersave via D-BUS for KPowersave is implemented. Thanks again to Holger. Also set schemes works now, had to add a new function to send needed action. (Must at least fix the suspend screen.) But now to the point of this mail: While testing kpowersave I never got a button.*.* event. Looks like them never emitted. I get only the related ACPI event but nover a related powersave event. Also checked with dbus-monitor, no event emitted. This must fixed, without the button.lid.close event KPowersave can't lock the screen. cheers, danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] get no button.* from powersave via D-BUS
On Friday 05 August 2005 07:21, Danny Kukawka wrote: > Hi, > > now the events and notifications from powersave via D-BUS for KPowersave is > implemented. Thanks again to Holger. Also set schemes works now, had to add > a new function to send needed action. (Must at least fix the suspend > screen.) > > But now to the point of this mail: While testing kpowersave I never got a > button.*.* event. Looks like them never emitted. I get only the related > ACPI event but nover a related powersave event. Also checked with > dbus-monitor, no event emitted. UPDATE: button.sleep is emitted Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] progress messages
Hi, more testing, more bugs! ;-) In the powersave dbus specifications a progress message is defined as: Return types: 0 string: Progress description 1 int32: Progress But powersave emit "same" messages as like as in powersave with sockets: e.g. * "10" or * "20|Raceaward for Jo!" This must be fix, or the spec must be rewritten. Need a reliably fact about the messages. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] making the debug messages shorter
On Friday 05 August 2005 20:03, Stefan Seyfried wrote: > still some of the messages are too long for my terminal, but it is a big > better. Also i wondered if it really makes sense to _not_ print function > and linenumber at levels info and debug, since if you need this great > detail, the function and linenumber would fit in well. I wondered also. I would prefer also to know the file. Something like this: syslog(LOG_ERR, "[E] %s:%d: %s", string, __FILE__, __LINE__, __FUNCTION__, ## args) > In fact, there are already many debug messages of the type > > pDebug(DBG_DEBUG, "%s", __FUNCTION__); > > so this is apparently actually needed ;-) > > If there are no objections, i'd like something like this to get in. Come on! ;-) Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] rip out "-a" (ACCESS_MODE)
On Friday 05 August 2005 20:44, Stefan Seyfried wrote: > Hi, > > i am on the train and had nothing to do, so here it is: > rip out the resmgr/group/etc access control. > This may help getting this going, i'll probably not commit it since it > is incomplete (e.g. checkPermissions() probably should go away completely). > But a little bit of the long boring stuff is done ;-) To rip out the resmgr support sounds good for me and make the code/powersave more portable/attractive for other distributions. nice! Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] making the debug messages shorter
On Saturday 06 August 2005 22:53, Stefan Seyfried wrote: > Danny Kukawka wrote: > > I wondered also. I would prefer also to know the file. Something like > > this: > > > > syslog(LOG_ERR, "[E] %s:%d: %s", string, __FILE__, __LINE__, > > __FUNCTION__, ## args) > > but this makes the lines even longer, not shorter :-) > We could put something like this in a configure --enable-verbose-debug, > so we can use it in a experimental build but disable in official releases. Yes, I know, this makes the lines a littlebit longer, but also more informatively. I would replace WARNING, ...,ERROR with [W], ..., [E] and remove the '()' anyway. But maybe also the messages self are to long?! We could maybe add a new debug level for this, but a configure option is also o.k. for me. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [Fwd: Memory leak in kpowersave when switching from AC to battery mode?]
On Tuesday 09 August 2005 09:01, Thomas Renninger wrote: > We have to run powersave/kpowersave in valgrind before sending out > this time. > > Tracking this one down for 9.3 shortly before 10.0 is bad, we all have a > lot work to do? This wasn't find, because nobody has this problem ever befor. Thats the point! If there where such problems we would have already get bugreports from the suse-laptop mailinglist or SUSE people. And I can't reproduce such memory leak with 9.3 and the 9.3 KPowersave version. The 30 MB of memory for KPowersave is full normal (discussed this with Adrian for shipping 9.3 version). This is shared memory (e.g. kdelibs etc). And after suspend to disk and resume all is normal for me and kpowersave consume the same shared memory as before, the same if I remove and plug in the ac adapter very often. > I have a feeling that this comes from scheme fetching code which should > have been elemintated from Holger ... I'm not sure about this, but *feel* don't help. Can you reproduce this? I can't see a memory leak or reproduce it. Cheer, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: CVS commit to /cvsroot/powersave/powersave/daemon by hmacht
On Wednesday 10 August 2005 11:56, Thomas Renninger wrote: > Stefan Seyfried wrote: > > Thomas Renninger wrote: > >>>I don't think so. Maybe I think my mashine is on power and suddenly the > >>>light goes out. > >> > >>If you assume online the light should go on, or? > > > > not necessarily. Due to a hal bug (fixed) my machine always told me AC > > was on although i had forgotten to plug it in. Since i was "online", i > > did not get any warning about battery state and suddenly the light went > > off. > > > > This is an important part which i never thought about before: > > > > If battery is (low|warning|critical) and we are (offline|unknown), > > notify the user. Right now, we only notify if we are offline, but not if > > online or unknown (which is "assume online"). > > Good point. > But be careful, you possibly have to touch other code parts where > I expected ac to only be ONLINE/OFFLINE in daemon/* code. > Maybe also in kpowersave... for kpowersave: no, I reported this problem and I would know if the state of AC is unknown e.g. if maybe HAL is down. In this case kpowersave can try to get the AC state from /proc/acpi. It's IMHO always better to set such things to unknown if unknown and not to dupe a (wrong) state Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: CVS commit to /cvsroot/powersave/kpowersave/po by dkukawka
On Friday 19 August 2005 13:04, Thomas Renninger wrote: > [EMAIL PROTECTED] wrote: > > CVS commit to /cvsroot/powersave/kpowersave/po by dkukawka > > > > Added Files: > > Tag: DBUS_INTEGRATION > > Hmm, you should have tagged it the other way (WITHOUT_DBUS_INTEGRATION), > now we have to merge this back to head. > I just wanted to have a look at the sources and was quite astonished that > head is still using the old interface ... > Anything planned to get CVS head to current implementation? This was the way we choose to add the DBUS things. We planed to merge this changes to head if we ship the final version for 10.0 Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Suggestions for Powersave and KPowersave
On Thursday 25 August 2005 14:33, Mark Hellman wrote: > Regarding KPowersave, when the laptop is plugged in, KPowersave could show > the time remaining until charged, just like 'acpi -V' does. The tooltip > could show, for example, the following info: > Plugged in -- 97% charged -- 6:52 minutes until charged -- 600 MHz > instead of just > Plugged in -- 97% charged -- battery is charging -- 600 MHz > > The time remaining until the battery is fully charged is an useful > information for most users. Hi, thanks for you proposal. I think, we do this with the new upcommig version with HAL and DBUS support for powersave/KPowersave. We are currently busy with porting and changing both for the next openSUSE release. If it should not work with upcoming version, we fix this after openSUSE 10.0 final. Did you tested one of the actual openSUSE Beta? Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Suggestions for Powersave and KPowersave
On Thursday 25 August 2005 18:33, Mark Hellman wrote: > Danny Kukawka wrote: > > Did you tested one of the actual openSUSE Beta? > > Not yet. But I plan to test it in the next couple of days. > > And what about the wireless power management? Do you think it makes sense? If you need it you can maybe add this to /etc/sysconfig/powersave/events , we need to discuss if it make sense to add this generally. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Suggestions for Powersave and KPowersave
On Thursday 25 August 2005 23:20, Holger Macht wrote: > On Thu 25. Aug 18:25:36, Danny Kukawka wrote: > > On Thursday 25 August 2005 14:33, Mark Hellman wrote: > > > Regarding KPowersave, when the laptop is plugged in, KPowersave could > > > show the time remaining until charged, just like 'acpi -V' does. The > > > tooltip could show, for example, the following info: > > > Plugged in -- 97% charged -- 6:52 minutes until charged -- 600 > > > MHz instead of just > > > Plugged in -- 97% charged -- battery is charging -- 600 MHz > > > > > > The time remaining until the battery is fully charged is an useful > > > information for most users. > > > > Hi, > > > > thanks for you proposal. > > > > I think, we do this with the new upcommig version with HAL and DBUS > > support for powersave/KPowersave. > > > > We are currently busy with porting and changing both for the next > > openSUSE release. If it should not work with upcoming version, we fix > > this after openSUSE 10.0 final. > > I think this should be easy to implement in kpowersave. Powersave already > provides this information. I will try to implement it for Beta4 of > openSUSE. I checked this again and it's already implemented since HAL compute the remaining time until battery is full changed. It worked out of the box. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Suggestions for Powersave and KPowersave
On Friday 26 August 2005 10:44, Holger Macht wrote: > > I checked this again and it's already implemented since HAL compute the > > remaining time until battery is full changed. It worked out of the box. > > And does hal also estimate the remaining charging time if the present rate > is not available? > > Danny, you can simply use BatteryRemainingTime method. The returned value > will either be the time until the battery is empty or the time until > battery is fully charged. I think we do exactly this currently, so we don't need to change annything ;-) Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Suggestions for Powersave and KPowersave
On Friday 26 August 2005 10:49, Anton Farygin wrote: > Great ! > > Danny, where possible download current unstable version ? only from CVS ? > > I plan build it for ALT Linux Sisyphus (unstable ALT Linux repository) > after hal-0.5.4 release. (for testing) I pre-decided with David Zeuten to make today the next HAL release. I add over the weekend new packages for KPowersave and powersave to the Novell- and Sourceforge homepage of the project. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Suggestions for Powersave and KPowersave
On Friday 26 August 2005 13:16, Stefan Seyfried wrote: > Danny can tell you more about the hal > stuff (hal also has to wait for acpid to reappear and not grab > /proc/acpi/event), but IIUC most of those patches are submitted back > upstream. All patches are pushed upstream and should be in the 0.5.4 release. ;) Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] inline functions from daemon/cpufreq.cpp
On Friday 02 September 2005 15:24, Anton Farygin wrote: > i compile current powersave CVS (HEAD) for ALT Linux Sisyphus and see > error (gcc 3.4): > g++ -Wall -DHAVE_SYSLOG_H -DDEBUG -g -O2 -o .libs/powersaved acpi.o apm.o > config_pm.o cpufreq.o cpufreq_userspace.o cpufreq_kernel.o event.o > general_config.o powersaved.o scheme_config.o clientConnection.o > event_management.o stringutil.o dbus_server.o brightness.o > ../libpower/.libs/libpowersave.so > ../libpower/.libs/libpowersave_clientsocket.so > ../libpower/.libs/libpowersave_dbus.so -Wl,--rpath -Wl,/usr/local/lib > cpufreq_userspace.o(.text+0x24f): In function > `CPUFreq_Userspace::initFreqsViaFile()': > /usr/lib/gcc/i586-alt-linux/3.4.4/../../../../include/c++/3.4.4/bits/basic_ >string.h:1456: undefined reference to `read_line(char const*, char*, > unsigned int)' > > After moving inline functions body to cpufreq.h - powersave daemon > compliled without a errors. > > This is correct ? Which state of the CVS? Did the CVS from tag VERSION_10_10_0 works for you? If not, pleas send a patch with the changes. Thanks. Cheers, Danny ps: current packages are available for powersave and KPowersave: http://sourceforge.net/projects/powersave/ ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: inline functions from daemon/cpufreq.cpp
On Friday 02 September 2005 16:52, Anton Farygin wrote: > This is correct ? I'm not sure if this is correct to move the code from cpp to header file. I think we should remove the inline definition and use normal functions instead of inline. Inline is a replacement for time critical macros and this is also only a proposal for the compiler. I didn't take a deeper look in the code. Don't see currently a reason why not use a normal function here. > >>> Which state of the CVS? > >> > >> HEAD > >> > >>> Did the CVS from tag VERSION_10_10_0 works for > >>> you? If not, pleas send a patch with the changes. Thanks. > >> > >> may be VERSION_0_10_10 ? > >> > >> Permissions denied for anonymous :-( > >> > >> $ cvs up -rVERSION_0_10_10 > >> Password: cvs [server aborted]: cannot write > >> /cvsroot/powersave/CVSROOT/val-tags: Permission denied > > > > What the ... is that? > > Anonymous user cannot checkout TAGS? Not needed too assign a bug. This need to long until a fix is there. ;) We should contact them directly. The tagged version of (K)powersave is available as tar.bz2 at sf.net. > > We need to assign a bug to the forge project ... > > > > Could you please send a patch for HEAD then. There shouldn't be any > > changes in this area recently. > > attached. Did you tried to remove the inline mark? Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Suggestions for Powersave and KPowersave
On Monday 05 September 2005 01:30, Mark Hellman wrote: > Danny Kukawka wrote: > >> I think this should be easy to implement in kpowersave. Powersave > >> already provides this information. I will try to implement it for Beta4 > >> of openSUSE. > > > > I checked this again and it's already implemented since HAL compute the > > remaining time until battery is full changed. It worked out of the box. > > Danny, I am not sure what do you mean by "it worked out of the box", but I > have just tried Beta4 and KPowersave still is not showing the time remaning > until charged (when plugged in). Instead, it is showing a rather irrelevant > and potentially misleading information: the time remaning until DISCHARGED > (when plugged in). Hm ... worked for me, what say cat /proc/acpi/battery/*/* while charging? Maybe you present rate is unknown. If so we have a little bug in powersave, where powersave not set the key to -1 or 0 if HAL not provides the related key. Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Suggestions for Powersave and KPowersave
On Monday 05 September 2005 11:09, Danny Kukawka wrote: > Hm ... worked for me, what say cat /proc/acpi/battery/*/* while charging? > Maybe you present rate is unknown. If so we have a little bug in powersave, > where powersave not set the key to -1 or 0 if HAL not provides the related > key. As discussed with Holger, this looks like a problem in powersave and not in HAL. Holger analyse the problem currently Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] [RFC] Testsuite for powersave
Hi, I think we need a testsuit for powersave to simulate all the broken ACPI/APM battery cases. For this I would propose this points: - add a configure option to change the path of /proc/acpi for powersave - add a testarchive with preferably all cases of working and broken acpi battery entries/files with different states for proc. - add a little program/script to run all the testcases, read values from powersave and write a testlog. - add a testlog with correct values for easy compare the values We should implement this post the release of openSUSE 10.0. Any other ideas? Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Notify method in Beta4
On Thursday 08 September 2005 17:56, Holger Macht wrote: > On Thu 08. Sep 16:18:34, Mark Hellman wrote: > > In Beta4, powersave notifications in KDE are shown, not only on a yellow > > tooltip, but also on a Kwrited window. > > In previous versions, the Kwrited window was not shown (which I suppose > > is the normal behavior). Is this a bug in Beta4? > > No. It was a bug in previous versions that it was not shown before. The > kwrited window appears because we use the wall command to notify users on > konsole. Maybe we should remove this bahaviour by default in future. As > long as this does not happen and you are annoyed of it, you can set the > variable NOTIFY_METHOD in /etc/sysconfig/powersave/common to > "notify_popup_window" and so overwriting "notify_console". Did we not add a special connect typ to get also notification messages? Is this no longer in powersave? No way for powersave to detect if there is a client which wait for notifications? In this case powersave should not open a windows in KDE. Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] [Request] translator for Russian language file (and uk, tr, sk, sv)
Hi all! As me Ines from the translation team told we have currently no active translator for Russian language. Same problem with this languages: - Ukrainian (uk.po) - Turkish (tr.po) - Slovak (sk.po) - Swedish (sv.po) If anybody know somebody for translate or see a possible way to get updated po-file, let me know. The related files are available her: http://forge.novell.com/modules/xfmod/cvs/cvsbrowse.php/powersave/kpowersave/po/ Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] [INFO] Added ML to tracker on projectsites at sf.net and forge.novell.com
Hi, We added the mailinglist as recipient for all tracker (Bug Tracking System, Tech Support Tracking System, Patch Tracking System, Feature Request Tracking System) and the forum at sf.net to inform about new posts there. If we get anytime to much posts, we add a new mailinglist for this. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: [Request] translator for Russian language file (and uk, tr, sk, sv)
On Tuesday 20 September 2005 11:32, Anton Farygin wrote: > Translation to Russian attached. Thanks, I added the file to CVS. I plan to release a new package at sf.net next week. Cheers, Danny > Rgds, > Anton ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Bugs in Powersave/KPowersave on SuSE 10.0
On Friday 14 October 2005 15:28, Mark Hellman wrote: > BUG 1 > I have installed SuSE 10.0 on two laptops. And one of the first things I > noticed on both of them was that, unlike on previous SuSE versions, > kpowersave did not react immediately to changes in battery charging state. > In other words, when I pull the plug, kpowersave takes about 30 seconds > till it shows that the laptop is running on battery. The same delay happens > when I plug it in. On previous versions, kpowersave took about 1 second to > show the state change... This is a known bug in HAL on SUSE related to receive and forward ACPI events from acpid. There is already a YOU Update for HAL in the pipe and should be available in the next days. Danny P.S. I will answer the second bug in a new mail, need to check first. ;) ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Bugs in Powersave/KPowersave on SuSE 10.0
On Friday 14 October 2005 15:28, Mark Hellman wrote: > BUG 2 > When the laptop is plugged in, kpowersave shows an info like the following: > Plugged in -- 54% charged (1:37 remaining hours) -- battery is charging > ... > > "1:37 remaining hours" until what?... Not until full charge as one might > think, but actually until discharge. > I have already brought this subject to this list one month ago. Then Danny > Kukawka wrote: > «I checked this again and it's already implemented since HAL compute the > remaining time until battery is full changed. It worked out of the box.» Could it be that this value never change? I saw this here and it looks like a bug in KPowersave at the moment. If you stop KPowersave and restart while the machine is charging the tooltip is correct (no time is displayed). I take a look at this. > I am not sure what Danny meant by "worked out of the box". If the context > was kpowersave, I am afraid it still does not work as expected. I thought we read this value from HAL, but we don't do this in powersave. We maybe should implement this and read the remaining time to charge from there, but you can also start and compile powersave without HAL, for this case we must implement this generally in powersave. Holger: any ideas or plans? Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Bugs in Powersave/KPowersave on SuSE 10.0
On Monday 17 October 2005 08:22, Anton Farygin wrote: > On Fri, 14 Oct 2005 16:20:05 +0200, Danny Kukawka wrote: > > This is a known bug in HAL on SUSE related to receive and forward ACPI > > events from acpid. There is already a YOU Update for HAL in the pipe and > > should be available in the next days. > > This bug also reproduced on ALT Linux with hal-0.5.4. Is there a open Bugzilla for ALT Linux where I can take a look at the problem, or could you send be the bugreport? I would take a look at the problem. You maybe would like to take a look at the current acpid package of SUSE, we fixed several bugs (like file descriptor leaks) in acpid [1]. Cheers, Danny [1] ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/acpid-1.0.4-9.2.src.rpm ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Bug in powersave/libpower/hal.c
Hi Holger and seife! There is IMO a bug in the hal code in powersave. We never check if the devices from HAL detected with capability 'battery' are APM/ACPI batteries. With the current code it could happen, that we also read UPS instead of APM/ACPI batteries. After reading all batteries with capability 'battery', we need to check which type the battery is. Check for this the property battery.type and use only devices with 'primary' (for UPS devices this is 'ups'). I take a look at this, but not before wednesday. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [ powersave-Bugs-1353119 ] cpufreq unreliable with Athlon64 X2 (dual core)
Hi Holger and Thomas! Can somebody of you take a look at this bug? The guy also submitted a patch to the sf.net bugzilla. Would be nice if you could check the patch, comment the patch and/or commit to CVS (and close the bug.). Thanks, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Debian packaging effort and some more general remarks
On Tuesday 15 November 2005 10:19, Holger Macht wrote: > > kpowersave: > > > > 1.) [0.4.5/0.5.0] Please distribute the autotools generated files with > > the tarball. The easiest way to achieve that is to use "make dist". > > This should be no problem because make dist should work with newer > versions of kpowersave No Holger, this does not work at the moment with kpowersave, we need to fix this for make dist and make distcheck. > > For this > > 2.) [0.4.5] set the correct version in configure.in.in (AM_INIT_AUTOMAKE) We do this already for the newer versions. > > 3.) [0.4.5/0.5.0] build path != source path not possible (make install > > fails). Fix: See attachement absolute_build_path_fix.diff > > Thanks for the patch. I take a look at this > > 5.) [0.4.5/0.5.0] Dependency to old Qt1/Qt2 headers, e.g. qvector.h. > > Imo it would be a good idea to use the Qt3 counterparts. o.k. I removed the included header. Was not needed. Do you know which other headers are obsolete? Is there a way to check this automatically? > > 6.) [0.4.5/0.5.0] Path to sound files in settings dialog is hard coded > > to /opt/kde. Please use @prefix@ and respect the path that is already > > set, i.e. if the use has set e.g. /usr/share/sounds/bla/blub.ogg start > > with path /usr/share/sounds/bla/ and *not* the default path. > > > > 7.) [0.4.5/0.5.0] Use KDialogBase for settings dialog. That way the user > > settings are used (icons on buttons etc.) > > > > 8.) [0.4.5/0.5.0] If battery runs out I get xmessages that a powersaved > > event was received with no further informations. That is pretty useless > > imo. Hm, I never got this. What exactly was the message? Maybe a problem with powersave and sending a empty message?! > Do you look at these issues danny? Yes, I take a look at this. > > 10.) [0.9.25/0.10.19] AUTHORS, ChangeLog, TODO, NEWS empty or missing. > > I will add contents to the AUTHORS file. > > NEWS? We have none ;-) We try to file news items to sourceforge or > forge.novell.com regulary. I think it is pretty useless to have them > multiple times at different locations. Btw. would be nice to have this file also in the package. Maybe like at HAL informatation about the release and changes. > > 23.) [0.10.19] What is the minimum required version for hal > > (configure.ac only checks the min version for dbus) > > I'm not exactly sure about this. But 0.5x is not mandatory needed IMHO. I > hope Danny can tell us when the api changed the last time. If there are > unsupported information in ealier version, this should not matter because > then the information would simply not be available. Last big API change was 0.5.x . Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Debian packaging effort and some more general remarks
On Tuesday 15 November 2005 12:29, Danny Kukawka wrote: > On Tuesday 15 November 2005 10:19, Holger Macht wrote: [...] > > > 3.) [0.4.5/0.5.0] build path != source path not possible (make install > > > fails). Fix: See attachement absolute_build_path_fix.diff > > > > Thanks for the patch. > > I take a look at this Commited to CVS HEAD. Thanks for the patch. > > > 6.) [0.4.5/0.5.0] Path to sound files in settings dialog is hard coded > > > to /opt/kde. Please use @prefix@ and respect the path that is already > > > set, i.e. if the use has set e.g. /usr/share/sounds/bla/blub.ogg start > > > with path /usr/share/sounds/bla/ and *not* the default path. Fixed in CVS HEAD. > > > 7.) [0.4.5/0.5.0] Use KDialogBase for settings dialog. That way the > > > user settings are used (icons on buttons etc.) For the hole configure dialog or for which dialogs? > > > 8.) [0.4.5/0.5.0] If battery runs out I get xmessages that a powersaved > > > event was received with no further informations. That is pretty useless > > > imo. > > Hm, I never got this. What exactly was the message? Maybe a problem with > powersave and sending a empty message?! I work on this issue. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Debian packaging effort and some more general remarks
On Friday 02 December 2005 19:57, Danny Kukawka wrote: > On Tuesday 15 November 2005 12:29, Danny Kukawka wrote: > > On Tuesday 15 November 2005 10:19, Holger Macht wrote: [...] > > > > 8.) [0.4.5/0.5.0] If battery runs out I get xmessages that a > > > > powersaved event was received with no further informations. That is > > > > pretty useless imo. > > > > Hm, I never got this. What exactly was the message? Maybe a problem with > > powersave and sending a empty message?! Hm ... I noticed it first now, but was this really a xmessage or a KDE dialog? If it was xmessage, this is really a powersave problem. We don't display xmessages from kpowersave, we do this only in powersave, but this should not happen if there is KPowersave connected to powersave. Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Debian packaging effort and some more general remarks
On Saturday 03 December 2005 17:03, Michael Biebl wrote: > Danny Kukawka wrote: > > On Tuesday 15 November 2005 12:29, Danny Kukawka wrote: > >> On Tuesday 15 November 2005 10:19, Holger Macht wrote: [...] > >>>> 8.) [0.4.5/0.5.0] If battery runs out I get xmessages that a > >>>> powersaved event was received with no further informations. That is > >>>> pretty useless imo. > >> > >> Hm, I never got this. What exactly was the message? Maybe a problem with > >> powersave and sending a empty message?! > > > > I work on this issue. > > I checked it again an you are right, if kpowersave is connected, a KDE > dialog is shown and not a xmessage dialog box. Nevertheless it still has > some issues (please take a look at the picture [1]): > 1.) A dialog box *and* a notification area message is shown. I would > prefer if only the latter is shown. Yes I see this problem and we know such problems at the moment, if kpowersave is not connected to powersave. Which KPowersave/powersave version do you use currently? > 2.) The message shown in the notification area message is incorrect. I > set up powersaved to send a message when 10% of the battery level is > reached. KPowersave reports that only 0hours, 0 minutes are remaining, > which is obviously incorrect. Is the menu in KPowersave complete in this case and is powersave running? What say 'powersave -bB' in this case? Could you send me all your configurationfiles of you powersave installation (directly and not over the list.) > 3.) A small typo in the german translation: Minute(n) and not Minutei(n). Fixed this in CVS. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] New commit mailinglist
Hi, I added a new mailinglist for the SVN commit mails. You can subscribe under: http://forge.novell.com/modules/xfmod/maillist/subscribe.php?group_id=1438&list=powersave-commit For all which are currently in the direct SVN commit notification list: If you subscribe I would remove you from there to prevent dubs. Let me know if this is a problem for you. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: New commit mailinglist
On Monday 12 December 2005 17:38, Danny Kukawka wrote: > Hi, > > I added a new mailinglist for the SVN commit mails. You can subscribe > under: > > http://forge.novell.com/modules/xfmod/maillist/subscribe.php?group_id=1438&; >list=powersave-commit or use: http://forge.novell.com/mailman/admindb/powersave-devel Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: New commit mailinglist
On Monday 12 December 2005 17:43, Danny Kukawka wrote: > On Monday 12 December 2005 17:38, Danny Kukawka wrote: > > Hi, > > > > I added a new mailinglist for the SVN commit mails. You can subscribe > > under: > > > > http://forge.novell.com/modules/xfmod/maillist/subscribe.php?group_id=143 > >8& list=powersave-commit Now the correct link: http://forge.novell.com/mailman/listinfo/powersave-commit Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: kpowersave - scheme settings
Hi,
On Tuesday 17 January 2006 23:15, Ferdinand Gassauer <[EMAIL PROTECTED]> wrote:
> KDE tries to use (mostly) positive questions.
>
> kpowersave has a mixture of enable/disable questions. disable IMHO should
> be changed to "enable" and get checked when appropriate.
> may be you want to rethink the design.
Hmm, The only checkboxes we IMO could change are the scheme specific
sound settings.
In the other cases ("Disable screen saver", "Disable display power
management") I see no way to change this, because we *need* here the
'Disable'-checkbox because we must overwrite the KDE/X settings you can make
in KControl or in the KScreensaver settings. IMO in this context a 'enable'
checkbox make no sense.
What do you think?
Cheers,
Danny
--
Danny Kukawka
[EMAIL PROTECTED]
Mobile Devices
SUSE LINUX a Novell Business
Maxfeldstr. 5, D-90409 Nuernberg, Germany
___
powersave-devel mailing list
powersave-devel@forge.novell.com
http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Fwd: Re: kpowersave - scheme settings
-- Forwarded Message --
Subject: Re: kpowersave - scheme settings
Date: Wednesday 18 January 2006 00:14
From: Ferdinand Gassauer <[EMAIL PROTECTED]>
To: Danny Kukawka <[EMAIL PROTECTED]>
On Tuesday 17 January 2006 23:21, you wrote:
> Hi,
>
> On Tuesday 17 January 2006 23:15, Ferdinand Gassauer <[EMAIL PROTECTED]>
wrote:
> > KDE tries to use (mostly) positive questions.
> >
> > kpowersave has a mixture of enable/disable questions. disable IMHO
> > should be changed to "enable" and get checked when appropriate.
> > may be you want to rethink the design.
>
> Hmm, The only checkboxes we IMO could change are the scheme specific
> sound settings.
>
> In the other cases ("Disable screen saver", "Disable display power
> management") I see no way to change this, because we *need* here the
> 'Disable'-checkbox because we must overwrite the KDE/X settings you can
> make in KControl or in the KScreensaver settings. IMO in this context a
> 'enable' checkbox make no sense.
>
> What do you think?
(Y) is checked
(N) is unchecked
It says
* (Y) Enable specific screensaver settings
** (N) Disable screensaver
.
** (N) Disable Powersettings
IMHO the result is the same but would be easier to read
* (Y) Enable specific screensaver settings
** (Y) Enable screensaver
.
** (Y) Enable Powersettings
I just think it's easier for the user to deal only with "enable"
> Cheers,
>
> Danny
--
--
cu ferdinand
___
powersave-devel mailing list
powersave-devel@forge.novell.com
http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [powersave - Help] RE: compile errors (gcc4)
-- Forwarded Message -- Subject: [powersave - Help] RE: compile errors (gcc4) Date: Friday 20 January 2006 00:08 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3531830 By: Danny Kukawka Upps ... we had some trouble with build this files in our buildsystem. Looks as this files are for a SUSE 10.1 Alpha instead of 10.0. (the failed dependencies are the result - this are new files from upcomming 10.1) We added a new (tested) release for SUSE 10.0. You need also update powersave and from the new 'Update requirements'-section: sysfsutils and cpufrequtils. I hope this help you. Danny __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [powersave - Help] RE: compile errors (gcc4) [FW]
-- Forwarded Message -- Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3531928 By: denisq now i can use the binaries, nice! i suppose i still won't be able to compile myself, but now it's not necessary anymore. just strange because i don't know what fails or what is missing on my system. by the way, is the brightness feature hardware dependend? keyboard shortcuts can change the brightness on my laptop, but i suppose that's controlled technically by the hardware? hm, that's a pity, it would have been useful to set the brightness to the schemes! __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [powersave - Help] RE: compile errors (gcc4) [FW]
-- Forwarded Message -- Subject: [powersave - Help] RE: compile errors (gcc4) Date: Friday 20 January 2006 01:54 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3531943 By: Danny Kukawka Sounds good. As I sad, I think you did not install one of the needed packages. I should work if you select in YaST the development and KDE-development selection. Yes, set brightness via the scheme depends currently on the capabilities of your hardware. We work currently on integration of the generic ACPI video interface in powersave to set brightness on machine which support this. On all other machines we have currently no support. What kind of machine is your laptop? __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Error after installing kpowersave in Ubuntu Dapper
On Friday 20 January 2006 16:04, cRoMo wrote: > Hi, > Firstable I want to say hello to everyone, especially > developers. I've been following retorical discussion between David and > Gnome-Power-Manager's developer Richard Hughes and I have to say that I > am disappointed with the latter project. Avoiding any flamewar, I just > want to say I like to have lots of configuration possibilites that GPM > doesn't provide and, on the other hand, powersaved + kpowersave duo do. > Also I agree that powermanagement should be handled by a seprate > daemon, as I am often running console-only ;-) > Anyway, I have a problem with getting powersave & kpowersave working. > Both don't give an access to powersaved that I know is running fine. > The problem (after running powersave -v 31 -x for example) is beeing > described in syslog as: From where did you get the Ubuntu files? From [3]? O.k. let see ... > Jan 20 15:52:47 kromka [powersave]: ERROR (dbusSendMessageGeneric:184) > Error: A security policy in place prevents this sender from sending > this message to this recipient, see message bus configuration file > (rejected message had interface "com.novell.powersave.request" member > "SchemesGet" error name "(unset)" destination "com.novell.powersave") Looks like a problem with the settings for the powersave dbus interface. > I don't know wheter it's a powersave[d] duo fault or a dbus fault, or > anything esle's in my bleeding edge Ubuntu Dapper. I was googling and > looking in mailing list a couple weeks backwards (sadly no search > option :(), but had no luck in fiding a explaination/solution to this > problem. I am using powersaved 0.11.2 and kpowersave 0.5.2. This is a new, never before reported problem. Could you check if there is a powersave.conf in your dbus dir (usually in /etc/dbus-1/system.d)? If so, please mail this file to the ML. If not please try to add the file from the sourcepackage [1] or the svn [2]. Cheers, Danny [1] http://prdownloads.sourceforge.net/powersave/powersave-0.11.2.tar.bz2?download tar -xjf powersave-0.11.2.tar.bz2 cd powersave-0.11.2/config_files/ cp dbus_powersave.conf /etc/dbus-1/system.d/powersave.conf [2] svn checkout svn+ssh://[EMAIL PROTECTED]/svn/powersave/trunk/powersave/config_files/ cp config_files/dbus_powersave.conf /etc/dbus-1/system.d/powersave.conf [3] http://www.teco.edu/~biebl/ubuntu ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Powersave daemon and KPowersave packages available for FC4
On Monday 23 January 2006 02:24, oleksandr korneta wrote: > on 01/22/2006 05:58 PM Holger Macht wrote: > > Should be no problem to use it on x86_64 architecture. I just have to > > find a x86_64 machine and setup FC4 on it. Hopefully I will have the time > > this week... > > ok, I've got some result. > First of all I've installed dbus-0.50 (rebuild from source rpm) > along with dbus-devel-0.50 and dbus-glib-0.50. Then I did the same with > hal and hal-devel upgraded these to version 0.5.6. Moreover, the src.rpm > of hal that I found wanted pm-utils >0.04, therefore I had to upgrade > that one too (I got version 0.06 also rebuild from src.rpm). Thus, > finally seems like all the dependencies for rebuilding powersave are > satisfied. > However when I try to do > rpmbuild --rebuild powersave-0.11.2-1.FC4.src.rpm > > somewhere in the end, when the compilation is almost over it gives me > some strange error. This is IMO a bug in the files section of the spec files for x86_64, where the lib is not in /usr/lib but in /usr/lib64/. Try to change this: %files -f power-management.lang %defattr(-,root,root) %_sbindir/* %_bindir/powersave %_prefix/lib/powersave %_mandir/*/* %config /etc/init.d/powersaved %config /etc/dbus-1/system.d/powersave.conf /etc/acpi/events.ignore/events.ignore /etc/powersave %_docdir/%name To this: %files -f power-management.lang %defattr(-,root,root) %_sbindir/* %_bindir/powersave %_libdir/powersave %_mandir/*/* %config /etc/init.d/powersaved %config /etc/dbus-1/system.d/powersave.conf /etc/acpi/events.ignore/events.ignore /etc/powersave %_docdir/%name Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 13:53 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541064 By: hulder Please check whether there is a directory /etc/dbus-1/system.d/ and if so post the content of powersave.conf in that directory. Regards, Holger __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 15:02 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541174 By: cjaegle There was no such file in /etc/dbus-1/system.d/, so I copied files from /usr/local/... to the corresponding directories (and /usr/local/(s)bin/powersave(d) to /usr/(s)bin. The init script returned many errors so I started /usr/sbin/powersaved, it seems to run (display got brighter ad I can see the entry in the process table), but I don't have any menu items in kpowersave, don't know why. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 15:09 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541185 By: hulder Please don't copy all those files. This will result in unexpected behaviour. So you found a powersave.conf in /usr/local/etc/dbus-1/system.d or something similiar? If so, it should be enough to only copy this file. So if the initscript does not work, please start the powersve daemon with: powersaved -v 3 -f /var/run/acpid.socket Please tell me the result. Regards, Holger __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 15:38 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541237 By: cjaegle Installed acpid first. Here the output in /var/log/messages: Jan 25 15:32:54 defiant [powersave]: ERROR (PM_Interface:87) Haldaemon not running. Battery or ac adapter information will not be available. Jan 25 15:32:54 defiant [powersave]: WARNING (initSingleInterface:100) Kernel ondemand governor not working, trying userspace instead Jan 25 15:32:54 defiant [powersave-set_disk_settings][23504]: ERROR: invalid function call: do_remounts '' Jan 25 15:33:09 defiant logger: ACPI group battery / action battery is not defined defiant system.d # ps aux |grep hald 102 23428 0.3 0.6 4684 3324 ?Ss 15:32 0:01 /usr/sbin/hald --use-syslog 102 23433 0.0 0.1 1740 676 ?S15:32 0:00 hald-addon-acpi 102 23443 0.0 0.1 1740 656 ?S15:32 0:00 hald-addon-storage __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 16:54 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541355 By: cjaegle Ah, there seems to be a problem with the user rights. When I start kpowersave as root, I can see the entries and powersave -c gives an correct output. Hm should I add the user to a special group? __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 16:14 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541295 By: cjaegle No not more entries. After some seconds there pops up a message which says that the powersave daemon isn't running. powersave - b gives a reasonable output. uncommented entries in /etc/acpi/events/default Thanks for your help so far. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 17:15 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541447 By: hulder Please post your /etc/dbus-1/system.conf. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 16:16 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541298 By: cjaegle No not more entries. After some seconds there pops up a message which says that the powersave daemon isn't running. powersave - b gives a reasonable output. uncommented entries in /etc/acpi/events/default Thanks for your help so far. Sry for wrong location of my postings __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 16:39 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541332 By: hulder Ok, so hal seems to be ok. Please do 'powersave -c' and tell me if the current cpufreq policy is printed. This assures that the connection to the powersaved can be established. Then we maybe have a problem with kpowersave... Now please also do: logger xx powersaved -v 15 -f /var/run/acpid.socket Now there should appear a line containing x in /var/log/messages. Please post the output starting from this line. Regards, Holger __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 18:32 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541832 By: cjaegle http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> system messagebus /var/run/dbus.pid EXTERNAL unix:path=/var/run/dbus/system_bus_socket system.d system-local.conf contexts/dbus_contexts __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] daemon doesn't start Date: Wednesday 25 January 2006 00:23 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3540168 By: cjaegle I'm using gentoo linux and the powersave daemon doesn't start. Tried the verbose option and I get following errors: (Many infos about empty values) [powersave]: ERROR (PM_Interface:87) Haldaemon not running. Battery or ac adapter information will not be available. [powersave]: ERROR (openSystemConnection:277) dbus_bus_request_name(): Error. (Connection ":1.15094" is not allowed to own the service "com.novell.powersave" due to security policies in the configuration file) [powersave]: ERROR (MainLoop:57) Error setting up connection to DBus system bus. Aborting... Hald and dbus are running. hal-0.5.5.1-r3 dbus-0.60-r3 Any ideas? __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 20:57 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3542110 By: hulder This looks good. The problem must be within the powersave dbus config file then. Please replace the content of /etc/dbus-1/system.d/powersave.conf with the following: ---snip- http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> -snip--- Regards, Holger __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Thursday 26 January 2006 00:23 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3542434 By: cjaegle Thank you very much, now it's running. One last question. I can only choose suspend to disk (not working now, but that's probably not related to this software), what do I have to do when I would like to have the possibility to select suspend to ram and standby? (When I remember correctly sus to ram worked a few weeks ago) __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Thursday 26 January 2006 00:35 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3542453 By: hulder For getting suspend to ram and standby (if supported) enabled, you have to change the variables DISABLE_USER_SUSPEND2DISK and DISABLE_USER_SUSPEND2RAM in the powersave sleep configuration file. For suspend to disk, you need a software suspend (not swsusp2) enabled kernel. Just a note: With the removed at_console policy in the dbus configuration file, any user logged in remote to your machine can suspend it. Maybe you know somebody from gentoo who you can ask if there is a replacement for at_console in gentoo? Now I would have a request. Would it be possible for you to summarize the outcomes of this thread and write a short guide how to get the powersave daemon and kpowersave running on gentoo? What needs to be installed, configuration etc. Maybe you can put it in the gentoo wiki and send it to me that we can also include it in our documentation. Just if you like. Regards, Holger __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Thursday 26 January 2006 15:25 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3543153 By: cjaegle Probably not the next few days but then I'l try to do ebuilds, never did this before, so I'm not sure if I will have success. Perhaps I can write some lines here what I did, but it's not gentoo specific, so it would be better if there were ebuilds for powersave and kpowersave and a short description of how to use them. Is the acpi daemon required for powersave(d)? __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Thursday 26 January 2006 15:28 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3543163 By: hulder Ebuilds would be great! Yes, acpid is required. And also hal, dbus and in recent versions cpufreq-utils. The problem with at_console _is_ system specific. It depends on what the system supports. SUSE and Fedora are the two I know they do. Thanks anyway, Holger __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Help request: KPowersave Translations
Hi, we added in the last days all needed strings for translation to KPowersave for the next stable release (v0.6.0) upcommig with SUSE 10.1 release. Now we need some help to translate all strings - currently the SUSE/Novell Language team is working on the translations, but the could not translate all files (as e.g. ru, uk). The current po files are available in the SVN [1]. I attach a file with the current state of translation for all languages. All help to translate the files would be really appreciated. In the next days I submit a new version of the kpowersave help/handbook to the SVN. Currently only 3 languages are supported (en,hu,no). Here we need also some more langugages. ;-) Thanks for your help and let me know if you plan to translate something. Cheers, Danny [1] http://forge.novell.com/modules/xfmod/svn/svnpage.php/powersave/ bg.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. cs.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. da.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. de.po:227 translated messages. el.po: 86 translated messages, 27 fuzzy translations, 117 untranslated messages. es.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. fi.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. fr.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. hu.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. it.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. ja.po:140 translated messages, 24 fuzzy translations, 66 untranslated messages. nb.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. nl.po:116 translated messages, 48 fuzzy translations, 66 untranslated messages. pa.po:127 translated messages, 24 fuzzy translations, 79 untranslated messages. pl.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. pt.po:139 translated messages, 25 fuzzy translations, 66 untranslated messages. pt_BR.po: 139 translated messages, 25 fuzzy translations, 66 untranslated messages. ru.po:133 translated messages, 25 fuzzy translations, 72 untranslated messages. sk.po: 31 translated messages, 49 fuzzy translations, 150 untranslated messages. sl_SI.po: 139 translated messages, 25 fuzzy translations, 66 untranslated messages. sv.po: 27 translated messages, 28 fuzzy translations, 175 untranslated messages. tr.po: 22 translated messages, 29 fuzzy translations, 179 untranslated messages. uk.po: 30 translated messages, 50 fuzzy translations, 150 untranslated messages. zh_CN.po: 139 translated messages, 25 fuzzy translations, 66 untranslated messages. zh_TW.po: 139 translated messages, 25 fuzzy translations, 66 untranslated messages. ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Thursday 26 January 2006 15:51 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3543196 By: cjaegle ah mom, I didnt' use your posted configuration file, I only changed send/recieve interface from deny to allow for default context policy. I did't change or remove at_console policy. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Thursday 26 January 2006 15:54 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3543200 By: hulder Yes, if you enable those for context default, it is enabled for default ;-) But on you system it is not sufficient to enable it for at_console. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] ADMIN: Sorry for confusing and resending messages
Hi, Sorry for resending this messages. We stopped automatic accept the mails from sourceforge forums to the devel list, because they are not correct threaded. I resended them to remove the not threaded from the archive. From now all sf.net mails will be send in this way. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [FW] [powersave-devel] [powersave - Help] daemon doesn't start
-- Forwarded Message -- Subject: [powersave-devel] [powersave - Help] RE: daemon doesn't start Date: Wednesday 25 January 2006 15:54 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3541258 By: hulder So does kpowersave show more menue entries now? I will go through the error messages step by step: 1 .ERROR (PM_Interface:87) Haldaemon not running. Battery or ac adapter information will not be available. If a 'powersave -b' or 'lshal' gives any reasonable output, you can ignore this message. It it caused by a check for a pidfile that can't be found. 2. WARNING (initSingleInterface:100) Kernel ondemand governor not working, trying userspace instead It seems that the userspace governor for cpu frequency scaling is working. Good. 3. ERROR: invalid function call: do_remounts '' Ignore it, it is already fixed in newer versions and does not cause any problems. 4. logger: ACPI group battery / action battery is not defined That is acpid throwing this error. If you are using the powersave daemon, you need no processing of acpi buttons anymore. Please make sure that /etc/acpi/events/ does not contain any rules. Additionally, the powersaved should have installed a /etc/acpi/events.ignore/events.ignore file. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [powersave - Help] RE: compile errors (gcc4) [FW]
-- Forwarded Message -- Subject: [powersave - Help] RE: compile errors (gcc4) Date: Friday 27 January 2006 01:39 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3544114 By: denisq an Acer TravelMate 2310! i use suse 10.0 and there are some differences: - i miss the cpu frequency policy - and the standby button, but that's not important at all! __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Fwd: kpowersave and backup applications
Hi all, This sounds interesting ... I answer him. Cheer, Danny -- Forwarded Message -- Subject: kpowersave and backup applications Date: Wednesday 18 January 2006 20:29:48 From: Jonathan Riddell <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Has anyone had experiences with kpowersave? It seems better maintained than the klaptopdaemon we use at the moment but I'm looking for experiences of whether it's more reliable or not. [...] Jonathan --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: Fwd: kpowersave and backup applications
-- Forwarded Message -- Subject: kpowersave and backup applications Date: Sun Jan 22 20:37:03 2006 From: Sebastian Kügler <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] On Wednesday 18 January 2006 21:29, Jonathan Riddell wrote: > Has anyone had experiences with kpowersave? It seems better > maintained than the klaptopdaemon we use at the moment but I'm looking > for experiences of whether it's more reliable or not. klaptopdaemon is quite horrible code-wise, so it's good to consider removing it. I've installed kpowersave today, and it seems quite nice. I'm using suspend2 [S2], however, together with the hibernate script, and I needed a quite hackish solution to be able to hibernate from kpowersaved. That bit is easier with klaptopdaemon. Also, it seems to have been written for SuSE, one of the warning dialogues I ran across mentions /etc/sysconfig/... which we of course don't have. Other than that, kpowersaved looks great, and I'd like to see it in Kubuntu Dapper. I think with some minor changes, it would be a nice replacement for klaptopdaemon, which is pretty much unmaintained. [S2] http://www.suspend2.net -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - When you're discussing code, often the best answer to criticism is a patch - not a dissertation. - Rik van Riel --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Fwd: kpowersave and backup applications
On Sun Jan 22 20:37:03 2006 Sebastian Kügler wrote: > On Wednesday 18 January 2006 21:29, Jonathan Riddell wrote: > > Has anyone had experiences with kpowersave? It seems better > > maintained than the klaptopdaemon we use at the moment but I'm looking > > for experiences of whether it's more reliable or not. Sound good for us as KPowersave/powersave developers. KPowersave is since years the default powermanagement fontend/solution under KDE on SUSE. We would be happy if KPowersave could also replace klaptop on an other distribution. ;-) > klaptopdaemon is quite horrible code-wise, so it's good to consider > removing it. Jupp ... ;-) > I've installed kpowersave today, and it seems quite nice. I'm using > suspend2 [S2], however, together with the hibernate script, and I needed a > quite hackish solution to be able to hibernate from kpowersaved. That bit > is easier with klaptopdaemon. We plan to add suspend2 support to the powersave daemon for future releases. > Also, it seems to have been written for SuSE, one of the warning dialogues > I ran across mentions /etc/sysconfig/... which we of course don't have. Yes, it was written for SUSE (But it's also available for ALT Linux, Debian, K/Ubuntu, Fedora and IMO somewhere for Gentoo). We work permanently on porting K/Powersave to other dists. Help would be really appreciated [1]. IMO the path for the powersave config files is configurable now with a configures switch, so you don't need to use /etc/sysconfig/ . > Other than that, kpowersaved looks great, and I'd like to see it in Kubuntu > Dapper. I think with some minor changes, it would be a nice replacement for > klaptopdaemon, which is pretty much unmaintained. If you have any patches send them to the powersave-devel mailinglist and we integrate them to the source for the next release. If you need any help to get KPowersave and powersave running on Kubuntu feel free to contact [1] or me directly. Cheers, Danny Kukawka P.S. Please CC me if you answer, I'm not subscriped to kubuntu-devel ML. [1] powersave-devel@forge.novell.com Danny Kukawka [EMAIL PROTECTED] ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Problem with Actions on inactivity
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 powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] kpowersave * powersave error?
On Tuesday 31 January 2006 16:56, Dawid Wróbel wrote: [...] > Also, when > I click on kpowersave icon that nice information dialog appears, > confirming the above and introducing small UI bug [1]. And there is no > cpufreq policy submenu when I right click on kpowersave's icon. [...] > > [1] http://cromo.klej.net/screen.png . The "running" text should be by > the "Powersave Daemon" text I fixed this bug for the next release. An other question: Could you translate the KPowersave strings (see the po file for your language in the source) for your language? All help for translation would be appreciated! ;-) Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] kpowersave * powersave error?
On Wednesday 01 February 2006 18:14, Dawid Wróbel wrote: > On Wed, 1 Feb 2006 17:36:12 +0100 Danny Kukawka > <[EMAIL PROTECTED]> wrote > > > An other question: Could you translate the KPowersave strings (see > > the po file for your language in the source) for your language? All > > help for translation would be appreciated! ;-) > > Actually I was planning this, but had to learn for exams and the last > one was today, so I am free by now to do some more pleasnt things ;) sounds great :-) > Should I translate it and send directly by email to you? Yes. Thanks and Cheers, danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: kpowersave - rights & autosuspend feature
Hi, On Thursday 02 February 2006 15:42, you wrote: > I'm trying to get kpowersave running under gentoo. > I've been running into two problems: > > 1. kpowersave only works if it has been started as root (with kdesu) IMO this is a gentoo problem with the permissions/settings of DBUS. Please take a look at the powersave-devel mailinglist [1]. There was already a gentoo user we helped to get powersave/kpowersave running [2]. If this doesn't help, write a mail to the list. > 2. the autosuspend feature doesn' t work. (may this be caused by the first > issue?) Not sure, may try first to get kpowersave running as normal user and retry then. > kpowersave is version 0.5.5, > powersaved is version 0.11.8 > hal is version 0.5.5.1 > dbus is version 0.60 > > Since the included initscript doesn't work under gentoo (will write one if > above problems are solved) I've just started powersaved as root from > commandline. Acpid is started and the cpufreq governors are loaded Powersave must run as root. A rc-script for gentoo would be nice. > I would be pleased if you could help me. Cheers, Danny [1] http://forge.novell.com/modules/xfmod/maillist/?group_id=1438 [2] http://thread.gmane.org/gmane.linux.power-management.powersave/245 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [SOLVED] Re: [powersave-devel] Re: kpowersave - rights & autosuspend feature
On Friday 03 February 2006 01:57, Michael Biebl wrote: > I found the bug that made kpowersave fail to properly autosuspend. > It's the path to the pidof binary, which is set to /sbin/pidof. But in > Debian and Gentoo it is /bin/pidof. So checkBlacklisted fails and > kpowersave does not generate a suspend event. > You can apply the patch which sets the correct path for Gentoo. good catch :-) > @Danny: Do you think it would be safe to assume /bin/pidof or should we > create a configure check? I take a look at this, I had no time in the last days, but I fix this for the next release. Thanks, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: po.pl translation file attached
On Thursday 02 February 2006 17:33, you wrote: > On Thu, 2 Feb 2006 15:18:44 +0100 Danny Kukawka > > <[EMAIL PROTECTED]> wrote: > > Thanks for the file. Currently there are 26 fuzzy translations left > > in the file and I think the most of them are incorrect (they are > > marked with '#, fuzzy') because they was only automatically merged. > > This strings are not translated in KPowersave if they marked as fuzzy. > > During translation I revised all the strings that were already > translated by previous translator and those fuzzy ones too. > Because I had no idea what does this "fuzzy" mark mean I left > these marks. The fuzzy mark is a mark from the automatically merge between existing language files and a updated pot file (which contains all translatable strings). If already existing strings in the po file are not changed in the pot files they are used without any changes (no mark set). But if the strings in the code are changed ore maybe new strings intruduced the merge tool try to check if there are maybe already translations. In this case this not 100% clear strings get the mark #fuzzy. In the most cases the translator need now check the strings and need only some litte changes to correct them. Btw. the qt/kde translation lib ignore this potential wrong strings. The mark is simply a help for the translator. One example for fuzzy string is: #: detailed_dialog.cpp:123 #, fuzzy msgid "kpowersave" msgstr "Oszczędzanie energii" The correct oen would be: #: detailed_dialog.cpp:123 msgid "kpowersave" msgstr "KPowersave" --> I fixed this one ;-) > So now it was just enough to remove them. Also I > made some corrections in my translations and translated that one line I > forgot to before. Hope it's fine now. Thanks for your help to translate KPowersave. > > > Thanks for your help, > > Thanks for this great piece of software :) ;-) Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [SOLVED] Re: [powersave-devel] Re: kpowersave - rights & autosuspend feature
On Friday 03 February 2006 23:19, Simon Hjorth Bøggild wrote: > This also solved my problem on Arch Linux, where pidof is also located in > /bin . Making a symlink allieviates the problem for me. Could you provide a pkg.tar.gz for Arch Linux which we could release on sf.net project page (if so, mail it directly to me)? Is there any kind of spec-files or script to create this package format? Thanks, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
FW: Re: [powersave-devel] [powersave - Help] RE: kpowersave and battery status problem
-- Forwarded Message -- Subject: [powersave - Help] RE: kpowersave and battery status problem Date: Tuesday 07 February 2006 04:40 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3562178 By: chevyou I disagree. I uninstalled my current powersave and kpowersave packages, rebooted the computer, and then reinstalled both packages from ftp://ftp.gwdg.de/pub/opensuse/distribution/SL-10.0-OSS/inst-source/, and still I have the same problem as erkac. The battery state is being improperly reported __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: FW: Re: [powersave-devel] [powersave - Help] RE: kpowersave and battery status problem
-- Forwarded Message -- Subject: [powersave - Help] RE: kpowersave and battery status problem Date: Tuesday 07 February 2006 04:47 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3562186 By: chevyou Edit from last message. This problem is temporarily fixed if I stop and restart the powersave daemon, but as soon as I reboot the problem returns __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: Localizaton of KPowersave for PT
Hi, Thanks for the files and the work. I added the new file and the changes to the SVN. The changes should be available in SUSE 10.1 RC1. Thanks and Regards, Danny On Tuesday 07 February 2006 13:49, you wrote: > Hi, > > this are the localization files for "pt" (European Portuguese) for > KPowersave. In the .desktop I only changed the "Comment[pt]" line. > > Hope it's all ok, sometimes the encoding for accented characters doesn't > work well. > > Keep up the great job. :-) > > Yours trully ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] dbus error message misleading in case of insufficient access rights
On Monday 13 February 2006 14:30, Michael Biebl wrote: > The same user had another problem. Because he did not read the complete > documentation, especially the Debian specific details, he missed the > part where the documentation says, that in order to access powersaved > via dbus as a regular user, he has to add them to a special group > (that's how I handle access control under Debian, as there is no > pam_console). > The resulting error message of powersave or kpowersave is > "Cannot connect to powersaved. Is the daemon running? (dbus error)". > To be honest, I myself wouldn't have guessed that this means, I don't > have access rights for powersaved. > Is it possible to tell from the return code of dbus what the correct > problem is and display the error message in (k)powersave > correspondingly? If you give me some pointers where to start and look > at, I might take a look at it myself, if you are too busy. I take a look at this, but not for the release today, but for the next (release candidate next monday). Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [Fwd: Bug#352686: kpowersave: confusing information dialog: Processor 1 deactivated]
On Monday 13 February 2006 14:58, Michael Biebl wrote: > Me again, > > is this really a kpowersave problem or is it powersaved sending the > wrong current state of the cpu? This is a problem with CPUs which not support cpufreq. We read the CPU speed from the sysfs dir for cpufreq, but there is in this case (maybe a Celeron or the CPU only support throttling) nothing. We work for the next release, next week on a better solution. Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [Fwd: Bug#352686: kpowersave: confusing information dialog: Processor 1 deactivated]
On Monday 13 February 2006 15:47, Holger Macht wrote: > On Mon 13. Feb - 14:58:09, Michael Biebl wrote: > > Me again, > > > > is this really a kpowersave problem or is it powersaved sending the > > wrong current state of the cpu? > > It is KPowersave reading out this information. It checks for a > /sys/devices/system/cpu/cpu0/cpufreq directory and if not present it > assumes that the cpu is offline. This is wrong. It has to check the > content of /sys/devices/system/cpu/cpu0/online. Because cpufreq might be > not supported but the cpu is online ;-) > > Danny, can you look into this? See my other mail, this is not a problem with /sys/devices/system/cpu/cpu0/online, this is a problem on Celeron and other cpufreq not supporting machines. Daniel is working on this for the next release next week. Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Fwd: [fmII] KPowersave 0.5.7-rc1 released (Development branch)
-- Forwarded Message -- Subject: [fmII] KPowersave 0.5.7-rc1 released (Development branch) Date: Tuesday 14 February 2006 00:38 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] This email is to inform you about the release of version '0.5.7-rc1' of 'KPowersave' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/kpowersave/ The changes in this release are as follows: This release contains many translation updates (bg, cs, es, fr, it, ja, pt, nb, pt_BR, zh_CN, and zh_TW). A new languages is supported (Khmer). There is a new version of the handbook (Finnish). The detailed dialog was again fixed for machines without CPU Freq support, and provides some more information. This release also includes autotools fixes to be more portable. Release focus: 4 - Minor feature enhancements Project added: Sun, Jan 16th 2005 12:31 (1 year, 0 months ago) Project description: KPowersave provides battery monitoring and suspend/ standby triggers for KDE. It is based on the powersave package and therefore supports APM and ACPI. Trove categories: [Development Status ] 5 - Production/Stable [Intended Audience ] End Users/Desktop [License ] OSI Approved :: GNU General Public License (GPL), OSI Approved :: GNU Lesser General Public License (LGPL) [Operating System] POSIX :: Linux [Topic ] Desktop Environment, Desktop Environment :: K Desktop Environment (KDE), Desktop Environment :: Tools [Translations] Bulgarian, Czech, Danish, Dutch, English, French, German, Greek, Hungarian, Italian, Japanese, Norwegian, Russian, Slovak, Slovenian, Spanish, Swedish, Turkish If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects and categories you're subscribed to in the right column, which you may cancel by highlighting the project or category in question and clicking the 'delete' button. Sincerely, freshmeat.net ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] (k)powersave won't let me STD if grub has no resume parameter
On Thursday 16 February 2006 17:27, Michael Biebl wrote: > Hi all, [...] > I would propose that kpowersave should show a warning message, if it > finds no resume parameter. The warning message should have a abort > suspend button and a timeout of something like 30 secs. If the user does > not click abort, the machine is suspended. In addition the dialog should > have a "don't show this message again" for people, who are sure, that > everything is correct and don't want to be bothered by this message again. This is currently not possible with the powersave. We already work/plan to add a interface to stop/interrupt the suspend to allow clients and connected/registered applications to temporally halt the suspend. Btw. seife work on a general solution in powersave to check this. Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Fwd: Kpowersave with acpi-support
-- Forwarded Message --
Subject: Kpowersave with acpi-support
Date: Friday 17 February 2006 01:13
From: Luka Renko <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Hi!
I made a quick hack to change Kpowersave/powersaved configuration to use
default scripts provided by Ubuntu. I did it only for Hibernate (suspend to
disk) as suspend to RAM does not work on my laptop (HP Compaq nw8240).
I started with the following hints:
http://forge.novell.com/pipermail/powersave-devel/2006-February/000294.html
If you want to try, you need to do the following:
1. Change following lines in /etc/powersave/events:
EVENT_GLOBAL_SUSPEND2DISK="ubuntu_hibernate"
EVENT_GLOBAL_RESUME_SUSPEND2DISK="ubuntu_resume"
2. Create /usr/lib/powersave/scripts/ubuntu_hibernate with following
content:
#!/bin/bash
# first get helper functions (e.g. DEBUG, load_scheme, ...)
"${0%/*}/helper_functions"
/etc/acpi/hibernate.sh
EXIT 0
3. Create /usr/lib/powersave/scripts/ubuntu_resume with following content:
#!/bin/bash
# first get helper functions (e.g. DEBUG, load_scheme, ...)
"${0%/*}/helper_functions"
EXIT 0
4. sudo chmod +x /usr/lib/powersave/scripts/ubuntu_*
5. Restart powersaved and kpowersave
# Kpowersave -> Quit
/etc/init.d/powersaved restart
kpowersave
6. Now "Suspend to Disk" will use Ubuntu scripts instead of powersaved
scripts/method.
Riddell: is this what you had in mind or am I going the wrong route?
Open issues:
- Kpowersave has options for screensaver - those will not have effect on
Ubuntu way unless we change Ubuntu scripts
- I have seen that ACPI scripts have some awareness for klaptopdaemon and
kpowersave - we may need to look if everything is there
- Ubuntu packages are old (0.5.2-1) - latest is 0.5.7-rc1 (with lots of
changes) - I already wrote to package author if he plans new Ubuntu packages
(there are latest versions for Debian Sid) or should we prepare them
Regards,
Luka
---
Hi!I made a quick hack to change Kpowersave/powersaved configuration to use default scripts provided by Ubuntu. I did it only for Hibernate (suspend to disk) as suspend to RAM does not work on my laptop (HP Compaq nw8240).
I started with the following hints: http://forge.novell.com/pipermail/powersave-devel/2006-February/000294.htmlIf you want to try, you need to do the following:
1. Change following lines in /etc/powersave/events:EVENT_GLOBAL_SUSPEND2DISK="ubuntu_hibernate"EVENT_GLOBAL_RESUME_SUSPEND2DISK="ubuntu_resume"2. Create /usr/lib/powersave/scripts/ubuntu_hibernate with following content:
#!/bin/bash# first get helper functions (e.g. DEBUG, load_scheme, ..). "${0%/*}/helper_functions"/etc/acpi/hibernate.shEXIT 03. Create /usr/lib/powersave/scripts/ubuntu_resume with following content:
#!/bin/bash
# first get helper functions (e.g. DEBUG, load_scheme, ...)
"${0%/*}/helper_functions"
EXIT 0
4. sudo chmod +x /usr/lib/powersave/scripts/ubuntu_*5. Restart powersaved and kpowersave# Kpowersave -> Quit/etc/init.d/powersaved restartkpowersave6. Now "Suspend to Disk" will use Ubuntu scripts instead of powersaved scripts/method.
Riddell: is this what you had in mind or am I going the wrong route?Open issues:- Kpowersave has options for screensaver - those will not have effect on Ubuntu way unless we change Ubuntu scripts
- I have seen that ACPI scripts have some awareness for klaptopdaemon
and kpowersave - we may need to look if everything is there
- Ubuntu packages are old (0.5.2-1) - latest is 0.5.7-rc1 (with lots of changes) - I already wrote to package author if he plans new Ubuntu packages (there are latest versions for Debian Sid) or should we prepare them
Regards,Luka
--
kubuntu-devel mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
___
powersave-devel mailing list
powersave-devel@forge.novell.com
http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] [Fwd: Bug#352686: kpowersave: confusing information dialog: Processor 1 deactivated]
On Tuesday 21 February 2006 19:55, Michael Biebl wrote: > According to the bug reporter this bug is not fixed yet for 0.5.8. Is > that correct? I can't test it myself and haven't looked at the code yet. It should work now. If there is nothing in /sys/devices/system/cpu/*/* we read the CPU freq from /proc/cpuinfo and check if the machine is throttled (/proc/acpi/processor/CPU*/throttling). I checked this on several machines with CPUfreq and with only throttling support, but there is maybe a bug in the logic? What kind of machine is this? What kind of processor? Maybe without acpid and only with APM support? The reporter should provide this informations: * cat /proc/cpuinfo * cat /proc/acpi/processor/CPU*/* * tree /sys/devices/system/cpu/*/* * grep . /sys/devices/system/cpu/*/* -r Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] kpowersave 0.5.8-1.1 - more translation errors
On Tuesday 21 February 2006 22:43, Axel Braun wrote: > Hi, > > seems that this is now completely messed up: > > I have *no* external power supply connected - the battery field shows > 'Stromstecker angeschlossen', but the light is dark.better would be > 'Stromversorgung nicht angeschlossen' Thanks for the report. We get currently a new (last) translation round and because of this we changed and activated some (new) keys. With this it looks as this was a wrong translation in the german po file. Fixed in SVN for 0.5.9-rc3: Modified: trunk/kpowersave/ChangeLog trunk/kpowersave/po/de.po Log: 2006-02-21 Danny Kukawka <[EMAIL PROTECTED]> * po/de.po: fixed translation for "unplugged" Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] JFYI: [fmII] KPowersave 0.5.8-rc2 released (Development branch)
-- Forwarded Message -- Subject: [fmII] KPowersave 0.5.8-rc2 released (Development branch) Date: Tuesday 21 February 2006 01:26 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] This email is to inform you about the release of version '0.5.8-rc2' of 'KPowersave' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/kpowersave/ The changes in this release are as follows: The sound settings for events were removed from the configure dialog and replaced with KNotify, and many new events were added. Now the user can e.g. play sounds, configure messages, or execute commands on events (configurable via the KNotify dialog from the applet menu or the configure dialog). This version contains fixes in the detailed dialog. It fixes support for CPUs that only support throttling, and all battery bars are the same size. It fixes autosuspend for FC 4, changes the path to powersaved in the dialogs to be more portable, and has several fixes and translation updates. Release focus: 5 - Major feature enhancements Project added: Sun, Jan 16th 2005 12:31 (1 year, 1 month ago) Project description: KPowersave provides battery monitoring and suspend/ standby triggers for KDE. It is based on the powersave package and therefore supports APM and ACPI. Trove categories: [Development Status ] 5 - Production/Stable [Intended Audience ] End Users/Desktop [License ] OSI Approved :: GNU General Public License (GPL), OSI Approved :: GNU Lesser General Public License (LGPL) [Operating System] POSIX :: Linux [Topic ] Desktop Environment, Desktop Environment :: K Desktop Environment (KDE), Desktop Environment :: Tools [Translations] Bulgarian, Czech, Danish, Dutch, English, French, German, Greek, Hungarian, Italian, Japanese, Norwegian, Russian, Slovak, Slovenian, Spanish, Swedish, Turkish If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects and categories you're subscribed to in the right column, which you may cancel by highlighting the project or category in question and clicking the 'delete' button. Sincerely, freshmeat.net --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] [PATCH] fix battery state if no battery is in the machine
Hi,
this patch fixes problems with powersave -s and also with dbus methode
BatteryState if no battery is in the system available. Currently the methode
return BAT_NORM_STATE (which result in powersave -s == NORMAL) but it should
be BAT_NONE_STATE.
Please review.
Cheers,
Danny
daemon/battery.cpp |2 +-
libpower/battery.c | 40 ++--
2 files changed, 23 insertions(+), 19 deletions(-)
Index: daemon/battery.cpp
===
--- daemon/battery.cpp (Revision 1950)
+++ daemon/battery.cpp (Arbeitskopie)
@@ -48,7 +48,7 @@
_msecs_last_battery_read = 0;
- if (getBatteriesInfo(&_bg) < 0) {
+ if (getBatteriesInfo(&_bg) <= 0) {
pDebug(DBG_INFO, "Could not get battery info");
// cannot read out battery, no cpufreq, stop polling
// suppors AC online and set battery state to normal
Index: libpower/battery.c
===
--- libpower/battery.c (Revision 1950)
+++ libpower/battery.c (Arbeitskopie)
@@ -104,27 +104,31 @@
continue;
}
- /* calculate the charging rate for the multiple battery case */
- if (bg.remaining_minutes > 0 && bd.remaining_capacity != UNKNOWN) {
- int to_go = 0;
- if (bg.charging_state & CHARG_STATE_CHARGING) {
-if (bd.last_full_capacity != UNKNOWN)
- to_go = bd.last_full_capacity - bd.remaining_capacity;
- } else {
-to_go = bd.remaining_capacity;
+ if( bd.present == PRESENT_NO) {
+ valid_batteries--;
+ } else {
+ /* calculate the charging rate for the multiple battery case */
+ if (bg.remaining_minutes > 0 && bd.remaining_capacity != UNKNOWN) {
+int to_go = 0;
+if (bg.charging_state & CHARG_STATE_CHARGING) {
+ if (bd.last_full_capacity != UNKNOWN)
+ to_go = bd.last_full_capacity - bd.remaining_capacity;
+} else {
+ to_go = bd.remaining_capacity;
+}
+rate += (to_go / bg.remaining_minutes);
}
- rate += (to_go / bg.remaining_minutes);
- }
- /* FIXME: can we have one battery with valid last_full and a
- second battery with last_full == UNKNOWN?
- This would make those values totally bogus. */
- if (bd.last_full_capacity != UNKNOWN) {
- last_full_capacity_sum += bd.last_full_capacity;
+ /* FIXME: can we have one battery with valid last_full and a
+ second battery with last_full == UNKNOWN?
+ This would make those values totally bogus. */
+ if (bd.last_full_capacity != UNKNOWN) {
+last_full_capacity_sum += bd.last_full_capacity;
- /* see the FIXME above, same applies here... */
- if (bd.remaining_capacity != UNKNOWN) {
-remaining_capacity_sum += bd.remaining_capacity;
+/* see the FIXME above, same applies here... */
+if (bd.remaining_capacity != UNKNOWN) {
+ remaining_capacity_sum += bd.remaining_capacity;
+}
}
}
}
___
powersave-devel mailing list
powersave-devel@forge.novell.com
http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] [PATCH] fix APM battery support in powerlib
Hi,
this patch fix the user binary and the powerlib to support battery information
on APM machines. Currently powersave only provide information about ACPI
batteries. I think this is a bug related to the switch to HAL.
Please review the patch. There are maybe sidekicks.
One problem I already found is that HAL poll on APM battery and AC every 2
seconds - which results in the most cases in a remaining_time property change
with each poll. This can produce more events than are useful. Through this
events KPowersave maybe run to often rechecks on APM machines.
Btw. the bug is in HAL, I take a look at this - HAL should only poll AC every
2 seconds and the battery maybe only ever 30-60 secs.
Cheers,
Danny
libpower/battery.c| 14 --
user_binary/powersave.cpp | 13 +++--
2 files changed, 19 insertions(+), 8 deletions(-)
Index: user_binary/powersave.cpp
===
--- user_binary/powersave.cpp (Revision 1951)
+++ user_binary/powersave.cpp (Arbeitskopie)
@@ -377,15 +377,24 @@
fprintf(stdout, ", %d minutes remaining", bg.remaining_minutes);
}
+ if (bg.charging_state & CHARG_STATE_CHARGING) {
+fprintf(stdout, " charging");
+}
+if (bg.charging_state & CHARG_STATE_DISCHARGING) {
+fprintf(stdout, " discharging");
+ }
+
fprintf(stdout, "\n");
}
if (ac_state == AC_ONLINE)
fprintf(stdout, "AC is online.\n");
+ else
+ fprintf(stdout, "AC is offline.\n");
}
// Test of detailed battery information
if (ext) {
- if (checkACPI() == ACPI) {
+ if (checkACPI() == ACPI || checkACPI() == APM) {
for (x = 0; x < numBatteries(); x++) {
int ret = getBatteryInfo(x, &bg);
@@ -415,7 +424,7 @@
}
}
} else
- fprintf(stdout, "No acpi system\n");
+ fprintf(stdout, "No acpi or apm system\n");
}
return 1;
}
Index: libpower/battery.c
===
--- libpower/battery.c (Revision 1951)
+++ libpower/battery.c (Arbeitskopie)
@@ -282,7 +287,7 @@
return -3;
}
- if (checkACPI() != ACPI) {
+ if (checkACPI() != ACPI && checkACPI() != APM) {
return NO_ACPI_ERROR;
}
@@ -290,11 +295,13 @@
return -2;
}
- /* check whether module has been loaded and device is available */
- int res = check_ACPI_dir(ACPI_BATTERY_DIR);
- if (res < 0)
- /* returns either NO_DEVICE_ERROR or NO_MODULE_ERROR */
- return res;
+ if (checkACPI == ACPI) {
+ /* check whether module has been loaded and device is available */
+ int res = check_ACPI_dir(ACPI_BATTERY_DIR);
+ if (res < 0)
+ /* returns either NO_DEVICE_ERROR or NO_MODULE_ERROR */
+ return res;
+ }
char **batteries;
int numBatteries;
___
powersave-devel mailing list
powersave-devel@forge.novell.com
http://forge.novell.com/mailman/listinfo/powersave-devel
Re: FW: Re: [powersave-devel] [powersave - Help] RE: kpowersave and battery status problem
-- Forwarded Message -- Subject: [powersave - Help] RE: kpowersave and battery status problem Date: Tuesday 28 February 2006 00:21 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3600611 By: chevyou I gave up. I found that the daemon works fine. I'm not using an alternative to Kpowersave which is kthinkbat. Not all the cool options, but it gives me what I need. Something that tells me the percentage of juice I have left. Thanks for comin out! __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: FW: Re: [powersave-devel] [powersave - Help] RE: kpowersave and battery status problem
-- Forwarded Message -- Subject: [powersave - Help] RE: kpowersave and battery status problem Date: Tuesday 28 February 2006 10:20 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3601161 By: Danny Kukawka Please retry with packages from ftp://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/ this should work. If not, write a mail to [EMAIL PROTECTED] - it's easier than discuss this in this forum. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
FW: Re: [powersave-devel] [powersave - Help] basic configuration?
-- Forwarded Message -- Subject: [powersave - Help] RE: basic configuration? Date: Tuesday 28 February 2006 14:18 From: "SourceForge.net" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3601516 By: hulder Please note that if kpowersave is running, it cares about screenlocking. If powersaved could not read the configuration, it definitely would complain in /var/log/messages. We know that the documentation still contains some hardcoded paths and we are currently working on removing all those occurences. We also currently working on a general documentation cleanup. Please try to use the example event script /usr/share/doc/packages/powersave/contrib/example_event_script (or wherever it got installed) as a template in case of a wrong script. If this does not help, please post your custom event script. Regards, Holger __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=424162 --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] [fmII] KPowersave 0.5.9-rc3 released (Development branch)
-- Forwarded Message -- Subject: [fmII] KPowersave 0.5.9-rc3 released (Development branch) Date: Wednesday 01 March 2006 22:21 This email is to inform you about the release of version '0.5.9-rc3' of 'KPowersave' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/kpowersave/ The changes in this release are as follows: This release candidate depends on powersave 0.12.1 or higher because of APM and battery related fixes in powersave. This version fixes problems in the information dialog and the applet tooltip with battery information on machines with APM support, and with processor information on machines without CPUfreq or throttling support. It also includes a fix for battery state info if no battery is available, translations, and handbook updates. Release focus: 7 - Major bugfixes Project added: Sun, Jan 16th 2005 12:31 (1 year, 1 month ago) Project description: KPowersave provides battery monitoring and suspend/ standby triggers for KDE. It is based on the powersave package and therefore supports APM and ACPI. Trove categories: [Development Status ] 5 - Production/Stable [Intended Audience ] End Users/Desktop [License ] OSI Approved :: GNU General Public License (GPL), OSI Approved :: GNU Lesser General Public License (LGPL) [Operating System] POSIX :: Linux [Topic ] Desktop Environment, Desktop Environment :: K Desktop Environment (KDE), Desktop Environment :: Tools [Translations] Bulgarian, Czech, Danish, Dutch, English, French, German, Greek, Hungarian, Italian, Japanese, Norwegian, Russian, Slovak, Slovenian, Spanish, Swedish, Turkish If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects and categories you're subscribed to in the right column, which you may cancel by highlighting the project or category in question and clicking the 'delete' button. Sincerely, freshmeat.net --- ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: Fwd: [powersave-users] kPowerSave problem: kubuntu version
On Thursday 02 March 2006 14:27, Luka Renko wrote: > FYI, more users wanting kpowersave... > Not sure what we can do here, due to this clash of package dependencies... > [...] > Preconfiguring packages ... > dpkg: apmd: dependency problems, but removing anyway as you request: > kubuntu-desktop depends on apmd. > (Reading database ... 63888 files and directories currently installed.) > Removing apmd ... > dpkg: powernowd: dependency problems, but removing anyway as you request: > kubuntu-desktop depends on powernowd; however: > Package powernowd is to be removed. > Removing powernowd ... > * Stopping powernowd: [ > ok ] [...] apmd need not to be deinstalled, if you can guarantee that apmd is never running if the powersave daemon run because if both run there are races, because both daemons try to handle the same events and e.g. also suspend. Btw. the best is remove apmd and fix the dependency in kubuntu-desktop (why depends kubuntu-desktop on apmd? apmd is e.g. useless on ACPI machines). powernowd is maybe not such a big problem, but the best is: remove (or be sure powernowd is not running) if powersave is installed because powersaved also handle/control cpufreq settings. Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] Re: Kpowersave with acpi-support
Hi, On Friday 17 February 2006 01:13, Luka Renko wrote: > I made a quick hack to change Kpowersave/powersaved configuration to use > default scripts provided by Ubuntu. I did it only for Hibernate (suspend to > disk) as suspend to RAM does not work on my laptop (HP Compaq nw8240). > I started with the following hints: > http://forge.novell.com/pipermail/powersave-devel/2006-February/000294.html I'm glad to inform you that powersave with v0.12.0 has now suspend2 support out of the box. If you switch to (K)powersave as replacement for klaptop as default powermanagement solution, you maybe also should adjust the HAL suspend methodes to use powersave as e.g. currently for SUSE. Cheers, Danny -- Danny Kukawka [EMAIL PROTECTED] http://sourceforge.net/projects/powersave/ ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] Re: Kpowersave with acpi-support
On Thursday 02 March 2006 15:11, Luka Renko wrote: > This is good news, however due to feature freeze there is not much we can > do for Kubuntu Dapper release (maybe just sync upstream with final > 0.6release?), but I for sure would like to replace klaptop in future. > Currently we need to think if we can reduce the dependancy issue (apmd, > powernowd) in order to at least allow users to switch to kpowersave easier. Depending on the current SUSE 10.1/NLD/SLES release schedule we plan to release final version 0.6.0 with SUSE 10.1rc1 which is planed for Fri, Mar 31. The final version was planed earlier (this is also the reason why the KPowersave packages are already RC's) but the release plan for SUSE changed. Regards, Danny -- Danny Kukawka [EMAIL PROTECTED] http://sourceforge.net/projects/powersave/ ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
Re: [powersave-devel] powersave fedora src.rpm?
On Saturday 04 March 2006 03:03, oleksandr korneta wrote: > Hello, > > I was going to rebuild an rpm of the last version of powersave for my > FC4 x86_64, but I don't see the src.rpm for fedora on the project site. > Is it going to appear there later? Yes I think I upload new Fedora packages today or tomorrow. If you build the powersave packages (and maybe also the KPowersave packages) for FC4 on x86_64 - could you send me the rpms? I would add them to sf.net Cheers, Danny ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] [released] powersave 0.12.2 and kpowersave 0.5.9 for Mandriva 2006.1
Hi, I'm glad to announce that I tonight finished building the first powersave and kpowersave packages for Mandriva 2006.1. In order to get them working properly, you need to have dbus >= 0.61 , hal > 0.5.5.1 and cpufrequtils >= 0.4. All this packages can be installed via RpmDrake from available mirrors. There are some point to consider: - powersave replace several no longer needed packages/programms (they can also produce races with powersave) - if you use a APM machine, remove apmd or be sure that apmd is not running if powersave runs - you should remove also these packages from your boot process: cpufreqd, powernowd, cpufreq - on ACPI systems: powersave need a running acpid Please report all issues on powersave-devel@forge.novell.com Regards, Danny [1] http://sourceforge.net/project/showfiles.php?group_id=124576&package_id=162439&release_id=395174 [2] http://sourceforge.net/project/showfiles.php?group_id=124576&package_id=162525&release_id=398258 ___ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
[powersave-devel] [PATCH] add LCD brightness support for Omnibook
Hi,
this patch adds support for set brightness on machines which supported by the
omnibook kernel module [1] and support set brightness.
Please review.
Cheers,
Danny
[1] http://sourceforge.net/projects/omke/
brightness.cpp | 86 +
brightness.h | 15
2 files changed, 101 insertions(+)
Index: daemon/brightness.h
===
--- daemon/brightness.h (revision 2004)
+++ daemon/brightness.h (working copy)
@@ -32,6 +32,7 @@
#define ACPI_SONY "/proc/acpi/sony/brightness"
#define ACPI_TOSHIBA "/proc/acpi/toshiba/lcd"
#define ACPI_PANASONIC "/proc/acpi/panasonic/"
+#define LCD_OMNIBOOK "/proc/omnibook/lcd"
/* merge #include "powersaved.h" */
@@ -138,3 +139,17 @@
int GetLevels();
};
#endif/* POWERSAVE_BRIGHTNESS_H */
+
+class BrightnessOmnibook:public Brightness {
+ public:
+ void Init();
+
+ int Get();
+ void Set(int);
+
+ void Min();
+ void Med();
+
+ int GetLevels();
+};
+
Index: daemon/brightness.cpp
===
--- daemon/brightness.cpp (revision 2004)
+++ daemon/brightness.cpp (working copy)
@@ -5,6 +5,7 @@
* Copyright (C) 2004,2005 SUSE Linux Products GmbH *
* *
* Author(s): Timo Hoenig <[EMAIL PROTECTED]> *
+ * Danny Kukawka <[EMAIL PROTECTED]> *
* *
* This program is free software; you can redistribute it and/or modify it *
* under the terms of the GNU General Public License as published by the *
@@ -70,6 +71,11 @@
return new BrightnessPanasonic();
}
+ if ((fd = open(LCD_OMNIBOOK, O_RDONLY)) > 0) {
+ close(fd);
+ return new BrightnessOmnibook();
+ }
+
if (fd) {
close(fd);
}
@@ -641,3 +647,83 @@
{
return (brt_max - brt_min) * 10 / brt_scale + 1;
}
+
+/* Brightness (Omnibook object) */
+
+void BrightnessOmnibook::Init()
+{
+ last_percent = -1;
+ iface = LCD_OMNIBOOK;
+ return;
+}
+
+int BrightnessOmnibook::Get()
+{
+ char value[19];
+ int level;
+
+ if ((fd = open(iface, O_RDONLY)) < 0) {
+ perror(iface);
+ level = -1;
+ goto out;
+ }
+
+ if (read(fd, &value, 18) == -1) {
+ level = -1;
+ goto out;
+ }
+
+ sscanf(value, "LCD brightness: %d", &level);
+
+out:
+ if (fd) {
+ close(fd);
+ }
+ return level;
+}
+
+void BrightnessOmnibook::Set(int level)
+{
+ char value[3];
+ int n;
+
+ if ((fd = open(iface, O_RDWR)) < 1) {
+ perror(iface);
+ goto out;
+ }
+
+ if (level > 10)
+ level = 10;
+ else if (level < 0)
+ level = 0;
+ n = sprintf(value, "%d", level);
+ if (write(fd, value, n) < 0) {
+ pDebug(DBG_WARN,
+ "Unable to write to Omnibook brightness interface");
+ goto out;
+ }
+
+out:
+ if (fd) {
+ close(fd);
+ }
+ return;
+}
+
+void BrightnessOmnibook::Min()
+{
+ Set(1);
+ return;
+}
+
+void BrightnessOmnibook::Med()
+{
+ Set(5);
+ return;
+}
+
+int BrightnessOmnibook::GetLevels()
+{
+ return 10;
+}
+
___
powersave-devel mailing list
powersave-devel@forge.novell.com
http://forge.novell.com/mailman/listinfo/powersave-devel
