Bug#474201: KPowersave doesn't suspend/hibernate

2008-05-01 Thread Thomas Zander
On Monday 28. April 2008 02:34:15 Michael Biebl wrote:
 Can you really reproduce the problem by creating a file ~/.dbus?

My guess is that with a .dbus file present apps that start later can't find 
the running daemon.

 Maybe it was a missing dbus-x11 package. Did you have this package
 installed, when you noticed the problem, do you have it installed now?

I had that installed before, and still do.
-- 
Thomas Zander


signature.asc
Description: This is a digitally signed message part.


Bug#474201: [Pkg-utopia-maintainers] Bug#474201: KPowersave doesn't suspend/hibernate

2008-05-01 Thread Michael Biebl

Thomas Zander wrote:

On Monday 28. April 2008 02:34:15 Michael Biebl wrote:

Can you really reproduce the problem by creating a file ~/.dbus?


My guess is that with a .dbus file present apps that start later can't find 
the running daemon.


The problem is, that I can't reproduce this bug by creating a file 
~/.dbus. That's why I asked you, if you can verify this problem by 
creating such a file.
The problem could be someplace else after all and we are on the wrong 
track alltogether.





Maybe it was a missing dbus-x11 package. Did you have this package
installed, when you noticed the problem, do you have it installed now?


I had that installed before, and still do.



Ok.

Michael


--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-27 Thread Thomas Zander
On Thursday 24. April 2008 07:12:13 Michael Biebl wrote:
 Thomas Zander wrote:

  Would it be an idea to add an  rm -f $HOME/.dbus  before the try to
  create a

 Yes, please remove the ~/.dbus file. There is no need though to create
 the directory manually in a boot script. dbus-daemon will do that
 automatically.

Ok, let me rephrase my question as my intend apparently didn't come across.

I think its a bug [somewhere] that the dbus daemon silently fails when the 
user has a .dbus file in his homedir.
I think this bug should be fixed by deleting that file either in the startup 
sequence or in the dbus daemon itself.
Do you have any suggestions where that could be done?  If so, please rename 
and reassign this task to the appropriate package.

-- 
Thomas Zander


signature.asc
Description: This is a digitally signed message part.


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-27 Thread Michael Biebl

reassign 474201 dbus
thanks

Thomas Zander wrote:

On Thursday 24. April 2008 07:12:13 Michael Biebl wrote:

Thomas Zander wrote:



Would it be an idea to add an  rm -f $HOME/.dbus  before the try to
create a

Yes, please remove the ~/.dbus file. There is no need though to create
the directory manually in a boot script. dbus-daemon will do that
automatically.


Ok, let me rephrase my question as my intend apparently didn't come across.

I think its a bug [somewhere] that the dbus daemon silently fails when the 
user has a .dbus file in his homedir.
I think this bug should be fixed by deleting that file either in the startup 
sequence or in the dbus daemon itself.


Dbus should only delete the ~/.dbus file it it has created it itself. As 
dbus-daemon doesn't create a ~/.dbus file, but a ~/.dbus *directory*, it 
would be wrong, if dbus-daemon simply removed the file, when it doesn't 
belong to dbus-daemon (it could be a configuration file of some other 
software, who knows).


Do you have any suggestions where that could be done?  If so, please rename 
and reassign this task to the appropriate package.


It's obvious not a bug in kpowersave.
I'm reassignig to dbus, although I doubt that it is a bug in dbus.
I can only assume that the .dbus file got created by an accident.

Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-27 Thread Michael Biebl

Thomas Zander wrote:

On Thursday 24. April 2008 07:12:13 Michael Biebl wrote:

Thomas Zander wrote:



Would it be an idea to add an  rm -f $HOME/.dbus  before the try to
create a

Yes, please remove the ~/.dbus file. There is no need though to create
the directory manually in a boot script. dbus-daemon will do that
automatically.


Ok, let me rephrase my question as my intend apparently didn't come across.

I think its a bug [somewhere] that the dbus daemon silently fails when the 
user has a .dbus file in his homedir.


Just tried to reproduce your problem. I created a file ~/.dbus, but 
dbus-daemon --session is still correctly started.


Can you really reproduce the problem by creating a file ~/.dbus?

Maybe it was a missing dbus-x11 package. Did you have this package 
installed, when you noticed the problem, do you have it installed now?


Cheers,
Michael


--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-23 Thread Michael Biebl

Thomas Zander wrote:

On Thursday 10. April 2008 23:46:55 you wrote:

please run hald in debug mode
(hald --daemon=no --verbose=yes) and attach the output to the bug
report.

ok.

The log doesn't seem to contain a suspend attempt.
Could you only send me the relevant log output when you do the suspend
attempt.


That attempt is at the very end, I indeed saw no reaction in the hal log.

I did more digging here, as I am not convinced that searching outside of 
kpowersave is relevant.

[reading .xsession-errors]
this is an interresting line;
Xsession: X session started for zander at Tue Apr  8 23:01:27 CEST 2008
Unable to create /home/zander/.dbus/session-bus

The reason, I found, is that somehow I got a .dbus FILE in my homedir. So 
obviously the dir could not be created.  I bet that file got restored from 
the backup from another system.
Would it be an idea to add an  rm -f $HOME/.dbus  before the try to create a 


Yes, please remove the ~/.dbus file. There is no need though to create 
the directory manually in a boot script. dbus-daemon will do that 
automatically.


Please make also sure that you have installed dbus-x11.

Cheers,
Michael

--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-12 Thread Thomas Zander
On Thursday 10. April 2008 23:46:55 you wrote:
  please run hald in debug mode
  (hald --daemon=no --verbose=yes) and attach the output to the bug
  report.
 
  ok.

 The log doesn't seem to contain a suspend attempt.
 Could you only send me the relevant log output when you do the suspend
 attempt.

That attempt is at the very end, I indeed saw no reaction in the hal log.

I did more digging here, as I am not convinced that searching outside of 
kpowersave is relevant.
[reading .xsession-errors]
this is an interresting line;
Xsession: X session started for zander at Tue Apr  8 23:01:27 CEST 2008
Unable to create /home/zander/.dbus/session-bus

The reason, I found, is that somehow I got a .dbus FILE in my homedir. So 
obviously the dir could not be created.  I bet that file got restored from 
the backup from another system.
Would it be an idea to add an  rm -f $HOME/.dbus  before the try to create a 
dir (in the boot scripts)?
-- 
Thomas Zander


signature.asc
Description: This is a digitally signed message part.


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-10 Thread Michael Biebl
Michael Biebl wrote:
 tags 474201 moreinfo unreproducible
 thanks
 
 
 Thomas Zander wrote:
 Package: kpowersave
 Version:0.7.3-1
 Severity: important

 When using the kpowersave systray item I can select to either suspend to 
 disk 
 or suspend to ram.  Unfortunately nothing happens when I click either. Well, 
 my screen locks, but nothing more happens.

 When I type s2ram or s2disk, or even hibernate (all as root) my laptop does 
 get suspended correctly. Which leads me to believe that kpowersave doesn't 
 work together with other debian packages properly.
 
 Hi Thomas,
 
 your bug report is missing vital information:
 kernel version, architecture, versions of dependend packages like hal
 and pm-utils. I can only suggest that you use reportbug (or
 reportbug-ng) for future bug reports.
 
 Just guessing out of the blue: Is your user in group powerdev?
 If not, please add your user to group plugdev and reload dbus
 (/etc/init.d/dbus force-reload).
 If that doesn't help, please run hald in debug mode
 (hald --daemon=no --verbose=yes) and attach the output to the bug report.
 

Hi Thomas,

can you provide me the information I requested? Otherwise I'll close
this bug.

Cheers,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-10 Thread Thomas Zander
On Friday 4. April 2008 09:01:29 Michael Biebl wrote:
  When using the kpowersave systray item I can select to either suspend to
  disk or suspend to ram.  Unfortunately nothing happens when I click
  either. Well, my screen locks, but nothing more happens.
 
  When I type s2ram or s2disk, or even hibernate (all as root) my laptop
  does get suspended correctly. Which leads me to believe that kpowersave
  doesn't work together with other debian packages properly.

 Hi Thomas,

 your bug report is missing vital information:
 kernel version, architecture, versions of dependend packages like hal
 and pm-utils. I can only suggest that you use reportbug (or
 reportbug-ng) for future bug reports.

If only reportbug was intelligent enough to find out that I have exim setup to 
never do mail and propose to save a file instead... (or start kmail or so)
I.e. I tried, but no bug actually gets reported if I use it.

Anyway, sorry for not providing more info; I am using 'lenny'

Linux lacuna 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 GNU/Linux

 Just guessing out of the blue: Is your user in group powerdev?

No, its not. Which package should I file a bug against to make sure the 
default (i.e. created in the installer), only non-root user gets auto-added 
to that group?

 If not, please add your user to group plugdev and reload dbus
 (/etc/init.d/dbus force-reload).
 If that doesn't help, 

It didn't.
I rebooted my machine in the meantime (and promptly forgot I had this mail in 
my drafts box, thanks for the reminder!)
Still no luck.

 please run hald in debug mode 
 (hald --daemon=no --verbose=yes) and attach the output to the bug report.
ok.
-- 
Thomas Zander


hald.out.bz2
Description: BZip2 compressed data


signature.asc
Description: This is a digitally signed message part.


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-10 Thread Michael Biebl
Thomas Zander wrote:
 On Friday 4. April 2008 09:01:29 Michael Biebl wrote:
 When using the kpowersave systray item I can select to either suspend to
 disk or suspend to ram.  Unfortunately nothing happens when I click
 either. Well, my screen locks, but nothing more happens.

 When I type s2ram or s2disk, or even hibernate (all as root) my laptop
 does get suspended correctly. Which leads me to believe that kpowersave
 doesn't work together with other debian packages properly.
 Hi Thomas,

 your bug report is missing vital information:
 kernel version, architecture, versions of dependend packages like hal
 and pm-utils. I can only suggest that you use reportbug (or
 reportbug-ng) for future bug reports.
 
 If only reportbug was intelligent enough to find out that I have exim setup 
 to 
 never do mail and propose to save a file instead... (or start kmail or so)
 I.e. I tried, but no bug actually gets reported if I use it.

You can try reportbug-ng in that case (it allows to use a mua of your
choice)

 Anyway, sorry for not providing more info; I am using 'lenny'
 
 Linux lacuna 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 GNU/Linux
 
 Just guessing out of the blue: Is your user in group powerdev?
 
 No, its not. Which package should I file a bug against to make sure the 
 default (i.e. created in the installer), only non-root user gets auto-added 
 to that group?

The user created during installation (using d-i) should be in group
powerdev/netdev/plugdev afaik.

 If not, please add your user to group plugdev and reload dbus
 (/etc/init.d/dbus force-reload).
 If that doesn't help, 
 
 It didn't.
 I rebooted my machine in the meantime (and promptly forgot I had this mail in 
 my drafts box, thanks for the reminder!)
 Still no luck.
 
 please run hald in debug mode 
 (hald --daemon=no --verbose=yes) and attach the output to the bug report.
 ok.

The log doesn't seem to contain a suspend attempt.
Could you only send me the relevant log output when you do the suspend
attempt.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-04 Thread Thomas Zander
Package: kpowersave
Version:0.7.3-1
Severity: important

When using the kpowersave systray item I can select to either suspend to disk 
or suspend to ram.  Unfortunately nothing happens when I click either. Well, 
my screen locks, but nothing more happens.

When I type s2ram or s2disk, or even hibernate (all as root) my laptop does 
get suspended correctly. Which leads me to believe that kpowersave doesn't 
work together with other debian packages properly.
-- 
Thomas Zander



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



Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-04 Thread Michael Biebl
tags 474201 moreinfo unreproducible
thanks


Thomas Zander wrote:
 Package: kpowersave
 Version:0.7.3-1
 Severity: important
 
 When using the kpowersave systray item I can select to either suspend to disk 
 or suspend to ram.  Unfortunately nothing happens when I click either. Well, 
 my screen locks, but nothing more happens.
 
 When I type s2ram or s2disk, or even hibernate (all as root) my laptop does 
 get suspended correctly. Which leads me to believe that kpowersave doesn't 
 work together with other debian packages properly.

Hi Thomas,

your bug report is missing vital information:
kernel version, architecture, versions of dependend packages like hal
and pm-utils. I can only suggest that you use reportbug (or
reportbug-ng) for future bug reports.

Just guessing out of the blue: Is your user in group powerdev?
If not, please add your user to group plugdev and reload dbus
(/etc/init.d/dbus force-reload).
If that doesn't help, please run hald in debug mode
(hald --daemon=no --verbose=yes) and attach the output to the bug report.

Thanks,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#474201: KPowersave doesn't suspend/hibernate

2008-04-04 Thread Michael Biebl
Michael Biebl wrote:

 
 Just guessing out of the blue: Is your user in group powerdev?
 If not, please add your user to group plugdev and reload dbus
^^^
   err, powerdev, obviously

See also /etc/dbus-1/system.d/hal.conf and /usr/share/doc/hal/README.Debian.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature