Laurent: First off, thanks so much for the backtrace; it's exactly what
I thought it would be. Should this not be filed as a new bug?
The patch for the corrupt shac value blatantly ignores the exception (just logs
it) because the value is not used anywhere else, and ignoring it follows the
logic
Can anyone please attach a backtrace?
--
telepathy-butterfly crashed with TypeError in b64decode()
https://bugs.launchpad.net/bugs/401028
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Debdiff of upstream patch to stop saving stale colors in the header
cache
** Attachment added: "mutt_1.5.20-4ubuntu1.1.debdiff"
http://launchpadlibrarian.net/40994740/mutt_1.5.20-4ubuntu1.1.debdiff
--
Previously tagged messages keep the associated background color until message
is again disp
Public bug reported:
Binary package hint: mutt
See http://dev.mutt.org/trac/ticket/3376
Header cache stores previous color settings.
** Affects: mutt (Ubuntu)
Importance: Undecided
Status: New
--
Previously tagged messages keep the associated background color until message
is a
Can anyone with the error on lucid please file a separate bug and attach a
backtrace?
On launchpad, insist that it is not a duplicate bug.
The original exception is caught and ignored, so this exception must be
happening elsewhere, likely in the b64decode of the other data hash
nearby (sha1d).
-
I've reproduced this locally by sending a malformed SHA1C value via an
msn_object avatar. It's not as trivial to reproduce using the
telepathy/papyon framework since SHA1C values are normally ignored in
all cases, but still processed. Yes, you read that correctly.
Going along with upstream's metho
** This bug has been flagged as a security vulnerability
--
telepathy-butterfly crashed with TypeError in b64decode()
https://bugs.launchpad.net/bugs/401028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
I wish I could tell you guys what my fix was :-/ I realize how annoying
and inconvenient this bug is.
--
Backlight control doesn't work anymore on thinkpad
https://bugs.launchpad.net/bugs/313231
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Somewhere on a reboot after the session where I executed xrandr, my
brightness controls began functioning as normal - Thinkpad X61s, other
details available in my last comment.
--
Backlight control doesn't work anymore on thinkpad
https://bugs.launchpad.net/bugs/313231
You received this bug notif
Any updates on this?
Bug confirmed:
X61s
2.6.27-11-generic
The function keys do not adjust the backlight brightness
same dmesg
brightness_enable=1 has no result
acpitool -l adjusts brightness just fine
executing:
xrandr --output LVDS --set BACKLIGHT_CONTROL native
makes everything function "prope
10 matches
Mail list logo
