severity 568971 important
thanks

Jö Fahlke wrote:
> Package: modemmanager
> Version: 0.3-1
> Severity: normal
> 
> I had the same problem after an interactive upgrade with aptitude.  But I
> noticed it before it filled up my harddrive :)
> 
> The problem went away after "invoke-rc.d dbus restart":
> ======================================================================
> Stopping network connection manager: NetworkManager.
> Stopping Hardware abstraction layer: hald.
> Stopping bluetooth: bluetoothd.
> Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon.
> Stopping system message bus: dbus.
> Starting system message bus: dbus.
> Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
> Starting bluetooth: bluetoothd.
> Starting Hardware abstraction layer: hald.
> Starting network connection manager: NetworkManager.
> ======================================================================
> 
> Attached are to excerpts from my syslog, one from the initial start of the
> modemmanager during upgrade and one from the restart of dbus above.  I removed
> log entries for services I deemed irrelevant.  If you suspekt some of the
> removed entries are indeed relevant, please ask for them.
> 
> The thing that strikes me about the logs is that there is a flurry of restarts
> of the modemmanager by the NetworkManager in the same second, then nothing for
> exactly two minutes, then again a flurry of restarts and so on.
> 
> Bye,
> Jö.
> 
> -- System Information:
> Debian Release: squeeze/sid
>   APT prefers testing-proposed-updates
>   APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
> Architecture: i386 (x86_64)
> 
> Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages modemmanager depends on:
> ii  libc6                         2.10.2-2   GNU C Library: Shared libraries
> ii  libdbus-1-3                   1.2.16-2   simple interprocess messaging 
> syst

So far, this doesn't look like a modemmanager bug per se.

It looks like dbus is not correctly picking up the installed modemmanager dbus
policy file after installation, which leads to the flood of access denials.
D-Bus uses inotify to monitor /etc/dbus-1 for changes, and there were fixes in
1.2.20 which particularly address bugs in the inotify handling [1].
So far, all bug reporters seems to have used dbus 1.2.16. 1.2.20 has migrated to
testing already, so it is likely this particular issue won't show up again (and
unless someone confirms this with dbus 1.2.20, I'll keep this bug at severity
important).
Nonetheless, there are a couple of things we might consider:
1.) modemmanager could reload dbus manually in postinst, to trigger a reload of
the dbus config files
2.) network-manager should be more clever when trying to reconnect to
modemmanager and not simply try to do it brute force. It could use something
like a exponential back off.

cheers,
Michael


[1]
http://cgit.freedesktop.org/dbus/dbus/commit/?h=dbus-1.2&id=8a9880ffd2b81df38bb0e3492bda7a9636ac0280


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

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to