reassign 512288 hal
severity 512288 normal
retitle 512288 hal: hald is sending unrequested replies
thanks
Frans Pop wrote:
> JFYI.
>
> Just got another one after resume. At least that makes it clear that it's
> reproducible for me.
>
> Jan 19 19:46:48 aragorn kernel: Back to C!
> [...]
> Jan 19
Processing commands for cont...@bugs.debian.org:
> reassign 512288 hal
Bug#512288: kpowersave: Shows dbus errors since recent dbus update
Bug reassigned from package `kpowersave' to `hal'.
> severity 512288 normal
Bug#512288: kpowersave: Shows dbus errors since recent dbus update
Frans Pop wrote:
> JFYI.
>
> Just got another one after resume. At least that makes it clear that it's
> reproducible for me.
Do you actually have a failing suspend because of this or other regressions?
(just wondering why you filed with severity serious)
Michael
--
Why is it that all of the
JFYI.
Just got another one after resume. At least that makes it clear that it's
reproducible for me.
Jan 19 19:46:48 aragorn kernel: Back to C!
[...]
Jan 19 19:46:48 aragorn acpid: client connected from 3616[0:0]
Jan 19 19:46:49 aragorn anacron[21487]: Anacron 2.3 started on 2009-01-19
Jan 19 19
On Monday 19 January 2009, Michael Biebl wrote:
> Do you use static groups via /etc/groups or a networked setup like nis
> or ldap?
Plain static.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Frans Pop wrote:
>
> The error does not happen on (re)boot [1] or when I dock/undock the
> notebook (i.e. on power status changes).
>
> It seems 100% clear to me that the error must be related to the dbus
> upgrade. I'm afraid I cannot help you much with why.
Yeah, the dbus upgrade made the d
On Monday 19 January 2009, Frans Pop wrote:
> The dbus upgrade was on Sat, Jan 17 2009 09:19:41 +0100:
> [UPGRADE] dbus 1.2.1-4 -> 1.2.1-5
> [UPGRADE] dbus-x11 1.2.1-4 -> 1.2.1-5
> [UPGRADE] libdbus-1-3 1.2.1-4 -> 1.2.1-5
>
> Before the dbus upgrade I've never had these errors.
Just for the sake o
On Monday 19 January 2009, Michael Biebl wrote:
> Does it help if you reload dbus (restart dbus) or reboot your laptop?
No. I rebooted the laptop before I reported the problem.
Additional info
===
Last kpowersave upgrade was on Tue, Jan 13 2009 09:13:35 +0100:
[UPGRADE] kpowersave 0.7
Frans Pop wrote:
> On Monday 19 January 2009, Michael Biebl wrote:
>> Could you also please send me your /etc/dbus-1/system.d/hal.conf
>
> Attached.
>
Ok, this looks all good and I can't reproduce your problems.
Does it help if you reload dbus (restart dbus) or reboot your laptop?
Michael
On Monday 19 January 2009, Michael Biebl wrote:
> Could you also please send me your /etc/dbus-1/system.d/hal.conf
Attached.
Frans Pop schrieb:
> On Monday 19 January 2009, Michael Biebl wrote:
>> are you using group "powerdev" to control access to hal or consolekit?
>
> powerdev group:
>
> $ id
> uid=1000(fjp) gid=1000(fjp) groups=4(adm),20(dialout),24(cdrom),25
> (floppy),29(audio),44(video),46(plugdev),50(staff),110
On Monday 19 January 2009, Michael Biebl wrote:
> are you using group "powerdev" to control access to hal or consolekit?
powerdev group:
$ id
uid=1000(fjp) gid=1000(fjp) groups=4(adm),20(dialout),24(cdrom),25
(floppy),29(audio),44(video),46(plugdev),50(staff),110(powerdev),111
(vboxusers),1000(fj
Frans Pop schrieb:
> Package: kpowersave
> Version: 0.7.3-3
> Severity: serious
>
> Since the recent upgrade of dbus that changed default permissions I'm
> getting the following error in my logs when I suspend my notebook to
> RAM:
>
> Jan 19 11:47:25 aragorn dbus-daemon: Rejected send message, 2
Package: kpowersave
Version: 0.7.3-3
Severity: serious
Since the recent upgrade of dbus that changed default permissions I'm
getting the following error in my logs when I suspend my notebook to
RAM:
Jan 19 11:47:25 aragorn dbus-daemon: Rejected send message, 2 matched rules;
type="method_return"
14 matches
Mail list logo
