[Bug 401028] Re: telepathy-butterfly crashed with TypeError in b64decode()

2010-04-06 Thread temugen
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 of the rest of the codebase. However, ignoring corrupted shad values in 
this way could be a bad idea. If the data hash is corrupt, that signals that 
the data (a profile icon for example) could also be corrupt. Now, there are two 
reasonable ways to fix this:
A) Follow the logic set in place by the codebase as if the data hashes, while 
valid, don't match. I haven't look at the code yet but I believe that logic is 
to drop the invalid data message. After logging, this would be the proper way 
to handle corrupt data imo.
B) Let FD.o take care of it. It should be up to them how they want to handle 
corrupt messages.

Unfortunately there are still many unchecked exceptions throughout
papyon aside from this one.

-- 
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 401028] Re: telepathy-butterfly crashed with TypeError in b64decode()

2010-03-22 Thread temugen
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 539348] Re: Previously tagged messages keep the associated background color until message is again displayed

2010-03-16 Thread temugen
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 displayed
https://bugs.launchpad.net/bugs/539348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 539348] [NEW] Previously tagged messages keep the associated background color until message is again displayed

2010-03-15 Thread temugen
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 again displayed
https://bugs.launchpad.net/bugs/539348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 401028] Re: telepathy-butterfly crashed with TypeError in b64decode()

2010-03-10 Thread temugen
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).

-- 
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 401028] Re: telepathy-butterfly crashed with TypeError in b64decode()

2009-11-08 Thread temugen
** 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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 401028] Re: telepathy-butterfly crashed with TypeError in b64decode()

2009-11-08 Thread temugen
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 methodology that the checksum is redundant
and all that is necessary is the data (for which the hash is properly
compared and handled), I've written a patch to silently ignore malformed
checksums and log a warning when doing so. Other than that, I guess
we'll have to wait for upstream to decide how they want to properly
handle this field, since as of now it's just a waste of clock cycles as
far as I can tell.

My patch right now only addresses the base 64 decoding issue in SHA1C
parsing that everyone seems to be having, and there is more to take care
of as far as DoSing with unexpected data goes. For example, a ParseError
is raised when there is no xml data, but that again crashes the
conversation. KeyErrors are raised when certain attributes are missing
from the xml, which too crash the conversation.

For upstream see bug #24138.

** Attachment added: 02_fix_malformed_sha1c.diff
   http://launchpadlibrarian.net/35357473/02_fix_malformed_sha1c.diff

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 313231] Re: Backlight control doesn't work anymore on thinkpad

2009-03-18 Thread temugen
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 Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 313231] Re: Backlight control doesn't work anymore on thinkpad

2009-03-15 Thread temugen
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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 313231] Re: Backlight control doesn't work anymore on thinkpad

2009-02-27 Thread temugen
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 properly

I've looked into the acpi events and scripts, and I don't think the problem 
resides there.
I can provide more information and logs.

-- 
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 Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs