Mpris Plugin for tunecontroller

Hi,

I slightly changes Matthieu Volat's mpris code so that it only creates
one mpris plugin. The patch should work with every mpris compatible
player (tested with audacious and a xmms2 mpris extension)
The patch can also be pulled from http://github.com/caotic/psi/tree/master

Hi,

I slightly changes Matthieu Volat's mpris code so that it only creates
one mpris plugin. The patch should work with every mpris compatible
player (tested with audacious and a xmms2 mpris extension)
The patch can also be pulled from http://github.com/caotic/psi/tree/master

Re: Nightly builds crash on MacOS X

$ gdb ./src/psi.app/Contents/MacOS/psi
Unknown signature value:  668
instance = ITunesPlugin
instance = PsiFilePlugin
instance = opensslPlugin
instance = gnupgPlugin
instance = ITunesPlugin
instance = PsiFilePlugin
instance = opensslPlugin
instance = gnupgPlugin
Unknown signature value:  668

*** Here I quit the application ***

instance = XMPP::JDnsProvider

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0xb0240790
0x01c2b656 in QObject::~QObject ()
(gdb)
(gdb) bt
#0  0x01c2b656 in QObject::~QObject ()
#1  0x004eafb1 in
XMPP::NetInterfaceManagerPrivate::~NetInterfaceManagerPrivate
(this=0x205a1b10) at ../corelib/netinterface.cpp:323
#2  0x004e8ade in XMPP::NetInterfaceManager::~NetInterfaceManager
(this=0x205a1788) at ../corelib/netinterface.cpp:448
#3  0x0050a167 in XMPP::JDnsGlobal::~JDnsGlobal (this=0x205a1760) at
../corelib/netnames_jdns.cpp:288
#4  0x004f9b46 in XMPP::JDnsProvider::~JDnsProvider (this=0x205a1590)

Re: Nightly builds crash on MacOS X

> Any ideas as to when this started happening?  By the trace, it looks like a
> crash I fixed in September.

Also, look at the 'About->Psi' dialog, and tell us the date please.
Might be something wrong with the nightly build too.

cheers,
Remko

Nightly builds crash on MacOS X

Hi,
the crash happens when quitting the application and it's 99% reproducible.

Process:         psi [208]
Path:            /Applications/Psi.app/Contents/MacOS/psi
Identifier:      org.psi-im
Version:         Psi 0.13-devel (0.13-devel)
Code Type:       X86 (Native)
Parent Process:  launchd [118]

Date/Time:       2008-11-16 01:26:57.468 +0100
OS Version:      Mac OS X 10.5.5 (9F33)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000b02407d0
Crashed Thread:  0

Thread 0 Crashed:
0   QtCore                              0x016f81b6 QObject::~QObject() + 118
1   org.psi-im                          0x0035cbb7
XMPP::NetInterfaceManagerPrivate::~NetInterfaceManagerPrivate() + 125
2   org.psi-im                          0x0035bc32
XMPP::NetInterfaceManager::~NetInterfaceManager() + 84
3   org.psi-im                          0x0036e45a
XMPP::JDnsGlobal::~JDnsGlobal() + 272
4   org.psi-im                          0x0036605b
XMPP::JDnsProvider::~JDnsProvider() + 47
5   org.psi-im                          0x0035a65f
XMPP::PluginInstance::~PluginInstance() + 31

gmail video chat

<div>
<a href="http://www.google.com/mail/help/videochat/learnmore.html">http://www.google.com/mail/help/videochat/learnmore.html</a><br clear="all"><br>-- <br>$signature = "Hal Rottenberg, MVP - Admin Frameworks"<br>$projects =  <at> { title = "Blog Author"; url = "<a href="http://halr9000.com">http://halr9000.com</a>" },<br>
 &nbsp; <at> { title = "Co-host"; url = "<a href="http://powerscripting.net">http://powerscripting.net</a>" },<br> &nbsp; <at> { title = "Community Director"; url = "<a href="http://PowerShellCommunity.org">http://PowerShellCommunity.org</a>" },<br>
 &nbsp; <at> { title = "Psi Webmaster"; url = "<a href="http://psi-im.org">http://psi-im.org</a>" }<br><br><br>
</div>

Strange Send file behaviour

Hi,

if I decide to send a file to one of my contacts, the send file dialog
opens and with it instantly the file chooser.
If I now press Cancel in the file chooser, the send file dialog remains
open.
Is that the desired behaviour? I mean, what could that dialog be useful for
at that time?

Regards

Fwd: Psi Jabber Client - FS#187: Make popups configurable (Attachment added)

FYI

---------- Forwarded message ----------
From: Psi Jabber Client <flyspray@...>
Date: Thu, Nov 6, 2008 at 1:22 AM
Subject: Psi Jabber Client - FS#187: Make popups configurable
(Attachment added)
To: hal@...

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#187 - Make popups configurable
User who did this - C.H. (chtesterp)

----------
I merged my PsiPopup patch with Machekku's patch "Avatars in Popup"
pictures here http://paveltitkov.blogspot.com/2008/11/psipopup-avatar-patch.html
----------

One or more files have been attached.

More information can be found at the following URL:
http://flyspray.psi-im.org/task/187#comment924

You are receiving this message because you have requested it from the
Flyspray bugtracking system.  If you did not expect this message or
don't want to receive mails in future, you can change your
notification settings at the URL shown above.

--

-- 
$signature = "Hal Rottenberg, MVP - Admin Frameworks"
$projects = @{ title = "Blog Author"; url = "http://halr9000.com" },
  @{ title = "Co-host"; url = "http://powerscripting.net" },
  @{ title = "Community Director"; url = "http://PowerShellCommunity.org" },
  @{ title = "Psi Webmaster"; url = "http://psi-im.org" }

[PATCH] OS X link fix

Hi,

the attached patch fixes psi linking on OS X for me, I need to link explicitely 
against the Cocoa framework to make it work.

Regards,

From be37ba0724baa8253048bbf23ee2d45642ee6016 Mon Sep 17 00:00:00 2001
From: Frank Osterfeld <osterfeld@...>
Date: Thu, 6 Nov 2008 11:53:43 +0100
Subject: [PATCH] fix build on OS X: link against Cocoa

---
 src/CocoaUtilities/CocoaUtilities.pri |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/src/CocoaUtilities/CocoaUtilities.pri b/src/CocoaUtilities/CocoaUtilities.pri
index b77fb37..7da5402 100644
--- a/src/CocoaUtilities/CocoaUtilities.pri
+++ b/src/CocoaUtilities/CocoaUtilities.pri
@@ -1,6 +1,8 @@
 INCLUDEPATH *= $$PWD/..
 DEPENDPATH *= $$PWD $$PWD/..

+LIBS += -framework Cocoa
+
 HEADERS += \
 	$$PWD/CocoaInitializer.h

-- 
1.6.0.2

From be37ba0724baa8253048bbf23ee2d45642ee6016 Mon Sep 17 00:00:00 2001
From: Frank Osterfeld <osterfeld@...>
Date: Thu, 6 Nov 2008 11:53:43 +0100
Subject: [PATCH] fix build on OS X: link against Cocoa

---
 src/CocoaUtilities/CocoaUtilities.pri |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/src/CocoaUtilities/CocoaUtilities.pri b/src/CocoaUtilities/CocoaUtilities.pri
index b77fb37..7da5402 100644
--- a/src/CocoaUtilities/CocoaUtilities.pri
+++ b/src/CocoaUtilities/CocoaUtilities.pri
@@ -1,6 +1,8 @@
 INCLUDEPATH *= $$PWD/..
 DEPENDPATH *= $$PWD $$PWD/..

+LIBS += -framework Cocoa
+
 HEADERS += \
 	$$PWD/CocoaInitializer.h

--

-- 
1.6.0.2

Whiteboard not ready yet

While the whiteboard engine itself may be all well and good, the presentation 
of the whiteboarding feature in Psi needs some work before I'd consider it 
release quality.

When a whiteboard is session is requested, there is no window or anything to 
indicate that there is an outbound whiteboarding request.  Several times it 
has happened to me, that I click the whiteboard option in the menu of a 
contact, click 'No' on the question about loading an SVG file, and I'm left 
with nothing on the screen (leading me to think that I actually cancelled my 
whiteboarding request).  Then, much later, the remote contact acks the 
request and I suddenly get a whiteboard from nowhere.  Also, there's no way 
to cancel an outbound request.

When a whiteboarding request is received, there is no queued event.  Instead, 
a yes/no prompt is thrown in my face.

For the whiteboard to be ready for prime time, we need:
 - some WbRequestDlg or such, analogous to FileRequestDlg
 - outbound requests are shown visibly and are cancelable
 - a PsiEvent for whiteboard requests, that can be queued in the roster/tray
 - inbound request handler shown when the event is opened

Additionally there are some smaller issues which should probably be addressed:
 - I sometimes experience crashes on accept (still).  I stupidly didn't have 
coredumps enabled last it happened, but I'm willing to do tests with anyone 
to reproduce.
 - I don't like how whiteboards share the chatdlg sizing info.  as a non-tabs 
user, I'd prefer to have groupchats, regular chats, and whiteboards all at 
varying sizes.  this is probably an easy fix, just allocate a new options 
variable for the whiteboard size.
 - There appears to be no indication that the other party has left the 
whiteboard, or at least I couldn't find it.  This is pretty important 
information I think. :)

-Justin

0.13 feature freeze

Hi all,
  The devteam just entered feature freeze for 0.13, so no new code
will be committed until 0.13 release that doesn't fix a
release-critical bug.
Now and the coming weeks are a good time to get testing and help out ;)

/K

Trunk Source Access

<div><p>Hello Everyone,<br><br>I'm attempting to update a couple patches against the current trunk, but I've ran into some problems.&nbsp; I followed the public SVN instructions, but the resulting source doesn't build on my machine, despite 0.12 building correctly.&nbsp; So, I did some more research and found this post (<a href="http://lists.affinix.com/htdig.cgi/psi-devel-affinix.com/2008-August/008206.html">http://lists.affinix.com/htdig.cgi/psi-devel-affinix.com/2008-August/008206.html</a>), which hints that Psi might have moved to Git.&nbsp; When I attempt to pull that source via the Eclipse Git plugin, I get an error message about corrupt data and the import never completes.&nbsp; I suspect that could be a problem with the Git plugin, but I haven't looked into that issue furth
 er.<br><br>Now, my question:<br><br>I can attempt to use the command line instructions given in that somewhat old e-mail and then figure out Git, but I'd like to know that I'm even heading in the right direction.&nbsp; Could someone please confirm that those instructions are still valid, if the Wiki should be updated away from SVN instructions, etc?&nbsp; Also, what is the current patch submission method?&nbsp; Do I use git for that, should I be sending a seperate patch (like when the developers were on darcs, but everyone else was asked to move to SVN), etc?<br><br><br>Thanks,<br><br>-Rick<br></p></div>