Package: pm-utils
Version: 1.2.5-4
Severity: normal

Hey Tim!

Thanks for maintaining pm-utils! 

kpowersave pops up a window telling that an error "1" has occurred when
suspending to ram. The error "1" message is annoying and lacks meaning to
the user.

It's caused by maybe_deallocvt returning the ret_val of state_exists when 
the tested (here: console) file isn't found. This absence of this file seems
not to do any harm therefore the escalation of the ret_val 1 is deprecated.

Solution: just tell maybe_deallocvt to return 0 in the above case.

NB: other functions have similar return constructions and some if not all
(not verified) have a ret_val of 0.

Thanks and take care! :)

Nils


diff -Naur to fix this:
--- fromDeb/99video     2009-11-07 00:24:05.000000000 +0100
+++ /usr/lib/pm-utils/sleep.d/99video   2009-11-07 00:23:56.000000000 +0100
@@ -92,7 +92,7 @@
 
 maybe_deallocvt()
 {
-    state_exists console || return
+    state_exists console || return 0
     chvt $(restorestate console)
     deallocvt 63
 }

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.31.1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pm-utils depends on:
ii  kbd                           1.15-4     Linux console font and keytable ut
ii  powermgmt-base                1.30+nmu1  Common utils and configs for power

Versions of packages pm-utils recommends:
ii  hal                           0.5.13-3   Hardware Abstraction Layer
ii  radeontool                    1.5-5      utility to control ATI Radeon back
pn  uswsusp                       <none>     (no description available)
ii  vbetool                       1.1-2      run real-mode video BIOS code to a

Versions of packages pm-utils suggests:
ii  cpufrequtils                  005-1      utilities to deal with the cpufreq

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to