On Sat, Apr 12, 2008 at 03:01:47PM +0200, Michael Biebl wrote:
> Jarek Kamiński wrote:
>> How do kpowersave and knetworkmanager handle this situation? They both
>> sit on panel during upgrade, detect dbus going down and reconnects, when
>> it's started again.
>> Working network connection is still
Jarek Kamiński wrote:
> On Wed, Jun 13, 2007 at 07:43:17PM +0200, Michael Biebl wrote:
>
> I've just found this bug fixed and read its log.
>
>> Antti-Juhani Kaijanaho wrote:
>>> On Wed, Jun 13, 2007 at 05:59:23PM +0200, Michael Biebl wrote:
How is NM supposed to know if dbus is started agai
On Wed, Jun 13, 2007 at 07:43:17PM +0200, Michael Biebl wrote:
I've just found this bug fixed and read its log.
> Antti-Juhani Kaijanaho wrote:
>> On Wed, Jun 13, 2007 at 05:59:23PM +0200, Michael Biebl wrote:
>>> How is NM supposed to know if dbus is started again? Should it poll forever
>>> in
I've got a laptop running network-manager with kde. Apt sources are nfs mounts
with file:// urls. Upgrading dbus disconnects the cabled network, aptitude
will then be unable to load and unpack packages from the network.
A workaround exists: running dhclient eth0 re-starts the cabled network
con
On Wed, Jun 13, 2007 at 07:43:17PM +0200, Michael Biebl wrote:
> Don't be shy, just tell your ideas, because I don't have an elegant
> solution for this.
Another thing: how does dbus communicate with its clients? If it's a named
pipe or some other filesystem object, could you directly watch it?
On Wed, Jun 13, 2007 at 07:43:17PM +0200, Michael Biebl wrote:
> Don't be shy, just tell your ideas, because I don't have an elegant
> solution for this.
One possibility (I haven't feasibility checked it, though) is to have dbus keep
a pidfile in a known location, which NM can then watch (using in
Antti-Juhani Kaijanaho wrote:
> On Wed, Jun 13, 2007 at 05:59:23PM +0200, Michael Biebl wrote:
>> How is NM supposed to know if dbus is started again? Should it poll forever
>> in a
>> while loop checking for a dbus connection?
>
> I rather think that this is a problem for the NM and dbus maintai
On Wed, Jun 13, 2007 at 05:59:23PM +0200, Michael Biebl wrote:
> How is NM supposed to know if dbus is started again? Should it poll forever
> in a
> while loop checking for a dbus connection?
I rather think that this is a problem for the NM and dbus maintainers to solve,
not me the bug reporter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antti-Juhani Kaijanaho wrote:
> On Wed, Jun 13, 2007 at 02:53:22PM +0200, Michael Biebl wrote:
>> NetworkManager has to be restarted during dbus upgrades, because being a
>> D-Bus
>> application, it won't survive if the system bus is killed.
>
> Soun
On Wed, Jun 13, 2007 at 02:53:22PM +0200, Michael Biebl wrote:
> NetworkManager has to be restarted during dbus upgrades, because being a D-Bus
> application, it won't survive if the system bus is killed.
Sounds like here is the place where any fixes should go. NM should be able to
survive dbus s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antti-Juhani Kaijanaho wrote:
> Package: dbus
> Version: 1.1.0-1
>
> Preparing to replace dbus 1.0.2-5 (using .../dbus_1.1.0-1_amd64.deb) ...
> Stopping network connection manager: NetworkManager.
> Stopping Hardware abstraction layer: hald.
> Stoppin
Package: dbus
Version: 1.1.0-1
Preparing to replace dbus 1.0.2-5 (using .../dbus_1.1.0-1_amd64.deb) ...
Stopping network connection manager: NetworkManager.
Stopping Hardware abstraction layer: hald.
Stopping DHCP D-Bus daemon: dhcdbd.
Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Stopping Syst
12 matches
Mail list logo
