Package: gnome-power-manager
Version: 2.20.1-1
Severity: important
Gnome-power-manager properly shows all batteries, but the estimation of
the remaining uptime seem to only take into account the first one.
For instance, my laptop has two batteries : the built-in one, and an
additional one.
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 12:09:47 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
I'm out of idea; try to identify the broken file with:
scrollkeeper-rebuilddb -v
as root or strace it.
--
Loïc Minier
___
pkg-gnome-maintainers mailing list
pkg-gnome-maintainers@lists.alioth.debian.org
Your message dated Fri, 14 Dec 2007 12:47:07 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452090: fixed in gtkmm2.4 1:2.12.3-1
has caused the attached Bug report 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 message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
Your message dated Fri, 14 Dec 2007 11:40:07 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing old gconf bugs
has caused the attached Bug report 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 14 Dec 2007 14:34:11 +0800
Source: glibmm2.4
Binary: libglibmm-2.4-dev libglibmm-2.4-doc libglibmm-2.4-1c2a libglibmm-2.4-dbg
Architecture: source all i386
Version: 2.14.2-3
Distribution: unstable
Urgency: low
Maintainer: Deng
Package: gdm
Version: 2.20.2-1
Followup-For: Bug #454097
ls --color still generates ansi control character when it
is invoked from gdm (also if you redirect output to pipe
or a file). I think the solution would be using /bin/ls
in Xsession instead of ls. See following Ubuntu bug report
for
Package: gtk+2.0
Version: 2.12.3-2
Severity: minor
The *.pc files of the libraries have a Requires: relation to the
libraries they need themselves. This is not the proper way to do this.
Requires: is meant for libraries which need to be directly linked by
any program linking the library. This
Package: epiphany-gecko
Version: 2.20.2-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The site at http://www.nintendo.co.uk/NOE/en_GB/ does not display
properly. It looks as if the CSS is not loaded/processed.
The site looks fine in Iceweasel.
- -- System Information:
Congratulations!!Your email I.D was selected and you have therefore
been awarded the sum of 750,000GBP by the microsoft promo. so contact the agent
email below:
[EMAIL PROTECTED]
Thank you.
___
pkg-gnome-maintainers mailing list
Package: gnome-applets
Version: 2.20.0-1+b1
Followup-For: Bug #448833
Hi,
launching from terminal:
$ /usr/lib/gnome-applets/cpufreq-applet
** (cpufreq-applet:7356): WARNING **: Error getting CPUINFO_MAX
(cpufreq-applet:7356): GLib-GObject-WARNING **: value -1 of type `gint' is
invalid or out
Package: gnome-keyring
Version: 2.20.2-1
Severity: normal
I run gnome-keyring-daemon with libpam-gnome-keyring. If I restart
dbus (/etc/init.d/dbus restart), gnome-keyring-daemon stops running.
In particular, this means that now when I restart dbus to unwedge
network-manager (which I do
Package: gnome-terminal
Version: 2.18.3-1
--- Please enter the report below this line. ---
This bug is dupplucate of bug #362156.
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-3-686
Debian Release: lenny/sid
500 unstableftp.fr.debian.org
--- Package
FYI: The status of the hotwire source package
in Debian's testing distribution has changed.
Previous version: 0.595-1
Current version: 0.620-2
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
Package: nautilus
Version: 2.18.3-3
Followup-For: Bug #454297
Nautilus restars when selected propierties in a .jpg file
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU
Your message dated Sat, 15 Dec 2007 04:55:52 +0100
with message-id [EMAIL PROTECTED]
and subject line libwnck18: dependencies problem
has caused the attached Bug report 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
Subject: Tries to remove non-existent /var/lib/gconf on purge
Package: gconf2
Version: 2.20.1-1
Severity: normal
Observe the following transcript
$ sudo aptitude purge -y ~c
E: /home/twb/.aptitude is readable but not writable; unable to write
configuration file.
Reading package
34 matches
Mail list logo
