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 cre
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
> install
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
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 ma
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 wil
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 susp
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 s
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
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
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 hap
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.co
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 sc
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 hibe
13 matches
Mail list logo
