Bug#507843: network-manager: fails to connect to 3G until 'noauth' is added to /etc/ppp/options

Package: network-manager
Version: 0.7.0-1
Severity: normal

Out of the box, 'noauth' is not set in /etc/ppp/options. In this state, 3G
connections will fail with no explanation given. Adding 'noauth' fixes the
problem.

'man pppd' says that this option is privileged. This might conceivably pose a
problem.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager depends on:
ii  adduser                3.110             add and remove users and groups
ii  dbus                   1.2.1-4           simple interprocess messaging syst
ii  hal                    0.5.11-6          Hardware Abstraction Layer
ii  ifupdown               0.6.8+nmu1        high level tools to configure netw
ii  libc6                  2.7-16            GNU C Library: Shared libraries
ii  libdbus-1-3            1.2.1-4           simple interprocess messaging syst
ii  libdbus-glib-1-2       0.76-1            simple interprocess messaging syst
ii  libgcrypt11            1.4.1-2           LGPL Crypto library - runtime libr

Bug#507842: network-manager: fails to connect over 3G if ppp is not installed

Package: network-manager
Version: 0.7.0-1
Severity: normal

If 'ppp' is not installed (as is relatively likely, as currently
network-manager does not depend on it in any way and soon will merely Recommend
it) 3G connections immediately fail with no explanation.

This situation should be handled more gracefully.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager depends on:
ii  adduser                3.110             add and remove users and groups
ii  dbus                   1.2.1-4           simple interprocess messaging syst
ii  hal                    0.5.11-6          Hardware Abstraction Layer
ii  ifupdown               0.6.8+nmu1        high level tools to configure netw
ii  libc6                  2.7-16            GNU C Library: Shared libraries
ii  libdbus-1-3            1.2.1-4           simple interprocess messaging syst
ii  libdbus-glib-1-2       0.76-1            simple interprocess messaging syst
ii  libgcrypt11            1.4.1-2           LGPL Crypto library - runtime libr
ii  libglib2.0-0           2.18.3-1          The GLib library of C routines

Processed: severity of 507815 is important

Processing commands for control <at> bugs.debian.org:

> severity 507815 important
Bug#507815: consolekit: race condition during D-Bus activation
Severity set to `important' from `normal'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Processed: tagging 507815

Processing commands for control <at> bugs.debian.org:

> tags 507815 confirmed
Bug#507815: consolekit: race condition during D-Bus activation
There were no tags set.
Tags added: confirmed

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Bug#507733: Edit Connections crashes if PolicyKit is not installed

Package: network-manager-gnome
Version: 0.7.0-1

network-manager recommends, but does not depend on, policykit. However,
when I did not have policykit installed, right-clicking nm-applet,
picking Edit Connections, picking Mobile Broadband, clicking Add,
choosing any option and clicking Okay crashed the Edit Connections
dialog, with the following printed to nm-applet's tty:

** (nm-connection-editor:19482): WARNING **: Failed to initialize
PolicyKit context: (null)
[WARN 19482] polkit-error.c:156:polkit_error_free(): error != NULL
 Not built with -rdynamic so unable to print a backtrace

--

-- 
Will

_______________________________________________
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers <at> lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-utopia-maintainers

[Fwd: Re: Bug#507630: Acknowledgement (nautilus: Is gnome-volume-manager obsolete with nautils 2.24.x?)]

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

From: Michael Biebl <biebl <at> debian.org>
Subject: Re: Bug#507630: Acknowledgement (nautilus: Is gnome-volume-manager obsolete with nautils 2.24.x?)
Date: 2008-12-03 19:55:18 GMT

Sven Arvidsson wrote:
> On Wed, 2008-12-03 at 19:10 +0100, Michael Biebl wrote:
>>> If I go to Edit->Preferences->Media in nautilus, there is a
>>> configuration tab for media handling (although here everything is greyed
>>> out, which is probably a bug on its own).
>> Attached is a screenshot, which shows what I mean. I have totem and gthumb
>> installed, fwiw.
> 
> It's probably a bug that you can't assign an application of your choice
> even if none are found, anyway...
> 
> For gthumb, you probably need the version in experimental:
> http://bugzilla.gnome.org/show_bug.cgi?id=560352
> 
> For totem, i guess not being registered as a music player is a feature.

Bug#507614: NetworkManager segfaults

Package: network-manager
Version: 0.6.6-2
Severity: important

I just got two seemingly identical NM segfaults.  The log reads:

Dec  3 00:40:53 radis NetworkManager: <info>  Activation (wlan0/wireless): association took too long
(>120s), failing activation.
Dec  3 00:40:53 radis NetworkManager: <info>  Activation (wlan0) failed for access point (XXXXXX)
Dec  3 00:40:53 radis NetworkManager: <info>  Activation (wlan0) failed.
Dec  3 00:40:53 radis NetworkManager: <info>  Deactivating device wlan0.
Dec  3 00:40:53 radis NetworkManager: <info>  Activation (wlan0) failure scheduled...
Dec  3 00:40:53 radis NetworkManager: <WARN>  nm_signal_handler(): Caught signal 11.  Generating backtrace...
Dec  3 00:40:53 radis NetworkManager: ******************* START **********************************
Dec  3 00:40:53 radis NetworkManager: Frame 0: /usr/sbin/NetworkManager [0x428c37]
Dec  3 00:40:53 radis NetworkManager: Frame 1: /usr/sbin/NetworkManager [0x428e00]
Dec  3 00:40:53 radis NetworkManager: Frame 2: /lib/libpthread.so.0 [0x7fe138279a80]
Dec  3 00:40:53 radis NetworkManager: Frame 3: /usr/sbin/NetworkManager [0x42df77]
Dec  3 00:40:53 radis NetworkManager: Frame 4: /usr/lib/libglib-2.0.so.0 [0x7fe138726d5e]
Dec  3 00:40:53 radis NetworkManager: Frame 5:
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x35c) [0x7fe1387278ac]
Dec  3 00:40:53 radis NetworkManager: Frame 6: /usr/lib/libglib-2.0.so.0 [0x7fe13872af5d]
Dec  3 00:40:53 radis NetworkManager: Frame 7: /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1cd) [0x7fe13872b48d]
Dec  3 00:40:53 radis NetworkManager: Frame 8: /usr/sbin/NetworkManager [0x4129d2]
Dec  3 00:40:53 radis NetworkManager: Frame 9: /usr/lib/libglib-2.0.so.0 [0x7fe138750454]
Dec  3 00:40:53 radis NetworkManager: Frame 10: /lib/libpthread.so.0 [0x7fe138271fc7]
Dec  3 00:40:53 radis NetworkManager: Frame 11: /lib/libc.so.6(clone+0x6d) [0x7fe137fe75ad]
Dec  3 00:40:53 radis NetworkManager: ******************* END **********************************

I'll try to rebuild with debugging symbols and get a core dump.

Bug#507565: Bug#507565: Bug#507565: Bug#507565: network-manager-gnome: nm-applet crashes - symbol lookup error

Thanks so much for your help...even though that wasn't a real bug!
Thanks a million...it works.

Best regards

Am Dienstag, den 02.12.2008, 18:57 +0100 schrieb Michael Biebl:
> rapper wrote:
> > I installed the deb packages through apt-get, I didn't compile them
> > myself.
> > 
> > ldd /usr/bin/nm-applet
> 
> > 	libnm-util.so.0 => /usr/local/lib/libnm-util.so.0 (0xb779e000)
>                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Here we are. This file seems to come from a local installation.
> Remove this local installation and it should work.
> 
> 
> 
> The system libnm-util0 lib is fine:
> 
> > 000065a0 g    DF .text	0000006a  Base        dbus_method_dispatcher_new
> 
> Cheers,
> Michael
> 
> 

Bug#507565: network-manager-gnome: nm-applet crashes - symbol lookup error

Subject: network-manager-gnome: nm-applet crashes - symbol lookup error
Package: network-manager-gnome
Version: 0.6.6-2
Severity: important

*** Please type your report below this line ***
When trying to start nm-applet I get the following message:
>nm-applet
nm-applet: symbol lookup error: nm-applet: undefined symbol: 
dbus_method_dispatcher_new

Here's the tail of strace nm-applet:
read(3, 
"\34\"\250\0\3\0@\3\202\1\0\0\221\10\325\0\0\1\0\0\2\0\0\0\1\0\0\0\320~F
\10"..., 
4096) = 32
read(3, 0x808c1fc, 4096)                = -1 EAGAIN (Resource 
temporarily unavailable)
select(4, [3], [3], NULL, NULL)         = 1 (out [3])
writev(3, [{"\31\0\v\0\341\0\0\1\0\0\0\0! 
\0\0\341\0\0\1}\1\0\0\221\10\325\0\0\0\0\0\3"..., 48}], 1) = 48
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1\2\252\0\0\0\0\0\272>\200\2\\\326 
\10Tj\213\277\0\25\227\10\304\"\36\10\2113\t\10"..., 4096) = 32
read(3, 0x808c1fc, 4096)                = -1 EAGAIN (Resource 
temporarily unavailable)
writev(2, [{"nm-applet"..., 9}, {": "..., 2}, {"symbol lookup
error"..., 
19}, {": "..., 2}, {"nm-applet"..., 9}, {": "..., 2}, {"undefined 
symbol: dbus_method_dis"..., 44}, {""..., 0}, {""..., 0}, {"\n"...,

Bug#504918: [Debian Wiki] Update of "NewInLenny" : Upgrade over SSH issue

Here's the data you requested; I'm sorry it doesn't seem to be of much help (the data in syslog seems to have
aged out).

One thing that may have had an impact - drive space was very low during the upgrade and could have conceivably
been completely used up at the time.

-Rob

elm:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
        address 10.240.0.50
        netmask 255.255.255.0
        gateway 10.240.0.1
elm:/var/log# zcat /var/log/sysl*gz /var/log/syslog* | grep NetworkManager

gzip: /var/log/syslog: not in gzip format

gzip: /var/log/syslog.0: not in gzip format
elm:~# zcat /var/log/sysl*gz | grep Network ; grep Network /var/log/sysl*
elm:~# /etc/init.d/network-manager restart
Restarting network connection manager: NetworkManager.

Bug#504918: [Debian Wiki] Update of "NewInLenny" : Upgrade over SSH issue

severity 504918 grave
--

[BCC Stuart Prescott: "stuart+debian AT nanonanonano net"]

Hello Stuart,

(I hope you are the right "Stuart")

You added the following comment on the wiki page:

On Mon, 2008-12-01 at 18:27 +0000, Debian Wiki wrote:
> The following page has been changed by StuartPrescott:
[..]
> +  * Upgrading over ssh when the connection is managed by NetworkManager can 
> lead the upgrade failing/hanging when the NetworkManager service is restarted.
> If you are lucky, the ssh connection will not drop out; if you are unlucky, 
> the ssh connection will drop out and at the next interactive point in the 
> upgrade (e.g. dpkg "replace this file" or debconf) the entire upgrade is 
> left in a horrible state.

I didn't found a bug report from you. However I fount those two bug that
are similar.

* Network-manager shouldn't stop the network during an upgrade
  http://bugs.debian.org/474352
* Updating to lenny failed when NetworkManager got updated
  http://bugs.debian.org/504918

It looks like it could hurt many user that upgrade [lots of] desktops