Sure, why not. A slp* crash was fixed today btw so I'll do a new build soon.hippy dave wrote:yeah i've been getting occasional crashes, which look to be slp-related - eg. the last one:
want the debug logs?
If so, then it's ok now. btw, unlike Adium29 would suggest, the problem was present in all messages styles.supertoom2 wrote:In the 24709 build I can't see time stamps in the conversations, it just says HH.mm.
okay, good to know.Chabou wrote:By timestamps you mean this bug I think ?
If so, then it's ok now. btw, unlike Adium29 would suggest, the problem was present in all messages styles.supertoom2 wrote:In the 24709 build I can't see time stamps in the conversations, it just says HH.mm.
You have to reset that in advanced -> Messages as the ticket for the bug says. http://trac.adiumx.com/ticket/10630supertoom2 wrote:For me the timestamp bug is half fixed, half still there. The time in the header of the conversation is displayed correctly, so are the day/year/date in the status field, but for the time for every single message sent, it still says HH.mm.
Code: Select all
Date/Time: 2008-08-16 14:00:55.717 +0800
OS Version: Mac OS X 10.5.4 (9E17)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000005
Crashed Thread: 0
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x9011f2d4 CFRetain + 36
1 com.apple.CoreFoundation 0x900adf25 CFArrayCreate + 357
2 com.apple.CFNetwork 0x95e748a8 CFHostCreateWithName + 72
3 com.adiumX.AdiumPurple 0x1845e24a -[AdiumPurpleDnsRequest startLookup] + 171
4 com.adiumX.AdiumPurple 0x1845e42d adiumPurpleDnsRequestResolve + 58
5 libpurple 0x1861a5ac purple_dnsquery_ui_resolve + 69
6 libpurple 0x1861affd handle_next_queued_request + 92
7 libpurple 0x1861b3e6 resolve_host + 27
8 com.adiumX.AdiumPurple 0x18439150 callTimerFunc + 120
9 com.apple.CoreFoundation 0x9011db45 CFRunLoopRunSpecific + 4469
10 com.apple.CoreFoundation 0x9011dcf8 CFRunLoopRunInMode + 88
11 com.apple.HIToolbox 0x96e15da4 RunCurrentEventLoopInMode + 283
12 com.apple.HIToolbox 0x96e15bbd ReceiveNextEventCommon + 374
13 com.apple.HIToolbox 0x96e15a31 BlockUntilNextEventMatchingListInMode + 106
14 com.apple.AppKit 0x90daa505 _DPSNextEvent + 657
15 com.apple.AppKit 0x90da9db8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
16 com.apple.AppKit 0x90da2df3 -[NSApplication run] + 795
17 com.apple.AppKit 0x90d70030 NSApplicationMain + 574
18 com.adiumX.adiumX 0x00003522 _start + 216
19 com.adiumX.adiumX 0x00003449 start + 41You are running the official beta or at least not one of my builds so why do you write about it here? If you are running the official beta(the one on beta.adiumx.com) which it looks like you do you should report this problem to trac.lukeoldboy wrote:Hello, it's my first message here! I'm using adium 1.3b11 exclusively with msn protocol (thank you for the personal messages support!), it works fine, except for a crash occurring every time I'm talking with a specific contact (using amsn on mac). The scenario: we begin a chat, and I don't close the window (let's suppose I leave the room...): if I just click on the window after a while (5-10 mins), adium always crashes.
That's great!hippy dave wrote:well i haven't had any more slp crashes (or any other crashes) since updating to your latest build a few days ago
Hi DimmuxxDimmuxx wrote:
Sure, why not. A slp* crash was fixed today btw so I'll do a new build soon.
Edit: New build is out and let's hope this one built correctly for ppc. Please report if the timestamps work correctly too.
Interesting. How did the MSNP15 for 10.4 users go out in the end? MSNP15 in a 1.3.x update, or won't they get it at all?Dimmuxx wrote:That's great!hippy dave wrote:well i haven't had any more slp crashes (or any other crashes) since updating to your latest build a few days ago
Fun fact: Pidgin 2.5.0 with msnp15 was released today and the only major protocol that people haven't found any big problems with is msn so it seems that all the testing did pay off.
The current plan is to include it in a 1.3.x update but this might change.David Munch wrote: Interesting. How did the MSNP15 for 10.4 users go out in the end? MSNP15 in a 1.3.x update, or won't they get it at all?
MSN works fine for me. It can send *gasp* messages.markes wrote:Adium team, we hope you prioritize MSN more. We know you are not using it and we know it depends on Pidgin, but whole Europe are using MSN mainly. Proper MSN support will make Adium a LOT better.
I'm not sure how we *could* prioritize it more than we are at the moment, considering there's two projects (msn-pecan and libpurple's msnp15) both moving specifically it forward, as opposed to 0 specific projects for the other protocols. We may hate it (I certainly do), but since we're forced to support it, it may as well work well.markes wrote:Adium team, we hope you prioritize MSN more. We know you are not using it and we know it depends on Pidgin, but whole Europe are using MSN mainly. Proper MSN support will make Adium a LOT better.
my typewriter worked just fine! i don't know why i buy a Mac *gasp*David Munch wrote: MSN works fine for me. It can send *gasp* messages.
The games my friend, the games...neckaros wrote:my typewriter worked just fine! i don't know why i buy a Mac *gasp*David Munch wrote: MSN works fine for me. It can send *gasp* messages.
