Your message dated Sat, 22 Aug 2020 15:20:20 +0000 with message-id <[email protected]> and subject line Bug#968033: Removed package(s) from unstable has caused the Debian Bug report #692344, regarding wicd-curses dies when moving around a conference to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 692344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692344 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: wicd Version: 1.7.2.4-2 Severity: normal I find that wicd-curses works fine when used in one place (work, home), but in a real conference setting with mulitple APs it often dies with: DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses. Traceback (most recent call last): File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper return func(*args, **kargs) File "/usr/share/wicd/curses/wicd-curses.py", line 727, in update_status if check_for_wired(wired.GetWiredIP(''),self.set_status): File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. This happens just from moving about between rooms, and thus APs. It may also happen from suspending/unsuspending the laptop - I've not checked carefully enough to be sure. So maybe half the time, after I've moved somewhere else after an hour or two, I find that the network is not up and wicd-curses is in this state. re-running it causes a re-connect or reports that the connection is already up. I generally leave wicd-curses running in a terminal for network monitoring purposes (I prefer it to the wicd-gtk interface). The wicd dameon always seems to be still running, contrary to the suggestion in the error message. It seems to me that wicd-curses should deal better with this state and continue running. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-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/dash Versions of packages wicd depends on: ii wicd-cli [wicd-client] 1.7.2.4-2 ii wicd-curses [wicd-client] 1.7.2.4-2 ii wicd-daemon 1.7.2.4-2 ii wicd-gtk [wicd-client] 1.7.2.4-2 wicd recommends no packages. wicd suggests no packages. Versions of packages wicd-cli depends on: ii python 2.7.3~rc2-1 ii wicd-daemon 1.7.2.4-2 Versions of packages wicd-cli recommends: ii sudo 1.8.5p2-1 Versions of packages wicd-gtk depends on: ii python 2.7.3~rc2-1 ii python-glade2 2.24.0-3 ii python-gtk2 2.24.0-3 ii wicd-daemon 1.7.2.4-2 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-6 ii python-notify 0.1.1-3 Versions of packages wicd-curses depends on: ii python 2.7.3~rc2-1 ii python-urwid 1.0.1-2 ii wicd-daemon 1.7.2.4-2 Versions of packages wicd-curses recommends: ii sudo 1.8.5p2-1 Versions of packages wicd-daemon depends on: ii adduser 3.113+nmu3 ii dbus 1.6.0-1 ii debconf 1.5.46 ii dhcp3-client 4.1.1-P1-17 ii ethtool 1:3.4.2-1 ii iproute 20120521-3 ii iputils-ping 3:20101006-1+b1 ii isc-dhcp-client [dhcp3-client] 4.2.2.dfsg.1-5+deb70u1 ii lsb-base 4.1+Debian7 ii net-tools 1.60-24.2 ii psmisc 22.19-1 ii python 2.7.3~rc2-1 ii python-dbus 1.1.1-1 ii python-gobject 3.2.2-1 ii python-wicd 1.7.2.4-2 ii wireless-tools 30~pre9-8 ii wpasupplicant 1.0-2 Versions of packages wicd-daemon recommends: ii wicd-cli [wicd-client] 1.7.2.4-2 ii wicd-curses [wicd-client] 1.7.2.4-2 ii wicd-gtk [wicd-client] 1.7.2.4-2 Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-9 Versions of packages python-wicd depends on: ii python 2.7.3~rc2-1 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3~rc2-2.1 -- debconf information: * wicd/users: wookey
--- End Message ---
--- Begin Message ---Version: 1.7.4+tb2-6+rm Dear submitter, as the package wicd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/968033 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)
--- End Message ---
