Package: linux-image-3.2.0-4-orion5x
Severity: critical
Tags: d-i upstream
Justification: breaks the whole system
Dear Maintainer,
I've got an old D-Link DNS-323 NAS box that I've been using for ARM
development for a number of years (Thanks, guys, for supporting it).
Anyway, I upgraded from Stabl
Subject: xfce4-power-manager: Broken empty battery icon on system tray
Package: xfce4-power-manager
Version: 1.0.10-3
Severity: normal
*** Please type your report below this line ***
After upgrading to XFCE 4.8 the icon for "empty battery" on the system
tray broke. I have two batteries, and when
In case the description was not clear enough... I just took a few
screenshots of that missing icon.
- Kim
<><><>
On 2011-06-05 10:48, Yves-Alexis Perez wrote:
After upgrading to XFCE 4.8 the icon for "empty battery" on the system
tray broke. I have two batteries, and when the first one is empty
and I'm _not_ plugged in I get the default "no icon found" icon for
that battery instead of the "empty battery" o
On 2011-06-05 13:00, Yves-Alexis Perez wrote:
Three different dumps attached. It's BAT1 that's showing the wrong icon
when it's empty and the laptop is not plugged in.
Assuming this is the third log, this is because BAT1 is not marked as
“empty” but discharging, with a very low charge. I gues
On 2011-06-05 13:21, Yves-Alexis Perez wrote:
Actually, the problem is the first log "upower-dump-0-perc.txt" (upower
dump at 0 percent, copy&pasted below). In that log the state of BAT1 is
"empty" as it should be, but the relevat icon is apparently not found
and an placeholder default icon is u
On 2011-06-05 13:25, Yves-Alexis Perez wrote:
And something which might be helpful too is running xfce4-power-manager
--dump in the “0 percent” situation, and running xfce4-power-manager
with --no-daemon and --debug (quit the running daemon first), so we have
an idea what xfpm is thinking about
On 2011-06-05 14:43, Yves-Alexis Perez wrote:
** (xfce4-power-manager:11351): WARNING **: Unable to load icon :
\u0018a\u001e\xad\xdb\u007f : Icon '\u0018a\u001e\xad\xdb\u007f' not
present in theme
Anyway, that looks like a pointer problem to me - if you decode the
UTF-8 string it makes no sens
On 2011-06-05 20:30, Yves-Alexis Perez wrote:
I traced the code a bit and found function xfpm_battery_refresh_icon()
which looks a bit fishy. It's the function that converts battery
percentage to an icon name.
So you have a tentative fix ready? I can try testing it, I should have a
mostly empt
On 2011-06-05 22:31, Yves-Alexis Perez wrote:
Yup, got a working patch. The bug was just shoddy coding - two if loops
with missing final elses and an uninitalizd string icon_name.
Attached simple patch fixes the if clauses and makes sure the string
variable is always defined before returning.
Package: milter-greylist
Version: 3.0-3.1
Severity: wishlist
Tags: patch
Here's a logcheck ignore file for milter-greylist so that logcheck will
ignore all "safe" lines in syslog and only report about the real problems.
Probably not comprehensive, but at least it's a good start.
I felt particul
Package: xserver-xorg-input-kbd
Version: 1:1.3.2-4
Severity: important
I just dist-upgraded my testing installation yesterday which updated
xorg to the latest level. This got rid of the old keyboard handling code
and switched to evdev.
Along with the change came the old bug I've had in Ubunt
Package: openssh-client
Version: 1:4.2p1-7
Severity: important
A regular apt-get update on my Debian Unstable today failed with the following
symptoms:
cube:~# apt-get -f install
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not
Justin Pryzby wrote:
A regular apt-get update on my Debian Unstable today failed with the following
symptoms:
Setting up openssh-client (4.2p1-7) ...
update-alternatives: internal error: /var/lib/dpkg/alternatives/rcp corrupt:
manflag
dpkg: error processing openssh-client (--configure):
>
T
On 2011-01-30 08:38, Cyril Brulebois wrote:
Along with the change came the old bug I've had in Ubuntu before:
keyboard repeat rate/delay works ok for all keyboards that are
plugged in while starting X, but any hotplugged keyboards default to
some strange repeat rate/delay. I can fix the problem
Package: rsyslog
Version: 3.18.6-4
Severity: wishlist
Tags: patch
Logcheck emails me every day telling me that yes, rsyslog has really been
restarted. Again.
Attached is an logcheck ignore file for rsyslog. It's not complete, but at
least it's a start and silences the daily notifications I get
Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
Uh-oh, the patch to a bug was buggy
Replace
x-pid="2061"
with
x-pid="[0-9]+"
- Kim
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
Michael Biebl wrote:
Logcheck emails me every day telling me that yes, rsyslog has really been
restarted. Again.
Attached is an logcheck ignore file for rsyslog. It's not complete, but at
least it's a start and silences the daily notifications I get.
I don't know anything about logcheck and
Michael Biebl wrote:
Could you provide a complete patch (against the source package) or at least more
detailed instructions how to correctly use it.
>>
If I do a complete patch, which version do you want it against?
The current version in unstable is preferred.
Patch against the sources in
Package: portmap
Version: 6.0.0-2
Severity: normal
Portmapper stopped working on my Testing system a while ago.
Can't really tell when, but NFS worked ok for a long time
and then one day about a month ago I noticed that it just
didn't work. Didn't really debug the problem until now...
As for sy
I had messed up my /etc/network/interfaces so that interface lo never
got up properly. That was the reason for non-working portmap...
- Kim
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: xserver-xorg-video-intel
Version: 2:2.12.0+shadow-2
Severity: normal
I dist-upgraded this Testing installation a few days ago and it totally
broke my X. After some hacking I figured out that the current X11 Intel
driver requires KMS which for some reason just didn't work for me
because
On 2010-10-26 19:34, Cyril Brulebois wrote:
>> I have nothing against KMS itself, but the fact that it cannot be
>> turned off pretty much ruins everything right now...
>
> can you please file a bug upstream for that? You may want to test a
> newer upstream snapshot first though: http://autobuild
On 2010-10-27 11:18, Cyril Brulebois wrote:
What's next - would you like me to file an upstream bug?
Yes please, giving me the URL or bug number so that I can link both
reports.
After trying experimental xorg (no working intel driver package -
boohoo), purging all of xorg and reinstalling t
24 matches
Mail list logo
