Your message dated Wed, 16 Jun 2010 22:17:30 +0000
with message-id <[email protected]>
and subject line Bug#582824: fixed in update-manager 0.200.4-1
has caused the Debian Bug report #582824,
regarding ChangelogViewer sudo gnome-open fails if gksu in __init__.py uses su
mode
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.)
--
582824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582824
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: update-manager-gnome
Version: 0.200.3-2
Severity: important
Tags: squeeze
For the times when clicking on a bug link in the changelog has worked
(it has been broken on and off for various reasons for the past couple of
years),
I have had to run with with gksu set to 'sudo mode' in Gconf. While trying
to the current broken ChangelogViewer.py (see http://bugs.debian.org/546837)
I changed the gksu back to the default 'su mode', but the gnome-open of
the linked bug report failed with the following error:
GConf Error: Failed to contact configuration server; some possible causes are
that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information.
(Details - 1: Failed to get connection to session: /usr/bin/dbus-launch
terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.
After changing the mode (via Gnome Configuration Editor) back to 'sudo mode'
the links open fine (with the changes I have made to ChangelogViewer.py).
I have a feeling this is due to the underlying gksu behavior, but the code
in update-manager
was changed in how the call to gnome-open was done, and the changes are such
that
gksudo cannot be called (the UID of the originating user is used instead of the
USERNAME from the environment).
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages update-manager-gnome depends on:
ii gconf2 2.28.1-3 GNOME configuration database syste
ii gksu 2.0.2-2+b1 graphical frontend to su
ii python 2.5.4-9 An interactive high-level object-o
ii python-dbus 0.83.1-1 simple interprocess messaging syst
ii python-gconf 2.28.1-1 Python bindings for the GConf conf
ii python-gobject 2.21.1-1 Python bindings for the GObject li
ii python-gtk2 2.17.0-2 Python bindings for the GTK+ widge
ii python-support 1.0.8 automated rebuilding support for P
ii python-vte 1:0.24.1-1 Python bindings for the VTE widget
ii update-manager-core 0.200.3-2 APT update manager core functional
update-manager-gnome recommends no packages.
Versions of packages update-manager-gnome suggests:
ii software-properties-gtk 0.60.debian-1.1 manage the repositories that you i
ii update-notifier 0.99.3debian4 Daemon which notifies about packag
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: update-manager
Source-Version: 0.200.4-1
We believe that the bug you reported is fixed in the latest version of
update-manager, which is due to be installed in the Debian FTP archive:
update-manager-core_0.200.4-1_all.deb
to main/u/update-manager/update-manager-core_0.200.4-1_all.deb
update-manager-doc_0.200.4-1_all.deb
to main/u/update-manager/update-manager-doc_0.200.4-1_all.deb
update-manager-gnome_0.200.4-1_all.deb
to main/u/update-manager/update-manager-gnome_0.200.4-1_all.deb
update-manager_0.200.4-1.diff.gz
to main/u/update-manager/update-manager_0.200.4-1.diff.gz
update-manager_0.200.4-1.dsc
to main/u/update-manager/update-manager_0.200.4-1.dsc
update-manager_0.200.4.orig.tar.gz
to main/u/update-manager/update-manager_0.200.4.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stephan Peijnik <[email protected]> (supplier of updated update-manager package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Mon, 24 May 2010 13:10:26 +0200
Source: update-manager
Binary: update-manager-core update-manager-doc update-manager-gnome
Architecture: source all
Version: 0.200.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian GNOME Maintainers
<[email protected]>
Changed-By: Stephan Peijnik <[email protected]>
Description:
update-manager-core - APT update manager core functionality
update-manager-doc - Update Manager API documentation
update-manager-gnome - GNOME application that manages software updates
Closes: 580570 581262 582824
Changes:
update-manager (0.200.4-1) unstable; urgency=low
.
* Fixed AttributeError in ChangeLogViewer (Closes: #580570, #581262,
#582824).
* 00_pygtk_api_change.diff: Removed, included in upstream release now.
Checksums-Sha1:
79c161e531f62f41923de814e441d961005b3fd5 1775 update-manager_0.200.4-1.dsc
a1c557f9394df2769edce522c3c10607d8c3cd5a 1784431
update-manager_0.200.4.orig.tar.gz
9cfeafa956019fc36aff4589991f708ea6b79eb1 23210 update-manager_0.200.4-1.diff.gz
3e3db65dbf6cd5b91329204051082dd4373e7cda 117726
update-manager-core_0.200.4-1_all.deb
daeca7da10a0f928bd153249d67c72bf13b8d1c1 81718
update-manager-doc_0.200.4-1_all.deb
7e5031a2ee4c357e3206760a1de6b932a12bcadb 754470
update-manager-gnome_0.200.4-1_all.deb
Checksums-Sha256:
2aa9cfd595bca0279a0d235fbc36bad089eeff569246711c0dd53afffacf00d9 1775
update-manager_0.200.4-1.dsc
05cd65b7c057b8c339af4a34aefc643ca2b4878acaf4c8a4e84817eb65676b31 1784431
update-manager_0.200.4.orig.tar.gz
8cc2f42559a8996e577da2c7d006e354c95b631bafea9c22bc16a1ea66db4e28 23210
update-manager_0.200.4-1.diff.gz
017e96fe20d9be2c1a564696f300ed208f2a7afe17e5726dfa3d92857a6fc0a7 117726
update-manager-core_0.200.4-1_all.deb
23c2af83bd66f23d0632f82dd90260e8923e7e37fd08909e838dad27851381dc 81718
update-manager-doc_0.200.4-1_all.deb
73aa40af7203eb330fb4dd1800abbf2339b8832b16f36fb5e2b64eec7533509b 754470
update-manager-gnome_0.200.4-1_all.deb
Files:
5b7746514964e9222957a69acef53e46 1775 admin optional
update-manager_0.200.4-1.dsc
8415502b258568286007bcbcc11557ac 1784431 admin optional
update-manager_0.200.4.orig.tar.gz
c73554bd34d0e6e721c3da4913be8e91 23210 admin optional
update-manager_0.200.4-1.diff.gz
b5a9a21e9321f74468f29b86352566aa 117726 admin optional
update-manager-core_0.200.4-1_all.deb
36337090acb207f270c45e84b2d8f6cc 81718 doc optional
update-manager-doc_0.200.4-1_all.deb
96ef4ddf02f316930ee4e24b90df1ee8 754470 gnome optional
update-manager-gnome_0.200.4-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFMGUswrSla4ddfhTMRAmZXAJ9lN1Qrb+P6WCgoa1m+ksh683cHrgCeJk4J
dfs0h7SS4QGCREkHvKc/bsY=
=tb5D
-----END PGP SIGNATURE-----
--- End Message ---
