Your message dated Tue, 10 Nov 2009 22:38:17 +0100
with message-id <8b2d7b4d0911101338h5998ada5r9133fa3e85a61...@mail.gmail.com>
and subject line Re: Bug#555633: reportbug dies with a sys.excepthook error
has caused the Debian Bug report #555633,
regarding reportbug dies with a sys.excepthook error
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 ow...@bugs.debian.org
immediately.)
--
555633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 4.8
Severity: grave
Justification: renders package unusable
we...@westek:~$ reportbug
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such file or
directory
Error in sys.excepthook:
Original exception was:
we...@westek:~$ reportbug
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such file or
directory
/usr/lib/pymodules/python2.5/reportbug/ui/gtk2_ui.py:446: PangoWarning: Invalid
UTF-8 string passed to pango_layout_set_text()
gtk.main ()
we...@westek:~$ reportbug --configure
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such file or
directory
Error in sys.excepthook:
Original exception was:
we...@westek:~$ reportbug
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such file or
directory
-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"
** /home/westk/.reportbugrc:
reportbug_version "4.8"
mode novice
ui gtk2
email "we...@acu.edu"
no-cc
header "X-Debbugs-CC: we...@acu.edu"
smtphost reportbug.debian.org
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.20.2+lenny1 Advanced front-end for dpkg
ii python 2.5.4-2 An interactive high-level object-o
ii python-reportbug 4.8 Python modules for interacting wit
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn debconf-utils <none> (no description available)
pn debsums <none> (no description available)
pn dlocate <none> (no description available)
ii exim4 4.69-11 metapackage to ease Exim MTA (v4)
ii exim4-daemon-light [mail-tra 4.69-11+b1 lightweight Exim MTA (v4) daemon
ii file 5.03-2 Determines file type using "magic"
ii gnupg 1.4.10-2 GNU privacy guard - a free PGP rep
ii python-gtk2 2.12.1-6 Python bindings for the GTK+ widge
pn python-gtkspell <none> (no description available)
pn python-urwid <none> (no description available)
ii python-vte 1:0.16.14-4 Python bindings for the VTE widget
ii xdg-utils 1.0.2-6.1 desktop integration utilities from
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Kent,
On Tue, Nov 10, 2009 at 22:24, Kent West <we...@acu.edu> wrote:
> Ehm, no: there's something broken on your installation; I didn't close
> the bug because I may help you debugging it.
>
>
>
> Thank you.
you're welcome
> you're using reportbug at version 4.8 (which is only in
> unstable/testing) but your apt is configure to only look at 'stable'
> release. You have installed by hand some packages from
> unstable/testing, ain't you? that broke your system.
>
>
> Ah, now this starts to make sense.
>
> I had been running unstable, but then something broke in X so that my
> dual-monitor setup stopped working, and I tried for about six months to get
> it to work again, and finally gave up, and thought I had purged enough of
> the unstable system and reinstall it from stable to have my world working
> again, but apparently I missed something.
yeah, Xorg has moved a lot forward during this release cycle, and
sadly such things happen.
> In this case, it's pretty obvious to me that we're not looking at a bug in
> reportbug, but a failure on my part to run a clean system (and perhaps more
> generally in Debian's inability to downgrade the system - meh).
Well, it's much harder to support both smooth upgrades and downgrades.
Also, software tends to move forward, not backward :)
> I suggest you go ahead and close the bug report; it's not a problem on your
Ok, doing with this email.
> end, but on mine. (I don't expect to get it fixed anytime soon without a
> clean reinstall, so I'll just have to live with the various glitches that
well, there's something broken in the Gnome system, so that's
something you may want to look into asap.
> arise; it's my own fault for trusting unstable without really knowing what
> I'm doing (which worked for me for about 8 years without any real
> glitches).)
:)
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
