Re: [Council] Maemo 5 gets community OS updates
 

As I've commented on the bug: the attachments are sent fine, it's just than modest is using the incorrect MIME type for the message (multipart/alternative instead of multipart/mixed) so some mail clients (correctly) don't show anything other than the the first part (which is the message text).

Re: [Council] Maemo 5 gets community OS updates
 

I've had this since before installation of the CSSU, reckon it might simply be a MicroB bug or alternatively some app screwing with the UI.

Re: The in-development Maemo 5 Community SSU
 

Only once i got two browsers opened by bookmark, but I noticed now that email isn't working. Picture attachment plus text does not work at all..:(

Nothing else so far...

Re: The in-development Maemo 5 Community SSU
 

So far I have found only one bug; I normally use my phone book by just start typing persons name on desktop.

That doesn't work with CSSU, everytime I wanna search someone from phone book, I need first open phone book application.

Even my OC's were there after update... :)

BIG thanks for update!

Re: The in-development Maemo 5 Community SSU
 

That's fixed with the gconf command (search the thread for details).

Re: The in-development Maemo 5 Community SSU
 

i lost no functionality when updating to CSSU, apart from modded hildon-desktop

Re: [Council] Maemo 5 gets community OS updates
 

sorry for not knowing what those multipart/alternative/mixed means..

basically what I mean is that, when i try to send the attachments/pictures via n900, it doesn't get sent like how I receive mail sent from my laptop. I sent an email to myself via laptop and checked from the phone and it was fine...

more importantly, how then do we make it back to normal? thanks

Re: [Council] Maemo 5 gets community OS updates
 

An email message has a MIME type which indicates what the content is - for a simple email this is usally text/plain. A lot of clients nowadays use HTML instead though, in which case the MIME type would be text/html. However, to support older clients they can also send a plain text version alongside the HTML version. Now the overall message is tagged as multipart/alternative - multipart because there's more than one section in the message (each of which will have its own MIME type) and alternative because the sections should be just alternative versions (so the client can just pick the best one to show). The sections will then in turn be tagged as text/html and text/plain respectively.

If you're using attachments, the MIME type for the overall message should instead be multipart/mixed - there's multiple parts again, but they're not just alternative versions of the same message.

The version of modest in the CSSU gets this wrong, so although the message still actually contains the attachments, many clients will fail to show them (as they think they're just different forms of the same message).

Yeah - that's how it shows up. If you use a different client then you may see the attachments - modest will show them fine for example. That's why some people just aren't seeing this problem - their client shows all the parts, irrespective of whether they're just alternatives.

It needs a new modest release including a patch for this, or a rollback to the standard PR1.3 version.

Re: [Council] Maemo 5 gets community OS updates
 

One question, is there any middleware upgrade in this CSSU?

If not, it would be great for next releases if some stuff like Pulseaudio, dbus or bluez could be updated without breaking applications.

Re: [Council] Maemo 5 gets community OS updates
 

Very odd. It never happened to me before CSSU. I think I found a pattern. It happens mostly the first time. Just like only the first link from desktop lets the bookmarks window behind. All subsequent links work fine.

Can I reliably reproduce this bug? I like it :)