Bug#588618: network-manager-gnome needs tighter dep on network-manager
As said, the only possible explanation I have, is that you upgraded the packages, suspended your laptop (then, NM is disabled by /usr/lib/pm-utils/sleep.d/55NetworkManager), your resume failed and you had to reboot. This is exactly what happened to me. As this is the first time that I've ever had a suspend failure on this laptop (suspend light was on, but CPU and LCD were still on, so the laptop was roasting when I got it out of my bag) I'm suspecting that NM was responsible for the suspend failure too. Anyway, that isn't the point. Please make the deps tighter so that the client and the daemon can always talk. This time it's just the global on/off, but in the future who knows what will change. Ross -- Ross Burton mail: r...@burtonini.com jabber: r...@burtonini.com www: http://burtonini.com signature.asc Description: This is a digitally signed message part
Bug#588618: [Pkg-utopia-maintainers] Bug#588618: Bug#588618: Bug#588618: network-manager-gnome needs tighter dep on network-manager
severity 588618 important thanks hi michael, On Sat, Jul 10, 2010 at 05:57:20PM +0200, Michael Biebl wrote: As said, the only possible explanation I have, is that you upgraded the packages, suspended your laptop (then, NM is disabled by /usr/lib/pm-utils/sleep.d/55NetworkManager), your resume failed and you had to reboot. After the reboot NM stayed in disabled state and you weren't able to enable NM via nm-applet. after some testing i think this sounds the most plausible situation. my laptop crashes every day or two (ah, the joys of running bleeding edge gallium drivers) and I can confirm that rebooting and normal suspend/resume function just fine wrt n-m. however, if the system crashes on the way in or out of suspend, then we get this problem on the next boot. so i guess the argument for grave is a bit more tenuous, and since you've already voiced your opinion on the matter i'll go ahead and lower it in good faith that we'll see a fix soon anyway :) sean signature.asc Description: Digital signature
Bug#588618: network-manager-gnome needs tighter dep on network-manager
Package: network-manager-gnome
Version: 0.8.0.999-1
Severity: grave
Justification: renders package unusable
Hi there,
the latest n-m update was partially blocked by the updated dependency on
isc-dhcp-client, which in turn conflicts with the latest version of
resolvconf. unfortunately the dependencies in n-m-gnome (n-m = 0.7)
are a little too loose and as a result n-m-gnome was updated while n-m
was held back.
the resulting situation is that n-m-gnome is completely unusable as i guess
there's some incompatibilities between 0.8 and 0.8.0.999. i don't
know the relations in n-m well enough to know if a ${source:Version} or
${binary:Version} would be appropriate here, but i suggest that you at
least bump dependency for n-m-gnome to nm = 0.8.0.999-1 in the meantime.
sean
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35-rc4minime-00955-g60c07e7 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager-gnome depends on:
ii dbus-x111.2.24-1 simple interprocess messaging syst
ii gconf2 2.28.1-3 GNOME configuration database syste
ii gnome-icon-theme2.30.3-1 GNOME Desktop icon theme
ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst
ii libdbus-glib-1-20.86-1 simple interprocess messaging syst
ii libfontconfig1 2.8.0-2.1generic font configuration library
ii libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii libgconf2-4 2.28.1-3 GNOME configuration database syste
ii libglade2-0 1:2.6.4-1library to load .glade files at ru
ii libglib2.0-02.24.1-1 The GLib library of C routines
ii libgnome-bluetooth7 2.30.0-2 GNOME Bluetooth tools - support li
ii libgnome-keyring0 2.30.1-1 GNOME keyring services library
ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface
ii libnm-glib-vpn1 0.8.0.999-1 network management framework (GLib
ii libnm-glib2 0.8.0.999-1 network management framework (GLib
ii libnm-util1 0.8.0.999-1 network management framework (shar
ii libnotify1 [libnotify1- 0.5.0-2 sends desktop notifications to a n
ii libpango1.0-0 1.28.1-1 Layout and rendering of internatio
ii libxml2 2.7.7.dfsg-4 GNOME XML library
ii network-manager 0.8.0.999-1 network management framework daemo
ii policykit-1-gnome 0.96-2 GNOME authentication agent for Pol
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages network-manager-gnome recommends:
ii gnome-bluetooth 2.30.0-2 GNOME Bluetooth tools
ii libpam-gnome-keyring [libpam- 2.30.1-2 PAM module to unlock the GNOME key
ii mobile-broadband-provider-inf 20100702-1 database of mobile broadband servi
ii notification-daemon 0.5.0-2daemon to displays passive pop-up
Versions of packages network-manager-gnome suggests:
ii network-manager-openvpn-gnome 0.8-1 network management framework (Open
pn network-manager-pptp-gnomenone (no description available)
pn network-manager-vpnc-gnomenone (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588618: [Pkg-utopia-maintainers] Bug#588618: network-manager-gnome needs tighter dep on network-manager
On 10.07.2010 13:57, sean finney wrote:
Package: network-manager-gnome
Version: 0.8.0.999-1
Severity: grave
Justification: renders package unusable
Hi there,
the latest n-m update was partially blocked by the updated dependency on
isc-dhcp-client, which in turn conflicts with the latest version of
resolvconf. unfortunately the dependencies in n-m-gnome (n-m = 0.7)
are a little too loose and as a result n-m-gnome was updated while n-m
was held back.
the resulting situation is that n-m-gnome is completely unusable as i guess
there's some incompatibilities between 0.8 and 0.8.0.999. i don't
know the relations in n-m well enough to know if a ${source:Version} or
${binary:Version} would be appropriate here, but i suggest that you at
least bump dependency for n-m-gnome to nm = 0.8.0.999-1 in the meantime.
Could you be more specific, what you did and what problems you had.
Did you do a partial upgrade of the network-manager, i.e. you only upgrade the
libnm-* libs to 0.8.0.999 but not network-manager itself?
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#588618: [Pkg-utopia-maintainers] Bug#588618: network-manager-gnome needs tighter dep on network-manager
On 10.07.2010 14:12, Michael Biebl wrote: Did you do a partial upgrade of the network-manager, i.e. you only upgrade the libnm-* libs to 0.8.0.999 but not network-manager itself? To be more clear about this: what combination of packages and versions did you test, which didn't work 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#588618: [Pkg-utopia-maintainers] Bug#588618: network-manager-gnome needs tighter dep on network-manager
hi michael, On Sat, Jul 10, 2010 at 02:12:30PM +0200, Michael Biebl wrote: Could you be more specific, what you did and what problems you had. the applet remains visible but the enable networking option remains unselectable (if you select it it stays disabled). so it is not possible to use either wired or wireless networking without manually configuring it via dhclient/iwconfig etc. Did you do a partial upgrade of the network-manager, i.e. you only upgrade the libnm-* libs to 0.8.0.999 but not network-manager itself? yeah. when i did an apt-get upgrade it brought in libnm-util1 libnm-glib-vpn1 libnm-glib2 and network-manager-gnome, but network-manager remained at the previous version because of the situation with isc-dhcp-client and resolvconf. sean signature.asc Description: Digital signature
Bug#588618: [Pkg-utopia-maintainers] Bug#588618: network-manager-gnome needs tighter dep on network-manager
On Sat, Jul 10, 2010 at 02:16:22PM +0200, Michael Biebl wrote: libnm-* libs to 0.8.0.999 but not network-manager itself? To be more clear about this: what combination of packages and versions did you test, which didn't work i believe everything except network-manager was updated to 0.8.0.999. sean signature.asc Description: Digital signature
Bug#588618: [Pkg-utopia-maintainers] Bug#588618: Bug#588618: network-manager-gnome needs tighter dep on network-manager
On 10.07.2010 14:28, sean finney wrote: hi michael, On Sat, Jul 10, 2010 at 02:12:30PM +0200, Michael Biebl wrote: Could you be more specific, what you did and what problems you had. the applet remains visible but the enable networking option remains unselectable (if you select it it stays disabled). so it is not possible to use either wired or wireless networking without manually configuring it via dhclient/iwconfig etc. Did you do a partial upgrade of the network-manager, i.e. you only upgrade the libnm-* libs to 0.8.0.999 but not network-manager itself? yeah. when i did an apt-get upgrade it brought in libnm-util1 libnm-glib-vpn1 libnm-glib2 and network-manager-gnome, but network-manager remained at the previous version because of the situation with isc-dhcp-client and resolvconf. Ok, I just tested this combination. networkmanager-gnome 0.8.0.999 libnm-* libs 0.8.0.999 network-manager 0.8 And this combination works more or less fine for me. I can activate existing connections (system/user), create new ones, delete existing ones. The only issue I can confirm is, that indeed, the Enable/Disable network button is not selectable. (The reason for this is, that in 0.8.0.999, there is a distinction between user intiated or system initiated state changes and the new nm-gnome makes use of this new API which nm 0.8 doesn't offer). That said, while I agree, that bumping the dep on nm to = 0.8.0.999 in nm-gnome is probably the right thing to do, the severity grave is not justified given that I'm still able to use nm-applet. How did you end up with a disabled networkmanager? Did you disable it before you upgraded or did you have a failed suspend/resume in between? Michael Did you perhaps disable network, upgrade nm-gnome and afterwards you -- 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#588618: [Pkg-utopia-maintainers] Bug#588618: Bug#588618: network-manager-gnome needs tighter dep on network-manager
hi michael, On Sat, Jul 10, 2010 at 02:43:06PM +0200, Michael Biebl wrote: That said, while I agree, that bumping the dep on nm to = 0.8.0.999 in nm-gnome is probably the right thing to do, the severity grave is not justified given that I'm still able to use nm-applet. How did you end up with a disabled networkmanager? Did you disable it before you upgraded or did you have a failed suspend/resume in between? i rebooted and it didn't work when my laptop came back up. actually i upgraded the other packages earlier this morning and the system was working fine until that point. could you see if you can reproduce that, to make sure it wasn't something with just my system? sean -- signature.asc Description: Digital signature
Bug#588618: [Pkg-utopia-maintainers] Bug#588618: Bug#588618: Bug#588618: network-manager-gnome needs tighter dep on network-manager
On 10.07.2010 15:14, sean finney wrote: hi michael, Hi On Sat, Jul 10, 2010 at 02:43:06PM +0200, Michael Biebl wrote: That said, while I agree, that bumping the dep on nm to = 0.8.0.999 in nm-gnome is probably the right thing to do, the severity grave is not justified given that I'm still able to use nm-applet. How did you end up with a disabled networkmanager? Did you disable it before you upgraded or did you have a failed suspend/resume in between? i rebooted and it didn't work when my laptop came back up. actually i upgraded the other packages earlier this morning and the system was working fine until that point. could you see if you can reproduce that, to make sure it wasn't something with just my system? I can't reproduce the problem. You you redo all steps, and save /var/lib/NetworkManager/NetworkManager.state after the upgrade (when NM still works) and after the reboot (when NM is disabled). As said, the only possible explanation I have, is that you upgraded the packages, suspended your laptop (then, NM is disabled by /usr/lib/pm-utils/sleep.d/55NetworkManager), your resume failed and you had to reboot. After the reboot NM stayed in disabled state and you weren't able to enable NM via nm-applet. 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
